Provisioning

com.webmethods.platform.management.client.provision.jobs.max.fix.provisioning.job.retries

Configure for OSGI-CCE. The maximum number of times that Command Central retries fix installation.

Default: 1

com.webmethods.platform.management.client.provision.artifacts.job.timeout.minutes

Configure for OSGI-CCE. The time interval in minutes Command Central waits for a provisioning products job to execute, before cancelling the job.

Default: 180

com.webmethods.platform.management.client.provision.bootstrap.node.timeout.minutes

Configure for OSGI-CCE. The time interval in minutes Command Central waits for the bootstrap node jobs to get executed, before cancelling the job.

Default: 120

com.webmethods.platform.management.client.provision.bootstrap.platform.manager.timeout.minutes

Configure for OSGI-CCE. The time interval in minutes Command Central waits for a Platform Manager bootstrap job to get executed before cancelling the job.

Default: 120

com.webmethods.platform.management.client.remote.requests.connect.timeout

Configure for OSGI-CCE. The time interval in milliseconds Command Central waits to establish a connection to Platform Manager before terminating the connection attempt.

Default: 900

com.webmethods.platform.management.client.remote.requests.sync.read.timeout

Configure for OSGI-CCE. The time interval in milliseconds in which Command Central synchronizes data with Platform Manager.

Default: 900

com.webmethods.platform.management.client.remoteaccess.keepaliveperiodsec

The time interval in seconds between keep-alive messages from the client to the remote SSH server. Use this property to keep the SSH connection open when Command Central runs long-running operations on a remote machine and the SSH server is configured to terminate idle sessions. To send keep-alive messages, set a positive integer greater than zero.

Default: 0 - Indicates not to send keep-alive messages.

You must set a keep-alive interval that is smaller than the terminate idle sessions interval, configured on the remote SSH server. For example, if the SSH server terminates idle sessions after 180 seconds, set the keep-alive property to 150 seconds.

com.webmethods.platform.management.client.template.composite.apply.job.timeout.minutes

Configure for OSGI-CCE. The time interval in minutes Command Central waits for a composite template apply job to get executed before cancelling the job.

Default: 120

com.webmethods.platform.management.client.template.composite.node.check.online.poll.timeout.miliseconds

Configure for OSGI-CCE. The time interval in milliseconds in which to update the status of the Platform Manager nodes.

Default: 2400

com.webmethods.platform.management.client.template.composite.node.check.status.poll.request.enable

When bootstrapping Platform Manager installations using a composite template, the property specifies whether Command Central must check the status of a Platform Manager. This check is additional to the status checks performed by the Command Central monitoring service. You must enable this property only if you experience issues detecting the status of the bootstrapped nodes. By default, the additional check is disabled. To enable the status check, set to:

com.webmethods.platform.management.client.template.composite.node.check.status.
poll.request.enable=true

Default: false

com.webmethods.platform.management.template.configuration.type.retry

Specifies which configuration instances of the configuration types to retrieve when applying the template, in addition to the default COMMON-SYSPROPS and COMMON-MEMORY configuration instances. The value is a comma-separated list with the IDs of the configuration instances that you must specify on one line. Do not specify the same property with a different value on separate lines.

com.webmethods.platform.management.client.template.parallel.exec.nodes

When applying a composite template on installations located on the same physical machine, Command Central applies the inline templates in sequence. This system property enables applying the inline templates in parallel and supports the following values:

Comma-separated list of node aliases - applies the inline templates in parallel on the listed nodes, for example:
```
com.webmethods.platform.management.client.template.parallel.exec.nodes=nodeAlias1,nodeAlias2
```
In this example, Command Central applies the inline templates on nodeAlias1 and nodeAlias2 in parallel.
ALL - applies the inline templates in parallel on all nodes.

You must specify the values for this property on one line. Do not specify the same property with a different value on separate lines.

If you do not set the com.webmethods.platform.management.client.template.parallel.exec.nodes property, Command Central applies the inline templates in sequence.

com.webmethods.platform.management.client.template.composite.restart.online.status.poll.timeout.miliseconds

Configure for OSGI-CCE. The time interval in milliseconds in which to update the status of the run-time components.

Default: 2400

com.webmethods.platform.management.client.template.composite.skip.restart.runtimes

Indicates whether to bypass the restart of the run-time components at the end of the composite template application. If the property is set to false, Command Central restarts the run-time components at the end of the composite template application. If the property is set to true, Command Central does not re-start the run-time components.

Default: false

com.webmethods.platform.management.client.template.composite.skip.restart.for

Indicates whether to bypass the restart of specific run-time components at the end of the composite template application. The value is a comma-separated list with the IDs of the run-time components that you must specify on one line. Do not specify the same property with a different value on separate lines. For example, to skip the restart of the run-time component with IDs "TES-default", "IS-instance1", "IS-instance2":

com.webmethods.platform.management.client.template.composite.skip.restart.for=TES-default,
IS-instance1,IS-instance2

Restart Command Central after setting the property, and then apply the template.

com.webmethods.platform.management.job.thread.pool.size

Configure for OSGI-CCE. The number of jobs that can run in parallel. The number of jobs corresponds to the number of nodes that Command Central processes in parallel. For example, if the thread pool size is set to 10 and you have 100 nodes in the list, the nodes are processed 10 at a time in parallel, in the order in which they are listed.

Default: 40

com.webmethods.platform.management.job.timeout

Configure for OSGI-CCE and OSGI-SPM. The time interval in milliseconds Command Central waits for a generic job to get executed before cancelling the job.

Default: 4800

com.webmethods.platform.management.mirror.job.timeout

Configure for OSGI-CCE and OSGI-SPM. The time interval in minutes Command Central waits for a mirror repository job to get executed, before cancelling the job.

Default: 720

com.webmethods.plm.sum.cc.override.resolve.validation

Configure for OSGI-SPM. Specifies whether to validate unresolved fix dependencies when applying a product fix. By default, Command Central validates unresolved fix dependencies. To disable this validation:

com.webmethods.plm.sum.cc.override.resolve.validation=false

Default: true