=============================================================================== IBM WebSphere Business Integrator Version 2.1 Product Release Notes Last Updated: 25 May 2001 (C) Copyright IBM Corporation 2001. All rights reserved. =============================================================================== This file contains instructions that will ensure proper solution development and deployment from Solution Studio and the Deployment Framework. =============================================================================== I. CONTENTS =============================================================================== I. CONTENTS II. ACCESSING THE PRODUCT WEB SITE III. TRADEMARKS 1. DOCUMENTATION 2. WORKING IN SOLUTION STUDIO 3. USER REGISTRATION SAMPLE SOLUTION BEFORE PUBLISHING 4. USER REGISTRATION SAMPLE SOLUTION AFTER DEPLOYMENT 5. PURCHASE ORDER SAMPLE SOLUTION AFTER DEPLOYMENT =============================================================================== II. ACCESSING THE PRODUCT WEB SITE =============================================================================== Please visit the WebSphere Business Integrator Web site for the most recent product information: http://www.ibm.com/software/websphere/btobintegrator =============================================================================== III. 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. WORKING IN SOLUTION STUDIO =============================================================================== 2.1 SUBSTITUTION STRINGS DO NOT WORK FOR DB2 USERID AND PASSWORD TOPOLOGIES: All. MACHINES: All. SYMPTOM: Two Solution Studio Wizards create instructions to deploy Enterprise Java Beans in WebSphere Application Server. These instructions require a valid DB2 Administrator userid and password. The wizards use substitution strings to obtain this information from LDAP and this substitution process is failing. RESOLUTION: Hard code the DB2 Administrator's userid and password by hand prior to publishing a Solution Package. DETAILS: After executing the WebSphere Application Server Artifact Configuration Wizard and the MQSeries Adapter Builder Wizard (with Enterprise Java Bean) an XML instruction file will be created. These files must be changed to hold the actual userid and password. For example: After configuring an Enterprise Java Bean the following instructions will be created: ... WAS importEJB ... The third and fourth parameters contain a string that should resolve to the DB2 userid and password. This string should be changed in the file to the actual userid and password as follows: ... WAS importEJB ... 2.2 QUEUE MANAGER SUBSTITUTION STRINGS NOT WORKING PROPERLY TOPOLOGIES: All. MACHINES: All. SYMPTOM: There is a case mismatch when trying to resolve Queue Manager names using hostnames. The Solution Studio Wizards provide a means to allow for substitution strings to be used to resolve to installed Queue Manager names. RESOLUTION: Hard code Queue Manager names when defining them in Solution Studio, do not use the substitution strings. =============================================================================== 3. USER REGISTRATION SAMPLE SOLUTION BEFORE PUBLISHING =============================================================================== The following changes should be made to the Solution Studio. 3.1 QUEUE MANAGER NAME IN THE USER REGISTRATION PACKAGE MAY NOT MATCH RUN TIME PLATFORM TOPOLOGIES: All. MACHINES: All. SYMPTOM: User Registration may fail if the Queue Manager name in the deployable package does not match the Queue Manager name specified when the MQSeries Workflow machine was installed. RESOLUTION: Edit the B2BITemplatesUserReg.fdl to use the Queue Manager name installed with MQSeries Workflow. DETAILS: Before publishing User Registration: 1. Edit the B2BiTempatesUserReg.fdl file in the BusinessProcess folder of the User Registration Project. 2. Search the FDL for "QUEUE_MANAGER_NAME". 3. Change the value that follows to the actual Queue Manager Name used for MQSeries Workflow in the run-time environment. 4. Continue searching until all occurrences of QUEUE_MANAGER_NAME have been found and changed. 5. Save the file and check it into the Studio project. 3.1 CONFIGURATION ERRORS IN USERREG.WSR TOPOLOGIES: All. MACHINES: All. SYMPTOM: Deployment of User Registration fails with no User Registration error message. RESOLUTION: If you use User Registration .wsr file to load Solution Studio and deploy the User Registration sample, two changes must be made by hand: 1. Update ReceiveConfirmation_Adapter_Inst.xml change UserReg to UserRegContainer. 2. Update UserRegWraparound_Inst.xml change UserReg to UserRegContainer. DETAILS: Before publishing User Registration: 1. Edit the ReceiveConfirmation_Adapter_Inst.xml file in the Application/BFMAdapters folder of the User Registration Project. 2. Search the file for "UserReg". 3. Change the value from UserReg to "UserRegContainer". Note that you are seeking the UserReg by itself not other UserRegContiner fields. 4. Save the file and check it into the Studio project. 5. Edit the UserRegWraparound_Inst.xml file in the Application/BFMAdapters folder of the User Registration Project. 6. Search the file for "UserReg" 7. Change the value from UserReg to "UserRegContainer" Note that you are seeking the UserReg by itself not other UserRegContiner fields. 8. Save the file and check it into the Studio project. =============================================================================== 4. USER REGISTRATION SAMPLE SOLUTION AFTER DEPLOYMENT =============================================================================== The following changes should be made for the User Registration Sample after it has been deployed using the deployment framework. 4.1 USER REGISTRATION DATABASE TABLES MUST BE DEFINED TOPOLOGIES: All. MACHINES: Business Flow Manager WebSphere Application Server. SYMPTOM: The User Registration sample will not run without the database tables. RESOLUTION: After deploying User Registration on the Business Flow Manager machine, from a DB2 command window, enter: db2 -f wsbi_install_path\solution\SQL\registration.ddl 4.2 USER REGISTRATION REGISTRATION.DDL FILE NEEDS SPECIAL CARE TO CREATE DATABASE TOPOLOGIES: All. MACHINES: Business Flow Manager WebSphere Application Server. SYMPTOM: In a client/server environment the registration.ddl may not create the database. RESOLUTION: Create the database using the DB2 Control Center. DETAILS: From a DB2 command prompt enter: db2 -f wsbi_install_path\solution\SQL\registration.ddl This will attempt to create the B2BITMPL database, connect to it, and (re-)create the REGISTRATIONBDO table. Typically, the ddl is executed on the DB2 server node. If running from a DB2 client node, the database may not be created. In such cases, you may use the DB2 control center database creation wizard first and create the database, and after that run the db2 command against the ddl as shown above. 4.3 USER REGISTRATION REQUIRES A JTA ENABLED DRIVER TOPOLOGIES: All. MACHINES: Business Flow Manager WebSphere Application Server. SYMPTOM: The User Registration sample will not run without the proper database driver. RESOLUTION: After deploying, use the WebSphere Administration Console to update the JTA enable driver. DETAILS: After deploying User Registration, use the WebSphere Administration Console to: 1. Select the WSBIDeploy application server. 2. Stop the WSBIDeploy application server. 3. Modify the database driver used by the BtoBiTemplatesDS and set it to "JTA enabled". 4. Apply the change. 5. Start the WSBIDeploy application server. =============================================================================== 5. PURCHASE ORDER SAMPLE SOLUTION AFTER DEPLOYMENT =============================================================================== The following changes should be made for the User Registration sample after it has been deployed using the deployment framework. 5.1 PURCHASE ORDER DATABASE TABLES MUST BE DEFINED TOPOLOGIES: All. MACHINES: Business Flow Manager WebSphere Application Server. SYMPTOM: The Purchase Order sample will not run without the database tables. RESOLUTION: After deploying Purchase Order, on the Business Flow Manager machine, from a DB2 command window, enter: db2 -f wsbi_install_path\solution\SQL\B2BiTemplatesPOMgmt.ddl 5.2 PURCHASE ORDER B2BITEMPLATESPOMGMT.DDL FILE NEEDS SPECIAL CARE TO CREATE DATABASE TOPOLOGIES: All. MACHINES: Business Flow Manager WebSphere Application Server. SYMPTOM: In a client/server environment the registration.ddl may not create the database. RESOLUTION: Create the database using the DB2 Control Center. DETAILS: From a DB2 command prompt enter: db2 -f wsbi_install_path\solution\SQL\B2BiTemplatesPOMgmt.ddl This will attempt to create the B2BITMPL database, connect to it, and (re-)create the BackorderedItem, CatalogItem, InventoryItem, PO, POLineItem tables. Typically, the ddl is executed on the DB2 server node. If running from a DB2 client node, the database may not be created. In such cases, you may use the DB2 control center database creation wizard first and create the database, and after that run the db2 command against the ddl as shown above. 5.3 PURCHASE ORDER REQUIRES A JTA ENABLED DRIVER TOPOLOGIES: All. MACHINES: Business Flow Manager WebSphere Application Server. SYMPTOM: The Purchase Order sample will not run without the proper database driver. RESOLUTION: After deploying, use the WebSphere Administration Console to update the JTA enable driver. DETAILS: After deploying User Registration, use the WebSphere Administration console to: 1. Select the WSBIDeploy application server. 2. Stop the WSBIDeploy application server. 3. Modify the database driver used by the BtoBiTemplatesDS and set it to "JTA enabled". 4. Apply the change. 5. Start the WSBIDeploy application server.