Page History
...
- Encrypt command
- Apply License command
- Change an installed Precise Listener port
- Create support file command
- Update main registry command
- Clean Main DB and Infra DB CLI command
- LDAP Sync command
- List Applications, Tiers, and instances
- Associate/Disassociate instance Tier
- Copy Report Manager Reports
- Create inventory report
- Clean Logger cache
- Change GUI server port
- Join instances to cluster
- Configure SmartLink for an application
- Downtime command
- AdminPoint Dashboard acknowledgement
| Anchor | ||||
|---|---|---|---|---|
|
The Encrypt command encrypts passwords that are used as parameters. The encryption is based on the encryption type that is currently configured on the site.
...
Windows infra\bin\psin_cli.bat
-action encrypt
-password <password>
UNIX ./infra/bin/psin_cli.sh
-action encrypt
-password <password>
password element
The following table describes the syntax of the password element.
...
| Element | Description | ||
|---|---|---|---|
| password password | Contains the value of the password to be encrypted. To encrypt an empty password, type "".
For example, replace: dba-encrypted-password to: dba-clear-password |
| Anchor | ||||
|---|---|---|---|---|
|
The Apply License CLI applies a new license to Precise.
...
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action apply-license
-license-file <license_file_name>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action apply-license
-license-file <license_file_name>
License file name element
The following table describes the syntax of the license file name element.
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| action | Always apply-license Mandatory: Yes |
| license-file | Specifies the path to the license file name that needs to be applied. |
| Anchor | ||||
|---|---|---|---|---|
|
The Listener Port Change command enables you to change the port number of an installed Precise Listener.
...
Windows Infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action port-change
-port <port_number>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action port-change
-port <port_number>
| Anchor | ||||
|---|---|---|---|---|
|
The Create a support file command enables you to generate a support file for Precise. The created support file is saved in the <precise_root>/support folder on the main Precise FocalPoint.
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| action | Always support Mandatory: Yes |
| mode | The type for the support file. Values:
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 |
| Anchor | ||||
|---|---|---|---|---|
|
The update main registry command updates the main registry with the proxy registry. The command should run on the proxy that the change was made on, and will update the main registry.
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| 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. |
| Anchor | ||||
|---|---|---|---|---|
|
Precise maintains logically deleted entities for its operation. This allows, for example, reusing deleted instance's historical data for new instance installation. However as the Precise system ages, performance might be affected. To improve performance, clean the deleted entities using the following CLI.
...
| Info |
|---|
Reusing deleted instance's historical data will not be available once this is used. |
| Anchor | ||||
|---|---|---|---|---|
|
Precise can use LDAP for its roles & users management. For more details about LDAP and Precise integration, see the Precise Administration Guide and/or the Precise Installation Guide. Precise automatically runs LDAP sync once a day at 00:08.
...
| Element | Description |
|---|---|
| action | Always ldap-sync Mandatory: Yes |
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| Anchor | ||||
|---|---|---|---|---|
|
Using CLI you can list the entire Precise applications, Tiers and instances structure in a XML formatted file. To list, run the following command on the main Precise FocalPoint from the <precise_root>:
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| 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 |
| Anchor | ||||
|---|---|---|---|---|
|
This command associates or disassociates instances to the Tier. Please note the following:
...
| Element | Descriptions |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| action | Always instance-apptier Mandatory: Yes |
| technology | Values: Technology code. For more information, see Technology Codes. 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 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 |
| Anchor | ||||
|---|---|---|---|---|
|
CLI enables you to copy reports from one Tier to another. This can also be done between different Nodes, meaning between 2 applications on the same Precise federated installations that each belongs to different Node. To copy Report Manager reports from one Tier to another run the following command from the main Precise FocalPoint root folder:
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-clear-password | See Authenticate to CLI Utility. |
| action | Values: fs-copy-foresight-custom-report. Mandatory: Yes |
parametersfile | Values: Mandatory: |
| Anchor | ||||
|---|---|---|---|---|
|
The create inventory report enables you to create an Excel file containing information regarding your installation servers, nodes, PW, and instances.
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| action | Values: Always inventory-report. Mandatory: Yes |
| output-file | The file name to save report to. Values: Path Mandatory: No |
| Anchor | ||||
|---|---|---|---|---|
|
Each agent that uses the logger has a cached configuration for the logger. When you want to update the logger configuration, you need to remove the logger cache, so that the related agent will reload the new updated configuration.
...
| Element | Description |
|---|---|
| action | Always clean-logger-cache. Mandatory: Yes |
| server | The server name where the related agent is installed. Mandatory: Yes |
| proxy-alias | The proxy alias. Values: alias of the related node Mandatory: Only for a federated installation |
| Anchor | ||||
|---|---|---|---|---|
|
You can change the GUI server port using CLI. To change the GUI server port run the following command on the Precise FocalPoint whose GUI server port you want to change:
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-clear-password | See Authenticate to CLI Utility. |
| 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 |
| Anchor | ||||
|---|---|---|---|---|
|
Web and J2EE technologies support cluster installation. When installing an instance, you can choose whether to install the instance as a standalone instance or as a cluster.
If you have installed instances as standalone instances and they should have been installed as a cluster, you can uninstall the instances and reinstall one instance as a cluster instead. This, however does not keep historical data for the newly installed cluster’s instances. If you want to keep the historical data related to the instances, you can use the join instances to cluster CLI utility command.
Prerequisites for using the Join instances to cluster command
The following list describes the prerequisites for using the Join instances to cluster command:
- 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 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.
The Join instances to cluster command
To join the instances, run the following CLI utility command from the Main Precise FocalPoint root folder:
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-clear-password | See Authenticate to CLI Utility. |
| 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. 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:
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| 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:
...
| Element | Description |
|---|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| 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. For more information, see Technology Codes. 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 | ||||
|---|---|---|---|---|
|
The AdminPoint Dashboard provides information regarding health of the Precise installation. The information is displayed in categories for each category per components. If you want to ignore a report for a specific component, for instance because the problem is currently being handled, you will have to add the Unique Key column to the Dashboard and use this relevant key in a CLI utillities command.
...