This guide shows you how to set up Data Director to replicate Data from Head Office to Store.

Transcription

1 Install Data Director 3 This guide shows you how to set up Data Director to replicate Data from Head Office to Store. Installation Run the setup file LS.DataDirector.3.02.xx.Setup.exe and set the location where you want it to be installed. Select which components you want to install. If no options are selected, DD will only install client controls files needed to communicate with DD Service on another host. Options for LS Retail NAV 6.x and older select: DD Service, Client Tools, CFront Files & DD2 Client for NAV Options for LS Retail NAV 2013 and later: DD Service, Client Tools, DD Client files for NAV 201x RTC/SRV Add-ins Options for POS: No extra options needs to be selected for POS, setup will only install the client controls.

2 DD Configuration Depending on what you are using DD for, there are some settings you may want to look at in the DD Configuration tool. Default settings are fine for most setups and when installing DD, depending on what you choose in the install options, these settings are done for you on a clean install. LS Retail NAV 6.x and older: Communication with Native NAV or SQL NAV is done via CFront, so activate the CFront option. SQL NAV can be communicated via SQL driver, and if you plan to use that driver and have no Native NAV, you can turn off the CFront option. Old DD Support is for older DD2 communication and also to support older CodeUnits that still reference the DD2 TransAutomClient.dll LS Retail NAV 2013 and later and LS One Site Manager (Store Controller): NAV 2013 and later do not support CFront so there is no need to activate it unless you also have older NAV system still running in your setup. All new Codeunits in LS Retail NAV 201x use newer DD3 TransAutomClient.dll so there is no need for Old DD support unless you are sending to DD2 service somewhere. When connecting to many database servers, you may want to increase the Data Thread Limit value under System Config. This also takes care of the error when using CFront that there are no more threads allowed.

3 Configuration at Head Office After installing DD at HO and Store, open the Configuration Tool at Head Office computer and add the Store DD to the Host List. Open up the Configuration Tool in Start Menu under the LS Retail Data Director 3 folder Add the Store computers to the Host list. Type in the host name and press the Add button. To remove a host from the Host list, select the host in the list and click on Remove button. When you open up the Configuration Tool, by default it loads the local configuration from disk for the local host. If you make any changes to the configuration and press the Save Config button, the DD System needs to be restarted for the changes to take effect. Configuration on running system can by changed on runtime by clicking on the Get Config button, which will then load the running configuration and after you have done your changes, click on Send Config button to send the configuration back.

4 To load the configuration from the stores, select the stores from the host list, you can load more than one at same time by select more than one. (Hold down Ctrl or Shift to select more than one host) Press Get Config button to fetch the configuration from the Stores. Do this also for local host, to load the configuration from the running DD at Head Office. Update Data Director Licenses By default Data Director is shipped with a demo license that allows replication within same Network. Upload you Data Director License and also NAV license. Select all DD hosts in the list, and press the Send DD License button. Select the Data Director License file and press OK. This will update the license file on all the hosts. NOTE: The DD License has to be version 1. To check if your license is version 0 or 1, open it up in notepad or text editor and check if it starts with DD_LIC1, if so then its version 1, if it starts with DD_LIC, then it is version 0 and you need updated license file from LS Retail Support.

5 Update NAV Licenses for Data Director NOTE: NAV License is only needed for Dynamic NAV 6.x or older. DD does not need license when communicating with NAV 2013 or later. Select all DD hosts in the list, go to the App Config tab and press the Send NAV License button. Select the license file and press OK. How to confirm if license files were uploaded successfully After a DD License or NAV License has been uploaded, you get the message that the file has been sent. Use the Monitor to check if it was successful or not. Open the Job Monitor Connect to the DD Host, where you sent the files from. You should see the status Done in all locations if the license files were sent successfully to the destination hosts.

6 Distribution Location setup in NAV In NAV, nothing has changed. You still set up the location as before. DD3 runs on host names, not DD Service names like DD2 did so you only type in the Host name of the computers where DD3 is running. The Path to the CFront Directory field should point to the location where the CFront folder, located where DD is installed. Now you should be able to do Test Connection to both locations, with or without DD.

7 Distribution Server Name DD works default on Local Host name. Type in the Local host name on the host where DD is running into the Distribution Server name field. DD matches valid host name with the information in the Destination Server field to decide if it should process the job or not. If host name is not known on the Source Host you may also use IP Address. To see what valid host name and IP Addresses are for the Destination host where DD is running on, open DD Configuration Tool on the Destination host or connect remotely to that host and Get Config. Click on the DNS button and you will see list valid Host name and IP Addresses returned by the DNS Lookup on that host. Any other Host name or Old DD2 Service name that do not show up in the DNS Lookup, can be added to the Aliases field and then DD will accept those jobs with that host name for processing.

8 Using Windows NT Authentication If you plan to use Windows NT Authentication to connect to databases, you need to assign the Windows user to the DD Service. Open up Windows Services, locate LS Data Director 3 Service and open Properties for the service. Under the Log On tab, select the windows user that should be used to connect to the databases, and note this user has to have full access on the local host as well. In the Distribution Location card, you skip putting in database user and password for that location, if using CFront (fin) mode. If using SQL (ms) mode then add ;Integrated Security=SSPI; to the connection string instead of user and password. You can see samples of connection strings in DD User Guide.

9 Update DD remotely When new version or update of DD is available you can update all DD hosts that are running DD Service from the DD Configuration tool. Recommended method of updating DDs in the network is to do the HO server first by running install locally (not use the remote update button), then use the remote update option to update the stores. Select all the stores from the host list, press the Remote Update button. Select the new DD installation file LS.DataDirector.3.02.xx.Setup.exe. Choose which install options you want to run, usually it s not needed to select CFront Files and DD2 Client as there will be no more updates in those files. You can add which applications to kill on the remote host before the install will run by type in the process name of the application and press Add App button. Add all applications that are using some of the DD files so the files will not be in use when the installation will run. Press OK and then job will be created that will send the installation file to the remote hosts and run the install. After installation is done the remote system is ready to run. To monitor the Install process, open Job Monitor and look for LS DataDirector Install job. Its recommended after the installation is done to Get Config from all the hosts, check the version under Debugging tab, and if everything is ok, Send Config again to all hosts to update the configuration with any new config values that may have been added in the new release.