UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1296 views

One broker per tree? How?

Hey there.

We had two servers, each running a broker and a Manager. Through a bunch of reading I found out that it is now recommended that there is only one broker per tree if possible. No problem. How do you do that?

I turned off the broker on the other server, restarted the Manager, and it never found the new broker. When I go into the manager or a printer and try to attach print drivers, there are none listed. On the server where the Manager and Broker are running, everything looks and runs fine.

How do I get the Manager and printers on the other server to see the single broker? I looked all over for something that shows how to do this. Is it just suppose to work?

I deleted the broker that I am not wanting to use anymore thinking that this may have been the issue. Nope.

Tom

0 Likes
5 Replies
Cadet 1st Class
Cadet 1st Class

Tom Hafemann wrote:

> Through a bunch of reading I found out that it is now recommended
> that there is only one broker per tree if possible


Please start by specifying where you found that info......

--
Best Regards

Tommy Mikkelsen

IT Quality A/S
Denmark

Novell Support Forums SYSOP

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB

Be a GroupWiseR, go http://www.groupwiser.net

Best Regards

Tommy Mikkelsen

Denmark

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB
0 Likes
Absent Member.
Absent Member.

What you need is the setens and setrms swtches for the NDPS Manager to
point to the Broker:

http://support.novell.com/docs/Tids/Solutions/10067688.html

Some clarification however:
The recommendation to only use one Broker only holds when using iPrint. If
you use NDPS to access the pritners, then you should better use at least
one Broker per site.

Explanation:
In NDPS, the clients directly talk to the Broker to download drivers and
to register events. As such, there is quite some traffic between clients
and the Broker and a single Broker might be a bottleneck.
With iPrint, clients no longer talk to the Broker. Instead, all traffic
goes directly to the server holding the Manager. Even driver download go
through the server holding the Manager. That server contacts the Broker
the first time a new driver is needed. Then that driver is put in the
MOD_IPP driver cache, and any further workstation that asks for the
drivers receives it from the cache and no further access to the Broker is
needed. Also, the event notification service does not exist in iPrint and
as such, that second service of the Broker is not needed.

The main advantage of having a single Broker is to have just one single
driver repository. You don't need to upload the same driver to multiple
Brokers and you don't have problems with a same driver having a different
reference on each server, a thing which makes it more difficult to move
pritners between different managers as after each move, you would have to
reassign the driver.

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Absent Member.
Absent Member.

Tommy Mikkelsen wrote:

>Please start by specifying where you found that info......


It can for example be found here:

http://www.novell.com/support/viewContent.do?externalId=3281477

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Absent Member.
Absent Member.

BINGO, thanks!

That would have been a hard tid to find for me. I was asking all the wrong questions.

Tom


>>> Marcel Cox<Marcel_Cox@no-mx.forums.novell.com> 7/17/2008 1:50 AM >>>

What you need is the setens and setrms swtches for the NDPS Manager to
point to the Broker:

http://support.novell.com/docs/Tids/Solutions/10067688.html

Some clarification however:
The recommendation to only use one Broker only holds when using iPrint. If
you use NDPS to access the pritners, then you should better use at least
one Broker per site.

Explanation:
In NDPS, the clients directly talk to the Broker to download drivers and
to register events. As such, there is quite some traffic between clients
and the Broker and a single Broker might be a bottleneck.
With iPrint, clients no longer talk to the Broker. Instead, all traffic
goes directly to the server holding the Manager. Even driver download go
through the server holding the Manager. That server contacts the Broker
the first time a new driver is needed. Then that driver is put in the
MOD_IPP driver cache, and any further workstation that asks for the
drivers receives it from the cache and no further access to the Broker is
needed. Also, the event notification service does not exist in iPrint and
as such, that second service of the Broker is not needed.

The main advantage of having a single Broker is to have just one single
driver repository. You don't need to upload the same driver to multiple
Brokers and you don't have problems with a same driver having a different
reference on each server, a thing which makes it more difficult to move
pritners between different managers as after each move, you would have to
reassign the driver.

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Cadet 1st Class
Cadet 1st Class

WOW.....


--
Best Regards

Tommy Mikkelsen

IT Quality A/S
Denmark

Novell Support Forums SYSOP

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB

Be a GroupWiseR, go http://www.groupwiser.net

Best Regards

Tommy Mikkelsen

Denmark

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.