Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 5 Advanced Topics : Local Repository Locator String

Local Repository Locator String
Applications built using the TIBCO Adapter SDK use a locator string to specify the repository location and other properties. For local repositories, the string starts with the instance name, which can optionally be preceded by localrepo@. The instance name can either be a fully qualified path or a relative path. The .dat extension is optional.
In addition, clients support the following optional properties separated by colons:
CLIENT_USAGE_DONT_CARE—Client reads until update, then switches to write. This is the default.
CLIENT_USAGE_READ_ONLY—Client is not allowed to do updates.
CLIENT_USAGE_READ_WRITE—Client can do both reads and updates.
CLIENT_USAGE_REACQUIRE_INSTANCE_LOCK—Client is allowed to overwrite this local repository even if a lock file exists, as long as it’s the same user.
CLIENT_USAGE_FORCE_INSTANCE_LOCK—Client is allowed to overwrite this local repository even if a lock file exists. WARNING: Using this option may result in other users overwriting your project.
See Repository Locking for additional information.
Encryption can be performed explicitly by running the obfuscate tool in TIBCO_HOME\tra\version\bin. The tool obfuscates all values starting with #!.
For example, if a file contains this value: repo.serverPassword=#!RepoTestServerPass
See the TIBCO Runtime Agent Installation guide for additional information.
Examples
 
./instances/myInst.dat:userName=deborah
c:/tibco/administrator/myinstances/myInst.dat:urlFile=c:/tibco/
                                       administrator/props/deborah
myProj.dat
myProj
myProj/myrepo.dat

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved