Configuring CallConnect.jnlp | IBM SG24-6526-00 specs

Figure 3-22 Additional Meta (MIME) information for file extensions section

11.At the top of the page, select Administration.

12.Click the Manage HTTP Servers link in the left-hand panel.

13.On the Manage HTTP Servers page (Figure 3-18 on page 47), stop the HTTP Server and then start it.

Attention: For increased security, configure the aliases in a similar way to those suggested for the original server.

Configuring CallConnect.jnlp

In Windows Explorer, modify the /ordermanagement/client/callconnect.jnlp file as follows to reflect the alias that you previously set:

codebase="http://<iSeries>/callconnect/"

Change the server name. Also change the following line to point to the correct iSeries and port number:

<property name="java.naming.provider.url" value="iiop://<iSeries>:900"/>

The default port number for the default instance of WebSphere is 900.

Configuring JWS.bat

After you set up the HTTP Server, configure JWS.bat as explained here:

1.In Windows Explorer, enter your iSeries name in the following line in the /ordermanagement/client/JWS.bat file:

"C:\Program Files\Java Web Start\javaws" http://<iSeries>/callconnect/CallConnect.jnlp

Chapter 3. Installing and setting up call.connect 51

Image 63

IBM SG24-6526-00 manual Configuring CallConnect.jnlp, Configuring JWS.bat

Contents

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