Versions Compared

Old Version 56

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 57

changes.mady.by.user Nadja Pollard

Saved on

Key

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

...

The Precise Framework can be installed directly from the Precise v9.6 download onto the Precise FocalPoint server. You can use the Precise CLI utility to install the following Framework components:

...

If installation is successful, a message appears "Framework install setup process done.".

Info

For Windows Server which has the User Account Control enabled, you must run this command using Administrator permissions: Click Start Menu, right-click Command Prompt, click "Run as administrator", click Continue button, to approve the operation. Run the command specified above.

...

The parameters file is an XML file containing a list of parameters for a Precise framework installation.

Table 2- 1 Elements of the Precise framework parameter file

...

The following table lists the additional parameters needed for a PMDB installation using an Oracle database.

Table 2- 2 Additional parameter file elements for the PMDB on an Oracle database

...

The following table lists the additional parameters needed for a PMDB installation using an MS-SQL Server database.

Table 2- 3 Additional parameter file elements for the PMDB on an MS-SQL Server database

...

The following table lists the additional parameters needed for server installation, wherever FocalPoints are installed. These are required only if when installing the Framework FocalPoint on servers other than the Precise FocalPoint. In such cases specify the parameters below for each server and replace server-name (italic) with the real server name.

Table 2- 4 Additional parameter file elements for server installation

...

<parameters>
     <parameter name="..." value="..."/> ...
</parameters>

Table 2- 5 Parameter file elements for a Precise FocalPoint installation

