WebSphere Business Integration Server Foundation V5.1 Handbook

410 WebSphere Business Integrator Server Foundation V5.1 Handbook

SystemOut O ReceiverNotificationBean.handleEvent(): Event received at Thu Jun 10 23:05:07

EDT 2004

SystemOut O ReceiverNotificationBean.handleEvent(): Task FIRED

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Task Name : BatchProcessTask

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Task ID : 1

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Repeats left : 5

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Next fire time : Thu Jun 10

23:05:04 EDT 2004

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Task Status : SCHEDULED to

execute

SystemOut O ----------------------------------------------------------------

SystemOut O ----------------------------------------------------------------------

SystemOut O ReceiverNotificationBean.handleEvent(): Event received at Thu Jun 10 23:05:07

EDT 2004

SystemOut O ReceiverNotificationBean.handleEvent(): Task was SCHEDULED

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Task Name : BatchProcessTask

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Task ID : 1

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Repeats left : 5

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Next fire time : Thu Jun 10

23:05:04 EDT 2004

SystemOut O ReceiverNotificationBean.checkTaskStatus(): Task Status : SCHEDULED to

execute

SystemOut O ----------------------------------------------------------------

You can see five execution of the HelloWorld process, then the Task status

becomes: INVALID.

7. Stop the server.

14.5 Assembly

The following section discusses the application assembly related actions for the

Scheduler service.

In the application code, local name references are used for the Scheduler service

so before you can use the Scheduler Task beans in WebSphere Business

Integration Server Foundation runtime environment, you have to tell your

application where they are in the JNDI name space. There are two ways to

accomplish this task:

1. Use WebSphere Studio Application Developer Integration Edition and make

appropriate changes to the Deployment Descriptors prior to importing the

Enterprise Application Archive.

2. Use the Application Server Toolkit to make the changes.