IBM Support

How to specify an alternative scheduler or data source for EJB timer service in Change Management Server

Question & Answer


Question

How do you specify an alternative scheduler or data source for EJB timer service in IBM Rational Change Management (CM) server?

Cause

IBM WebSphere Application Server (WAS) implements the EJB timer service. IBM Rational Change Management (CM) Server that runs on WAS utilizes this service when IBM Rational ClearQuest Web (CQWeb) is used.

The default EJB timer service uses an internal scheduler service which is associated with a Cloudscape database. If you choose to customize the pre-configured instance, you can change the data source to any supported database, such as DB2 or Oracle.

Answer

Follow the steps below to create a new scheduler service associated with an Oracle database and assign it to EJB timer service:

  1. Create an Oracle user account and make sure that the user has "connect" and "resource" privileges.

    Note: If you have an existing Oracle account with proper privileges, you don't need to create a new account.

  2. Start CM Server.

  3. Open WebSphere Application Server Administrative Console and log on the following url with a blank user name: "http://localhost:12060/ibm/console"

    For more details, refer to WebSphere Application Server Information Center.

  4. Create a new JDBC provider.
    • Go to Resources > JDBC > JDBC Providers
    • Choose scope as "Node=dfltnode, Server=server1"
    • Click New
    • Select database type as Oracle
    • Keep provider type as Oracle JDBC Driver
    • Select implementation type as connection pool data source
    • Specify a name for the provider
    • Click Next
    • Specify the directory location for ojdbc14.jar
    • Click Next
    • Review the summary and click Finish
    • Click Save to save the changes

      For more details, refer to WebSphere Application Server Information Center.

  5. Create a new data source.
    • Go to Resources > JDBC > Data Sources
    • Choose scope as Node=dfltnode, Server=server1
    • Click New
    • Specify a data source name, for example: mydatasource
    • Specify a JNDI name for the data source, for example: jdbc/mydatasource
    • Click Next
    • Select the JDBC provider that you just created
    • Click Next
    • Specify the URL for the database connection, for example: jdbc:oracle:thin:@localhost:1521:orcl
    • Click Next
    • Review the summary and click Finish
    • Click Save to save the changes

      For more details, refer to WebSphere Application Server Information Center.

  6. Specify log on information for the data source.
    • Go to Resources > JDBC > Data Sources
    • Open the data source that you just created
    • Open JAAS - J2C authentication data under Related Items
    • Click New
    • Specify an alias along with the user name and password for the user account that you created in Step 1
    • Click OK
    • Click Save to save the changes
    • Open the data source again
    • Choose the JAAS alias that you just created for Component-managed authentication alias
    • Click OK
    • Click Save to save the changes
    • (Optional) you can then test the connection of the data source in the data source list

  7. Create a new scheduler.
    • Go to Resources > Schedulers
    • Choose scope as Node=dfltnode, Server=server1
    • Click New
    • Specify a name for the scheduler, for example: myscheduler
    • Specify a JNDI name for the scheduler, for example: jdbc/myscheduler
    • Select the data source you just created
    • Specify the table prefix for the scheduler tables, for example: ejbts_
      Notice that the pre-configured EJB timer service uses EJBTIMER_ as the prefix.
    • Select the default work manager wm/default
    • Click OK
    • Click Save to save the changes

      For more details, refer to WebSphere Application Server Information Center.

  8. Create tables for the scheduler.
  9. Configure the EJB timer service to use the new scheduler.
    • Go to Application servers > server1 > EJB Container Settings > EJB timer service settings
    • Check Use custom scheduler instance and select the JNDI name of the scheduler that you just created
    • Click OK
    • Click Save to save the changes

      For more details, refer to WebSphere Application Server Information Center.

To configure EJB timer service for multiple CM Servers using the same database server, use different database user accounts in Step 1 or specify different table prefix for the schedulers in Step 7 above.

[{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"CM Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1;7.1.0.1;7.1.0.2;7.1.1;7.1.1.1;7.1.1.2;7.1.1.3;7.1.1.4;7.1.1.5;7.1.1.6;7.1.1.7;7.1.1.8;7.1.1.9;7.1.2;7.1.2.1;7.1.2.10;7.1.2.11;7.1.2.12;7.1.2.13;7.1.2.14;7.1.2.15;7.1.2.16;7.1.2.17;7.1.2.18;7.1.2.2;7.1.2.3;7.1.2.4;7.1.2.5;7.1.2.6;7.1.2.7;7.1.2.8;7.1.2.9","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21449519