[chrisplough]

Quite often, clients need to install multiple OTM versions and/or instances on a single server, particularly in QA and DEV environments. This is best achieved by assigning multiple IP addresses to a single server and then binding each OTM installation to a separate IP address, which helps to avoid port conflicts and allows each OTM installation to use the standard ports. However, there are a few ports that OTM (and it's components) use, which cannot be bound to an IP address, so here's some information to help.

Tomcat

Tomcat uses two ports, one for data-transfer (default 8009), which can be bound to a specific IP address, and one for shutdown (default 8007), which must be bound to localhost or 127.0.0.1. Since the shutdown port must be bound to localhost, each OTM installation on a server will need to use a unique port. For instance, I usually bind the first installation to 8007, the next to 8006, the next to 8005, and so on. This helps to avoid trampling on each other and also conflicting with the data port of 8009.

WebLogic

WebLogic uses two ports, one for data-transfer (default 7001), which can be bound to a specific IP address, and one for SNMP (default 7161) which listens on all available IP addresses. Since this SNMP port cannot be bound to a specific IP address, each installation on a server will need to use a unique port. I usually bind the first one to 7161, the next to 7162, the next to 7163, and so on. This keeps them from trampling on each other and just moves upward ad-infinitum.

Hope this helps!

--Chris