BPMManageApplications troubleshooting

This command disables or enables the automatic starting of applications and schedulers. If you see an exception when you run this command, you can diagnose the problem by changing the log level to FINEST and running the command again.

Change the log level to FINEST as described in "Troubleshooting migration." After you run the command again, check the log file named BPMManageApplications_timestamp.log. If you cannot find the cause of the problem, you can provide the log to IBM support.
  • If you use the remote migration utility to run the command in the source environment, the log file is in remote_migration_utility/logs/migration.
  • Otherwise, the log file is in install_root/logs/migration in the target environment.
To check that the BPMManageApplications command was successful, perform the following actions:
  • To see the status of your WebSphere® Application Server applications, open the administrative console and go to Applications > Application types > WebSphere enterprise applications.
  • To see the status of the schedulers, go to the server log for the application cluster. You can find the log under the profile path of any custom node, in node_profile/logs/app_cluster_member/SystemOut.log. Check for a message in the log similar to the following message:
    [6/27/13 12:13:03:311 CST] 0000008b SchedulerDaem I   SCHD0038I: The Scheduler Daemon for instance BPEScheduler has started.
    This message provides the status for the scheduler daemon for the instance named BPEScheduler. If you do not see such a message, the scheduler is not started.