After you create a Jolt connection pool you assign (target) it to
servers or clusters. Only servlets or applications on the targeted
servers or clusters can access BEA Tuxedo.
When you target all or part of a cluster, the Administration Console
initiates a two-phase deployment. In general, such a deployment ensures
that if the deployment fails for one active server, it fails for all
Note: To temporarily disable access to
Tuxedo, un-target the connection pool from all servers by deselecting
them on the Target and Deploy tab.
To target Jolt connection pools:
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
Administration Console, expand Interoperability
and select Jolt Connection Pools.
On the Jolt
Connection Pools page, click the name of a connection pool.
Select the Target and Deploy tab.
To target servers that are not part of a cluster, under
Servers, check the server name.
To target all or
part of a cluster, under Clusters check one or
more clusters. Then:
To assign a connection pool to the all of the servers in a
cluster, select All servers in the
To assign a connection pool to selected servers in a
cluster, select Part of the cluster. Check
one or more servers in the cluster.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart (see Use the Change Center).