OasisConfig.Properties Reference › Oasis Configuration Properties File

Oasis Configuration Properties File

The Oasis Configuration properties file (OasisConfig.properties) contains the property settings for all aspects of CA Process Automation. The file is located in the install_dir/server/c2o/.config folder. All users with access to the CA Process Automation installation location can modify the files. Consider restricting access to this location. Some values must not be edited.

Settings include:

USE_DEPRECATED_COMMS_V1

(For agents only) Determines during the start of an agent whether it uses the new mode of communication or deprecated mode of communication. This is a boolean value.

When the Use Deprecated Communications check box in an agent's properties is selected, this value is set to true. CA Process Automation:

• Terminates the web socket connection from the agent, then passes that information to all of the Orchestrators before termination.
• Cleans the server map where these connection details are stored.

When the Use Deprecated Communications check box in an agent's properties is not selected, this value is set to false.

• The agent creates a new web socket connection and sends connection details for the Orchestrator.
• The Orchestrator saves these connection details in a server map.

See About Agent Communication for more information.

DOMAINID

Defines the unique ID for the Domain.

Example

ac04f945-f08b-4308-aa9c-c3fd95964f4d

CLUSTERNODEID

Determines a node uniquely in a cluster.

Example

8d11558a-3bf7-43d9-b394-4c055229e9ae

KEYSTOREID

Defines the password of the keystore.

Example

ac04f945-f08b-4308-aa9c-c3fd95964f4d

itpam.web.keystorepath

Defines the path of the keystore that is used for signing jars.

Example

C:/Program Files/CA/PAMcert_Java7_Node2/server/c2o/.config/c2okeystore

itpam.web.keystore.password

Defines the password of the keystore that is used for signing jars.

Example

LQotQj55Y8dPGRRXkrF4yTyk/IwzTcT0rLY+pWeGrGHaRKnlcXHL3fr7pYIzjVhoGdrnRxSO4Prl70rIxqs3fCGIgFVIAnOzICQ9ct4qXIBIPnxQcgflrF0WDdaIjCS6ubKwe9Wxhn0xjnmctvkLnMC1L74b48yQd9yhWSMAgpLAPLPJiMz/VoIzcFVylqLS44KdM+wH6b6xkqVJECSH1GolBG2QUj/2

itpam.web.keystorealias

Defines the alias name of the certificate in the keystore that is used for signing jars.

Example

ITPAM

CERTPASSWORD

Defines the password that is used to control access to the keystore that is used to encrypt passwords and other critical data.

Example

XNASLujiOdl6POYm8CwjBTHnFUlbXQLcPqd+xc7oJkPF5X3cq8UHbEYL4iH+01b1EmwHhw9uPXqDABcJqIJ+ECmODDAMn7rytSWqli+oxKp+e5scp1fnHjF1ENCKZNasYy6nF6vPozT9qLmB7DhzuFAvg8Av9J/U4ngYrZ5AMdU1sFP5Ddf3nw==

oasis.database.username

Defines the user name for the Library database server.

Example

sa

oasis.database.password

Defines the password that is associated with the specified library database server user.

Example

SSb28pTxSL4fxuv+8IV8zLz+S6jwleU4mpQTDTM1xmwQ037qmAjDO74Y569W3LIP0vBUEkJ30raf3/RsodMLdL3L51cnz8Gus4mJfGJla7WdTtzx0ts0BuUFPxZ1pOpHOUUljFHn73243Iv7/pXIQe+O8lrHB00XotDicrleXavs+8sXSIPqKyX3gmjy6LUZ

oasis.database.dbhostname

Defines the host name of the library database server.

Example

lodivsa205

oasis.database.dbport

Defines the Library database server connection port number.

Example

1433

oasis.database.connectionurl

Defines the Library database JDBC connection URL.

Example

jdbc:sqlserver://lodivsa205:1433;databaseName=

oasis.database.databasetype

Defines the type of library database.

Example

MSSQLServer2005

oasis.database.dialect

