WebSphere MQ Workflow Version 3.4.0 - Service Pack #1 (March 2003) ------------------------------------------------------------------ INDEX -------------------------------------------------------------- 1. Installation of Service Pack #1 1.1 Installation on Microsoft Windows NT/2000/XP 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 Packs to the Web Client 2.2 Documentation error for Portal Client 2.3 Database problems 3. Changes 3.1 Changes in Service Pack #1 4. License Notices -------------------------------------------------------------- 1. Installation of Service Pack #1 ================================== 1.1 Installation on Microsoft Windows NT/2000/XP ------------------------------------------------ 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 WebSphere MQ Workflow. To make the distribution of client updates easier, there are three types of self-extracting executables to update Client, Buildtime, or full installations. The Client and Buildtime packages contain only certain WebSphere MQ 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 that include more than these components. The Client package consists of the API Runtime Library, Program Execution Agent, Runtime Client, Lotus Notes API, Administration Utility, Samples, Java, and the Java Agent component. The Buildtime package includes the Buildtime component and samples. List of the available self-extracting executables: Full Package: ------------- W340ENA1.EXE - U.S. English language version W340CSA1.EXE - Simplified Chinese language version W340CTA1.EXE - Traditional Chinese language version W340DEA1.EXE - German language version W340ESA1.EXE - Spanish language version W340FRA1.EXE - French language version W340HEA1.EXE - Hebrew language version W340HUA1.EXE - Hungarian language version W340ITA1.EXE - Italian language version W340JPA1.EXE - Japanese language version W340KOA1.EXE - Korean language version W340NLA1.EXE - Dutch language version W340PBA1.EXE - Brazilian Portuguese language version W340PGA1.EXE - Portuguese language version W340PLA1.EXE - Polish language version W340TRA1.EXE - Turkish language version Client Package: --------------- W340ENC1.EXE - U.S. English language version W340CSC1.EXE - Simplified Chinese language version W340CTC1.EXE - Traditional Chinese language version W340DEC1.EXE - German language version W340ESC1.EXE - Spanish language version W340FRC1.EXE - French language version W340HEC1.EXE - Hebrew language version W340HUC1.EXE - Hungarian language version W340ITC1.EXE - Italian language version W340JPC1.EXE - Japanese language version W340KOC1.EXE - Korean language version W340NLC1.EXE - Dutch language version W340PBC1.EXE - Brazilian Portuguese language version W340PGC1.EXE - Portuguese language version W340PLC1.EXE - Polish language version W340TRC1.EXE - Turkish language version Buildtime Package: ----------------- W340ENB1.EXE - U.S. English language version W340CSB1.EXE - Simplified Chinese language version W340CTB1.EXE - Traditional Chinese language version W340DEB1.EXE - German language version W340ESB1.EXE - Spanish language version W340FRB1.EXE - French language version W340HEB1.EXE - Hebrew language version W340HUB1.EXE - Hungarian language version W340ITB1.EXE - Italian language version W340JPB1.EXE - Japanese language version W340KOB1.EXE - Korean language version W340NLB1.EXE - Dutch language version W340PBB1.EXE - Brazilian Portuguese language version W340PGB1.EXE - Portuguese language version W340PLB1.EXE - Polish language version W340TRB1.EXE - Turkish language version 1.1.2 Installing the Service Pack Make sure that you have stopped all running WebSphere MQ Workflow processes and services before installing the Service Pack. Double click on the downloaded executable in Windows Explorer. The program unpacks the files to the temporary directory and starts the installation right after unpacking. 1.2 Installation on IBM AIX --------------------------- 1.2.1 Which files must be downloaded? Download the package wf340a1u.tar.gz (21 MB) and unpack the file to a temporary subdirectory. You need approximately 38 MB to unpack the file. To create the update installation images, unpack the downloaded file using the command: gzip -dc wf340a1u.tar.gz | tar -vxf - 1.2.2 Installing the Service Pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow system using the administration utility "fmcautil". 2) As root, perform the command 'slibclean'. 3) Update your WebSphere MQ Workflow 3.4.0.0 installation (with or without having hotfixes applied) using smit - "update to latest level" to level 3.4.0.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". 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? Download the package wf340s1.tar.gz (15 MB) and unpack the file to a temporary subdirectory. You need approximately 47 MB to unpack the file. To create the update installation image, unpack the downloaded file using the command: gzip -dc wf340s1u.tar.gz | tar -vxf - For a client-only installation, use the file wf340s1c.tar.gz (10 MB), which needs about 30 MB to unpack. 1.3.2 Installing the Service Pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow System using the admin utility "fmcautil". Make sure that all WebSphere MQ Workflow processes are stopped and there are no product files in use. 2) Update your WebSphere MQ Workflow 3.4.0.0 files (with or without having hotfixes applied) to level 3.4.0.10: Issue the following command line as user "root", replace the path "/tmp/fmc340u1.pkg" from this example with the fully-qualified path and filename of your ".pkg" file: pkgadd -d /tmp/fmc340u1.pkg (full package) or pkgadd -d /tmp/fmc340u1cl.pkg (client package) Accept the installation of this package and overwrite files of the previous package 3.4.0.0. Note: Your configuration (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". 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? Download the package wf340h1u.tar.gz (22 MB) and unpack the file to a temporary subdirectory. You need approximately 23 MB to unpack the file. To create the update installation images, unpack the downloaded file using the command: gzip -dc wf340h1u.tar.gz | tar -vxf - For a client-only installation, use the file wf340h1c.tar.gz (10 MB), which needs about 10 MB to unpack. 1.4.2 Installing the Service Pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow system using the administration utility "fmcautil". Make sure that all WebSphere MQ Workflow processes are stopped and there are no product files in use. 2) Update your WebSphere MQ Workflow 3.4.0.0 files (with or without having hotfixes applied) to level 3.4.0.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 "FMC340U1.PKG" (for the full installation package) and the filename itself. - Use the file FMC340U1CL.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. Note: Your configuration (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. 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 & 2. Important Notes ================== 2.1 Applying Service Packs to the Web Client -------------------------------------- It is recommended that you have your own configuration for the Web Client. This way, you can easily apply service to the Web Client as follows: - Install the WebSphere MQ Workflow Service Pack - If you are using WebSphere V4, 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. This is 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 Web Client's application server in WebSphere. If you are using WebSphere Version 4, you must remove the Web Client 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, such as 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_-_. If you want to use https in WebSphere 4.0.2, set the system properties under jvm settings. Set the property 'java.protocol.handler.pkgs' to the value 'com.ibm.net.ssl.internal.www.protocol'. For further update details, see the WebSphere manuals. 2.2 Documentation error for Portal Client ----------------------------------------- Installation Guide, Appendix H, page 411, parts 1a and 3g refer to the Portal Client war file as 'MQWFPortalClient.war'. This is incorrect, the actual file name is 'fmcopcli.war'. 2.3 Database problems --------------------- 2.3.1 DB2 Version 8 If you use DB2 Version 8.1, make sure that you have installed the fix for DB2 APAR IY39361. 2.3.1.1 DB2 Version 8 on Sun Solaris On Sun Solaris, there is a known problem in the setup of the XA communication. IY41550 is the corresponding DB2 APAR number. As long as there is no fix available, the SQL error 998 with a reason code of 09 and a subcode of 02 might occur. It has to be ensured that the value of the database manager configuration variable "tp_mon_name" is set to "mq" (rather than mqmax). The DB2 instance owner can set this configuration parameter with the following command: db2 update dbm cfg using tp_mon_name mq Furthermore, the Websphere MQ Series library directory has to be checked for the existence of a library or link named "libmqmax.so". If neither the link nor the library exists, then the link can be created by the MQ installation owner with the following command: ln -s /opt/mq/lib/libmqmax.so /opt/mqm/lib/libmqmax.a 2.3.2 Oracle version 8i Make sure that you have installed Oracle 8i patchset 8.1.7.1, or higher. With earlier versions of the Oracle DBMS, the run-time servers do not start. On AIX, do not use Oracle 8i patchset 8.1.7.2 because this contains errors. 3. Changes ========== 3.1 Changes in Service Pack #1 ------------------------------ The following problems are fixed: Nr. PMR/APAR Description 17991 Canceling the suspending of a process instance makes list portlet unusable 18007 fmczchk on UNIX: Warning is displayed (default port 5010 not found) 18184 Some actions from PropertiesView are not executed 18318 Web Client Logon screen: German Language, Umlaut not shown correctly 18332 Question mark appended at process instance name 18363 Error with XML-Msg via SDDS together with MQ531beta 18451 IY39345 FMCZUTIL does not allow 8 character SIDs 18456 IY39437 System Log and Error Log are not deleted automatically. Depending on the FDL settings MESSAGE_RETAIN_PERIOD and ERROR_RETAIN_PERIOD, system log entries and error log entries in the MQWF runtime database are now deleted automatically by the administration server. 18467 IY39760 Rounding problems with float/string conversion 18468 IY39759 Expiration and Notification are not updated with ForceRestart 18472 IY39717 Web Client with JNDI Locator Policy and a remote JNDI Name Service does not work 18477 PMR49020 FMC00100E Internal Error on Workitem::Transfer() call 18486 IY39929 Creating MQWF databases using raw devices (remote) not possible 18507 Buildtime: No Mapping possible. Pressing OK leads to FMCKRequire 18518 PMR31252 An MQWF EXE Server address space controlled by WLM was not terminated 18542 Web Client: 'Suspend Instance' year field cannot be left empty 18543 Remove of deadlocks in a scenario with parallel processing of scheduling and cleanup server. Remove of deadlocks in scenarios with high workload and parallel processing of QryWorkItem and Checkout/CheckinWorkitem. 18544 IY40460 FMCEMAIN fails with FMC12250E error in FMCSYS.LOG when for example refresh on a process instance is called by a user who is not authorized. 18545 Use "MQ" instead of "mqmax" as TP_MON_NAME 18546 Unattended (default) configuration is not DB2 V8 enabled 18559 LDAP Bridge, sample command runbr on UNIX, zOS: The parameter handling of this command file was not correct. 18587 IY41141 Allow Cookie ID different from JSESSIONID 18596 HP-UX: Configuration switch for Oracle or MQServer fails 18600 BufferPool not customizable in DB2 part 18608 IBM Java 1.4 RTE is not found by Workflow 18622 Transfer item in Portal Client does not work 18623 Web Client does not work with SupportPac WA82 18639 Error pages are not working correctly in Web Client 18657 Empty directory \bin\JAVA3401 if config Web Client WAS4.x/5.0 18658 IY41977 Queries with multiple GDC tables in order statement 18666 PQ72169 Long and Float constants in "IN" predicate of filter strings in queries 18668 Configuration Win: Registry contains a corrupted path for fmcerr.log\fmcsys.log 4. License Notices ================== This product internally uses the XML4C parser and therefore is obliged to distribute the following license text: --------------------------------------------------------------------- /* * The Apache Software License, Version 1.1 * * * Copyright (c) 1999 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://www.apache.org/)." * Alternately, this acknowledgment may appear in the software itself, * if and wherever such third-party acknowledgments normally appear. * * 4. The names "Xerces" and "Apache Software Foundation" must * not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact apache@apache.org. * * 5. Products derived from this software may not be called "Apache", * nor may "Apache" appear in their name, without prior written * permission of the Apache Software Foundation. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ==================================================================== * * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation and was * originally based on software copyright (c) 1999, International * Business Machines, Inc., http://www.ibm.com. For more * information on the Apache Software Foundation, please see * . */ --------------------------------------------------------------------- ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1995-2001 International Business Machines Corporation and others All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder. ---------------------------------------------------------------------- All trademarks and registered trademarks mentioned herein are the property of their respective owners.