Page History
...
To join the instances, run the following CLI utility command from the Main Precise FocalPoint root folder:
Windows infra\bin\psin_cli.bat
-i3-user <user
...
_
...
name>
-i3-clear-password <clear_password>
-action join-instances-to-cluster
[-proxy-
...
alias<proxy alias>]
-instances-ids "<instances_ids>"
-cluster-name
...
<cluster_
...
name>
-[template <template
...
>]
[[-installation-cd-path
...
<cd_
...
path>]
...
UNIX infra/bin/psin_cli.sh
-i3-user <user
...
_
...
name>
-i3-clear-password <clear_password>
-action join-instances-to-cluster
[-proxy-
...
alias<proxy alias>]
-instances-ids "
...
<instances_
...
ids>"
-cluster-name
...
<cluster_
...
name> [template <template
...
>]
[[-installation-cd-path
...
<cd_
...
path>]
Table 15-13 Elements 13 Elements for Join instances to clusterElement Description
Element | Description |
---|---|
i3- |
...
user | See Authenticate to CLI Utility on page 8. |
i3-clear- |
...
password | See Authenticate to CLI Utility on page 8. |
...
action | Always join-instances-to-cluster Mandatory: Yes |
proxy- |
...
alias | Alias of the instance’s related node. Mandatory: Yes, only in a federation installation. |
instances- |
...
ids | Comma separated list of IDs related to the instances that need to be joined. To get the IDs related to the instances, use the get-instance-id CLI utility command. See Installing a new instance while keeping historical data from an old instance on page 82. Mandatory: Yes |
cluster- |
...
name | The name of the cluster to install. Mandatory: Yes |
template |
...
The ID of the instance that will be used as the template to install the new cluster. If omitted, the first instance in -instances-ids is used as the |
...
template instance. Mandatory: No |
installation-cd- |
...
path | Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to. Values: String Mandatory: Yes |
Anchor | ||||
---|---|---|---|---|
|
SmartLink is set by default for an application containing Web/J2EE/.NET Tiers. If you want to disable SmartLink for the application, run the following CLI utilities command on the main Precise FocalPoint:
Windows infra\bin\psin_cli.bat
-i3-user
...
<user_
...
name>
{-i3-encrypted-password
...
<encrypted_
...
password> | -i3-clear-password <clear_password>}
-action smartlink-config
-environment-name
...
<application_
...
name>
-enable <enable_smartlink>
UNIX ./infra/bin/psin_cli.sh
-i3-user
...
<user_
...
name>
{-i3-encrypted-password
...
<encrypted_
...
password> | -i3-clear-password <clear_password>}
-action smartlink-config
-environment-name
...
<application_
...
name>
-enable <enable_smartlink>
Table 15-14 Elements 14 Elements to configure SmartLinkElement Description
Element | Description |
---|---|
i3- |
...
user | See Authenticate to CLI Utility on page 8. |
i3-encrypted- |
...
password | See Authenticate to CLI Utility on page 8. |
...
action | Always smartlink-config Mandatory: Yes |
environment- |
...
name | The name of the application on which SmartLink should be enabled/disabled. Mandatory: Yes |
...
enable | Indicates whether SmartLink |
...
should be enabled or disabled for the application. Values: true, false Mandatory: Yes |
Anchor | ||||
---|---|---|---|---|
|
The downtime command defines new downtime rules for an application, server, or specific Instance. Define the downtime using CLI utilities by running the following command:
Windows infra\bin\psin_cli.bat
-i3-user <user
...
_
...
name>
{-i3-encrypted-password
...
<encrypted_
...
password> | -i3-clear-password <clear_password>}
-action downtime
{-environment-name
...
<application_
...
name> | -server <server
...
_
...
name> | -instance-name
...
<instance_
...
name>
-technology <technology
...
_
...
code> -server <server
...
_
...
name>}
-proxy-alias
...
<proxy_alias_
...
name>
-start date
...
<start_
...
date>
-start time
...
<start_
...
time>
-end date
...
<end_
...
date>
-end time
...
<end_
...
time>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user
...
_
...
name>
{-i3-encrypted-password
...
<encrypted_
...
password> | -i3-clear-password <clear_password>}
-action downtime
{-environment-name
...
<application_
...
name> | -server <server
...
_
...
name> | -instance-name
...
<instance_
...
name>
-technology
...
<technology_
...
code> -server <server
...
_
...
name>}
-proxy-alias
...
<proxy_alias_
...
name>
-start date
...
<start_
...
date>
-start time
...
<start_
...
time>
-end date
...
<end_
...
date>
-end time
...
<end_
...
time>
Table 15-15 Elements 15 Elements to configure the downtimeElement Description
Element | Description |
---|---|
i3- |
...
user | See Authenticate to CLI Utility on page 8. |
i3-encrypted- |
...
password | See Authenticate to CLI Utility on page 8. |
action |
...
Always downtime. Mandatory: Yes |
environment- |
...
name | The name of the application on which the downtime needs to be defined. The downtime rules will be applied to all instances on this application Values: String Mandatory: Yes, unless the downtime rule is defined per server or an instance. |
...
server | The name of the server on which the downtime needs to be defined. The downtime rules will be applied to all instances on this server. Values: String Mandatory: Yes, unless the downtime rule is defined per application. |
...
technology | The related technology code. Values: String. See Technology Codes on page 174. Mandatory: Yes, when the downtime rule is applied to a specific instance. |
proxy- |
...
alias | The proxy alias related to the downtime definition. Values: String Mandatory: No, unless there is more than one proxy. |
start- |
...
date | The start date of the downtime rule. Values: Date (format: YYYY-MM-DD) Mandatory: Yes |
start- |
...
time | The start time of the downtime rule. Values: Time (format: HH24:MI:SS) Mandatory: Yes |
end- |
...
date | The end date of the downtime rule. Values: Date (format: YYYY-MM-DD) Mandatory: Yes |
end- |
...
time | The end time of the downtime rule. Values: Time (format: HH24:MI:SS) Mandatory: Yes |
Anchor | ||||
---|---|---|---|---|
|
...