Network configuration C

An external LAN-segment with workstations that want to use the LION application, is connected through a router, a bridge or a modem to another LAN-segment on which the Application server runs. All files for the LION application are transported to only one location in the external LAN-segment, by the Application server, insofar as they are needed on the client. The user only requires a shortcut to "App.exe" or "AmtScreens.exe" on a server in the local LAN-segment. 

For the workstations in the external LAN-segment, it is sufficient that they only ‘see’ the machines in their own LAN-segment; adjustments in the configurations (router/bridge/modem, remote access, etc.) of all the workstations are not necessary.

All files needed are located at one place in the LAN-segment, as in configuration A. All shortcuts of the workstations define the path to "AmtScreens.exe" at this one spot.

In the external LAN-segment one server has the task to make the connection to the Application server through the router/bridge/modem: the Communication server. Only on this machine the configuration (router/bridge/modem, remote access, etc.) has to be set for this.

Optionally a Communication Manager, and when needed a Spare Communication Manager, can be installed. In that case you can install more than one Communication Server in the local LAN-segment and the Communication Manager will distribute the connections over the Communication Servers.

Communication Server

When the Communication server is started, it contacts the Application server. As in configuration B, the Application server and the Communication server together compare the time stamps of the library files and, if necessary, transport files. In case the Communication service itself has to be updated, it will be shut down and restarted automatically, after the transport.

The first client can only log on to the Communication server after the time stamps of the following files are checked and possible transports of the newest versions are completed:

• CommunicationServer.exe
  
• RestartService.exe 
• AmtScreens.exe
  

Thanks to the setting of the configuration C in "App.ini", on the workstations "AmtScreens.exe" only checks whether the Communication server is active and whether it accepts logins. If so, "AmtScreens.exe" will continue running.

In configuration C, "AmtScreens.exe" does not contact the Application server, but the Communication server. The Communication server registers in a table all locally present files and the corresponding time stamps. This way it is possible to determine fast, with help of the Application server, whether file transport is needed or not.

The Communication server asks the Application server the time stamp of "Isp_<screen>.CTR", for every screen that is retrieved by the workstations. When it is newer than the copy on the external LAN-segment, then this is transported first. After that, only the version on the external LAN-segment is used.

The Communication server does the same for every combo box and list box. Continuously, a copy of the newest version is present on the external LAN-segment. Subsequently, only this version is used to work with, so a minimum of data transmission takes place.

When the transport of files from the Application server to the Communication server is the result of a retrieval of a client, then on that client appears a message that something is being downloaded, with an indication of its progress. Other clients are normally served by the Communication server, insofar as they are not also waiting for a download.

Implementation

• Make sure that the following file is copied into the desired folder on the machine the Communication Server will run on
  • From the Common directory:
    CommunicationServer.exe
     
    
  • From the ClientGui folder (this file can also be copied directly into the desired ComServer folder, or into a subfolder named ClientGui):
    App.ini
     
• Edit the App.ini file and add (or change) the following lines:
  • CONFIGURATION=C
  • LIONCOMSERVER=TCP <Server> <Port>
     
• Add the Communication Server through the Control Center using the service name and server name.
  
  • See also LION Servers.
  • When the Server to install the Communication server on is reachable form the Control Center server and you have specified the correct account for creating the service on the remote Server then you can use the Control Center to install the service. Else you need to install the service manually (See the bullet below).
     
• Install the Communication Server as a Windows Service in an elevated command prompt window using the following command:
  • sc.exe create <Service Name> binpath= "<Path>\CommunicationServer.exe /n:<Service Name>"
  • Take note of the space between binpath= and the double quote.
  • On correct installation of the service the following installation log information should show:
    
    
     
• Start the Communication Service.
  
  • With correct user rights on the remote machine this can be done in the Control Center, otherwise the Service should be started on the remote machine itself. See also Controlling Services from a User Account.
  • After starting the Communication Service, two or three new folders will be created:
    • ClientGUI, if not manually created already the app.ini file will be moved to this folder. Additionally the AmtScreens executable along with its support files will be downloaded into this folder. The screens, listbox and image files will be downloaded in subfolders located here when requested by users.  
    • Log, here the logfiles of the Communication service and the RestartService.exe program can be found
    • NewUpdates, in case the Communication server finds a new version of itself, this update will first be placed here and then be copied with the help of the program ResartService.exe, after which the Communication service will be restarted.
       
• Create a network share for the directory ClientGUI.
  Now, clients on the remote network can log in when they have access to the "AmtScreens.exe" executable file. If clients have a shortcut to this file, they can simply click this shortcut to run the application.
   

