Friday, 6 June 2014

SAP Router Installation

SAProuter Installation Step by Step

SAProuter Installation

1.     Introduction

The purpose of this document is to set out the process used in the creation of a SAProuter connection to SAP.

2.     Installation Process

2.1. Server

A dedicated server (hostname) has been built for the SAProuter). The spec of this server is:
·         2 hyper-threading (HTT) CPUs with 2GHz tact frequency
·         2 GB RAM
·         50 MB free space on the hard drive for SAProuter and configuration
·         20GB D: drive for SAP router & log files
·         64bit server
·         OS  Windows 2008
Its internal IP address: Host IP

2.2. SAP Registration

In order to have this new SAProuter connection with SAP, registered the following details with SAP.
On approval SAP register the following details in the SAP Marketplace


1.1. SAProuter Software

The following version of the SAProuter software was downloaded from the SAP Marketplace:
·         SAProuter 7.20 (patch level 423) for Windows on x64 64bit



We also downloaded the following cryptographic software for the SNC connection
·         SAPCRYPTOLIB 5.5.5 (patch level 36) for Windows on x64 64bit

1.1. Setting the environment variable

Once the software has been installed on the server the next step is to set the environment variables SECUDIR and SNC_LIB. These are as follows:
·         SECUDIR = D:\usr\sap\sap\saprouter
·         SNC_LIB = D:\usr\sap\sap\saprouter\ntintel\sapcrypto.dll
One set reboot the system once you have checked that the terminal services have started.

1.1. Downloading and installing the SAProuter certificate

From the SAP Marketplace download a certificate and then install it on the server. The process for doing this is as follows.
Go to the SAP Marketplace and obtain the “Distinguished Name” for the new SAProuter installation as advised by SAP. For this installation it is:
·         CN=HOSTNAME, OU=0000848841, OU=SAProuter, O=SAP, C=DE

Generate the certificate request with the command: sapgenpse get_pse -v -r certreq -p local.pse "" as follows:
·         sapgenpse get_pse -v -r certreq -p local.pse "CN=hostname, OU=0000848841, OU=SAProuter, O=SAP, C=DE"
From the directory D:\usr\sap\sap\saprouter\ntintel\, copy the content of the file certreq to the second tab “Create and Enter CSR” in the SAP Marketplace.


SAP will then return the new certificate on selecting “Request Certificate
Copy and paste the text to a new local file named "srcert", which must be created in the same directory as the sapgenpse executable (D:\usr\sap\sap\saprouter\ntintel\)

This certificate needs to be imported into SAProuter.
First of all execute the following command on the /saprouter/ntintel directory:
·         sapgenpse import_own_cert -c srcert -p local.pse
Enter PIN: ?????

Now you will have to create the credentials for the SAProuter to do this execute the following command in the /saprouter/ntintel directory.
·         sapgenpse seclogin -p local.pse
·         Enter PIN: ????? (same as point 9)
This will create a file "cred_v2" in the same directory as local.pse.

To check whether the certificate has been imported correctly execute this command in the /saprouter/ntintel directory.
·         sapgenpse get_my_name -v -n Issuer
The successful result will be: Issuer  : "CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE".

1.1. Installing the SAProuter as an NT Service

Should there be registry changes also detailed here?
Use the following command to newly define the service from the command line:
·         sc.exe create SAPRouter binPath= "D:\usr\sap\saprouter\saprouter.exe service -r -W 60000 -R D:\usr\sap\saprouter\saprouttab -K ^p:CN=HOSTNAME, OU=0000848841, OU=SAProuter, O=SAP, C=DE ^" start= auto obj= "NT AUTHORITY\LocalService"
You will receive the following success message: [SC] CreateService SUCCESS

1.1. Starting the SAProuter


To start the SAProuter use the following command line:
·         saprouter -r -S -K "p:"
(-K tells the SAProuter to start with loading the SNC library)
In our case the command was:
·         saprouter -r -K "p:CN=hostname, OU=0000848841, OU=SAProuter, O=SAP, C=DE"
The parameter  -S , was omitted and therefore the SAProuter is using the default port 3299.

Network Part.
|

|
Network Part.


Steps described in SAP note 525751(Installation of the SNC SAP Router as NT Service)
Edit the string in the registry under MyComputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ saprouter and change ^ to “ under Image Path.


Then Save it.

Routtab configuration.

The corresponding file saprouttab must contain at least the following entries
# Outbound connections to will use SNC
KT "p:CN=sapservX, OU=SAProuter, O=SAP, C=DE"
# Inbound connections MUST use SNC
KP "p:CN=sapservX, OU=SAProuter, O=SAP, C=DE"
# Repeat this for the servers and port_numbers you will need to
# allow. Please make sure that all explicit ports are inserted
in
# front of a generic entry '*' for port_number
# Permission entries to check if connection is allowed at all
P
# All other connections will be denied
D * * *
 Configuration in SAP market place and OSS1 (Technical settings)

