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.

3.4.5 Log files and debugging -- 3.5 Manual configuration -- 3.5.1 Non-standard Order Management and call.connect installation -- 3.5.2 WebSphere manual configuration -- 3.5.3 Manual client installation -- 3.6 Alternative configurations -- 3.6.1 Setting up a test instance of WebSphere -- 3.6.2 Setting up an iSeries server for a test system -- 3.6.3 Server configuration -- 3.6.4 WebSphere administration -- 3.6.5 Manual client installation -- Chapter 4. Installing and setting up vendor.connect -- 4.1 Preparing for the installation -- 4.1.1 Skills required -- 4.2 Installing vendor.connect -- 4.2.1 System21 base -- 4.2.2 Java components and configuration files -- 4.2.3 Restoring libraries -- 4.2.4 Installing and configuring WebSphere -- 4.2.5 IBM HTTP Server for iSeries -- 4.2.6 MQSeries -- 4.2.7 Work Management Trigger Handler for the iSeries -- 4.2.8 Active Architecture framework -- 4.2.9 JConnects server -- 4.2.10 Setting up new vendor.connect user IDs and supplier IDs -- 4.2.11 Database synchronization from System21 to the vendor.connect database -- 4.2.12 Testing the vendor.connect Web site -- 4.2.13 Backing up the configuration components -- 4.3 Changing the iSeries on which the application is running -- 4.4 Housekeeping -- 4.4.1 Daily -- 4.4.2 Stopping -- 4.4.3 Starting -- 4.4.4 Restoring the vendor.connect IFS objects -- Chapter 5. Performance tuning -- 5.1 Hardware -- 5.2 Operating System/400 (OS/400) -- 5.2.1 SQL server job configuration -- 5.2.2 Toolbox JDBC driver -- 5.2.3 Subsystems and memory pools -- 5.2.4 Automatic performance adjustment -- 5.2.5 Manual performance adjustment -- 5.3 Stateless and stateful connections, datasources, connection pools, etc. -- 5.3.1 Stateful connections -- 5.3.2 Stateless connections -- 5.3.3 Total connections and SQL server jobs -- 5.4 Performance topics for Java virtual machine (JVM) settings.

5.4.1 Initial Java heap size -- 5.4.2 Maximum Java heap size -- 5.4.3 Verbose garbage collection -- 5.4.4 Static compilation -- Chapter 6. Tips and techniques -- 6.1 The iSeries integrated file system -- 6.1.1 Using File Transfer Protocol (FTP) with the iSeries IFS -- 6.1.2 Mapping a PC drive to the iSeries IFS -- 6.1.3 Editing an iSeries stream file using a PC editor -- 6.1.4 Stream files and CCSID -- 6.1.5 The cd command -- 6.1.6 Managing stream files with the OS/400 WRKLNK command -- 6.1.7 Other stream file commands -- 6.1.8 Stream file authority -- 6.1.9 Editing an iSeries stream file using the OS/400 EDTF command -- 6.2 The Qshell -- 6.2.1 Managing stream files with Qshell commands -- 6.2.2 The touch and setccsid commands -- 6.2.3 Viewing an iSeries stream file using the Qshell tail command -- 6.2.4 Qshell scripts -- 6.3 Checking the QEJBSBS subsystem -- 6.3.1 Instance monitor jobs -- 6.3.2 Instance administration jobs -- 6.3.3 Specifying ports -- 6.3.4 Application server jobs -- 6.4 WebSphere versions on the iSeries, your console system, and clients -- 6.4.1 Checking the WebSphere PTF level on the iSeries -- 6.4.2 Checking the WebSphere PTF level on a PC -- 6.5 Common problems with commerce.connect on iSeries -- 6.5.1 Problems connecting the console to WebSphere on the iSeries -- 6.5.2 Checking the iSeries name as required by WebSphere -- 6.5.3 Checking the iSeries database name -- Related publications -- IBM Redbooks -- Other resources -- Referenced Web sites -- How to get IBM Redbooks -- IBM Redbooks collections -- Index -- Back cover.