IBM SG24-6526-00 manual

12.End the SQL server prestart jobs by entering the following command:

Figure 5-10 Display Routing Entry Detail display

12.End the SQL server prestart jobs by entering the following command:

ENDPJ SBS(QSYSWRK) PGM(QSQSRVR)

13.Add the storage pool to the QSYSWRK subsystem.

14.Verify whether the QSYSWRK subsystem was already modified by entering the following command:

DSPSBSD SBSD(QSYSWRK)

15.On the next display, select option 2 to see the pool.

16.On the Display Pool Definitions display (Figure 5-11),if there is a single entry with a pool ID of 1 and a size of *BASE, then the subsystem was not yet modified in this way. If it was modified, then determine why and how it was modified before you continue to the next step.

If you want to continue with this modification, then change the pool ID (2 in this example) to a number higher than the highest number that is currently in use. Note that this number is the pool number relative to this subsystem and the system as a whole as shown by

WRKSYSSTS.

Figure 5-11 Display Pool Definitions display for QSYSWRK

Again, the modification was already made using shared pool 2. Therefore, subsystem pool 2 appears. In this case, the subsystem pool number is the same as for QEJBSBS, but this is not necessary. When started a system pool number, as shown by WRKSYSSTS, will be

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

Image 130

IBM SG24-6526-00 manual End the SQL server prestart jobs by entering the following command

Contents

