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

Client Configuration

A client is something (often a machine) that is going to submit = jobs, but not run them. Compared to the Worker, client configuration is a v= ery simple process - the only thing that requires configuration is the name= of the Supervisor. The Supervisor setting can be explicitly set, or it can= be determined using auto-discovery.

Like the Workers, Qube! clients can use Supervisor auto-discovery to aut= omatically determine the Supervisor if on the same network subnet. There is= a drawback to using auto-discovery: each time a client application execute= s, it must rediscover the Supervisor. This could result in a slight increas= e in network traffic or a noticeable delay in execution as the clients wait= s for a response to the query.

To avoid this added network traffic, you should explicitly set the Super= visor hostname for the client. This can be done from the WranglerView UI un= der "Administration->Configure (local)=E2=80=A6" or by manuall= y editing the client's qb.conf file to specify the qb_supervisor value.

File Locations

The qb.conf file is located in the following directories depending on th= e platform:

See Also

qb_supervisor

------=_Part_9146_621013333.1711721868867--