A single deployment server process can monitor one or more deployment queues in multiple base databases. You configure the deployment server in DM_ROOT/dfs/deploy_config.dat file. By default, the configuration file is set up by the installer to monitor the default database in the listener configuration file (DM_ROOT/dfs/listener.dat). The configuration parameters in deploy_config.dat are organized in two groups:
Global parameters that apply to all base databases.
Base database-specific parameters.
Parameter |
Description |
Default value |
log_dir |
Specify this parameter if you want to:
|
None, logging is off. |
idle_timeout |
Specifies the timeout after which the deployment server will close unused application server connections. If you set the parameter to 0 unused connections will be kept in the connection pool until the deployment server terminates. |
60 |
Parameter |
Description |
Default value |
database database_[n] |
Specifies the database to be monitored for new deployment jobs. You can specify any number of databases to monitor using the format database_[n] where: n = 1, 2, 3, ... You must specify at least one database otherwise the deployment server will be inactive. |
None |
host host_[n] |
Specifies the application server host and port that is working with the databases that correspond to the parameters database and database_[n]. |
Local hostname |
dmuser dmuser_[n] |
Specifies the deployment queue service user account. This is a registered Dimensions user that is used to read and initiate deployment job processing in databases that correspond to the parameters:
You must register the passwords corresponding to the Dimensions users in DM_ROOT/dfs/registry.dat (use the dmpasswd utility). |
dmsys |
threads threads_[n] |
Specifies the number of threads that will be used to execute deployment jobs in the databases that correspond to the parameters:
|
20 |