IO09912: CONTENT MANAGER 8.4 (SPECIFICALLY ECLIENT) FIXPACK INSTALL ERROR

APAR status

• Closed as program error.

Error description

• When running the Content Manager 8.4 fixpack installer, the
  following error is generated:
  
  2008-11-12 16:37:08.812 DEBUG:: Command = {
  '/usr/IBM/WebSphere/AppServer/profiles/dev_eclient_profile/bin/w
  sadmin.sh' '-username' 'VALUE_NOT_SET' '-password' '********'
  '-c' '$AdminApp export eClient
  /opt/IBM/db2cmv8/CMeClient/eclient.ear' }
  2008-11-12 16:37:14.870 DEBUG:: WASX7209I: Connected to process
  "dmgr" on node nodeA using SOAP connector;  The type of process
  is: DeploymentManager
  2008-11-12 16:38:07.827 DEBUG:: WASX7015E: Exception running
  command: "$AdminApp export eClient
  /opt/IBM/db2cmv8/CMeClient/eclient.ear"; exception information:
  2008-11-12 16:38:07.828 DEBUG::
  com.ibm.websphere.management.exception.AdminException
  2008-11-12 16:38:07.828 DEBUG:: javax.management.MBeanException
  2008-11-12 16:38:07.828 DEBUG::
  com.ibm.websphere.management.exception.AdminException: The
  application can not be exported. The export directory:
  /opt/IBM/db2cmv8/CMeClient has read only permission
  ...
  2008-11-12 16:38:08.432 ERROR:: java.util.zip.ZipException: No
  such file or directory /opt/IBM/db2cmv8/CMeClient/eclient.ear
  
  
  This problem happens when the administrator initiates the
  eClient 8.4 fixpack installation on the machine where the
  managed node is installed, but the deployment manager node is
  installed on another machine (or it can happen in a standalone
  installation). This problem occurs on all platforms.
  

Local fix

• Workaround:
  
  1. Logon to the Websphere administration console, export the
  eclient application using the name eclient.ear.  (Important: the
  exported ear file must be saved using the name "eclient.ear"
  (this is case-sensitive)).
  
  2. Copy this ear file to the directory "IBMCMROOT/CMeClient/" on
  the machine that is running the eClient fixpack
  installation/configuration.
  
  3. Launch the fixpack installation.
  

Problem summary

• eClient fixpack instllation fails when deploying to a managed
  node.
  

Problem conclusion

• The problem has been fixed in Content Manager version 8.4.1
  fixpack1.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• eclient
  

Fix information

• Fixed component name

  ECLIENT

• Fixed component ID

  5724B43Z1

Applicable component levels

• R841 PSY

     UP