How do we handle multiple instances of webMethods IS on the

When installing multiple Webmethods products on one server to support a dev and qa environment, do you install separate filesytems and a separate database for each one?

Any pros / cons of doing one way vs. other, would be very much appreciated

We are running on Solaris servers, and host multiple environments on a single server. Each environment is setup under a different user, none root, and each has its own virtual network address. All databases are off platform, and have completely separate ids as well. There is nothing common that is shared across environments, with the exception of the network interface. So think separate JVM’s, memory, disk space, etc. A downside, is that all outbound network traffic, shows the network card address as the source, independent of the process (virtual interface) originating the transfer, therefore other firewalls need to handle this. We don’t use the 5555 port, which allows us to bring up each environment for initial configuration without conflict, prior to setting the watt.server.inetaddress=“your virtual address”. We currently don’t use reverse invoke, but will likely in the future, and may have some related issues. We do use a webMethods IS server in the DMZ to front-end an internal IS/TN server. My preference would be to use individual servers, but there are many tradeoffs to consider, which are local to the organization. In any event, it works.

You will need to do a seperate installation and database for each IS that you istall. webMethods is not capable of hosting multiple IS servers from the same installation directory.

We have a test and development IS on the same machine. We installed them separately, with distinct installation directories, and were sure to use different ports for each.

If you install them as Windows services, be sure to give them distinct names.