Bookshelf Home | Contents | Index | PDF |
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 IntegrationThis 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 WorkflowsBefore you can integrate OPA with Siebel Public Sector Self Service, you must perform the following tasks:
Setting the Application Level User PropertyIf 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 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 ServiceIf 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
Exposing the Siebel Metadata to OPAThis 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
Setting Up the OPA Hub ConnectionThis procedure is mandatory if a metadata service is used. To set up an OPA Hub Connection
|
Siebel Self Service Administration Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |