cancel
Showing results for 
Search instead for 
Did you mean: 

doubt

Former Member
0 Kudos

hi

in some scenerios they are definig more msg interface , msg mapping ,interface determiniation, recevier determination....(both in simple scnerios and BPM scenerios)

what is necessity of creating it and in which case we will go for it...

plz help me.. i can't get with this point...

Accepted Solutions (1)

Accepted Solutions (1)

former_member187437
Contributor
0 Kudos

For most simple scenarios , you need to create the following.

<b>Design Objects:</b>

1. Data type

2. Message Type

3. Message interface (one for sender and one for receiver)

4. MEssage Mapping

5. Interface Mapping.

<b>

Configuration Objects:</b>

1. A business service.

2. 2 communcaiotn channels (for sender and reciever)

3. Sender agreement

4. Receiver agreement

5. INterface determination

6. Receiver determination

Answers (1)

Answers (1)

santhosh_kumarv
Active Contributor
0 Kudos

Hi limat...

>>more msg interface , msg mapping

In a scenario using BPM it neads atleast 3 message inteface 1 outbound, 1 inbound and 1 abstract message interface and if the outbound and inbound message type to BPM are diff the there needs one more abstract interface.. so the message interface keeps on adding up based on the requirement and scenario... it is not necessary to be constant in all the scenarios....

Message mapping also depends upon the scenario only...

>>interface determiniation, recevier determination

If there are multiple senders or receivers there is an necessity to have more number of ID and receiver determination

Eg: simple file to file without BPM:

ID: Sender: File -


> Receiver File.

simple file to file with BPM:

ID: Sender: File -


> BPM.

BPM -


> Receiver File.

Hence this keeps on adding up based upon our scenario...

Hope this clears your doubt.....

Regards

San

there is a Way.