Known problem: Creating the server profile for eDiscovery Manager in a non-default directory causes problems

com.ibm.websphere.management.exception.ConnectorException

[wsadmin] org.apache.soap.SOAPException: [SOAPException:

faultCode=SOAP-ENV:Client; msg=Read timed out;

targetException=java.net.SocketTimeoutException: Read timed out]

INSTALL_APPS_STDERR=The system cannot find the path specified.

1. Manually undeploy eDiscovery Manager. (WebSphere Application Server Base environments only)
2. Prevent timeouts from occurring during deployment.
3. Manually deploy eDiscovery Manager.

Manually undeploy eDiscovery Manager

(This procedure is relevant only in WebSphere Application Server Base environments. It is necessary because a timeout can occur at one of several times during deployment; no way exists to determine at which point the deployment failed.)

To manually undeploy eDiscovery Manager:

1. Use the WebSphere Administrative Console to manually remove any eDiscovery Manager objects.

Servers

In Application servers > eDM_app_server > Process definition > Environment Entries:
• LIBPATH (C:/IBM/eDM/lib)
• PATH (C:/IBM/eDM/lib)
Applications
• EDMClient
• EDMWorkMgrServer
Async beans work managers
• EDMClientWorkManager
• EDMServerWorkManager
• EDMWorkItemManager
Mail, Mail Session
• EDMMailSession
Shared libraries
• EDMLibraries
• EDMWorkMgrLibrary
• EDMClientLibrary
JVM Properties
• heap size=254, max heap size=1 GB
• classpath, for example, on Windows:
  C:/IBM/eDM/config/resources;C:/IBM/eDM/config;C:/Program Files/IBM/db2cmv8/cmgmt
• In the Generic JVM arguments:

  -DedmBinDir=C:/IBM/eDM/bin/

• An additional parameter in the Generic JVM argument:

  -Djava.security.auth.login.config=eDM_HOME\config\
  jaas.conf.WebSphere

AIX

eDMAppConfig.sh uninstall-all [WAS_admin_username WAS_admin_password]

Windows

eDMAppConfig.bat uninstall-all [WAS_admin_username WAS_admin_password]

Prevent timeouts from occurring during deployment

To prevent timeouts from occurring during deployment, change the value of the property com.ibm.SOAP.requestTimeout from its default value of 180 to a value of 0.

(This procedure is relevant for both WebSphere Application Server environments.)

1. Edit the file soap.client.props to set the value of the com.ibm.SOAP.requestTimeout property to 0.

The file soap.client.props exists in the properties subdirectory of the path to the WebSphere Application Server profile for eDiscovery Manager.

It can be useful to leave the value of this property at 0 even after eDiscovery Manager is successfully deployed. Doing so prevents subsequent uninstallation commands from timing out if you later decide to remove eDiscovery Manager from the system.

To manually deploy eDiscovery Manager:

1. Edit the file eDMAppConfig.bat to remove the following two exits at the end of the file.

exit 0
exit %rc%

AIX
export ANT_CMD=/usr/MyWASProfiles/eDMServer/bin/ws_ant.sh

Windows

set ANT_CMD=E:\MyWASProfiles\eDMServer\bin\ws_ant


The file setenv.* exists in the scriptsWAS subdirectory of the eDiscovery Manager installation directory.

AIX
WASProfilePath=/usr/MyWASProfiles/eDMServer

Windows

WASProfilePath=e\:/MyWASProfiles/eDMServer

AIX

When installing eDiscovery Manager for the first time:
eDMAppConfig.sh install-all WAS_userid WAS_password >> out.out

When upgrading eDiscovery Manager:
eDMAppConfig.sh update-all WAS_userid WAS_password >> out.out


Windows

When installing eDiscovery Manager for the first time:
eDMAppConfig.bat install-all WAS_userid WAS_password >> out.out

When upgrading eDiscovery Manager:
eDMAppConfig.bat update-all WAS_userid WAS_password >> out.out

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 script with only the FALSE parameter. For example:

/opt/IBM/eDM/scripts/postinstalledm.sh FALSE