MQSeries Workflow 3.3.0 - Service Pack #2 ----------------------------------------- INDEX ------------------------------------------ 1. Installation of Service Pack #2 1.1 Installation on Microsoft Windows 1.2 Installation on IBM AIX 1.3 Installation on Sun Solaris 1.4 Installation on HP-Unix 2. Important Notices 2.1 Applying service to the Web Client 2.2 WebSphere Application Server 4.0 AE support 2.3 Web Client NLS support 3. Changes 3.1 Changes in Service Pack #1 3.2 Changes in Service Pack #2 ------------------------------------------ 1. Installation of Service Pack #2 =========================================== 1.1 Installing the Service Pack on 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. 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, CORBA Agent component. The Buildtime package includes Buildtime and Samples. Following the list of the self-extracting executables: Full Package: ------------- W330ENA2.EXE - U.S. English language version W330CSA2.EXE - Simplified Chinese language version W330CTA2.EXE - Traditional Chinese language version W330DAA2.EXE - Danish language version W330DEA2.EXE - German language version W330ESA2.EXE - Spanish language version W330FIA2.EXE - Finnish language version W330FRA2.EXE - French language version W330HEA2.EXE - Hebrew language version W330HUA2.EXE - Hungarian language version W330ITA2.EXE - Italian language version W330JPA2.EXE - Japanese language version W330KOA2.EXE - Korean language version W330NLA2.EXE - Dutch language version W330NOA2.EXE - Norwegian language version W330PLA2.EXE - Polish language version W330PBA2.EXE - Brazilian Portuguese language version W330PGA2.EXE - Portuguese language version W330TRA2.EXE - Turkish language version Client Package: --------------- W330ENC2.EXE - U.S. English language version W330CSC2.EXE - Simplified Chinese language version W330CTC2.EXE - Traditional Chinese language version W330DAC2.EXE - Danish language version W330DEC2.EXE - German language version W330ESC2.EXE - Spanish language version W330FIC2.EXE - Finnish language version W330FRC2.EXE - French language version W330HEC2.EXE - Hebrew language version W330HUC2.EXE - Hungarian language version W330ITC2.EXE - Italian language version W330JPC2.EXE - Japanese language version W330KOC2.EXE - Korean language version W330NLC2.EXE - Dutch language version W330NOC2.EXE - Norwegian language version W330PLC2.EXE - Polish language version W330PBC2.EXE - Brazilian Portuguese language version W330PGC2.EXE - Portuguese language version W330TRC2.EXE - Turkish language version Buildtime Package: ----------------- W330ENB2.EXE - U.S. English language version W330CSB2.EXE - Simplified Chinese language version W330CTB2.EXE - Traditional Chinese language version W330DAB2.EXE - Danish language version W330DEB2.EXE - German language version W330ESB2.EXE - Spanish language version W330FIB.EXE - Finnish language version W330FRB2.EXE - French language version W330HEB2.EXE - Hebrew language version W330HUB2.EXE - Hungarian language version W330ITB2.EXE - Italian language version W330JPB2.EXE - Japanese language version W330KOB2.EXE - Korean language version W330NLB2.EXE - Dutch language version W330NOB2.EXE - Norwegian language version W330PLB2.EXE - Polish language version W330PBB2.EXE - Brazilian Portuguese language version W330PGB2.EXE - Portuguese language version W330TRB2.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 As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. Open a DOS Command Prompt and run fmczutil and choose the configuration identifier of the configuration you would like to update. Then choose the 'r'untime database menu and select 'b'ind. Now all bindings will be made for you. This may take several minutes. After these steps your system is ready to run. You may 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 wf330a2u.tar.gz (91 MB) and unpack the file to a temporary subdirectory. You need approximately 235 MB to unpack the file. 1.2.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". 2) As root, perform the command 'slibclean'. 3) Update your MQSeries Workflow 3.3.0.x installation (with or without having hotfixes applied) using smit - "update to latest level" to level 3.3.0.20. 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=2". 4) As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. As user "fmc" invoke fmczutil and choose the configuration identifier of the configuration you would like to update. Then choose the 'r'untime database menu and select 'b'ind. Now all bindings will be made for you. This may take several minutes. After these steps your system is ready to run. You may 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 wf330s2u.tar.gz (31 MB) and unpack the file to a temporary subdirectory. You need approximately 115 MB to unpack the file. 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.0.x files (with or without having hotfixes applied) to level 3.3.0.20: Issue the following command line as user "root", replace the path "/tmp/fmc330u2.pkg" from this example with the fully qualified path and filename of your ".pkg" file: pkgadd -d /tmp/fmc330u2.pkg accept the installation of this package and overwriting files of the previous package 3.3.0.x. 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=2". 3) As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. As user "fmc" invoke fmczutil and choose the configuration identifier of the configuration you would like to update. Then choose the 'r'untime database menu and select 'b'ind. Now all bindings will be made for you. This may take several minutes. After these steps your system is ready to run. You may 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 wf330h2u.tar.gz (43 MB) and unpack the file to a temporary subdirectory. You need approximately 45 MB to unpack the file. 1.4.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.0.x files (with or without having hotfixes applied) to level 3.3.0.20: Use "sam" to install the new package. Use the "software" icon, and select "add software to local host". Then choose installation from disc and enter the fully qualified path to the file "FMC330U2.PKG" and the filename itself. Choose "Install" from the "Actions" pulldown menu and confirm twice. After installation you will be ready to go on 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=2". This value reflects the current service pack level of the installation. 4) As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. As user "fmc" invoke fmczutil and choose the configuration identifier of the configuration you would like to update. Then choose the 'r'untime database menu and select 'b'ind. Now all bindings will be made for you. This may take several minutes. After these steps your system is ready to run. You may 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 Notices =========================================== 2.1 Applying service to the Web Client -------------------------------------- It is recommended to have an own configuration for just the Web Client. This way you can easily apply service to the Web Client: - 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, because the complete subtree of your old Web Client configuration will be deleted in the next step. - Delete the Web Client configuration using fmczutil - Create a Web Client configuration. If you do not change the configuration identifier, it is not necessary to redeploy the Web Client in the WebSphere Application Server. - 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, this temporary directory is \temp\\MQWFClient-, for example, d:\WebSphere\AppServer\temp\default_host\MQWFClient-WEBC. 2.2 WebSphere Application Server 4.0 AE support ----------------------------------------------- With MQSeries Workflow version 3.3 Service Pack 2, it is possible to configure and deploy the Web Client in WebSphere Application Server 4.0 AE. Note: In this Service Pack, the dialog for the WAS 4.0 AE configuration utility is only available in English. It is planned that other languages will be supported in a forthcoming release of MQSeries Workflow. Using the configuration utility fmczutil, you must do the following to configure the Web Client with WAS 4.0 AE: Follow the instructions in the Installation Guide until you are prompted to select an application server. The following describes the special steps for WAS 4.0 AE. The sequence shown here applies to Windows and UNIX platforms. Note: On Windows, make sure that you are using the original command line processor cmd.exe. Using a command line processor like 4NT can cause problems. - Select 'f ... (X) WebSphere 4.0 (EAR)' - Code Version : [3302] Enter the code version of the Java Agent to be used. The default is the latest version. - FMC33607I Specify information about the WebSphere Application Server ...: Installation directory : [D:\WebSphere\AppServer] Enter the directory where WebSphere AppServer is installed - TCP/IP address of administration node : [fmtc503] Enter the hostname (no doted TCP/IP address) of the administration server - TCP/IP address of name service host : [fmtc503] Enter hostname (no doted TCP/IP address) of server where the Naming Service is running - TCP/IP port number of name service : [900] Enter Port used by the naming service - XML configuration skeleton file name : [fmcoh40.skel] For WAS 4.0 the skeleton file must be fmcoh40.skel! - HTTP transport port of the webcontainer:[9081] Enter port number to be used for the communication between WebSphere and the HTTP server. Note: You cannot use the same port for multiple web applications running in parallel! Therefore, use an unused port number. - After you entered the information select create configuration profile c ... Create configuration profile for '' now s ... Save input to file r ... Review/change input x ... Exit (input for configuration '' will be lost) The resulting output looks similar to the following: - FMC33680I The profile for the configuration '' was updated successfully. - FMC33682I The general configuration profile was updated successfully. FMC33938I Creating 'fmcohcli.war'. FMC33938I Creating 'fmcohcli.ear'. - Do you want to configure the Web Client within the WebSphere Application Server now? y ... Yes n ... No Be sure that the administration server of WebSphere AppServer is running before you select yes! You get several lines of output from the WebSphere installation utility. Finally, a message confirms that the configuration ended successfully. - FMC33659I The configuration within the WebSphere Application Server was successful. - FMC33940I Please restart your HTTP server to activate the changes. Be sure to restart your HTTP server to let the changes for the configuration become effective! Note: The WebClient.properties file must now be customized in the /installedApps/MQWFWebClient_.ear\fmcohcli.war directory. Java Server pages and html files for process start and activity implementations must now be put into these directories: /installedApps/MQWFWebClient_.ear\fmcohcli.war\processes and /installedApps/MQWFWebClient_.ear\fmcohcli.war\programs If you use a different application server, which is J2EE 1.2 compliant, choose 'j ... ( ) Other (Servlet 2.2 / J2EE 1.2)' when prompted for your application server. This means that an enterprise archive (.ear) file will be created for the Web Client servlet by the configuration utility. It is located in the /cfgs//WebClient directory and can be used according to the installation instructions of your application server. Note: The only officially supported application server is WebSphere! The other two selection possibilities 'w ... ( ) WebSphere 3.x' and 'o ... ( ) Other' work the same way as with MQWF v3.3 and v3.3SP1. That means that no enterprise archive is created, only the open directory structure is created and used for the application servers. 2.3 Web Client NLS support -------------------------- The Web Client now supports the following languages: English, Czech, French, Japanese. These languages are supported in parallel by the Web Client. The language used in the Web Browser depends on the settings of the Web Browser. For example with Microsoft Internet Explorer, select the 'Tools' drop-down menu, then 'Internet Options...', then 'Languages...'. Here, add one of English[en], Czech[cs], French[fr], Japanese[ja] to the list. The first language matching one of the four supported languages is used to display the messages in this language. With one MQ Workflow installation, different languages can be used in parallel from different Web Browsers as long as these languages use the same code page. Therefore, English and French can be used in parallel, whereas Czech and Japanese cannot be mixed with other languages. If this is done, then errors can occur when typing in national characters and viewing them on a Browser using a language with a different code page. The helps for the Web Client are only available in English. 3. Changes =========================================== 3.1 Changes in Service Pack #1 ------------------------------ The following problems are fixed: Nr. PMR/APAR Desc. 14888 Web Client Work List not found 14996 Logon to Web Client fails after previous logoff 12585 Cleanup server floods the execution server queue 14942 Expiration time is not forwarded to MQ message expiration time. 14948 Pre-condition failure in fmcmproc.cxx 14960 Improve trace performance for AIX 14975 FMCEMAIN abends with SQL code 904 14976 Server Framework dumps when terminating 14978 Migration problem 14985 Access violation in fmccmqfr.dll 14986 L0 trace: Assertions don't contain failure location 15007 Memory leak with dynamic SQL for DB2 15085 Memory leak in MQ layer 14971 fmczinsx -o db2/ora: wrong links in a client only installation 15034 Syntax checker does not allow '-' (dashes) in TCP/IP hostnames 15036 HP-UX language support ja_JP.SJIS configuration incorrect 3.2 Changes in Service Pack #2 ------------------------------ The following problems are fixed: Nr. PMR/APAR Desc. 14872 Web Client cannot delete existing lists 14982 The priority of an activity can be updated via the predefined member ACTIVITY_INFO.PRIORITY. However, this change was not reflected on the corresponding workitems. 14983 Data integrity problem in the area of workitems that only occurs when using an Oracle database and running heavy stress scenarios. 14990 FmcDynPointer::Ensure potentially loops forever 15044 Transfer workitems has wrong default 15049 fmczccd: wrong output, if hostname is longer than 13 chars 15066 Incorrect conversion from local time to UTC (and v.v) in Windows 15073 (AvtiveX) Error in the Container processing. The SetValueDbl() method was in error. 15075 Multithreading problems in web context. Servlet crashes and brings JVM down. 15077 If an API program using the MQ Workflow C++ API tried to retrieve a string container element into non-initialized memory, the GetValue method of the container element could return FMC_OK, without the memory being changed. In this case, the wrong value could be returned. In order to fix this problem, fmcjpcon.inl was changed which makes necessary a recompile of the application using the MQ Workflow C++ API. 15090 Refreshing the list of lists does not work 15092 Problem when using the restart activity API with certain input data. 15097 Problem if the last activity of a block expires and the exit condition of this block fails. 15124 Run-time error 40002 (Abnormal Program Termination) 15125 XML Error Handling: Poisoned message 15128 Oracle: Cleanup Server terminates when DB is filled with many processes. If many processes in the database, and many clients are working with system, the cleanup server gets the error code ORA-1555 and terminates. It starts again, delete the remaining process instances, but gets the error again. The cleanup server does not respond anymore to any shutdown request of the Admin Utility. It must be killed manually. 15139 A deadlock may occur if a program finished message and a suspend process instance message are processed by different execution servers at the same time. 15154 Codepage conversion: support SUN patch 107811-01 15163 Activity Name missing in condition syntax checker messages 15164 Web Client: Change password in user info not possible 15166 Web Client: Duplicate data on user information / substitution and authorization page 15168 WebClient (French Version): User Information doesn't work 15171 Converter ignores the current locale setting. 15172 If roles had been specified 'from container', then during notification, the coordinator of this role was not notified as it should be. 15181 (ActiveX) Error in the ExecutionService processing: The SetSessionContext() method was in error. 15182 Web Client: Wrong icon for finished/terminated workitem. 15185 Web Client: Finished workitem / finished instance cannot be deleted. 15190 Web Client: Disabled workitem shows wrong state icon. 15192 Runtime error 40009 -> Buildtime goes away... 15231 IY20420 Run-time error 438 15235 fmczchk should check db profile for variable RR_TO_RS 15248 Configuration does not allow DB2 parallel processing 15252 Incorrect display of Czech characters in WebClient 15277 18878,519 No server shut down when audit queue not defined 15293 No message if audit trail cannot be put to audit trail queue 15318 For some user defined program execution server, the system and system group had to be specified when referencing it in an activity. This is no longer necessary. Instead, the name is resolved at execution time. 15328 When retrieving the container content RC=112 and RC=113 is sometimes returned on AIX with DB2 V7 fixpack 2 , even if the correct container schema is used. 15349 Assertion during Server Shutdown 15350 ORACLE: A worklist using a filter with an variable like (OWNER=CURRENT_USER) causes the Execution Server to trap. 15355 IY22319 Runtime Client: Problem entering data to DBCS data structure members 15359 RTC sorts not the same as the server 15464 Wrong default XML skeleton file for WebSphere in configuration utility 15484 XML Release 2 support for WF/390 15545 68741,033 Multithreading Problems in web environment: Running the Web client in Websphere on Solaris causes core dumps and servlet restarts due to invariant-assertions in FmcBinary JavaAgentGCErr The distributed garbage collector of the Java Agent sometimes uses 100% CPU time