| # How to subscribe to an event publishing service This section explains how to subscribe an application to an event publishing service of an LN Business Interface. Event Publishing Concept A Business Object can publish event messages to report state changes on its instances or to request asynchronous services, such as an update, from external applications. Other applications can subscribe to these event messages. Such subscriptions are referred to as Event Subscriptions. An event subscription for a business object in an LN company means that another application is interested in events from the company for that business object. So it doesn’t mean the specified business object will receive events, but that the specified business object will publish events, because another party is subscribed to those events. In LN, business objects are represented by Business Interfaces. Two types of Business Interfaces are distinguished: BDE Business Interfaces which are business interfaces that use BDE-specific XML messages to exchange business data. BOD Business Interfaces which are business interfaces that use standard OAGIS BOD messages to exchange business data. Although BODs for LN are implemented through business objects, they are not managed in the Infor Enterprise Server user interface. Therefore, they are not discussed further here or in the session help. Standard event messages are published to spread information on state changes of business objects. Custom event messages are used to carry out an asynchronous service request on a business object of an external application. Event Publishing through BDE interfaces A BDE Business Interface can publish event messages when changes occur to its instances, for example, the removal of a particular BDE object. The message indicates what has changed and this information is sent to another application. To receive event messages, the application requires a subscription to the corresponding publishing service. Applications that subscribed to an event publishing service are referred to as the event consumers of that particular service. The event messages are used to exchange business data with BDE Business interfaces in an XML vocabulary that is based on the BDE standard. In addition to the business data, each event message includes controlling data such as a timestamp and the event action. The event action can either be a standard action (create, change or delete) or a business object specific event action (such as approve or cancel). To receive event messages from a BDE interface on an LN server, an external application must be connected to the LN server through the Infor Integration infrastructure and must have taken a subscription to the involved BDE event publishing service. To create a subscription for a particular application, you must specify the name of the application as the event consumer and the address of the server that runs the application as the destination of the publishing service. This address is represented by an Infor Integration Bus Component (a communication channel specific to Infor Integration). For more information on the LN event publishing services of BDE Business Interfaces, refer to the following guides: Infor Integration- Integration Guide for BDE Clients (U9051 US) Infor LN BODs and BDEs Development Guide (U9215 US) To create a subscription These steps describe how you create a subscription to a BDE event publishing service. These services are also referred to as publishers. The applications that receive the published event messages are referred to as the event consumers. Step 1. Start Event Subscription session Start the Event Subscriptions (tlbct5500m000) session from the Tools/ Integration Tools/ Event Publishing menu. This session lists the current subscriptions for a particular LN company. Step 2. Start Subscribe session To start the Subscribe (tlbct5220m000) session, click Subscribe on the appropriate menu of the Event Subscriptions (tlbct5500m000) session. Step 3. Create a Subscription To create a subscription, specify the required fields of the Event Subscriptions (tlbct5500m000) session and then click Subscribe. For more information, refer to Event Subscriptions (tlbct5500m000). |