Disabling Multicast

Disabling multicast may be useful if there is a firewall between clients, application servers or mediation servers that must discover each other. Application-to-mediation server communication does not use multicast, although mediation-to-application server does, unless disabled.

To disable multicast communication between application and mediation servers, define the property OWARE.CONTEXT.SERVER.URL in the installedprops/medserver/lib/installed.properties file and the property should point to the application server ip address and should be in the following format:

OWARE.CONTEXT.SERVER.URL=jnp://<application server ip address>:1099

If the mediation server is communicating to a cluster of application servers then the value should define all the application servers separated by a comma For example:

OWARE.CONTEXT.SERVER.URL=jnp://<application server A ip address>:1099,jnp://<application server B ip address>:1099

Define this property on all mediation servers.

This configuration change is only for application and mediation server communication. The mediation servers in a cluster still use multicast between themselves. If you use OWARE.CONTEXT.SERVER.URL, you must (comma-separated) list all available servers wherever you use it to bypass multicast.

[spacer]

The context URL is also required when clients are behind firewall and wants to communicate to application server.

[spacer]

If you make a mistake in installing portions of your cluster, remember you must either re-source the Oware environment, or delete all files in oware/temp (and restart the process in question) before changes can be effective.

[spacer]

Multicast is still required between the cluster mediation servers, or application servers in a cluster unless you follow the instructions in the next section.