Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following table describes the syntax of the password element.

Table 15- 1 Password element

ElementDescription
password password

Contains the value of the password to be encrypted. To encrypt an empty password, type "".

Info

Any password parameter can be a clear text value. To create a clear text value, replace the name of the parameter from encrypt to clear.

For example, replace:

dba-encrypted-password

to:

dba-clear-password

...

The following table describes the syntax of the license file name element.

Table 15- 2 license file name element

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
action

Always apply-license

Mandatory: Yes

license-fileSpecifies the path to the license file name that needs to be applied.

...

Windows    Infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action support
                    -mode <support_mode>
                    -servers <servers_list>
                    [-proxy-alias <node_alias>]
UNIX           
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action support
                    -mode <support_mode>
                    -servers <servers_list>
                    [-proxy-alias <node_alias>]

Table 15- 3 Elements for Create support file

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
action

Always support

Mandatory: Yes

mode

The type for the support file.

Values:

  • Full - for creating a full support file.
  • Express - for creating an express support file.

Mandatory: Yes

servers

The names of the servers for which you want to create support files. The servers names are separated by a comma. The servers list should contain at least one server name. If the list contains more than one server name, it should be wrapped with double quotes. The following format is used:

"server1, server2, ..., serverN"

Mandatory: Yes

proxy-alias

The proxy alias.

Values: alias of the related node

Mandatory: Only for a federated installation

...

Windows    Infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action update-main-registry
                    -registry-path <registry_path>
UNIX           
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action update-main-registry
                    -registry-path <registry_path>

Table 15- 4 Elements for Update main registry

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
action

Update-main-registry

Mandatory: Yes

registry-path

The registry path that was updated in the proxy should start with /registry.

It should not be a relative, nor an absolute path. The path should be the path to an existing registry file without the .xml suffix, for example /registry/products/infrastructure/thin.

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action clean-infra-db
UNIX           
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action clean-infra-db

Table 15- 5 Elements for Clean Main DB and Infra DB CLI

ElementDescriptions
action

Always clean-infra-db

Mandatory:Yes

i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.


Info

Reusing deleted instance's historical data will not be available once this is used.

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action ldap-sync
UNIX           
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action ldap-sync

Table 15- 6 Elements for LDAP Configuration

ElementDescription
action

Always ldap-sync

Mandatory: Yes

i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.

Anchor
ListApplicationsTiersandinstances
ListApplicationsTiersandinstances
List Applications, Tiers, and instances

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action environments-list
                    [-output-file <output_file>]
UNIX           
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action environments-list
                    [-output-file <output_file>]

Table 15- 7 Elements for List Applications, Tiers, and instances

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
action

Always environments-list

Mandatory: Yes

output-file

Values: path to output file

If output-file argument is omitted, output will be redirected to a new file created in infra/cli/output folder.

Mandatory: No

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action instance-apptier
                    -technology <technology_code>
                    -instance-server-machine-name <server_machine_name>
                    [-proxy-alias <node_alias>]
                    -instance-name <instance_name>
                    -apptier-name <Tier_name>
                    -environment-name <application_name>
                    -type <type>}
                    [-apptier-application <application_code>] [-apptier-frontend {true|false}]
                    [-force {true|false}]
UNIX           
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action instance-apptier
                    -technology <technology_code>
                    -instance-server-machine-name <server_machine_name>
                    [-proxy-alias <node_alias>]
                    -instance-name <instance_name>
                    -apptier-name <Tier_name>
                    -environment-name <application_name>
                    -type <type>
                    [-apptier-application <application_code>] [-apptier-frontend {true|false}]
                    [-force {true|false}]

Table 15- 8 Elements for Associate/Disassociate instance Tier

ElementDescriptions
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
action

Always instance-apptier

Mandatory: Yes

technology

Values: Technology code. For more information, see Technology Codes on page 174.

Mandatory: Yes

instance-server-machine-name

The instance server machine name.

Values: string

Mandatory: Yes

proxy-alias

The proxy alias.

Values: alias of the related node

Mandatory: Only for a federated installation

instance-name

The instance name.

Values: string

Mandatory: Yes

apptier-name

The Tier name.

Values: string

Mandatory: Yes

environment-name

The application name.

Values: string

