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


Chapter 5 Advanced Topics : Server-Based Repository Locator String

Server-Based Repository Locator String
Applications built using the TIBCO Adapter SDK use a locator string to specify their application data’s repository location and other properties. The locator string is also used by repository management tools (see Chapter 6, Command Line Utilities), TIBCO BusinessWorks engines, and other TIBCO products.
Depending on how a client accesses the domain repository (4.x legacy projects) or application repository, the locator string differs, as discussed in the following sections:
TIBCO Rendezvous
In case of a TIBCO Rendezvous transport, the locator string begins with tibcr:// or tibcr@, followed by the instance name. In addition, the optional properties listed in Table 8 are supported. Each property is separated by a colon.
TIBCO Rendezvous rvd daemon value.
TIBCO Rendezvous rvd service value.
TIBCO Rendezvous rvd network value.
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.
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
 
tibcr://myInst:service=5456:userName=ann:timeout=4000
tibcr@myInst:service=5456:urlFile=/tibco/props/fredsProps.txt
tibcr://myInst:urlFile=/tibco/props/fredsProps.txt
HTTP and HTTPS
In case of HTTP transports, the locator string begins with http://.
In case of HTTPS transports (HTTP over Secure Socket Layer) the locator string begins with https://.
Host name and port number are next (http://host:port).
The host name and port number are followed by the instance name, which is preceded by a question mark (?), for example, http://host:8080/?inst1
Optionally, administrator/repo may be included as part of the instance name, for example, http://host:8080/administrator/repo/?inst1
HTTPS-specific properties should be placed in a property file and that file should be specified using "urlFile=". If you do not wish to specify HTTPS validation properties, urlFile is not a required property for HTTPS.
In addition, remote HTTP or HTTPS clients support the following optional properties separated by &. Note that when & is used as the separator of properties, and the URL is specified on the command line, the URL should be enclosed in quotes so that the shell does not interpret it.
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.
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
 
"http://host:8080?myInst&userName=ann&timeout=4000"
"http://host:8080/administrator/repo?myInst&userName=ann&timeout=
                                                             4000"
"https://host:8443?myInst&urlFile=httpsProps.ini"
"https://host:8443/administrator/repo?myInst&server=s1&userName=
                                               bob&password=bswrd"
"https://host:8443/administrator/repo?myInst&urlFile=
                                                   httpsProps.ini"
Creating a urlFile for Use With HTTPS
To use HTTPS, the following information must be included in the properties file:
For Java repository clients, this can be either j2se or entrust61. This string is case sensitive.
Password for the certificate specified by trustedCerts. This property is not relevant for C++ repository clients.
Example for Java Applications
Following is an example for a url file containing HTTPS-specific properties for Java applications:
 
httpsVendor=j2se
trustedCerts=H:/downloads/certs/clientcerts/trustedcerts/RSA/PEM/
                                               RSA1024ca1.cert.PEM
trustedCertFormat=PEM
trustedCertPassword=RSA1024ca1
identityFile=H:/downloads/certs/clientcerts/idcert/RSA/P12/
                                               RSA1024ca2.cert.P12
identityType=P12
keyPassword=RSA1024ca2
Example for C++ Applications
Following is an example for a url File containing HTTPS specific properties for a C++ application:
 
httpsVendor=j2se
trustedCerts=H:/downloads/certs/clientcerts/trustedcerts/RSA/PEM/
                                               RSA1024ca1.cert.PEM
trustedCertFormat=PEM
trustedCertPassword=RSA1024ca1
identityFile=H:/downloads/certs/clientcerts/idcert/RSA/P12/
                                               RSA1024ca2.cert.P12
identityType=P12
keyPassword=RSA1024ca2
egdSocket=/etc/egd-pool

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