IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting installation and configuration
Diagnosing a failing Ant configuration script
Determine whether a product installation problem on an operating system is caused by a failing Apache Ant configuration script.
Start diagnosing installation problems by looking at the troubleshooting procedure. See Troubleshooting installation and configuration. After the installation completes successfully, several Ant scripts configure the product. The following procedure describes what to do when an Ant script fails. When the installation log does not indicate a failure, determine how to correct any problems with failing Ant configuration scripts.
The INSTALL_ROOT/logs/wbi/install/installconfig_server.log file, when present, describes any failure of an Ant script. Determine if any of the following configuration scripts failed. If so, use the configuration script recovery procedures. Use the investigative action to manually verify that the following configuration scripts ran successfully during the configuration of the IBM BPM product.
If any script failed, use the recovery action steps to complete the function of the script.
To diagnose failed Ant configuration scripts...
Procedure
- Diagnose the failed 90SConfigWBIMigrationScript.ant configuration script. This script changes the permissions of the following script to 755: INSTALL_ROOT/bin/BPMMigrate. This script also replaces the following tokens in the INSTALL_ROOT/bin/BPMMigrate script:
From: To the value that you selected during installation: ${JAVAROOT} INSTALL_ROOT/java/jre/bin/java ${MIGRATIONJAR} INSTALL_ROOT/bin/migration/migrationGUI/migrationGUI.jar ${WASROOT} INSTALL_ROOT ${PRODUCTID} ${WS_CMT_PRODUCT_TYPE}
- Investigative action: Verify that the permissions are 755 for the following directories:
INSTALL_ROOT/bin/BPMMigrate.sh
INSTALL_ROOT\bin\BPMMigrate.bat
- Recovery action: Issue the following command:
chmod 755 INSTALL_ROOT/bin/BPMMigrate.sh
chmod 755 INSTALL_ROOT\bin\BPMMigrate.bat
- Investigative action: Open the following file in an editor and verify that real values exist instead of the following values: ${JAVAROOT}, ${MIGRATIONJAR}, ${WASROOT}, and ${PRODUCTID}.
INSTALL_ROOT/bin/BPMMigrate.sh
INSTALL_ROOT\bin\BPMMigrate.bat
- Recovery action: Change the following tokens to values in the BPMMigrate script: ${JAVAROOT}, ${MIGRATIONJAR}, ${WASROOT}, and ${PRODUCTID}.
- Diagnose the failed 85SConfigNoProfileFirstStepsWBI.ant. This script copies all files from the INSTALL_ROOT/properties/version/install.wbi/firststeps.wbi directory to the INSTALL_ROOT/firststeps/wbi/html/noprofile directory. This script also replaces the following tokens in the following files:
INSTALL_ROOT/firststeps/wbi/firststeps.sh
INSTALL_ROOT\firststeps\wbi\firststeps.bat
From: To the value that you selected during installation: ${JAVAROOT} INSTALL_ROOT/java/jre/bin/java ${PROFILEROOT} INSTALL_ROOT ${HTMLSHELLJAR} INSTALL_ROOT/lib/htmlshellwbi.jar ${CELLNAME} ${WS_CMT_CELL_NAME}
- Investigative action: Verify that all files are copied from the INSTALL_ROOT/properties/version/install.wbi/firststeps.wbi directory to the INSTALL_ROOT/firststeps/wbi/html/noprofile directory.
- Recovery action: Copy all of the files from the INSTALL_ROOT/properties/version/install.wbi/firststeps.wbi directory to the INSTALL_ROOT/firststeps/wbi/html/noprofile directory.
- Investigative action: Open the INSTALL_ROOT/firststeps/wbi/firststeps script in an editor. Verify that real values exist instead of the following values: ${JAVAROOT}, ${PROFILEROOT}, ${HTMLSHELLJAR}, and ${CELLNAME}.
- Recovery action: Change the following tokens to values in the INSTALL_ROOT/firststeps/wbi/firststeps script. ${JAVAROOT}, ${PROFILEROOT}, ${HTMLSHELLJAR}, and ${CELLNAME}.
Results
After you correct any installation errors and any Ant script configuration errors by performing the corrective actions in this procedure, the installation is complete.
What to do next
Start the First steps console.