Planning for IBM WebSphere Application Server

You can use IBM WebSphere Application Server as your application server that hosts IBM Content Navigator components. However, all of your repositories must be running on IBM WebSphere Application Server.

For example, assume that your IBM Content Cortex repositories are deployed on Oracle WebLogic Server and you want to deploy IBM Content Navigator on IBM WebSphere Application Server. You must redeploy IBM Content Cortex on IBM WebSphere Application Server.

Required configuration for IBM WebSphere Application Server and WebSphere Application Server Network Deployment

If you deploy IBM Content Navigator on IBM WebSphere Application Server, ensure that you have the following configurations in your environment:
  • Enable IBM WebSphere Application Server administrative security before you run the IBM Content Navigator Configuration and Deployment Tool. The Configuration and Deployment Tool requires you to specify the name and password of a web application server administrator to connect to your web application server.
  • Use IBM HTTP Server to direct HTTP traffic to the IBM Content Navigator server. After you deploy your web applications, you must map the modules from your deployed web application to IBM HTTP Server.

Support for security domains

You can use security domains to configure the security settings for a set of applications that are deployed on IBM WebSphere Application Server.

If you have security domains configured in your WebSphere Application Server environment, you can select the security domain that you want to use in the Configuration and Deployment Tool. If the security domain is not mapped to the server or cluster where you deploy your application, the Configuration and Deployment Tool updates the definition of the security domain to include the mapping.

If you do not have any security domains configured, the global security settings for the application server are used.

Managing multiple versions of IBM Content Navigator applications in a clustered WebSphere Application Server environment

You can use application edition management to upgrade an IBM Content Navigator application in a clustered WebSphere Application Server environment while the current edition is still running. Application edition management helps you manage multiple versions of applications by enabling you to transition from one version of an application to the next without interrupting service to your users.

If you do not use application edition management, the existing application deployment on the server is overwritten.

Deploying IBM Content Cortex and IBM Content Navigator

You can deploy IBM Content Navigator into its own WebSphere Application Server profile or into the same profile as Content Platform Engine. If you deploy IBM Content Navigator into a different profile, then you must follow all the planning and installation instructions. If you deploy into the same profile, be aware of the following requirements:
Security requirements
  • You can use the LDAP configuration that is already in place for Content Engine. You do not need to create a separate LDAP configuration for IBM Content Navigator.
  • If you plan to use SSL or SSO, you must perform any required configurations to use SSL and SSO.
  • You can use the same Content Platform Engine security accounts, the same application server administrator, and administrative console user.
  • You must create a separate data source for the IBM Content Navigator database. To create this data source, you must create or identify the database accounts that are required by the IBM Content Navigator Configuration and Deployment Tool.
  • You must create the IBM Content Navigator login module when you run the IBM Content Navigator Configuration and Deployment Tool.
Client connector file requirements
  • You must update the Content Platform Engine client connector files if the version of the files that are installed with IBM Content Navigator do not match the version of the client connector files on your Content Platform Engine server.
  • If you plan to use IBM Content Cortex workflows, you must update the Content Platform Engine client connector files if the version of the files that are installed with IBM Content Navigator do not match the version of the client connector files on your Content Platform Engine server.

Planning for WebSphere Application Server Network Deployment

If you deploy IBM Content Navigator in a highly available cluster, you must take additional steps for certain tasks on all of the nodes in your cluster. When an additional action is required in a highly available environment, the following graphic is used to identify the action:
Begin alt text. Flagging graphic for High Availability Clusters information. End alt text.
Requirement: If you want to deploy IBM Content Navigator in a highly available cluster, you must increase the Java™ virtual machine (JVM) minimum heap size on the deployment manager to at least 1024 MB.
Important: If Memory-to-Memory (M2M) session replication is enabled in IBM WebSphere Application Server, then in the web server plug-in configuration, you must change the setting for GetDWLMTable to true. For more information about recommended values for web server plug-in configuration, see http://www.ibm.com/support/docview.wss?uid=swg21318463 External link opens a new window or tab.