Oracle Policy Automation 12 and Siebel IP 2016 – Installation and Configuration
Returning to this subject, at the request of one of our readers, we will look at the detailed steps to deliver the content of the Oracle White Paper recently published on the Oracle Blog. This post does not assume much Siebel experience, or for that matter Oracle Policy Automation experience, but you should at least be able to navigate your way round Oracle Policy Modeling and the Siebel client. We do assume the following setup
- Siebel On Premise
- Oracle Policy Automation On Premise or Cloud
- Word and Excel installed
- Oracle Policy Modeling installed
And so, on to the first step:
Install Siebel Tools
Much of the content delivered in the ZIP file that accompanies the Oracle Blog article is to be imported into your Siebel environment. In order to do this, you will need Siebel Tools. It goes without saying (but I will say it anyway) that anything you do in the next few steps can potentially damage your Siebel instance if you get it badly wrong (although with a degree of common sense you should be fine).
To install Siebel Tools, simply download Siebel Tools from edelivery.oracle.com and install it on your hard drive like any other Windows application. A good guide Siebel Tools installation guide [free registration required] is available on our sister site, the Siebel Hub.
Make the Metadata Changes
How you next proceed very much depends on your situation. If you are working as part of a team of developers, then you would Check Out the Projects you need before doing anything. For the purposes of brevity, I am going to assume you are on a self-study Siebel environment so you can safely login to Siebel Tools and connect to your Server database, something that you would never do in real life, and make the changes there directly.
In any case I suggest you observe closely the output of the import that follows, and back out of the import and back up (Tools > Add to Archive) any objects that are going to be updated or deleted.
- Unzip the attached OPA Siebel Generic WS Connector.zip
- Login to Siebel Tools as SADMIN to your Oracle Server DB (not Sample or XE)
- In Siebel Tools, in the menu, click Tools > Import from Archive and select the file OPAGenericWSConnector.sif from the SIF folder amongst the files you just unzipped
- In Siebel Tools, in the menu click Tools > Compile All Projects and compile the file into the SRF that is in your Client folder (Client\Objects\ENU\siebel_sia.srf for example). When the compile is complete, the SRF will also need to be moved to the Server\Objects\ENU folder which will require the Server to be stopped and restarted.
Deploy the Workflow Processes
- Still in Siebel Tools, in the Object Explorer Tree, select Workflow Process
- Search for OPA Get Checkpoint. If it is present, click the blue Publish icon on the Toolbar
- Repeat for OPA Load for Pub Sample Intake Contact, OPA Process Submit Data, OPA Set Checkpoint and OPA Submit for PUB Sample Intake Contact.
- Restart the Siebel Server and then login to the thin client http://yourwebserver/callcenter_enu or whatever your application is.
- Navigate to Administration – Business Process > Workflow Deployment
- In the top part of the page, search in turn for each of the 5 workflows, each time clicking Activate when you find them.
Deploy the XSL Files
The XSL files need to be copied to the Server\XSLT folder, the c:\temp folder and the Client\XSLT folder. The reason for the c:\temp folder – which you should create if you don’t have one – is simple, some of the workflows dump files into that folder. You can change the folder location / modify the workflows later if you want.
Deploy the Policy Automation Projects
The demonstration processes use the Projects called ApplyForBenefits or Eligibility. you will need to unzip them (they can usually be found in the Tools\REPPATCH folder, and you can unzip them, open them in Oracle Policy Modeling and then deploy them to your Oracle Policy Automation Hub. One of them – ApplyForBenefits – needs to be replaced with the version in the Zip file, Policy Models folder version . This is because the original ones were written quite some time ago, and the Value Lists data type confuses things when upgrading them.
You should at least be able to get the Benefits and Eligibility projects deployed. When deploying, make a note of the Deployment name. You can use the default Collection, or better still create a new Collection and give your user the required rights to it.
Deploy the Web Services
The Siebel application is contacted by an Inbound Web Service whenever the Policy Automation Project loads or saves data. So the next step is to import a ready-made Web Service. In Siebel, go to Administration – Integration > Inbound Web Service. Search for OPA Generic Connection. If it already exists, rename it and save the changes. Then click the green button and import the Web Service in the unzipped files. It is called OPA Generic Web.XML When you have done that, click the Gear menu again and Clear Cache.
By now you basically have a Web Service which will come inbound into Siebel, and this will trigger one of the Workflow Processes you imported. They will be represented by the different Service Ports of the Inbound Web Service. At the moment you only have two Service Ports, one called CheckAlive and one called GetMetaData. These are used when modeling a Policy that needs to reference Siebel business entities.
Getting the Connection into Oracle Policy Automation
Now. log in to the Oracle Policy Automation Hub and proceed to the Connections menu. You are going to create a new Connection. Bearing in mind that you are going to be communicating between Siebel and the Oracle Policy Automation Hub, it goes without saying that if you are using Self-Study environments of Siebel and Oracle Policy Automation, for example installed on a Virtual Machine, this is going to be a hell of a lot easier than it will be otherwise – you would have to take into account things like firewalls between Siebel and OPA and so forth. Assuming that both Siebel and OPA are installed on the same VM, this means you do not have to modify the Service Ports in Siebel (they are all pointing to something like this
The localhost being your web server. This is the URL you will need for the Connection in the Hub. You can follow the other items from the PDF white paper but here is a screenshot anyway.
The areas highlighted in red are respectively the address of the Web Service, and the smaller red box is to highlight something you will need to check. It corresponds to the Service Port Operations prefix that may be present in your Web Service. If the prefix is present (these are used to help distinguish different calls to multiple OPA Web Services) you would see it here in Siebel:
The full line from the Oracle Policy Automation Hub SOAP Action Pattern might look therefore something like this
With those elements entered into Oracle Policy Automation, with your Workflow Processes active, your Web Service Cache cleared and your EAI Object Manager running on the Siebel Server, then you should be able to open Oracle Policy Modeling, create a Project and add a connection to the Siebel data Connection through the ribbon, connecting to your Hub and then to your Connection:
That concludes part one of this post. Part Two will be posted when part one is successful for you all.