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

Incorporating Your Extensions in Oracle Fusion Middleware

This task is a step in Process of Extending the Connector.

In this topic, you incorporate your extensions in Oracle Fusion Middleware. To configure this example, you must possess detailed expertise and knowledge of using Oracle JDeveloper.

To incorporate your extensions in Oracle Fusion Middleware

1. Open the Oracle SOA Composer for your integration.

   For example, open Internet Explorer, and then navigate to the following address:

   http://computer_address:soa_server_port/soa/composer

2. At the login screen, enter your user name and password, and then click Login.
3. Enable the hook point you use in this example:
   1. Click Open, and then choose Open DVM.
   2. In the Select a DVM dialog box, click SBL_ORS_Parameter_Definition.dvm, and then click Open.
   3. In the SBL_ORS_Parameter_Definition.dvm screen, enable the CustomExtn_BookAppt_Hook2_Enabled parameter using values from the following table.

      Parameter	Value
      CustomExtn_BookAppt_Hook2_Enabled	true

      For more information, see Parameters You Must Set in the Parameter Definition File.

4. Open Oracle JDeveloper, and then do the following work:
   1. Add three new fields:
      • Use the same name and type that you used in Step 4.
      • Add these fields in the absSiebel.xsd input XSD. This XSD is located in the following directory:

   oramds:/apps/SBL_ORS_INTRG/v1/XSD

   • Add these fields in the Action complexType element.
   2. Add the fields that you added in Step a to the mediator XSLT files:

      Mediator_Input_To_BPEL_ApptBookingSys_BookAppt.xsl

      This XSLT file is located in the following directory in Oracle MDS:

   oramds:/apps/SBL_ORS_INTRG/v1/XSLT

   This step configures this integration to route the changes you make in Siebel CRM through the mediator to Oracle Fusion Middleware.

   3. Add the extra fields that you added in Step a to hook point 2 in the following file:

      CustomExtn_BookAppt_Hook2_Inpt.xsl

      This step configures this integration to send information about the new fields to the hook point.

   4. To manipulate the transformation from Siebel CRM to Oracle Real-Time Scheduler, map the following fields in the input for hook point 2.

      Siebel CRM	Oracle Real-Time Scheduler
      PrimaryActivityId	PRIMARY_STOP_ID
      MinOffset	MIN_OFFSET
      MaxOffset	MAX_OFFSET

      To avoid a conflict, make sure all names you use are unique.

5. Deploy the main composite and the hook point:
   1. To make sure this integration updates the Oracle Meta Data Services with your changes, use the updateMDS ant command.

      For more information, see Ant Commands You Can Use to Compile and Deploy Composites.

   2. Compile and deploy your changes.

      For more information, see Compiling and Deploying Oracle Fusion Middleware Artifacts.

6. Test your changes.

   To test your extension you run the appointment booking flow. For more information, see Siebel Field Service Integration to Oracle Real-Time Scheduler Installation and Administration Guide.

Using Hook Point 1 and Hook Point 3

This topic describes how to use only hook point 2. To make sure the output is correct, hook point 1 and hook point 3 are disabled. If you require hook point 1 or hook point 3, then make sure you do the following work:

• Modify the XSLT transformation files for hook point 1 and hook point 3.
• Set the corresponding DVM parameters to true.