Configuring the J2EE Job Executor Agent

To set up the environment on the external WebSphere® Application Server, Version 7.0 for the J2EE Job Executor Agent, do the following:

Create a Service Integration Bus
  1. Open the WebSphere Administrative Console (for example, http://localhost:9060/admin, depending on the admin port you configured).
  2. Expand Service Integration and select Buses. The Buses window is displayed.
  3. Click New to display the Buses configuration window.
  4. Type a name for the new bus, for example MyBus and click Next and then Finish to confirm.
  5. Click the MyBus name and the MyBus properties are displayed.
  6. Under Topology, click Bus Members. The Buses→MyBus→Bus members window is displayed.
  7. Click Add, select the Server radio button, choose your_application_server_name, click Next, and then click Finish.
  8. When the Confirm the addition of a new bus member panel is displayed, click Finish.
  9. Select Service Integration → Buses → MyBus → Destinations → New.
  10. Select Queue as the type and click Next
  11. Type BusQueue as the identifier and assign the queue to a bus member. Click Next. In the confirmation panel click Finish.
Configure the Default Messaging Service
  1. From the left panel of the WebSphere Administrative Console, expand Resources→ JMS→ JMS Providers, then click Default messaging at the server level as scope.
  2. In the Connection Factories section, click New.
  3. On the New JMS connection factory window, type in the following fields:
    Name
    MyCF
    JNDI name
    jms/MyCF
    Bus name
    MyBus
    Provider endpoints
    <hostname>:<Basic SIB port number>:BootstrapBasicMessaging;<hostname>:<Secure SIB port number>:BootstrapSecureMessaging
  4. Select again Resources -→ JMS-→ JMS Providers → Default Messaging at the server level as scope, locate the section Destinations, and click Queues. Click New and type in the following fields as shown:
    • Name=MyQueue
    • JNDI name=jms/MyQueue
    • Bus name=MyBus
    • Queue name=BusQueue
    Click Ok.
  5. Select again Resources → JMS → JMS Providers → Default Messaging at the server level as scope, and locate the section Activation Specifications.
  6. Click JMS activation specification. Click New and type in the following fields as shown:
    • Name=MyActSpec
    • JNDI name=eis/MyActSpec
    • Bus name=MyBus
    • Destination type=Queue
    • Destination JNDI name=jms/MyQueue
    Click Ok.
Configure the Java security
  1. Select Security → Secure Administration, applications and infrastructure.
  2. Locate the Authentication section, expand the Java Authentication and Authorization Service, and click J2C authentication data.
  3. Click New and type in the following fields as shown:
    • Alias=usr
    • User ID=usr
    • Password=pwd
    where usr is the user ID authenticated when using connector security and pwd is the related password.
  4. Click Ok.
Create an XA DataSource
  1. In the left pane, go to Resources → JDBC..→ JDBCProviders. In the resulting right pane, check that the scope is pointing to your_application_server_name.
  2. Locate the DERBY JDBC Provider (XA) entry and click it.
  3. Locate the Additional Properties section and click Data Sources.
  4. Click New and type in the following fields as shown:
    • Name = MyScheduler XA DataSource
    • JNDI name = jdbc/SchedulerXADS
    • Database name = ${USER_INSTALL_ROOT}/databases/Schedulers/${SERVER}/SchedulerDB;create=true
  5. At the top of the page, click Test connection button.
  6. Even if you get a negative result, modify the Database name field, deleting the part ;create=true. Click Ok.
Create a WorkManager
  1. In the left pane, go to Resources → Asynchronous beans → Work managers and click New.
  2. type in the following fields as shown:
    • Name=SchedulerWM
    • JNDI name=wm/SchedulerWM
  3. Click Ok.
Create and configure a scheduler
  1. In the left pane, go to Resources → Schedulers and click New.
  2. type in the following fields as shown:
    • Name=MyScheduler
    • JNDI name=sch/MyScheduler
    • Data source JNDI name=jdbc/SchedulerXADS
    • Table prefix=MYSCHED
    • Work managers JNDI name=wm/SchedulerWM
  3. Click Ok.
  4. Select MyScheduler and click Create tables.
  5. Deploy the test application.