Installation Guide › Installing an AIX Implementation › Run the CA RCM Installer › Complete CA RCM Server Installation on AIX/WebSphere › Configure J2C Authentication and JDBC Data Sources in the CA RCM Cluster

Configure J2C Authentication and JDBC Data Sources in the CA RCM Cluster

J2C authentication secures database access.

To configure J2C authentication and JDBC data sources in the CA RCM cluster

1. In the WebSphere administration console, click Security, Secure administration, Java Authentication and Authorization Service, J2C authentication data.
2. Create new database credentials for each of these databases:
   • CA RCM database – alias: eurekifyDBCred
   • Tickets Database – alias: eurekifyTmsDBCred
   • Queue Database – alias: eurekifyQueueDBCred
   • (optional) if you chose to install the reporting database - alias eurekifyReportDBCred
3. Click Resources, JDBC, Data Sources.
4. Create data sources as follows:
   • For the eurekify data source specify the following:

     Scope: CA RCM Cluster

     Name: eurekifyDS

     JNDI Name: jdbc/eurekifyDS

     Authentication Alias: .../eurekifyDBCred

   • For the eurekifyTMS data source specify the following:

     Scope: CA RCM Cluster

     Name: eurekifyTmsDS

     JNDI Name: jdbc/eurekifyTmsDS

     Authentication Alias: .../eurekifyTmsDBCred

   • For the eurekifyBusQueue data source specify the following:

     Scope: CA RCM Cluster

     Name: eurekifyBusQueueDS

     JNDI Name: jdbc/eurekifyBusQueueDS

     Authentication Alias: .../eurekifyQueueDBCred

   • For the eurekifyReport data source specify the following:

     Scope: CA RCM Cluster

     Name: eurekifyReportDS

     JNDI Name: jdbc/eurekifyReportdbDS

     Authentication Alias: .../eurekifyReportDBCred

     Note: Create the eurekifyReportDS data source only if you chose to install the reporting database. This data source must reference a Microsoft SQL Server JDBC provider, not an Oracle JDBC provider.

   Apply the following settings to all the data sources.

   • JDBC Provider – Select the existing MS SQL or Oracle JDBC Provider
   • Data store helper class –
     • For databases on Microsoft SQL Server:

       com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper

     • For databases on Oracle:

       Oracle 10g data store helper

   • CMP – Not selected
   • URL – (Oracle only) The URL of the database. This URL has the following format:

     jdbc:oracle:thin@Oracle_server:Port/Service_name
     

     Note: Oracle_server is the host name or IP address of the Oracle database server, Port is the port on the Oracle server, and Service_name identifies the target database.

5. Edit each of the data sources. Specify the following connection information:
   • Name – the database name you specified when you created the database.
   • Server Name – the server label or network address of the server hosting the database.
   • Port – The default port is 1433 for Microsoft SQL Server, and 1521 for Oracle.
6. Under Additional properties, Connection pool properties, set the value of the Maximum connections parameter for each data source as follows:
   • eurekifyDS – 80
   • eurekifyTmsDS – 80
   • eurekifyBusQueueDS – 20
   • (Optional) eurekifyReportdbDS - 20
7. Under Additional properties, WebSphere Application Server data source properties, set the Statement cache size to 50.
8. Click Test Connection to confirm that each data source connects to its database.
9. Restart the WebSphere Application Server or the Deployment Manager service as required in your WebSphere environment to implement the new data source definitions.