Hotfix Package #2 for MQSeries Workflow Version 3.2.0 ----------------------------------------------------- Installation information: The Hotfix Package #2 consists of one package for all components, one for the client on Windows NT and one package for the buildtime. The installation procedure is depending on the installation environment. It is strongly recommended to upgrade the server first and then all clients. Windows NT ---------- wf320nau.exe contains the fixed code for the all components. wf320nbu.exe contains the fixed code for the buildtime installation wf320ncu.exe contains the fixed code for the client installation. wf320upd.txt is the readme file describing the installation and the problems fixed. This text file is part of the compressed package. OS/2 ---- wf320oau.exe contains the fixed code for all components. wf320upd.txt is the readme file describing the installation and the problems fixed. This text file is part of the compressed package. Java support ------------ Distributed client/server solutions which are based on RMI or CORBA, as the Java CORBA Agent and Java API Beans are, have some inherent requirements regarding the code level on the client (API Beans) and the server (Java CORBA Agent). Namely, the code level on the client and on the server MUST match, otherwise the client cannot work with the objects on the server (objects are marshalled and de-marshalled when they are transfered over the wire). So if the hotfix is installed on the agent and your solution uses fmcojapi.jar on the client side, all your clients must be updated. If you're using local bindings, e.g. in a web server / servlet solution, or as a Java application, then only fmcojagt.jar bas to be updated. Please be aware of the implications this may cause. For this kind of update no changes to any existing configurations are required, nor to create any new configuration. On AIX, there was a bug in the configuration utility that caused the profile not to be updated correctly when configuring a Java agent. The symptom of this is a java.lang.NullPointerException when starting the Java agent. To fix this, you have to update the profile manually. When using RMI, run fmczchk -c inst:m,Agent.Locator,RMI_LOCATOR When using IIOP, replace RMI_LOCATOR with OSA_LOCATOR, COS_LOCATOR, or IOR_LOCATOR as appropriate. After that, run fmczchk again without command line parameters and check the resulting fmczchk.log file to see if the profile has been correctly updated. Installation on WinNT and OS/2 -- Server machine ------------------------------------------------ 1. Back-up your existing installation (recommendation). 2. Stop all running MQSeries Workflow processes (including the listener and trigger monitor). The FMCQM queue manager can remain running. 3. Unpack the file WF320ysu.exe (y = n for Windows NT, y = o for OS/2) with the following syntax: wf320ysu /D x:\path (where x:\path is a temporary directory to which the files are unpacked) 4. Copy the files from the temporary directory to the directory in which the product has been installed. Use XCOPY to perform this task: cd x:\path (where x:\path is your temporary directory) xcopy *.* y:\product-path /s (where y:\product-path is the directory of the product, i.e. d:\fmcwinnt) 5. Issue the command: fmczrdb -o:b to bind the changed packages. Installation on Windows NT, Windows 95, and OS/2 client machines ---------------------------------------------------------------- 1. Back-up your existing installation (recommendation). 2. Unpack the file WF320ycu.exe (y = n for Windows NT, y = o for OS/2) with the following syntax: wf320ycu /D x:\path (where x:\path is a temporary directory to which the files are unpacked) 3. Copy the files from the temporary directory to the directory in which the product has been installed. Use XCOPY to perform this task: cd x:\path (where x:\path is your temporarydirectory) xcopy *.* y:\product-path /s (where y:\product-path is the directory of the product, i.e. d:\fmcwinnt) AIX: ---- wf320upd.txt is the readme file describing the installation and the problems fixed. wf320aau.tar.gz contains the fixed code. fmchotfix is a shell script, which can be used to install the Hotfix Package #2. You need to be root to install this package. All running MQSeries Workflow processes should have been stopped. You need temporarily about 250 MB in the current file system. "gzip" has to be installed. Parameter: 1) Input file to be unpacked (must be wf320aau.tar.gz) 2) (optional parameter) Existing backup directory, where the original files can be copied into Note: You need about 250 MB free space in the backup directory Example: fmchotfix wf320aau.tar.gz /tmp/WF320backup After having updated the server, you must run the bind process with the user-id fmc using the command: fmczrdb -o:b List of fixed problems: ----------------------- 1. Buildtime: Apply does not work correctly for new process Platform: WinNT, Win95 2. Runtime Client: Filters cannot be set If you create a new worklist and set the following filter: OWNER = QXGC3GC and STATE NOT IN Disabled and click OK to create the worklist, the worklist gets created correctly. If you then want to change the filter, you select Settings... from the worklist context menu. This displays the Worklist properties dialog, where you click on the Filter tab. After doing so, you click on the Add button to add another criteria and select NAME = MY ACTIVITY. You click on OK and then when you click OK on the Worklist properties dialog, the following message appears: fmcn6lpd (in the title bar), Invalid filter string, expected 'FE 0; FE 1; FE 2' and found 'STATE'. The only option is to click OK and when you do that, you lose all filter criteria. Platform: WinNT, Win95 3. Execution server: User can delete last ready workitem in case it was restarted. Platform: independent of platform 4. Import: Assertion when importing SESSION_EXPIRATION_TIME FOREVER When importing a DOMAIN entity and using processing option UPDATE the attributes SESSION SESSION_EXPIRATION_TIME FOREVER // TimePeriod import fails. This attribute can now be updated and replaced. 5. Buildtime: Mapping Problems This hotfix removes a couple of problems related to data mappings in Buildtime. Platform: WinNT, Win95 6. Java: java.lang.IllegalAccessError This is a workaround for a bug in the Microsoft JVM where nested classes cannot access protected members of enclosing classes when the source files were compiled using javac's '-O' flag. Platform: WinNT, Win95 7. Runtime Database: Internal database layer IMPORTANT: If you have migrated your runtime database from MQseries Workflow 3.1.2 you must apply this hotfix. It applies a fix to the internal database access layer. Platform: independent of platform 8. Cleanup Server: KEEP_WORKITEMS and KEEP_PROCESSES not honoured. KEEP_WORKITEMS and KEEP_PROCESSES will be honoured by the cleanup server not only when specified on process level, but also when specified on domain, system group or system level. Platform: independent of platform 9. Java: JNI traps when API is being used from within VisualAge for Java Platform: independent of platform 10. Cleanup server: Assertion failure fmcecosa.cxx line 2535 This problem ocurred when the cleanup server collected workitems with the state 'deleted/finished/forceFinished' for deletion. This problem is now removed. Platform: independent of platform 11. Buildtime: Workitem authorization is lost Changing the workitem authorizations of a person could have an incorrrect impact on the authorizations of other persons. Platform: WinNT, Win95 12. Communication Layer - Server: Automatic activity not started Due to concurrent processes accessing the same data container, automatic activities inside those processes seemed to 'hang' in 'ready' state. These automatic activities now will execute. Platform: independent of platform 13. Import: Assertion failed in e:\v321\src\fmcixlat.cxx(5537) Platform: independent of platform 14. Runtime client: Notifications - Delete not shown in context menu Deleting Notifications from the context menu has been made possible. Platform: WinNT, Win95 15. Runtime Client: Transfer not enabled for terminated workitem In order to reactivate running work items, a user can transfer them now to an administration user who is able to restart the work item. Platform: WinNT, Win95 16. PEA does not automatically reconnect after a broken connection. The program execution agents did not reconnect to the system after a broken connection. A broken connection will now be transparent to the users, because the program execution agents reconnect automatically after a connection breakdown. Platform: independent of platform 17. All servers: Setting message size to unlimited caused the servers to fail Using the checkbox 'unlimited message size' in the Buildtime and importing the settings into the runtime database caused the servers to fail. Platform: independent of platform 18. Execution Server: Failure with states finished/finished A subprocess whose end activity finished while the subprocess was in suspending state could not be successfully resumed. Platform: independent of platform 19. Runtime client: Deletion of process notification failed Platform: WinNT, Win95 20. NOTIFICATION TO xxx AFTER TAKEN_FROM yyy not honoured Platform: independent of platform 21. Verify rejects mappings that should be OK Platform: independent of platform 22. RT import abends by dll_load_mode unlimited RT import abends by the following statement in the fdl: PROGRAM_EXECUTION_AGENT DLL_LOAD_MODE UNLIMITED Platform: independent of platform 23. PEA on different system not addressed. The customer is executing a process on System1, and tries to invoke a program via a PEA connected to System2. However, the InvokeProgram message is put erroneously into the PEA-Input-Queue of System1. Platform: independent of platform 24. Remove type "ErrorNotification" in filter/sort dialogs Platform: WinNT, Win95 25. No error message if refresh of a list fails Platform: WinNT, Win95 26. PMR20130: PEA consumes too much CPU on AIX The symptom is that 10 PEAs on midrange AIX system cause the system to virtually hang. Platform: AIX