Open topic with navigation

TIBCO GridServer® 7.1.0

# Disabling Resource Deployment

There are some situations in which you might not want to use the Resource Manager for replication. For example, you might want to use another shared location for Grid Libraries, deploy resources manually, or deploy different sets of resources to different Brokers.

There are four different strategies for disabling resource deployment:

| • | Disabling Director to Broker synchronization on the Director.

| • | Disabling Director to Broker synchronization on the Broker.

| • | Disabling Broker to Engine synchronization on the Broker.

| • | Disabling Broker to Engine synchronization in an Engine Configuration.

Each of the strategies is described below.

Note that for manual deployment, when you deploy Grid Libraries, you must click the Update button on the Services > Services > Grid Libraries page to notify all Engines to rescan their directories.

## Disabling Director to Broker Synchronization on the Director

If you want to have different sets of resources on different Brokers, you can disable the Director to Broker resource synchronization on the Director. This causes none of the Brokers reporting to that Director to synchronize resources with that Director. The Brokers continue to synchronize resources with their Engines.

To disable Director to Broker synchronization on the Director, go to Admin > System Admin > Manager Configuration > Resource Deployment, and under the Director Settings heading, change Synchronize Resources To All Brokers to False.

When you disable Director to Broker Synchronization, if for any reasons your Engines move to a different Broker, they need to synchronize their resources with the new Broker. This can result in a significant delay in the Engine being able to take tasks and can cause a severe increase in network traffic depending on how many Engines move.

Warning | Grids that rely on Engines being shared are strongly recommended not to use this option. If you must use this option, minimize Engine movement by disabling Engine sharing and balancing. In general, we do not recommend you use this option and consider Grid Library filters instead.

## Disabling Director to Broker Synchronization on the Broker

In some situations, it might be desirable to disable Director to Broker resource synchronization on specific Brokers, while still permitting Broker to Engine resource synchronization. For example, allowing “last week’s” tasks to run to completion on a limited subset of the grid, while permitting “this week’s” tasks to be launched with new resources.

This is similar to disabling synchronization on the Director, but because the setting is on the Broker, it is used on a case-by-case basis. You can have some Brokers synchronize, and disable synchronization on others.

To disable Director to Broker synchronization on a Broker, go to Admin > System Admin > Manager Configuration > Resource Deployment, and under the Broker Settings heading, change the value of Synchronize Resources From Director to False.

Note | If you disable synchronization on the Director, no Brokers synchronize with the Director regardless of this setting on the Broker.

## Disabling Broker to Engine Synchronization on the Broker

If you want to manually deploy resources to Engines, such as when you use a shared resource location on a shared file system, you can disable synchronization between a Broker and all of its Engines.

To manually deploy resources:

| 1. | Go to Admin > System Admin > Manager Configuration > Resource Deployment, and under the Broker Settings heading, change the value of Synchronize Resources to Engines to False.

| 2. | Unpack the required Grid Libraries in a shared location, such as a shared network drive that the Engines can access. You must manually extract the resource files, as the Engine won’t unpack them.

| 3. | In the Engine Configuration, set Grid Library Path to the location of the shared resources from step 2.

Note | When Broker to Engine synchronization is disabled, Director to Broker synchronization still occurs. This means the Engines still auto-upgrade themselves when an update is installed.

## Disabling Resource Synchronization in Engine Configuration

To change resource synchronization on a per-Engine basis, in the Engine Configuration, under the Resource Validation heading, change the value of Synchronize Resources to False. When an Engine with this setting disabled logs in, it does not synchronize resources.

This is useful when you want to isolate a set of Engines and prevent them from doing any resource synchronization from any Broker. This must not be used if you want to manually deploy your resources.

Note | When resource synchronization is disabled in the Engine Configuration, Engines do not auto-upgrade themselves when an update is installed or when the grid is upgraded.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO GridServer®

Copyright © 2001-2022. TIBCO Software Inc. All Rights Reserved.