Outstanding Contributor.. csaunderson Outstanding Contributor..
Outstanding Contributor..
730 views

RAS_OPERATOR_PATH at the subflow level

Jump to solution

Have been looking at the new RAS architecture as a way to allow us to traverse multiple network segments from different RAS. While it seems straightforward to do this at the operation level, I swear that I saw a post/forum article/something on the Interwebs that this could be set a the subflow level. Am I imagining things?

 

The goal in what I'm trying to achieve is to allow a specific set of operations for a specific network segment to be handled by a specific set of RAS workers, and the rest of the flow to use a different RAS worker group.


Thanks!

 

--Chris

0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: RAS_OPERATOR_PATH at the subflow level

Jump to solution

Hi Chris,

As it has been previously mentioned on this forum the solution to handling parts of flows on specific workers can be handled via the overrideNRAS/overrideJRAS  variables (NRAS for .net based content and JRAS for java based content).  The beauty of this sistem is that beacuse it is basically handled during flow authoring it can be handled in such a way as it to be dynamic. A

s you may have noticed already all operations have either ${overrideNRAS} or ${overrideJRAS}, as such building these variabes anywhere in the flow will affect all  steps  after the uild of these variables will use them until their value changes. Furthermore if a step is a flow (ie entering a subflow) it is enough to place these variables as step inputs and the entire subflow will be executed on those specific worker groups.

The result you are trying to achieve therefore has 2 parts:

- authoring flows to take advantage of these flow variables

- central worker grouping in such a way as to separate the RASes into worker groups which take full advantage of the authored usage of the NRAS/JRAS overrides.

Hope this helps,

Vlad

2 Replies
Micro Focus Expert
Micro Focus Expert

Re: RAS_OPERATOR_PATH at the subflow level

Jump to solution

Hi Chris,

As it has been previously mentioned on this forum the solution to handling parts of flows on specific workers can be handled via the overrideNRAS/overrideJRAS  variables (NRAS for .net based content and JRAS for java based content).  The beauty of this sistem is that beacuse it is basically handled during flow authoring it can be handled in such a way as it to be dynamic. A

s you may have noticed already all operations have either ${overrideNRAS} or ${overrideJRAS}, as such building these variabes anywhere in the flow will affect all  steps  after the uild of these variables will use them until their value changes. Furthermore if a step is a flow (ie entering a subflow) it is enough to place these variables as step inputs and the entire subflow will be executed on those specific worker groups.

The result you are trying to achieve therefore has 2 parts:

- authoring flows to take advantage of these flow variables

- central worker grouping in such a way as to separate the RASes into worker groups which take full advantage of the authored usage of the NRAS/JRAS overrides.

Hope this helps,

Vlad

Outstanding Contributor.. csaunderson Outstanding Contributor..
Outstanding Contributor..

Re: RAS_OPERATOR_PATH at the subflow level

Jump to solution

Hi Vlad!

 

Thank you very much for the detailed explanation. That's exactly what I was looking for. Thanks!

 

--Chris

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.