Inbound Web service

Integration has always been fun and good that my exposure to integration has improved considerably in the last year. In my current project I had to create couple of inbound web services and was successful in finding a scriptless solution. Here is how I configured it,

1 .Create a workflow process with first step of EAI Integration Object Hierarchy to XML Hier Bus Service .Define a process property of type Integration Object and In (for In/Out)

2. Then use EAI Dispatch web service look up method to parse the XML .

For the EAI Dispatch service to process the XML define the xpath for the xml elements on Administration-Integration -> EAI Dispatch Service view.

The Key point in the workflow process , which I figured after a while, create a process property of type in and data type Integration Object. This would make sure that incoming message is received as Siebel Message and then process XML.

I'm planning to change the configuration I posted for Outbound webservice before with Integration-data-map and then EAI dispatch service. I bet that would be scriptless too and would perform better..Later.

Visibility for pick applet

Hi
Just configured something tricky today.Had to configure an account pick applet to show only My account. As always wanted to find a scriptless solution for this too and was successful. There is a set of class defined in the Siebel Security guide as well as on how to configure. Followed the instruction in the bookshelf to create a pick applet based on a special class and defined a applet user property and that's it I could see only My accounts on the pick applet.

I wish this was on the config apps bookshelf but later when I read through the configuration understood why Siebel has documented it in Security guide.Probably need to skim through the book to learn few more tricks on access control..Later...