<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tl/bct/tlbct5500m000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Event Subscriptions (tlbct5500m000)</Title>
		<Keyword ContextSensitive="No"><Level1>Event Subscriptions</Level1>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Event Publishing Services</Level1>
			<Level2>subscriptions to</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Publishers</Level1>
			<Level2>subscriptions to publishing services</Level2>
		</Keyword>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to view and maintain subscriptions to event publishing services.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph class="Default">You start this session from the <GUIRef href="" role="manual">Tools</GUIRef>/ <GUIRef href="" role="manual">Integration Tools</GUIRef>/ <GUIRef href="" role="manual">Event Publishing</GUIRef> menu.</Paragraph>
			<Paragraph class="Default">This session shows the subscriptions to event publishing services, which are available in the ERP LN application. These services are referred to as <Emphasis>publishers</Emphasis>.</Paragraph>
			<Paragraph class="Default">The subscriptions are specific to a business object of a particular ERP LN company. All fields are presented in a read-only mode, so you can only view the subscription properties. To edit a subscription, you use the <GUIRef href="/baanerp/tl/bct/tlbct5220m000" role="session">Subscribe (tlbct5220m000)</GUIRef> session.</Paragraph>
			<Paragraph class="Default">For more information on subscriptions to event publishing services, refer to help topic <Link href="/baanerp/tl/onlinemanual/event_subscriptions" role="manual">How to subscribe to an event publishing service</Link>.</Paragraph>
			<Paragraph class="Default">This session has a details mode and an overview mode.</Paragraph>
			<GeneralSection><SectionTitle>Overview session</SectionTitle>
				<Paragraph class="Default">The Event Subscriptions (tlbct5500m000) session starts in the overview mode. The overview mode can contain multiple Event Subscription records, which show the following fields:</Paragraph>
				<List><ListItem><GUIRef href="" role="manual">Company</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="" role="manual">Business Object</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="" role="manual">Event Consumer</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="" role="manual">Destination</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="" role="manual">Publisher Status</GUIRef>
					</ListItem>
				</List>
				<Paragraph class="Default">For a description of these fields, refer to the <GUIRef href="" role="manual">Subscription</GUIRef> tab and the <GUIRef href="" role="manual">Publisher</GUIRef> tab of the details session. To view the subscription records from another company, specify the number of this company in the <GUIRef href="" role="manual">Event Subscriptions - Find</GUIRef> dialog box (on the <GUIRef href="" role="manual">Edit</GUIRef> menu, click <GUIRef href="" role="manual">Find</GUIRef> ).</Paragraph>
				<Paragraph class="Default">In the overview mode, you can start other sessions from the <GUIRef href="" role="manual">Specific</GUIRef> menu to stop or start publishers, to check the current status of publishers and to create or edit subscriptions. To start these sessions for the selected subscription, use the following commands:</Paragraph>
				<List><ListItem><GUIRef href="" role="manual">Check and Continue Publishing</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="" role="manual">Start/Stop Publishing</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="" role="manual">Subscribe</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="" role="manual">Unsubscribe</GUIRef>
					</ListItem>
				</List>
				<Paragraph class="Default">For a more detailed description of these commands, refer to the <GUIRef href="" role="manual">Subscription</GUIRef> tab of the details session.</Paragraph>
				<Paragraph class="Default">In the overview session, double click a subscription to start the details session for this subscription.</Paragraph>
			</GeneralSection>
			<GeneralSection><SectionTitle>Details session</SectionTitle>
				<Paragraph class="Default">The details session shows the complete configuration of a single event subscription and has separate tabs for the Subscription data, the Publisher data and the Technical Details data.</Paragraph>
			</GeneralSection>
		</GeneralSection>
	</HelpTopic>
	<Forms><Form><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Subscription</Title>
				<Keyword ContextSensitive="No"><Level1>Event Subscriptions</Level1>
				</Keyword>
				<Keyword ContextSensitive="No"><Level1>Event Publishing Services</Level1>
					<Level2>subscriptions to</Level2>
				</Keyword>
			</Header>
			<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">This tab contains the properties of the selected subscription. For a more detailed description, refer to the <GUIRef href="/baanerp/tl/bct/tlbct5220m000" role="session">Subscribe (tlbct5220m000)</GUIRef> session.</Paragraph>
				</AimSection>
				<GeneralSection><Note><SectionTitle>
                                          Note
                                       </SectionTitle>
						<Paragraph class="Default">A subscription is identified by the business object and the ERP LN company to which this business object belongs. In a specific ERP LN company, it is therefore not possible to create multiple subscriptions for one business object.</Paragraph>
					</Note>
				</GeneralSection>
			</HelpTopic>
			<Fields><FieldHelp ID="tlbct500.comp" OtherIDs="tlbct510.comp"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Company</Title>
					</Header>
					<FuncDesc>The number of the ERP LN company from which events are published through the business object.</FuncDesc>
				</FieldHelp>
				<FieldHelp ID="tlbct500.cbde" OtherIDs="tlbct510.cbde"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Business Object</Title>
					</Header>
					<FuncDesc>The business object that provides the event publishing service.</FuncDesc>
				</FieldHelp>
				<FieldGroup><Title>Subscription settings</Title>
					<FieldHelp ID="tlbct500.evco" OtherIDs="tlbct510.evco"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Event Consumer</Title>
						</Header>
						<FuncDesc>The name of the application that consumes the published event messages.</FuncDesc>
					</FieldHelp>
					<FieldHelp ID="tlbct500.dest" OtherIDs="tlbct510.dest"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Destination</Title>
						</Header>
						<FuncDesc>The address the event messages are sent to.</FuncDesc>
					</FieldHelp>
					<FieldHelp ID="event.actions"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Event Actions</Title>
						</Header>
						<FuncDesc>The actions that can be performed on the displayed business object and that trigger an event.</FuncDesc>
					</FieldHelp>
				</FieldGroup>
				<FieldGroup><Title>Selection and Filter</Title>
					<FieldHelp ID="selection"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Selection</Title>
						</Header>
						<FuncDesc>The attributes and components that will be included in the published event messages.</FuncDesc>
					</FieldHelp>
					<FieldHelp ID="tlbct500.filt"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Filter</Title>
						</Header>
						<FuncDesc>The filter that determines from which instances event messages are published. The filter is in an XML format that is specific to ERP LN and that conforms to the BDE standards of ERP LN.</FuncDesc>
					</FieldHelp>
				</FieldGroup>
			</Fields>
			<FormCommands><CommandHelp ID="tlbct5200m000"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Check and Continue Publishing</Title>
					</Header>
					<FuncDesc>Starts the Check and Continue Publishing (tlbct5200m000) session. In this session, you can check the status of all available event publishing services (publishers).</FuncDesc>
				</CommandHelp>
				<CommandHelp ID="tlbct5210m000"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Start/Stop Publishing</Title>
					</Header>
					<FuncDesc>Starts the Start/Stop Publishing (tlbct5210m000) session. In this session, you can start or stop event publishing services of a specified range of subscriptions. When you stop a publishing service, the status publisher status becomes 'Paused'.</FuncDesc>
				</CommandHelp>
				<CommandHelp ID="execute.subscribe"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Subscribe</Title>
					</Header>
					<FuncDesc>Starts the Subscribe (tlbct5220m000) session. In this session, you can create and edit subscriptions.</FuncDesc>
				</CommandHelp>
				<CommandHelp ID="execute.unsubscribe"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Unsubscribe</Title>
					</Header>
					<FuncDesc>Deletes the selected subscription.</FuncDesc>
					<SimpleSection><Paragraph class="Default">You are asked to confirm the removal of the subscription. After confirmation, ERP LN sends a unsubscribe request to the business object and subsequently informs you about the result. Among other things, the result will depend on authorization settings and dependency constraints.</Paragraph>
						<Paragraph class="Default"><Emphasis>Caution</Emphasis>
						</Paragraph>
						<Paragraph class="Default"><Emphasis>After the unsubscribe command is carried out, the operation will be permanent. You cannot undo the command.</Emphasis>
						</Paragraph>
					</SimpleSection>
				</CommandHelp>
			</FormCommands>
		</Form>
		<Form><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Publisher</Title>
				<Keyword ContextSensitive="No"><Level1>Publishers</Level1>
					<Level2>subscriptions</Level2>
				</Keyword>
				<Keyword ContextSensitive="No"><Level1>Event Publishers</Level1>
					<Level2>subscriptions</Level2>
				</Keyword>
			</Header>
			<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">This tab contains the properties of the event publishing service (publisher) of the current subscription.</Paragraph>
				</AimSection>
			</HelpTopic>
			<Fields><FieldGroup><Title>Publisher Settings</Title>
					<FieldHelp ID="tlbct510.pnam"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Audit Profile</Title>
						</Header>
						<FuncDesc>The name of the audit profile used to monitor event actions.</FuncDesc>
						<SimpleSection><Paragraph class="Default">To view the audit profiles, run the Audit Profiles (ttaud3110m000) session.</Paragraph>
						</SimpleSection>
					</FieldHelp>
					<FieldHelp ID="tlbct510.freq"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Publication Frequency</Title>
						</Header>
						<FuncDesc>The frequency used to monitor the event actions. The frequency is expressed in the number of seconds after which a check for new events will be done.</FuncDesc>
					</FieldHelp>
					<FieldHelp ID="tlbct510.pref"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Process Reference</Title>
						</Header>
						<FuncDesc>The number of the event publishing process.</FuncDesc>
						<SimpleSection><Paragraph class="Default">You can use this number when interpreting a trace file, if the tracing is carried out for multiple processes.</Paragraph>
						</SimpleSection>
					</FieldHelp>
					<FieldHelp ID="tlbct510.traf"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Trace File</Title>
						</Header>
						<FuncDesc>The full path of the trace file in which the event publishing process is logged.</FuncDesc>
					</FieldHelp>
				</FieldGroup>
				<FieldGroup><Title>Publisher Status</Title>
					<FieldHelp ID="tlbct510.stat"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Publisher Status</Title>
						</Header>
						<FuncDesc>The current status of the event publishing service (publisher).</FuncDesc>
						<SimpleSection><Paragraph class="Default">The status can have the following values:</Paragraph>
							<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><TBODY><TR><TH rowspan="1" colspan="1">Status</TH>
										<TH rowspan="1" colspan="1">Description</TH>
									</TR>
									<TR><TD rowspan="1" colspan="1">Running</TD>
										<TD rowspan="1" colspan="1">Publisher is started. To verify whether the publisher is actually running properly, use the <GUIRef href="" role="manual">Check Process</GUIRef> command.</TD>
									</TR>
									<TR><TD rowspan="1" colspan="1">Interrupted</TD>
										<TD rowspan="1" colspan="1">Publisher is not running because it has been interrupted by an external factor, such as a bshell termination.</TD>
									</TR>
									<TR><TD rowspan="1" colspan="1">Error</TD>
										<TD rowspan="1" colspan="1">Publisher is not running because a fatal error occurred in the service process.</TD>
									</TR>
									<TR><TD rowspan="1" colspan="1">Paused</TD>
										<TD rowspan="1" colspan="1">Publisher is paused, which means temporary stopped by a user.</TD>
									</TR>
								</TBODY>
							</TABLE>
						</SimpleSection>
					</FieldHelp>
					<FieldHelp ID="tlbct510.strt"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Start Time</Title>
						</Header>
						<FuncDesc>The date and time the publisher started. The publisher will process all events that occurred in transactions that are committed on or after that time.</FuncDesc>
					</FieldHelp>
					<FieldHelp ID="tlbct510.endt"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">End Time</Title>
						</Header>
						<FuncDesc>The date and time from the last event that was published. While the publisher is running, it will regularly update the End Time after publishing a number of events. If the publisher is not running, it will use the End Time to continue processing, so no events are lost as long as the subscription exists.</FuncDesc>
					</FieldHelp>
					<FieldHelp ID="tlbct510.reft"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Refresh Time</Title>
						</Header>
						<FuncDesc>The moment when the publisher must refresh its state. If the publisher's end time equals to its refresh time, the publisher is refreshed as defined by the <GUIRef href="" role="manual">Refresh Type</GUIRef> value.</FuncDesc>
					</FieldHelp>
					<FieldHelp ID="tlbct510.rtyp"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Refresh Type</Title>
						</Header>
						<FuncDesc>Indicates whether the publishing process must refresh its state. The refresh type indicates what the publisher must do at refresh time.</FuncDesc>
						<SimpleSection><Paragraph class="Default">The refresh type can have the following values:</Paragraph>
							<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><TBODY><TR><TH rowspan="1" colspan="1">Value</TH>
										<TH rowspan="1" colspan="1">Description</TH>
									</TR>
									<TR><TD rowspan="1" colspan="1">None</TD>
										<TD rowspan="1" colspan="1">No refresh is needed.</TD>
									</TR>
									<TR><TD rowspan="1" colspan="1">New</TD>
										<TD rowspan="1" colspan="1">The publisher must use new subscription settings after the moment indicated by the Refresh Time.</TD>
									</TR>
									<TR><TD rowspan="1" colspan="1">Pause</TD>
										<TD rowspan="1" colspan="1">The publisher must pause.</TD>
									</TR>
								</TBODY>
							</TABLE>
						</SimpleSection>
					</FieldHelp>
				</FieldGroup>
			</Fields>
			<FormCommands><CommandHelp ID="check.process.status"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Check Process</Title>
					</Header>
					<FuncDesc>Check the status of the current event publishing process.</FuncDesc>
				</CommandHelp>
				<CommandHelp ID="pause.process"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Pause Process</Title>
					</Header>
					<FuncDesc>Temporary stops the current publisher. The status of the publisher changes to <Code>Paused</Code>. This means that all occurring events remain in a queue and will not be processed until the publisher is reactivated.</FuncDesc>
					<SimpleSection><Paragraph class="Default">The command only applies to running publishers.</Paragraph>
					</SimpleSection>
				</CommandHelp>
				<CommandHelp ID="continue.process"><Header>
						<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Reactivate Process</Title>
					</Header>
					<FuncDesc>Starts the current publisher. The publisher will continue at the point where it was paused (or stopped because of an error). So, it will first process the backlog of events that are waiting in the queue before processing new events.</FuncDesc>
					<SimpleSection><Paragraph class="Default">The command applies to paused publishers and to publishers with status Error or Interrupted.</Paragraph>
					</SimpleSection>
				</CommandHelp>
			</FormCommands>
		</Form>
		<Form><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Technical Details</Title>
				<Keyword ContextSensitive="No"><Level1>Publishers</Level1>
					<Level2>business interface definition</Level2>
				</Keyword>
				<Keyword ContextSensitive="No"><Level1>BID</Level1>
				</Keyword>
				<Keyword ContextSensitive="No"><Level1>Business Object Definition</Level1>
				</Keyword>
				<Keyword ContextSensitive="No"><Level1>Event Publishers</Level1>
					<Level2>business interface definition</Level2>
				</Keyword>
			</Header>
			<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">This tab contains the metadata of the Business Interface that provides the event publishing service.</Paragraph>
				</AimSection>
			</HelpTopic>
			<Fields><FieldGroup><Title>Technical Details</Title>
					<FieldHelp ID="tlbct500.meta" OtherIDs="tlbct510.meta"><Header>
							<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Meta Data</Title>
						</Header>
						<FuncDesc>Meta data as used by the publisher. This data is only relevant if vendor support is required.</FuncDesc>
					</FieldHelp>
				</FieldGroup>
			</Fields>
		</Form>
	</Forms>
</Session>
