IBM Support

Using the Java JAR command to unpack ZIP files can change file permissions

Troubleshooting


Problem

Unpacking WebSphere Application Server install images, fix packs, refresh packs, and cumulative fixes that have been provided in a ZIP file format on a UNIX environment using the Java JAR command can cause the file permissions to change. The execute file permissions can be removed.

Symptom

Installation of WebSphere Application Server can fail because the execute file permissions have been removed. The result can be a failure to complete the configuration updates to WebSphere Application Server during the final stages of the installation or update.

Examples of the type of errors that can occur are:

  • From the log.txt file:

    (Jan 11, 2006 11:05:36 AM), Install, com.ibm.ws.install.ni.ismp.actions.ISMPConfigManagerLaunchAction, msg1, INSTCONFSUCCESS: Post-installation configuration is successful.
    (Jan 11, 2006 11:05:48 AM), Install, com.ibm.ws.install.ni.ismp.actions.ISMPWSProfileLaunchAction, err, INSTCONFFAILED: Cannot complete required configuration actions after the installation. The configuration failed. The installation is not successful. Refer to /opt/IBM/WebSphere/AppServer/logs/wasprofile/wasprofile_create_default.log for more details.
    (Jan 11, 2006 11:05:48 AM), Install, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, The Profile Creation Tool (PCT) has finished.
    (Jan 11, 2006 11:05:48 AM), Install, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFFAILED

  • From the wasprofle_create_default.log file:

    <message>Configuration action failed: com.ibm.ws.install.configmanager.actionengine.ANTAction-/opt/IBM/WebSphere/AppServer/profileTemplates/default/actions/bootStrapWCCMFiles.ant</message>
    ...
     <message>Creation of profile default at path /opt/IBM/WebSphere/AppServer/profiles/default failed.</message>
    ...
     <message>INSTCONFFAILED: Cannot create profile: The profile does not exist.</message>
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Install","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"7.0;6.1;6.0","Edition":"Network Deployment","Line of Business":{"code":"LOB77","label":"Automation Platform"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

More support for:
WebSphere Application Server

Software version:
7.0, 6.1, 6.0

Operating system(s):
AIX, HP-UX, Linux, Solaris

Document number:
345853

Modified date:
03 March 2025

UID

swg21227729

Manage My Notification Subscriptions