Defines the user-defined dialect class of the library database.

Example

com.optinuity.c2o.persistence.MSQLServerDialect

oasis.database.genericdialect

Defines the dialect class of the library database.

Example

org.hibernate.dialect.SQLServerDialect

oasis.database.driver

Defines the fully qualified name of the JDBC driver class.

Example

com.microsoft.sqlserver.jdbc.SQLServerDriver

oasis.database.typemapping

Defines the type mapping for the datasource.

Example

MS SQLSERVER2000

oasis.database.exceptionsorter

Defines a class that implements the org.jboss.resource.adapter.jdbc.ExceptionSorter interface. The interface examines database exceptions to determine whether they indicate a connection error.

Example

org.jboss.resource.adapter.jdbc.vendor.SybaseExceptionSorter

oasis.database.validConnectionChecker

Defines a class that implements the org.jboss.resource.adapter.jdbc.ValidConnectionChecker interface. The interface provides a SQLException isValidConnection(Connection e) mode. The application calls the mode with a connection that is returned from the pool to test its validity.

Example

org.jboss.jca.adapters.jdbc.extensions.mssql.MSSQLValidConnectionChecker

oasis.database.datasource.class

Defines the datasource class.

Example

com.microsoft.sqlserver.jdbc.SQLServerXADataSource

oasis.database.additionalparamurl

Defines parameters that are used to create the database connection.

Example

responseBuffering=full;SelectMethod=cursor;

oasis.database.lib.dbname

Defines the name of the library database.

Example

pamgacert_cluster_JDK7_rep

oasis.database.queues.dbname

Defines the name of queues database.

Example

pamgacert_cluster_JDK7_run

oasis.reporting.database.databasetype

Defines the type of reporting database.

Example

MSSQLServer2005

oasis.reporting.database.username

Defines the user name for the reporting database server.

Example

sa

oasis.reporting.database.password

Defines the password that is associated with the specified user for the reporting database server.

Example

oIzz9oH5OU4XRkOaeLblNqEYDsaXNGiMg9LSy2P7gsVLG0ea32nBlUIvXgEXhiKfGzIbCmYFgYoFg0sVBlnY/k1sAeZ21z20sw5Yr9HC2B3+IRoyy5LXCmByMUMc7Ywq/BocPnw4e1DBDDfGqCQL/6ciK4CT1C7hU/V3Y4Ktrc9IsPK1aXeNRM1qvpVwBAtG

oasis.reporting.database.dbhostname

Defines the host name of the reporting database server.

Example

lodivsa205

oasis.reporting.database.dbport

Defines the reporting database server connection port number.

Example

1433

oasis.reporting.database.genericdialect

Defines the dialect class of the reporting database.

Example

org.hibernate.dialect.SQLServerDialect

oasis.reporting.database.driver

Defines the fully qualified name of the JDBC driver class.

Example

com.microsoft.sqlserver.jdbc.SQLServerDriver

oasis.reporting.database.typemapping

Defines the type mapping for the data source.

Example

MS SQLSERVER2000

oasis.reporting.database.dialect

Defines the user-defined dialect class of the reporting database.

Example

org.jboss.resource.adapter.jdbc.vendor.SybaseExceptionSorter

oasis.reporting.database.ValidConnectionQuery

Defines an SQL statement to run on a connection before it returns from the pool to verify its validity to test for stale pool connections. For example: select count(*) from x.

Example

select 1

oasis.reporting.database.connectionurl

Defines the reporting database JDBC connection URL.

Example

jdbc:sqlserver://lodivsa205:1433;databaseName=

oasis.reporting.database.additionalparamurl

Defines the additional parameters to use for creating the database connection.

Example

;responseBuffering=full;SelectMethod=cursor;

FIPS_COMPLIANT

Specifies whether the CA Process Automation server is FIPS-compliant.

Example

true

oasis.reporting.database.dbname

Defines the name of the reporting database.

Example

pamgacert_cluster_JDK7_rpt

