When can we bypass the interface mapping?

[xinjiang_li]

Hi gurus,

When can we bypass the interface mapping?

Can we do that when the structure of outbound interface and inbound interface are the same? If so, we don't need to create message mapping and interface mapping in IR and populate interface mapping of interface determination in ID?

Thanks in advance.

[Former Member]

Hi,

As already many people explained to u here,

When there is no transformation is required from source to target(i.e., no changes u want to make for the payload) then

u will think of a interface without any Interface mapping., inturn no message mappng.

Babu

[xinjiang_li]

Thanks all. That does make sense.

In our project, many scenarios need us to create the message mapping and interface mapping, which is very time-consuming based on the requirement that sender structure and receiver structure are totally same except the name of the message type or message interface.

Do we have a good method to create all the objects in one step just like the config wizard in integration directory?

Thanks.

[samiullah_qureshi]

Do we have a good method to create all the objects in one step just like the config wizard in integration directory?

Sorry to say that, but i dont think there is a way to do that in one step.

However, if fields names are same in ur sender and receiver structure and ur mapping is direct mapping(without any logic in between) then u can use header mapping technique.

In header mapping u have to select header nodes from source and target message. Then select Header mapping button(which is second button above ur source message). It will map all the fields in the substructures of the selected nodes which are having identical field names.

This will reduce ur development time for message mapping.

[xinjiang_li]

Hi Samiullah,

Do you mean the header mapping in integration directory when you talk about header mapping? It seems it's about party and service. Maybe you only mean that automatic mapping button in message mapping editor, right? Even that button make life easier, I'm still lazy to choose source message, target message, source interface, targ interface, mapping program... especially when we have many scenarios.

[samiullah_qureshi]

I meant hearder mapping button in ur message mapping editor of IR.

Yeah, i can understand it makes us lazy when number of interfaces are large. But it is part of our job, we have to live with it

Edited by: Samiullah Qureshi on Oct 26, 2010 9:09 AM

[Former Member]

Hi,

>>>When can we bypass the interface mapping?

When the strucutre(MessageType) of your outbound interface and inbound interface is the same, then you do not need to provide the interface mapping. However, you have to create the interface determination to determine inbound interface for corresponding outbound interface. while creating the interface determination, you can manually type in the dummy value of the interface name and namespace. No, operation mapping is needed in this case.

>>>Can we do that when the structure of outbound interface and inbound interface are the same? If so, we don't need to create message mapping and interface mapping in IR and populate interface mapping of interface determination in ID?

To do this, there is no need to develop any objects in the ESR, you can refer dummy interfaces while configuration in the ID.

I hope this helps.

Regards, Gaurav.

[xinjiang_li]

Hi Kumar,

Do you mean that if the sender message and receiver message have the same structure (even if both message have different names), then we don't need to create mapping object ?

[Former Member]

Hi,

Do you mean that if the sender message and receiver message have the same structure (even if both message have different names), then we don't need to create mapping object ? 

Nope, this is not the case.

Only same structures will not suffice, they both should be the same message type itself, as at runtime, the message type carries the actual values.

-Supriya.

[Former Member]

Hi,

In simple words, when you don't have message mapping in between Outbound and Inbound interfaces, then you don't have to go for interface mapping.

Actually interface mapping is high level representation for message mapping with direction(as outbound and inbound interfaces are involved), so if message types of both the messages are same, then interface mapping is not required.

-Supriya.

[Former Member]

Hi,

Please check the below link:

http://saptechnical .com/Tutorials/XI/File2File/Demo1.htm

Thanks,

[Former Member]

Hi,

You can bypass interface mapping whenever source and target structure is the same. But in this case you need to maintain entry for inbound interface.

As Raja suggested, no need to develop any objects in ESR, you can refer dummy interfaces while configuration.

Regards,

Divyesh

[rajasekhar_reddy14]

>

> When can we bypass the interface mapping?

> Can we do that when the structure of outbound interface and inbound interface are the same? If so, we don't need to create message mapping and interface mapping in IR and populate interface mapping of interface determination in ID?

>

in this case you no need to create anything in ESR, create ID part, give some dummy SERVICE INTERFACE nam and ,Name space , just type manually.

in interface determination step no need to add operation mapping.

Regards,

Raj

[samiullah_qureshi]

If strucutre(MT) of ur outbound interface n inbound interface then u need not to provide the interface mapping interface determination. However, u have to create the interface determination to determine inbound interface for corresponding outbound interface.