When Developing Your Own Interaction with the Source
When you develop your own logic to interact with the source resource, the logic should include sending a document when a data change occurs within the resource. You define the document fields that you require for the notification. Be sure to include a field for the native ID to identify the changed object on the source.
After determining the fields that you need in the source native document (i.e., the notification), use Software AG Designer to define an IS document type for the native document. The logic you create to interact with the source resource can do one of the following to send the source native document:
Publish the source native document. If your logic publishes the source’s native document, define a publishable document type for the source’s native document. A trigger on the source
Integration Server subscribes to this publishable document type. When the trigger receives a document that matches the publishable document type for the source’s native document, it invokes the trigger service that builds the canonical document.
Directly invoke the service that builds the canonical document, When the service is directly invoked, the source’s native document is sent to the service as input. If your logic passes the native document to the service as input, the IS document type does not need to be publishable.
For more information about creating the service that your logic should invoke, see
Setting Up Key Cross-Referencing in the
Source
Integration Server .