JR46477: BPMCONFIGUREPROCESSSERVER FAILED FOR WBI-TOPOLOGIES.XML NOT CORRECT WHEN THE SOURCE CLUSTER IS CONFIGURED USING COMMAND

Download Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• when you take migration from WPS to BPM, and the source
  clustered envrionment was created with manual steps instead of
  Deployment Environment, in step 14
  of following guidance,
  http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0m1/index.jsp?topi
  c=%2Fcom.ibm.wbpm.imuc.doc%2Ftopics%2Ftmig_vtv_ndfull.html
  
  while running BPMConfigureProcessServer.sh, below error may be
  thrown.
  
  [13-4-11 ??05?41?10?] MigrationLogger                S log
  CWMCO0929E Get cluster information failed because cannot parse
  the
  topology XML file.
  CWMCO0929E Get cluster information failed because cannot parse
  the
  topology XML file.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Business Process Manager v8.0.1             *
  ****************************************************************
  * PROBLEM DESCRIPTION: BPMConfigureProcessServer.sh fails      *
  *                      while parsing wbi-topologies.xml when   *
  *                      source cluster configured manually      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  when you take migration from WPS to BPM, and the source
  clustered envrionment was created with manual steps instead of
  Deployment Environment, 'annot parse the topology XML
  file' may been throwns while running
  BPMConfigureProcessServer.sh
  The problem is caused by the parsing code not
  accounting for different format topology.xml when deployment
  environment configured manually.
  

Problem conclusion

• The provided fix will parse the topology xml file correctly.
  
  Install/Dependency information is available in the readme.txt
  on FixCentral. When the user goes to the download files page
  in FixCentral, the readme will be available with the fix
  package as a separate download.
  

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