pabloecipi
New Member.
1346 views

Second POA agent for QF in OES2

I want to automate the starting of two POA agent for the same PO, a dedicated Quickfinder and one for the other functions.
Defined a new POA agent in C1.
Create a new po.poaindex with the values ​​for which only functions as QuickFinder.
The problem appears with the gwah.conf.
With the service starts successfully start grpwise both POA Agent, but then I can not see the status or service down
SUSE 10 SP3 64 bits and OES2 SP3
Labels (2)
0 Likes
5 Replies
Highlighted
pabloecipi
New Member.

Re: Second POA agent for QF in OES2

The name of file is gwha.conf
0 Likes
Knowledge Partner
Knowledge Partner

Re: Second POA agent for QF in OES2

On 22.02.2012 22:56, pabloecipi wrote:
>
> I want to automate the starting of two POA agent for the same PO, a
> dedicated Quickfinder and one for the other functions.


Why? The only difference whatsoever if that the QF threads are started
by a different parent task. Completely pointless excercise.

> Defined a new POA agent in C1.
> Create a new po.poaindex with the values​​for which only
> functions as QuickFinder.


No. You need to run the installers agent configuration, don't try it
manually.


CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
pabloecipi
New Member.

Re: Second POA agent for QF in OES2

Massimo:
Thanks for your reply
The modification I am making is based on this documentation
Novell Doc: GroupWise 8 Administration Guide - Optimizing Indexing --> 38.4.3 Configuring a Dedicated Indexing POA

In an installation where few users, but have a lot of incoming and outgoing messages

regards
0 Likes
Knowledge Partner
Knowledge Partner

Re: Second POA agent for QF in OES2

On 29.02.2012 13:16, pabloecipi wrote:
>
> Massimo:
> Thanks for your reply
> The modification I am making is based on this documentation
> 'Novell Doc: GroupWise 8 Administration Guide - Optimizing Indexing'
> (http://www.novell.com/documentation/gw8/gw8_admin/data/akagb75.html#hjdvwl3e)
> --> 38.4.3 Configuring a Dedicated Indexing POA
>
> In an installation where few users, but have a lot of incoming and
> outgoing messages


1. Define "lots". I run Post Offices with several thousand users, size
in the TB range, that send and receive about 100k messages per day p
*without* a dedicated QF poa.

2. A dedicated QF POA *on the same server* is nonsenic. The idea of the
dedicated POA is to remove CPU load from the server. If a dedicated QF
POA *ever* makes any sense whatsoever (which I highly doubt it ever does
thee days), then when it runs on a different server than the main POA.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
buckesfeld Absent Member.
Absent Member.

Re: Second POA agent for QF in OES2

* pabloecipi,

to add to Massimo's, I'd check the POA log (verbose mode) via the web interface to watch how long the QF actually runs. I bet it's extremely short.
I don't think you need a dedicated indexer, either. What I'd do is set the qflevel to 999 in the POA startup file, so that the indexer catches everything if it ever fails or you have to delete an index manually. Then set it to run every hour or so.

Uwe

--
Novell Knowledge Partner (NKP)
Please don't send me support related e-mail unless I ask you to do so.
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.