Diagnosing a failing ANT configuration script
This topic helps you determine whether a product installation problem on an operating system such as AIX or Linux is caused by a failing ANT configuration script.
Start diagnosing installation problems by looking at the troubleshooting procedure. See Troubleshooting installation. After the installation completes successfully, several ANT scripts configure the product. This topic describes what to do when an ANT script fails.
If you are looking for troubleshooting information for the Web server plug-ins for WebSphere Application Server, see Troubleshooting Web server plug-ins installation and removal. This topic does not describe the plug-ins.
Use this topic when the installation log does not indicate a failure, to correct any problems with failing ANT configuration scripts.
Overview
The app_server_root/logs/instconfig.log file contains information about ANT scripts. The file is not created on systems such as AIX or Linux. The installation utility known as the ConfigManager runs the ANT scripts.
The app_server_root/logs/instconfig.log file, when present, describes any failure of an ANT script.
Use this topic to 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 WAS product. If any script failed, use the recovery action to complete the function of the script.
Procedure
- Configuration script 1: 90SCloudscapeModifyPermission.ant
This script changes the permission of the following directory to 766: app_server_root/cloudscape/databases
Log file to investigate for a possible error: app_server_root/logs/ModifyCloudscapePermission.log
Investigative action: Verify that the permissions of the following directory are 766: app_server_root/cloudscape/databases
Recovery action: Issue the following command to change the permission: chmod -R 766 app_server_root/cloudscape/databases
- Configuration script 2: 90SConfigMigrationScript.ant
This script changes the permissions of the following script to 755: app_server_root/bin/migration.sh This script also replaces the following tokens in the app_server_root/bin/migration.sh script:
From: To the value that you selected during installation: ${JAVAROOT} app_server_root/java/jre/bin/java ${MIGRATIONJAR} app_server_root/bin/migration/migrationGUI/migrationGUI.jar ${WASROOT} app_server_root ${PRODUCTID} ${WS_CMT_PRODUCT_TYPE}
Log file to investigate for a possible error: No log file exists for this script.
Investigative action:
- Verify that the permissions of the app_server_root/bin/migration.sh script are 755.
- Open the app_server_root/bin/migration.sh script in an editor. Verify that real values exist instead of the following values:
- ${JAVAROOT}
- ${MIGRATIONJAR}
- ${WASROOT}
- ${PRODUCTID}
Recovery actions:
- Issue the following command: chmod 755 app_server_root/bin/migration.sh
- Change the following tokens to actual values in the app_server_root/bin/migration.sh script.
- ${JAVAROOT}
- ${MIGRATIONJAR}
- ${WASROOT}
- ${PRODUCTID}
- Configuration script 3: 90SConfigNoProfileFirstStepsND.ant
This script copies all files from the app_server_root /properties/version/install/firststeps directory to the app_server_root /firststeps/html/noprofile directory. This script also replaces the following tokens in the app_server_root /firststeps/firststeps.sh script:
From: To the value that you selected during installation: ${JAVAROOT} app_server_root/java/jre/bin/java ${PROFILEROOT} app_server_root ${HTMLSHELLJAR} app_server_root/lib/htmlshell.jar ${CELLNAME} ${WS_CMT_CELL_NAME}
Log file to investigate for a possible error: No log file exists for this script.
Investigative actions:
- Verify that all files are copied from the app_server_root /properties/version/install/firststeps directory to the app_server_root /firststeps/html/noprofile directory.
- Open the app_server_root/bin/migration.sh script in an editor. Verify that real values exist instead of the following values:
- ${JAVAROOT}
- ${PROFILEROOT}
- ${HTMLSHELLJAR}
- ${CELLNAME}
Recovery actions:
- Copy all of the files from the app_server_root /properties/version/install/firststeps directory to the app_server_root /firststeps/html/noprofile directory.
- Change the following tokens to actual values in the app_server_root/bin/migration.sh script.
- ${JAVAROOT}
- ${PROFILEROOT}
- ${HTMLSHELLJAR}
- ${CELLNAME}
- Configuration script 4: 90SModifyDirectoryPermission.ant This script modifies the permissions of the following directories to 755:
- app_server_root/uninstall
- app_server_root/logs
- app_server_root/properties
Log file to investigate for a possible error: app_server_root/logs/ModifyPermission.log
Investigative action: Verify that the permissions of the following directories are 755:
- app_server_root/uninstall
- app_server_root/logs
- app_server_root/properties
Recovery action: Issue the following commands:
- chmod -R 755 app_server_root/uninstall
- chmod -R 755 app_server_root/logs
- chmod -R 755 app_server_root/properties
- Configuration script 5: 99SCreateEmptyDirs.ant This script creates the following empty directories:
- app_server_root/classes
- app_server_root/lib/ext
- app_server_root/properties/version/history
Log file to investigate for a possible error: No log file exists for this script.
Investigative action: Verify that the empty directories exist.
Recovery action: Create the directories.
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
Use the firststeps script to start the First steps console. See firststeps command for more information.
Troubleshooting installation
Troubleshooting Web server plug-ins installation and removal