Process Server - Status Overloaded

[Former Member]

I have implemented alerting for status changes on process servers. I notice that frequently the status of the process server goes into overloaded and then goes back into a running status within a minute or two.

We currently have 4 SAP systems configured and connected directly to the CI server since we don't run BTC on our app servers.

Can someone explain to me what threshold will cause the PS to go into overloaded and how I can prevent this status from occuring on the PS? We don't have any BATCH delays on the CI system itself.

[former_member72868 · Accepted solution]

Hello Brian,

When a process server goes to overloaded status, it means that a process server threshold has been passed. Do you have a value configured for the Load Threshold field of the process server in question?

(The load, jobs * load factor, at which the process server should go into overloaded in SAP CPS, should be higher than the Threshold.)

Rgds, David

[Former Member · Accepted solution]

I have not defined any load thresholds for the process servers or the sap system defined. Does it default to something if nothing is defined?

Thx,

Brian

[former_member72868 · Accepted solution]

Hi Brian,

A process server can go to overloaded status if all available batch work processes are in use at the time. Could this have been the case in your situation?

Rgds, David

[Former Member · Accepted solution]

David,

To confirm what you are saying...

If my CI has 10 BTC processes and I have no LOAD Threshold defined the PS will go into OVERLOADED status once 10 batch jobs are running..... preventing further batch jobs from being created on the SAP side - correct?

If I were to set the Load Threshold to say 15 on that PS then even if all 10 BTC were consumed on the SAP side the PS wouldn't go into an OVERLOADED status allowing SAP jobs to create/run (even if they sit delayed in SAP). I think this is currenlt what happens in Redwood 7 which is what we are migrating from.

Thx,

Brian

[Former Member · Accepted solution]

I found a way around this - I disabled the "App. server load balancing" on the defined SAP system. It no longer throws the process server into overloaded. The jobs go into an Assigned status until there is a free BGD process for it to run on.

Thanks for the feedback.

Brian