Small quary about PO and POA

[200063]

Well, I was trying to build a new PO.
In my opinion, each PO should own a POA at least.
If I have 10 POs in the domain, shall I see 10 POAs in the system console list?
When I creat a new PO and run the POA for the new PO, it says the port is occupied by the another POA. Shall I change the port each time when I have a new POA connecting with PO?

 

[terry712]

each postoffice has to have a poa (it's basically the same thing)
keep it simple - stick with the default ports - unless you are playing around and have a server that is running multiple poa's
in a real life scenario then i cant see why you would every have more than one poa loaded on a server

 

[200063]

Dear terry:
I don't want to have many POAs in the serve, I did that because that's what I learn from the GW65 PDF.
From that PDF, I should build a NEW po from the console, then, I should install and start a NEW POA.
Am I wrong?
Back to my question, how can I connect my new po to the poa?
I check the grpwise.ncf. There are three command lines in that file.
gwmta @XXX.MTA
gwpoa @old.poa
gwpoa @new.poa
But I got error when I execute this file because I load the GWPOA twice and the program occupies the same port.

 

[marvhuffaker]

Man oh man, why do you want to run 10 po's on the same server? that's insane.

How many users do you have total? Simplest setup that works for most companies (even large ones) is to have one PO and one primary domain and one secondary domain (for redundancy).

The main reason you'd really want more PO's is if you have numerous different WAN locations and you want each location to have their own Post office to reduce WAN traffic. But then you'll have servers at each location and a PO running on each one, so you don't have the port conflict problem.


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[200063]

oh, My god, you are kidding me or the book written by stupid guy kidding me.
From the GW6.5 PDF, It looks very nice if each department has their own PO. Therefore, I thought I may design a better environment with PO in each division. -_-b

Thank u, Marvhuffaker.

 

[marvhuffaker]

Of course it depends on your environment, and I suppose that is a valid design that they talk about...

But I will stick my neck out and say that Most of Novell's Documentation is either really bad or it is severe overkill.. It's written for very complex and large environments. A lot of the concepts either don't apply or are not practical for the average company. And they make a lot of assumptions and don't answer the basic questions.

I'm not dissin' on Novell... Their products are awesome. They just need have real people write the manuals, not the engineers that designed the software.



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[terry712]

yes you need to change the port on the second poa - then you would do a rebuild on the second one
personally i would delete the second one

stick with one postoffice on a server - there is no need to departmental it - there are enough options that you can control things

if you have other sites across a wan link and they have a local server then yes - install another postoffice - in fact if it's a large site - ie say in excess of 50 people or they are heavy users then i would be inclined to install another domain as well

 

[200063]

Thank u , guys. :>

 

[200063]

And I also want to say that
If the Novell company wants to make themsevles back to the market stage, they need to change their attitude of ignoring the small "fussy" mistakes in their programs. They also need to write a very clear and useful instruction.
As a person who had studied DOS 3.3 before, I don't mind to use command lines at all. Actually, I love to know the instructure of whole system, which is enable me to make a change and repair easily.
Making installation programma work, at least, the system should can work after installation. That's the bottom line.