Managing HP Serviceguard Extension for SAP for Linux (May 2013)

Table 25 Legal values for sgesap/sap_infra_sw_type (continued)
DescriptionValue
SAP webdispatcher (not installed as SAP instance, but
unpacked and bootstrapped to
/usr/sap/<SID>/sapwebdisp)
sapwebdisp
SAP software network routing toolsaprouter
You can specify the saprouter and biamaster values more than once.
The attribute sap_infra_treat specifies whether the component will only be started/notified
with the package startup, or whether it will also be stopped as part of a package shutdown (default).
Possible values are startonly and startnstop.
sap_infra_sw_params specifies additional command line parameters to be called with the
component. You can add the sap_infra_sw_host parameter to specify the hostname where
to start a BIA master instance. You can ignore this parameter for other infrastructure components
because this will not have any effect as these are always started or stopped locally.
Examples:
sap_infra_sw_type saposcol
sap_infra_sw_type saprouter
sap_infra_sw_treat startnstop
sap_infra_sw_params "-H virtual_IP -W 20000\
-R /sapmnt/C11/profile/saprouttab\
-T /sapmnt/C11/profile/dev_rout1"
sap_infra_sw_type sapccmsr
sap_infra_sw_params /sapmnt/C11/profile/ccmsr_profilename
sap_infra_sw_type sapwebdisp
sap_infra_sw_treat startnstop
sap_infra_sw_params “-shm_attachmode 6”
When using the Serviceguard Manager to configure this module the following can be configured:
Figure 21 Configuring SAP infrastructure software components screen
76 Clustering SAP using SGeSAP packages