JR43554: DB SCHEMA AND USER FOR ME ARE DIFFERENT FROM DBDESIGN FILE WHILE CREATING STAND-ALONE PROFILE WITH ORACLE

Version 8.0 Refresh Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When create BPM V8 adv stand-alone PC profile with DbDesign
  file (Oracle), firstly you created DbDesign file, then run
  these script to configure the Oracle DB tables.
  Then you created a profile with this DbDesign file. But
  after creating the profile successfully (no error in
  createprofile log), ME (SCA SYS ME, CEI ME, SCA APP ME, BPC ME)
  can not be started because the DB schema/user id of these ME are
  not same as defined in DbDesign file.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  BPM 8.0 User                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB SCHEMA AND USER FOR ME ARE           *
  *                      DIFFERENT FROM DBDESIGN FILE            *
  *                      WHILECREATING STAND-ALONE PROFILE       *
  *                      WITH ORACLE                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When create BPM V8 adv stand-alone PC profile with DbDesign
  file (Oracle), after created a profile with this DbDesign
  file successfully, ME DB(SCA SYS ME, CEI ME, SCA APP ME, BPC
  ME) can not be started because the DB schema/user id of these
  ME arenot same as defined in DbDesign file.  This Ifix provide
  update to sib-engines.xml to fix the schema/user id issue.
  

Problem conclusion

• It is pragmatic fix that user need to set the password the
  same as it is specified in dbDesign file for the corresponding
  schemaNames if they are set and if dbType=ORACLE. It requires
  that for this scenario the 3 ME "Password" parameters are
  additionally specified on the command line in the response
  file (i.e., duplicated from the dbDesign file):
  For manageprofile, you can execute like this:
  manageprofiles ... -bpmdbDesign bpm.advanced.standalone.dbDesign
  -dbSysMePassword CMNSS00p -dbAppMePassword CMNSA00p
  -dbCeiMePassword CMNCM00p ...
  
  When using PMT you have to go to the admin console and update
  the three ME auth data aliases with the desired password after
  creating the profiles.
  

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

• R800 PSY

     UP