The command line version of configure supports the use of a defaults file:
configure defaults <filename>
This is useful for large installations of Entuity that require identical setup for multiple ENA servers. Automating the configure process can eliminate the need to interactively run configure (from either the CLI or the UI) on multiple occasions and having to make the same responses each time. Instead, the user can create a defaults file that provides configure with the information required to set up an ENA server quickly and consistently. It also simplifies the process of creating a script to automate the configuration of an ENA installation. Note, this simply automates one part of the Entuity setup process, not the entire process.
The recommended procedure for generating a defaults file is to run configure interactively once, and then use the values from the resulting entuity.cfg file to create a defaults file. This defaults file can be used with configure defaults on other servers, to then create a matching setup.
Please find below a list of properties that you can set during configure using the defaults file. This file contains all possible attributes that can be overridden. Note the following:
- only values that have changed from the default need to be entered into the defaults file.
- only include attributes that need to be set, and with valid (non-empty) values.
- do not set an empty value - this will risk creating a state whereby Entuity will not run.
- the [modules] section is not found in entuity.cfg. It tells configure which optional modules should be enabled, which then modifies other module-specific files.
Configure defaults can also be run without a defaults file, which will result in an Entuity server configured with the most common default options, using the demo license file. This is useful in case you would like to try a test installation, for example.
[]
[]
dbdir=
logdir=
activeuser=
dbportnum=
webportnum=
hostname=
licensefile=
[backup]
[backup]
dir=
[capabilities]
Turn on or off an Entuity capability. 1 is on, 0 is off.
[capabilities]
polling=
flowcollector=
surepathagent=
[Events]
[Events]
requestsListenerPort=
receiverPort=
[flow]
[flow]
port=
managementport=
[JustForTemplates]
This is only applicable if BMC Remedy module is on.
Server IP Address:
[JustForTemplates]
ARServer_Server=
ARServer_MidTier=
ARServer_User=
ARServer_Pass=
ARServer_Auth=
ARServer_Port=
ARServer_Rpc=
ARServer_Ssl=
BEM configuration if required.
[JustForTemplates]
BEMProperties_cellname=
BEMProperties_webServerHostName=
BEMProperties_webServerPortNumber=
BEMProperties_webServerSSL=
BEMProperties_webServiceName=
Entuity database configuration for Atrium.
[JustForTemplates]
AtriumProperties_dataexport.dbServer=
AtriumProperties_dataexport.dbUser=
AtriumProperties_dataexport.dbName=
BMC Atrium Server configuration.
[JustForTemplates]
AtriumProperties_atrium.server=
AtriumProperties_atrium.port=
AtriumProperties_atrium.user=
AtriumProperties_atrium.datasetId=
AtriumProperties_atrium.trustedDataset=
[lcm]
This is only applicable if Configuration Management module is on.
[lcm]
tftpServerIp=
tftpHome=
archivedir=
[modules]
By default, most modules are turned on. Here is a list of modules that are turned off by default and can be turned on during configure.
[modules]
Cisco_IP_SLA=
Cisco_CallManager=
Remedy70_Integration=
QoS_Module=
Atrium_Integration=
Configuration_Management_New=
[server]
Webserver SSL Configuration. 1 is enable, 0 is disable.
[server]
ssl_enabled=
https_redirect_enabled=
ssl_cert_file=
ssl_cacert_file=
ssl_key_file=
[smtp]
[smtp]
servers=
smtpUsername=
emailFrom=
eventSubject=
[ticker]
[ticker]
port=
[tomcat]
[tomcat]
port=
adminport=
Comments
0 comments
Please sign in to leave a comment.