Installation completes with errors

If you receive errors when installing IBM® eDiscovery Manager, check the eDiscovery Manager installation log and, in some cases, manually deploy the IBM WebSphere® Application Server.

Symptoms

The Installation Complete window of the eDiscovery Manager installation program reports that the installation completed with errors, for example (on a Windows system):
The installation completed with errors.

To get more detailed information, see the eDiscovery Manager installation
log files.

eDiscovery Manager installation log files:
C:\Program Files\IBM\eDM\logs\eDMInstallDebug*.log

Causes

Possible causes for the installation errors are:
  • Specifying a directory that is not writable or does not exist.
  • Failing a prerequisite check.
  • Selecting the wrong WebSphere Application Server profile or selecting a WebSphere Application Server profile for which security was enabled, but not providing an administrative user name and password.
  • Errors occurred when the eDiscovery Manager application server was being deployed to the WebSphere Application Server.

Resolving the problem

To resolve the problem:

  1. Check the eDiscovery Manager installation log files to see more detailed information. Search for errors at the end of the log file or files.
    During the installation: During the installation, the eDiscovery Manager installation program writes installation progress messages, error messages, and IBM WebSphere Application Server deployment information to installation debug log files. If the installation debug log file reaches 5 MB in size, eDiscovery Manager rolls it over and creates another log file. eDiscovery Manager creates up to four installation log files (eDMInstallDebug00.log, eDMInstallDebug01.log, eDMInstallDebug02.log, and eDMInstallConfig3.log) before it begins overwriting the first log file.
    Before the installation completes: Before the installation completes, the installation debug log files and the configuration debug log files exist in your home directory. On an AIX® system, the home directory is defined by the HOME environment variable. On a Microsoft Windows system, the home directory is defined by the HOMEPATH environment variable. For example, on Microsoft Windows, your home directory might be C:\Users\yourUserName.
  2. If necessary, use WebSphere Application Server scripts to manually deploy the eDiscovery Manager application server:

    The eDiscovery Manager deployment scripts are in the scriptsWAS subdirectory of the eDiscovery Manager installation directory.

    1. Find and change the following lines in the eDMAppConfig.bat file to keep the window open so that you can watch the deployment process:

      Change: exit 0

      to: rem exit 0

      Change: exit %rc%

      to: echo %rc%

    2. Based on the log file errors that you found, change the values of the appropriate variables in the setenv file and the appdeploy.properties file.
      For example, if you selected the wrong WebSphere Application Server profile, change the value of the profile name parameter:
      Windows (setenv.bat)
      set PROFILE_NAME=eDMServer
set PROFILE_PATH=/usr/IBM/WebSphere/AppServer/profiles/eDMServer
      Tip: You might also need to change the cellName and nodeName parameter values too. For example: 
      set PROFILE_NAME=eDMServer
set PROFILE_PATH=C:\Program Files\IBM\WebSphere\AppServer\profiles\
eDMServer
set cellName=mmri1aNode02Cell
set nodeName=mmri1aNode02
      Windows (appdeploy.properties)
      profileName=eDMServer
WASProfilePath=C\:/Program Files/IBM/WebSphere/AppServer/profiles/
eDMServer
      AIX (setenv.sh)
      export PROFILE_NAME=eDMServer
export PROFILE_PATH=/usr/IBM/WebSphere/AppServer/profiles/eDMServer
      Tip: You might also need to change the cellName and nodeName parameter values too. For example: 
      export PROFILE_NAME=eDMServer
export PROFILE_PATH=/usr/IBM/WebSphere/AppServer/profiles/
eDMServer
export cellName=mmri1aNode02Cell
export nodeName=mmri1aNode02
      AIX (appdeploy.properties)
      profileName=eDMServer
WASProfilePath=/usr/IBM/WebSphere/AppServer/profiles/eDMServer
    3. Deploy eDiscovery Manager from the command line. To capture console log messages, redirect the output of the deployment command to a log file.
      For example, to deploy eDiscovery Manager to a secure WebSphere Application Server, enter:
      AIX
      When installing:
      eDMAppConfig.sh install WAS_admin_username WAS_admin_password \ 
>> output.log
      When upgrading:
      eDMAppConfig.sh update-all WAS_admin_username WAS_admin_password \ 
>> output.log
      Windows
      When installing:
      eDMAppConfig.bat install WAS_admin_username WAS_admin_password \ 
>> output.log
      When upgrading:
      eDMAppConfig.bat update-all WAS_admin_username WAS_admin_password \ 
>> output.log
    4. Run the postinstalledm.sh shell script to perform some necessary post-installation tasks.

      The eDiscovery Manager scripts are in the scripts subdirectory of the eDiscovery Manager installation directory. For example, enter the following command to run the script on a WebSphere Application Server that has security enabled:

      /opt/IBM/eDM/scripts/postinstalledm.sh TRUE WAS_admin_username \
WAS_admin_password
      If security is not enabled on the WebSphere Application Server, run the postinstalledm.sh shell script with only the FALSE parameter. For example:
      /opt/IBM/eDM/scripts/postinstalledm.sh FALSE