In simple terms...
Integration Scenario represents one view of your complete integration scenario.
It includes all the components like business system, interfaces, business process etc.
You can import the same Integration scenario designed in IR to ID and use it for configuration purpose. No need to define all objects separately. ALL under one roof.
<b>1.</b> Integration Scenarios are definitely not just for documentation. With them, you avoid having to create the Configuration Objects manually (or even interface by interface, using wizard); you just run the scenario configurator, relate each application component to a business service/system/integration scenario, create/refer necessary Communication Channels and that's it;
<b>.2.</b> Of course you can use business services in Integration Scenario Configurator, but only for B2B communications. Hence, your application component must be set with "external" flag (same for action);
<b>3.</b> You don't "import" BPM from IS into ID. You just refer to the Integration Process as a service, meaning, the only information you have about IP in Integration Directory is its interfaces, inbound or outbound (output or input ones; actually they are all abstract);
Finally, for the actual question: an action reflects an execution within the integration scope, meaning, a system triggering an access to other system(s). In XI's scope, that execution means one interface, and that's exactly the information that goes into the action: the interface, its type (message interface, imported RFC/IDoc etc), whether it refers to an internal (reflecting an A2A scenario) or an external (reflecting a B2B scenario) system and whether it's an outgoing or incoming message (outbound or inbound, in the point of view of the application systems).
**************Award points,if found useful
Edited by: BVS on Apr 1, 2008 11:43 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.