Follow the step-by-step guide to install commerce.connect
Front cover
Yessong Johng Colin Brown Jim Hirsch John Lawler
Geac System21 commerce.connect
Page
SG24-6526-00
International Technical Support Organization
December
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
Index
Page
Notices
Trademarks
Become a published author
Preface
The 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 Server
Stock allocation Rule-based stock allocation and sourcing engine
1.2 vendor.connect
Web-based interfaces to System21 to support
Page
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.4 Implementation
2.1.5 The design methodology Using Unified Modelling Language
2.1.3 The development process
Supply
SalesOrder
Pricing
Delivery
contract
2.2 Messaging Java Message Service and IBM WebSphere MQ
2.2.1 call.connect
shipment
Adding a Sales Order Line scenario
2.2.2 vendor.connect
Events
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
2.4.3 Functional architectural considerations
2.5 Reusing and extending System21 business logic
2.5.1 Accessing System21 RPG business logic
The deployment influence
The choice
Stored procedures
Java Native Interface JNI
Chapter 3. Installing and setting up call.connect
Copyright IBM Corp. 2002. All rights reserved
iSeries hardware requirements
3.1.1 Skills
3.1.2 Prerequisites
iSeries software requirements
iSeries Developer Kit for Java 5769-JV1, Version 1.2 option
Workstation hardware requirements
3.2 Standard installation procedures
3.1.3 System21 authorization code for Order Management OM
Workstation software requirements
System21 base
3.2.1 Installing Order Management and call.connect
Checklist of the basic steps
System21 Order Management OM
Starting the administration server
3.2.2 WebSphere installation and configuration
Java components and configuration files
Importing the configuration file
Starting the application
3.2.3 Journaling
Journaling the files without an ASP
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
Setting up MQSeries
Creating a queue manager
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
3.2.6 User profiles
Testing the messaging
Additional WebSphere configuration
Job description
userpassword
Setting up call.connect users in the XML user directory
Setting up System21 user profiles
Password for call.connect
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
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 Backup
3.3.1 Daily backups
3.3 call.connect housekeeping
3.3.3 Starting call.connect
3.4 Troubleshooting
Starting WebSphere default instance
3.3.4 Restoring IFS objects
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
Setting up logging on the client
Manually configured client
Server
OrderManagement/test/cfg/ejbdefault
3.5 Manual configuration
3.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 configuration
Starting QEJBSBS on the iSeries
OrderManagement/test/cfg/log.cfg
3. Wait for the message, “Create completed successfully”
Creating JDBC drivers
Creating DataSources
Setting the node parameters
Creating the application server
1. Right-click the container and select Create- Enterprise Bean
Creating an EJB container
Creating enterprise beans
3.5.3 Manual client installation
Ejbdefault.cfg
Running the manually configured client
3.6 Alternative configurations
3.6.1 Setting up a test instance of WebSphere
Log.cfg
Journaling
3.6.2 Setting up an iSeries server for a test system
System21 data
Table 3-4 Steps required to configure a WebSphere instance
system21.password Password for this user
3.6.3 Server configuration
Server ejbdefault.cfg
Test user
Starting the administration server
3.6.4 WebSphere administration
adminNodeName , -import , and -substitute
Importing the configuration file
3.6.5 Manual client installation
Starting application server
Ejbdefault.cfg
Testing Java Web Start
HTTP Server for iSeries original
Running the manually configured client
Index
HTTP Server for iSeries powered by Apache
URL Template Replacement File Path
Action
a. Select Static Web Pages and Files
Configuring JWS.bat
Changing to another instance
Configuring CallConnect.jnlp
Figure 3-25 Manage HTTP Servers page Stopping the server
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
Chapter 4. Installing and setting up vendor.connect
Copyright IBM Corp. 2002. All rights reserved
Basic steps checklist
4.1 Preparing for the installation
4.2 Installing vendor.connect
4.1.1 Skills required
vendor.connect components
4.2.2 Java components and configuration files
4.2.1 System21 base
4.2.4 Installing and configuring WebSphere
4.2.3 Restoring libraries
Creating a new instance
Starting the administration server
Importing the configuration file
Starting the instance
Page
Starting the application
4.2.5 IBM HTTP Server for iSeries
Ensuring that the HTTP Server is ready
Configuring the HTTP Server on the iSeries
Figure 4-3 AS/400 Tasks page
Configuring IBM HTTP Server for iSeries original
Figure 4-4 IBM HTTP Server for AS/400 page
Creating a configuration
Figure 4-5 IBM HTTP Server Configuration and Administration page
Creating an instance
Figure 4-6 Create configuration page
Chapter 4. Installing and setting up vendor.connect
Setting up on the iSeries
Journaling
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
4.2.6 MQSeries
Creating a queue manager
Publisher
4.2.7 Work Management Trigger Handler for the iSeries
4.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 IDs
ConnectorManager.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 box
b. Set Administrator name as CN=root
Chapter 4. Installing and setting up vendor.connect
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 DN
c. 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 site
4.2.13 Backing up the configuration components
4.4 Housekeeping
Starting the trigger handler and AIF controller
4.4.3 Starting
4.4.4 Restoring the vendor.connect IFS objects
Starting WebSphere default instance
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.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
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
Constrained performance
Application settings
Performance requirements
Transaction time out
Figure 5-24 Advanced page of the Application Server panel
Ping interval and timeout
Transaction inactivity time out
Datasource settings
Orphan time out
Connection time out
Idle time out
Figure 5-26 The Advanced page of the DataSource panel
Page
Chapter 6. Tips and techniques
Copyright IBM Corp. 2002. All rights reserved
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 command
6.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
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.2 Instance administration jobs
6.3.1 Instance monitor 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 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 Redbooks
OS/400 Work Management, SC41-5306 Backup and Recovery, SC41-5304
Geac System21 Installation and Setup Guide
Page
Numerics
Symbols
Index
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 cover
Learn helpful usage and performance tips and techniques
Geac System21 commerce.connect
