Installation error: Cannot add asset com.ibm.mdm.hub.server.app.eba

Cannot add the asset com.ibm.mdm.hub.server.app-name.eba.

Description

This error means the IVT response file is not available because there was a problem in deploying the Enterprise Bundle Archive (EBA). During InfoSphere® MDM installation, if the IBM® WebSphere® Application Server is unable to deploy the com.ibm.mdm.hub.server.app-name.eba file, this error is logged. The EBA file is one of the InfoSphere MDM installation deployment archives. If this issue occurs, the installer can process to the end of the installation tasks and install InfoSphere MDM, but an indication that the IVT (Installation Verification Tool) is not successful is given. The error message can be seen in the IBM Installation Manager log file.

The error message is similar to this IBM Installation Manager log file example message:
Custom operation MDM Operational Server, deploying enterprise business application (EBA) on target server1 in unit com.ibm.mdm.mdm_config.install.eba.win completed: output in TIME_STAMP.log
Buildfile: build.xml

install_mdm_eba:
Creating new property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Updating property file: C:\IBM\E443\MDM\properties\install_mdm_eba.properties
Expanding: C:\IBM\E443\MDM\InstallableApps\com.ibm.mdm.hub.server.app.eba into C:\IBM\E443\MDM\tmp\mdm_eba_temp_TIME_STAMP
########################### entering ConfigEBATask ###########################
baseDir is ../../tmp//mdm_eba_temp_TIME_STAMP/
ebaID is E443
versionFilePath is ./MDM_VERSION
Begin to modify the file.
Begin to read the File.
Read the file successfully.
Begin to write the modified file.
Write the modified file successfully.
Modify the file sucessfully.
Begin to read version.
Read the file sucessfully: 11.0.0
Begin to record version.
Record version sucessfully: C:\IBM\E443\MDM\mds\scripts\.\MDM_VERSION
...................................
Set cuSourceID parameter to assetname=com.ibm.mdm.hub.server.app-E443.eba
Failed from asyncCmdClientHelper.processCommandParameters(cmd).
com.ibm.wsspi.management.bla.op.OpExecutionException: CWSAL0022E: Cannot add asset com.ibm.mdm.hub.server.app-E443.eba because bundles that it requires are not downloaded. To start the bundle download, save changes to the master configuration after importing the asset.
	at com.ibm.ws.management.bla.commands.ADTCommand.finishOp(ADTCommand.java:320)
	at com.ibm.ws.management.bla.commands.ADTCommand.opCompleted(ADTCommand.java:428)
	at com.ibm.wsspi.management.bla.op.Operation.notifyListeners(Operation.java:170)
	at com.ibm.wsspi.management.bla.op.Operation.execute(Operation.java:242)
	at com.ibm.wsspi.management.bla.op.compound.CompoundOperation.execute(CompoundOperation.java:83)
	at com.ibm.ws.management.bla.commands.ADTCommand$OperationScheduler.run(ADTCommand.java:672)
	at java.lang.Thread.run(Thread.java:773)
...................................

Solution

  1. Make sure that the machine where you are deploying InfoSphere MDM meets the hardware requirements and has at least 8G of RAM.
  2. Shutdown other none-essential applications, especially applications that are running JVMs.
  3. Uninstall InfoSphere MDM and install it again.


Last updated: 8 Mar 2019