This section includes the following topics:
About auto deployment
To enhance the installation experience a new option has been developed that helps you install servers faster. This option is called "Template Listener" and is set up from the Main Precise FocalPoint. The option consists of two CLI utility commands that prepare the Template Listener for installing new servers and the installation based on the Template Listener. The Template Listener is a set of files that is relevant for a defined type of servers.
The Template Listener needs to be recreated if one of the following cases is applicable:
- The original version of the software on the server is upgraded (e.g. v9.0 to v10.0)
- You have applied an update that include updated packages of psin_ba* or jre_*
Preparing auto deployment
Using the CLI utilities, you can prepare the Template Listener on the Main Precise FocalPoint. This command creates a self extract file that should be extracted on the server that the Precise Listener will be installed on.
To prepare the Template Listener, 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 template-listener-prepare
-bits <bits>
-os "<os_type>"
-cpu-model <model> [-output-file <file>]
[-proxy-alias <node_alias>]
[-parameter server-machine-port-template-listener <port>]
[-parameter server-machine-security-encrypted-password-template-listener <encrypted_password>] [-installation-cd-path <installation_path>]
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action template-listener-prepare
-bits <bits>
-os "<os_type>"
-cpu-model <model> [-output-file <file>]
[-proxy-alias <node_alias>]
[-parameter server-machine-port-template-listener <port>]
[-parameter server-machine-security-encrypted-password-template-listener <encrypted_password>] [-installation-cd-path <installation_path>]
Table 1 Elements of the Prepare command
Element | Description |
---|---|
i3-user | See Authenticate to CLI Utility on page 8. |
i3-encrypted-password | See Authenticate to CLI Utility on page 8. |
action | Always template-listener-prepare Mandatory: Yes |
bits | The OS bits of the server in the template. Values: 32 or 64 Mandatory: Yes |
os | The type of operating system used. Values: See Operating System Type and Flavor on page 176. Mandatory: Yes |
cpu-model | The CPU model. Values: AMD or ITANIUM Mandatory: Only used for Windows or Linux 64 bits |
output-file | The location of the output Values: string Mandatory: No |
proxy-alias | Alias of the node Values: string Mandatory: Yes, only in a federation installation |
parameter server-machine-port-template-listener | The listener port for the Template Listener server Values: string Mandatory: No |
parameter server-machine-security-encrypted-password-template-listener | The password used to encrypt the communication key of the Listener. If this parameter is used, it must also be used in the template-listener-install command for the Template Listener server Values: string Mandatory: No |
installation-cd-path | The path of the installation media. Values: string Mandatory: No |
Installing with the Template Listener
Using the CLI utilities, you can install the new server based on the prepared Template Listener. The initial process is to copy the self extract file to a dedicated folder on the new server and run it. This can be done by including the extracted files as part of the server’s template, or ad-hoc step. If you intend to monitor cluster application servers on the server, verify that you extract the Template Listener to the same folder and drive on every server (so the Precise root folder will be identical). You need to recreate this image in those cases as described at the beginning of this section.
If the main Precise FocalPoint is Windows server and this server is a UNIX server, perform the following step after extracting the self extract file on the new server:
- chmod -R 775 <the folder in the new server with the template files> This command handles the permission for this folder.
To install the Template Listener, run the following command from the root folder of the new server:
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action template-listener-install
[-parameter server-machine-security-clear-password-template-listener=<clear_password>]
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action template-listener-install
[-parameter server-machine-security-clear-password-template-listener=<clear_password>]
Table 2 Elements of the Install command
Element | Description |
---|---|
i3-user | See Authenticate to CLI Utility on page 8. |
i3-encrypted-password | See Authenticate to CLI Utility on page 8. |
action | Always template-listener-install Mandatory: Yes |
parameter server-machine-security-clear-password-template-listener | The password for the template listener written in clear text. Values: string Mandatory: Must be specified when supplied in the template-listener-prepare command |
Additionally settings can be adapted using the template-listener_override.xml
file.
About the template-listener_override.xml parameter file
Template Listener settings can be changed by using the template-listener_override.xml
file that you need to create in the root folder of the new server. This file is an optional file. If it does not exist in the installation root folder, defaults will be used according to the ones in the template. Apply the following parameters that will override the standard settings:
<template-listener-override>
<override>
<parameter name="template-listener-server-machine-name" value="<name>"/>
<parameter name="server-machine-port-template-listener" value="<port>"/>
<parameter name="server-machine-use-communication-relay-template-listener" value="true|false"/>
</override>
<instance>
parameters for instances as described in this guide (optional)
</instance>
</template-listener-override>
The instance tag section can contain instances that you want to install on the server automatically. To specify parameter values which contain the server name (which may be unknown at the time of the template creation) use the word "template-listener". For example: <parameter name="collector-server-machine-name" value="template-listener"/>
.
Table 3 Elements of the Install parameters file
Element | Description |
---|---|
template-listener-server-machine-name | The name of the template-listener server. Values: string Mandatory: No. If not specified the host name is applied. |
server-machine-port-template-listener | The listener port for the template-listener server. Values: string Mandatory: No |
server-machine-use-communication-relay-template-listener | Indicates whether this server should use relay communication. Select this option if the server resides behind a firewall. Firewall must be opened at the time of installation. Only block the connection with the server after the installation is complete. Values: (true/false) Mandatory: No |