oasis.runtime.database.dbtype

Defines the runtime database type.

Example

MSSQLServer2005

oasis.runtime.database.username

Defines the user name for the runtime database server.

Example

sa

oasis.runtime.database.password

Defines the password that is associated with the specified user for the runtime database server.

Example

SOIjQ79jp66tm5E7ZYxLV2yqtVV54HRVs+xvNksG7p1pzTZOoOXahwS0XOcVoMl8MznkgQgVOllCIU/YBx6lT3ZAxnzOMY2xBQnIp5xTxw0Dv5eqqTvpOnm6P2vPOS1RzYGA6GRt3VdASiTZwZs/BkIX/sY+6C52V/x5Eg7l4hff6/6gS6wvRHdJG/sXU6D6

oasis.rntime.database.dbhostname

Defines the host name of the runtime database server.

Example

lodivsa205

oasis.runtime.database.port

Defines the runtime database server connection port number.

Example

1433

oasis.runtime.database.dialect

Defines the user-defined dialect class of the runtime database.

Example

com.optinuity.c2o.persistence.MSQLServerDialect

oasis.runtime.database.genericdialect

Defines the dialect class of the runtime database.

Example

org.hibernate.dialect.SQLServerDialect

oasis.runtime.database.driver

Defines the fully qualified name of the JDBC driver class.

Example

com.microsoft.sqlserver.jdbc.SQLServerDriver

oasis.runtime.database.typemapping

Defines the type mapping for the data source.

Example

MS SQLSERVER2000

oasis.runtime.database.exceptionsorter

Defines a class that implements the org.jboss.resource.adapter.jdbc.ExceptionSorter interface to examine database exceptions to determine whether the exception indicates a connection error.

Example

org.jboss.resource.adapter.jdbc.vendor.SybaseExceptionSorter

oasis.runtime.database.ValidConnectionQuery

Defines an SQL statement to run on a connection before it returns from the pool to verify its validity to test for stale pool connections. For example: select count(*) from x.

Example

select 1

oasis.runtime.database.validConnectionChecker

Defines a class that implements the org.jboss.resource.adapter.jdbc.ValidConnectionChecker interface to provide a SQLException isValidConnection(Connection e) method. A connection that returns from the pool calls this method to test its validity.

Example

org.jboss.jca.adapters.jdbc.extensions.mssql.MSSQLValidConnectionChecker

oasis.runtime.database.datasource.class

Defines the data source class.

Example

com.microsoft.sqlserver.jdbc.SQLServerXADataSource

oasis.runtime.properties.table.create.stmt

Defines the SQL statement to use to create the properties table if it is not present. The user is not expected to modify this statement because the application configures the correct value for the relevant database by default.

Example

create table properties (propkey varchar(255) NOT NULL,propvalue NVARCHAR(MAX),PRIMARY KEY (propkey))

oasis.runtime.database.connectionurl

Defines the runtime database JDBC connection URL.

Example

jdbc:sqlserver://lodivsa205:1433;databaseName=

oasis.runtime.database.additionalparamurl

Defines the additional parameters that are used to create the database connection.

Example

;responseBuffering=full;SelectMethod=cursor;

oasis.runtime.database.driver.name

Defines the runtime database driver name.

Example

com.microsoft.sqlserver.jdbc.SQLServerDriver (for a MSSQL database) 

oasis.runtime.database.dbname

Defines the name of the runtime database.

Example

pamgacert_cluster_JDK7_run

oasis.security.server.type

Defines the type of security server that is used for authentication and authorization.

Example

EEM

oasis.policy.type

Defines the type of login policy.

Example

EEM

certificatefolderFullpath

Defines the path of the folder that contains the security certificate. The path is relative to the c2o folder.

Example

install_dir/server/c2o/.c2orepository/public/certification/

oasis.eem.backend.server.location

Defines the host name of the computer that hosts the EEM security server.

Example

lodivsa205

oasis.eem.application.name

Defines the application name in the EEM server on which the policies are defined for the current CA Process Automation instance.

