18.2.3 tierlb.properties (tier-side load balancer connection configuration property file)

Organization of this subsection

(1) Format
(2) File location
(3) Functionality
(4) Keys that can be specified

(1) Format

J2SE property file format

To Page Top

(2) File location

In Windows

definition-directory\tier-specific-definition-directory\vmi\
In UNIX

definition-directory/tier-specific-definition-directory/vmi/

Copy and use the following template file:

In Windows

Cosminexus-installation-directory\manager\vmi\templates\tierlb.properties
In UNIX

/opt/Cosminexus/manager/vmi/templates/tierlb.properties

To Page Top

(3) Functionality

This file configures connection information necessary to access the load balancer within a tier.

To Page Top

(4) Keys that can be specified

The keys that can be specified are shown below. The Default value column gives the value assumed if the key is omitted. VR indicates the version of the application server on which the keys are introduced or changed.

Key name	Description	Specifiable value	Default value	VR
`lb.type`	Specify the load balancer type.	The following values can be specified: `BIG-IPv9` `BIG-IPv10.1` `BIG-IPv10.2` `BIG-IPv11` `ACOS`	None	08-53
`lb.host`	Specify the management IP address of the load balancer to be connected.	IPv4 dot notation	None	08-53
`lb.protocol`	Specify the method of connecting to the load balancer. `API`: Uses the API to connect to the load balancer	The following value can be specified: `API`	None	08-53
`lb.port`	Specify the port number to be used by the load balancer.	The following values can be specified: API `1`-`65534`	API: `443`	08-53
`lb.user`	Specify the user name used to connect to the load balancer.	Any character string can be used.	None	08-53
`lb.password`	Specify the user password used to connect to the load balancer.	Any character string can be used.	Null	08-53
`lb.persistence.cookie-insert.templatename`	Specify the cookie persistence template name created on the load balancer. The specified key becomes effective if the following conditions are met: `lb.type=ACOS` and `lb.protocol=API` are specified in `LB-connection-information-distinguished-name.properties` or `tierlb.properties` `lb.persistence.method=cookie-insert` is specified in `tier.properties`	A 1-13 character string consisting of alphanumeric characters and underscores (`_`)	None	08-70
`lb.timeout`	Specify the timeout period (in seconds) for login to the loader balancer or command transmission. If login to the load balancer or a CLI command issued to the load balancer is not complete within the time specified in this key, the `vmiunit` command will end abnormally due to a timeout error.	`1`-`2147483`	`10`	08-53
`lb.API.protocol`	Specify the protocol to be used for communication with the load balancer. `http`: Uses the HTTP communication protocol. `https`: Uses the HTTPS communication protocol.	The following values can be specified: `http` `https`	`https`	09-00
`lb.ACOS.privilegedexec.password`	Specify the password necessary for the Privileged EXEC level set on ACOS. The specified key is only valid when the load balancer type is ACOS.	Any character string can be used.	None	08-53
`javax.net.ssl.trustStore`	Specify the trust store where the server certificate for the load balancer is registered. The specified key becomes effective if all of the following values are specified in `LB-connection-information-distinguished-name.properties` or `tierlb.properties`: `lb.type=ACOS` `lb.protocol=API` `lb.API.protocol=https`	Follow the Java specifications.	cacerts (Default trust store for JDK)	08-70
`javax.net.ssl.trustStorePassword`	Specify the password for the trust store where the server certificate for the load balancer is registered. The specified key becomes effective if all of the following values are specified in `LB-connection-information-distinguished-name.properties` or `tierlb.properties`: `lb.type=ACOS` `lb.protocol=API` `lb.API.protocol=https`	Follow the Java specifications.	cacerts (The default key store trusted by Java is used.)	08-70

To Page Top