Setup Satellite

After starting the Global daemon on the Hub the administrator can start another instance at a satellite. Once this has been done the administrator can begin customizing the way that communications between the two machines take place through WCF.

1. Conduct the following steps on the Hub machine:

   1. Create a new transfer folder on the Hub machine.

      Refer to the Global User Guide (section 4.6 Creating Location Files).

   2. Using the SAM project as an example, navigate to the following folder:

      C:\AVEVA\plant\PDMS12.1.1\project\Sample

   3. Create a folder called SAM_SAT as a new transfer folder:

      C:\AVEVA\plant\PDMS12.1.1\project\Sample\SAM_SAT

   4. In the Sample folder open the evars batch file for the project inside a text editor.

      The evars file for SAM is evarsSample.bat.

   5. Create a new environment variable to point to the SAM_SAT folder:

      set SAM_SAT=C:\AVEVA\plant\PDMS12.1.1\project\Sample\SAM_SAT

   6. Launch the base product Admin module.

   7. Create location in admin module

      

2. Conduct the following steps on the Satellite machine:

   1. On the satellite make sure that the base product and Global Server have been pre-installed. Make sure that both have had the WCF enabled.

   2. Copy the contents of the SAM_SAT transfer folder on the Hub:

      C:\AVEVA\plant\PDMS12.1.1\project\Sample\SAM_SAT

      ... to the following location on the satellite:

      C:\AVEVA\plant\PDMS12.1.1\project\Sample\

   3. Copy the evarsSample.bat file from the Hub to the satellite project folder.

   4. Modify the singleds.bat file on the satellite to point to the evarsSample.bat.

   5. From the command line run the singleds.bat file by using the following syntax:

      singleds start sam

   6. On the satellite launch the base product Admin module.

      

   7. Initialize the Satellite location by clicking Initialize Location.

   The Hub and Satellite will now be communicating through Global by using WCF as the authentication provider.

3. From the satellite the administrator can test communication by issuing a ping command.

   Important: There will be a delay when the first communication is established between nodes when using WCF.

4. From the Command Line in the Admin Module enter the following:

   

   On the Hub machine the console window for the daemon will display a summary of communication between the two workstations: