Fix (APAR): IZ25593 Status: Fix Product: WBI Release: 6.1.2.0 Operating System: All operating systems Supersedes Fixes: Pre-requisite Fixes: Exclusive-requisite Fixes: CMVC Defect: IZ25593 Byte size of APAR: 4056499 Date: 2008-08-05 Abstract: HTM_PredefinedTaskMsg_V612_xxxx and HTM_PredefinedTasks_V612_xxxx applications fail to start when the BPEDB database is located on a System i machine. Description/symptom of problem: When a WBI 6.1.2 process server configured with BFM/HTM containers is started, the HTM_PredefinedTaskMsg_V612_xxxx and HTM_PredefinedTasks_V612_xxxx applications fail to start. The SystemOut.log shows the following exceptions: ContainerImpl E WSVR0501E: Error creating component null [class com.ibm.ws.runtime.component.ApplicationServerImpl] com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.RuntimeWarning: could not start application HTM_PredefinedTaskMsg_V612_xxxx because of filter com.ibm.task.mbean.HumanTaskManager@38663866 at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplications(ApplicationMgrImpl.java:823) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:564) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:977) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:673) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:191) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:977) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:673) Problem summary This problem occurs if the BPEDB schema or database is located on IBM i. The WBI 6.1.2 process server may either be running locally on the same IBM i machine, remotely on IBM i, or remotely on another multiplatform machine. The startup of the two applications containing the predefined tasks fails because the deployment of the task templates fails. The task templates are deployed when the application is started for the first time. The task templates come with predefined NLS message strings that represent typical activities of business users. These strings are written into the BPEDB schema at application startup and are available in all supported languages including those that require a multibyte representation in UTF-8. The IBM i BPEDB schema was defined with a single byte CCSID assigned by the IBM i job attributes which cannot store multibyte national characters. A database conversion or SQL truncation exception then occurs internally and causes the deployment to terminate and the application startup to fail. Substitution characters may be inserted into the BPEDB tables for characters that could not be converted thereby corrupting the original strings. Problem conclusion This iFix should be applied before the BFM/HTM containers are configured and started the first time or before the createSchema.sql is invoked to generate the BPEDB schema on IBM i. The BPEDB schema will then be defined correctly to support unicode data and all NLS strings before any application data is inserted into the BPEDB schema. This will prevent possible data loss or truncation when the schema is later upgraded or if the table columns need to be manually tagged with UTF-8 (CCSID 1208) to correct this problem after the BPEDB schema has been in production. Records may be truncated when table columns are tagged later with UTF-8 since an NLS character requiring a single byte may now require multiple bytes. NOTE: For manual schema upgrade instructions to update existing BEPDB database tables with UTF-8 support see Technte at http://www-1.ibm.com/support/docview.wss?rs=2307&uid=swg21312699. iFix IZ25593 must be applied before doing the manual schema upgrade instructions. NOTE: This iFix must be applied immediately to prevent possible data loss or truncation after the BPEDB schema has been in production or when the schema is later upgraded for a new release. NOTE: This interim fix is applicable to both a full WPS installation as well as a WPS client installation. Directions to apply fix: 1) Copy pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix. 4) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Additional Information: