Versions Compared

Key

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

...

The encrypted password is displayed in the standard output. The Encrypt command uses the following format:

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.

Table 15-1    Password 1 Password element

Element

...

Description
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

Anchor
ApplyLicensecommand
ApplyLicensecommand
Apply License command

...

To apply the license, run the following command on the main Precise FocalPoint server:

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.

Table 15-2    license 2 license file name element

Element

...

Description
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.

Anchor
#ChangeaninstalledPreciseListenerport
#ChangeaninstalledPreciseListenerport
Change an installed Precise Listener port

The Listener Port Change command enables you to change the port number of an installed Precise Listener.

Info

...

This command must be executed on the server itself. You are not allowed to change the Precise FocalPoint Listener port number.

To change listener port, run the following command:

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
Createsupportfilecommand
Createsupportfilecommand
Create support file command

The Create a support file command enables you to generate a support file for Precise. The created support file is saved in the <precise<precise_root>root>/support folder on the main Precise FocalPoint.

To create a support file, 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 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 3 Elements for Create support file

Element

...

Description
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

Anchor
Updatemainregistrycommand
Updatemainregistrycommand
Update main registry command

...

The update-main-registry command uses the following format:

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 4 Elements for Update main registryElement    Description

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.

Anchor
CleanMainDBandInfraDBCLIcommand
CleanMainDBandInfraDBCLIcommand
Clean Main DB and Infra DB CLI command

...

Run the following command from the Main Precise FocalPoint root folder:

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 5 Elements for Clean Main DB and Infra DB CLI

Element    Descriptions

...

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.

Anchor
LDAPSynccommand
LDAPSynccommand
LDAP Sync command

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.

If you have changed LDAP configuration (add/removed users and/or groups) it will be applied at the next 00:08. In case you have changed the LDAP configuration and you don't want to wait, you can force the LDAP sync. Run the LDAP Sync command on the main Precise FocalPoint from the <precise<precise_root>root>:

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 6 Elements for LDAP Configuration

Element    Descriptions

...

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

...