Manuals / IBM / Computer Equipment / Laptop

IBM SG24-6526-00 manual 15 Request routing page

Models: SG24-6526-00

1 184

Download 184 pages 3.35 Kb

Page 56

Figure 3-15 Request routing page

4.The Request routing page (Figure 3-15)appears. Insert the following actions, templates, and replacement file paths. This allows the system to find actual files when the user logs on to call.connect. Be sure to click the Insert after radio button:

Action	URL template	Replacement file path
Pass	/callconnect/	/ordermanagement/client/index.html
Pass	/callconnect/*.gif	/ordermanagement/client/*.gif
Pass	/callconnect/callconnect.jnlp	/ordermanagement/client/callconnect.jnlp
Pass	/callconnect/*.jar	/ordermanagement/client/*.jar
Pass	/callconnect/setup.exe	/ordermanagement/client/setup.exe
Pass	/callconnect/help/	/ordermanagement/client/help/introduction.htm
Pass	/callconnect/help/*.gif	/ordermanagement/client/help/*.gif

Click Apply.

Figure 3-15 Request routing page

5. Select the Languages and Encoding link on the left. Then select MIME types.

44Geac System21 commerce.connect: Implementation on the iSeries Server

Image 56

IBM SG24-6526-00 manual 15 Request routing page

Contents

Front cover Yessong Johng Colin Brown Jim Hirsch John LawlerFollow the step-by-step guide to install commerce.connect Geac System21 commerce.connectPage SG24-6526-00 International Technical Support OrganizationDecember First Edition December Contents Copyright IBM Corp. 2002. All rights reserved3.3.4 Restoring IFS objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.4.1 WebSphere node name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.4.2 Errors on starting the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.4.3 Errors when running the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.4.4 Cached data and .bl and .cd files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.4.5 Log files and debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3.5 Manual configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 3.5.1 Non-standard Order Management and call.connect installation . . . . . . . . . . . . . . 56 3.5.2 WebSphere manual configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 3.5.3 Manual client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.6 Alternative configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 3.6.1 Setting up a test instance of WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 3.6.2 Setting up an iSeries server for a test system. . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 3.6.3 Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 3.6.4 WebSphere administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 3.6.5 Manual client installation Contents IndexPage Notices Trademarks Become a published author PrefaceThe team that wrote this redbook Comments welcome Chapter 1. The .connect applications 1.1 call.connect 2 Geac System21 commerce.connect Implementation on the iSeries ServerStock allocation Rule-based stock allocation and sourcing engine 1.2 vendor.connect Web-based interfaces to System21 to supportPage 6 Geac System21 commerce.connect Implementation on the iSeries Server Chapter 2. Architecture of the commerce.connect products 2.1 The need for an architecture 8 Geac System21 commerce.connect Implementation on the iSeries Server2.1.2 The architecture moving forward Chapter 2. Architecture of the commerce.connect products2.1.4 Implementation 2.1.5 The design methodology Using Unified Modelling Language2.1.3 The development process SalesOrder PricingSupply Delivery2.2 Messaging Java Message Service and IBM WebSphere MQ 2.2.1 call.connectcontract shipmentAdding a Sales Order Line scenario 2.2.2 vendor.connect EventsDatabase 2.3 Overview of process.connectSystem21 2.4.2 Non-functional architectural considerations 2.4 Architectural representation2.4.1 Architectural goals and constraints 2.5 Reusing and extending System21 business logic 2.5.1 Accessing System21 RPG business logic2.4.3 Functional architectural considerations The deployment influenceThe choice Stored proceduresJava Native Interface JNI Chapter 3. Installing and setting up call.connect Copyright IBM Corp. 2002. All rights reservediSeries hardware requirements 3.1.1 Skills3.1.2 Prerequisites iSeries software requirements iSeries Developer Kit for Java 5769-JV1, Version 1.2 option3.2 Standard installation procedures 3.1.3 System21 authorization code for Order Management OMWorkstation hardware requirements Workstation software requirements3.2.1 Installing Order Management and call.connect Checklist of the basic stepsSystem21 base System21 Order Management OMStarting the administration server 3.2.2 WebSphere installation and configurationJava components and configuration files Importing the configuration file Starting the application 3.2.3 Journaling Journaling the files without an ASPJournaling multiple files within a library Journaling the files with an ASPJournaling a single file Stored procedures 3.2.4 Stored procedures and SQLCommand = STRJRNPF FILE&L/&N JRNOSLF3/OSL OMTJRNE*OPNCLO To run SQL scripts, follow these steps Other SQL 3.2.5 Java Message Service5. Open the /OrderManagement/Stored Procedures folder Setting up MQSeries Creating a queue managerQueue Name SALESORDER.QUEUE Creating a queueGranting authority Object Type *Q User Names *PUBLIC see the following note Standard properties Additional files neededCreating the JNDI/MQ objects Testing the messaging Additional WebSphere configuration3.2.6 User profiles Job descriptionSetting up call.connect users in the XML user directory Setting up System21 user profilesuserpassword Password for call.connectSetting up an operator 3.2.8 Java Web Start 3.2.7 System21 data set upEnsuring that the HTTP administrative server is ready Configuring the HTTP Server on the iSeries Figure 3-12 HTTP Server configuration Configuring an HTTP Server for iSeries original Figure 3-13 IBM HTTP Server Configuration and Administration pageCreating a configuration Figure 3-15 Request routing page jnlp extension htm extensionCreating an instance Configuring an HTTP Server for iSeries powered by Apache Figure 3-18 Manage HTTP Servers pageType of server HTTP Server powered by Apache - recommended a. Select Static Web Pages and Files a. Click Add b. Enter the following information File Extension .jnlp Configuring CallConnect.jnlp Configuring JWS.bat3.2.9 Backup 3.3.1 Daily backups3. Click Install Java Web Start 3.3 call.connect housekeeping3.4 Troubleshooting Starting WebSphere default instance3.3.3 Starting call.connect 3.3.4 Restoring IFS objects3.4.2 Errors on starting the client 3.4.3 Errors when running the client3.4.1 WebSphere node name 3.4.4 Cached data and .bl and .cd filesSetting up logging on the client Manually configured client3.4.5 Log files and debugging Server3.5 Manual configuration 3.5.1 Non-standard Order Management and call.connect installationOrderManagement/test/cfg/ejbdefault PreGenerate Buying Lists3.5.2 WebSphere manual configuration Starting QEJBSBS on the iSeriesStarting the WebSphere console on a PC OrderManagement/test/cfg/log.cfg3. Wait for the message, “Create completed successfully” Creating JDBC driversCreating DataSources Setting the node parameters Creating the application server1. Right-click the container and select Create- Enterprise Bean Creating an EJB containerCreating enterprise beans 3.5.3 Manual client installation Ejbdefault.cfg3.6 Alternative configurations 3.6.1 Setting up a test instance of WebSphereRunning the manually configured client Log.cfg3.6.2 Setting up an iSeries server for a test system System21 dataJournaling Table 3-4 Steps required to configure a WebSphere instance3.6.3 Server configuration Server ejbdefault.cfgsystem21.password Password for this user Test user3.6.4 WebSphere administration adminNodeName , -import , and -substituteStarting the administration server Importing the configuration file3.6.5 Manual client installation Starting application serverTesting Java Web Start HTTP Server for iSeries originalEjbdefault.cfg Running the manually configured clientHTTP Server for iSeries powered by Apache URL Template Replacement File PathIndex Actiona. Select Static Web Pages and Files Changing to another instance Configuring CallConnect.jnlpConfiguring JWS.bat Figure 3-25 Manage HTTP Servers page Stopping the serverChapter 3. Installing and setting up call.connect The files to modify are ejbdefault.cfg log.cfg standard.propertiesSee 3.6.5, “Manual client installation” on page Page Chapter 4. Installing and setting up vendor.connect Copyright IBM Corp. 2002. All rights reserved4.1 Preparing for the installation 4.2 Installing vendor.connectBasic steps checklist 4.1.1 Skills requiredvendor.connect components 4.2.2 Java components and configuration files4.2.1 System21 base 4.2.4 Installing and configuring WebSphere 4.2.3 Restoring librariesStarting the administration server Importing the configuration fileCreating a new instance Starting the instancePage Starting the application 4.2.5 IBM HTTP Server for iSeriesEnsuring that the HTTP Server is ready Configuring the HTTP Server on the iSeries Figure 4-3 AS/400 Tasks pageConfiguring IBM HTTP Server for iSeries original Figure 4-4 IBM HTTP Server for AS/400 pageCreating a configuration Figure 4-5 IBM HTTP Server Configuration and Administration pageCreating an instance Figure 4-6 Create configuration pageChapter 4. Installing and setting up vendor.connect Setting up on the iSeries JournalingYou must journal the following files at a minimum Figure 4-9 Create User-Defined Option display Command STRJRNPF FILE&L/&N JRNOSLF3/OSL OMTJRNE*OPNCLOFigure 4-8 Working with the user-defined options Database triggers System21 data setupUser profiles 4.2.6 MQSeries Creating a queue manager4.2.7 Work Management Trigger Handler for the iSeries 4.2.8 Active Architecture frameworkPublisher Verifying whether folders have write authorityUpdating the events rules Controller 4.2.10 Setting up new vendor.connect user IDs and supplier IDs ConnectorManager.xml4.2.9 JConnects server AIF .ini filesXML security Using LDAP Configuring the LDAP servera. Select the Start server when TCP is started box b. Set Administrator name as CN=rootc. Click the Password button. Enter and confirm your password Chapter 4. Installing and setting up vendor.connectUsing IBM SecureWay Figure 4-13 Directory Properties Database/Suffixes pagea. Enter the server name needjava in this example a. Select the Authenticated option b. Enter CN=root for User DN c. Enter the password you entered on the Add directory server displayOn the Rebind to server panel these tasks d. Click OKc. Select the Organizational unit option Creating the vcadmin user in IBM SecureWay Creating the authorization rule Figure 4-19 Logging on as vcadmin Figure 4-20 Setting up a new user1. Set the library list by connecting to the iSeries 4. Run the set of SQL commands that are detailed in the following SQL example. They cause triggers to be fired so that the System21 data will be synchronized into the VendorConnect database. You can find the SQL in the SQL to sync dbs on initial load.txt file in the SQL folder 4.2.12 Testing the vendor.connect Web site 4.2.13 Backing up the configuration components4.3 Changing the iSeries on which the application is running 4.4 Housekeeping4.4.3 Starting 4.4.4 Restoring the vendor.connect IFS objectsStarting the trigger handler and AIF controller Starting WebSphere default instanceCopyright IBM Corp. 2002. All rights reserved Chapter 5. Performance tuningThis chapter covers performance tuning of Geac System21 products 5.1 Hardware 5.2.1 SQL server job configuration 5.2 Operating System/400 OS/4001. Sign on as QSECOFR 2. Enter the following command Figure 5-3 Display Prestart Job Entries list Figure 5-4 Display Prestart Job Entry Detail for QSQSRVROnly one instance of WebSphere is running 5.2.2 Toolbox JDBC driver Note The commands are the same, but the parameters may be different 5.2.3 Subsystems and memory pools Figure 5-7 WRKSYSSTS command showing the memory pool names2. End the QEJBSBS subsystem by using the following command For a more simplified method, you can enter 12.End the SQL server prestart jobs by entering the following command 17.Change the SQL server prestart job to use the new pool 22.Check the QSQSRVR jobs by using the following command 5.2.4 Automatic performance adjustment 5.2.5 Manual performance adjustment 5.3.1 Stateful connections5.3.2 Stateless connections 5.4 Performance topics for Java virtual machine JVM settings 5.3.3 Total connections and SQL server jobs5.4.1 Initial Java heap size 5.4.2 Maximum Java heap size5.4.3 Verbose garbage collection 5.4.4 Static compilation CRTJVAPGM CLSF/OrderManagement/Deployed/roseaodeployed.jar OPTIMIZE40 Figure 5-20 The DSPJVAPGM command used with a compiled JAR fileDSPJVAPGM CLSF/OrderManagement/Deployed/roseaodeployed.jar place of the OS/400 system class loader. This custom class loader does not detect the static programs 2. Add a colon to the end of each line, except the last Enterprise bean settings Application settings Performance requirementsConstrained performance Transaction time outFigure 5-24 Advanced page of the Application Server panel Ping interval and timeoutTransaction inactivity time out Datasource settings Connection time out Idle time outOrphan time out Figure 5-26 The Advanced page of the DataSource panelPage Chapter 6. Tips and techniques Copyright IBM Corp. 2002. All rights reserved6.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 3. Expand File Systems, and select File SharesFigure 6-1 Creating a file share 6.1.3 Editing an iSeries stream file using a PC editor 6.1.4 Stream files and CCSID6.1.5 The cd command 6.1.6 Managing stream files with the OS/400 WRKLNK commandTOCCSID819 DTAFMT*TXT cd /OrderManagement/log6.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 QshellFigure 6-4 The QSH Command Entry display 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 commandDIRECTORY=/OrderManagement 6.2.4 Qshell scriptstail -f /OrderManagement/log.stdout.txt myscript.sh redirect.out cd $DIRECTORY/logexport DIRECTORY=/OrderManagement 6.3 Checking the QEJBSBS subsystem 6.3.2 Instance administration jobs 6.3.1 Instance monitor jobsnetstat *cnn Figure 6-6 Job log of the QEJBADMIN jobMessage . . . . WebSphere administration server QEJBADMIN ready Figure 6-7 The NETSTAT command showing ports 900 and 6.3.3 Specifying ports6.3.4 Application server jobs 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 iSeries6.5.2 Checking the iSeries name as required by WebSphere 6.5.3 Checking the iSeries database name How to get IBM Redbooks OS/400 Work Management, SC41-5306 Backup and Recovery, SC41-5304Geac call.connect Installation Guide Geac System21 Installation and Setup GuidePage Numerics SymbolsIndex Page Page stateless connection Windows Explorer Page 0.2”spine 0.17”-0.473” 90-249 pages Page Page Back cover Learn helpful usage and performance tips and techniquesFollow the step-by-step guide to install commerce.connect Geac System21 commerce.connect