SAP JAVA Central Services (SCS) - Enqueue Replication Server (ERS) high availability policy (Java™)

Enter the name of your SA MP domain.

Provide the name of an existing SA MP domain. The SA MP domain will host the SAP resources that will be configured with this template.

Select the IP version used in the SAP environment.

Depending on the IP version, either a NetMask for IPv4 or a NetPrefix for IPv6 has to be specified.

One of the following values:

IPv4

IPv6

Specify the existing SAP system ID (SID).

The SAP system ID consists of 3 characters and is configured during the SAP installation.

Minimum number of characters: 3, maximum number of characters: 3 (plus additional value checking)

Specify your SAP instance owner user name.

The default SAP instance owner user's name is composed of the SAP SID (in lower case) and the suffix "adm".

Enter your desired prefix for all JAVA resources.

This prefix will be used as a prefix for all SA MP resources that cover SAP JAVA components. For later operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. You may consider to encode the SAP solution name, e.g. EP (Enterprise Portal), which would result in a prefix like "PE_JAVA".

Enter the nodes where you want to automate your SAP Central Services Instance for JAVA (SCS).

These nodes must be listed by the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. A SCS resource will be created for each of the specified nodes.

List of values, value type for each value:

Hostname or IP version 4 address (plus additional value checking)

Specify the instance name of the SAP Central Services Instance for JAVA (SCS).

This instance name is used for the instance directory that contains all necessary files for the SCS instance. A sample instance name is 'SCS01'.

String

Minimum number of characters: 5, maximum number of characters: 5

Specify the virtual host name for the Central Services Instance for JAVA (SCS). Enter the same virtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-virt_hostname- during the SAP installation.

This host name will be used as a virtual host name for the Central Services Instance for JAVA (SCS).

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv4"

Specify the virtual IPv4 address for the SAP Central Services Instance for JAVA (SCS).

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv6"

Specify the virtual IPv6 address for the SAP Central Services Instance for JAVA (SCS).

This IPv6 address will be used as a virtual IP address for the floating SAP Central Services Instance for JAVA (SCS).

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv4"

Specify the netmask for the virtual JAVA SCS instance IP address.

Enter the netmask for the subnet of the JAVA SCS instance IP address. An example for a netmask is "255.255.255.0".

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv6"

Enter the NetPrefix for the JAVA SCS instance virtual IP address.

Enter the NetPrefix for the JAVA SCS instance virtual IP address. An example for a NetPrefix is 80.

Numeric

Minimum value: 0, maximum value: 128

Specify the network interface name where your JAVA SCS instance virtual IP address is activated on each node as alias. The following network interfaces are available on your local system:

(remaining part of description is harvested from running system)

The network interface specifies on which network interface on each node the virtual JAVA SCS instance IP address can be bound to, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be available on all nodes where the JAVA SCS instance will be automated.

Specify the instance name of the JAVA ERS instance.

This instance name is used for the instance directory that contains all necessary files for the JAVA ERS instance. A sample instance name is 'ERS11'.

String

Minimum number of characters: 5, maximum number of characters: 5 (plus additional value checking)

Specify the virtual host name of SAP JAVA enqueue replication server (JAVA ERS).

This host name will be used as a virtual host name for the JAVA ERS instance. Enter the same virtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-virt_hostname- during the JAVA ERS installation. If the ERS instance was not installed using a virtual host name, then specify the host name of a unique IP address that will be moved together with the ERS. This host name allows the SAP tools to connect to the node currently running the ERS.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv4"

Specify the virtual IPv4 address for the JAVA enqueue replication server (JAVA ERS).

This IPv4 address will be used as a virtual IP address for the JAVA enqueue replication server (JAVA ERS) instance.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv6"

Specify the virtual IPv6 address for the JAVA enqueue replication server (JAVA ERS).

This IPv6 address will be used as a virtual IP address for the JAVA enqueue replication server (JAVA ERS) instance.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv4"

Specify the netmask for the virtual JAVA ERS instance IP address.

Enter the netmask for the subnet of the virtual JAVA ERS instance IP address. An example for a netmask is "255.255.255.0".

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv6"

Enter the NetPrefix for the JAVA ERS instance virtual IP address.

Enter the NetPrefix for the JAVA ERS instance virtual IP address. An example for a NetPrefix is 80.

Numeric

