=============================================================================== IBM WebSphere Business Integrator Version 2.1 Product Release Notes Last Updated: 25 May 2001 (C) Copyright IBM Corporation 2001. All rights reserved. =============================================================================== These release notes contain information required for installation, configuration, and deployment, as well as information that was not available for inclusion in the product documentation. You can find any additional files documented here in the accompanying "Release Notes.zip" file. =============================================================================== I. CONTENTS =============================================================================== I. CONTENTS II. TRADEMARKS 1. DOCUMENTATION 2. BEFORE STARTING YOUR INSTALLATION 3. INSTALLING THE FACILITIES IN THE MACHINES IN YOUR TOPOLOGY 4. BEFORE RUNNING CONFIGURE.BAT 5. WHILE RUNNING CONFIGURE.BAT 6. AFTER RUNNING CONFIGURE.BAT 7. RUNTIME 8. TRACING AND LOGGING 9. DEPLOYMENT 10. UNDEPLOYMENT 11. PARTNER AGREEMENT MANAGER =============================================================================== II. TRADEMARKS =============================================================================== The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: DB2 IBM MQSeries WebSphere Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. =============================================================================== 1. DOCUMENTATION =============================================================================== IT IS IMPORTANT THAT THIS DOCUMENT AND THE INSTALLATION GUIDE ARE READ IN FULL BEFORE COMMENCING THE INSTALLATION AND CONFIGURATION OF THE PRODUCT. YOU SHOULD ALSO CHECK THE PRODUCT WEB SITE FOR UPDATES TO THIS INFORMATION: http://www.ibm.com/software/webservers/btobintegrator/ support.html#Technical notes FAILURE TO DO SO MAY RESULT IN PROBLEMS THAT REQUIRE EITHER A FULL OR PARTIAL RE-INSTALLATION AND/OR RE-CONFIGURATION OF THE PRODUCT. =============================================================================== 2. BEFORE STARTING YOUR INSTALLATION =============================================================================== The following steps should be performed before the installation of WebSphere Business Integrator. 2.1 STOP THE WINDOWS INSTALLER SERVICE BEFORE INSTALLATION TOPOLOGIES: All. MACHINES: All. SYMPTOM: Installation of the JMS support pac may fail with RC=61 and the following message in biz_wrapper.log: "Silent install file handle can't be found" RESOLUTION: Using the Services applet on the Microsoft Windows NT Control Panel, ensure that the Windows Installer service is stopped before installation. =============================================================================== 3. INSTALLING THE FACILITIES IN THE MACHINES IN YOUR TOPOLOGY =============================================================================== The following steps should be performed during the installation of WebSphere Business Integrator. 3.1 CLASSPATH MAY REQUIRE MANUAL EDITING FOLLOWING REPEATED ATTEMPTS TO INSTALL THE GATEWAY ADAPTER TOPOLOGIES: All using the Partner Agreement Manager. MACHINES: Machine containing the Partner Agreement Manager facility. SYMPTOM: If multiple installations of the Gateway Adapter are made on a machine then the following error dialog may be displayed: "Error 401 - String variable is not large enough for string. Check the string declarations." RESOLUTION: This is caused by the installer appending entries to the system classpath that are not removed. Manually delete the following entries using the System applet on the Microsoft Windows NT Control Panel: 1. The "\java" directory below the WebSphere Business Integrator installation directory (for example C:\PROGRA~1\IBM\WSBI\lib\java). 2. The "\lib" directory below the WebSphere Business Integrator Business Managers installation directory (for example C:\PROGRA~1\IBM\WSBI\lib). 3. The "\bin" directory below the MQSeries Adapter Kernel installation directory (for example C:\MQAK\bin). 4. The classpath entries for the following two JAR files: ibmjndi.jar (for example C:\LDAP\java\ibmjndi.jar) jndi.jar (for example C:\LDAP\java\jndi.jar) Note: these paths are all appended to the classpath in their short form. 3.2 MANUAL RE-BOOT REQUIRED AFTER INSTALLATION TOPOLOGIES: All. MACHINES: All. SYMPTOM: When biz_install completes it displays a message indicating that it will reboot the machine, but the re-boot does not occur. RESOLUTION: Perform a manual re-boot of the machine (by pressing Ctrl-Alt-Delete and selecting "Shutdown"). =============================================================================== 4. BEFORE RUNNING CONFIGURE.BAT =============================================================================== The following steps should be performed before the configuration of WebSphere Business Integrator, i.e. before running configure.bat. 4.1 NEW BATCH FILE REQUIRED TO CONFIGURE THE ENTRY TEST TOPOLOGY BASE MACHINE FOR THE PARTNER AGREEMENT MANAGER FACILITY TOPOLOGIES: Entry Test Topology. MACHINES: Base machine. SYMPTOM: Error messages occur during Partner Agreement Manager facility pre-configuration: 1. "******Connecting to DB2 Database" "Could not find C:\temp\~tmp.log" 2. "SQL103N The database alias name or database name "WSBIPAM" could not be found. SQLSTATE=42705" 3. "Could not find C:\temp\wsbipam\ddl.sql" 4. "Could not find C:\temp\wsbipam\al_tbl.sql" 5. "Could not find C:\temp\wsbipam\is_tbl.sql" 6. "SQL1005N The database alias "WSBIPAM" already exists in either the local database or system database directory." 7. "SQL0805N Package "NULLID.SQLC2D01" was not found. SQLSTATE=51002" 8. "There was a problem declaring the DDL portion of the schema. Please view the logs and attempt to correct the problem with either the schema configuration or the db2 server configuration" RESOLUTION: Replace the file PAM.bat in the directory: \config with the version supplied in "Release Notes.zip", prior to running configure.bat. 4.2 MANUAL JDBC CONFIGURATION REQUIRED TOPOLOGIES: All. MACHINES: All. SYMPTOM: When the WSBIDeploy application server is importing to WebSphere Application Server, Java JDBC Driver exceptions might be reported. RESOLUTION: Before running configure.bat, stop the DB2 JDBC Applet Server in the control panel and run the batch file: :\sqllib\java12\usejdbc2.bat 4.3 ADDITIONAL CONFIGURATION REQUIRED IF THE WRAPPER INSTALLATION OF JMS FAILS AND IT IS INSTALLED MANUALLY TOPOLOGIES: All. MACHINES: All. SYMPTOM: The wrapper installation of JMS fails and it is installed manually. RESOLUTION: In order to ensure that the topology repository is updated correctly during configuration, after a manual installation of JMS, the following commands must be run from a command window on the affected machines: biztmapiput softwareproductinstallstate _p_mqjms 2 biztmapiput facilityinstallstate _r_sm 2 4.4 MQSERIES WORKFLOW MAY REQUIRE ADDITIONAL CONFIGURATION TOPOLOGIES: All Enterprise. MACHINES: Machine containing the Business Flow Manager Workflow facility. SYMPTOM: The default port for the Workflow database instance is 50020. If this port is already in use on the Trust and Access Manager machine then the user is asked to select another. This new port number is not automatically configured on the Workflow machine preventing it from accessing the database. RESOLUTION: If a new port number was requested on the Trust and Access Manager machine, then before running configuration on the Workflow machine edit the file: \config\wflow.bat Change the port number in the line: set BIZ_WFDBPORT=50020 =============================================================================== 5. WHILE RUNNING CONFIGURE.BAT =============================================================================== The following steps should be performed during the configuration of WebSphere Business Integrator. 5.1 CONFIGURE.BAT MUST BE RE-RUN DUE TO POLICY DIRECTOR PROBLEM TOPOLOGIES: All Enterprise. MACHINES: Machine containing the Trust and Access Manager Plus facility. SYMPTOM: Configuration reports that Policy Director Manager is not running. RESOLUTION: Re-run configure.bat. 5.2 CONFIGURE.BAT MUST BE RE-RUN BECAUSE A WEBSPHERE APPLICATION SERVER SERVICE CANNOT BE STARTED TOPOLOGIES: All. MACHINES: Machines with the WebSphere Application Server installed. SYMPTOM: Configuration stops because the WebSphere Application Server Administration Server service cannot be started. RESOLUTION: Edit the httpd.conf file. Go to the last line but one and remove "f.bak" from the start of the alias entry. Start the service manually and then re-run configure.bat. 5.3 A WEB PROXY JUNCTION NEEDS TO BE DEFINED SPECIFICALLY FOR THE USER REGISTRATION SAMPLE TOPOLOGIES: All Enterprise. MACHINES: WebProxy machine. SYMPTOM: User Registration is not accessible from the Web without configuring the WebProxy machine. RESOLUTION: The WebProxy installation documentation does not indicate how to define a junction specifically for the User Registration sample. The steps required are: 1. From the following directory on the Business Flow Manager WebSphere Application Server machine: \AppServer\hosts\default_host\web\webseal copy the files: RegistrationForm.html index.html into the following directory on the WebProxy Machine: \www\docs 2. The file index.html must be edited to correspond to the WebProxy machine and the correct junction. The URL should be: https://// 5.4 CONFIGURE.BAT MAY REQUIRE MANUAL TERMINATION TOPOLOGIES: All. MACHINES: All containing MQSeries Workflow. SYMPTOM: Configure.bat does not terminate after the "Config Ended" message. RESOLUTION: Press Ctrl-C to terminate the batch file and return to a command prompt after the "Config Ended" message has been displayed. 5.5 MQSERIES CONFIGURATION ERROR MESSAGE CAN BE SAFELY IGNORED TOPOLOGIES: All. MACHINES: Machines containing the Trust and Access Manager or Trust and Access Manager Plus facilities. SYMPTOM: The MQSeries configuration of the Trust and Access Manager or Trust and Access Manager Plus machine reports an invalid queue name and port number when trying to specify the cluster sender: 6 : DEFINE CHANNEL(TO."NOTAM") CHLTYPE(CLUSSDR) + : CONNAME('IDMESR6()') CLUSTER(SVT_D) + : DESCR('BPIP cluster sender') REPLACE AMQ8405: Syntax error detected at or near end of command segment below:- DEFINE CHANNEL(TO... RESOLUTION: This error message can safely be ignored. =============================================================================== 6. AFTER RUNNING CONFIGURE.BAT =============================================================================== The following steps should be performed after the configuration of WebSphere Business Integrator but before deploying or running solutions. 6.1 JAR FILE MUST BE ADDED TO THE WEBSPHERE APPLICATION SERVER DEPENDENT CLASSPATH TOPOLOGIES: All. MACHINES: Machines containing the Business Flow Manager WebSphere Application Server facility. SYMPTOM: The User Registration sample solution, and other solutions that were built with MQSeries Adapter Builder, do not work correctly because they require the MQAOJFramework class files. RESOLUTION: After configuration of the Business Flow Manager WebSphere Application Server machine use the WebSphere Application Server Administration GUI to change the dependent classpath. Under the WebSphere Administrative Domain, select the node (hostname) and add the following to the dependent classpath: \lib\java\clientjars\MQAOJFramework.jar Be sure to apply the change and restart the node. 6.2 JAR FILES MUST BE ADDED TO THE SYSTEM CLASSPATH ON THE MQSERIES WORKFLOW MACHINE TOPOLOGIES: All Enterprise topologies where MQSeries Workflow is installed on a separate machine from the Business Flow Manager WebSphere Application Server machine. MACHINES: Machine containing the Business Flow Manager Workflow facility. SYMPTOM: MQSeries Workflow cannot be used by WebSphere Application Server. RESOLUTION: The files ejs.jar, ivjejb35.jar, and ujc.jar from WebSphere Application Server are installed on each machine in: \lib\java\clientjars However, they are not included on the classpath. Adjust the system classpath on the MQSeries Workflow machine to include these files. This is done using the System applet from the Microsoft Windows NT Control Panel. 6.3 AMS_GSO_USER AUTHORITY MUST BE MODIFIED ON THE BUSINESS FLOW MANAGER WEBSPHERE APPLICATION SERVER MACHINE TOPOLOGIES: All Enterprise. MACHINES: Machine containing the Business Flow Manager WebSphere Application Server facility. SYMPTOM: AMS_GSO_User does not have proper authority. RESOLUTION: After running configure.bat on the Business Flow Manager WebSphere Application Server machine, enter the following from a command prompt: cd \bin gsouser -a 1 -u cn=root -p -s -n AMS_GSO_User -d uid=AMS_GSO_User,o=ePICUsers,o=epic 6.4 LDAP SETTINGS MUST BE RESET FOLLOWING DISABLE/RE-ENABLE OF WEBSPHERE GLOBAL SECURITY TOPOLOGIES: All. MACHINE: Base. SYMPTOM: The LDAP advanced settings are customized to work with WebSphere Business Integrator. When WebSphere Global Security is disabled and then re-enabled, the LDAP settings are changed to some other values (not even the default values). RESOLUTION: Change the settings to the correct values as specified in the Installation Guide section on WebSphere Application Server security. 6.5 WEBSPHERE APPLICATION SERVER ALIASES MUST BE CONFIGURED FOR INTERACTION MANAGER AND SOLUTION MANAGER MACHINES TOPOLOGIES: All. MACHINES: Machine containing the Interaction Manager facility and the machine containing the Solution Manager facility. SYMPTOM: HTTP Requests to the Interaction Manager and Solution Manager machines are not recognized. The configuration of the default host in WebSphere Application Server does not include aliases for the Interaction Manager and Solution Manager machines. RESOLUTION: Manually add the following entries to the WebSphere Application Server configuration through the WebSphere administrator console. 1. Select the default host and display its properties panel. 2. Through the advanced panel, add the following host aliases: . .:80 .:443 :80 :443 . .:80 .:443 :80 :443 6.6 MANUAL CONFIGURATION OF DATA INTERCHANGE LDAP ENTRIES REQUIRED ON THE TRUST AND ACCESS MANAGER PLUS MACHINE TOPOLOGIES: All enterprise with Data Interchange option. MACHINES: Base. SYMPTOM: The entries in LDAP required by the Data Interchange adapter are incorrect. RESOLUTION: The following LDAP entries must be manually configured on the Trust and Access Manager Plus machine: 1. DN = cn=epicAppExtensions,ePICAppID=DI,o=ePICApplications, o=epic Where the attribute: ePICBinDirectory - should be changed to the location of the Data Interchange Server bin directory. ePICDataDirectory - should be changed to the location of the Data Interchange Server Runtime directory. uid - should be changed to the userid of the DB2 server on the Trust and Access Manager Plus machine. userPassword - should be changed to the password of the DB2 server on the Trust and Access Manager Plus machine. epicPlan - should be changed to "EDIEC31E". 2. DN = cn=ePICAdapterRouting,ePICAppID=EDITP1, o=ePICApplications,o=epic Add the attribute "ePICReceiveMode" with the value "MQPP". 3. DN = cn=ePICAdapterRouting,ePICAppID=DI, o=ePICApplications,o=epic Add the attribute "ePICReceiveMode" with the value "MQPP". 6.7 MANUAL CONFIGURATION OF THE WEBSPHERE GLOBAL SECURITY SETTINGS REQUIRED TOPOLOGIES: All Enterprise. MACHINES: Base. SYMPTOM: WebSphere Global security settings are incorrect for the User Registration sample. RESOLUTION: The following manual configuration steps must be performed: 1. Set the User Filter in the LDAP Advanced Properties to: (|(&(cn=%v)(objectclass=ePerson))(&(uid=%v) (objectclass=ePerson))) 2. Change the Security ServerId and its password from: WebSphere to: WSBIAdmin 6.8 MANUAL CONFIGURATION REQUIRED FOR THE WSBIDEPLOY ENVIRONMENT CLASSPATH TOPOLOGIES: All Enterprise. MACHINES: Base. SYMPTOM: An error occurs indicating that Policy Director class files could not be found. RESOLUTION: Using the WebSphere Administration console, edit the AMS Application Service and modify the classpath. Change the $Pddir$ entries to the path where Policy Director is installed. You must use the short name for the directories. For example, if Policy Director is installed into: d:\WebSphere Business Integrator\Tivoli\PolicyDirector you would replace all occurrences of $Pddir$ to: d:\WebSph~1\Tivoli\Policy~1 6.9 MANUAL CONFIGURATION OF POLICY DIRECTOR FILE REQUIRED TOPOLOGIES: All Enterprise. MACHINES: Base. SYMPTOM: The file PDPerm.properties is created in the wrong directory. RESOLUTION: Look for the file PDPerm.properties in the directory: websphere\jdk\jre If it is not present, search for the file and copy it to this directory. 6.10 THE AQMSETUPFILE ENVIRONMENT VARIABLE MUST BE UPDATED ON THE EDI GATEWAY MACHINE TOPOLOGIES: All Enterprise using the EDI Gateway facility. MACHINES: EDI Gateway. RESOLUTION: Using the System applet from the Microsoft Windows NT Control Panel, change the AQMSETUPFILE system environment variable to point to the aqmsetup file. For example: AQMSETUPFILE=\properties\aqmsetup 6.11 LOG FILE NAMES SHOULD BE CHANGED FOR WEBSPHERE WORKFLOW SERVICES AND WEBSPHERE WORKFLOW TOPOLOGIES: All Enterprise. MACHINES: Machine containing the Business Flow Manager WebSphere Application Server facility. SYMPTOM: These two application servers share the same log file, making the log entries difficult to read. RESOLUTION: Using the Websphere Administration console, select the WWFServices application server and modify the standard out and standard error file names to values different from the Websphere Workflow application server's standard out and standard error file names. 6.12 MQSERIES PUBLISH/SUBSCRIBE QUEUES REQUIRE CONFIGURATION TOPOLOGIES: All. MACHINES: Machines containing the Business Flow Manager WebSphere Application Server and Solution Manager facilities. SYMPTOM: The message queues required by MQSeries publish/subscribe are not configured automatically during the configuration process. RESOLUTION: After running configure.bat perform the following steps from the same window that configure.bat was run: cd /d \java\bin runmqsc %QMgrName% < MQJMS_PSQ.mqsc 6.13 THE DEPLOYMENT WIZARD HANGS WHEN DEPLOYING A SOLUTION PACKAGE TOPOLOGIES: All. MACHINES: All. SYMPTOM: The Deployment Wizard hangs when a solution package is being deployed. RESOLUTION: Replace the file TopologyData.class in the directory: \lib\java\com\ibm\btobi\topology\tmapi with the TopologyData.class supplied in "Release Notes.zip", and then re-boot the machine. =============================================================================== 7. RUNTIME =============================================================================== The entries in this section apply to the WebSphere Business Integrator components at runtime. 7.1 AMENDMENTS MAY BE REQUIRED TO THE SOLUTION CONSOLE SERVER'S STARTUP INSTRUCTIONS TOPOLOGIES: All. MACHINES: Enterprise topologies: machine containing the Interaction Manager facility. Entry topologies: machine containing the Business Flow Manager WebSphere Application Server facility. SYMPTOM: The Solution Console server's startup instructions in early versions of the Runtime book are incomplete. RESOLUTION: The startup instructions for Solution Manager Servers must include setSMenv.bat. For each of the following servers, the user must first run the batch file setSMenv.bat to set environment variables and then run: RegisterAuditLogServer.bat RegisterExceptionServer.bat StartAuditLogServer.bat StartExceptionServer.bat StopAuditLogServer.bat StopExceptionService.bat 7.2 MQSERIES WORKFLOW MEMORY LEAK SHOULD BE MONITORED TOPOLOGIES: All Enterprise. MACHINES: Machine containing the Business Flow Manager Workflow facility. SYMPTOM: When running the MQSeries Workflow Java Agent for a long time, memory usage will grow and eventually cause program failures. RESOLUTION: Watch for excessive memory usage on the Business Flow Manager machine where the MQSeries Workflow Java Agent is running. If it approaches the memory limit, stop solutions on the platform and reboot the machine. 7.3 INCORRECT STATUS REPORTED BY THE PLATFORM CONSOLE TOPOLOGIES: All. MACHINES: Machine containing the Platform Console. SYMPTOM: The Platform Console allows users to view the current status of managed products in the topology. On certain facilities, the Platform Console incorrectly reports that DB2 Enterprise Edition has been installed instead of DB2 Administration Client, and shows the status of these instances as being unknown (indicated by a yellow exclamation mark icon). RESOLUTION: Although the Platform Console will incorrectly allow you to invoke DB2 management operations on these instances, they will not do anything. 7.4 THE PLATFORM CONSOLE MAY INCORRECTLY REPORT THAT MANAGEMENT OPERATIONS COULD NOT BE COMPLETED TOPOLOGIES: All. MACHINES: Machine containing the Platform Console. SYMPTOM: The Platform Console reports that management operations have failed despite their successful completion (as indicated by the Services applet of the Microsoft Windows NT Control Panel). RESOLUTION: There is currently no resolution to this problem. 7.5 INTERACTION MANAGER REQUIRES INTERNET EXPLORER 5.0 TOPOLOGIES: All Enterprise. MACHINES: All used to access the Interaction Manager navigation framework. SYMPTOM: The navigation framework on Interaction Manager does not work with Netscape Navigator 4.7. RESOLUTION: Use Internet Explorer 5.0. 7.6 ALIAS REQUIRED IN HTTPD.CONF TOPOLOGIES: All Entry. MACHINES: Business Flow Manager SYMPTOM: The exception, logging, and event services may not find required XML files. RESOLUTION: Edit the httpd.conf file in the HTTP Server's installation directory and add the following aliases: Alias /epic/xml "/xml/" Alias /wsbi/ "/" Aliases are added in the section identified in the file. =============================================================================== 8. TRACING AND LOGGING =============================================================================== The entries in this section apply to the tracing and logging facilities used by the following WebSphere Business Integrator components: 1. The Topology Repository 2. Deployment 3. Management tools 8.1 DEFAULT TRACE SETTINGS The default entries in the LDAP configuration of trace for the components listed above give the following: ADMINISTRATION LOG MESSAGES 1. Logging on 2. All log messages enabled 3. Logging is synchronous 4. Messages are logged to the file: \logs\AdminMessages.log SERVICE LOG MESSAGES 1. Logging off 2. All log messages enabled 3. Logging is not synchronous 4. Messages are logged to the file: \logs\ServiceMessages.log 8.2 TURNING TRACE ON AND OFF To turn on service tracing for these components apply the TraceOn.ldif file using the command: ldapadd -r -c -h -p -D -w password -f TraceOn.ldif To turn off service tracing apply the TraceOff.ldif file using the command: ldapadd -r -c -h -p -D -w password -f TraceOff.ldif Both of these files can be found in "Release Notes.zip". Individual entries can be turned on and off either by using a modified LDIF file or by changing entries in the directory using the Directory Management Tool (DMT) on the LDAP server or client. =============================================================================== 9. DEPLOYMENT =============================================================================== The entries in this section apply to the deployment of WebSphere Business Integrator solutions at run-time. 9.1 ACTION REQUIRED TO AVOID WRITE FAILURES DURING DEPLOYMENT TOPOLOGIES: All. MACHINES: Machine containing the Platform Console. SYMPTOM: "Permission denied" write failures occur when redeploying a solution package or a solution element. RESOLUTION: Write failures during deployment can be caused by the operation of the IBM HTTP Server file cache. To avoid this problem, first stop the IBM HTTP Server Service and then restart it for all but the first attempt to deploy or re-deploy a solution or solution element. 9.2 SOLUTION ELEMENTS MUST BE RE-DEPLOYED IN FULL IF THE ACTIVATION PHASE FAILS TOPOLOGIES: All. MACHINES: All. SYMPTOM: The deployment application cleans up the resources for a solution element on the target machine, even though the deployment has failed during the activation phase. RESOLUTION: To complete the deployment, force the re-deployment of the entire solution element as described in the product documentation. =============================================================================== 10. UNDEPLOYMENT =============================================================================== 10.1 UNDEPLOYMENT INSTRUCTION GENERATION NOT FUNCTIONING TOPOLOGIES: All. MACHINES: Machine containing the Platform Console. SYMPTOM: The "Generate Undeployment Instructions" option from the "File" menu of the Platform Console will cause the Platform Console to hang. RESOLUTION: No workaround is available, however the command window which hangs can be interrupted by pressing Ctrl-C. This option should not be used. =============================================================================== 11. PARTNER AGREEMENT MANAGER =============================================================================== The entries in this section apply to the WebSphere Business Integrator Partner Agreement Manager. 11.1 ERRORS RUNNING IMPGWADP.BAT TOPOLOGIES: All containing the Partner Agreement Manager option. MACHINES: Machine containing the Partner Agreement Manager facility. SYMPTOM: Errors occur during the running of the file impgwadp.bat on the Partner Agreement Manager machine indicating that the following files cannot be found: BPI_Adapter_Applications.ldif BPI_Adapter_Applications_JMS.ldif RESOLUTION: Before running configuration on the Partner Agreement Manager machine, copy these two files plus AIV.bat to the directory: \config Then copy the file AdapterTest.class to the directory: \lib\java\com\ibm\btobi\gateway\pam\ adapters\config All four of these files can be found in "Release Notes.zip". 11.2 BPI ADAPTER DOES NOT WORK WITH JMS TOPOLOGIES: All containing the Partner Agreement Manager option. MACHINES: Machines containing the Partner Agreement Manager facility. SYMPTOM: The BPI adapter does not run if it is configured to use JMS as its means of communication. RESOLUTION: This is caused because two JAR files are missing from the system classpath. Using the System applet from the Microsoft Windows NT Control Panel, ensure that the following two JAR files are included in the system classpath environment variable: \java\lib\jms.jar \java\lib\com.ibm.mqjms.jar Re-boot the system to make these changes take effect. 11.3 DEVELOPMENT-TIME AND RUN-TIME PAM PARTNER IDS MUST MATCH TOPOLOGIES: All containing the Partner Agreement Manager option. MACHINES: Machines containing the Partner Agreement Manager facility. SYMPTOM: Partner Agreement Manager problems if development-time and run-time Partner IDs do not match. RESOLUTION: In a full environment there are often two Partner Agreement Manager servers. One of these would be for development/test and the other for run-time. In this situation the partner name and ID should be the same on both machines. This is because when a Public Process is deployed to a run-time machine, the Private Process definitions are generated for the Public Process steps owned by the local partner. 11.4 MESSAGE REMAINS ON QUEUE WHEN COMPLETION NOTIFICATIONS IS OFF TOPOLOGIES: All containing the Partner Agreement Manager option. MACHINES: Machines containing the Partner Agreement Manager facility. SYMPTOM: Messages can be left on the SYSTEM.PAM.INTERNAL.STATE.QUEUE until the BPI adapter is restarted. RESOLUTION: The BPI adapter is an MQSeries Adapter Offering (MQAO) adapter which runs with the PAM. It provides a means for other MQAO adapters to interact with public processes running on PAM. Two queues are required to support the operation of the adapter. These are set up during installation and configuration. One of the queue names is SYSTEM.PAM.INTERNAL.STATE.QUEUE and is used by the adapter for storing and persisting messages. When the option "ProcessCompletionNotification" is set to false, messages can be left on the queue and will not be removed until the adapter is restarted. There may be performance implications where this option is set to false, many messages are received and the adapter is left running for a considerable time. If a performance degradation is observed with the adapter and the SYSTEM.PAM.INTERNAL.STATE.QUEUE has many old messages we suggest a periodic restart of the adapter or changing the "ProcessCompletionNotification" option to true. 11.5 ADAPTER SERVER MUST BE RESTARTED WHEN USING BPI ADAPTER TYPE 1 IF PROCESS SERVER IS RESTARTED TOPOLOGIES: All containing Partner Agreement Manager option. MACHINES: Machines containing the Partner Agreement Manager facility. SYMPTOM: Completion notification message will no longer be sent from the Partner Agreement Manager via the adapter. RESOLUTION: Restart the Adapter Server. 11.6 PROCESS SERVER SHOULD BE RESTARTED IF DATABASE CONNECTION IS LOST TOPOLOGIES: All containing Partner Agreement Manager option. MACHINES: Machines containing the Partner Agreement Manager facility. SYMPTOM: DB2 error messages occur either as pop up messages or in the logs. RESOLUTION: Restart the Process Server.