Siebel IP 16 and Oracle Policy Automation 12 Integration : Some Things to Think About

Siebel IP 16 and Oracle Policy Automation 12 Integration : Some Things to Think About

Siebel IP 16 and Oracle Policy Automation 12 Integration

As I am now approaching the end of another Siebel and Oracle Policy Automation integration setup, I thought I would take a few moments to list here the different things that may cause you some pain or anguish if you are attempting the same. This list is not exhaustive, and I expect I will be coming back to it from time to time and adding more Siebel IP 16 and Oracle Policy Automation 12 Integration pain points.

The starting point for the integration is the ZIP File provided on the Oracle Policy Automation Blog by the folks at Oracle.

Oracle Policy Automation

  1. Check that you have set the correct access parameters for Anonymous API Access
  2. Check that you have entered the same prefix_{0} in your Connection parameters as the Siebel team have added to their Web Service
  3. Check that the username and password provided in the Connection actually does work in Siebel
  4. If you are testing using the ApplyBenefits Policy Model, remember to use the new version supplied in the ZIP not the one provided when you installed Siebel, to get around the List of Values custom type errors.

Siebel Enterprise

  1. Check the XSL files. Specifically look for missing “field-type” mappings. For example, does your Oracle Policy Automation Project pass Boolean attribute types back and forth? Check that all the relevant  mappings are present in  the file StartInterviewToLoadResponse.xsl. If they are missing, add them accordingly. (In the example file, only number-val, text-val and date-val are present).
  2. Check the Filter Business Services used by the Web Services in Request and Response are in the Respository and compiled in your SRF.
  3. Remember that the example “OPA Submit For PUB Sample Intake Contact.xml” Workflow Process only makes minor updates to Siebel : there is a hard coded reference to updating the Job Title Field with the text “OPA Fan” which you need to get rid of.
  4. As well as making the necessary changes to the Integration Object references, you will need to obtain a reference to the returned PropertySet and iterate through the responses yourself, which will require Scripting or a Business Service-based approach with the Row Set Transformation Toolkit if you have a license for it. Then you will need to adapt the Workflow Process to do whatever you want it to do (records being updated or inserted).
  5. The GetCheckPoint and SetCheckPoint Workflow Processes and associated logic will not function unless you have already installed Oracle Policy Automation Connector for Siebel version 10, since the database tables used in the example are not part of the version 12 integration.

General Advice for Siebel IP 16 and Oracle Policy Automation 12 Integration

It’s no secret that the Message Logging in Oracle Policy Automation Hub is pretty weak. In case of any issues, you are far better off using SoapUI, and setting the Web Service-related, Workflow Process-related and Object Manager-related logging in Siebel to higher than normal levels. Additionally, consider adding “dump to file” steps to the Workflow Processes that you can control using Decision Points based on a “Debug Mode” input variable”.

More on this subject you may be interested in:

Richard Napier

Author: Richard Napier

Richard Napier joined Siebel Systems in 1999 and took up the role of managing the nascent Siebel University in Southern Europe. He subsequently was Director of Business Development and Education for InFact Group (now part of Business & Decisions) for 8 years. He now runs his Consulting and mentoring company, On Demand Consulting & Education Ltd and has run ODCE since 2010. Owner of, he also is Co-Founder of the Siebel Hub.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Logo by Southpaw Projects LLC