<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/da/onlinemanual/000500b" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Synchronization Server - User Tasks</Title>
		<Keyword ContextSensitive="No"><Level1>Synchronization Server</Level1>
		</Keyword>
	</Header>
	<AimSection><Paragraph class="Default">This manual topic describes a number of typical user tasks. For each task, the sessions and commands to be used are mentioned.</Paragraph>
	</AimSection>
	<GeneralSection><SectionTitle>Change the settings for a synchronization object</SectionTitle>
		<Paragraph class="Default">In the <Link href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</Link> session, you can define a synchronization object. Then create the runtime using the command in that session. Normally this task is not done via the Synchronization Server user interface, because a synchronization object is created automatically when a PublishChanges request arrives for a business object.</Paragraph>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">Before you can start publishing, the audit profile must be converted to runtime. This is an application administrator's task, which may impact end users of ERP LN. To convert the audit profile to runtime, you must run the <Link href="/baanerp/tt/aud/ttaud3200s000" role="session">Create Runtime Audit Definitions (ttaud3200s000)</Link>, which can be started from the <Link href="/baanerp/tt/aud/ttaud3110m000" role="session">Audit Profiles (ttaud3110m000)</Link> session. After the setup and the conversion to runtime, run a test through the <GUIRef href="/baanerp/da/nch/danch2510m000#danch2212m000" role="command">Test Synchronization Object</GUIRef> command in the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> session. Events will be written to a file and the contents of that file will be displayed after stopping the server.</Paragraph>
		</Note>
	</GeneralSection>
	<GeneralSection><SectionTitle>Start publishing</SectionTitle>
		<Paragraph class="Default">Run the <GUIRef href="/baanerp/da/nch/danch2510m000#command.start.changes" role="command">Start</GUIRef> command in the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> details session. If a range of servers must be started and/or a specific starting moment is required, you can start the <Link href="/baanerp/da/nch/danch2213m000" role="session">Start Publishing (danch2213m000)</Link> session from the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> overview session.</Paragraph>
		<List><ListIntro>A specific starting moment is needed if:</ListIntro>
			<ListItem>The server did not run before and should start at some moment in the past instead of the current moment. E.g. publish all events using transactions executed since the beginning of this week.</ListItem>
			<ListItem>The server ran before but has a large backlog. For example, if it has not been running for a month then it could be started at the current time, instead of continuing where it stopped (provided the clients for the change events do not need the events from that month anymore).</ListItem>
			<ListItem>A range of servers must be started at the same point in time, for example, because the business objects are related and consequently the change events may be interdependent.</ListItem>
		</List>
	</GeneralSection>
	<GeneralSection><SectionTitle>View Status and Solve Issues</SectionTitle>
		<Paragraph class="Default">View the status (whether the server is running or not) in the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> details session.</Paragraph>
		<Paragraph class="Default">If needed, you can view the history by starting the <Link href="/baanerp/da/nch/danch2520m000" role="session">SyncChanges Server Runs (danch2520m000)</Link> session. Through that session, you can also view the log file for each run, which contains the exceptions that occurred.</Paragraph>
		<Paragraph class="Default">If needed, you can reset the complete status of the synchronization object via the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> details session.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Change a synchronization object</SectionTitle>
		<Paragraph class="Default">You can change the settings for an existing synchronization object via the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> details session. After such a change, if the business object, selection or filter was changed, the configuration library and audit profile are regenerated.</Paragraph>
		<Paragraph class="Default">Finally, if a server is running for processing change events, that server must be stopped and started again (continued) to make use of the new settings.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Make sure servers keep running</SectionTitle>
		<Paragraph class="Default">Add the <Link href="/baanerp/da/nch/danch2210m000" role="session">Check and Continue Servers (danch2210m000)</Link> session to a job that is executed according to a predefined interval or calendar.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Cleanup</SectionTitle>
		<Paragraph class="Default">To clear the history, use the <Link href="/baanerp/da/nch/danch2220m000" role="session">Purge Server Runs (danch2220m000)</Link> session. You can start this session through the <GUIRef href="" role="manual">History</GUIRef> command in the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> details session.</Paragraph>
		<Paragraph class="Default">Do not clear the last run, unless you want to reset the current status. After clearing the last run, the server cannot continue anymore from the point where it stopped last time.</Paragraph>
		<Paragraph class="Default">You can also reset the synchronization object (including the current status) through the <GUIRef href="/baanerp/da/nch/danch2510m000#command.reset" role="command">Reset</GUIRef> command in the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> details session. This command removes all history and status data.</Paragraph>
		<Paragraph class="Default">You can cleanup the Audit Trail through the Audit Management sessions.</Paragraph>
		<Paragraph class="Default">You do not have to cleanup any transaction data for the Synchronization Server, because after an event is passed on to the publication channel (bus component) it is not available anymore in the Synchronization Server.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Stop publishing</SectionTitle>
		<Paragraph class="Default">Run the <GUIRef href="/baanerp/da/nch/danch2510m000#command.stop.changes" role="command">Stop</GUIRef> command in the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> details session. If a range of servers must be stopped, you can start the <Link href="/baanerp/da/nch/danch2214m000" role="session">Stop Publishing (danch2214m000)</Link> session from the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> overview session.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Delete a synchronization object</SectionTitle>
		<Paragraph class="Default">If the server is running, first stop it through the <GUIRef href="/baanerp/da/nch/danch2510m000" role="session">Synchronization Objects (danch2510m000)</GUIRef> details session. Then delete the synchronization object via the overview session.</Paragraph>
		<Paragraph class="Default">Normally this action is not required, because a synchronization object is deleted automatically when an UnpublishChanges request arrives for a business object.</Paragraph>
	</GeneralSection>
	<RelatedTopics><SectionTitle>
                              Related topics
                           </SectionTitle>
		<RelTopic><Link href="/baanerp/da/onlinemanual/000500a" role="manual">Synchronization Server - User Interface Overview</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/da/onlinemanual/000500" role="manual">Synchronization Server Overview</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