Mandatory: Yes

type

Values: one of DISSOCIATE,ASSOCIATE use ASSOCIATE to add an instance to a Tier use DISSOCIATE to remove an instance from a Tier.

Mandatory: Yes

apptier-application

Values: Application code is optional and can be specified only for the following technologies: Other – CTX, .Net - ASP,DNT, WEB - WEB, SAP, PST, SBL.

Mandatory: No

apptier-frontend

Indicates whether the Tier is a frontend front-end Tier.

Values: true or false

Mandatory: No

force

Indicates whether this operation should be performed even if it affects several instances.

Values: true or false

Mandatory: Yes if changing the instance Tier when the instance is part of a cluster

...

Info

To copy a Cross-Tier report, you should use the following string for both the "source-apptier" and "destination-apptier" parameter: "Cross-AppTiers".

Table 15- 9 Elements for Attach

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-clear-passwordSee Authenticate to CLI Utility on page 8.
action

Values: fs-copy-foresight-custom-report.

Mandatory: Yes

parametersfile

Values: Mandatory:

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action inventory-report
                    [-output-file <output_file_name>]
UNIX           
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action inventory-report
                    [-output-file <output_file_name>]

Table 15- 10 Elements for Create an inventory report

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
action

Values: Always inventory-report.

Mandatory: Yes

output-file

The file name to save report to.

Values: Path

Mandatory: No

...

Windows    infra\bin\psin_cli.bat
                    -action clean-logger-cache
                    -server <server_name>
                    [-proxy-alias <node_alias>]
UNIX           
./infra/bin/psin_cli.sh
                    -action clean-logger-cache
                    -server <server_name>
                    [-proxy-alias <node_alias>]

Table 15- 11 Elements for Clean Logger cache

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action change-gui-port
                    -port <the_new_port>
                    [-shutdown-port <the_new_shutdown_port>] [-url <the_gui_server_url>]
UNIX           
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action change-gui-port
                    -port <the_new_port>
                    [-shutdown-port <the_new_shutdown_port>] [-url <the_gui_server_url>]

Table 15- 12 Elements for Change GUI server port

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-clear-passwordSee Authenticate to CLI Utility on page 8.
action

Always change-gui-port.

Mandatory: Yes

port

The new port used for GUI server.

Mandatory: Yes

shutdown-port

Local port used to control the GUI server.

Mandatory: No

url

URL used to access the GUI server. This can also be used in case you have changed GUI server to use SSL, and you want to update Precise of this.

Mandatory: No

...

  • Only Web (WebSphere and WebLogic only) and J2EE instances are supported.
  • All instances’ servers must contain the same Precise version as the Main Precise FocalPoint. If upgrading from version Precise 8.7, complete the upgrade related action items.
  • All instance’s servers must have the same path to the Precise installation folder.
  • All instances must be of the same type (and for Web also of the same application) and must be standalone instances (you cannot join instances which are already installed as a cluster).
  • Before a Web instance can be joined, it must run at least once.

...

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 for Join instances to cluster

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-clear-passwordSee 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

...

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 to configure SmartLink

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee 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

...

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 to configure the downtime

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee 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  For more information, 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

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action dashboard-ignore-handle
                    -dashboard-key <dashboard_key>
                    -type {add|remove}
                    {-expire-in-days<expire_in_days>}
UNIX    
./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action dashboard-ignore-handle
                    -dashboard-key <dashboard_key>
                    -type {add|remove}
                    {-expire-in-days<expire_in_days>}

Table 15- 16 Elements to configure the Dashboard acknowledgement

ElementDescription
i3-userSee Authenticate to CLI Utility on page 8.
i3-encrypted-passwordSee Authenticate to CLI Utility on page 8.
action

Always dashboard-ignore-handle.

Mandatory: Yes

dashboard-key

The Unique Key of the Dashboard component.

Values: String

Info

Use quotes to specify a key that includes spaces.

 

Mandatory: Yes.

type

Add or remove the Dashboard acknowledgement.

Values: add, remove

Mandatory: Yes.

expire-in-days

Relevant for adding ignore. It specifies the amount of days that the ignore is relevant for. If not specified, the acknowledge is enabled for good.

Values: Integer

Mandatory: No.

...