CPA Event Registration 

Use

Collaboration profile agreement events (CPA events) display changes to the configuration data, for example, the creation or deletion of a communication channel. Such a change generally leads to a change in the underlying physical connection and its processing threads.

Integration

If you do not use this mechanism, the adapter must poll itself to keep the number of sender channels and their configuration data up to date.

Features

●     To use the CPA event mechanism, you must provide your adapter with a class that implements the com.sap.aii.af.service.administration.api.cpa.ChannelLifecycleCallback interface. This is demonstrated in the example adapter.

Open XIConfiguration.java and search for the character string CS_CPACB.

●     The adapter must then register the class that manages the configuration of all the adapter’s channels with the Adapter Administration and Monitoring (AAM) framework of the Adapter Framework by using registerAdapter(). See also: Connecting to the Communication Channel Monitor.

This is demonstrated in the example adapter.

Open XIConfiguration.java and search for the character string CS_CPAREG.

The introduction of the communication channel monitor means that the interface com.sap.aii.af.service.cpa.ChannelLifecycleCallback and the CPA registration using CallbackController.registerCallback(adapterType,adapterNamespace,callBackImpl) that are recommended up to XI 3.0 SP16 are wrapped by the corresponding AAM interfaces and classes. Adapters that you convert to the AAM framework and any new adapters should use the AAM interfaces. These interfaces are implemented in the example adapter as of SP17. The old interfaces and classes are still provided to ensure compatibility.