Contribute in GitHub:
Open doc issue|Edit online
Sending notifications
You can deliver a notification to every registered Listener. Here is a list of notification delivery parameters.
Sending notifications uses a method in com.ibm.di.api.APIEngine:
public static void sendNotification
(String type, String id, Object data, String configInstanceId)
This method creates a DIEvent. By this means, a notification is delivered to every Listener registered to receive the a particular type of notification. Notification delivery parameters include:
| Parameter name | Definition |
|---|---|
| type | Notification event type. |
| id | Notification event ID. |
| data | Notification event UserData object in the form of a Java™ object with additional information. |
| configInstanceId | Notification ConfigInstance ID to which the notification is bound. |
Table 1. Notification Delivery Parameters
The com.ibm.di.api.APIEngine method throws DIException if the type parameter is null. Calls to the method can be invoked either:
- Locally, from the IBM® Security Verify Directory Integrator Server JVM. This type of access includes scripting in AssemblyLine hooks and also uses the API from new Connectors implemented in Java and deployed on the IBM® Security Verify Directory IntegratorServer
- Remotely, from another JVM (on the local or a remote network computer), through Remote Method Invocation (RMI). This type of access uses solutions that:
- Connect remotely to IBM® Security Verify Directory Integrator
- Manage processes within IBM® Security Verify Directory Integrator
- Build business logic on top of IBM® Security Verify Directory Integrator
- Are applications dedicated only to IBM® Security Verify Directory Integrator
- Are applications that use IBM® Security Verify Directory Integrator to accomplish some of their goals