=============================================================================== IBM WebSphere Business Integrator Version 2.1 CSD 1 Product Release Notes Last Updated: Jun 20 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 "releasenotesfiles.zip" file. =============================================================================== I. CONTENTS =============================================================================== I. CONTENTS II. TRADEMARKS 1. DOCUMENTATION 2. CORRECTIVE SERVICE CSD01 3. BEFORE STARTING YOUR INSTALLATION 4. INSTALLING THE FACILITIES IN THE MACHINES IN YOUR TOPOLOGY 5. BEFORE RUNNING CONFIGURE.BAT 6. WHILE RUNNING CONFIGURE.BAT 7. AFTER RUNNING CONFIGURE.BAT 8. RUNTIME 9. DEPLOYMENT 10. 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 SupportPac 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 REINSTALLATION AND/OR RECONFIGURATION OF THE PRODUCT. =============================================================================== 2. CORRECTIVE SERVICE CSD01 =============================================================================== These release notes apply to WebSphere Business Integrator V2.1 with Corrective Service CSD01. You can find the Corrective Service at: http://www.ibm.com/software/webservers/btobintegrator/ support.html#Support downloads =============================================================================== 3. BEFORE STARTING YOUR INSTALLATION =============================================================================== The following steps should be performed before the installation of WebSphere Business Integrator. 3.1 STOP THE WINDOWS INSTALLER SERVICE BEFORE INSTALLATION TOPOLOGIES: All. MACHINES: All. SYMPTOM: Installation of the JMS SupportPac 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. =============================================================================== 4. INSTALLING THE FACILITIES IN THE MACHINES IN YOUR TOPOLOGY =============================================================================== The following steps should be performed during the installation of WebSphere Business Integrator. 4.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, 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. 4.2 WRAPPER INSTALL REPORTS THAT WEBSPHERE APPLICATION SERVER FAILED TO INSTALL TOPOLOGIES: All MACHINES: Machines containing WebSphere Application Server SYMPTOM: Bad return code for install of WebSphere Application Server is displayed at the end of the wrapper install. RESOLUTION: Install is checking the logfile produced by the WebSphere Application Server install program to determine the result of the install. Before the install attampts to read this logfile, it waits until it has reached a certain size. Occasionally, the install of WebSphere completes successfully before that minimum size is reached and therefore the log is never checked and the install wrapper assumes that WebSphere Application Server has failed to install. If this is the case, the logfile was.log in the Windows NT directory should be checked manually for a successful completion. If WebSphere Applicaton Server has installed correctly, update the topology repository using the following command at a Windows NT command prompt: bizTmapiPut SoftwareProductInstallState _p_was 2 This command should be run from the WSBI\bin directory. The is the hostname of the machine on which this command is being run. =============================================================================== 5. BEFORE RUNNING CONFIGURE.BAT =============================================================================== The following steps should be performed before the configuration of WebSphere Business Integrator; that is, before running configure.bat. 5.1 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 was installed manually. RESOLUTION: 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 5.2 LDAP CHANGES ON AN EXISTING INSTALLED AND CONFIGURED TOPOLOGY TOPOLOGIES: All. MACHINES: Base. SYMPTOM: If upgrading an existing WebSphere Business Integrator topology that is already installed and configured, configure.bat will prompt the user as follows: "LDAP is already configured, do you want to re-configure it..." Answer "No." Otherwise, all configuration data in LDAP will be lost. However, the LDAP changes included in the CSD will not be applied. RESOLUTION: If you are upgrading an existing WebSphere Business Integrator topology, apply this workaround to maintain your data in LDAP. After installing the CSD, but before running configure: 1. Replace the existing schema file by copying the new V3.epicschema file to \etc. 2. Restart the IBM SecureWay Directory V3.2 service. 3. From the command line, change to the directory where the csd.ldif file is located. This is included in the releasenotesfiles.zip file. 4. Run the command ldif2db -i csd.ldif. This will add new entries to the LDAP database. 5. Start the IBM SecureWay Directory Management Tool. 6. Edit LDAP data entries for the following DN string: ePICMenuItemId=SolutionManager,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic 7. If applicable, delete the space between words in the value for ePICMenuItemTitle. Leave the resulting string unchanged. 8. Change the ePICTarget value to be "Content". Use the exact case and do not include the quotes. 9. Repeat steps 7 and 8 for the following DN strings: ePICMenuItemId=ExceptionConsole,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic ePICMenuItemId=LDAPConfig,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic ePICMenuItemId=LogConsole,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic ePICMenuItemId=TraceConsole,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic ePICMenuItemId=LogManager,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic ePICMenuItemId=PO,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic ePICMenuItemId=User,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic ePICMenuItemId=System,o=MenuItem, cn=BtoBiTemplates,o=ePICSolutions,o=epic 10. Edit LDAP data entries for the following DN string: cn=ePICAppExtensions,ePICAppId=IM, o=ePICApplications,o=epic 11. Change the values in the following fields: ePICIMAuditHook: com.ibm.b2bi.im.DefaultAuditWrapper ePICLogging: false 12. Edit LDAP data entries for the following DN string: ePICAppId=BFM,o=ePICApplications,o=epic 13. Change the values in the following fields: ePICHostname: blank (no entry) ePICLogonInfoClassName: blank (no entry) ePICPropertyFile: bfm 14. Edit LDAP data entries for the following DN string: cn=ePICAppExtensions,ePICAppId=BFM, o=ePICApplications,o=epic 15. Change the values in the following fields: ePICBFMMessageFilename:bfm_messages ePICBFMPackage: com.ibm.epic.bfm.ejb ePICDataSourceStore: jdbc:db2:BFM ePICDataSourceString: jdbc/BFMDataSrc ePICDBDriver: COM.ibm.db2.jdbc.app.DB2Driver ePICInitialContextFactory: com.ibm.ejs.ns.jndi.CNInitialContextFactory ePICJawsWorkflowPackage: com.ibm.epic.bfm.jaws ePICJdbcURL: jdbc:db2:BFM 16. The remainder of the fields should be blank. 17. Edit LDAP data entries for the following DN string: ePICBodyType=DEFAULT,ePICBodyCategory=DEFAULT, cn=ePICAdapterRouting,ePICAppId=BFM, o=ePICApplications,o=epic 18. Change the values in the following fields: ePICCommandClassName: BFMMsgReceiver ePICCommandEJBInitialContext: com.ibm.ejs.ns.jndi.CNInitialContextFactory ePICCommandEJBMapper: com.ibm.epic.emp.common.adapters.bfmmsgreceiver.BFMMsgReceiverInput_Terminal1TDCMapper ePICCommandEJBMethod: executeBFMMsgReceiver ePICCommandEJBMethodParmType: com.ibm.epic.emp.common.adapters.bfmmsgreceiver.BFMMsgReceiverInput_Terminal1TDC ePICCommandEJBURL: IIOP:/// ePICCommandType: MQAKEJB ePICDestIds: MQSI ePICErrorMQPPQueue: BFMAEQ ePICJMSErrorQueueName: cn=JMSBFMAEQ ePICJMSReceiveQueueName: cn=JMSBFMAIQ ePICJMSReplyQueueName: cn=JMSBFMRPL ePICMessageFormatter: com.ibm.epic.adapters.eak.nativeadapter.JMSNMRFH2Formatter ePICReceiveMode: JMS ePICReceiveMQPPQueue: BFMAIQ ePICReceiveTimeout: 30000 ePICReplyMQPPQueue: BFMRPL 19. Leave the remaining fields blank. 5.3 STOP THE MQSERIES LISTENER BEFORE RERUNNING CONFIGURE.BAT FOR THE TRUST AND ACCESS MANAGER OR TRUST AND ACCESS MANAGER PLUS FACILITIES TOPOLOGIES: All. MACHINES: Base machine. SYMPTOM: When rerunning configuration a port mismatch between the Trust and Access Manager or Trust and Access Manager Plus facilities and the other machines for the cluster sender and cluster receiver channels. This mismatch occurs because an existing listener running on the base machine causes the MQSeries port number to be incremented in the topology repository. The number is subsequently used by the other machines but the value is not used on the base machine because the listener already exists. RESOLUTION: Use the MQSeries Services to manually stop the listener for the queue manager on the base machine before running configure.bat. =============================================================================== 6. WHILE RUNNING CONFIGURE.BAT =============================================================================== The following steps should be performed during the configuration of WebSphere Business Integrator. 6.1 CONFIGURE.BAT MUST BE RERUN BECAUSE OF A POLICY DIRECTOR PROBLEM TOPOLOGIES: All Enterprise. MACHINES: Machine containing the Trust and Access Manager Plus facility. SYMPTOM: Configuration reports that Policy Director Management Server service is not running. RESOLUTION: Rerun configure.bat. 6.2 CONFIGURE.BAT MUST BE RERUN BECAUSE 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 (IBM WS AdminServer) service cannot be started. RESOLUTION: Edit the httpd.conf file in the directory: \IBM HTTP Server\conf Go to the last line but one and remove "f.bak" from the start of the alias entry. Start the IBM HTTP Server service manually and then rerun configure.bat. 6.3 CONFIGURE.BAT MAY REQUIRE MANUAL TERMINATION TOPOLOGIES: All enterprise. MACHINES: Machine containing the BFM Workflow facility. 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. 6.4 MQSERIES CONFIGURATION ERROR MESSAGE CAN BE SAFELY IGNORED TOPOLOGIES: All. MACHINES: Base machine. 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.5 CHANGING THE LDAP CERTIFICATE NAME IF IT HAS BEEN ENTERED INCORRECTLY TOPOLOGIES: All. MACHINES: The Trust and Access Manager and the Trust and Access Manager Plus machines. SYMPTOM: The LDAP service fails because the certificate name has been entered incorrectly by the user. RESOLUTION: In the \etc directory of the SecureWay Directory use a text editor to open the file: slapd32.conf Locate the line: ibm-slapdSslCertificate: Change the entry to contain the correct certificate name. Note: this is not the same as the name of the kdb file. =============================================================================== 7. AFTER RUNNING CONFIGURE.BAT =============================================================================== The following steps should be performed after the configuration of WebSphere Business Integrator but before deploying or running solutions. 7.1 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. 7.2 LDAP SETTINGS MUST BE RESET FOLLOWING DISABLE/RE-ENABLE OF WEBSPHERE GLOBAL SECURITY TOPOLOGIES: All. MACHINES: 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 the default values). RESOLUTION: Change the settings to the correct values as specified in the Installation Guide section on WebSphere Application Server security. 7.3 MQSERIES PUBLISH/SUBSCRIBE QUEUES ARE NOT IN THE CLUSTER TOPOLOGIES: Large-scale Enterprise Production MACHINES: Machine containing the interaction manager facility SYMPTOM: MQSeries PUB/SUB queues are not in the cluster RESOLUTION: Make the local queues available to all the queue managers in the cluster. Use the MQSeries Explorer, and right click on the queues: SYSTEM.JMS.ADMIN.QUEUE SYSTEM.JMS.PS.STATUS.QUEUE SYSTEM.JMS.REPORT.QUEUE SYSTEM.JMS.ND.SUBSCRIBER.QUEUE SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE SYSTEM.JMS.D.SUBSCRIBER.QUEUE SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE For each queue select Share in Cluster, select the Share in Cluster option and then select the Cluster name from the dropdown box. 7.4 INTERACTION MANAGER PERSONALIZATION FILES ARE INSTALLED INTO THE WRONG DIRECTORY TOPOLOGIES: All. MACHINES: Machine containing the Interaction Manager facility. SYMPTOM: Interaction Manager personalization fails to work. RESOLUTION: After installing and configuring the CSD, move the file MenuItems.hrf from: \Personalization\publishedResources\ to \WAStarget_dir\Personalization\publishedResources\ 7.5 EXCEPTION.DTD IS IN THE WRONG DIRECTORY TOPOLOGIES: All. MACHINES: Machines containing the Solution Manager facility. SYMPTOM: The exception.dtd file needs to be in the directory with the xml file. RESOLUTION: Copy the file exception.dtd from: \properties to: \utils 7.6 MISSING EXCEPTIONS FROM DI ADAPTER TOPOLOGIES: All enterprise containing EDI Gateway option. MACHINES: Machine containing the EDI Gateway facility. SYMPTOM: EpicDIExceptionMessages.properties file missing. RESOLUTION: Follow these instructions on the machine containing the EDI Gateway facility. 1. Ensure that the WSBI DI Adaptor daemon is not running. 2. Open a command window. 3. Change drive and directory to the WebSphere DataInterchange bin directory: \WebSphere DataInterchange\bin 4. Make the directory com\ibm\epic\DI under the bin directory. Use the command: mkdir com\ibm\epic\DI You should now have the directory structure: \WebSphere DataInterchange\ bin\com\ibm\epic\DI 5. Copy from releasenotesfiles.zip the file EpicDIExceptionMessages.properties into \WebSphere DataInterchange\ bin\com\ibm\epic\DI 8. Copy from releasenotesfiles.zip the updated file Webb2bdi_1.jar into the WebSphere DataInterchange bin directory \WebSphere DataInterchange\bin 9. Now the WSBI DI Adapter daemon can be restarted. 7.7 JAR FILES MUST BE ADDED TO THE SYSTEM CLASSPATH ON THE DATA INTERCHANGE MACHINE TOPOLOGIES: All enterprise containing EDI Gateway option. MACHINES: Machine containing the EDI Gateway facility. SYMPTOM: Data Interchange adapter daemon fails to start. RESOLUTION: Include the following files on the system CLASSPATH : \MQSeries\Java\lib\com.ibm.mqjms.jar \MQSeries\Java\lib\jndi.jar \MQSeries\Java\lib\ldap.jar \MQSeries\Java\lib\providerutil.jar Use the System applet from the Microsoft Windows NT Control Panel. 7.8 CONFIGURATION FILES MISSING FOR SOLUTION MANAGER DAO FUNCTION TOPOLOGIES: All. MACHINES: Machines containing the Solution Manager facility. SYMPTOM: The DAO function of Solution Manger does not work correctly. RESOLUTION: After installing and configuring, copy the following files from releasenotesfiles.zip: DataAccessInsertNew.dtd DataAccessSelectNew.dtd to: \xml\ =============================================================================== 8. RUNTIME =============================================================================== The entries in this section apply to the WebSphere Business Integrator components at runtime. 8.1 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. 8.2 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 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. 8.3 THE WEBSPHERE APPLICATION SERVER ADMINISTRATION CLIENT SHOULD BE RUN FROM THE PRODUCT CONSOLE LAUNCHPAD TOPOLOGIES: All. MACHINES: Machine containing the Product Console or Product Console Plus facilities. SYMPTOM: The WebSphere Application Server Administration Client does not run from the entry provided on the Microsoft Windows NT Start menu. RESOLUTION: The client should be run from the Product Console Launchpad. See the WebSphere Business Integrator Run Time book for details. To run the client from the WebSphere Application Server adminserver.bat batch file, open a Windows NT Command Prompt and from the directory: \bin type the command: adminclient where is the hostname of the machine on which WebSphere Application Server is running. 8.4 STATUS AND MANAGEABILITY OF DB2 FROM THE PLATFORM CONSOLE TOPOLOGIES: All. MACHINES: All machines containing DB2 Server or DB2 Admin Client SYMPTOM: It is not possible to stop and start DB2 (Server or Client) from the Platform Console. It is not possible to determine the status of the DB2 Admin Client from the Platform Console. The DB2 Server, installed on the Base machine, is displayed in the Platform Console with a status icon indicating whether the server is running, stopped, or otherwise. Even though you can select "Manage" from the context menu for this application and invoke "start" and "stop" operations, these will not be completed because of dependent services. The server will remain in the state it was in before the operation was invoked. The DB2 Admin Client is installed on other machines and is indistinguishable from the DB2 Server within the Platform Console (it has the same application name and description). The Admin Client cannot be controlled by the "start" and "stop" from within the console. When you select "Manage" and try to run operations, no subsequent panel will be displayed. The status of the Admin Client will always have a blue-ball icon associated with it. RESOLUTION: Do not stop and start DB2 from the Platform Console. Use the Windows NT services application to stop and start DB2. Use the Windows NT services application to determine the status of the DB2 Admin Client. 8.5 STATUS AND MANAGEABILITY OF PARTNER AGREEMENT MANAGER FROM THE PLATFORM CONSOLE TOPOLOGIES: All topologies with the PAM Gateway option. MACHINES: All machines containing the PAM Gateway facility. SYMPTOM: It is not possible to stop and start the Partner Agreement Manager from the Platform Console, even though it appears as a service in the Windows NT Services manager. The status of Partner Agreement Manager will have an associated blue-ball icon representing it. RESOLUTION: Do not stop and start PAM from the Platform Console. Use the Windows NT services application to stop and start PAM. Use the Windows NT services application to determine the status of the PAM Admin Client. 8.6 MQSERIES ICON IN THE WINDOWS NT ICON TRAY IS NOT RESTORED TOPOLOGIES: All. MACHINES: All. SYMPTOM: If the MQSeries icon is enabled (it is visible) in the NT icon tray, stopping the MQSeries service from either the Platform Console or from the NT Services Manager results in the removal of the icon from the tray. Restarting the service will not restore the MQSeries icon to the tray. RESOLUTION: The icon can be permanently removed from the NT icon tray by running the MQSeries service from the Start menu (use WebSphere Business Integrator->IBM MQSeries folders), clicking on Alert Monitor with mouse button 2, selecting Properties, then the Parameters tab, and clicking the Hide button. You can restore the icon to the tray after it has been removed by following the above procedure and clicking on the Show button instead of Hide. 8.7 CANNOT INVOKE OPERATIONS OR GET STATUS OF MQSERIES WORKFLOW IN THE PLATFORM CONSOLE TOPOLOGIES: All Enterprise. MACHINES: All machines containing the BFM Workflow facility. SYMPTOM: MQSeries Workflow appears to be unmanageable from the Platform Console because it has a blue-ball default status icon. However, if you select "Manage" from the context menu, the subsequent panels are displayed. Operations such as "start" and "stop" are selectable from the panels but nothing will happen to the Workflow service. A message is displayed to say that the operation could not be completed. RESOLUTION: Do not stop and start MQSeries Workflow from the Platform Console. Use the Windows NT services applet to stop and start MQSeries Workflow. Use the Windows NT services applet to determine the status of the DB2 Admin Client. 8.8 TRUST AND ACCESS MANAGER RESTART CAUSES BROKER DATABASE ERROR TOPOLOGIES: All Enterprise. All Entry with the Message Broker option. MACHINES: Machine containing the Broker facility. SYMPTOM: If the TAM is restarted, the configmgr process (part of MQSeries Integrator running on the Broker machine) will start using 100% CPU and will fill up the NT Application log with many messages relating to the loss of the Database connection. In the NT application log, the error message will be created by MQSeries Integrator with ID 1205. RESOLUTION: Stop and restart the configmgr on the broker machine. 8.9 DATA INTERCHANGE QUEUES DO NOT APPEAR IN CLUSTER TOPOLOGIES: All enterprise containing EDI Gateway option. MACHINES: Machine containing the EDI Gateway facility. SYMPTOM: Data Interchange Queues do not appear in the cluster. RESOLUTION: Make the local queues available to all the queue managers in the cluster. Go to the MQSeries Explorer and right click on the following queues: DIAEQ DIAIQ DIRPL EDITP1AEQ EDITP1AIQ EDITP1RPL Select Share in Cluster, select the Share in Cluster option, and then select the Cluster name from the dropdown box. =============================================================================== 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 redeploy a solution or solution element. 9.2 UNABLE TO IMPORT ENTERPISE BEANS WITH DEPENDENT CLASSES TOPOLOGIES: All MACHINES: Machines containing the WebSphere Application Server product. SYMPTOM: Some Enterprise Beans fail to deploy to WebSphere Application Server because a class on which the bean depends is not in the CLASSPATH. RESOLUTION: On the machine with the Integrated Console facility installed, 1. Start the Product Console Launchpad using: Start->Programs->WebSphere Business Integrator-> IBM Solution Management->Product Console Launchpad 2. From the View menu, select Logical. 3. Select the BFM Application Server or BFM Application Server Plus facility in the left-hand panel. 4. Right-click the WebSphere AE entry in the right-hand panel and select WebSphere Admin Console. 5. In the admininstrative console, select each node under the WebSphere administrative domain in turn and do the following: a. Append the following text to the end of the dependent classpath (all on one line): ;\solution\lib; \solution\properties b. Right-click the node and select Restart. Note: The should be replaced with the directory under which WebSphere Business Integrator is installed on the node you are currently processing in the WebSphere Application Server console. 6. Start the IBM WS AdminServer service. =============================================================================== 10. PARTNER AGREEMENT MANAGER =============================================================================== The entries in this section apply to the WebSphere Business Integrator Partner Agreement Manager. 10.1 CONFIGURATION REQUIRED ON PARTNER AGREEMENT MANAGER DATABASE TOPOLOGIES: All containing Partner Agreement Manager MACHINES: Machine containing the Partner Agreement Manager facility. SYMPTOM: Various DB2 errors are seen in the Partner Agreement Manager logs regarding lack of heap space. RESOLUTION: It is important to set up the parameters for the DB2 database as noted in the Installing and Configuring DB2 section of the Installation Guide for Partner Agreement Manager. The following parameters might also be required Parameter Default Value Recommended Value dbheap 600 60000 app_ctl_heap_size 128 512 Also note #11174 in the Partner Agreement Manager README.txt file regarding the re-importing of a stored procedure. The comment below adds extra instructions that are required after running newdb and are modified to include values specific to WebSphere Business Integrator. Open the DB2 Control Center. 1. Select Databases->WSBIPAM->Application Objects-> Stored Procedures 2. Drop the Stored Procedure IS_UPD_REINIT_SP Open a DB2 Command Window and type the following commands: 1. db2 connect to WSBIPAM user db2admin using 2. cd \config\db2_schema\w32_intl 3. db2 put routine from is_upd_reinit_sp.sar 10.2 ERRORS OCCUR IF THE BPI ADAPTER IS CONFIGURED TO USE 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: These error are caused because two JAR files are missing from the system classpath or are absent from the /lib/ext directory. Open the System application from the Microsoft Windows NT Control Panel, access the Environment tab and 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 Restart the system to make these changes take effect. 10.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, 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. 10.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 that 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 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, because 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 you should perform a periodic restart of the adapter or change the ProcessCompletionNotification option to true. 10.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. 10.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.