JConnects server, ConnectorManager.xml | IBM SG24-6526-00 guide

4.2.9 JConnects server

This links vendor.connect back in to System21. Copy the Jacada directory to the root of your iSeries server. Make sure the files are writable by running the WRKLNK command as explained earlier.

ConnectorManager.xml

Edit the /VendorConnect/deployed/ConnectorManager.xml file. Change the following entries as appropriate to your iSeries setup:

<company>Z1</company> <environment>XXX</environment>

.

.

.

<host>your iSeries</host>

.

.

.

<user>userid</user> <password>password</password>

The user here must have access to the 2/AG option within System21 for the company also specified here. This option must be defined with a date format of D in Application Manager.

AIF .ini files

1.Open the /Jacada/SYS21AIF/classes/appls/SYS21AIF/server/resources/sys21aif.ini file.

2.At the start of the file, ensure that the RtRootDir is correct:

RtRootDir=/JACADA/SYS21AIF/

3.At the end of the file, change the Host statement to have the correct iSeries name:

After [GUISys TN5250]

.

Host=<youriSeries>

4.Open the /Jacada/SYS21AIF/classes/jacadasv.ini file.

5.Ensure that the RtRootDir value is the same as above.

4.2.10Setting up new vendor.connect user IDs and supplier IDs

There are two modes in which secure.connect can be run. The first holds the user details as an XML file called /vendorconnect/deployed/UserDirectory.xml. The second holds the user details in IBM’s version of Lightweight Directory Access Protocol (LDAP) called SecureWay. Obviously, the latter method is the more secure, but it requires an additional process to run, either on the workstation or on the iSeries.

SecurityManager.xml

You can configure the system to use either method by changing the /vendorconnect/deployed/SecurityManager.xml file.

vendor.connect uses the authentication context named “DEFAULT” in the SecurityManager.xml file. This default context, as shipped, is configured to use an LDAP directory. However, you should verify the following settings:

<authentication_context id="DEFAULT"> <directory id="SecureWay" type="LDAP">

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

Image 104

IBM SG24-6526-00 manual JConnects server, Setting up new vendor.connect user IDs and supplier IDs, ConnectorManager.xml

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 Implementation Design methodology Using Unified Modelling LanguageDevelopment process 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 Non-functional architectural considerations Architectural representationArchitectural goals and constraints Functional architectural considerations Reusing and extending System21 business logicAccessing System21 RPG business logic Choice Stored proceduresJava Native Interface JNI Installing and setting up call.connect ISeries hardware requirements SkillsPrerequisites Installation option During installation After installation ISeries software requirements Standard installation procedures System21 authorization code for Order Management OMWorkstation hardware requirements Workstation software requirements Installing Order Management and call.connect Checklist of the basic stepsSystem21 base System21 Order Management OM Starting the administration server WebSphere installation and configurationJava components and configuration files Importing the configuration file Starting the application Journaling Journaling the files without an ASP Journaling multiple files within a library Journaling the files with an ASPJournaling a single file Stored procedures and SQL Creating a user-defined option Client Access setup for the naming convention Other SQL Java Message ServiceOpen the /OrderManagement/Stored Procedures folder Setting up MQSeries Creating a queue manager Creating a queue Granting authority Object Name SALESORDER.QUEUE Standard properties Additional files neededCreating the JNDI/MQ objects Testing the messaging Additional WebSphere configurationUser profiles 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 Java Web Start System21 data set upEnsuring that the Http administrative server is ready 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 Backup Daily backupsCall.connect housekeeping Stopping WebSphere Troubleshooting Starting WebSphere default instanceStarting call.connect Restoring IFS objects Errors on starting the client Errors when running the clientWebSphere node name Cached data and .bl and .cd files Setting up logging on the client Manually configured clientLog files and debugging Server Manual configuration Non-standard Order Management and call.connect installationPreGenerate Buying Lists System21 and Order Management Starting the WebSphere console on a PC WebSphere manual configurationStarting Qejbsbs on the iSeries 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 Alternative configurations Setting up a test instance of WebSphereRunning the manually configured client Log.cfg Journaling Setting up an iSeries server for a test systemSystem21 data 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 Preparing for the installation Installing vendor.connectBasic steps checklist Skills required Vendor.connect components Java components and configuration filesSystem21 base Installing and configuring WebSphere Restoring libraries Starting the administration server Importing the configuration fileCreating a new instance Starting the instance 2shows an example of an imported configuration Starting the application IBM Http Server for iSeriesEnsuring that the Http Server is ready 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 Database triggers System21 data setupUser profiles MQSeries Creating a queue manager Publisher Work Management Trigger Handler for the iSeriesActive Architecture framework Updating the events rules Tests Controller Test Setting up new vendor.connect user IDs and supplier IDs ConnectorManager.xmlJConnects server 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 the trigger handler and AIF controller StartingRestoring the vendor.connect IFS objects 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 Application settings Performance requirementsConstrained performance Transaction time out Ping interval and timeout Transaction inactivity time out Datasource settings 26shows the Advanced page of the DataSource panel Orphan time out Connection time outIdle 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 How to get IBM Redbooks IBM RedbooksReferenced Web sites 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