cancel
Showing results for 
Search instead for 
Did you mean: 

Integration Scenario's utility in IR/ID ?? & Communication Channel

Former Member
0 Kudos

Hi All,

Please clear the following doubt about integration scenario and communication channel.

1. Is it necessary to create integration scenario in the IR(design) and then to import it in the ID(configuration) ?

Is it possible to create the integration scenario in the ID without even mentioning the same in the IR ?

2. During the design phase in the ID we get the option to create the communication channel tempelate, What is the purpose of it ? What if we create the communication channel in ID wihout using the IR option... ?

Thanks and Regards,

Mona

Accepted Solutions (0)

Answers (1)

Answers (1)

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

>>>1. Is it necessary to create integration scenario in the IR(design) and then to import it in the ID(configuration) ?

no

>>>>What if we create the communication channel in ID wihout using the IR option... ?

no problem this is a standard

Regards,

michal

former_member206604
Active Contributor
0 Kudos

Hi,

Michal had already answered you questions to the point. I just thought of adding few words..

Integration Scenario basically helps you to define the integration flow and you can use the same during the configuration> Because of this Ur ID work will be simple. As Michal said this is not mandatory and you can goahead without a Integration Scenario.

For Eg:

You think of a development enviorinment that there different consultant for Design and Config. I mean the person who is designing will not be doing the config... In this kind of situation how come the config consultant knows which interface to use where... say for instance if you use BPM it really hard to understand it. So either he needs to have a clear documentation with the clear name before he could do the configuration. The integration scenarios helps a lot in this case... The config guy just have to give few parameters and click next, next and done.

Thanks,

Prakash