To configure Cinegy Route Directory Relay Service, the ChannelRelay.exe.config file is used. It is located in the same folder with all other Cinegy Route files.

A sample of its structure is shown below:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <configSections>
        <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
            <section name="ChannelRelay.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <applicationSettings>
        <ChannelRelay.Properties.Settings>
            <setting name="Destination" serializeAs="String">
                <value>239.255.255.254:8888</value>
            </setting>
            <setting name="Ttl" serializeAs="String">
                <value>1</value>
            </setting>
            <setting name="SourceIP" serializeAs="String">
                <value>0.0.0.0:8888</value>
            </setting>
            <setting name="RegistryServer" serializeAs="String">
                <value>localhost</value>
            </setting>
        </ChannelRelay.Properties.Settings>
    </applicationSettings>
</configuration>
Note
Port 8888 in the ChannelRelay.exe.config file is used by default.

where:

Destination – defines the network group to broadcast information about the configuration changes.

Note
This parameter should not normally be adjusted, since all Cinegy clients will look for configuration information on this fixed address, and changing this value will prevent clients from registering any messages.

Ttl – defines time-to-live for multicast transmission of relay packets, used to control the number of router hops a packet is permitted to make before being dropped.

SourceIP – defines the local IP address and the port to be used for broadcasting the configuration changes. This value should correspond to the IP address of the server-local adapter for multicast configuration data to be transmitted on.

RegistryServer – this value should correspond to the central Cinegy Route Directory Service machine to be relayed. This parameter is used to establish connection from the Cinegy Route Directory Relay Service to the core service, and is embedded inside the multicast data as part of any URL entities, so should be consistent and resolvable by all clients.

Note
The RegistryServer parameter must match any value used when connecting to Cinegy tools and defining virtual destination addresses. If a client is subscribed to a virtual destination of http://route:9996/getvirtual?group=Bristol&name=CLIENT1, but the parameter on the Relay server is set to an IP address or a fully-qualified domain name, subscribing clients will not consider the details of changes to this virtual destination in the multicast data stream a match, and will continue polling the central service.

Once configured, Cinegy Route Directory Relay Service should be restarted to reload any changes. Use of network switch tools should show a multicast stream coming from the service, and it is recommended that client traffic is analyzed via network monitoring tools (e.g. WireShark) to verify proper operation.