Standalone launcher

[sjohn]

One small help.My data adapter needs to read the JMS URL , toopic name etc from an external def file . Can you tell me the best way to pass this to the dataadapter from the standalone launcher.
Can I pass the adapter.xml path , to server.adapterConfig ?

[DarioCrivelli]

I can only confirm and expand what was said in this thread
The prescribed way to supply a configuration file from the Remote Server "main" function in "StandaloneLauncher.cs" to the Data Adapter is to specify the file path in the "server.AdapterConfig" property; then, the Data Adapter "Init" method will receive the file name in its "configFile" argument and should take the burden of reading the file.

As an alternative, you can take the burden of reading the configuration file in StandaloneLauncher.cs and pass the relevant properties as a map, in "server.AdapterParams"; in this case, the Data Adapter "Init" method will receive the map as an "IDictionary" object, in the "parameters" argument.

In any case, no support for the configuration file management is available. The "adapters.xml" file used for the configuration of the java Adapters which run in-process with Lightstreamer Server has, unfortunately, no equivalent for the Remote Adapters.
The base Remote Server launcher (i.e. DotNetServer.exe) just gets configuration arguments from the command line and can only run one Adapter (see

DOCS-SDKs\sdk_adapter_dotnet\examples\DotNetStockListDe mo\Deployment\Deployment_DotNet_Server\DotNetServe rs.bat

), while the "open source" StandaloneLauncher.cs is specific for the StockListDemo and just transfers some arguments from its command line to the Metadata Adapter.

[sjohn]

So what is lightstreamers recommendation for running multiple adapters.
1) Do I need to write standalone launchers for each adapter?
2) What is lightstreamers receommendation for the below scenario?
I need to listen to various topics on the same jms url? Would I need to write a separate adapters for each topic?

[DarioCrivelli]

The main limitation about adapters is that each web client can open only one streaming session at a time and a session can be associated to only one Data/Metadata Adapter pair.
So, you probably need to setup a single Metadata Adapter and a single Data Adapter, unless totally different front-end applications have to be fed by the same Server instance. In a remoting scenario, this means one Metadata and Data Proxy Adapter (already supplied) plus one Metadata and Data Remote Adapter.

We have no recommendation about how to launch the Remote Adapters. Customizing a standalone launcher allows you to launch both Metadata and Data Remote Adapter together. If launching them separately is acceptable, then you may not need to customize two standalone launchers, but you may find it enough to use the provided Remote Server.

Note that you also may not need to use a Remote Metadata Adapter at all. You could setup a local, java Metadata Adapter in place of the Proxy Metadata Adapter and only need the Remote Data Adapter.