Geac System21 commerce.connect
Front cover
Yessong Johng Colin Brown Jim Hirsch John Lawler
Follow the step-by-step guide to install commerce.connect
Page
SG24-6526-00
International Technical Support Organization
December
First Edition December
Copyright IBM Corp. 2002. All rights reserved
Contents
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
Index
Contents
Page
Notices
Trademarks
Become a published author
Preface
The team that wrote this redbook
Comments welcome
Chapter 1. The .connect applications
2 Geac System21 commerce.connect Implementation on the iSeries Server
1.1 call.connect
Stock allocation Rule-based stock allocation and sourcing engine
Web-based interfaces to System21 to support
1.2 vendor.connect
Page
6 Geac System21 commerce.connect Implementation on the iSeries Server
Chapter 2. Architecture of the commerce.connect products
8 Geac System21 commerce.connect Implementation on the iSeries Server
2.1 The need for an architecture
Chapter 2. Architecture of the commerce.connect products
2.1.2 The architecture moving forward
2.1.4 Implementation
2.1.5 The design methodology Using Unified Modelling Language
2.1.3 The development process
Delivery
SalesOrder
Pricing
Supply
shipment
2.2 Messaging Java Message Service and IBM WebSphere MQ
2.2.1 call.connect
contract
Adding a Sales Order Line scenario
Events
2.2.2 vendor.connect
Database
2.3 Overview of process.connect
System21
2.4.2 Non-functional architectural considerations
2.4 Architectural representation
2.4.1 Architectural goals and constraints
The deployment influence
2.5 Reusing and extending System21 business logic
2.5.1 Accessing System21 RPG business logic
2.4.3 Functional architectural considerations
The choice
Stored procedures
Java Native Interface JNI
Copyright IBM Corp. 2002. All rights reserved
Chapter 3. Installing and setting up call.connect
iSeries hardware requirements
3.1.1 Skills
3.1.2 Prerequisites
iSeries Developer Kit for Java 5769-JV1, Version 1.2 option
iSeries software requirements
Workstation software requirements
3.2 Standard installation procedures
3.1.3 System21 authorization code for Order Management OM
Workstation hardware requirements
System21 Order Management OM
3.2.1 Installing Order Management and call.connect
Checklist of the basic steps
System21 base
Starting the administration server
3.2.2 WebSphere installation and configuration
Java components and configuration files
Importing the configuration file
Starting the application
Journaling the files without an ASP
3.2.3 Journaling
Journaling multiple files within a library
Journaling the files with an ASP
Journaling a single file
Stored procedures
3.2.4 Stored procedures and SQL
Command = STRJRNPF FILE&L/&N JRNOSLF3/OSL OMTJRNE*OPNCLO
To run SQL scripts, follow these steps
Other SQL
3.2.5 Java Message Service
5. Open the /OrderManagement/Stored Procedures folder
Creating a queue manager
Setting up MQSeries
Queue Name SALESORDER.QUEUE
Creating a queue
Granting authority
Object Type *Q User Names *PUBLIC see the following note
Standard properties
Additional files needed
Creating the JNDI/MQ objects
Job description
Testing the messaging
Additional WebSphere configuration
3.2.6 User profiles
Password for call.connect
Setting up call.connect users in the XML user directory
Setting up System21 user profiles
userpassword
Setting up an operator
3.2.8 Java Web Start
3.2.7 System21 data set up
Ensuring that the HTTP administrative server is ready
Configuring the HTTP Server on the iSeries
Figure 3-12 HTTP Server configuration
Figure 3-13 IBM HTTP Server Configuration and Administration page
Configuring an HTTP Server for iSeries original
Creating a configuration
Figure 3-15 Request routing page
htm extension
jnlp extension
Creating an instance
Figure 3-18 Manage HTTP Servers page
Configuring an HTTP Server for iSeries powered by Apache
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 JWS.bat
Configuring CallConnect.jnlp
3.3 call.connect housekeeping
3.2.9 Backup
3.3.1 Daily backups
3. Click Install Java Web Start
3.3.4 Restoring IFS objects
3.4 Troubleshooting
Starting WebSphere default instance
3.3.3 Starting call.connect
3.4.4 Cached data and .bl and .cd files
3.4.2 Errors on starting the client
3.4.3 Errors when running the client
3.4.1 WebSphere node name
Server
Setting up logging on the client
Manually configured client
3.4.5 Log files and debugging
PreGenerate Buying Lists
3.5 Manual configuration
3.5.1 Non-standard Order Management and call.connect installation
OrderManagement/test/cfg/ejbdefault
OrderManagement/test/cfg/log.cfg
3.5.2 WebSphere manual configuration
Starting QEJBSBS on the iSeries
Starting the WebSphere console on a PC
3. Wait for the message, “Create completed successfully”
Creating JDBC drivers
Creating DataSources
Creating the application server
Setting the node parameters
1. Right-click the container and select Create- Enterprise Bean
Creating an EJB container
Creating enterprise beans
Ejbdefault.cfg
3.5.3 Manual client installation
Log.cfg
3.6 Alternative configurations
3.6.1 Setting up a test instance of WebSphere
Running the manually configured client
Table 3-4 Steps required to configure a WebSphere instance
3.6.2 Setting up an iSeries server for a test system
System21 data
Journaling
Test user
3.6.3 Server configuration
Server ejbdefault.cfg
system21.password Password for this user
Importing the configuration file
3.6.4 WebSphere administration
adminNodeName , -import , and -substitute
Starting the administration server
Starting application server
3.6.5 Manual client installation
Running the manually configured client
Testing Java Web Start
HTTP Server for iSeries original
Ejbdefault.cfg
Action
HTTP Server for iSeries powered by Apache
URL Template Replacement File Path
Index
a. Select Static Web Pages and Files
Figure 3-25 Manage HTTP Servers page Stopping the server
Changing to another instance
Configuring CallConnect.jnlp
Configuring JWS.bat
Chapter 3. Installing and setting up call.connect
The files to modify are ejbdefault.cfg log.cfg standard.properties
See 3.6.5, “Manual client installation” on page
Page
Copyright IBM Corp. 2002. All rights reserved
Chapter 4. Installing and setting up vendor.connect
4.1.1 Skills required
4.1 Preparing for the installation
4.2 Installing vendor.connect
Basic steps checklist
vendor.connect components
4.2.2 Java components and configuration files
4.2.1 System21 base
4.2.3 Restoring libraries
4.2.4 Installing and configuring WebSphere
Starting the instance
Starting the administration server
Importing the configuration file
Creating a new instance
Page
Starting the application
4.2.5 IBM HTTP Server for iSeries
Ensuring that the HTTP Server is ready
Figure 4-3 AS/400 Tasks page
Configuring the HTTP Server on the iSeries
Figure 4-4 IBM HTTP Server for AS/400 page
Configuring IBM HTTP Server for iSeries original
Figure 4-5 IBM HTTP Server Configuration and Administration page
Creating a configuration
Creating an instance
Figure 4-6 Create configuration page
Chapter 4. Installing and setting up vendor.connect
Journaling
Setting up on the iSeries
You must journal the following files at a minimum
Figure 4-9 Create User-Defined Option display
Command STRJRNPF FILE&L/&N JRNOSLF3/OSL OMTJRNE*OPNCLO
Figure 4-8 Working with the user-defined options
Database triggers
System21 data setup
User profiles
Creating a queue manager
4.2.6 MQSeries
Verifying whether folders have write authority
4.2.7 Work Management Trigger Handler for the iSeries
4.2.8 Active Architecture framework
Publisher
Updating the events rules
Controller
AIF .ini files
4.2.10 Setting up new vendor.connect user IDs and supplier IDs
ConnectorManager.xml
4.2.9 JConnects server
XML security
Configuring the LDAP server
Using LDAP
Chapter 4. Installing and setting up vendor.connect
a. Select the Start server when TCP is started box
b. Set Administrator name as CN=root
c. Click the Password button. Enter and confirm your password
Figure 4-13 Directory Properties Database/Suffixes page
Using IBM SecureWay
a. Enter the server name needjava in this example
d. Click OK
a. Select the Authenticated option b. Enter CN=root for User DN
c. Enter the password you entered on the Add directory server display
On the Rebind to server panel these tasks
c. Select the Organizational unit option
Creating the vcadmin user in IBM SecureWay
Creating the authorization rule
Figure 4-20 Setting up a new user
Figure 4-19 Logging on as vcadmin
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.4 Housekeeping
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
Starting WebSphere default instance
4.4.3 Starting
4.4.4 Restoring the vendor.connect IFS objects
Starting the trigger handler and AIF controller
Copyright IBM Corp. 2002. All rights reserved
Chapter 5. Performance tuning
This chapter covers performance tuning of Geac System21 products
5.1 Hardware
5.2 Operating System/400 OS/400
5.2.1 SQL server job configuration
1. Sign on as QSECOFR 2. Enter the following command
Figure 5-4 Display Prestart Job Entry Detail for QSQSRVR
Figure 5-3 Display Prestart Job Entries list
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
Figure 5-7 WRKSYSSTS command showing the memory pool names
5.2.3 Subsystems and memory pools
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.3.1 Stateful connections
5.2.5 Manual performance adjustment
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.2 Maximum Java heap size
5.4.1 Initial Java heap size
5.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 file
DSPJVAPGM 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
Transaction time out
Application settings
Performance requirements
Constrained performance
Figure 5-24 Advanced page of the Application Server panel
Ping interval and timeout
Transaction inactivity time out
Datasource settings
Figure 5-26 The Advanced page of the DataSource panel
Connection time out
Idle time out
Orphan time out
Page
Copyright IBM Corp. 2002. All rights reserved
Chapter 6. Tips and techniques
6.1 The iSeries integrated file system
6.1.1 Using File Transfer Protocol FTP with the iSeries IFS
3. Expand File Systems, and select File Shares
6.1.2 Mapping a PC drive to the iSeries IFS
Figure 6-1 Creating a file share
6.1.4 Stream files and CCSID
6.1.3 Editing an iSeries stream file using a PC editor
cd /OrderManagement/log
6.1.5 The cd command
6.1.6 Managing stream files with the OS/400 WRKLNK command
TOCCSID819 DTAFMT*TXT
6.1.7 Other stream file commands
6.1.8 Stream file authority
6.2 The Qshell
6.1.9 Editing an iSeries stream file using the OS/400 EDTF command
Figure 6-4 The QSH Command Entry display
6.2.1 Managing stream files with Qshell commands
6.2.3 Viewing an iSeries stream file using the Qshell tail command
6.2.2 The touch and setccsid commands
DIRECTORY=/OrderManagement
6.2.4 Qshell scripts
tail -f /OrderManagement/log.stdout.txt
myscript.sh redirect.out
cd $DIRECTORY/log
export DIRECTORY=/OrderManagement
6.3 Checking the QEJBSBS subsystem
6.3.1 Instance monitor jobs
6.3.2 Instance administration jobs
netstat *cnn
Figure 6-6 Job log of the QEJBADMIN job
Message . . . . WebSphere administration server QEJBADMIN ready
Figure 6-7 The NETSTAT command showing ports 900 and
6.3.3 Specifying ports
6.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.1 Problems connecting the console to WebSphere on the iSeries
6.5 Common problems with commerce.connect on iSeries
6.5.2 Checking the iSeries name as required by WebSphere
6.5.3 Checking the iSeries database name
Geac System21 Installation and Setup Guide
How to get IBM Redbooks
OS/400 Work Management, SC41-5306 Backup and Recovery, SC41-5304
Geac call.connect Installation Guide
Page
Numerics
Symbols
Index
Page
Page
stateless connection
Windows Explorer
Page
0.2”spine 0.17”-0.473” 90-249 pages
Page
Page
Geac System21 commerce.connect
Back cover
Learn helpful usage and performance tips and techniques
Follow the step-by-step guide to install commerce.connect
