Siebel Self Service Administration Guide > Using Siebel Public Sector Self Service > Roadmap for Integrating Oracle Policy Automation With Siebel Public Sector Self Service >

Process of Preparing Oracle Policy Automation Integration

This process consists of prerequisite tasks that you must perform before you can integrate Oracle Policy Automation (OPA) with Siebel Public Sector Self Service.

Before you integrate OPA with Siebel Self Service, you must complete the following tasks:

• Activating the Appropriate Workflows
• Setting the Application Level User Property
• Configuring the Inbound Web Service for OPA Metadata Web Service
• Exposing the Siebel Metadata to OPA
• Setting Up the OPA Hub Connection

Activating the Appropriate Workflows

Before you can integrate OPA with Siebel Public Sector Self Service, you must perform the following tasks:

• For implementations applicable to releases before Innovation Pack 2015, Patchset 5, activate the following workflows:
  • OPA Integration Workflow. You must also reload the runtime events for this workflow. For more information about this workflow, see OPA Integration Workflow.
  • OPA Integration Sub Workflow. For more information about this workflow, see OPA Integration Sub Workflow.
• For implementations applicable to release Innovation Pack 2015, Patchset 5 or later, activate the following workflows:
  • OPA Interview Service Main Workflow. For more information about this workflow, see OPA Interview Service Main Workflow.
  • OPA Interview Service Sub Workflow. For more information about this workflow, see OPA Integration Sub Workflow.
  • OPA Get PreSeed Data Workflow. For more information about this workflow, see OPA Get PreSeed Data Workflow.
  • OPA Process Submit Data Workflow. For more information about this workflow, see OPA Process Submit Data Workflow.
  • OPA End Interview Workflow. For more information about this workflow, see OPA End Interview Workflow.
  • OPA Get Meta Data Service For PUB Sample Intake Contact Workflow. For more information about this workflow, see OPA Get Meta Data Service For PUB Sample Intake Contact Workflow.
  • OPA Metadata Service - CheckAlive Workflow. For more information about this workflow, see OPA Metadata Service - CheckAlive Workflow.

Setting the Application Level User Property

If you want to integrate Oracle Policy Automation (OPA) with Siebel Public Sector Self Service, you must first set up the application level user property for new applications. This allows the OPA Interview Screen on the Siebel Open UI client to invoke the Siebel Business Service to post the Interview data.

To set the application level user property

• Add the following application level user property to the Application object in the repository:
  • User Property Name. Enter ClientBusinessService.
  • Value. Enter the name of the business service.

NOTE:  For the Siebel Citizen Service Portal application, the ClientBusinessService business service is already set to OPA Interview Framework Service.

Configuring the Inbound Web Service for OPA Metadata Web Service

If you want to integrate Oracle Policy Automation (OPA) with Siebel Public Sector Self Service, you must first configure the inbound Web service for OPA Metadata Web service.

NOTE:  To work with inbound Web services you must be in the Siebel Call Center client.

To configure the Inbound Web service for OPA Metadata Web Service

1. In Siebel Call Center, choose Site Map and locate Inbound Web Services.
2. Create the required Web service records in the Inbound Web Services list.

   NOTE:  For more information on working with Inbound Web services and service ports, see Siebel CRM Web Services Reference.

3. Create a new service port for each Web service record in the Service Ports list.

   NOTE:  For more information, see OPA Get Meta Data Service For PUB Sample Intake Contact Workflow.

4. Create an operation record for each newly created service port in the Operations list, using the following parameter values:
   • Name. Enter the operation name in the correct format. For example, if the CheckAlive method has the prefix Sample, then the operation Name is SampleCheckAlive.
   • Request Filter Service Display. Enter Metadata Filter Service.
   • Request Filter Method Display. Enter Request Filter Method.
   • Response Filter Service Display. Enter Metadata Filter Service.
   • Response Filter Method Display. Enter Response Filter Method.

Exposing the Siebel Metadata to OPA

This task is required if you need to expose the Siebel OPA integration objects (other than contacts) to OPA for metadata mapping.

NOTE:  The Contacts integration object is available as standard in Siebel OPA integration.

The OPA metadata service is implemented based on OPA-defined XSD schema. In the request message description, the Siebel server expects the OperationName_Input element, but it is unavailable. Also, the Siebel server adds the OperationName_Output element in the response message description. To overcome this issue, the Siebel server uses a filter service to add the OperationName_Input element and to remove the OperationName_Output element.

To expose the Siebel metadata to OPA

1. Do one of the following:
   • Modify the existing workflow OPA Get Meta Data Service For PUB Sample Intake Contact Workflow to expose the new integration object.

     Step 1 of this workflow uses the PUB Sample Intake Contact integration object in the input argument, however you can change this to suit your requirements.

   • Create a new workflow similar to the OPA Get Meta Data Service For PUB Sample Intake Contact Workflow and use the Integration Object name in the input argument in the Get IO Definition step. In the Inbound Web Service, choose the newly created Workflow in the Service Ports applet.

Setting Up the OPA Hub Connection

This procedure is mandatory if a metadata service is used.

To set up an OPA Hub Connection

1. Set up a connection to a Web service data source.

   For more information, see the Oracle Policy Automation Documentation Library.

2. Update the connection details in the OPA hub as follows:
   • Name. Enter the name of the new connection.
   • URL. Enter the URL, which is available in the Address field of the Service Port view located in the Administration View for Inbound Web Services.
   • Version. Enter the correct Web services version. For example:

     http://xmlns.oracle.com/policyautomation/hub/12.2/metadata/types

   • SOAP Action Pattern. Enter a pattern in the following format:

     document/version:prefix of operation name{0}

     For example:

     document/http://xmlns.oracle.com/policyautomation/hub/12.2/metadata/types:PUBContact_{0}

     NOTE:  Use the same version that you used in the Version field. You must also use the same operation prefix name as described in Step 4 in Configuring the Inbound Web Service for OPA Metadata Web Service.

   • Requires WS-Security Username token in SOAP actions. Enter your Siebel user login details.