Highlighted
Micro Focus Contributor
Micro Focus Contributor
90 views

How to run a process SEQUENTIALLY on all resources of a resource group?

Jump to solution

Is there any way to achieve the following in DA?

For a given Resource Group

  • identify all its contained resources, 
  • and run a process on each resource, but not in parallel, as would be the default behaviour.
    Instead, run the process sequentially for each resource (starting the next execution after the previous one was finished).

I am aware that this is an unorthodox request.
The background is that one specific operation needs to be done for all members of the resource group, but  it is executed on the same physical machine. Therefore, a parallel execution would cripple the physical server.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: How to run a process SEQUENTIALLY on all resources of a resource group?

Jump to solution

To execute one at a time within a resource group, and in a situation where order of execution is not important (which resource executes first or second, etc.), I would recommend using resource locks.  Within your component process, use the process step Utility Steps | Resource Lock.  Create a name for the Resource Lock that such as

    ${p:component.name}-${p:componentProcess.name}-${environment.name}

As the processes start to execute, if the first step requires obtaining a lock on that name, only one resource at a time may obtain the lock, the others will wait.

 

If you wish to control the ordering of these, or if you do not wish to have several processes waiting for the lock, you may wish to look into Resource Roles.  If you would like details on Resource Roles, let me know.

View solution in original post

1 Reply
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: How to run a process SEQUENTIALLY on all resources of a resource group?

Jump to solution

To execute one at a time within a resource group, and in a situation where order of execution is not important (which resource executes first or second, etc.), I would recommend using resource locks.  Within your component process, use the process step Utility Steps | Resource Lock.  Create a name for the Resource Lock that such as

    ${p:component.name}-${p:componentProcess.name}-${environment.name}

As the processes start to execute, if the first step requires obtaining a lock on that name, only one resource at a time may obtain the lock, the others will wait.

 

If you wish to control the ordering of these, or if you do not wish to have several processes waiting for the lock, you may wish to look into Resource Roles.  If you would like details on Resource Roles, let me know.

View solution in original post

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.