Message-ID: <158458116.8127.1711617075691.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8126_990379259.1711617075691" ------=_Part_8126_990379259.1711617075691 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Scoped Resources

Scoped Resources

Scoped resources are similar to global resources in that they go= vern a resource available to the entire system. However, they may also be r= estricted on a per-host basis as well. For example, a site may have a certa= in number of software licenses, and be restricted to running only one insta= nce of the software per host.

Therefore, the scoped resource specification must not only be set in Sup= ervisor qb.conf, but also for the Worker in either a local qb.conf or the global qbwrk.conf:

Supervisor
supervisor_global_resources =3D re= sspec [, resspec,=E2=80=A6]

Worker
worker_resources =3D resspec [, <= em>resspec,=E2=80=A6]

Instead of global however, resspec uses the keyword scoped;
scoped.name=3Dquantity

When thinking about how to set up a scoped resource, ask these two quest= ions:

  1. How many total resources are available (Supervisor)?
  2. How many can each host get (Worker)?

Example

In this example we have a site with ten Shake licenses, but only one is = allowed to run per host:
supervisor_global_resources =3D scope= d.shake=3D10
worker_resources =3D scoped.shake=3D1

See Also

supervisor_global_= resources
worker_resour= ces

------=_Part_8126_990379259.1711617075691--