...

  1. 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 list-required-files-for-new-server
                     -bits <new server bits (32/64)>
                     -os <os _type>
    UNIX        ./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                   {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                   -action list-required-files-for-new-server
                   -bits <new server bits (32/64)>
                   -os <os_type>
    The CLI creates an XML file containing the list of required installation packages for the server.
    Table 2-6 Server Installation

    ElementDescription
    i3-userSee Authenticate to CLI utility on page 8Utility.
    i3-encrypted-passwordSee Authenticate to CLI utility on page 8Utility.
    actionAlways list-required-files-for-new-server.
    Mandatory    : Yes
    bitsThe OS bits in the new added server.
    Values:32 or 64
    Mandatory: Yes
    osThe added server OS.
    Values: See Operating System Type and Flavor on page 176.
    Mandatory: Yes


  2. On the new server create the installation folder and create new sub folder under it: distribution.
  3. Copy the files specified the XML file created in Step 1 to the new server in the
         <precise_root>/distribution
  4. Login to the server using the Precise user
         CD <precise_root>
  5. Run the following command:
    Windows    distribution\psin_ba_WIN.exe -s
    UNIX          ./distribution/psin_ba_<os_type> -s
    For more information, see Operating System Type and Flavor on page 176.
    Note the -s argument
  6. For each of the other files you've copied, run the following command:
    Windows    infra\bin\psin_file_new.exe -manual -extract distribution\<the_file_name> -event install
    UNIX    ./infra/bin/psin_file_new -manual -extract distribution/<the_file_name> -event install
  7. Create an XML file containing the relevant installation parameters. Place the file in <precise_root> folder on the target server. You can also set up this file in advance.
    By default, installing an non-secured local server using the CLI is not enabled. To enable a non-secured CLI server installation, set the Precise registry parameter:
         registry\products\infrastructure\setup\settings\enable-local-server-cli to true, and restart Precise FocalPoint.
  8. Run the following command to execute the CLI utility installation script from the <precise_root> folder on the target server:
    Windows    infra\bin\psin_cli.bat
                       -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action setup-server -parametersfile <server_installation_parameters_file_name>
    UNIX         ./infra/bin/psin_cli.sh
                     -i3-user <user_name>
                     {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action setup-server
                    -parametersfile <server_installation_parameters_file_name>
Info

For Windows Server 2008 (Windows Longhorn) , you must run this command using Administrator permissions: Click Start Menu, right-click Command Prompt, click Run as administrator, click Continue, to approve the operation. Run the command specified above.

Table 2- 7 CLI utility installation script

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

always setup-server

Mandatory: Yes

parametersfile

path to parameters file

Mandatory: Yes

...

The following table describes the elements of the parameter file.

Table 2- 8 Elements of the servers parameter file for product Collectors

...

  1. Prepare server parameters file. For more information, see Table 2-8 on page 22.
    Mandatory parameters for this installation are:
         server-machine-secured-protocol-server-name true

  2. On the main Precise FocalPoint server, run the following command from the <precise_root> folder:
    Windows    infra\bin\psin_cli.bat
                       -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action secure-crypt-keys
                      -ba-secure-clear-password <security_password>
    UNIX          ./infra/bin/psin_cli.sh
                      -i3-user <user_name>
                     {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                     -action secure-crypt-keys
                     -ba-secure-clear-password <security_password>
    The command will generate a key file on the Precise FocalPoint server, under the products/i3fp/security/keys/ folder.
    Table 2- 9 Local mode

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

    always secure-crypt-keys

    Mandatory: Yes

    ba-secure-encrypted-password

    Password used to encrypt the communication key, up to 8 characters.

    Mandatory: Yes

    Alternatively the i3clear-password can be used, allowing you to specify a clear password instead of an encrypted string.


  3. Copy and extract the server packages on the target server as specified in Installing Servers.
  4. Copy key file from: products/i3fp/security/keys/keys/xml on the main Precise FocalPoint to the target server, to the ./infra folder.
  5. On the target server, run the following command from the <precise_root > folder:
    Windows    infra\bin\psin_infra.exe
                       -manual-extricate-crypt <security_password>
    UNIX          ./infra/bin/psin_infra
                      -manual-extricate-crypt <security_password>
    The command will extricate the security keys on the target server.
  6. On the target server, run the following command from the <precise_root> folder. For more information, see Installing Servers.
    Windows    infra\bin\psin_cli.bat
                        -i3-user <user_name>
                        {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                        -action setup-server
                        -parametersfile <server_parameters_file_path>
    UNIX           ./infra/bin/psin_cli.sh
                       -i3-user <user_name>
                       {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action setup-server
                      -parametersfile <server_parameters_file_path>

...

For parameter details, see Table 2- 10 on page 28.

Anchor
#InstallingaTierwiththePreciseCLIutility
#InstallingaTierwiththePreciseCLIutility
Installing a Tier with the Precise CLI utility

...

The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.

Table 2- 10 Elements of the Precise for Oracle parameter file

...

The following table describes the updated elements of the parameter file.

Table 2- 11 Elements of the Precise for Storage parameter file

...

The following table describes the updated elements of the parameter file.

Table 2- 12 Elements of the Precise for J2EE parameter file

...

<parameters>
     <parameter name="setup-process" value="apptier-WW"/>
     <parameter name="collector-server-machine-name" value="server1"/>
     <parameter name="web-type" value="IIS"/>
     <parameter name="instance-identifier" value="WEB1" />
     <parameter name="is-cluster" value="false" />
     <parameter name="web-real-name" value="Default Web Site" />
     <parameter name="web-server-version" value="6.x" />
     <parameter name="web-application-used" value="Web" />
     <parameter name="install-filters" value="true" />
     <parameter name="install-instrumentation" value="true" />
     <parameter name="install-dynamic-instrumentation" value="true" />
     <parameter name="web-collect-extended-information" value="false" />
     <parameter name="web-ports" value="port=80;ip=server1;ssl=true"/>
     <parameter name="web-iis-instance-number" value="1"/>
     <parameter name="installation-cd-path" value="d:\"/>
</parameters>

Table 2- 13 Elements of the Precise for Web parameter file

...

<root>
     <parameter name="setup-process" value="apptier-DN"/>
     <parameter name="collector-server-machine-name" value="serverwin1004"/>
     <parameter name="instance-name" value="MyInstance"/>
     <parameter name="type" value="web" />
     <parameter name="application-name" value="IIS5" />
     <parameter name="process-name" value="aspnet_wp.exe" />
     <parameter name="installation-cd-path" value="d:\"/>
</root>

Table 2- 14 Elements of the Precise for Microsoft .NET parameter file

...

The following table describes the updated elements of the parameter file. Field names marked with an asterisk (*) can be updated after installation.

Table 2- 15 Elements of the Precise for SQL Server parameter file

...

<parameters>
     <parameter name="setup-process" value="apptier-SP"/>
     <parameter name="setup-mode" value="install"/>
     <parameter name="instance-name" value="H47_TEST2" />
     <parameter name="sap-system" value="H47" />
     <parameter name="default-app-server" value="poolhp3" />
     <parameter name="app-server-exist" value="true" />
     <parameter name="app-rout-string-exist" value="false" />
     <parameter name="app-rout-string" value="" />
     <parameter name="db-system-number" value="00" />
     <parameter name="sap-user" value="adm" />
     <parameter name="sap-clear-password" value="precise" />
     <parameter name="client-id" value="000" />
     <parameter name="environment-name" value="Default" />
     <parameter name="app-servers" value="host=poolhp3;routing-str=;port=00;name=poolhp3_H47_00" />
     <parameter name="clients" value="lang=E;number=000||lang=E;number=001||lang=E;number=066||lang=E;number=100" />
     <parameter name="installation-cd-path" value="d:\"/>
</parameters>

Table 2- 16 Elements of the Precise for SAP parameter file

...

The following table describes the updated elements of the parameter file. Field names marked with an asterisk (*) can be updated after installation.

Table 2- 17 Elements of the Precise for Sybase parameter file

...

The following table describes the updated elements of the parameter file. Field names marked with an asterisk (*) can be updated after installation.

Table 2- 18 Elements of the Sybase Replication Server parameter file

...

The following table describes the elements of the Precise for DB2 parameter file. Element names marked with an asterisk (*) can be updated after installation.

Table 2- 19 Elements of the Precise for DB2 parameter file

...

The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) in this table can be updated after installation.

Table 2- 20 Elements of the Tuxedo Collector parameter file

...

The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*), in this table, can be updated after installation.

Table 2- 21 Elements of the WebSphere MQ instance parameter file

...

The following table describes the elements of the parameter file. Element names marked with an asterisk (*), in this table, can be updated after installation.

Table 2- 22 Elements of the Oracle Applications Tier Collector parameter file

...

The following table describes the elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.

Table 2- 23 Elements of the Other Tier Collectors parameter file

...

The following table describes the updated elements of the parameter file.

Table 2- 24 Elements of the OS Collectors parameter file

...

The following table describes the updated elements of the parameter file. Element names marked with an asterisk (*) can be updated after installation.

Table 2- 25 Elements of the Interpoint for Siebel parameter file

...

The parameters file is an XML file containing a list of parameters for a Precise for vCenter Server installation.

Table 2- 26 Elements of the Precise for vCenter Server parameter file

...

The output will be done to an XML parameters file which is created by the CLI.

Table 2- 27 Elements of the Extricate command parameters file

...

  1. From the <precise_root> folder on the main Precise FocalPoint, run the following query command to retrieve the instance ID:
    Windows    infra\bin\psin_cli.bat
                        -i3-user <user_name>
                        {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                        -action get-instance-id
                        -technology <technology_code>
                       -instance <instance_name>
                       -server <server_name>
    UNIX          ./infra/bin/psin_cli.sh
                      -i3-user <user_name>
                      {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                      -action get-instance-id
                      -technology <technology_code>
                      -instance <instance_name>
                      -server <server_name>
    Table 2- 28 Elements of the Retrieve instance ID query command

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

    always get-instance-id

    Mandatory: Yes

    technology

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

    Mandatory: Yes

    instance

    The instance name.

    Values: String

    Mandatory: Yes

    server

    The instance server name.

    Values: String

    Mandatory: Yes


  2. If there are several instances with the same name, the CLI utility will provide the latest instance ID in the output. A non-deleted instance will appear as installed.
  3. Create CLI parameters file to install the new instance. Add the recovered-instance-id parameter to the parameters file with the instance ID that was detected and run the CLI to install the new instance. For more information, see Installing a Tier with the Precise CLI utility.

...