<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tl/onlinemanual/event_monitoring" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Event Monitoring</Title>
		<Keyword ContextSensitive="No"><Level1>Event Monitoring</Level1>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Event</Level1>
			<Level2>monitor</Level2>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph class="Default">Although the status of the event publishing can be monitored, by default you cannot see in Infor Enterprise Server what happened to a specific triggered event. Has the event already been published, or is the event still in the queue, or did an error occur?</Paragraph>
		<List><ListIntro>The basic functionality is as follows:</ListIntro>
			<ListItem>In the <Link href="/baanerp/tl/bct/tlbct5500m000" role="session">Event Subscriptions (tlbct5500m000)</Link> details session, the end commit time of the publisher is visible. The end commit time indicates that events from all transactions committed on or before that moment were processed.</ListItem>
			<ListItem>If an error occurs, it is handled in Integration 6.2. Depending on the configuration and type of error, it is either sent to an error handler bus component, or a retry is done after some time, or the error (including the message as it was when the error occurs) is written to an OpenWorld log file.</ListItem>
			<ListItem>If a subscription exists, an event is never lost. Either the event is still in the queue, or delivered to the specified destination, or is handled as an error in Integration 6.2.</ListItem>
		</List>
		<List><ListIntro>Event Monitoring adds the following:</ListIntro>
			<ListItem>An <Link href="/baanerp/tl/bct/tlbct5530m000" role="session">Events (tlbct5530m000)</Link> session is available. You can view the events that are in the queue to be published from ERP LN.</ListItem>
			<ListItem>An <Link href="/baanerp/tl/bct/tlbct5505m000" role="session">Event Publishing Settings (tlbct5505m000)</Link> session is available, where you can configure to keep the event history. If the history is kept, processed events can also be viewed in the <GUIRef href="/baanerp/tl/bct/tlbct5530m000" role="session">Events (tlbct5530m000)</GUIRef> session.</ListItem>
		</List>
		<Paragraph class="Default">Note that this functionality is an add-on and does not replace the basic functionality.</Paragraph>
	</GeneralSection>
	<RelatedTopics><SectionTitle>
                              Related topics
                           </SectionTitle>
		<RelTopic><Link href="/baanerp/tl/bct/tlbct5530m000" role="session">Events (tlbct5530m000)</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tl/bct/tlbct5505m000" role="session">Event Publishing Settings (tlbct5505m000)</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tl/bct/tlbct5500m000" role="session">Event Subscriptions (tlbct5500m000)</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
