JR55353: CUSTOMER IS UNABLE TO START THE MESSAGE ENGINE SERVER ON A NEW DEPLOYED BPM 7512 ENVIRONMENT.

bpm.8570.cf2016.06.delta.repository.1of2
bpm.8570.cf2016.06.delta.repository.2of2

APAR status

• Closed as program error.

Error description

• During startup messages are shown in the logs.
  
  [1/28/16 17:22:26:363 CET] 00000013 WSDefaultPrin W
  SECJ4062W: Cannot
  find the credential information.
  [1/28/16 17:22:26:364 CET] 00000014 WSDefaultPrin W
  SECJ4062W: Cannot
  find the credential information.
  [1/28/16 17:22:26:369 CET] 00000013 PrivExAction  E
  J2CA0044E: The
  Connection Manager failed to get a Subject from the security
  service
  associated with ConnectionFactory
  jdbc/com.ibm.ws.sib/twprocsvr_bus.
  Received exception javax.security.auth.login.LoginException:
  Incorrect authDataEntry and alias is:
  PROCSVRME_MessagingCluster_Auth_Alias
  

Local fix

• Problem can be circumvented by editing sib-engines.xml.
  Check in Websphere ISC the names of the authentication aliases
  configured in the system. Then check if those are matching the
  listed authentication aliases. There might be differences like
  listed below
  
  PERFDWME_bpme.Messaging_Auth_Alias
  PROCSVRME_bpme.MessagingCluster_Auth_Alias
  
  compared to
  
  PERFDWME_Messaging_Auth_Alias and
  PROCSVRME_MessagingCluster_Auth_Alias
  
  Changing the name of the Auth aliases fixes the issue.
  

Problem summary

• When you create an IBM Business Process Manager (BPM) deployment
   environment (DE) by using the IBM BPM DE wizard in the
  administrative console and modifying the name of the cluster
  that hosts the messaging infrastructure, the messaging engine
  configuration still points to the authentication data alias
  based on the default messaging cluster name, which does not
  exist. As a result, you see server startup errors.
  

Problem conclusion

• An interim fix for IBM BPM V7.5.1.2 is available that ensures
  the messaging engine authentication alias name is configured
  consistently, based on the actual messaging cluster name.
  
  PRODUCTS AFFECTED
  IBM BPM Advanced
  IBM BPM Standard
  IBM BPM Express
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels