Configuring an Http Server for iSeries original | IBM SG24-6526-00

Configuring an HTTP Server for iSeries (original)

To configure an IBM HTTP Server (original) at V4R5 or earlier, follow these steps. First, you should see the IBM HTTP Server Configuration and Administration page (Figure 3-13). Click the Configurations option on the left.

Figure 3-13 IBM HTTP Server Configuration and Administration page

Next you need to create a new configuration and a new instance, based on the IBM-supplied configurations and instances. This is explained in the following sections.

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

Image 54

IBM SG24-6526-00 manual Configuring an Http Server for iSeries original, IBM Http Server Configuration and Administration

Contents

Geac System21 commerce.connect Page International Technical Support Organization First Edition December Contents Page Index Page Copyright License Trademarks Team that wrote this redbook Become a published author Comments welcome .connect applications Call.connect Call.connect buying list Vendor.connect Web-based interfaces to System21 to support .connect applications Page Architecture of the commerce.connect products Need for an architecture Architecture moving forward Design methodology Using Unified Modelling Language Development processImplementation SalesOrder Pricing Messaging Java Message Service and IBM WebSphere MQ Call.connect Adding a Sales Order Line scenario 3shows how call.connect uses messaging Flow of Information to vendor.connect after System21 Update Vendor.connect Overview of process.connect Relationship between the .connect applications Architectural representation Architectural goals and constraintsNon-functional architectural considerations Reusing and extending System21 business logic Accessing System21 RPG business logicFunctional architectural considerations Stored procedures Java Native Interface JNIChoice Installing and setting up call.connect Skills PrerequisitesISeries hardware requirements Installation option During installation After installation ISeries software requirements Workstation hardware requirements Standard installation proceduresSystem21 authorization code for Order Management OM Workstation software requirements System21 base Installing Order Management and call.connectChecklist of the basic steps System21 Order Management OM WebSphere installation and configuration Java components and configuration filesStarting the administration server Importing the configuration file Starting the application Journaling Journaling the files without an ASP Journaling the files with an ASP Journaling a single fileJournaling multiple files within a library Stored procedures and SQL Creating a user-defined option Client Access setup for the naming convention Java Message Service Open the /OrderManagement/Stored Procedures folderOther SQL Setting up MQSeries Creating a queue manager Creating a queue Granting authority Object Name SALESORDER.QUEUE Additional files needed Creating the JNDI/MQ objectsStandard properties User profiles Testing the messagingAdditional WebSphere configuration Job description Setting up call.connect users in the XML user directory Setting up System21 user profiles Setting up an operator 10 Operator setup display System21 data set up Ensuring that the Http administrative server is readyJava Web Start Configuring the Http Server on the iSeries 11 Http Server configuration 12 Http Server configuration Configuring an Http Server for iSeries original 13 IBM Http Server Configuration and Administration Creating a configuration 14 Create configuration 15 Request routing Jnlp extension Htm extension Creating an instance 17 Create server instance Configuring an Http Server for iSeries powered by Apache 18 Manage Http Servers Type of server Http Server powered by Apache recommended 19 Http Server configuration 2 Apache 20 Http Server name Homera global settings Select Static Web Pages and Files Click Add Click Apply Configuring CallConnect.jnlp Configuring JWS.bat Call.connect housekeeping BackupDaily backups Stopping WebSphere Starting call.connect TroubleshootingStarting WebSphere default instance Restoring IFS objects WebSphere node name Errors on starting the clientErrors when running the client Cached data and .bl and .cd files Log files and debugging Setting up logging on the clientManually configured client Server PreGenerate Buying Lists Manual configurationNon-standard Order Management and call.connect installation System21 and Order Management WebSphere manual configuration Starting Qejbsbs on the iSeriesStarting the WebSphere console on a PC Creating Jdbc drivers Creating DataSources Setting the node parameters Creating the application server Creating an EJB container Creating enterprise beans Manual client installation Ejbdefault.cfg Running the manually configured client Alternative configurationsSetting up a test instance of WebSphere Log.cfg Setting up an iSeries server for a test system System21 dataJournaling Server configuration WebSphere administration Starting application server Testing Java Web Start Http Server for iSeries original Http Server for iSeries powered by Apache Index Action URL Template Replacement File Path Select Static Web Pages and Files Changing to another instance 25 Manage Http Servers page Stopping the server Installing and setting up call.connect Page Installing and setting up vendor.connect Basic steps checklist Preparing for the installationInstalling vendor.connect Skills required Java components and configuration files System21 baseVendor.connect components Installing and configuring WebSphere Restoring libraries Creating a new instance Starting the administration serverImporting the configuration file Starting the instance 2shows an example of an imported configuration IBM Http Server for iSeries Ensuring that the Http Server is readyStarting the application AS/400 Tasks Configuring IBM Http Server for iSeries original IBM Http Server for AS/400 IBM Http Server Configuration and Administration Create configuration Setting up on the iSeries Journaling Select option 9 Work with user-defined options Command Strjrnpf FILE&L/&N JRNOSLF3/OSL OMTJRNE*OPNCLO System21 data setup User profilesDatabase triggers MQSeries Creating a queue manager Work Management Trigger Handler for the iSeries Active Architecture frameworkPublisher Updating the events rules Tests Controller Test JConnects server Setting up new vendor.connect user IDs and supplier IDsConnectorManager.xml AIF .ini files Entry dn=cn=vcadmin, ou=cad, ou=ges,o=geac,c=uk objectclass XML security Using Ldap Configuring the Ldap server Select the Start server when TCP is started box 12 Directory Properties General Using IBM SecureWay 13 Directory Properties Database/Suffixes 14 Add directory server panel 15 Rebind to server panel Select the Organizational unit option 16 Adding an entry Creating the vcadmin user in IBM SecureWay 17 Creating the vcadmin user Creating the authorization rule 101 19 Logging on as vcadmin 21 Selecting Jdbc Setup in Client Access 103Page Changing the iSeries on which the application is running Housekeeping Starting Restoring the vendor.connect IFS objectsStarting the trigger handler and AIF controller Performance tuning 107 Hardware Work with Processor Resources display SQL server job configuration Operating System/400 OS/400 2shows the Display Subsystem Description menu. Select option Display Prestart Job Entries list Change the server settings with this command Wrkactjob command showing the Qsqsrvr jobs Toolbox Jdbc driver V4R5 uses slightly different commands as listed here Wrksyssts command showing the memory pool names Subsystems and memory pools End the Qejbsbs subsystem by using the following command For a more simplified method, you can enter Wrksyssts You may want to verify this step Use the following command Start the WebSphere subsystem Automatic performance adjustment 16shows the Display System Value display for Qpfradj Manual performance adjustment Stateful connections Stateless connections Performance topics for Java virtual machine JVM settings Total connections and SQL server jobs Initial Java heap size Maximum Java heap size Verbose garbage collection Static compilation 20 The Dspjvapgm command used with a compiled JAR file Performance tuning 22shows a command prompt and two Notepad sessions Enterprise bean settings Constrained performance Application settingsPerformance requirements Transaction time out Ping interval and timeout Transaction inactivity time out Datasource settings 26shows the Advanced page of the DataSource panel Connection time out Idle time outOrphan time out Page Tips and techniques 137 ISeries integrated file system Using File Transfer Protocol FTP with the iSeries IFS Mapping a PC drive to the iSeries IFS Expand File Systems, and select File Shares Creating a file share Editing an iSeries stream file using a PC editor Stream files and Ccsid Cd command Managing stream files with the OS/400 Wrklnk command Other stream file commands Wrklnk command showing the root directory Stream file authority 3shows the Save Object display Editing an iSeries stream file using the OS/400 Edtf command Qshell QSH Command Entry display Managing stream files with Qshell commands Touch and setccsid commands Viewing an iSeries stream file using the Qshell tail command Qshell scripts Cd $DIRECTORY/log Checking the Qejbsbs subsystem Instance administration jobs Instance monitor jobs Job log of the Qejbadmin job Specifying ports Application server jobs Checking the WebSphere PTF level on the iSeries Wrkdtaara command showing the SF99147 data area Checking the WebSphere PTF level on a PC Common problems with commerce.connect on iSeries Problems connecting the console to WebSphere on the iSeries Checking the iSeries name as required by WebSphere 11 The Wrkrdbdire command file Checking the iSeries database name Referenced Web sites How to get IBM RedbooksIBM Redbooks Other resourcesPage Index 163 111 Java Web Start in test JConnects server 123 140 Word processors Page 2spine 17-0.473 90-249 pages Page Page Geac System21 commerce.connect