User's Guide

sap_ext_host node2
sap_ext_treat nnnyn
sap_ext_instance D03
sap_ext_host node2
sap_ext_treat yyyyn
Subsection for additional SAP infrastructure software handling: OS472
Parameters to influence SAP software that runs outside of SAP Application Server Instances come with module
sgesap/sapinfra.
sap_infra_sw_type defines a SAP infrastructure software component that is to be covered by the package.
Such software pieces often support a specific SAP Netweaver Application Server, but they won't get started
and/or stopped as part of the Instance. SAP Netweaver Application Server Instances are not specified here,
but by using the sap_instance attribute. Legal values for sap_infra_sw_type:
saposcol = a SAP operating system monitor collector
sapccmsr = a SAP additional monitor collector
rfcadapter = a SAP XI/PI/EAI remote function call adapter
The following values can be specified more than once:
saprouter = a SAP software network routing tool
biamaster = a SAP BIA master nameserver (not for production use)
sap_infra_treat defines whether the tool 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 defines additional command line parameters to be called with the tool.
A sap_infra_sw_host value can be added to specify the hostname where to start a BIA master instance.
This parameter will be ignored for other infrastructure components, which always get started/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
Installation Step: IS473
Integrate the SAP startup framework with the cluster.
SAP introduced a startup control framework with Netweaver 2004s and SAP Application Server 7.0 that
enables the management of SAP instances from third party products using a defined application interface.
This control framework is implemented using a daemon process that is either started by:
• the operating system during boot time or
• the SAP startup script when the instance is started.
During the installation of a SAP Netweaver 2004s Web AS, the SAPIinst installer edits a file in
/usr/sap/sapservices and adds a line for each sapstartservice instance. During boot time an
init script is executed located in:
/sbin/init.d/sapinit referenced by /sbin/rc3.d/S<###>sapinit
The sapinit script reads the content in file /usr/sap/sapservices and starts a sapstartsrv for
each instance during OS boot time. This can lead to error output in the boot messages log file as file systems
for exclusive shared storage is not available at that time.
Modular Package Configuration 63