Okay, now we’ve got our proxy BS, Integration Objects and Web Service definitions all in Siebel, we can build a Workflow Process to invoke (consume) the Web Service and do something useful with the integration interface.
We’ll start with a pretty simple requirement – let’s look for the first post from the WordPress site and create a Siebel Action (Activity) record with the information.
- First up, create a new Data Map (Site Map > Integration – Administration > Data Map Editor)
- The Integration Objects that we’re going from and to are ‘Post’ and ‘Action_IO’ respectively
- The Integration Components are ‘Post’ and ‘Action’
- Map the [title] field from WordPress to the ‘Description’ field in Action and map the [content] field to ‘Comments’
- Map the [id] field to ‘Activity UID’ to give us a user key to play with
- Validate your new Data Map
Now let’s create a new Workflow Process.
- Create a new Workflow Process in the project that we created last time.
- You’ll need to define some new process properties:
- Create a new Workflow Process with the following steps:
- The first business service should be configured to run the proxy business service and the getPost method. Input should be the WP Post Id and the output will be the WP Post Message. Note that the output argument from the proxy BS is ‘getPostResponse:getPostReturn’
- Next, invoke the Purge method of the EAI Data Transformation Engine BS. This is good practice for testing but should be removed in a Production environment
- Now call the Execute method of the EAI Data Transformation Engine BS. Pass in the WP Post Message hierarchy, the name of the Data Map created earlier and output the WP Action Message property. This will give us our ‘Action’ IC with all the Integration Component Fields in place
- Finally, call the ‘Insert’ method of the EAI Siebel Adapter BS. This will take as input the hierarchy created by the mapper and use it to create a new Activity record
| Property | Type | Default | Comment |
|---|---|---|---|
| WP Post Id | String | 1 | Use this to store a literal for testing purposes |
| WP Post Message | Hierarchy | The Hierarchy we’ll use to grab data from WordPress | |
| WP Action Message | Hierarchy | The Hierarchy we’ll use to store the new Action definition |
| Name | Type | Business Service | Method | Comment |
|---|---|---|---|---|
| Start | Start | |||
| Get WP Post | Business Service | WordPressWebServicePortType | getPost | Proxy BS that invokes the Web Service |
| Purge Data Map | Business Service | EAI Data Transformation Engine | Purge | Refreshes the Data Map cache for testing |
| Data Map | Business Service | EAI Data Transformation Engine | Execute | Map the WP data to the Action IO |
| Insert Activity | Business Service | EAI Siebel Adapter | Insert | Creates the new Action BC record |
| End | End |
That’s it!
Run through the simulator and you’ll see that the process calls the Web Service that you created to grab an XML message from your WordPress site into a hierarchy. The Data Mapper then uses the IO definitions created by the EAI wizard to map the data across to the vanilla Action IO. Finally, the process uses the mapped message to create a new Activity record in Siebel!
Give it a go and post if you have any questions!
