Geac System21 commerce.connect : Implementation on the IBM eServer iSeries Server

Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. The .connect applications -- 1.1 call.connect -- 1.2 vendor.connect -- Chapter 2. Architecture of the commerce.connect products -- 2.1 The need for an architecture -- 2.1.1 Key Enterprise JavaBeans and WebSphere Application Server benefits -- 2.1.2 The architecture moving forward -- 2.1.3 The development process -- 2.1.4 Implementation -- 2.1.5 The design methodology: Using Unified Modelling Language -- 2.2 Messaging: Java Message Service and IBM WebSphere MQ -- 2.2.1 call.connect -- 2.2.2 vendor.connect -- 2.3 Overview of process.connect -- 2.4 Architectural representation -- 2.4.1 Architectural goals and constraints -- 2.4.2 Non-functional architectural considerations -- 2.4.3 Functional architectural considerations -- 2.5 Reusing and extending System21 business logic -- 2.5.1 Accessing System21 RPG business logic -- Chapter 3. Installing and setting up call.connect -- 3.1 Skills and prerequisites for installing, running WebSphere Application Server -- 3.1.1 Skills -- 3.1.2 Prerequisites -- 3.1.3 System21 authorization code for Order Management (OM) -- 3.2 Standard installation procedures -- 3.2.1 Installing Order Management and call.connect -- 3.2.2 WebSphere installation and configuration -- 3.2.3 Journaling -- 3.2.4 Stored procedures and SQL -- 3.2.5 Java Message Service -- 3.2.6 User profiles -- 3.2.7 System21 data set up -- 3.2.8 Java Web Start -- 3.2.9 Backup -- 3.3 call.connect housekeeping -- 3.3.1 Daily backups -- 3.3.2 Stopping WebSphere -- 3.3.3 Starting call.connect -- 3.3.4 Restoring IFS objects -- 3.4 Troubleshooting -- 3.4.1 WebSphere node name -- 3.4.2 Errors on starting the client -- 3.4.3 Errors when running the client -- 3.4.4 Cached data and .bl and .cd files.