Application schedulers can be created or configured using the Java
Management Extensions (JMX) API using one of several scripting languages or
Java.
Before you begin
In order to run with Java, two JAR files need to be present in the
program class path:
- wsexception.jar
- wasjmx.jar
and .
Why and when to perform this task
Complete these steps when using Java programs that utilize JMX.Steps for this task
- Look up the host and get an administration client handle.
- Get a configuration service handle.
- Update the resource-pme.xml file using the configuration service,
as desired.
- Find the SchedulerProvider for a given scope.
- Create a SchedulerConfiguration and specify all required parameters
identifying the SchedulerProvider as the parent object.
- Reload the resource-pme.xml file to bind the newly created scheduler
into the JNDI namespace. Perform this step if you want to use the newly created
scheduler immediately, without restarting the application server.
- Locate the DataSourceConfigHelper MBean using the name.
- Invoke the reload() operation.
Result
A scheduler is now configured and ready to use for newly installed
applications. If the scheduler JNDI name is not yet visible to your application,
reinstalling the application or restarting the application server will allow
the scheduler to be seen.
When schedulers are created for the first time,
the poll daemon does not automatically start, and you must start it manually.
When you restart the server, the poll daemon starts automatically. To start
the poll daemon manually, see the
Application scheduler daemon.
Note: Changes
to existing scheduler configurations will not take affect until after the
application server is restarted.
What to do next