adapteragent Properties for using Database/EMS
For a multi-agent, multi-machine environment using an external database, Oracle, and TIBCO Enterprise Message Service, the properties in the adapteragent.ini file are important.
| Property Name | Description |
|---|---|
| admin.technology.dbems.db.driver | The Database provider.
Example: dbdriver=oracle.jdbc.OracleDriver |
| admin.technology.dbems.db.connectionURL | The Database URL. The Database URL is the host, the port, and the ID of the port.
Example: dbconnectionURL=jdbc:oracle:thin:@<host>:<port>:<sid> |
| admin.technology.dbems.db.userName=<user> | The Database user.
Example: dbuserName=<user> |
| admin.technology.dbems.db.password | The Database user password.
You can obfuscate or encrypt the password if required. To obfuscate the password, see the Note provided under step 2 in "Enabling Database/EMS". Example: dbpassword=<password> |
| admin.technology.dbems.ems.ServerUrl | The EMS server URL.
Example: emsServerUrl=tcp://localhost:7222 |
| admin.technology.dbems.ems.UserName | The EMS user. If a value is not specified, then the EMS user would default to admin user.
Example: emsUserName=admin |
| admin.technology.dbems.ems.Password | The EMS user password. If a value is not specified, then the password would default to blank.
You can obfuscate or encrypt the password if required. To obfuscate the password, see the Note provided under step 2 in "Enabling Database/EMS". Example: emsPassword=<password> |
| admin.technology.dbems.ems.requestQueueName | The EMS member queue. The queue name is unique and is the adapteragent machine name preceded by "afx".
Example:emsrequestQueueName=afx.admin.operations.queue.%HOSTNAME% |
| admin.technology.technology.dbems.ems.qin.EMSPrefix | The EMS Adapter Agent Qin group name prefix. This property is optional and the default value is "EMSGMS".
Example: emsqinEMSPrefix=EMSGMS |
| admin.technology.dbems.ems.requestTimeout | The EMS request timeout to agent (ms). The default value is 60000 milliseconds.
Example: emsrequestTimeout=60000 |
| admin.technology.dbems.ems.reconnection.interval | The EMS reconnection interval (ms). If a value is not specified, then the reconnection interval would default to 10000.
Example: emsreconnectioninterval=10000 |
| admin.technology.dbems.ems.ssl.trust.identity | The EMS SSL connection trusted identity. It consists of the certificate, private key and optionally extra issuer certificates can be included into a single data block using PKCS12, KeyStore or Entrust Store encodings.
Example: ssltrustidentity={EMS_HOME}/samples/certs/client_identity.p12 |
| admin.technology.dbems.ems.ssl.trust.cert.location | The location of the EMS SSL connection trusted root certificate. The set of Trusted Certificates represents all trusted issuers of the server certificate. It must be specified by the client application unless the host certificate verification is completely disabled.
Example: ssltrustcertlocation={EMS_HOME}/samples/certs/server_root.cert.pem |
| admin.technology.dbems.ems.ssl.trust.password | The EMS SSL connection trust password. This property is required if the JMS server protocol is ssl.
You can obfuscate or encrypt the password if required. To obfuscate the password, see the Note provided under step 2 in "Enabling Database/EMS". Example: ssltrustpassword=<password> |
| admin.technology.dbems.ems.ssl.disable.verify.host.name | The EMS SSL host name verification. The trusted certificate commonname must match the ems server hostname if set to false.
Example: ssldisableverifyhostname=false |
| admin.technology.dbems.ems.ssl.disable.verify.host | The EMS SSL host verification. The client and server certificates must match if set to false.
Example: ssldisableverifyhost=false |