E4C Message Broker needs to be executed as a Windows service. Thus, it is necessary to create and configure the service in order to make the Message Broker work. To create service, open command line as administrator and run a command like:
| Code Block |
|---|
sc create FSMmessageBroker DisplayName= "FSM Message Broker" binPath= "path_to_the_messagebroker_exe_file" obj= "NT AUTHORITY\LocalService" |
Depending on the directory, to which you extracted the Message Broker archive, the path in the above command can be different, for instance: "C:\Program Files (x86)\proaxia\FSM Message Broker\MessageBroker.exe".
When entering the command, please note that for each parameter a space character after = sign is used. This is necessary for the command to work properly. The command creates Windows service named FSMMessageBroker, with display name FSM Message Broker and registered to run in context of LocalService user. In case there is more than one instance of Message Broker installed on the same server, you need to create a separate service for each of them. Please remember to give the services distinct names (e.g. FSMdevMessageBroker, FSMtestMessageBroker and FSMprodMessageBroker) and distinct display names. The service created with the sc command as above are set up to be run manually and switched off. After having configured the Message Broker (as described in subsequent section) and having run the service successfully (no errors in logs), you should switch the service startup type from Manual to Automatic.
Additionally, it should be considered, to configure the service to be restarted automatically in case of crashes, so that the work is uninterrupted, when such occur:
