Most recent edit on 2010-07-01 16:01:46 by AndreasSedlmeier [added some uniPaaS specific stuff and some more words]

Additions:
If you chose during installation to install the Magic request broker (>= v9) as an application and later on want to change this to "run as a service" or if you want to add additional brokers which should run as a service, you need to reinstall from CD or service pack file completely.

• use the "-is" (install as service) command line switch of the broker executable (not available in v10/uniPaaS anymore)

The broker executable has a command line switch which allows you to install the broker as a service.
This will install a service named (for v9): "Magic 9 Broker" and you can change the registry to get a more specific name like "Magic 9.4 Broker (production)" or so.
You can use the service control command line utility to install a Magic broker as a service. In uniPaaS this is the only option to install a Broker service (besides running an installtion) since the uniPaaS broker no longer supports the commandline switch "-is"
To create a Magic 9.4 broker service open a command prompt and type:
A uniPaaS Broker running as a service you could create with following command (note how the backslash character is used in this sample to escape embedded double quotes. Surrounding the path to the executable with double quotes is a requirement, if the pathname does contain blanks) :
sc create "My uP 1.8 Webservice Broker" binpath= "\"D:\up18\bin\uniRQBroker.exe\" -INI=D:\up18\ini\mgrb.ini -SERVICE=My uP 1.8 Webservice Broker" type= share displayname= "My uP 1.8 Webservice Broker" start= auto
Above will have created a service named "My uP 1.8 Webservice Broker" and you can delete this service by means of the sc delete command. Simply type:

sc delete "My uP 1.8 Webservice Broker"

Note that you should stop a service before you delete it in case its running. If you do not do this, the service will be marked for deletion but will actually not be deleted.
and ... for our uniPaaS based Broker Service from above:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\My uP 1.8 Webservice Broker

Deletions:
If you chose during installation to install the Magic request broker (>= v9) as an application and later on want to change this to "run as a service", you need to reinstall from CD or service pack file completely.

• use the "-is" (install as servce) command line switch of the broker executable (mgrqmrb.exe)

The broker executable (mgrqmrb.exe) has a command line switch which allows you to install the broker as a service.
This will install a service named (for v9): "Magic 9 Broker". You can change the registry to get a more specific name like "Magic 9.4 Broker (production)" or so.
You can use the service control command line utility to install a Magic broker as a service.
For this use following command line:
(note the spaces behind the parameternames which do end with an equal sign)
"Magic 9.4 Broker" here is the name we chose for the broker service during installation (and also the default name if the eDeveloper 9.4 setup installs the service).

---

Edited on 2010-04-14 14:09:18 by AndreasSedlmeier [added few things]

Additions:
Once the broker is installed you can change the commandline used to start the service by modifying the registry entry of the service, namely the value "ImagePath". Usually you want to specify there a different .ini than that located in the Magic folder which is named "mgrb.ini".
If you choose the service control manager to install the service you could already provide it with a complete command line so that there's no requirement to tweak the registry. You could also specify there to run the broker service with an account which is different from LocalSystem - and you probably want that because LOcalSystem has no access to any network resource.
To manually change broker settings in the registry, open the registry editor and position on following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Magic 9.4 Broker
"Magic 9.4 Broker" here is the name we chose for the broker service during installation (and also the default name if the eDeveloper 9.4 setup installs the service).

---

Edited on 2010-04-14 14:01:19 by AndreasSedlmeier [fixed a problem in the command line for SC invokation]

Additions:
sc create "Magic 9.4 Broker" binpath= "C:\Program Files\Magic\9.4\MGrqmrb.exe" type= share displayname= "Magic
(note the spaces behind the parameternames which do end with an equal sign)

Deletions:
sc create "Magic 9.4 Broker" binpath= "C:\Program Files\Magic\9.4\MGrqmrb.exe -SERVICE=Magic 9.4 Broker" type= share displayname= "Magic

---

Edited on 2008-11-25 11:41:32 by AndreasSedlmeier [formatted]

No differences.

---

Oldest known version of this page was edited on 2008-11-25 11:39:22 by AndreasSedlmeier [new page "Install Magic Request Broker as a service"]

Install Magic Request Broker as a service

If you chose during installation to install the Magic request broker (>= v9) as an application and later on want to change this to "run as a service", you need to reinstall from CD or service pack file completely.

Other ways to install the broker as a service are

• use the "-is" (install as servce) command line switch of the broker executable (mgrqmrb.exe)
• use the service control command line utility "sc"

using the "-is" command line switch to install broker as a service

The broker executable (mgrqmrb.exe) has a command line switch which allows you to install the broker as a service.
To achieve this, simply open a command prompt, change current directory to the directory where the broker resides and type following:

This will install a service named (for v9): "Magic 9 Broker". You can change the registry to get a more specific name like "Magic 9.4 Broker (production)" or so.

using sc command line utility to install broker as a service

You can use the service control command line utility to install a Magic broker as a service.
For this use following command line: