Installing WebSphere Application Server

Before you can install IBM® eDiscovery Manager, you must install IBM WebSphere Application Server on the same system.

You can install eDiscovery Manager to the following types of nodes:
  • A WebSphere Application Server Network Deployment managed or unmanaged node

  • A WebSphere Application Server Base managed or unmanaged node
Remember: Set the umask value to 022 before you install WebSphere Application Server. See Preparing AIX® systems for installation for more information about verifying and setting the umask value.

To install WebSphere Application Server in preparation for eDiscovery Manager:

  1. Install the prerequisite software for WebSphere Application Server.

    You can find a complete list of the WebSphere Application Server hardware and software requirements on the IBM Software Support site at http://www.ibm.com/support/docview.wss?uid=swg27006921.

  2. Prepare the operating system for WebSphere Application Server.

    To find more information about preparing the operating system, see Preparing the operating system for product installation.

  3. Install the appropriate version of WebSphere Application Server.

    For more information about installing WebSphere Application Server, see Installing WebSphere Application Server.

  4. Create a new server profile for eDiscovery Manager.

    In WebSphere Application Server Base environments, when you create a server profile, WebSphere Application Server creates a default application server instance named server1. In WebSphere Application Server Network Deployment environments, an application server must be created before installation. Other alternatives in both environments include creating a new application server instance for eDiscovery Manager in an existing profile or installing eDiscovery Manager to an unused application server instance of an existing profile.

    Recommendation: In WebSphere Application Server Base environments, use the server1 instance to simplify the administration and monitoring of eDiscovery Manager. (The only application server instance that can be monitored by the WebSphere administration console is server1. If you use a server instance other than server1 for eDiscovery Manager, you will not be able to start, stop, or monitor the status of eDiscovery Manager from within the WebSphere administration console because of this limitation.) You can find more information in Creating an application server profile.
    Requirement: When you create a server profile, WebSphere Application Server places several applications in the server instance that is associated with the new profile. You can ignore these applications. Do not install other, non-WebSphere applications in the server instance that is associated with the eDiscovery Manager profile. For example, do not install IBM FileNet® P8, the IBM Content Manager resource manager, or IBM Web Interface for Content Management in the eDiscovery Manager profile.
  5. Verify that the WebSphere Application Server is prepared for the eDiscovery Manager installation.
    • If you are deploying eDiscovery Manager to an unmanaged node, start the server instance of the WebSphere Application Server to which you plan to install eDiscovery Manager.
    • If you are deploying eDiscovery Manager to a managed node:
      1. Start the deployment manager.
      2. Start the node agent.
      3. Start the server instance for that node to which you plan to install eDiscovery Manager.
  6. Be sure to configure WebSphere Application Server as described in one of the following two information center topics, depending on which version of WebSphere Application Server you have installed:
    If you do not configure WebSphere Application Server as described, your users can receive the following error when they attempt a task after the Content Engine database is stopped and restarted:
    com.filenet.api.exception.EngineRuntimeException: 
DB_ERROR: An error occurred accessing the database.