Article

dzanre's picture
article
Reads:

4519

Score:
0
0
 
Comments:

3

Running More Than One MTA on the Same Server

Author Info

26 November 2008 - 4:35pm
Submitted by: dzanre

Author Blog
Author Profile

Tags

Tags Map

(View Disclaimer)

Here's something I stumbled on while writing my GW8 Upgrade Guide:

The new GroupWise 8 MTA opens a SOAP connection (for administrative purposes) on port 7161. If you intend to run more than one MTA on any particular server, you must set a unique SOAP port for the additional MTAs. This cannot be done in ConsoleOne, but must be configured in your MTA startup file. The default port is 7161. For each additional MTA you should set an alternative port.

For example:

  • NetWare/Windows: /soapport-7162
  • Linux: -- soapport 7162

This is undocumented as far as I can tell.

Caledonia Network Consulting:
http://www.caledonia.net/


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.



Related Articles


User Comments

Anonymous's picture

documentation

Submitted by Anonymous on 26 November 2008 - 12:52pm.

it's documented for the POA but yeah it should really also be documented for the MTA. Thanks!

Anonymous's picture

danita is the true goddess

Submitted by Anonymous on 28 November 2008 - 2:36pm.

I wonder which Dutch admirer showed you this one ... :-)

paulgear's picture

A simpler solution...?

Submitted by paulgear on 1 December 2008 - 3:21pm.

I always try to avoid making modifications to the startup file. It's a bad idea, in my opinion, because then NDS and the file say different things, and you have to know to go looking in the startup file (because it overrides NDS) when the behaviour you expect based on the NDS config is not happening.

My solution is this: Always allocate a separate IP for every MTA, POA, and gateway in your GroupWise system. You can configure the IP binding in ConsoleOne, so there's no need to edit the startup file, and you can easily move the IP between servers if you need to migrate for some reason. Planning even a small GroupWise system in a rigorous way like this is a great way to ensure easy upgradability in the future.

© 2013 Novell