<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/ads_microsoft_active_directory_service" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Microsoft Active Directory Service (ADS)</Title>
	</Header>
	<GeneralSection><SectionTitle>Introduction</SectionTitle>
		<Keyword type="section" order="IDADZAYB"><Level1>Microsoft Active Directory Service</Level1>
			<Level2>introduction</Level2>
		</Keyword>
		<List><ListIntro>This chapter describes Microsoft’s Active Directory Service management in ERP LN, and includes the following:</ListIntro>
			<ListItem>An overview of Microsoft’s Active Directory Service</ListItem>
			<ListItem>ADS in ERP LN
                              </ListItem>
			<ListItem>To find the ERP LN environment information in ADS</ListItem>
			<ListItem>To publish a UNIX server in the Infor Environment and Configuration Selector ( BECS )</ListItem>
			<ListItem>To maintain the ERP LN Windows configuration properties</ListItem>
		</List>
	</GeneralSection>
	<GeneralSection><SectionTitle>An overview of Microsoft’s Active Directory Service</SectionTitle>
		<Keyword type="section" order="IDA3ZAYB"><Level1>Microsoft Active Directory Service</Level1>
			<Level2>overview</Level2>
		</Keyword>
		<Paragraph class="Default">Microsoft’s Active Directory is the directory service for Microsoft’s Windows 200x Server. Microsoft’s Active Directory stores information about objects on the network and makes this information easy for administrators and users to find and use. Active Directory service (ADS) uses a structured data store as the basis for a logical, hierarchical organization of directory information.</Paragraph>
		<Paragraph class="Default">Network security is integrated with ADS through logon authentication and access control to objects in the directory. With a single network logon, administrators can manage directory data and organization throughout their network, and authorized network users can access resources anywhere on the network.</Paragraph>
		<GeneralSection><SectionTitle>ADS directory services</SectionTitle>
			<Paragraph class="Default">In ADS, a directory is a hierarchical structure that stores information about objects on the network. ADS provides the methods to store directory data and to make this data available to network users and administrators. For example, Active Directory stores information about user accounts, such as names, passwords, phone numbers, and so on, and enables other authorized users on the same network to access this information.</Paragraph>
			<List><ListIntro>Microsoft’s Active Directory Service has the following features:</ListIntro>
				<ListItem>A data store, also known as the directory, which stores information about Active Directory objects. These objects typically include shared resources such as servers, files, printers, and the network user and computer accounts</ListItem>
				<ListItem>A set of rules, the schema that defines the classes of objects and attributes contained in the directory, the constraints and limits on instances of these objects, and the format of their names.</ListItem>
				<ListItem>A global catalogue that contains information about every object in the directory. This enables users and administrators to find directory information regardless of which domain in the directory actually contains the data</ListItem>
				<ListItem>A query and index mechanism, so that objects and their properties can be published and found by network users or applications.</ListItem>
				<ListItem>A replication service that distributes directory data across a network. All domain controllers in a domain participate in replication and contain a complete copy of all directory information for their domain. Any change to directory data is replicated to all domain controllers in the domain.</ListItem>
				<ListItem>Integration with the security subsystem for a secure logon process to a network, as well as access control on both directory data queries and data modifications.</ListItem>
			</List>
			<Paragraph class="Default">For more information about Microsoft’s ADS, refer to the Microsoft documentation.</Paragraph>
		</GeneralSection>
	</GeneralSection>
	<GeneralSection><SectionTitle>ADS in ERP LN
                           </SectionTitle>
		<Keyword type="section" order="IDAN1AYB"><Level1>Microsoft Active Directory Service</Level1>
			<Level2>ADS in ERP LN</Level2>
		</Keyword>
		<List><ListIntro>
                                 ERP LN uses ADS for the following reasons:</ListIntro>
			<ListItem>ADS stores the client configuration settings.</ListItem>
			<ListItem>The ERP LN Logic Service publishes the connection points to the ERP LN software environments (BSE) in ADS.</ListItem>
		</List>
		<Paragraph class="Default">In ERP LN, the Active Directory Service (ADS) is a directory that you can use to store the client configuration settings that are available to all systems connected to a network. This enables you use the client configuration settings on other systems in the network. With ADS, users can access information on any system in the network. In other words, the network users are no longer tied to using their own client, with their own settings, in the network.</Paragraph>
		<Paragraph class="Default">The ERP LN Logic Service publishes the connection points to the BSE environments in ADS. Infor BW uses these connection points to connect to these environments. The Infor Environment and Configuration Selector ( BECS ) uses these connection points to display information about all available environments.</Paragraph>
		<GeneralSection><SectionTitle>Integration of ADS in ERP LN
                              </SectionTitle>
			<List><ListIntro>For the integration of ADS in ERP LN, the following components are used:</ListIntro>
				<ListItem>The Windows registry</ListItem>
				<ListItem>The ERP LN Logic Service</ListItem>
				<ListItem>Infor BW</ListItem>
				<ListItem>The Infor Environment and Configuration Selector ( BECS )</ListItem>
				<ListItem>A library with abstraction functions</ListItem>
			</List>
			<Paragraph class="Default">The ES Logic Service receives information about the available environments from the Windows registry, and publishes this information as connection points to the BSE environment in ADS. BW uses these connection points to connect to that environment, and BECS uses the connection points to display the available environments.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><FigIntro>The following figure provides a schematic overview of the integration in ERP LN:</FigIntro>
				<HTML:IMG width="343" height="323" SRC="../images/tr_graph_ads_integration_in_ssa_erp.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="tr_graph_ads_integration_in_ssa_erp.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/tr_graph_ads_integration_in_ssa_erp.gif" ID="IDAF5XBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">The ERP LN Logic Service publishes the services without any user interaction.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">To make sure that the directory is always available for a UNIX environment, you must at least use one Windows system as a directory server.</Paragraph>
			</Note>
		</GeneralSection>
		<GeneralSection><SectionTitle>Functionality ADS in ERP LN
                              </SectionTitle>
			<Paragraph class="Default">At startup, the ERP LN Logic service publishes the connection points in ADS for each environment on the server with information, such as the name of the server to connect to and the name of the BSE-environment. BW uses this information to set up a connection to the server.</Paragraph>
			<Paragraph class="Default">The information is no longer stored on the clients. In other words, if the name of the server changes, the name is updated in the directory object that the clients use, therefore, all clients are automatically connected to the new server. Without the directory, every client system must be reconfigured to use the new server.</Paragraph>
			<Paragraph class="Default">For each environment on a server, the ERP LN Logic Service creates an object in ADS. This object is of class serviceConnectionPoint. The objects are smaller than 1 KB. The objects in ADS are automatically updated at startup when the configuration of an ERP LN Software Environment (BSE) changes, for example, if you change the name of the server or the logon protocols.</Paragraph>
			<List><ListIntro>The ERP LN Logic Service uses the following string attributes:</ListIntro>
				<ListItemHead>cn</ListItemHead>
				<ListItem>You can use this string attribute to store the name of the environment that is published.</ListItem>
				<ListItemHead>serviceDNSName</ListItemHead>
				<ListItem>Use this string attribute to store the name of the server on which the environment is located.</ListItem>
				<ListItemHead>serviceBindingInformation</ListItemHead>
				<ListItem>Use this multivalued string attribute to store additional connection information. Currently, the port-number, protocol, portingset number, and the BSE-path is stored in this attribute, for example: <List><ListItem>Port: 512</ListItem>
						<ListItem>BSE: c:\BaanV</ListItem>
						<ListItem>Protocol: EXEC</ListItem>
						<ListItem>Portingset: 7.1b</ListItem>
					</List>
				</ListItem>
				<ListItemHead>keywords</ListItemHead>
				<ListItem><Paragraph class="Default">Administrators can use this multivalued string to perform queries. The ES Logic Service stores the company name ( Infor ) and the product name ( Infor ERP LN ) in this attribute.</Paragraph>
					<Paragraph class="Default">The names of classes and attributes must be unique in a company that uses ADS in ERP LN, which reduces the chance of clashes. However, this does not, however, guarantee that name clashes will never occur.</Paragraph>
				</ListItem>
			</List>
		</GeneralSection>
	</GeneralSection>
	<GeneralSection><SectionTitle>To find the ERP LN environment information in ADS</SectionTitle>
		<Keyword type="section" order="IDAU5AYB"><Level1>Microsoft Active Directory Service</Level1>
			<Level2>find the ERP LN environment information in ADS</Level2>
		</Keyword>
		<Paragraph class="Default">At startup, the ERP LN Logic service publishes the connection points in ADS for each environment on the server with information, such as the name of the server to connect to and the name of the BSE environment. BW uses this information to set up a connection to the server. The ES Logic Service publishes the services without any user interaction. In this example, the NTDEV.baan.com domain is used to explain ADSs features in ERP LN.</Paragraph>
		<List><ListIntro>To find the environments in ADS, take the following steps:</ListIntro>
			<ListItem>Log on as an administrator</ListItem>
			<ListItem>Click Start, Programs, Administrative Tools, Active Directory Users and Computers.</ListItem>
		</List>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">The server names in a domain must be unique.</Paragraph>
		</Note>
	</GeneralSection>
	<GeneralSection><SectionTitle>To publish a UNIX server in BECS
                           </SectionTitle>
		<Keyword type="section" order="IDAXABYB"><Level1>Microsoft Active Directory Service</Level1>
			<Level2>publish a UNIX server in BECS</Level2>
		</Keyword>
		<Paragraph class="Default">Typically, ADS is used for Windows servers. However, you can use the ERP LN Active Directory Service set-up utility to publish UNIX servers in the Infor Environment and Configuration Selector ( BECS ).</Paragraph>
		<List><ListIntro>To publish UNIX servers, take the following steps:</ListIntro>
			<ListItem>Log on as an administrator</ListItem>
			<ListItem>Start the Command Prompt</ListItem>
			<ListItem>Type: dssetup –publish [ ERP LN server description] [server name] [BSE directory]</ListItem>
			<ListItem>Start BECS – Infor Environment and Configuration Selector, to view the published ERP LN server</ListItem>
		</List>
	</GeneralSection>
	<GeneralSection><SectionTitle>To maintain the Infor BW configuration properties</SectionTitle>
		<Keyword type="section" order="IDATBBYB"><Level1>Microsoft Active Directory Service</Level1>
			<Level2>maintain the Infor BW configuration properties</Level2>
		</Keyword>
		<Paragraph class="Default">You can use the Infor Environment and Configuration Selector ( BECS ) to run various Infor BW versions on a single client. You can also use BECS to start the BW Configuration Properties dialog box, which you can use to maintain the configuration settings of the ERP LN environments on the client.</Paragraph>
		<List><ListIntro>To maintain the client’s ERP LN environment properties, take the following steps:</ListIntro>
			<ListItem>Start BECS – Infor Environment and Configuration Selector
                              </ListItem>
			<ListItem>Select an environment and start the BW Configuration Properties dialog</ListItem>
			<ListItem>Under Baan Service, you can choose to use an environment for which the connection points are published in ADS. You can also choose to use an environment for which the connection points are not published in ADS.</ListItem>
			<ListItem>Click <GUIRef href="" role="manual">Published</GUIRef> to use an environment for which the ES Logic Service has published the connection points in the ADS database. In the Published list, you can select an environment for which the connection points are stored in the ADS database. The Hostname, BSE, Protocol, and Portnumber fields are automatically filled with the information retrieved from the ADS database.</ListItem>
			<ListItem>Click <GUIRef href="" role="manual">Private</GUIRef> to use an environment for which the connection points are not published in ADS. You must now enter the data in the Hostname, BSE, Protocol, and Portnumber fields yourself.</ListItem>
		</List>
	</GeneralSection>
</ManualTopic>