Minimum value: 0, maximum value: 128

Specify the network interface name where your JAVA ERS instance virtual IP address is activated on each node as alias. The following network interfaces are available on your local system:

(remaining part of description is harvested from running system)

The network interface specifies to which network interface one each node the virtual JAVA ERS instance IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be available on all nodes where the JAVA ERS instance will be automated.

Do you want to automate the JAVA application servers?

Automation of the JAVA application servers is recommended, but optional. Choose yes if you want to automate the JAVA application servers.

Optional; a value for this parameter is only required if parameter #21 has the value "yes".

Enter the nodes where you want to automate the application servers.

These nodes must be listed by the SA MP command "lsrpnode" for the specified domain. You can use either the long or the short name for a node. An SA MP application server resource will be created for each of the specified nodes.

This parameter must have the same number of values as the following parameters:

- Parameter # 21, nested parameter 2

List of values, value type for each value:

Hostname or IP version 4 address

Optional; a value for this parameter is only required if parameter #21 has the value "yes".

Specify all instance names of your application servers. Use the same order as for the nodes in one of the previous questions.

In this policy, the instance names are used to identify the instance directory that contains all necessary files for the application server. The naming syntax is J-InstanceID- or JC-InstanceID-. Use the same order as for the nodes in one of the previous questions, i.e. if you specified node01 first, then you now have to specify the instance directory for your application server on node01 first.

This parameter must have the same number of values as the following parameters:

- Parameter # 21, nested parameter 1

List of values, value type for each value:

String (plus additional value checking)

Optional; a value for this parameter is only required if parameter #21 has the value "yes".

Enter the start timeout value for your JAVA application servers.

The start timeout attribute determines the maximum run time in seconds of the StartCommand. If the StartCommand does not return within the timeout period, System Automation for Multiplatforms kills the StartCommand with the SIGKILL command and logs a message to the system log of the node. The default value for the JAVA application servers is 500.

Optional; a value for this parameter is only required if parameter #21 has the value "yes".

Enter the stop timeout value for your JAVA application servers.

With the stop timeout attribute you specify the amount of time in seconds the stop command for your application servers allowed to run before it is killed by Tivoli System Automation. The default value for the JAVA application servers is 360 seconds.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 21 has the value "yes"

Did you configure a virtual host name during installation for at least one of the application servers specified in the previous question?

Choose yes if at least one of the application servers has been installed with a virtual host name.

{yes|no}

Optional; a value for this parameter is only required if parameter #22 has the value "yes".

Specify the virtual host name for each application server. Use the same order as for the nodes in one of the previous questions. If you installed one of the application servers without a virtual host name, specify the system host name instead.

This host name will be used as a virtual host name for an application server. Enter the same virtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-virt_hostname- during the SAP installation. Use the same order as for the nodes in one of the previous questions, i.e. if you specified node01 first, then you now have to specify the virtual host name for your application server on node01 first.

List of values, value type for each value:

Hostname

Do you want to automate the SAP Host Agent?

SAP Host Agent can be used for monitoring and control of SAP instances and non-SAP instances, operating systems, and databases.

Optional; a value for this parameter is only required if parameter #23 has the value "yes".

Enter the nodes where you want to automate the SAP Host Agent.

These nodes must be listed by the SA MP command "lsrpnode" for the specified domain. You can use either the long or the short name for a node. An SA MP host agent resource will be created for each of the specified nodes.

List of values, value type for each value:

Hostname or IP version 4 address

Do you want SA MP to automate your SAP router?

SAP router serves as a proxy in a network connection between SAP systems or between SAP systems and external networks. If you answer this question with yes, SA MP will create automation resources for the SAP router.

Optional; a value for this parameter is only required if parameter #24 has the value "yes".

Enter the desired prefix for the SAP router resources.

You are allowed to use the same prefix as for other resources, like JAVA or ABAP.

Optional; a value for this parameter is only required if parameter #24 has the value "yes".

Enter the nodes where you want to automate the SAP router.

For each of the nodes specified, SA MP will create SAP router resources.

List of values, value type for each value:

Hostname or IP version 4 address (plus additional value checking)

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv4"

Optional; a value for this parameter is only required if parameter #24 has the value "yes".

Specify the virtual IPv4 address that clients will use to connect to the SAP router.

This virtual IPv4 address is used to reach the SAP router, independent of the system it is currently running on.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv6"