Communication Manager

The Communication Manager regulates the connections between AmtScreens.exe and the Communication Servers for the situation where you need multiple Communication Servers by distributing the connections over the available Communications Servers following the in the Control Center set Load Balance schema. 

When the Communication Manager is started, it uses the available CommunicationServer.exe program to contact the Application server. As at configuration B, the Application server and the CommunicationServer.exe program together compare the time stamps of the library files and, if necessary, transport files. In case the Communication Manager itself has to be updated, it will be shut down and restarted automatically, after the transport.

The first client can only log on to the Communication Manager when time stamps of the following files are checked and possible transports of the newest versions are completed:

• CommunicationServer.exe
• CommunicationManager.exe
• RestartService.exe
• AmtScreens.exe
  

When the Communication Manager is then finally started it will read the App.ini file in the ClientGUI folder and read the port number it will use for the service. It will then just wait for things to happen.

After the startup of the Communication Managers the Communication Servers should be started. In their App.ini there has to be a entry about how to contact the Communication Manager. The Communication Server will then make the Communication Manager aware of its existence and running state.

When now the AmtScreens.exe program is started it will read the App.ini file, see that it has to contact the Communication Manager and make a connection to it. The Communication Manager will then tell AmtScreens.exe which Communication Server to use.

Implementation

• Make sure that the following files are copied into the desired folder on the machine the Communication Manager will run on
  •  From the Common folder:
    CommunicationManager.exe
    CommunicationServer.exe
     
    
  • From the ClientGUI folder (this file can also be copied directly into the desired ComManager folder, or into a subfolder named ClientGui):
    App.ini
     
• Edit the App.ini file and add (or change) the following lines:
  • CONFIGURATION=C
  • USECOMMANAGER=TRUE
  • COMMANAGER=TCP <Server> <Port>
     
• Add the Communication Manager through the Control Center using the intended service name and server name.
  
  • See also LION Managers
  • When the Server to install the Communication Manager on is reachable from the Control Center server and you have specified the correct account for creating the service on the remote server then you can use the Control Center to install the service. Else you need to install the service manually in the way described in the Communication Server section.
     
• Start the Communication Manager
  • Either from the Control Center or manually on the server depending on the access rights for controlling services.
  • After starting the Communication Manager, two or three new folders will be created:
    • ClientGUI, if not manually created already the app.ini file will be moved to this folder. Additionally the AmtScreens executable along with its support files will be downloaded into this folder.
    • Log, here the logfiles of the Communication Manager and the RestartService.exe program can be found.
    • NewUpdates, in case the update process finds new versions of the executables, these updates will be placed here and then be copied with the help of the program RestartService.exe, after which the Communication Manager will be restarted.
       
• Edit the App.ini files of the Communication Servers to contain the following four lines:
  • CONFIGURATION=C
  • LIONCOMSERVER=TCP <ComServer Server> <ComServer Port>
  • USECOMMANAGER=TRUE
  • COMMANAGER=TCP <ComManager Server> <ComManager Port>
     
• When AmtScreens.exe is installed on a Server not containing a Communication Server, edit the App.ini file to contain the lines:
  • CONFIGURATION=C
  • USECOMMANAGER=TRUE
  • COMMANAGER=TCP <ComManager Server> <ComManager Port>
     

   

Spare Communication Manager

It is possible to use a Spare Communication Manager as failover. When the main Communication Manager fails the Spare will take over the function of distributing the connections over the available Communication Servers.

Implementation

• Make sure to copy all the files needed into the desired folder on the machine the Spare Communication Manager will run on.
  
  • This are exactly the same files as for the Communication Manager as shown above.
     
• Copy the App.ini from the main Communication Manager and add the following two lines:
  • USESPARECOMMAN=TRUE
  • SPARECOMMANAGER=TCP <SpareComManager Server> <SparComManager Port>
     
• Add these two lines to any other App.ini using the Communication Managers and Servers
  
  • I.e. of all the Communication Servers and App.exe executables and of the main Communication Manager.
     
• Add the Spare Communication Manager through the Control Center using the intended service name and server name
  • See also LION Managers 
  • When the Server to install the Spare Communication Manager on is reachable from the Control Center server and you have specified the correct account for creating the service on the remote server then you can use the Control Center to install the service. Else you need to install the service manually in the way described in the Communication Server section.
     
• Start the Spare Communication Manager
  • Either from the Control Center or manually on the server depending on the access rights for controlling services.
  • After starting the same two folder will be created as with the Communication Manager