Page History
...
| Anchor | ||||
|---|---|---|---|---|
|
...
| 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 |
| Anchor | ||||
|---|---|---|---|---|
|
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.
...