Tibco TCP-BW6 Actual Questions

All the configurations required for the managed daemons are saved in local configuration files on the host where the managed daemon is running.

If there are pre-RV8.x release Rendezvous daemons running in the same network as RVDM, then RVDM is prevented from starting successfully.

When an inactive managed daemon becomes active again, the server ensures that the daemon receives and confirms the configuration update.

When administrators modify the configuration in RVDM, the server pushes the new configuration to all managed daemons.

Each managed daemon receives and installs the updated configuration from RVDM and confirms receipt to the RVDM server.

If a User task does not have a form or Pageflow linked to it, then it will create a default form at deployment.

One form cannot be called from more than one User task.

If a User task does not have a form or Pageflow linked to it, then it will indicate an error at deployment.

One form can be called from more than one User task.

Subflows can be nested, but SpawnWorkflows can not.

Both execution modes are supported by both activities.

SpawnWorkflow is ASYNCHR and Subflow is SYNCHR.

Subflow is ASYNCHR and SpawnWorkflow is SYNCHR.

Both Subflows and SpawnWorkflow can be nested.

since most clients are based in the U.S., use the TIBCO ActiveMatrix cluster at the U.S. site to set up a single worldwide ActiveMatrix Service Grid, with environments spanning the U.S. and Hong Kong sites

set up one ActiveMatrix cluster at each site, and use standard SOAP/HTTP or SOAP/JMS to integrate the two

sites

since most backend systems are in Hong Kong, use the TIBCO ActiveMatrix cluster at the Hong Kong site to O set up a single worldwide ActiveMatrix Service Grid, with environments spanning the U.S. and Hong Kong sites

The information provided is insufficient to determine a solution.