HP Storage Essentials SRM Enterprise Edition 6.0 Microsoft Windows Application Integration Software for SAP ACC version A.02.00 User Guide (T4283-96336, July 2008)

Application Scripts Description and Usage66
4. If the SAP Java instance is supported, it must be started before the Central Instance is started. In
this case, use SAPSTARTSRV.EXE to register the Java start profile, the SAP service user ID, and
the user environment. In the sample script, this is represented by the variables
JAVA_START_PROFILE, %USERDOMAIN%\%SAPService%SID%, and
%USERDOMAIN%\%SID%adm.
Include a waiting time (around 10 seconds) for the Java instance to start.
5. Start the Central Instance using SAPSTARTSRV.EXE. In the sample script, this is implemented
by the following command:
%SYSTEMDRIVE%\usr\sap%SID%\%SID%\sys\exe\run\SAPSTARTSRV.EXE
-r -q -p %START_PROFILE% -s %SID% -n %INR% -U
%USERDOMAIN%\SAPService%SID% -P %SAPSERVICEPASSWD% -e
%USERDOMAIN%\%SID%adm
6. Copy SAPSTARTSRV.EXE and the librfc32.dll to the system32 directory in your
Windows directory (for example: C:\WINDOWS\system32). The sample script copies these
files to the system32 directory and then changes to this directory location.
7. Verify that the following SAP services are present:
• SAP System Message Port
• SAP System Dispatcher port (for the SAP instance number)
• SAP System Dispatcher Security Port (for the SAP instance number)
• SAP System Gateway Port (for the CI)
• SAP System Gateway Security Port (for the CI)
• SAP System Gateway Port (for the SAP instance number)
• SAP System Gateway Security Port (for the SAP instance number)
The sample script executes a series of find commands to verify that the SAP services are
present. For example, to check if the SAP System Message Port service is present, you can run
the following command:
NOTE: You must customize this command for your system before running it.
find /i "sapms%SID%" %windir%\system32\drivers\etc\services
if %errorlevel%==0 goto sapms_defined
echo sapms%SID% 36%CINR%/tcp # SAP System Message Port >>
%windir%\system32\drivers\etc\services
After you have customized this script to your satisfaction, place the customized script in the
C:\usr\sap\adaptive\ directory on the Managed Node and execute it.
Verify the script has successfully started the SAP Central Instance. This process may vary depending
on the particular system. Consult the corresponding vendor documentation. Notice that the Central
Instance can not be verified unless the Database Instance is also running.
Attaching the SAP Database Instance
The purpose of this script is to attach the SAP Database (DB) Instance to the target SQL server.