bc22220_.htm |
Last updated Friday, 21 July 2017In WebSphere® Message Broker Version 8.0, you can add newly discovered objects into an existing adapter component without modifying any existing objects. This facility is known as iterative discovery. You can rediscover certain objects for an inbound or outbound adapter.
The following table identifies the options that you can use to rediscover objects for an outbound adapter.
| Discovery option | Existing XSD files affected | Description |
|---|---|---|
| BAPI | None | Rediscovery is possible. The addition of another BAPI does not require any existing XSD file to be replaced. |
| BAPI (Wrapper) | SAPBusinessObjectNameWrapper.xsd | By default, this option is cleared. Rediscovery is possible provided that you do not change the name of the business object. |
| BAPI (Work Unit) | SAPBusinessObjectNameTxn.xsd | Rediscovery is possible provided that you do not change the name of the business object. |
| BAPI (Result Set) | All XSD files need to be replaced | Incremental rediscovery is not possible because you can specify only two objects (Query and Response). |
| ALE passthrough IDoc | None | Rediscovery is possible provided that you do not change configuration parameters such as qRFC, which changes ASI annotations on top-level objects. |
| ALE | None | Rediscovery is possible provided that you do not change configuration parameters such as qRFC, which changes ASI annotations on top-level objects. |
| Advanced event processing (AEP) | None | Rediscovery is possible provided that you do not change configuration parameters such as the function module name, which changes ASI annotations on top-level objects. |
| Query interface for SAP Software (QISS) | None | Rediscovery is possible provided that you do not change configuration parameters such as custom function name, which changes ASI annotations on top-level objects. |
The following table identifies the options that you can use to rediscover objects for an inbound adapter.
| Discovery option | Existing XSD files affected | Description |
|---|---|---|
| ALE events: create, update, or delete | None | Rediscovery is possible if you add a new IDoc but do not change Create, Read, Update, or Delete operations on previously discovered IDocs. |
| ALE passthrough | All XSD files need to be replaced | Rediscovery is possible, but you can specify only one IDoc. The IDoc is treated as opaque binary. Ensure that you select the option to replace all files. |
| AEP | None | Rediscovery is possible because the addition of another IDoc does not change existing XSD files. |
| BAPI | None | Rediscovery is possible if you add a new BAPI and do not change Create, Read, Update, or Delete operations on previously discovered BAPIs. |
Last updated Friday, 21 July 2017