Follow the step-by-step guide to install commerce.connect Front coverYessong Johng Colin Brown Jim Hirsch John Lawler Geac System21 commerce.connectPage December International Technical Support OrganizationSG24-6526-00 First Edition December Contents Copyright IBM Corp. 2002. All rights reserved 3.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 The team that wrote this redbook PrefaceBecome a published author Comments welcome Chapter 1. The .connect applications 1.1 call.connect 2 Geac System21 commerce.connect Implementation on the iSeries Server Stock 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 Server 2.1.2 The architecture moving forward Chapter 2. Architecture of the commerce.connect products 2.1.3 The development process 2.1.5 The design methodology Using Unified Modelling Language2.1.4 Implementation Supply SalesOrderPricing Delivery contract 2.2 Messaging Java Message Service and IBM WebSphere MQ2.2.1 call.connect shipment Adding a Sales Order Line scenario 2.2.2 vendor.connect Events System21 2.3 Overview of process.connectDatabase 2.4.1 Architectural goals and constraints 2.4 Architectural representation2.4.2 Non-functional architectural considerations 2.4.3 Functional architectural considerations 2.5 Reusing and extending System21 business logic2.5.1 Accessing System21 RPG business logic The deployment influence Java Native Interface JNI Stored proceduresThe choice Chapter 3. Installing and setting up call.connect Copyright IBM Corp. 2002. All rights reserved 3.1.2 Prerequisites 3.1.1 SkillsiSeries hardware requirements iSeries software requirements iSeries Developer Kit for Java 5769-JV1, Version 1.2 option Workstation hardware requirements 3.2 Standard installation procedures3.1.3 System21 authorization code for Order Management OM Workstation software requirements System21 base 3.2.1 Installing Order Management and call.connectChecklist of the basic steps System21 Order Management OM Java components and configuration files 3.2.2 WebSphere installation and configurationStarting the administration server Importing the configuration file Starting the application 3.2.3 Journaling Journaling the files without an ASP Journaling a single file Journaling the files with an ASPJournaling multiple files within a library 3.2.4 Stored procedures and SQL Command = STRJRNPF FILE&L/&N JRNOSLF3/OSL OMTJRNE*OPNCLO To run SQL scripts, follow these steps 5. Open the /OrderManagement/Stored Procedures folder 3.2.5 Java Message ServiceOther SQL Setting up MQSeries Creating a queue manager Granting authority Creating a queueQueue Name SALESORDER.QUEUE Object Type *Q User Names *PUBLIC see the following note Creating the JNDI/MQ objects Additional files neededStandard properties 3.2.6 User profiles Testing the messagingAdditional WebSphere configuration Job description userpassword Setting up call.connect users in the XML user directorySetting up System21 user profiles Password for call.connect Setting up an operator Ensuring that the HTTP administrative server is ready 3.2.7 System21 data set up3.2.8 Java Web Start 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 page Creating a configuration Figure 3-15 Request routing page jnlp extension htm extension Creating an instance Configuring an HTTP Server for iSeries powered by Apache Figure 3-18 Manage HTTP Servers page Type 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.bat 3. Click Install Java Web Start 3.2.9 Backup3.3.1 Daily backups 3.3 call.connect housekeeping 3.3.3 Starting call.connect 3.4 TroubleshootingStarting WebSphere default instance 3.3.4 Restoring IFS objects 3.4.1 WebSphere node name 3.4.2 Errors on starting the client3.4.3 Errors when running the client 3.4.4 Cached data and .bl and .cd files 3.4.5 Log files and debugging Setting up logging on the clientManually configured client Server OrderManagement/test/cfg/ejbdefault 3.5 Manual configuration3.5.1 Non-standard Order Management and call.connect installation PreGenerate Buying Lists Starting the WebSphere console on a PC 3.5.2 WebSphere manual configurationStarting QEJBSBS on the iSeries OrderManagement/test/cfg/log.cfg Creating DataSources Creating JDBC drivers3. Wait for the message, “Create completed successfully” Setting the node parameters Creating the application server Creating enterprise beans Creating an EJB container1. Right-click the container and select Create- Enterprise Bean 3.5.3 Manual client installation Ejbdefault.cfg Running the manually configured client 3.6 Alternative configurations3.6.1 Setting up a test instance of WebSphere Log.cfg Journaling 3.6.2 Setting up an iSeries server for a test systemSystem21 data Table 3-4 Steps required to configure a WebSphere instance system21.password Password for this user 3.6.3 Server configurationServer ejbdefault.cfg Test user 3.6.4 WebSphere administration adminNodeName , -import , and -substitute 3.6.5 Manual client installation Starting application server Testing Java Web Start HTTP Server for iSeries original Index HTTP Server for iSeries powered by ApacheURL Template Replacement File Path Action a. Select Static Web Pages and Files Changing to another instance Figure 3-25 Manage HTTP Servers page Stopping the server The files to modify are ejbdefault.cfg log.cfg standard.properties See 3.6.5, “Manual client installation” on pagePage Chapter 4. Installing and setting up vendor.connect Basic steps checklist 4.1 Preparing for the installation4.2 Installing vendor.connect 4.1.1 Skills required 4.2.1 System21 base 4.2.2 Java components and configuration filesvendor.connect components 4.2.4 Installing and configuring WebSphere 4.2.3 Restoring libraries Creating a new instance Starting the administration serverImporting the configuration file Starting the instancePage Ensuring that the HTTP Server is ready 4.2.5 IBM HTTP Server for iSeriesStarting the application Figure 4-3 AS/400 Tasks page Configuring IBM HTTP Server for iSeries original Figure 4-4 IBM HTTP Server for AS/400 page Figure 4-5 IBM HTTP Server Configuration and Administration page Figure 4-6 Create configuration page Setting up on the iSeries Journaling You must journal the following files at a minimum Figure 4-8 Working with the user-defined options Command STRJRNPF FILE&L/&N JRNOSLF3/OSL OMTJRNE*OPNCLOFigure 4-9 Create User-Defined Option display User profiles System21 data setupDatabase triggers 4.2.6 MQSeries Creating a queue manager Publisher 4.2.7 Work Management Trigger Handler for the iSeries4.2.8 Active Architecture framework Verifying whether folders have write authority Updating the events rules Controller 4.2.9 JConnects server 4.2.10 Setting up new vendor.connect user IDs and supplier IDsConnectorManager.xml AIF .ini files XML security Using LDAP Configuring the LDAP server c. Click the Password button. Enter and confirm your password a. Select the Start server when TCP is started boxb. Set Administrator name as CN=root Figure 4-12 Directory Properties General page Using IBM SecureWay Figure 4-13 Directory Properties Database/Suffixes page a. Enter the server name needjava in this example On the Rebind to server panel these tasks a. Select the Authenticated option b. Enter CN=root for User DNc. Enter the password you entered on the Add directory server display d. Click OK c. 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 user 1. 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.3 Changing the iSeries on which the application is running 4.2.12 Testing the vendor.connect Web site4.2.13 Backing up the configuration components 4.4 Housekeeping 4.4.4 Restoring the vendor.connect IFS objects 4.4.3 StartingStarting the trigger handler and AIF controller Chapter 5. Performance tuning This chapter covers performance tuning of Geac System21 products 5.1 Hardware 5.2.1 SQL server job configuration 5.2 Operating System/400 OS/400 1. 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 QSQSRVR Only 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 names 2. 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 connections 5.3.2 Stateless connections 5.4 Performance topics for Java virtual machine JVM settings 5.3.3 Total connections and SQL server jobs 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 DSPJVAPGM CLSF/OrderManagement/Deployed/roseaodeployed.jar Figure 5-20 The DSPJVAPGM command used with a compiled JAR fileCRTJVAPGM CLSF/OrderManagement/Deployed/roseaodeployed.jar OPTIMIZE40 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 Constrained performance Application settingsPerformance requirements Transaction time out Transaction inactivity time out Ping interval and timeoutFigure 5-24 Advanced page of the Application Server panel Datasource settings Orphan time out Connection time outIdle time out Figure 5-26 The Advanced page of the DataSource panelPage 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 3. Expand File Systems, and select File Shares Figure 6-1 Creating a file share 6.1.3 Editing an iSeries stream file using a PC editor 6.1.4 Stream files and CCSID TOCCSID819 DTAFMT*TXT 6.1.5 The cd command6.1.6 Managing stream files with the OS/400 WRKLNK command cd /OrderManagement/log 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 Figure 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 command tail -f /OrderManagement/log.stdout.txt 6.2.4 Qshell scriptsDIRECTORY=/OrderManagement export DIRECTORY=/OrderManagement cd $DIRECTORY/logmyscript.sh redirect.out 6.3 Checking the QEJBSBS subsystem 6.3.2 Instance administration jobs 6.3.1 Instance monitor jobs Message . . . . WebSphere administration server QEJBADMIN ready Figure 6-6 Job log of the QEJBADMIN jobnetstat *cnn 6.3.4 Application server jobs 6.3.3 Specifying portsFigure 6-7 The NETSTAT command showing ports 900 and 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 Geac call.connect Installation Guide How to get IBM RedbooksOS/400 Work Management, SC41-5306 Backup and Recovery, SC41-5304 Geac System21 Installation and Setup GuidePage Index SymbolsNumerics Page Page stateless connection Windows Explorer Page 0.2”spine 0.17”-0.473” 90-249 pages Page Page Follow the step-by-step guide to install commerce.connect Back coverLearn helpful usage and performance tips and techniques Geac System21 commerce.connect