Each configured scheduler is available using the Scheduler API
from a J2EE server application, such as a servlet or EJB module. Use a JNDI
name or resource reference to access schedulers. Each scheduler is also available
using the JMX API, using its associated WASScheduler MBean.
About this task
Scheduler and WASScheduler interfaces are the starting point for
all scheduler activities. Each scheduler is independent and allows task life
cycle operations, such as creating new tasks.
Procedure
- Locate schedulers using the javax.naming.Context.lookup() method
from a J2EE server application, such as a servlet or EJB module like the following
example:
//lookup the scheduler to be used
import com.ibm.websphere.scheduler.Scheduler;
import javax.naming.InitialContext;
Scheduler scheduler = (Scheduler)new InitialContext.lookup("java:comp/env/sched/MyScheduler");
- Use wsadmin to locate a WASScheduler MBean using JACL scripting:
set jndiName sched/MyScheduler
# Map the JNDI name to the mbean name. The mbean name is
# formed by replacing the / in the JNDI namewith . and prepending
# Scheduler_
regsub -all {/} $jndiName "." jndiName
set mbeanName Scheduler_$jndiName
puts "Looking-up Scheduler MBean $mbeanName"
set sched [$AdminControl queryNames WebSphere:*,type=WASScheduler,name=$mbeanName]
puts $sched