Example

pamgacert_cluster_JDK7

isFipsMode

Specifies whether the EEM server is running in FIPS mode.

Example

false

oasis.eem.certificate.path

Defines the name of the security certificate.

Example

PAM.p12

eiamCertKeyPath

Defines the name of the security certificate key file that is used for authentication. This property is only applicable if isFipsMode=true.

Example

PAM.key

oasis.eem.certificate.password

Defines the password that is associated with the EEM security certificate. This property is only applicable if isFipsMode=false.

Example

dD65vFTVmbn8aaZxjot9QCUIfPEey1H8/KGtNShgrronJk0rMtqliDMrNo2VE+xoAUDcfmT9IPCQsAe497w1xUBkHg8PbZNjWVkPpFYw496eFiwiq7AoyB8WCoUrx8wVnkMjoGs1BqDND+kjHcnUt9HLljYgxatT7Q2FpbTA7+Qag0W9gSv2oH4iBsUjVs22

ntlm.enabled

Specifies whether NTLM authentication is enabled. When changing this port, remove the .c2o folder in the ${Installation Dir}/server/c2o/.system folder, if it exists.

oasis.jxta.port

Defines the port to use for communication with other Orchestrators or agents.

Example

7001

oasis.jxta.host

Defines the host name of the computer that is used for communication with the Orchestrator or agent.

Example

name03-I40136.ca.com

oasis.local.hostname

Defines the host name of the computer where CA Process Automation is installed.

Example

name03-I40136.ca.com

oasis.server.isCluster

Specifies whether this CA Process Automation instance is clustered.

Example

true

loadbalancer.worker.node

Defines the name of this node in the cluster. This property is applicable only if it is a part of cluster.

Example

node2

oasis.snmptrigger.service.port

Defines the listening port for SNMP triggers.

Example

162

oasis.transport.secure

Specifies whether communication is secure.

Example

true

AcceptAllSSLCertificates

Specifies whether to accept all certificates in secure communication.

Example

true

oasis.reject.unnecessary.approval

Specifies whether to reject an interaction form which has not been configured for approval.

Example

true

managementconsole.timeout

Defines the timeout (in minutes) for CA Process Automation. The timeout is the interval CA Process Automation can be idle, after which the session expires.

Example

30

eem.connection.retries

Defines the number of retries for authentication when the security server is EEM.

Example

3

SSL_PROTOCOL

Defines the SSL protocol type. If the Java vendor is IBM Corporation, SSL protocol is used. Otherwise, TLS is used.

Example

TLS

X509_ALGORITHM

Defines the algorithm that is used for SSL certificates. If the Java vendor is IBM Corporation, the algorithm that is used is IbmX509. Otherwise, SunX509 is used.

Example

SunX509

oasis.publisher.name

Defines the name under which this CA Process Automation instance is licensed.

Example

CA

jboss.partition.udpgroup

Defines the multicast address for this cluster node.

Example

228.1.46.192

jboss.rmi.port

Defines the port of the RMI naming service.

Example

1098

jboss.jndi.port

Defines the listening port for the bootstrap JNP(JNDI Provider) service.

Example

1099

jboss.rmi.classloader.webservice.port

Defines the port that is used for the simple HTTP service that supports requests for classes for RMI dynamic class loading, org.jboss.web.WebService.

Example

8083

jboss.rmi.object.port

Defines the RMI server socket listening port to which RMI clients connect when communicating through the proxy interface.

Example

4444

jboss.pooledinvoker.serverbind.port

Defines the pooled invoker server bind port.

Example

4445

remoting.transport.connector.port

Defines the remoting server bind port.

Example

4448

jboss.ha.jndi.port

Defines the port on which the HA-JNDI stub is made available.

Example

1100

jboss.ha.jndi.rmi.port

Defines the RMI port that the HA-JNDI service uses when bound.

Example

1101

jboss.ha.rmi.object.port

Defines the RMI object port that JRMPInvokerHA uses.

