Configuring InfoSphere Optim web applications on WebSphere Application Server V8

InfoSphere® Optim™ web applications can be configured on IBM® WebSphere® Application Server V8. You can choose to use WebSphere Application Server V8 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.

If you are to use Lightweight Directory Access Protocol (LDAP) or Active Directory (AD) for security, configure the following web application security groups in the LDAP or AP server.
Group name Description
OptOCMAdmin The administrator of the connection manager, who configures and maintains Optim directory connection settings and users.
OptMgrAdmin The administrator of the manager, who configures and maintains services.
OptMgrDesign The service designer, who creates and tests services in the manager.
OptMgrRequest The test analyst, who makes work order requests in the manager.
OptMgrOperate The test analyst, who makes work order requests in the manager.
OptMgrReview The business analyst, who reviews service requests in the manager to ensure that the requests are made for valid business reasons.

To configure InfoSphere Optim web applications on WebSphere Application Server V8:

  1. Create a Java 2 Connector (J2C) authentication alias for the connection manager database.
    1. Click Security > Global security.
    2. Under Authentication, click Java Authentication and Authorization Service > J2C authentication data.
    3. Click New.
    4. Enter a unique alias name and a valid user ID and password for the connection manager database and click OK. You can use a name of your choice for the alias.
    5. Click Save.
  2. Create a Java Database Connectivity (JDBC) provider for the connection manager database.
    1. Click Resources > JDBC > JDBC Providers.
    2. Select the scope at which applications can use the JDBC 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. Click New.
    4. Select the database type and JDBC provider type for the JDBC provider, select the XA data source implementation type, and click Next.
    5. Click Next to accept the remaining defaults, and click Finish at the end of the wizard.
    6. Click Save.
  3. Create a JDBC data source for the connection manager database.
    1. Click Resources > JDBC > Data sources.
    2. Select the scope at which applications can use the data source. When you specify a scope (or node and server) for the data source, specify the scope to which you are to deploy the Optim WAR file.
    3. Click New.
    4. Enter OptimOCM as the data source name, enter jdbc/OptimOCM as the Java Naming and Directory Interface (JNDI) name, and click Next.
    5. Click Select an existing JDBC provider, select the JDBC provider that you created earlier, and click Next.
    6. Enter the database-specific connection properties for the database (such as the database name and server name), and click Next.
    7. Select the Java 2 Connector (J2C) authentication alias that you created earlier in Authentication alias for XA recovery, Component-managed authentication alias, and Container-managed authentication alias, and click Next.
    8. Click Finish.
    9. Click Save.
    10. Click the name OptimOCM in the table to show the data source configuration settings.
    11. Click WebSphere Application Server data source properties.
    12. Select Non-transactional data source and click OK.
    13. Click Save.
  4. Click Test connection to ensure that the connection properties are configured correctly.
  5. Create the custom properties in the Java virtual machine of the application server.
    1. Click Servers > Server Types > WebSphere application servers > server_name, where server_name is the name of the application server that you are using.
    2. Under Server Infrastructure, click Java and Process Management > Process definition > Java virtual machine > Custom properties.
    3. Under Additional Properties, click Java Virtual Machine.
    4. Under Additional Properties, click Custom properties.
    5. For each of the properties in the following table, click New, enter the name and indicated value of the property, and click OK.
      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. Click Save.
  6. Configure the application server to allow database connections to be reused across servlets.
    1. Click Servers > Server Types > WebSphere application servers > server_name, where server_name is the name of the application server that you are using.
    2. Under Container Settings, click Web Container Settings > Web Container.
    3. Under Additional Properties, click Custom properties.
    4. Click New.
    5. Enter DisableMultiThreadedServletConnectionMgmt as the name and true as the value of the property and click OK.
    6. Click Save.
  7. Configure users and groups for the web application server.

    If you are to use LDAP or AD for security, configure global security to use the LDAP or AD server.

    1. Click Security > Global Security.
    2. Click Security configuration wizard.
    3. Select Enable application security and click Next.
    4. Select Standalone LDAP registry and click Next.
    5. Enter the primary administrative user name, type of server, and host name for the LDAP or AD server and click Next.
    6. Click Finish at the end of the wizard.
    7. Click Save.

    If you do not use LDAP or AD for security, create users and groups within the application server.

    1. Click Users and Groups > Manage Groups.
    2. For each of the following groups, click Create, enter the group name, and click Create.
      Group name Description
      OptOCMAdmin The administrator of the connection manager, who configures and maintains Optim directory connection settings and users.
      OptMgrAdmin The administrator of the manager, who configures and maintains services.
      OptMgrDesign The service designer, who creates and tests services in the manager.
      OptMgrRequest The test analyst, who makes work order requests in the manager.
      OptMgrOperate The test analyst, who makes work order requests in the manager.
      OptMgrReview The business analyst, who reviews service requests in the manager to ensure that the requests are made for valid business reasons.
    3. Click Users and Groups > Manage Users.
    4. For each user, click Create, enter the user information, click Group Membership, add groups to the user, click Close, and click Create.
  8. To notify users of work order status changes by sending emails to users, configure the unified web application WAR file for email notification of work order changes.
  9. Install the unified web application WAR file optim.unified.web.app.war.
    1. Click Applications > New Application.
    2. Click New Enterprise Application
    3. Click Browse, use the Browse window to select the optim.unified.web.app.war file on your computer, and click Next. The optim.unified.web.app.war file is shared_installation_directory/web/app/optim.unified.web.app.war, where shared_installation_directory is the installation directory that you specified for the IBM Optim Shared package group. For example, the default location for the WAR file on Microsoft Windows is C:\IBM\InfoSphere\Optim\shared\web\app\optim.unified.web.app.war.
    4. Click Detailed and click Next.
    5. Review the settings for each step and click Next. In most cases, take the default settings.
      • When you map resource references to resources, 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
        Ignore any warnings that the resources are beyond the deployment target scope.
      • When you map context roots for web modules, specify /optim as the context root.
      • When you map security roles to users or groups, select each role in turn and click Map Users or Map Groups to map users or groups to the selected security role. To use the groups that you configured in the LDAP or AD server, map each of the following security roles to the indicated group.
        Security role name Group name
        ocmadmin OptOCMAdmin
        admin OptMgrAdmin
        designer OptMgrDesign
        requester OptMgrRequest
        operator OptMgrOperate
        reviewer OptMgrReview
    6. Click Finish at the end of the wizard.
    7. Click Save.
  10. Start the unified web application.
    1. Click Applications > Application Types > WebSphere enterprise applications.
    2. Select optim_unified_web_app_war and click Start.
  11. Access the connection manager.
  12. Create or edit connections to Optim directories in the connection manager.
  13. If you use LDAP or AD, use the connection manager to import the users into the connection manager user registry.
  14. Configure and start a server so that the server registers with the connection manager.
  15. Access the manager and configure the location of the connection manager.


Feedback

URL of this topic: