Bookshelf Home | Contents | Index | PDF     

Siebel eService Administration Guide for Siebel Open UI > Configuring Siebel eService > Integrating Oracle Policy Automation With Siebel Public Sector eService >

Prerequisites for Integrating Oracle Policy Automation

Before you can integrate Oracle Policy Automation (OPA) with Siebel Public Sector eService, you must complete the following tasks:

  • Create and deploy the rulebases in OPA.

    Sample rulebase projects are packaged in Siebel Tools, and you can extract the rulebase projects from the following directories:

    Tools_install_location\REPPATCH\SampleScreening.zip

    Tools_install_location\REPPATCH\ApplyForBenefits.zip

    When you deploy the sample rulebase for screening, you must change its deployment name to Screening so that it functions with the preconfigured OPA integration. Similarly, when you deploy the sample rulebase applicable to applying for benefits, its deployment name must be ApplyForBenefits so that it functions with the preconfigured OPA integration.

  • Activate the appropriate workflows.
  • Use the InvokeWorkflow method in the appropriate business service to call the appropriate workflow.
    • For implementations applicable to releases before Innovation Pack 2015, Patchset 5, the Invoke Workflow method in the OPA Interface Service business service calls the OPA Integration Workflow. For information about other methods in this business service, see OPA Integration Workflow and OPA Integration Sub Workflow.
    • For implementations applicable to release Innovation Pack 2015, Patchset 5 or later, the Invoke Workflow method in the OPA Interview Framework Service business service calls the OPA Interview Service Main Workflow. For more information about the methods in this business service, see Business Services for Oracle Policy Automation.

      The required input parameters for the InvokeWorkflow method are Rulebase and WorkflowName. If you want to add other input parameters to this method, then you must define these parameters in the process properties of the workflow so that the workflow can receive these parameters.

      To configure the text for the Close button on the last screen of the interview session, you pass the CloseBtnLOV input parameter to the InvokeWorkflow method. The value for this parameter is a Type field value that you set up in the List of Values view of the Administration - Data screen in Siebel Public Sector. In this view, specify a value for the Type field (for example, OPA_CLOSE), for the Language-Independent Code field (for example, close) and for the Display Value field (for example, Apply).

      For implementations applicable to release Innovation Pack 2015, Patchset 5 or later, you can use the Close Button LIC parameter and the IsCloseButtonRequired parameter to configure the Close button. For more information about these parameters, see Parameters for Configuring Interview Sessions.

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:

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.
      
Siebel eService Administration Guide for Siebel Open UI Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices.