JR42314: SRVC - SAVE THE BOOTSTRAPPROCESSSERVERDATA.LOG FIlE UNDER /X/<PROFILE>/LOGS DIRECTORY

Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• bootstrapProcessServerData when exec from command line , the
  output is sent to the stdout and  does not get saved.
  
  We are  not able to get the orginal file from custoemr and have
  to request custoemr to rerun the command again with redirect >
  to a text file and send the file again.  the symptom may change
  when run the second time and als this is delay in resolving the
  customer problems.
  
  Request :
  1. Disaply the output on the command line as well as save the
  file
  under <porfile>/logs . Saving the file under <porfile>/logs help
  get all the files at the same time and reduce time to resolve
  the customer problem.
  
  
  2. Also not that when the Bootstratdata.ant is run during the
  porfilecreation get saved as XML file under
  <install>/logs/manageprofiles/profile_create.log
  
  The excaption are not readable where each line of the
  exception stack is between the XML tags !!
  
  Best to create a separate log for bootstrap task and save the
  Bootstrap log independently under followign directory.
  <install>/logs/manageprofiles/<ProfileName>/bootstrapdata.log
  
  -------
  
  If is easier to chose the same location  for both 1.command line
  and 2. during profile creation , it should be ok.  It may not be
  intuitive to customers and support team but as long as you can
  print the location of the log, we shoudl be able to find it.
  

Local fix

• n/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM Business Process Manager v7.5.1     *
  *                  users.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The bootstrapProcessServerData          *
  *                      results are not logged.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the bootstrapProcessServerData operation is run separate
  from profile creation, the results are only written to the
  console and there is no log of the execution.  If
  bootstrapProcessServerData is executed during profile
  creation, the output is directed to the profile creation log
  and is difficult to read.
  

Problem conclusion

• This iFix will direct the output for the
  bootstrapProcessServerData
  command to be saved to user.install.root/logs/ directory
  regardless if run as part of profile creation or as a separate
  command.   The command output will be in a file of the name of
  bootstrapProcessServerData.<cluster name>.<timestamp>.log,
  bootstrapProcessServerData.<node name>.<server
  name>.<timestamp>.log or
  bootstrapProcessServerData.<timestamp>.log depending on which
  target was specified for the command. A subset of the output
  will also be displayed to the console.
  

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 STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R750 PSY

     UP