IBM Support

A registry initialization error occurs after migrating to IBM Business Process Manager (BPM) Advanced for z/OS V8.0.1

Troubleshooting


Problem

After you migrate an IBM Business Process Manager Advanced for z/OS Network Deployment cell from Version 7.5.x to 8.0.1 and start the migrated servers, the registry might fail to initialize.

Symptom

The startup log for a migrated server shows a severe error message of the following type:

   ThreadId: 00000007
   FunctionName: WLE.wle
   SourceId: WLE.wle
   Category: SEVERE
   ExtendedMessage: CWLLG2035E:  The registry was not initialized.   Error:  org.springframework.beans.factory.BeanCreationException:
  Error creating bean with name 'ejbCore.PersistenceServicesCore' defined in class path resource [registry.xml]: Cannot create inner bean  com.lombardisoftware.server.NotifyCacheUpdateManager#4b8a83a2'

Cause

This error occurs if the IBM_JAVA_OPTIONS parameter named -Dteamworks.server.home, which is in the variables.xml file for the deployment manager profile, is set to the migration source directory.

Resolving The Problem

To resolve the problem, complete the following steps:

  1. For each of the servers in the cluster, edit the cell_dir/nodes/node_name/servers/server_name/variables.xml file under the deployment manager profile. Replace all instances of the WAS_HOME migration source directory with the WAS_HOME migration target directory.

  2. Locate the IBM_JAVA_OPTIONS area in the variables.xml file and ensure that the -Dteamworks.server.home parameter is set to the migration target file system directory.

  3. Synchronize the cell and then restart the cluster.

[{"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Migration","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21619826

Page Feedback