Optional; a value for this parameter is only required if parameter #24 has the value "yes".

Specify the virtual IPv6 address that clients will use to connect to the SAP router.

This virtual IPv6 address is used to reach the SAP router, independent of the system it is currently running on.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv4"

Optional; a value for this parameter is only required if parameter #24 has the value "yes".

Specify the netmask for the SAP router virtual IP address.

Enter the netmask for the subnet of the SAP router virtual IP address. An example for a netmask is "255.255.255.0".

Do you want SA MP to automate the SAP Web dispatcher?

- Parameter # 2 has the value "IPv6"

Optional; a value for this parameter is only required if parameter #24 has the value "yes".

Enter the NetPrefix for the SAP router virtual IP address.

Enter the NetPrefix for the SAP router virtual IP address. An example for a NetPrefix is 80.

Numeric

Minimum value: 0, maximum value: 128

Optional; a value for this parameter is only required if parameter #24 has the value "yes".

Enter the network interface for the SAP router IP address. The following network interfaces are available on your local system:

(remaining part of description is harvested from running system)

The available network interface specifies to which network interfaces the SAP router virtual IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be available on all nodes where the SAP router will be automated.

Optional; a value for this parameter is only required if parameter #24 has the value "yes".

Specify the fully qualified SAP router routing table filename.

Use the location of the NFS device that contains the routing table file. An example for the fully qualified SAP router routing table filename is /usr/sap/-SAPSID-/SYS/global/saprouttab.

Do you want SA MP to automate the SAP Web Dispatcher?

The SAP Web dispatcher receives HTTP(s) requests from the internet that are targeted for your SAP system. If you answer this question with yes, SA MP will create automation resources for the SAP Web dispatcher.

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Enter the desired prefix for the SAP Web Dispatcher resources. You are allowed to use the same prefix as for other resources, like JAVA or ABAP.

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Enter the nodes where you want to automate the SAP Web Dispatcher.

Nodes where the SAP Web Dispatcher is configured and where it will be automated.

List of values, value type for each value:

Hostname or IP version 4 address (plus additional value checking)

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Specify the SAP system ID (SAPSID) for the SAP Web Dispatcher.

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Specify the instance owner username that will be used to execute the start, stop and monitor commands for SAP Web Dispatcher resources.

The instance owner username is composed of the SAP Web Dispatcher SID and the suffix "adm".

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Specify the instance name of the SAP web dispatcher instance, i.e. 'W00'.

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Specify the virtual host name for the SAP Web Dispatcher.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv4"

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Specify the virtual IPv4 address that clients will use to connect to the SAP Web Dispatcher.

This virtual IPv4 address is used to reach the SAP Web Dispatcher, independent of the system it is currently running on.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv6"

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Specify the virtual IPv6 address that clients will use to connect to the SAP Web Dispatcher.

This virtual IPv6 address is used to reach the SAP Web Dispatcher, independent of the system it is currently running on.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv4"

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Specify the netmask for the SAP Web Dispatcher virtual IP address

Enter the netmask for the subnet of the SAP Web Dispatcher virtual IP address. An example for a netmask is "255.255.255.0".

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 2 has the value "IPv6"

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Enter the NetPrefix for the SAP Web Dispatcher IP address.

Enter the NetPrefix for the SAP Web Dispatcher IP address. An example for a NetPrefix is 80.

Numeric

Minimum value: 0, maximum value: 128

Optional; a value for this parameter is only required if parameter #25 has the value "yes".

Specify the network interface on which SAP Web Dispatcher virtual IP address is activated on each node as alias. The following network interfaces are available on your local system:

(remaining part of description is harvested from running system)

The available network interface specifies to which network interfaces the SAP web dispatcher virtual IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be available on all nodes where the SAP Web dispatcher instance will be automated.

This parameter will be ignored unless all following conditions are fulfilled:

- Parameter # 21 has the value "yes"

If your database is automated with SA MP in the same cluster, do you want to create startAfter relationships for your application servers?

A startAfter relationship will be created for each Application Server. If you want to create startAfter relationships to a database, the database needs to be automated in the same cluster as SAP.

Optional; a value for this parameter is only required if parameter #26 has the value "yes".

Enter the name of your floating SA MP database resource.

This is the name of your floating SA MP database resource, i.e. "db2_db2ax0_0-rs".