Define cluster interconnection inside the ebms properties file

By this change the settings of port number and used servlet are
controled via the ebms properties file instead of being hardcoded
inside the InboundMessageProcessor class.

A simple description of this cluster implementation.

Consider a cluster of Hermes instances behind a loadbalancer. Each
Hermes instance is a complete instance in itself, its own database etc.

Whenever a message is sent by a Hermes instance within the cluster a
reply message from outside can be expected.
When a Hermes instance receives a reply message it will first try to
find the order message for which the reply message was sent. This is
done based upon the RefToMessageId inside the reply message. If the
order message is found normal processing will follow.

If the order message is not found the Hermes instance will normaly
reply with an error message. However this implementation will take the
RefToMessageId and will cut out the host address of the RefToMessageId.
It will then setup a http session with that host and sends the received
reply message to that host as a ebMS. So the receiving host will
process the reply message as a standard reply message. And will also
respond in the same manner.
Based upon the response from the host the Hermes instance will answer
the ebMS that originally sent the reply message.

So to get this working there are some things to consider:
- The Hermes instances must be able to sent messages to each other
- Inside a cluster the message will be sent via http, no SSL, so the
server should be able the receive the messages via http.
- It is important that the host address can be retrieved from the
RefToMessageId, so it should be part of all MessageIds of the messages
sent. This is default behaviour but make sure it is there (and not an
'unknown host').