IBM Support

Interpreting the result of WebSphere Business Monitor profile creation or augmentation

Troubleshooting


Problem

How do I determine whether a result other than INSTCONFSUCCESS at the end of a WebSphere Business Monitor installation (with profile creation) or a profile augmentation with WebSphere Business Monitor is fatal or benign?

Resolving The Problem

When a new installation of WebSphere Business Monitor (with the option to create a new Monitor profile specified) or augmentation of an existing profile with WebSphere Business Monitor is completed, a result code of INSTCONFSUCCESS, INSTCONFPARTIALSUCCESS, or INSTCONFFAILED will be reported.

Profile creation and augmentation is performed by execution of a series of actions implemented as ANT (filename *.ant) scripts, with the exact set of actions dependent upon the type of profile (custom, deployment manager, or stand-alone) that is being created or augmented. The tables below, for Versions 6.2 and 7.0 of WebSphere Business Monitor, list the possible actions, and for each type of profile, whether a failure in that action is considered fatal or not. Here is how to interpret the tables:

  • A value of Y indicates that a failure in the action for that type of profile is considered fatal, resulting in immediate failure of the profile creation/augmentation.
  • A value of N indicates that a failure in the action for that type of profile is considered benign, resulting in profile creation/augmentation returning a result of INSTCONFPARTIALSUCCESS (if no subsequent action with a value of Y fails).
  • A value of n/a indicates that the action is not executed for that type of profile.


WebSphere Business Monitor Version 7.0

Action
Custom profile
Deployment manager profile
Standalone profile
presetVariables.ant
Y
Y
Y
stopNode.ant
N
n/a
n/a
addNodeMetadata.ant
Y
Y
n/a
clearOSGICaches.ant
n/a
n/a
N
installWBMWCCM.ant
Y
Y
Y
augmentBusinessSpace.ant
n/a
N
Y
addBSpaceMetadata.ant
Y
N
N
addServerPerms.ant
N
n/a
N
startNode.ant
N
n/a
n/a
configFirstStepsWBMManaged.ant
N
n/a
n/a
configFirstStepsWBMDmgr.ant
n/a
N
n/a
launchWsAdminListener.ant
Y
Y
Y
createWBMTemplate.ant
N
N
N
addDefaultWBMVar.ant
N
n/a
n/a
databaseInstall.ant
n/a
N
N
stopWsAdminListener.ant
Y
Y
Y
configCEI.ant
n/a
n/a
N
addNodeMetadata.ant
n/a
n/a
Y
monitorServerResourceInstall.ant
n/a
Y
Y
createMonitorScheduler.ant
n/a
N
N
createModeratorWorkManagers.ant
n/a
N
N
installBSpace.ant
n/a
n/a
Y
configBSpace.ant
n/a
n/a
N
configWBMSIB.ant
n/a
n/a
Y
enableIdentityAssertion.ant
n/a
n/a
N
installActionManager.ant
n/a
N
N
installDMSService.ant
n/a
N
N
installMSSService.ant
n/a
n/a
N
configWebDashboard.ant
n/a
n/a
N
installMobileDashboard.ant
n/a
n/a
N
addBPMMetadata.ant
N
N
N
augmentBPMFeature.ant
n/a
N
N
installEmitterRestServices.ant
n/a
n/a
N
installVmmService.ant
n/a
N
N
installCbebrowser.ant
n/a
N
N
installDebugger.ant
n/a
n/a
N
installWBMISCPortlet.ant
n/a
N
N
configureRESTGatewayServices.ant
n/a
n/a
Y
registerRESTServiceEndpoints.ant
n/a
n/a
Y
iscRestore.ant
n/a
N
N
csiEnableIdentityAssertion.ant
n/a
N
n/a
configFirstStepsWBMDefault.ant
n/a
n/a
N
deployABXservice.ant
n/a
n/a
Y
addABXpermissions.ant
N
N
N
startServer.ant
n/a
n/a
N
configRESTSecurity.ant
n/a
n/a
N
configEventsRecord.ant
n/a
n/a
N
installHumanTask.ant
n/a
n/a
N
installGlobalProcessTask.ant
n/a
n/a
N
stopServer.ant
n/a
n/a
N
prepareShowcaseSample.ant
n/a
n/a
N
WBMShowcaseInstall.ant
n/a
n/a
N
removeValues.ant
N
N
N
createProfileShortCut2StartMenuDefaultWBMServer.ant
n/a
n/a
N
createProfileShortCut2StartMenuABXWBMServer.ant
n/a
n/a
N
createProfileShortCut2StartMenuManagedWBMServer.ant
N
n/a
n/a
createProfileShortCut2StartMenuDmgrWBMServer.ant
n/a
N
n/a
moveWBMAugmentLog.ant
N
N
N
aboutThisProfile.ant
N
N
N



