BenutzerhandbuchInhaltsverzeichnisFront cover1Contents5Notices9Trademarks10Preface11The team that wrote this redbook11Become a published author11Comments welcome12Chapter 1. The .connect applications131.1 call.connect141.2 vendor.connect16Chapter 2. Architecture of the commerce.connect products192.1 The need for an architecture202.1.1 Key Enterprise JavaBeans and WebSphere Application Server benefits202.1.2 The architecture moving forward212.1.3 The development process222.1.4 Implementation222.1.5 The design methodology: Using Unified Modelling Language222.2 Messaging: Java Message Service and IBM WebSphere MQ242.2.1 call.connect242.2.2 vendor.connect262.3 Overview of process.connect272.4 Architectural representation282.4.1 Architectural goals and constraints282.4.2 Non-functional architectural considerations282.4.3 Functional architectural considerations292.5 Reusing and extending System21 business logic292.5.1 Accessing System21 RPG business logic29Chapter 3. Installing and setting up call.connect313.1 Skills and prerequisites for installing, running WebSphere Application Server323.1.1 Skills323.1.2 Prerequisites323.1.3 System21 authorization code for Order Management (OM)343.2 Standard installation procedures343.2.1 Installing Order Management and call.connect353.2.2 WebSphere installation and configuration363.2.3 Journaling393.2.4 Stored procedures and SQL413.2.5 Java Message Service433.2.6 User profiles483.2.7 System21 data set up513.2.8 Java Web Start513.2.9 Backup643.3 call.connect housekeeping643.3.1 Daily backups643.3.2 Stopping WebSphere643.3.3 Starting call.connect653.3.4 Restoring IFS objects653.4 Troubleshooting653.4.1 WebSphere node name663.4.2 Errors on starting the client663.4.3 Errors when running the client663.4.4 Cached data and .bl and .cd files663.4.5 Log files and debugging673.5 Manual configuration683.5.1 Non-standard Order Management and call.connect installation683.5.2 WebSphere manual configuration693.5.3 Manual client installation733.6 Alternative configurations743.6.1 Setting up a test instance of WebSphere743.6.2 Setting up an iSeries server for a test system753.6.3 Server configuration763.6.4 WebSphere administration773.6.5 Manual client installation78Chapter 4. Installing and setting up vendor.connect854.1 Preparing for the installation864.1.1 Skills required864.2 Installing vendor.connect864.2.1 System21 base874.2.2 Java components and configuration files874.2.3 Restoring libraries884.2.4 Installing and configuring WebSphere884.2.5 IBM HTTP Server for iSeries914.2.6 MQSeries1004.2.7 Work Management Trigger Handler for the iSeries1014.2.8 Active Architecture framework1014.2.9 JConnects server1044.2.10 Setting up new vendor.connect user IDs and supplier IDs1044.2.11 Database synchronization from System21 to the vendor.connect database1154.2.12 Testing the vendor.connect Web site1174.2.13 Backing up the configuration components1174.3 Changing the iSeries on which the application is running1174.4 Housekeeping1174.4.1 Daily1174.4.2 Stopping1174.4.3 Starting1184.4.4 Restoring the vendor.connect IFS objects118Chapter 5. Performance tuning1195.1 Hardware1205.2 Operating System/400 (OS/400)1215.2.1 SQL server job configuration1215.2.2 Toolbox JDBC driver1255.2.3 Subsystems and memory pools1275.2.4 Automatic performance adjustment1335.2.5 Manual performance adjustment1345.3 Stateless and stateful connections, datasources, connection pools, etc.1345.3.1 Stateful connections1345.3.2 Stateless connections1355.3.3 Total connections and SQL server jobs1365.4 Performance topics for Java virtual machine (JVM) settings1365.4.1 Initial Java heap size1375.4.2 Maximum Java heap size1375.4.3 Verbose garbage collection1385.4.4 Static compilation139Chapter 6. Tips and techniques1496.1 The iSeries integrated file system1506.1.1 Using File Transfer Protocol (FTP) with the iSeries IFS1516.1.2 Mapping a PC drive to the iSeries IFS1526.1.3 Editing an iSeries stream file using a PC editor1546.1.4 Stream files and CCSID1546.1.5 The cd command1556.1.6 Managing stream files with the OS/400 WRKLNK command1556.1.7 Other stream file commands1566.1.8 Stream file authority1576.1.9 Editing an iSeries stream file using the OS/400 EDTF command1586.2 The Qshell1586.2.1 Managing stream files with Qshell commands1606.2.2 The touch and setccsid commands1616.2.3 Viewing an iSeries stream file using the Qshell tail command1616.2.4 Qshell scripts1626.3 Checking the QEJBSBS subsystem1646.3.1 Instance monitor jobs1656.3.2 Instance administration jobs1656.3.3 Specifying ports1676.3.4 Application server jobs1676.4 WebSphere versions on the iSeries, your console system, and clients1686.4.1 Checking the WebSphere PTF level on the iSeries1686.4.2 Checking the WebSphere PTF level on a PC1696.5 Common problems with commerce.connect on iSeries1706.5.1 Problems connecting the console to WebSphere on the iSeries1706.5.2 Checking the iSeries name as required by WebSphere1716.5.3 Checking the iSeries database name172Related publications173IBM Redbooks173Other resources173Referenced Web sites173How to get IBM Redbooks173IBM Redbooks collections173Index175Back cover184Größe: 7,44 MBSeiten: 184Language: EnglishHandbuch öffnen
