Startup order for Node Type (On-Premise environment)

Hi,

we’re implementing node classification in test environment (we’re on-premise) on Pega 8.5.3.

We have 1 WebUser, 1 BackgroundProcessing and 1 Stream,Search node.

is there a specific start and stop sequence? ù

or can be start in any order?

can be also start alltogether?

thank you,

Andrea

@AndreaG86 does this other PSC question post your question as well?

Hi @MarijeSchillern

i’ve found this article, but it’s not clear what is the accepted solution, some replies say that there isn’t an order, some others that there’s.

it’s the reason why i’ve asked this question.

sorry i should have mentioned the article that you posted.

best regards,

Andrea

@AndreaG86

A search in our support system shows that it depends on your architecture and must be handled at your end by being aware of how the single instance restart can be done by not affecting the other

Below information may or may not help you as it totally depends on your architecture

Generally for pega cloud clients we go with rolling restart from GOC only. from GOC it first completes all non marketing tiers and then will start app nodes

if we have to manually do → then we follow → stream->util->dds->dataflow->adm->vbd->decisionhub->app

STOPPING :Do it in following order:
SMS >> Email >> AppTier >> DecisionHub >> Dataflow >> VBD

ADM >> Stream >> DDS >> Util

Starting
Util >>DDS >> Stream >> ADM >> VBD >> Dataflow >> DecisionHub

AppTier >> Email >> SMS

I agree that the documentation does not appear to cover this:

Assigning node types to nodes for on-premises environments

It would be great if you could hit the ‘Feedback’ button to ask our documentation team to include this in future documents.

@yarrs2 would you be able to comment on this question?

@AndreaG86

Startup order should be-

  1. Search

  2. Stream

  3. BGP

  4. WebUser