In WebSphere Application Server, how do you create J2C authentication data for Decision Center in WebSphere Operational Decision Management V7.5?
This information is provided as an additional step for configuring Decision Center on WebSphere Application Server.
Creating J2C authentication data in WebSphere Application Server for Decision Center V7.5
After you have created your data source and connection pool (see Step 2: Creating a data source and connection pool) , you create the J2C authentication data. J2C is a secure mechanism for integrating enterprise information systems to an application server and enterprise applications.
This step uses resAdmin as the user ID and resAdmin as the password. Your user ID and password might be different, depending on the user or schema that is used to execute the Rule Execution Server SQL script. If you perform the step as described, tables are created under the resAdmin schema.
In the case of a Derby database, if the connect command does not contain the user ID, then the user ID and password use the default values APP and APP. If you create the tables under the APP schema, you do not need to perform this step.
1. In the Integrated Solutions Console, open Resources > JDBC and Data sources.
2. Click ilogDataSource.
3. Under Related Items, click JAAS - J2C authentication data.
4. Click New and set the fields Alias, User ID, and Password. For example, this procedure uses the following values:
- Alias: RtsDerbyUser
- User ID: rtsAdmin
- Password: rtsAdmin
6. Open Resources > JDBC and Data sources and click ilogDataSource.
7. In the Security settings section, for Component-managed authentication alias, select the <NodeName>/RtsDerbyUser alias, where <NodeName> is the name of the WebSphere Application Server node on which you are configuring Rule Execution Server.
8. For Container-managed authentication alias, select <node name>/RtsDerbyUser.
9. Click Apply and Save to save directly to the master configuration.