Troubleshooting
Problem
Changes in V8.5 of Operational Decision Manager necessitate changes to the command lines that are present in the documentation that concerns the silent mode.
Symptom
Step three under "Installing Operational Decision Manager silently" refers to the wxssetup.response file that no longer exists in version 8.5.
Step eight under "Setting the response file for required software" refers to the wxssetup.response file that no longer exists in version 8.5.
Step six under "Setting the response file for required software" refers to an incorrect variable !WAS_SDK_FEATURE_BIT_32_OR_64!
Resolving The Problem
Step three under "Installing Operational Decision Manager silently" now refers to existing commands. For Windows, the command is imcl.exe input <path_to_response_file>\WXS_Silent.xml -acceptLicense. For Linux, the command is ./imcl input <path_to_response_file>/WXS_Silent.xml -acceptLicense.
Step eight under "Setting the response file for required software" now refers to WXS_Silent.xml in the response files directory. You must edit the WXS_Silent.xml file to set the !WXS_PROFILE_ID! found in id='com.ibm.websphere.WXS.was8.v86' version='8.6.0.20121115_1941' profile='!WXS_PROFILE_ID!' .../> to the same value as !WAS_PROFILE_ID!.
Step six under "Setting the response file for required software" now describes that you should be use your respective variable, either com.ibm.sdk.6_32bit or com.ibm.sdk.6_64bit. Your variable depends on whether you installed a 32-bit or 64-bit WebSphere Application Server.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21655539