Example

4447

jboss.ha.pooledinvoker.serverbind.port

Defines the pooled invoker HA server bind port.

Example

4446

jboss.mcast.jndi.autodiscovery.port

Defines the multicast group port that is used for JNDI autodiscovery. This port is defined in cluster-service.xml and hajndi-jms-ds.xml in deploy/jms.

Example

1102

jboss.mcast.ha.partition.port

Defines the multicast UDP port for HAPartition. This port is defined in cluster-service.xml and jmx-console.war/WEB-INF/web.xml.

Example

45566

jboss.mcast.http.sessionreplication.port

Defines the multicast UDP port for HttpSession replication. This port is defined in tc5-cluster-service.xml.

Example

45567

tomcat.connector.http.port

Defines the port for the connector component that supports the HTTP/1.1 protocol. This property enables Catalina to function as a stand-alone web server, in addition to its ability to run servlets and JSP pages. The Port is also configured in jboss-ws4ee.sar/META-INF/jboss-service.xml for Axis SService.

Example

8080

tomcat.connector.ajp.port

Defines the port for the connector component that communicates with a web connector through the AJP protocol.

Example

8009

tomcat.secure.port

Defines the secure port that the SSL connector uses. This port is unused. This port is the same port that is configured as:

• redirectPort for the AJP connector in server.xml
• WebServiceSecurePort for Axis Service in jboss-ws4ee.sar/META-INF/jboss-service.xml

The port is of use only if the SSL connector is enabled.

Example

8443

jboss.uil.serverbind.port

Defines the port to which Unified Invocation Layer (UIL) service clients connect when they establish a connection to the JBossMQ server.

Example

8093

oasis.protection.level

Specifies the CA Process Automation protection level. In secure mode, the protection level is set to CONFIDENTIAL, otherwise it is set to NONE.

Values: NONE, INTEGRAL, or CONFIDENTIAL.

itpam.initialperiodicheartbeatfrequency

Defines the initial heartbeat frequency (in minutes).

Example

2

system.encoding

Defines the encoding of this system.

Example

Cp1252

eem.max.search.size

Defines the maximum number of records to search simultaneously in EEM.

Example

10000

jboss.remoting.transport.Connector.port

Defines a JBoss-related port.

Example

3873

OAPort

Defines a JBoss-related port.

Example

3528

OASSLPort

Defines a JBoss-related port.

Example

3529

scripts.tmpDir

Defines the value of the temporary directory that runs scripts.

Example:

C:/Users/ADMINI~1/AppData/Local/Temp/2

oasis.powershell.setexecutionpolicy

Specifies whether the user selected an option to change the PowerShell run policy during installation.

Example

false

oasis.powershell.path

Defines the PowerShell path on the host computer.

Example

C:/Windows/System32/WindowsPowerShell/v1.0

override.jvm.tmpdir

Specifies whether to override the java.io.tmpdir system variable. The default value (true) lets the server refer the system variable to c2oHome/tmp. Set this property to false if you do not want the server to refer the system variable to c2oHome/tmp..

Example

true

jboss.default.jgroups.stack

Defines the default stack type being set up for use by JGroups for the application to run on.

Example

tcp

jboss.jgroups.tcp.tcp_port

Defines the TCP port for TCP-based clustering in JBoss.

Example

7600

jboss.jgroups.tcp_sync.tcp_port

Defines the TCP sync port for TCP-based clustering in JBoss.

Example

7650

jboss.messaging.datachanneltcpport

Defines the TCP-based messaging datachannel port.

Example

7900

jboss.messaging.controlchanneltcpport

Defines the TCP-based messaging control channel port.

Example

7901

jts.default.tx.reaper.timeout

Defines a nonnegative integer that the JBoss Transaction Service requires.

Example

120000

jboss.transaction.timeout

Defines the time when the reaper starts timing out the ongoing transactions after timeout a timeout occurs. JBoss requires this property.

Example

300

jboss.service.binding.port

