Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide > Extending the Connector >

Overview of Extending the Connector

A hook point is a service you can use to extend a composite. It uses input that you provide to communicate with a composite and it returns a result from the composite. You can use hook points to extend the following items:

• Schema
• Mediator
• BPEL flow

Note the following:

• This integration uses each hook point as a placeholder in a BPEL flow.
• A hook point does not include any functionality or perform any manipulation other than to access a composite.
• Every hook point uses a synchronous request and reply model.
• You can use hook points to extend a direct integration flow.
• This integration disables every hook point by default. To use a hook point, you must set a DVM (domain value map) parameter for the hook point parameter to true. For more information, see Parameters You Must Set in the Parameter Definition File.
• If you use a hook point, then make sure you avoid a name space conflict in the implementation.

Figure 16 illustrates a generic flow that includes hook points.

Figure 16. Generic Flow That Includes Hook Points

Explanation of Callouts

This integration performs the following work for most hook points:

1. Hook Point 1. The input for hook point 1 is the Siebel request message. For example, the Siebel input for the appointment booking flow is absInput. The output of hook point 1 is the extended Siebel request message.
2. Hook Point 2. The input for hook point 2 is the extended Siebel request message to the composite and the Oracle Real-Time Scheduler request message for the operation. The composite that calls the hook point determines this operation. The output for hook point 2 is the Oracle Real-Time Scheduler requested message for the called operation. For more information, see Hook Point Operations That This Integration Calls.
3. Hook Point 3. The input for hook point 3 is the Oracle Real-Time Scheduler response message. The composite that calls the hook point determines this output. For example, the Siebel output for the appointment booking flow is absReply. The output for hook point 3 is the Siebel response message.
4. ORS Web Service. The external Web service that the composite calls.