Tag: Symbolic URL

Siebel Symbolic URL and OPA


Siebel Symbolic URL and OPA

Last week I was working on Oracle Policy Automation integrated with Siebel. As part of the implementation one of the Oracle Policy Projects is going to be displayed in a Symbolic URL. If you are not a Siebel person, then this is a mechanism to pass arguments to a base URL using an Administration screen. Typical arguments might include the window size, the SSO characteristics and other disposition information.

The reason I mention it here is because the Oracle Policy Automation project had several input attributes mapped to URL arguments. It is worthwhile knowing and remembering that the manner in which Oracle Policy Automation handles these arguments is different to the standard way that Siebel does it.

From the documentation we learn that input attributes thusly mapped are to be provided in one of two ways. The choice depends both on the desired approach and the number of attributes.

  • startsession/ProjectName?seedData=argument%3dWord%20SecondWord

The above method is passing one argument. The URL is encoded.

  • startsession/ProjectName?seedData={name:Word%20SecondWord,assessment_date:2017-01-07}

This second example has two arguments, and uses a JSON snippet. This format allows for multiple input arguments. The principle reason for speaking about these two concepts is that Siebel Symbolic URL tries to code the URL by default. So if it is already coded as above you might get some odd results.

If you are using Siebel therefore you will need to add the following Field to your Symbolic URL definition in Siebel. The EncodeURL command takes a Boolean value so you try and set it to False.

Have a nice day.

 

Siebel Open UI and Oracle Policy Automation 12 Integration Version 12 #2

[vc_row][vc_column][vc_column_text]Siebel Open UI and Oracle Policy Automation 12 Integration Version 12 #2

After I wrote the previous article, it struck me that Siebel people might need a bit of an overview of Integration with Oracle Policy Automation, before I plunged into the specific scenario of the Interview Service. Let’s be clear the Interview Service is just one of a series of Web Service connection points for Siebel people looking to get OPA into their Oracle Siebel CRM Application. In fact they are not limited to Web Services as far as integration is concerned. Let’s therefore take a moment in this post to review the options. I am writing here about Oracle Policy Automation 12.

Symbolic URL

Sometimes, a nice little frame in which Oracle Policy Automation is displayed is frankly good enough. The interface proposed to the user will of course be that of Oracle Policy Automation. In Oracle Policy Modeller we can implement custom style sheets for our interview, bringing it closer to the Siebel Open UI look and feel, and we can use the dynamic nature of the Symbolic URL principle to add pertinent information into the URL and to an extent pre-seed the interview with data in Siebel, using the recent addition to the Oracle Policy Modeller Edit Attribute Dialog.

Seeding Parameters via URL

Assess Service

If you are looking to use Oracle Policy Automation as a back-end, zero user interface platform, then the Assess Service is going to probably be one of your chosen solutions. It has methods dedicated to passing in data and simply receiving the response. Of course it is up to you to provide the mechanism (probably some EAI Siebel Adapter, some transformation and a bit of Workflow Process) that is going to actually handle the input and output. This is pretty much what existed in version 10.

Answer Service

Newer than the¬†Assess Service it has methods relating to the use of Connection objects in Oracle Policy Automation. In short, if you have Oracle Policy Modeller mapped to another application (let’s say a database or SAP or something) and you want to call it from Siebel, then you will need to know the data model that Oracle Policy Automation is expecting, so that you can build the right input. Enter the GetInputDataDefinition Action, followed in all probability by the GetAnswer action. Still fundamentally a “zero user interface” integration. We never see the Interview created in Oracle Policy Modeller.

Interview Service

As the name clearly shows, this service allows us to work though the Interview Screens of your Policy Model, and to handle all the different interactions (back, forward, save, close, and so on) that can occur. This service can then be connected to, for example Siebel CRM, and fancy techniques used to generate the user interface natively in Siebel Open UI, but based on the structure and logic of the UI built in Oracle Policy Automation. Look out for GetInputDataDefinition, StartInterview, Investigate, EndInterview, GetFiles and SnapshotSession actions. If you see them, then you are looking at the Interview Service.

Server Service

Last but by no means least, the Server service gives access to things like the Timezone settings as well as a list of deployed Rulebases.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]As ever the documentation can be found online.[/vc_column_text][/vc_column][/vc_row]

Worldwide
Logo by Southpaw Projects LLC