WebSphere Business Monitor Version 6.2

Action
Custom profile
Deployment manager profile
Standalone profile
presetVariables.ant
Y
Y
Y
stopNode.ant
N
n/a
n/a
addNodeMetadata.ant
Y
Y
n/a
clearOSGICaches.ant
n/a
n/a
N
installWBMWCCM.ant
Y
Y
Y
augmentBusinessSpace.ant
n/a
N
Y
addBSpaceMetadata.ant
Y
N
N
addServerPerms.ant
N
n/a
N
startNode.ant
N
n/a
n/a
configFirstStepsWBMManaged.ant
N
n/a
n/a
configFirstStepsWBMDmgr.ant
n/a
N
n/a
launchWsAdminListener.ant
Y
Y
Y
createWBMTemplate.ant
N
N
N
addDefaultWBMVar.ant
N
n/a
n/a
databaseInstall.ant
n/a
N
N
stopWsAdminListener.ant
Y
Y
Y
configCEI.ant
n/a
n/a
N
addNodeMetadata.ant
n/a
n/a
Y
monitorServerResourceInstall.ant
n/a
Y
Y
createMonitorScheduler.ant
n/a
N
N
createModeratorWorkManagers.ant
n/a
N
N
installBSpace.ant
n/a
n/a
Y
configBSpace.ant
n/a
n/a
N
configWBMSIB.ant
n/a
n/a
Y
enableIdentityAssertion.ant
n/a
n/a
N
installActionManager.ant
n/a
N
N
installDMSService.ant
n/a
N
N
installMSSService.ant
n/a
n/a
N
configWebDashboard.ant
n/a
n/a
N
installMobileDashboard.ant
n/a
n/a
N
addBPMMetadata.ant
N
N
N
augmentBPMFeature.ant
n/a
N
N
installEmitterRestServices.ant
n/a
n/a
N
installVmmService.ant
n/a
N
N
installCbebrowser.ant
n/a
N
N
installDebugger.ant
n/a
n/a
N
installWBMISCPortlet.ant
n/a
N
N
configureRESTGatewayServices.ant
n/a
n/a
Y
registerRESTServiceEndpoints.ant
n/a
n/a
Y
iscRestore.ant
n/a
N
N
csiEnableIdentityAssertion.ant
n/a
N
n/a
configFirstStepsWBMDefault.ant
n/a
n/a
N
deployABXservice.ant
n/a
n/a
Y
addABXpermissions.ant
N
N
N
startServer.ant
n/a
n/a
N
configRESTSecurity.ant
n/a
n/a
N
configEventsRecord.ant
n/a
n/a
N
installHumanTask.ant
n/a
n/a
N
installGlobalProcessTask.ant
n/a
n/a
N
stopServer.ant
n/a
n/a
N
prepareShowcaseSample.ant
n/a
n/a
N
WBMShowcaseInstall.ant
n/a
n/a
N
removeValues.ant
n/a
N
N
createProfileShortCut2StartMenuDefaultWBMServer.ant
n/a
n/a
N
createProfileShortCut2StartMenuABXWBMServer.ant
n/a
n/a
N
createProfileShortCut2StartMenuManagedWBMServer.ant
N
n/a
n/a
createProfileShortCut2StartMenuDmgrWBMServer.ant
n/a
N
n/a
moveWBMAugmentLog.ant
N
N
N


Troubleshooting a fatal error
  1. Open the file <WAS_HOME>/logs/manageprofiles/<PROFILE_NAME>_create.log and search for the first occurrence of the word "fatal". Above the line containing that word, find the name of the ANT script (*.ant) for which failure was reported.
  2. In the directory <WAS_HOME>/logs/manageprofiles/<PROFILE_NAME>, open the file with the name "wbm.<action>.log" where <action> is the name of the script file (*.ant) found in step 1.
  3. Search for the error that was reported when the action failed. The file "wbm.<action>.wsadmin.traceout.log" (also in <WAS_HOME>/logs/manageprofiles/<PROFILE_NAME>) may have additional details.
  4. If the error can be corrected, correct the error and then uninstall and reinstall WebSphere Business Monitor (if this was an installation failure) or unaugment and reaugment the profile (if this was a profile augmentation failure). If the error cannot be corrected, please contact IBM support.

[{"Product":{"code":"SSSRR3","label":"WebSphere Business Monitor"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"7.0;6.2.0.2;6.2.0.1;6.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 June 2018

UID

swg21415428

Page Feedback