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
...
To create an inventory report, run the following 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 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 10 Elements for Create an inventory report
| Element |
|---|
...
| Description |
|---|
| i3- |
...
| user | See Authenticate to CLI Utility on page 8. |
| i3-encrypted- |
...
| password | See 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 |
| 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.
To update the logger configuration, run the following command on the Main Precise FocalPoint:
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 11 Elements for Clean Logger cache
Element Descriptions
...
| 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:
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 12 Elements for Change GUI server portElement 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 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 | ||||
|---|---|---|---|---|
|
...
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
- 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 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:
...