Administer > Content utilities > Creating a target mesh configuration file

Creating a target mesh configuration file

Create a target mesh configuration file to simplify the use of DET. A sample default configuration file is installed with DET at the following location:

cbt/cfg/default.properties

The mesh configuration file is a key=value pair text file that contains SA component access information that would otherwise need to be given on the DET command-line. To define the parameters of the DET mesh configuration file, make a copy of this file and save it to a known location.
 

Ensure the security of user names and passwords in the configuration file by encrypting the passwords using the cbt.security.obfuscatePasswords property.

Configuration properties contains all possible DET configuration-related properties. These properties can be either given on the DET command-line or specified in a configuration file.

The default configuration property values listed in Configuration properties assume that you are running DET on an SA mesh running the Command Center core component. (It is for this reason that the.host properties shows a localhost value.) Also, twist.certpaths, ssl.trustcerts, and ssl.keypairs assume paths on an Command Center server.

If a configuration-related property is not specifically mentioned in the mesh Configuration file, the default value shown in the Configuration Properties table below will be used.

Configuration properties

Property Name

Default Value

Description
cbt.security.obfuscatePasswords False

Enables password encryption by setting the cbt.security.obfuscatePasswords property value to "true".

By setting the value to true, the twist.password and spike.password field values will be encrypted and a new field, cbt.security.hash will be automatically added when you run the cbt command.

cbt.numthreads

1

Number of concurrent threads used for export.

For exporting content, you can specify as many threads as you wish.

However, for importing content, DET supports only one thread.

spike.enabled

True

Use Spike for authentication and authorization on all XML-RPC-based servers.

spike.host

way

Spike's host name or IP.

spike.path

wayrpc.py

Spike's base URL path.

spike.password

<no default>

User password for Spike authentication. This is an OCC user's password and is set during the installation of the mesh. Contact your SA Administrator (or the person who installed the mesh) for this information.

spike.port

1018

Spike's listener port.

spike.protocol

https

Spike's listener protocol. This is typically HTTPS.

spike.username

admin

User name for Spike authentication. This is the user who was granted permissions by the
cbtperm tool.

This user name needs to be an admin account that has permissions to create or modify objects. The DET default configuration sets spike.username to account: admin

spin.host

spin

Data Access Engine's host name or IP.

spin.path

spinrpc.py

Data Access Engine's base URL path.

spin.port

1004

Data Access Engine's listener port.

spin.protocol

http

Data Access Engine's listener protocol. HTTP if the DET is on the same server as the SA Command Center and is running a clear text spin in a multi-server mesh or HTTPS for any other configuration.

ssl.keyPairs

/var/opt/opsware/crypto/twist/spog.pkcs8

Comma-separated list of client certificates used to communicate with XML-RPC-based servers.

ssl.trustCerts

/var/opt/opsware/crypto/twist/opsware-ca.crt

Comma-separated list of trust certificate files used to communicate with XML-RPC-based servers.

ssl.useHttpClient

true

Use the HTTP Client library instead of JDK's built-in HTTP client.

 

twist.certPaths

/var/opt/opsware/crypto/twist/opsware-ca.crt

Comma-separated list of trust certificates used to communicate with the Web Services Data Access Engine.

twist.host

localhost

Web Services Data Access Engine's host name or IP.

twist.password

<no default>

Web Services Data Access Engine's password. This password is set during the installation of the mesh. Contact your SA Administrator (or the person who installed the mesh) for this information.

twist.port

1032

Web Services Data Access Engine's listening port.

twist.protocol

https

Web Services Data Access Engine's protocol. This should be http or https.

twist.username

detuser

Web Services Data Access Engine's user name. This needs to be “detuser”. This account is a system account, and the password is set during install of the mesh.

way.host

way

Command Engine's host name or IP.

way.path

wayrpc.py

Command Engine's base URL path.

way.port

1018

Command Engine's listener port.

way.protocol

https

Command Engine's listener protocol. This is typically HTTPS.

word.host

word

Software Repository's host name or IP. As of SA 7.80, the Software Repository is part of the Slice Component bundle.

word.path

wordbot-new.py

Software Repository's base URL path.

word.port

1003

Software Repository's listener port.

word.protocol

https

Software Repository's listener protocol. This is HTTPS.

mail.transport.protocol

smtp

Mail transport protocol used for your mail server.

mail.smtp.host

smtp

Mail server host name.

mail.smtp.port

25

Port number used by your mail server.

mail.from

<currentuser>@<currenthost>

Email address to use for the From field in the notification email.

The following is an example of a target mesh configuration file that contains only essential mesh configuration information.

twist.host=twist.c07.dev.opsware.com
twist.port=1032
twist.protocol=https
twist.username=<detuser>
twist.password=<twist_password>
twist.certPaths=<absolute path to opsware-ca.crt>

spike.username=<OCC_user>
spike.password=<OCC_user_password>
spike.host=way.c07.dev.opsware.com
way.host=way.c07.dev.opsware.com
spin.host=spin.c07.dev.opsware.com
word.host=theword.c07.dev.opsware.com

ssl.keyPairs=<absolute path to spog.pkcs8>
ssl.trustCerts=<absolute path to opsware-ca.crt>

mail.transport.protocol=smtp
mail.smtp.host=mail
mail.smtp.port=44
mail.from=joe_user@yourcompany.com

Send Help Center feedback