UK Oracle User Group


Siebel Web Services – XML Attributes

18 May 2015

Oli from www.siebel-tech.com shares a neat little thing he discovered when importing attributes...

 

I building an External Web Service the other day, when I noticed that the message format exposed by the external application relied, rather heavily, on XML attributes...For example:

My HouseMy Street

1

2

3

4

5

6

7

8

9

10

 

  

    Bob

    Ollerenshaw

  

  

 

    My House

    My Street

  

 

I wanted to use the Declarative UI Data Mapper to bring this information into my Contact BC model and had immediate concerns about the use of attributes.

I needn’t have worried, as the WSDL import process does something rather clever with the Integration Object for the external message structure.

 

What I found was that the import wizard created IC fields for each of my attributes:

1

2

3

4

5

6

7

8

9

listOfCustomer

  listOfNamePart

    namePart

      type*

      namePart_Value

  listOfAddressLine

    addressLine

      lineNumber*

      addressLine_Value

The “type” and “lineNumber” IC fields have an “XML Style” property of “attribute”, allowing the EAI mapping engine to map between the IO instance and resulting XML message without losing the context of the data.

I was also then able to use the EAI Data Mapper, by means of a Source Component Search Spec, to retrieve the “first” and “last” names for use in my internal IO instance.

I love the integration capabilities of Siebel and have yet to find a requirement that cannot be met by declarative means.

 

Source: http://www.siebel-tech.com

We'd love to get your feedback on this; you'll need a UKOUG login to provide it, so if you don't have one, please click on 'create a web profile' first.

Top