| tibco.clientVar.CL/Logging/fileFilter
|
| |
Specifies the lists of facade operation as a pipe ('|') separated string. The transaction logs of these facade operations are logged to the files instead of database.
For example:
ping|test|addConfiguration
|
| tibco.clientVar.CL/Logging/files/directory
|
| |
Specifies the directory name to store the log file used by the Core Engine to record the transactions of facade operations.
The default value is
ASG_HOME/bin/logs.
|
| tibco.clientVar.CL/Logging/files/transactions
|
| |
Specifies the name of the log file used by the Core Engine to record the transactions data. This is used only for the transactions of facade operations which are filtered by the
tibco.clientVar.CL/Logging/fileFilter property.
The default value is
trans_log.txt.
|
| tibco.clientVar.CL/Logging/files/maxcount
|
| |
Specifies the maximum number of log files for the Core Engine to keep on roll over for the transactions log file.
The default value is
3.
|
| tibco.clientVar.CL/Logging/files/maxsize
|
| |
Specifies the maximum size (in bytes) of the log file for writing the transactions data at which the Core Engine rolls over to the next log file.
The default value is
5000000.
|
| tibco.clientVar.ASG/Logging/tsFormat=yyyyMMdd HH:mm:ss.SSSS
|
| |
Specifies the format of the log's timestamp value.
|
| tibco.clientVar.Common/Connections/RV/SubjectPrefix
|
| |
Specifies the prefix for all Rendezvous subject names used between the Core Engine and Central Logger.
The default value is
TIBCO.ASG.INTERNAL.
|
| RV Session Connection Parameters
|
| tibco.clientVar.ASG/CL/RV/RvService
|
| |
Specifies the service parameter for Rendezvous used between the Core Engine and Central Logger communication.
The default value is
7500.
|
| tibco.clientVar.ASG/CL/RV/RvDaemon
|
| |
Specifies the daemon parameter for Rendezvous used between the Core Engine and Central Logger communication.
The default value is
tcp:7500
.
|
| tibco.clientVar.ASG/CL/RV/RvNetwork
|
| |
Specifies the network parameter for Rendezvous used between the Core Engine and Central Logger communication.
|
| Database Connection Parameters
|
| be.dbconcepts.dburi
|
| |
/CentralLogger/SharedResources/Logging Database.sharedjdbc
|
| be.dbconcepts.connection.retry.count
|
| |
Specifies the number of attempts to be made for the Central Logger to connect to the database server.
|
| be.dbconcepts.connection.check.interval
|
| |
Specifies the time interval (in seconds) for the Central Logger to connect to the database server.
The default value is
5.
|
| tibco.clientVar.CL/Database/Username
|
| |
Specifies the username for the Central Logger to connect to the database server.
The default value is
asguser.
|
| tibco.clientVar.CL/Database/Password
|
| |
Specifies the password for the Central Logger to connect to the database server.
|
| tibco.clientVar.CL/Database/Driver
|
| |
Specifies the database driver for the database server used by the Central Logger.
For example:
For oracle database, the value is defined as:
oracle.jdbc.OracleDriver.
For MS SQL server, the value is defined as:
com.microsoft.sqlserver.jdbc.SQLServerDriver.
|
| tibco.clientVar.CL/Database/Url
|
| |
Specifies the database server connection URL for the Central Logger.
For example:
For oracle database, the value is defined as:
jdbc:oracle:thin:@localhost:1521:asgstat.
For MS SQL server, the value is defined as:
sqlserver://localhost:1433;databaseName=asgstat.
|
| tibco.clientVar.CL/Database/Schema
|
| |
Specifies the database schema to be used by the Central Logger on the database server.
For example:
For oracle database, the value is defined as:
asgstat
For MS SQL server, the value is defined as:
dbo
|
| Enable JMS Transport for Central Logger Properties
|
| tibco.clientVar.ASG/Logging/transport
|
| |
Specifies the transport to be used between the Core Engine and Central Logger component to log the transactions. Valid values are RV or JMS.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JMSProviderURL
|
| |
Specifies the URL to connect to the Enterprise Message Service (EMS) or a JMS server.
Example:
tcp://localhost:7222
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JNDIContextURL
|
| |
Specifies a JNDI connection URL to look up a JMS server.
Example:
tibjmsnaming://localhost:7222
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/TopicConnectionFactoryName
|
| |
Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with JMS server for the Central Logger.
The default value is
TopicConnectionFactory.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/QueueConnectionFactoryName
|
| |
Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with JMS server for the Central Logger.
The default value is
QueueConnectionFactory.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JNDIUsername
|
| |
Specifies the user name to use when logging into the JNDI server. If the JNDI provider does not require access control, this field can be empty.
Example,
admin.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JNDIPassword
|
| |
Specifies the password for logging into the JNDI server. If the JNDI provider does not require access control, this field can be empty.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JMSUsername
|
| |
Specifies the user name to use to authenticate to the JMS server.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/JMSPassword
|
| |
Specifies the password to use to authenticate to the JMS server.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/TransactionReportDestinationName
|
| |
Specifies the name of the JMS destination where the transaction reports are sent to the Central Logger by the Core Engine.
For example,
asg.cl.transaction.queue
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/TransactionReportDestinationType
|
| |
Specifies the type of the JMS destination where the transaction reports are sent to the Central Logger by the Core Engine.
The possible values are
queue or
topic.
The default value is
queue.
The Central Logger always listens on a queue. If the value of destination type is set to
topic, the JMS administrator must configure a bridge between the topic and the queue.
|
| SSL JMS Transport Properties for Central Logger
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/useSSL
|
| |
Specifies if SSL is enabled for the Central Logger when using the JMS transport. Set this to
true to enable SSL for the JMS transport.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/TrustedCertificatesFolder
|
| |
If you use the SSL enabled JMS transport for Central Logger, this field specifies a location of the trusted certificates on this machine. The trusted certificates are a collection of certificates from servers with which you establish connections. If the server with which the connection is going to be established, presents a certificate that does not match one of your trusted certificates, the connection is refused. This prevents connections to unauthorized servers. Import the trusted certificates into a folder before you select the folder in this field.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/Identity
|
| |
Specifies an identity resource used to provide the SSL properties for JMS transport. The default value is:
/Common/SharedResources/JMS/CL_JMSConnIdentityResource.id
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/TrustStorePassword
|
| |
Specifies the password to access the certificate stored in the folder defined by the
Trusted Certificate Folder field. The certificate is required for SSL connection.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/trace
|
| |
Specifies whether SSL tracing should be enabled during the SSL connection. If the value is set to true, the SSL connection messages are logged and sent to the console.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/debugTrace
|
| |
Specifies whether SSL debug tracing should be enabled during the SSL connection. Debug tracing provides more detailed messages than standard tracing.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/verifyHostName
|
| |
Specifies whether the host you are connecting to is the expected host. The host name in the digital certificate of the host is compared against the value in the
Expected Host Name field. If the host name does not match the expected host name, the connection is refused.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/ExpectedHostName
|
| |
Specifies the name of the host you are expecting to connect to. This field is only relevant if the
Verify Host Name field is set to
true. If the name of the host in the digital certificate of host does not match the value specified in this field, the connection is refused.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/strongCipherSuitesOnly
|
| |
When this field is set to true, this specifies the minimum strength of the cipher suites that can be specified with the
bw.plugin.security.strongcipher.minstrength custom engine property. See
TIBCO ActiveMatrix BusinessWorks Administration for more information about this property. The default value of the property disables cipher suites with an effective key length below
128 bits. When this field is set to
false, only cipher suites with an effective key length of up to
128 bits can be used.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/IdentityType
|
| |
Specifies the type of identity resource for SSL connection. The possible values are:
- certPlusKeyURL
- url
- usernamePassword
|
| Properties for Identity Type=usernamePassword
Use this option if you want to use a user name and password for authentication instead of a certificate.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/IdentityUsername
|
| |
Specifies the name of the user for this identity.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/IdentityPassword
|
| |
Specifies the password for the user for this identity
|
| Properties for Identity Type=url
Use this option if the certificate includes the private key information in the same file.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/IdentityFileType
|
| |
Specifies the type of certificate file if
Identity Type is set to
url.
The accepted values are as follows:
- Entrust
- JCEKS
- JKS
- PEM
- PKCS12
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/IdentityURL
|
| |
Specifies the location of the certificate (which includes the private key) if
Identity Type is set to url.
For example,
C:\asgserver.pfx
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/KeyPassword
|
| |
Specifies the password for the certificate if
Identity Type is of
url type.
|
| Properties for Identity Type=certPlusKeyURL
Use this option if the private key and the certificate are in two separate files.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/KeyPassword
|
| |
Specifies the password for the certificate if
Identity Type is of
certPlusKeyURL type.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/CertificateURL
|
| |
Specifies the URL to the certificate file if
Identity Type is of
certPlusKeyURL type.
|
| tibco.clientVar.Common/Connections/JMS/CL_JMSConnection/KeyURL
|
| |
Specifies the URL to the private key in the certificate file if
Identity Type is of
certPlusKeyURL type.
|