Tcode- OSS1

Go to – technical settings
 Maintain the details. (New SAP router details)


Cross check the Msg Server string, it should be with the new SAP router,

/H/Router Host IP/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001

Login to SMP. (SAP market place)

Help & Support -> Connect to SAP > Maintain connection

Select the system.> go to system data. Update the router information as below indicated


Installation of SAP Solution Manager in Windows platform compatible with Amazon / Azure Cloud / Hyper-V / Standalone server

The SAP Solution Manager 7.1 installation steps below suitable on all Windows server environment including Amazon Web Services (AWS), Microsoft Azure, Microsoft Hyper-V or standalone server installation.

These configurations including:
A) Prerequisite
B) Oracle Database Installation
C) SAP Solution Manager 7.1 Installation with SWPM
D) SAP GUI Installation and login the SAP Solution Manager for the first time
E) Others


A) Prerequisite:
1) Windows server 2008 be ready

2) Minimum SAP Solution Manager 7.1 installation files
Download ObjectTitle
50118243_6NW 7.0 Presentation - 7.30 Compilation 2 Present. ½
51041940ORACLE Client 11.2.0.3
51042334_1 – 6ORACLE RDBMS 11.2.0.3 Windows x64
51042607_1 - 12SAP SOLMAN 7.1 SR1 Inst. Export (2)
51042609_1 – 5SAP SOLMAN 7.1 SR1 Java Comp
51042616_9SL CONTROLLER 700
51046511_6720 UC Kernel for SWPM SP03 - Windows Server on x64 64bit
70SWPM10SP02_4-20009707.sarSoftware Provisioning Manager 1.0 SP2 for NW 7.0x

3) Recommended server specifications:
TypeDescriptions
OSWindows Server 2012 Data Center
RAM12GB
Hard disk400GB (c:\ 100GB d:\300GB)

4) Reference for OS environment setup on AWS Cloud and Microsoft Hyper-V
- AWS Cloud:  Section: AWS AMI Setup and Configurations (SAP IDES Installation)

5) Assumption:
     - The Windows OS will be configure as workgroup instead of joining a domain / active directory.
     - All the installation are mostly with default settings and further configurations or fine tune will be perform
        after the installation.
     - Windows OS been patched to latest update and some prerequisite steps as in SAP IDES Installation
     - The installation time estimation was based on a installation on Microsoft Hyper-V 2012 environment
        with the above mentioned hardware. In fact, the actual installation time might vary.

B) Oracle Database Installation

1) Run the Oracle setup batch file "sapserver,cmd" to begin the database installation

 2) Enter the installation drive and SID

 3) Installation splash screen

 4) Click "Next"

 5) Click "Next" ignore the warning

 6) Select "Skip the software updates"

 7) Select " Install database software only"

 8) Select "single instance database installation"

 9) Click "Next"

 10) Select "Enterprise Edition"

 11) Choose the installation drive

 12) Wait for the verification process

 13) The verification process

 14) Click "Install" to begin the installation

 15) Click "Details" button to shown the installation progress

 16) The additional installation progress screen

 17) Wait until the installation complete and the click "Close" button

 18) Confirm the database been installed



B) SAP Solution Manager 7.1 Installation with SWPM
The installation process estimate will take about ~5 hours to complete with the above mentioned hardware specifications

1) Double click the "sapinst" extracted from SWPM - Section E) Others below shown how to extract the installation file with sapcar program

 2) Select "SAP Solution Manager 7.1 Support Release 1"

 3) Select "typical"

 4) The installation splash screen

 5) Select the SWPM kernel

 6) Enter the SAPSID and installation drive

 7) Configure the FQDN or it can be configure after the installation

 8) Enter the master password

 9) Enter the Oracle database ID created during the database installation

 10) Select the installation export package

 11) Select the other installation export package

 12) Click  "Next" with all the default settings

 13) Select the Java component package

 14) Ensure the installation drive are correct

 15) Click "Next" to accept the default listener configuration or change the port according to existing firewall
        policy

 16) Select the kernel package

 17) Select the Oracle client package

 18) Select "Configure a local SLD" in this example

 19) Enter the computer name in "Object Server Name"

 20) Click the "Next" button

 21) Click "Yes" button

 22) Click "No SLD destination" in this example

 23) Verify the selected options and click "Next" to accept all the settings

 24) The installation begin

 25) Example of the installation process

 26) Example of the installation process

 27) Example of the installation process

 28) Around ~5 hours for the installation to complete

 29) SAP management console and listener status command showing the SAP services are up and running