MQSeries Workflow Version 3.3.2 - Service Pack #1 ----------------------------------------- INDEX ------------------------------------------ 1. Installation of Service Pack #1 1.1 Installation on Microsoft Windows NT/2000/ME/98 1.2 Installation on IBM AIX 1.3 Installation on Sun Solaris 1.4 Installation on HP-UX 2. Important Notes 2.1 Applying service to the Web Client 2.2 Migrating from a previous release - Installation Guide update 3. Changes 3.1 Changes in Service Pack #1 ------------------------------------------ 1. Installation of Service Pack #1 ================================== 1.1 Installation on Microsoft Windows NT/2000/ME/98 --------------------------------------------------- 1.1.1 Which files must be downloaded? The Service Pack consists of several self-extracting and self-installing executables. There is one for each National Language version of IBM MQSeries Workflow. To make the distribution of client updates easier, there are three types of self-extracting executables to update Client, Buildtime or full installations, respectively. The Client and Buildtime packages contain only certain MQSeries Workflow components and they are only applicable if these components or a subset of these components are installed. Use the full package to update installations including more than these components. The Client package consists of the API Runtime Library, Program Execution Agent, Runtime Client, Lotus Notes API, Admininstration Utility, Samples, Java, and the CORBA Agent component. The Buildtime package includes the Buildtime component and samples. List of the available self-extracting executables: Full Package: ------------- W332ENA2.EXE - U.S. English language version W332CSA2.EXE - Simplified Chinese language version W332CTA2.EXE - Traditional Chinese language version W332DAA2.EXE - Danish language version W332DEA2.EXE - German language version W332ESA2.EXE - Spanish language version W332FIA2.EXE - Finnish language version W332FRA2.EXE - French language version W332HEA2.EXE - Hebrew language version W332HUA2.EXE - Hungarian language version W332ITA2.EXE - Italian language version W332JPA2.EXE - Japanese language version W332KOA2.EXE - Korean language version W332NLA2.EXE - Dutch language version W332NOA2.EXE - Norwegian language version W332PLA2.EXE - Polish language version W332PBA2.EXE - Brazilian Portuguese language version W332PGA2.EXE - Portuguese language version W332TRA2.EXE - Turkish language version Client Package: --------------- W332ENC2.EXE - U.S. English language version W332CSC2.EXE - Simplified Chinese language version W332CTC2.EXE - Traditional Chinese language version W332DAC2.EXE - Danish language version W332DEC2.EXE - German language version W332ESC2.EXE - Spanish language version W332FIC2.EXE - Finnish language version W332FRC2.EXE - French language version W332HEC2.EXE - Hebrew language version W332HUC2.EXE - Hungarian language version W332ITC2.EXE - Italian language version W332JPC2.EXE - Japanese language version W332KOC2.EXE - Korean language version W332NLC2.EXE - Dutch language version W332NOC2.EXE - Norwegian language version W332PLC2.EXE - Polish language version W332PBC2.EXE - Brazilian Portuguese language version W332PGC2.EXE - Portuguese language version W332TRC2.EXE - Turkish language version Buildtime Package: ----------------- W332ENB2.EXE - U.S. English language version W332CSB2.EXE - Simplified Chinese language version W332CTB2.EXE - Traditional Chinese language version W332DAB2.EXE - Danish language version W332DEB2.EXE - German language version W332ESB2.EXE - Spanish language version W332FIB2.EXE - Finnish language version W332FRB2.EXE - French language version W332HEB2.EXE - Hebrew language version W332HUB2.EXE - Hungarian language version W332ITB2.EXE - Italian language version W332JPB2.EXE - Japanese language version W332KOB2.EXE - Korean language version W332NLB2.EXE - Dutch language version W332NOB2.EXE - Norwegian language version W332PLB2.EXE - Polish language version W332PBB2.EXE - Brazilian Portuguese language version W332PGB2.EXE - Portuguese language version W332TRB2.EXE - Turkish language version 1.1.2 Installing the Service Pack Make sure that you have stopped all running MQSeries Workflow processes and services before installing the Service Pack. Double click on the downloaded executable in the Windows Explorer. The program unpacks the files to the temporary directory and starts the installation right after unpacking. 1.1.3 Upgrading your existing MQSeries Workflow configuration Because this package includes updated DB2 bind files, you have to bind the new files to your MQSeries Workflow runtime databases as follows: - Open a DOS Command Prompt and run the configuration utility 'fmczutil' - Choose the configuration identifier of the configuration you want to update. - Choose the 'r'untime database menu, then select 'b'ind. All bindings are made for you. This can take several minutes. After you have performed these steps, your system is ready to run. You can restart your MQSeries Workflow services and processes again. 1.2 Installation on IBM AIX --------------------------- 1.2.1 Which files must be downloaded? Please download the package wf332a1u.tar.gz (42 MB) and unpack the file to a temporary subdirectory. You need approximately 88 MB to unpack the file. Unpack the downloaded file using the command gzip -dc wf332a1u.tar.gz | tar -vxf - to create the actual update installation images. 1.2.2 Installing the Service Pack 1) Stop all running MQSeries Workflow processes, for example, by shutting down the MQSeries Workflow system using the administration utility "fmcautil". 2) As root, perform the command 'slibclean'. 3) Update your MQSeries Workflow 3.3.2.0 installation (with or without having hotfixes applied) using smit - "update to latest level" to level 3.3.2.10. Note: Your configuration (profiles, /var/fmc/...) will not be modified by the update. However, the installation profile /usr/lpp/fmc/fmcrc will be updated to reflect the new level "ServiceLevel=1". 4) Because this package includes updated DB2 bind files, you have to bind the new files to your MQSeries Workflow runtime databases as follows: - As user "fmc" invoke the configuration utility 'fmczutil' - Choose the configuration identifier of the configuration you want to update. - Choose the 'r'untime database menu, then select 'b'ind. All bindings will be made for you. This can take several minutes. After you have performed these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 1.3 Installation on SUN Solaris ------------------------------- 1.3.1 Which files must be downloaded? Please download the package wf332s1u.tar.gz (28 MB) and unpack the file to a temporary subdirectory. You need approximately 103 MB to unpack the file. Unpack the downloaded file using the command gzip -dc wf332s1u.tar.gz | tar -vxf - to create the actual update installation image. For a client-only installation, use the file wf332s1c.tar.gz. 1.3.2 Installing the Service Pack 1) First, stop all running MQSeries Workflow processes, for example by shutting down the MQSeries Workflow System using the admin utility "fmcautil". Make sure that all MQSeries Workflow processes are stopped and no file of the product is in use. 2) This is how to update your MQSeries Workflow 3.3.2.0 files (with or without having hotfixes applied) to level 3.3.2.10: Issue the following command line as user "root", replace the path "/tmp/fmc332u1.pkg" from this example with the fully qualified path and filename of your ".pkg" file: pkgadd -d /tmp/fmc332u1.pkg (full package) or pkgadd -d /tmp/fmc332u1cl.pkg (client package) accept the installation of this package and overwriting files of the previous package 3.3.2.0. Note: Your configuration(s) (profiles, /var/fmc/...) will NOT be modified by the update. However, the installation profile /opt/fmc/fmcrc will be updated to reflect the new level "ServiceLevel=1". 3) Full installation package only: Because this package includes updated DB2 bind files, you have to bind the new files to your MQSeries Workflow runtime databases as follows: - As user "fmc" invoke the configuration utility 'fmczutil' - Choose the configuration identifier of the configuration you want to update. - Choose the 'r'untime database menu, then select 'b'ind. All bindings will be made for you. This can take several minutes. After you have performed these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 1.4 Installation on HP-UX ------------------------- 1.4.1 Which files must be downloaded? Please download the package wf332h1u.tar.gz (39 MB) and unpack the file to a temporary subdirectory. You need approximately 41 MB to unpack the file. Unpack the downloaded file using the command gzip -dc wf332h1u.tar.gz | tar -vxf - to create the actual update installation images. For a client-only installation, use the file wf332h1c.tar.gz. 1.4.2 Installing the Service Pack 1) Stop all running MQSeries Workflow processes, for example, by shutting down the MQSeries Workflow system using the administration utility "fmcautil". Make sure that all MQSeries Workflow processes are stopped and no file of the product is in use. 2) Update your MQSeries Workflow 3.3.2.0 files (with or without having hotfixes applied) to level 3.3.2.10 as follows: - Use 'sam' to install the new package. - Select the "software" icon, then select "add software to local host". - Choose 'installation from disk' and enter the fully qualified path to the file "FMC332U1.PKG" (for the full installation package) and the filename itself. - Use the file FMC332U1CL.PKG for the client-only installation. - Choose "Install" from the "Actions" pulldown menu and confirm twice. After the installation you can proceed with step 3. If you do not want to use 'sam', you can use 'swinstall' with the appropriate command-line parameters that suit your needs. Note: Your configuration(s) (profiles, /var/fmc/...) will NOT be modified by the update. 3) Run the command fmczinsx -o upd to update the installation profile /opt/fmc/fmcrc with the new level "ServiceLevel=1". This value reflects the current service pack level of the installation. 4) Full installation package only: Because this package includes updated DB2 bind files, you have to bind the new files to your MQSeries Workflow runtime databases as follows: - As user "fmc" invoke the configuration utility 'fmczutil' - Choose the configuration identifier of the configuration you want to update. - Choose the 'r'untime database menu, then select 'b'ind. All bindings will be made for you. This can take several minutes. After you have performde these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 2. Important Notes ==================== 2.1 Applying service to the Web Client -------------------------------------- It is recommended to have an own configuration for the Web Client. This way, you can easily apply service to the Web Client as follows: - Install the MQSeries Workflow Service Pack - Back up the Web Client files that you have changed (for example, WebClient.properties) to a directory that is NOT a subdirectory of \cfgs or \installedApps in case you are using WebSphere V4, because the complete subtree of your old Web Client configuration will be deleted in the next step. - Delete the Web Client configuration using the configuration utility 'fmczutil'. - Remove the WebClient's application server in WebSphere. When using WebSphere Version 4, you must remove the WebClient enterprise application before you can remove the application server. - Create a new Web Client configuration. - Merge the changes you made with the new Web Client files. This includes re-installing the samples for the Web Client as, for example, the AuditTrailHandler and the Groupworklist sample. NOTE: For the AuditTrailHandler, the Web Client needs Xalan-Java 2, which is available on the following Web site: http://xml.apache.org/xalan-j It is strongly recommended that you delete the temporary directory that you created for the compiled JSPs of the Web Client on your application server. When using IBM WebSphere V3, this temporary directory is \temp\\MQWFClient-, for example, d:\WebSphere\AppServer\temp\default_host\MQWFClient-WEBC. When using IBM WebSphere V4, this temporary directory is \temp\\WebClient_Server_-_. 2.2 Migrating from a previous release - Installation Guide update ----------------------------------------------------------------- If you migrate a buildtime database from a previous release, you need to drop the tables in the database before removing the old installation. Execute the following command after you completed step "Export Buildtime data" on page 388, Appendix P of the Installation Guide: fmcbdcdb -o=db -yConfigID In section "Prepare Buildtime", bullet 2 on page 396, Appendix P of the Installation Guide execute only the second command to recreate the tables: fmcbdcdb -o=cb -yConfigID 3. Changes ========== 3.1 Changes in Service Pack #1 ------------------------------ The following problems are fixed: Nr. PMR/APAR Description 16183 PMR77561 Database deadlocks under various conditions 16240 PMR00361 " 16276 PQ57158 " 15052 Buildtime migration abends when PATH ends with \" 15255 WebClient: Do not allow 'OWNER=CURENT_USER' as process instance filter 15333 Fmcsclad execution time grows exponentially to cleanup entries with option ALL 15865 fmczchk: Trap on Solaris when using response file - 'fmczchk @file' 16046 Oracle: Process may result in wrong state, if parallel activities were running. 16113 PMR85007,033 Profile not found error in case of concurrent logins (multiple-threads) 16131 z/OS: Import of a process with a global container may fail (trace shows SQLCode -805) 16169 IY27119 remote UNIX Buildtime DB creation fails with "Option -l not specified"- update documentation 16168 IY27200 Windows configuration GUI cannot create a remote Buildtime 16180 Missing columns in database view PROCESS_EXEC. 16185 z/OS: Job FMCHJEDC using ...SFMCDB2(FMCHDEDC) fails. 16213 Oracle: Database views are not created in database. 16216 IY28137 port numbers larger than 32678 not accepted during configuration 16219 Pre-condition violation in Exe Server on invalid UserID in XML 16221 PMR62199 Admin Server crash if authentication with Java exit fails 16227 No DB2 Instances listed if db2 node directory is large 16230 IY28280 XML Encoding specification of UTF-16 abends the Execution Server 16235 WF/390 XML R3 Support 16245 Global Container mapping abends the Execution server if strings are longer than 254 bytes. 16246 XML audit trail time stamps do not contain milliseconds 16258 FMCH0IBA: internal exception when DBCS used in membernames 16054 PMR43283 ForceFinish activity in a block, exit condition is evaluated to false and block activity is restarted: Exe Server abends with error message: FMC31050E An error has occurred which has terminated processing. Error data = FmcAssertionException, Condition=*** Assertion failed in e:\v330\src\fmckids.inl(181): (_oid!=rhs._oid) || (_btid==rhs._btid) 16064 invalid char in xml error response message 16068 Missing/lost error info if UPES response msg is in error 16070 Oracle: Start instance with global container fails if empty strings should be inserted into global container. 16071 Query process instance for a Global Container member with filter and sortCriteria: runtime server abend 16072 ProcessInstanceRestart: process is restarted, but process context is missing 16085 Tracing on WIN ME/98 fails 16086 PMR56749 Shared library activity implementation terminates PEA with external exception. 16093 z/OS: SQL error occurs, when querying Process Instances with a filter on a Global Container member. 16096 ADMINSVR on z/OS abends with SQL code = -805. 16098 Wrong version number for NLS Italian 16108 PQ55975 Export does not show WLM setting of EXECUTION_SERVER 16132 Oracle: Resultset of persistent lists with global container filter may be incorrect. 16146 Make WebClient part of the client CSD package. 16148 RELATED_ROLE, RELATED_ORGANIZATION missing for single persons 16151 Execution Server does not terminate after CreateAndStartProcessInstance when AuditQueue is not defined 16153 Oracle: EqualityAssertion may occur, when update e.g. work_item with an empty string in description. 16154 Add password to IMS Bridge header 16164 NullPointerException in createAndStartInstance3() Java API 16207 UserId Mapping via PES Directory doesn't work 16208 Intermittent PEA crashes for Noop ActImpl.