E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (14)
View Page History
...
{section} This component relies on the Quartz open source project.
For more details about Quartz usage, visit its website at [http://www.quartz-scheduler.org/]
For more details about Quartz usage, visit its website at [http://www.quartz-scheduler.org/]
{column}
...h1. General information
h1. Scheduling service invocations (Consumes mode)
h2. General information
Since this component only supports consuming configurations, no WSDL is required.
However, the messages sent by this component must respect the WSDL of the invoked service.
However, the messages sent by this component must respect the WSDL of the invoked service.
...h1. Component Configuration
h2. JBI Descriptor
This component has no specific parameter in its configuration.
It only has the inherited ones from the CDK.
It only has the inherited ones from the CDK.
The Quartz component is configured with a CRON expression, the identifiers of a service to call and an XML message request to send to the service.
You have to deploy a service-unit with a JBI descriptor containing a *consumes* section with the right parameters.
You have to deploy a service-unit with a JBI descriptor containing a *consumes* section with the right parameters.
{include:0 CDK Component Configuration Table}
h1. Service Configuration
h2. Service Unit Descriptor
The Quartz component is configured with a CRON expression, a service to call and an XML message request to send to the service.
You have to deploy a Service Unit with a JBI descriptor containing a *consumes* section with the right parameters.
h1. Service Configuration
h2. Service Unit Descriptor
The Quartz component is configured with a CRON expression, a service to call and an XML message request to send to the service.
You have to deploy a Service Unit with a JBI descriptor containing a *consumes* section with the right parameters.
\\
Here is a sample of a SU JBI descriptor to call a Hello service with <text>hello</text> message, at 10:15am every day during the year 2005.
Here is a sample of a SU JBI descriptor to call a Hello service with <text>hello</text> message, at 10:15am every day during the year 2005.
...\\
*Configuration of a Service -Unit to create a scheduler into Petals ESB:*
|| Parameter || Description || Default || Required ||
...h2. Service Unit content
h2. Service-Unit content
The service -unit must only contain the JBI descriptor.
The directory structure of a SU for the Petals-SE-Quartz looks like this:
... - jbi.xml
{noformat}
{noformat}
h1. Configuring the component
This component has no specific parameter in its configuration.
It only has the inherited ones from the CDK.
{include:0 CDK Component Configuration Table}