Defines the File Ref deploy/messaging/remoting-bisocket-service.xml. JBoss Messaging requires this property.

Example

4457

jboss.remoting.port

Defines the File Ref deploy/jmx-remoting.sar. JBoss Remoting requires this property.

Example

1090

jboss.jbm2.port

Defines the communication transport to JBoss Messaging. JBoss Messaging 2 Netty requires this property.

Example

5445

jboss.hbm2.netty.ssl.port

The JBoss. SSL version of Netty requires this property.

Example

5446

jboss.tx.recovery.manager.port

Defines the File Ref deploy/transaction-jboss-beans.xml. JBossTS Recovery Manager requires this property.

Example

4712

jboss.tx.status.manager

Defines the File Ref deploy/transaction-jboss-beans.xml. JBossTS Transaction Status Manager requires this property.

Example

4713

jboss.tx.manager.sock.pid.port

Defines the File Ref deploy/transaction-jboss-beans.xml. JBossTS requires this property.

Example

4714

ucf.payload.file

Defines the name of the file that contains the Catalyst container payload.

Example

catalyst.installer.payload.zip

catalyst.container.name

Defines the name of the Catalyst container.

Example

node0

ucf.connector.enabled

Specifies whether the Catalyst Process Automation Services is enabled.

Example

false

ucf.payload.override

Specifies whether to override the payload (if the payload is present).

Example

false

ucf.pax.web.http.port

Defines the /container/etc/org.ops4j.pax.web.cfg port.

Example

8181

ucf.bus.hostname

Defines the host name of the Catalyst bus in /registry/topology/physical/node0/catalyst-bus/bus.properties.

Example

localhost

ucf.bus.port

Defines the port of the Catalyst bus in /registry/topology/physical/node0/catalyst-bus/bus.properties.

Example

61616

ucf.bus.http.port

Defines the HTTP port of the Catalyst bus in /registry/topology/physical/node0/catalyst-bus/bus.properties.

Example

61617

ucf.max.archive.query.results

Defines the maximum archive query results.

Example

30

use.catalyst.claims.credentials

Specifies whether to use the Catalyst claims for credentials.

Example

false

org.apache.commons.logging.Log

Defines a factory class for instantiating Loggers for Commons Logging.

Example

org.apache.commons.logging.impl.Log4JLogger

org.apache.commons.logging.LogFactory

Defines a factory class for instantiating Loggers for Commons Logging.

Example

org.apache.commons.logging.impl.Log4jFactory

eem.cache.timeout

This user-added parameter defines the maximum age (in seconds) of the cache that stores user credentials with the associated permissions profile. If set to zero, this CA Process Automation authorization cache is turned off and CA Process Automation sends a request to CA EEM each time user permissions are needed. When this parameter is missing, CA Process Automation uses 30 seconds as the refresh rate for the secondary cache.

Note: See Control the Refresh Rate of Caches of CA EEM Updates for details about the two CA EEM caches.

Example

30

mail.attachment.buffer.size

Lets you download an email with a specified amount of buffer.

K is the unit of measure. For example, if you specify 256, CA Process Automation defines it as 256K.

Example

mail.attachment.buffer.size=256

mail.imap.fetchsize

This property is specific to IMAP protocol and is not introduced for CA Process Automation. This property lets you more quickly download large mail attachments.

Specify this property in bytes.

Example

To specify 800k, multiply 800*1024.

mail.imap.fetchsize=819200

jts.allow.multi.last.rsrc

Specifies the property that Jboss Transaction Service uses. If XA resources are involved in multiple transactions, this property is false.

jsse.enableSNIExtension

Enables or Disables the SNI Host Name Matching.

org.apache.activemq.managementcontext.port

Defines the activeMQ Management Context port.

org.apache.activemq.minheapsize

Defines the activeMQ Min JVM Heap.

org.apache.activemq.tcp.port

Defines the tcp port of the activeMQ.

org.apache.activemq.maxheapsize

Defines the activeMQ Max JVM Heap.