[WINDOWS 2.0] URL namespace reservation

FSM Message Broker runs as a web service server. This service is used by its SAP counterpart (E4C Data Processor) to send messages to FSM Cloud. As such, the service must be available on a certain TCP port and is registered with a certain URL in the system. The service URL may look like the one below, when configured to listen on port 9999:
http://localhost:9999/proaxia.e4c.msgbrkr.Outbound.WebService/SendOutboundMessageService/.

Both, TCP port and the path in the URL are arbitrary. You can use any values that fit your needs (described in subsequent sections). You just need to make sure, that web service client definition on the SAP side refers to the correct URL.

If you try to run service without that, you will receive the following error entry in the log:

Exception while starting service of type proaxia.e4c.middleware.Outbound.WebService.SendOutboundMessageService System.ServiceModel.AddressAccessDeniedException
HTTP could not register URL http://+:9999/proaxia.e4c.middleware.Outbound.WebService/SendOutboundMessageService/. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details).

The error message points to a link at Microsoft (http://go.microsoft.com/fwlink/?LinkId=70353), which describes steps necessary to register the namespace reservation depending on the operating system version. For example, on Windows 2008 Server, you would issue the following command:

netsh http add urlacl url=http://+:9999/proaxia.e4c.msgbrkr.Outbound.WebService/SendOutboundMessageService/ user=LocalService

The service URL and user, in whose context the service is configured to run should be used to match the actual values.