Communication is performed via a series of Web Service calls. These are simply portals to call the process parts to run. If this is made as simple as possible, these simply start the process parts, and fail only if they cannot.

Remote Web Service Calls

Method	Description
Remote1Start	To start the Replication process on the REMOTE System, this tells the REMOTE System to get the non-static data.
Remote2Start	To tell the REMOTE System that the Transmission file is on the Remote System and to begin processing it.
RemoteStop	To tell the REMOTE System to cancel the current Replication process.

Local Web Service Calls

Method	Description
Local2Start	To tell the LOCAL System that the data is available.
Local3Start	To tell the LOCAL System that the update has completed successfully.
LocalStop	To tell the LOCAL System that an error occurred.

General Web Services Calls

Method	Description
GetProcessStatus	To get the status for a location.
ShowVersion	To get the version of the running software.

Web Service Configuration

The Web service has a number of configuration settings. It requires to know where Python is installed and where the Python scripts that form the ‘Entities’ are located.

Example

  <appSettings>
    <!-- Where to find Python -->   
    <add key="PythonDir" value="C:\Python25" />
    
    <!-- Where to find the scripts for the project -->
    <add key="ScriptDir" value="F:\Python\Source\Replication" />

The service itself can be configured to accept only calls for one or other of the ‘Entities’. By setting the value to True or False, you can enable whether these calls are allowed.

Example

    <add key="AllowRemote" value="True" />
    <add key="AllowLocal" value="False" />

Note

You can place a side into Test mode by setting this value to Test. In this mode, the service checks the parameters and reports back that the ‘Entity’ in question has successfully started, without actually starting anything. This is useful for testing purposes.

Browser not supported