Using the Scheduler Binding Component
Scheduler Binding Component Properties
This section contains the following topics:
- Runtime Properties for the Scheduler Binding Component
- Trigger Properties
- Scheduler BC Normalized Message Properties
Runtime Properties for the Scheduler Binding Component
The runtime properties allow you to make changes to a project after the project's design time is completed, without touching the business logic.
To access and edit the Scheduler runtime properties, do the following:
- Right-click the sun-scheduler-binding and select Properties from the pop-up menu. The Sun Scheduler Binding Properties Editor appears.
- From the Services window of the NetBeans IDE, expand the Servers node.
- If GlassFish is not started, start GlassFish. To do this, right-click GlassFish V2 and select Start from the pop-up menu.
- Under the application server, expand the JBI → Binding Components nodes and select the Scheduler Binding Component (sun-scheduler-binding). If sun-scheduler-binding is not started, start it now.
- Double-click the sun-scheduler-binding to open the properties editor.
- Edit the properties as needed. Once you are finished editing your properties, click the NetBeans IDE Save button, and redeploy your project to make your changes take affect.
The Scheduler Binding Component properties specify Thread Count, Application Configuration, Application Variables, Statistics, Loggers, and reference the Binding Component's description, name, type, and state.
- Displays the description of the binding component.
- Displays the name of the binding component.
- Indicates the state of the binding component as Started, or Stopped.
- Displays the component type.
- Displays the components specification version.
- Build Number
- Displays the build version for the current component.
- Thread Count
- Specifies the number of threads listening on the message bus.
- Quartz Worker Thread Count
- Specifies the number of threads that the Quartz Scheduler can use.
- Application Configuration
- Specifies the configured triggers name, starting date and time, ending date and time, and time zone. For more information on using the Application Configuration property see Scheduler Application Configuration.
- Application Variable
- Specifies the Application Variables configured for the binding component. Application Variables allow you to define a list of name:value pairs for a given stated type. The application variable name can be used as a token for a WSDL extensibility element attribute in a corresponding binding.
The Application Variables configuration property offers four variable types:
String: Specifies a string value, such as a path or directory.
Number: Specifies a number value.
Boolean: Specifies a Boolean value. The VALUE field provides a checkbox (checked = true).
Password: Specifies a password value. The password is masked and displays only asterisks.
For more information about using Application Variables, see Scheduler Binding Component Application Variables.
The Statistics properties provide a record of key statistics for the Scheduler Binding Component.
- Activated Endpoints
- Tracks the number of activated endpoints.
- Active Exchanges
- Tracks the number of active exchanges.
- Avg. Component Time
- Tracks the average message exchange component time in milliseconds.
- Avg. D.C. Time
- Tracks the average message exchange delivery channel time in milliseconds.
- Avg. Msg. Service Time
- Tracks the average message exchange message service time in milliseconds.
- Avg. Response Time
- Tracks the average message exchange response time in milliseconds.
- Completed Exchanges
- Tracks the total number of completed exchanges.
- Error Exchanges
- Tracks the total number of error exchanges.
- Received Dones
- Tracks the number of received dones.
- Received Errors
- Tracks the number of received errors.
- Received Faults
- Tracks the number of received faults.
- Received Replies
- Tracks the number of received replies.
- Received Requests
- Tracks the number of received requests.
- Sent Dones
- Tracks the number of sent dones.
- Sent Errors
- Tracks the number of sent errors.
- Sent Faults
- Tracks the number of sent faults.
- Sent Replies
- Tracks the number of sent replies.
- Sent Requests
- Tracks the number of sent requests.
- Up Time
- Tracks the up time of this component in milliseconds.
The Scheduler Binding Component runtime Logger properties include 13 different component activities that can be monitored and recorded at user-designated levels.
Each logger can be set to record information at any of the following levels:
- FINEST: messages provide highly detailed tracing
- FINER: messages provide reasonably detailed tracing
- FINE: messages provide basic tracing
- CONFIG: provides static configuration messages
- INFO: provides informative messages
- WARNING: messages indicate a warning
- SEVERE: messages indicate a severe failure
- OFF: no logging messages
Scheduler Binding Component Loggers
The values for the Scheduler Binding Component Loggers start with the location: sun-scheduler-binding. The value text has been wrapped for display purposes.
Specifies the logging level for the entire group of component loggers. Individual logger levels can then be changed as desired.
- Deployment Lookup (QoS)
- Messaging Channel (QoS)
- Accept Poller Thread (Comp TK)
- SchedulerBC Component Manager
- SchedulerBC Configuration Manager
- SchedulerBC Endpoint Manager
- SchedulerBC Exchange Handler
- SchedulerBC Service Unit Manager
- SchedulerBC Hybrid Trigger
- SchedulerBC Endpoint Handler
Exception messages start with a unique identifier. The Scheduler Binding Component exception message starts with SCHEDBC. For example:
SCHEDBC-3005: Quartz Cron trigger cronBinding.CronTrigger1 will fire next at:
COMPTK-3001: Message exchange accepted from NMR:
COMPTK-3009: Stopping SU-QosDemoCA-sun-scheduler-binding
For more information about the Scheduler Binding Component Logging Codes, see http://wiki.open-esb.java.net/Wiki.jsp?page=LoggingCodesByComponent.
The Scheduler Binding Component Trigger Properties allow you to make changes to the settings for a specific trigger in a group. You can also make these edits for a specific trigger using the Configure Scheduler Binding Wizard, accessed from the CASA Editor.
Using the Trigger Properties Editor
- To access the Properties Editor for a specific trigger, open the WSDL file that your project uses for the Scheduler Binding Component trigger from the Composite Application.
Note - Be aware that your completed project uses the WSDL file located under the Composite Application's Process Files directory, not the WSDL file located under the BPEL or XSLT project.
- From the WSDL Editor's WSDL view, expand Bindings → TriggerBinding → FireTriggerOperation → inMsg.
- Triggers in the tree appear in the order in which they were created. Right-click the trigger you wish to edit and select Properties from the pop-up menu.
The sched:trigger Properties Editor appears.
- Edit your properties as needed. Once you have finished editing your project's triggers, redeploy the project to enable your changes.
Trigger Configuration Properties
The Scheduler Binding Component trigger properties are:
- Specifies the name of the Quartz trigger.
- Specifies the type of Quartz trigger: Simple, Cron, or Hybrid.
- Specifies whether the Quartz trigger is enabled (true) or disabled (false).
- Specifies how many times the trigger repeats, indicated by a number or the keyword "indefinite" meaning indefinitely. This property only applies to Simple and Hybrid types.
- Specifies the interval between trigger firings, in milliseconds. This property only applies to Simple and Hybrid types.
- Specifies the Quartz Cron Expression that governs when a Cron or Hybrid trigger fires or begins, respectively. This property only applies to Cron and Hybrid types.
- Specifies the duration period, from the start time determined by the Cron Expression attribute, that the trigger repeatedly fires. That is, the specified length of time in which the trigger fires once it begins. This property only applies to Hybrid types.
- Specifies the message that is sent to the endpoint that is triggered. This message can also reference Application Variables, Java System Properties, or Scheduler Inbound Normalized Message Properties.
Once you have finished editing your project's triggers, redeploy the project to enable your changes.
Scheduler BC Normalized Message Properties
Normalized Message properties are commonly used to specify metadata that is associated with message content.
The Scheduler Binding Component uses three inbound Normalized Message Properties:
- Trigger Name
- Trigger Group
- Trigger Date
For information on using Normalized Message Properties in a BPEL process, see http://wiki.open-esb.java.net/Wiki.jsp?page=UsingNormalizedMessageProperties.