Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Administering a Distributed Environment : Setting Up Access to the Data

Setting Up Access to the Data
When the required physical connections are made so that users can access data at a location remote to your node, additional preparation is required. As the administrator, you must make sure:
Accessing a Default Store of Data
As described in Order of Evaluation to Determine Location, the location of data to be used by an application is resolved according to a specific order of evaluation. However, you can set a default location for use in a user’s session when a more explicit value is not provided. Two tools are provided with TIBCO Object Service Broker that you can use to manage this default value:
 
Returns the present value of the default remote location.
Nodes Available
You can access a list of node names that are available to your local node through the Resource Management facility from the TIBCO Object Service Broker Administration menu.
Changing the Default Location for User Sessions
In some instances it can be necessary for you to change the default remote location for your users. Use SETREMOTELOC and REMOTELOCATION to change this value.
Sample Rule
The following rule changes the default remote location, if it is not already the value required.

 
RULE EDITOR ===> SCROLL: P
CHANGE_LOCATION(VALUE);
_
_ ---------------------------------------------------------------------------
_ VALUE = REMOTELOCATION; | Y N
_ ------------------------------------------------------------+--------------
_ CALL SETREMOTELOC(VALUE); | 1
_ CALL ENDMSG(’THE LOCATION IS ’ || VALUE); | 1 2
_ ---------------------------------------------------------------------------

 
Setting Adequate Security
Security considerations are dependent on the type of security being used: TIBCO Object Service Broker, external, or mixed.
TIBCO Object Service Broker Security
If you specify TIBCO Object Service Broker security using the SECURITY External Environment parameter, security is local to the data and must be defined at the location where it is stored. You must ensure that the following security requirements are met at the local and remote nodes in order for a user to access remote data.
Same on both nodes and cannot be null if TIBCO Object Service Broker security is being used to verify login access.
Security groups
Current group of the user ID on the local node must be a group defined on the remote node. The group does not have to be the current group on the remote node and the security permissions for the groups can differ.

1
For more information on case sensitivity of passwords, refer to TIBCO Object Service Broker Managing Security.

External Security
If local user login is authenticated through an external security provider, when accessing a remote node the security requirement for a corresponding user ID and password is no longer applicable.
Mixed Security
In instances where both TIBCO Object Service Broker security and an external security provider are in use, the authentication process checks for TIBCO Object Service Broker security parameters first. If these are not in place, external security parameters are used.
How Do You Ensure Integrity?
In a distributed data environment, if data integrity is to be ensured, you must make sure that the Fail Safe level is set to two on each node that is being accessed.
See Also
Installing and Operating for your operating environment for more information about the Resource Management facility.
TIBCO Object Service Broker Shareable Tools for more information about the SETREMOTELOC and REMOTELOCATION tools.
TIBCO Object Service Broker Managing Security for further information on each of the security types described.
Managing Backup and Recovery for your operating environment for detailed information about Fail Safe levels and processing.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved