The imports and exports created by the enterprise service discovery wizard are related at run time to the inbound and outbound processing of events by a resource adapter.
In a development environment like WebSphere Integration Developer, imports and exports are the reference point when discussing the relationship between an application in WebSphere Integration Developer and an external application. In a runtime environment such as WebSphere Process Server, the inbound and outbound processing of events form that reference point. There is a correlation between these reference points: selecting an outbound service type when you create an EIS binding will result in the creation of an import and selecting an inbound service type when you create an EIS binding will result in the creation of an export.
The following table summarizes the correlation between these terms and explains why the creation of an import is determined by an outbound service type and the creation of an export is determined by an inbound service type.
Selection of an outbound or inbound service type | Creation of an import or export | Explanation |
---|---|---|
Outbound | Import | An import means that WebSphere Integration Developer will be sending transactions to an external system represented in WebSphere Integration Developer by the import. Invoking a transaction will result in sending data outward from the WebSphere Integration Developer application to the external application on an EIS system. Therefore, it is an outbound transaction and will result at run time in the outbound processing of events. |
Inbound | Export | An export means that WebSphere Integration Developer will be receiving transactions from an external system represented in WebSphere Integration Developer by the export. Invoking a transaction from this external application will result in having data stream inwards to the WebSphere Integration Developer application. Therefore, it is an inbound transaction and will result at run time in the inbound processing of events. |