Gets an oracle.as.scheduler.RequestExectionContext object from a serialized request execution context string. A one-way operation with a separate asynchronous response. Registers for an asynchronous status update when the request completes. This does not physically remove any data, although the request is no longer be accessible by most methods.įor parent requests, this operation cascades to all children. Marks a request in a terminal state for deletion. Oracle Enterprise SchedulerOracle Enterprise Scheduler Oracle Enterprise SchedulerOracle Enterprise SchedulerOracle Enterprise Scheduler Similar to addPPAction, except that you can package multiple actions in your request.Ĭancels the processing of a request that is not in a terminal state. The parameters to these legacy routines are passed as arguments to addPPAction in the order in which they were declared in the original routine. The method provides support for action previously supported by add_printer, add_notification, add_layout in concurrent processing. This method is called prior to submitting the request. Table 16-1 Summary of Operations Available with ESSWebservice OperationĪdds a post-processing action to a step in a job set request. Table 16-1 summarizes the operations available with ESSWebservice. The ESSWebservice WSDL describes the complete functionality for the ESSWebservice. However, Oracle Enterprise Scheduler web service also provides the capability to retrieve the job completion events asynchronously (in a manner similar to implementing the Oracle Enterprise Scheduler EventListener contract in the core API layer). Although the Oracle Enterprise Scheduler internal job execution model is asynchronous, the ESSWebservice APIs need not be asynchronous. The ESSWebservice is a synchronous web service, such that all the operations invoked are synchronous operations. Thus, the ESSWebservice is available on every node where Oracle Enterprise Scheduler is installed and deployed. ESSWebservice exposes job scheduling and management functionality for request submission and request management.ĮSSWebservice is deployed within the Oracle Enterprise Scheduler application, where the application is a Java EE application within the Oracle Enterprise Scheduler runtime framework. However, any client that requires a web service to interact with Oracle Enterprise Scheduler can use ESSWebservice. The ESSWebservice is provided primarily to support SOA integration, for example invoking Oracle Enterprise Scheduler from a BPEL process. Submitting and managing Oracle Enterprise Scheduler job requestsĬonfiguring and managing Oracle Enterprise SchedulerĬlient applications can use the Oracle Enterprise Scheduler web service (ESSWebservice) to access a subset of the Oracle Enterprise Scheduler runtime functionality. This functionality includes support for the following operations:Ĭreating and managing Oracle Enterprise Scheduler metadata Oracle Enterprise Scheduler provides a rich set of functionality for enterprise level scheduling.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |