Fix (APAR): IZ77855 Status: Fix Product: WBI Release: 6.2.0.3 Operating System: All operating systems Supersedes Fixes: Pre-requisite Fixes: Exclusive-requisite Fixes: CMVC Defect: IZ77855 Byte size of APAR: 31907 Date: 2010-06-23 Abstract: bpeconfig.jacl doesn't set the schema qualifier for the WebSphere scheduler it creates. Description/symptom of problem: When using the bpeconfig.jacl script to configure Business Process Choreographer, and specifying a non-empty value for the database schema name, this schema name will not be set for the WebSphere scheduler configuration that is created for Business Process Choreographer. This results in the following exception in SystemOut.log when starting the server: [6/21/10 16:04:57:520 CEST] 0000001c ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "createScheduledItem" on bean "BeanId(TaskContainer_fmtc7090Node01_Servlets_Server01#taskejb.jar#TaskServiceManagerBean, null)". Exception data: com.ibm.task.core.SchedulerError: CWTKE0001E: An error occurred when setting up the scheduler. com.ibm.websphere.scheduler.SchedulerNotAvailableException: SCHD0124E: Unable to initialize TaskStore due to error: SCHD0046E: The table SCHED_TREG in datasource jdbc/BPEDB used by scheduler resource BPEScheduler (BPEScheduler) is missing or is not accessible. at com.ibm.ws.scheduler.SchedulerImpl.initialize(SchedulerImpl.java:411) at com.ibm.ws.scheduler.SchedulerImpl.access$100(SchedulerImpl.java:171) at com.ibm.ws.scheduler.SchedulerImpl$1.run(SchedulerImpl.java:621) at java.security.AccessController.doPrivileged(AccessController.java:241) at com.ibm.ws.scheduler.SchedulerImpl.updateOrCreate(SchedulerImpl.java:604) at com.ibm.ws.scheduler.SchedulerImpl.create(SchedulerImpl.java:565) Apply this interim fix before using bpeconfig.jacl to configure Busines Process Choreograhper or Business Process Archive Manager. If you already have Business Process Choreographer configured follow these steps to fix up the configuration: 1. In the admin console, go to Resources > JDBC > Business Integration Data Sources. 2. Locate the data source with JNDI Name "jdbc/BPEDB" on the appropriate scope and note the value in the "Schema" column. 3. In the admin console, go to Resources > Schedulers 4. Select the scheduler named "BPEScheduler" on the appropriate scope. 5. Change the "Table prefix" attribute to ".SCHED_" where is the schema name noted in step 2. 6. Save your changes and in a network deployment environment synchronize the configuration changes with the managed nodes. 7. Re-start the application server or cluster members where Business Process Choreographer is configured. NOTE: Update installer version 7.0.0.1 or later is required to install this interim fix. NOTE: This interim fix is applicable to a full WPS installation only, and should not be applied to 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: