The Remote Control configuration file is specified in the configuration source remotecontrol in the configuration file Composer.Studio.exe.config.
<remotecontrol configSource="remotecontrol.config"/>
The actual configuration file RemoteControl.config defines which Remote Control Services are accessed on which server.
The following example uses a server named Hyland and a Remote Control Service named RemoteCotrolServiceComposer.
This is defined in the corresponding endpoint.
The Windows service is accessed via the name of the service (ModProcess_SVC).
<remotecontrol> <computers> <computer name="Hyland" display="Content Composer Server"> <services> ... <service name="ModProcess_SVC" display="Composer Process Service" runtime="TRUE" endpoint="RemoteControlServiceComposer"/> ... </services> </computer> </computers> </remotecontrol>
In the configuration file Composer.Studio.exe.config, the <client> element defines the endpoints used.
In the following example, the client uses IP port 4712 to communicate with the service RemoteControlService hosted on the computer with the network name Hyland.
The Remote Control Service is defined by its endpoint address.
<system.serviceModel> ... <client> <endpoint name="RemoteControlServiceModus" address="http://Hyland:4712/RemoteControlService" binding="wsDualHttpBinding" bindingConfiguration="Binding1" contract="ComposerSuite.Runtime.RemoteControlContract.IRuntimeControlService"/> ... </client> ... </system.serviceModel>
The associated binding (here Binding1) is used to specify the client base address the server uses to communicate with the client.
In the following example, the client (RemoteControlClient in Studio) runs on the computer with the network name Composer_Client and uses the IP port 8000:
</system.serviceModel> ... <bindings> <wsDualHttpBinding> <binding name="Binding1" clientBaseAddress="http://Composer_Client:8000/RemoteControlClient" ... </binding> ... </wsDualHttpBinding> ... </bindings> ... </system.serviceModel>