Configuring InfoSphere Optim web applications on a user-specified application server

InfoSphere® Optim™ web applications can use a Java™ Platform, Enterprise Edition (Java EE) application server other than WebSphere® Application Server Community Edition. You can choose to use an application server such as WebSphere Application Server for more reliable and faster performance and for better security.

Before you begin, you must have credentials with read and write access to a relational database system that the application server can use for the connection manager database. You must also have a Java Database Connectivity (JDBC) driver for the connection manager database.

To configure InfoSphere Optim web applications on a user-specified application server:

  1. Create a Java 2 Connector (J2C) authentication alias for the connection manager database. You can use a name of your choice for the factory or alias. When you specify a scope (or node and server) for the connection factory or authentication alias, specify the scope to which you are to deploy the Optim WAR file.
  2. Create a Java Database Connectivity (JDBC) provider for the connection manager database. Specify an XA data source implementation type for the provider. When you specify a scope (or node and server) for the JDBC provider, specify the scope to which you are to deploy the Optim WAR file.
  3. Create a JDBC data source for the connection manager database. The JDBC data source must have the following properties:
    • The JDBC data source must have the data source name OptimOCM and the Java Naming and Directory Interface (JNDI) name jdbc/OptimOCM.
    • When you specify a JDBC provider for the JDBC data source, use the JDBC provider that you created earlier.
    • When you specify the following security aliases, use the Java EE Connector connection factory or a Java 2 Connector (J2C) authentication alias that you created earlier:
      • Authentication alias for XA recovery
      • Component-managed authentication alias
      • Container-managed authentication alias
    • The JDBC data source must be set to be a nontransactional data source.
  4. Test the database connection to ensure that the connection properties are configured correctly.
  5. Create the following custom properties in the Java virtual machine of the application server, and assign the indicated values to the properties.
    Property Value
    com.ibm.nex.ocm.name The name of the connection manager database.
    com.ibm.nex.ocm.schema The schema that you use for the connection manager database.
    com.ibm.nex.ocm.vendor Oracle, DB2 UDB, or SQL Server
    com.ibm.nex.ocm.version The version number of the RDMS (for example, 11.2 or 9.7). For Oracle databases, specify all 4 digits in the version number.
  6. Configure the application server to allow database connections to be reused across servlets. To configure WebSphere Application Server to allow database connections to be reused across servlets, set the custom web container property DisableMultiThreadedServletConnectionMgmt to true.
  7. Determine what security realm you are to use for the web applications and configure the security realm with the users and groups that the web applications use. The following table lists the roles that are used by the web applications. For each role, the table indicates the default principal group name that is configured for the role in the unified web application WAR file, and a description of each role.
    Security role name Default principal group name Description of role
    ocmadmin OptOCMAdmin The administrator of the connection manager, who configures and maintains Optim directory connection settings and users.
    admin OptMgrAdmin The administrator of the manager, who configures and maintains services.
    designer OptMgrDesign The service designer, who creates and tests services in the manager.
    requester OptMgrRequest The test analyst, who makes work order requests in the manager.
    operator OptMgrOperate The test analyst, who makes work order requests in the manager.
    reviewer OptMgrReview The business analyst, who reviews service requests in the manager to ensure that the requests are made for valid business reasons.
  8. Deploy or install the unified web application WAR file optim.unified.web.app.war. Specify the following values for the indicated parameters.
    • Target resource JNDI name for the javax.mail.Session resource reference: mail/MailSession
    • Target resource JNDI name for the javax.sql.DataSource resource reference: jdbc/OptimOCM
    • Context root: /optim
  9. Start the unified web application.
  10. Access the connection manager and configure connections to Optim directories. If you use LDAP or AD, import the users into the connection manager user registry.
  11. Configure and start a server so that the server registers with the connection manager.
  12. Access the manager and configure the location of the connection manager.


Feedback

URL of this topic: