Installing SAP Solution Manager AS ABAP
SAP Solution Manager 7.2 needs two separate SAP systems to work as designed. One of those SAP systems is AS ABAP-based, the other on is AS Java-based. Both systems need to cooperate closely to offer all functions delivered with SAP Solution Manager 7.2. Therefore, during the installation of the SAP Solution Manager ABAP we will encounter elements that refer to SAP Solution Manager Java, and vice versa.
The SAP Solution Manager ABAP system needs to be installed first. For both SAP systems we will use the database SAP MaxDB, which will be installed by SAPinst.
For this installation, we make use of the option SAPinst offers to install the SAP system using a virtual host name. On Windows, the usage of virtual host names requires certain preparation steps.
We need to take special care when using virtual host names in our training environment. Aside from other preparation steps (not further detailed here) we need to add a registry key to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0, named BackConnectionHostNames set to the values, in our case: smxhost.wdf.sap.corp and smxhost. In addition to other steps, this allows us to connect to our training server using the names listed.
Note
Please read SAP Note1564275: How to Install SAP Systems Using Virtual Host Names on Windows for further information on the required steps for using virtual host names on Windows.
When preparing the installation, make sure to use the latest version of the tool Software Provisioning Manager. Extract the archive file to create a directory that contains the tool SAPinst.
SAPinst offers some command line options for being started. We will use the option SAPINST_USE_HOSTNAME for installing this SAP system. When using this option you can install your SAP system using virtual hostnames.
Note
Please note, that you will encounter different versions of the tools used in this course. SWPM 1.0 is the tool to install SAP Solution Manager 7.2.
As we did not configure SSL communication for SAPinst, the browser will warn about an insecure connection. You need to authenticate with a sufficiently authorized user.
The figure above shows the installation options offered by SWPM 1.0. These options depend on the version of SWPM.
Within SWPM (started by calling the executable SAPinst), drill down to the installation that you would like to perform.
The figure above highlights the selection (Standard System) that will install all AS ABAP-based elements of an SAP Solution Manager 7.2 Support Release 2 using the database SAP MaxDB.
Other installation options offer the distribution of components (Database, PAS, ASCS) onto different hosts or provide options for installing an SAP system within a high-availability environment.
After choosing Next, you will enter the dialog phase of the installation process, in which you will provide/set many parameters required by the installation process.
Within SAPinst, navigate to the Prerequisites Check if you would like to prepare for the actual system installation in advance.
The figure above shows the selection of the parameter modeCustom. It allows for setting each parameter explicitly; you are guided through each step. Always select Custom.
The parameter mode Typical presents a reduced set of steps. The final parameter check allows for the revision of each parameter.
In case SAPinst requires the update of certain DLLs a reboot of the server is necessary. Please note, that right after the reboot and logging on to the server, SAPinst will automatically restart and offer to proceed where you left off.
You are prompted for the SAP system ID (SAPSID) that your system should use. Note that some SIDs cannot be used; for example, the SID SAP is forbidden. The SAP System ID needs to be chosen following specific rules. Find more information in SAP Note 1979280: Reserved SAP System Identifiers (SAPSID) with Software Provisioning Manager 1.0.
Also above, you find another screen asking for the DNS Domain Name for your SAP system. Set the flag for Full Qualified Domain Name (FQDN) and provide the domain name to which your SAP system belongs. If you do not provide values here, different functions of your SAP system might not be usable or may require additional work.
The previous figure is of essential significance. Here you provide the so-called Master Password for this installation. The master password is used for standard users in the SAP system and for users on the operating system and database level, in case the database is installed by SAPinst — which is true for SAP MaxDB (e.g.). SAP recommends that after installation, you set individual passwords for the different users.
On operating system Windows you can decide on the next screen (also shown above) on the Domain Model for this installation. Usually, SAP systems are installed with admin users created on Domain level. In this training environment we select a so-called Local Domain installation.
The figure above shows the setting of the passwords for two users created during installation on Windows OS: <SID>adm and SAP Service<SID>. The default for this password is the master password you chose previously. You can specify a different password for these users.
On the lower screen shot in the figure above you find the setting of the SID for the database (DBSID).
The screen above asks you to enter the path to the installation media that should be used throughout the installation process. Theoretically, SAPinst should be able to identify several different installation media stored in the same location. At least the kernel installation is required to be found at that location. Also, you are required to provide archives (as listed) for kernel components in the same location.
The media directory shown in the figure above contains several installation media required during the installation as well as kernel packages.
A Prerequisite Check is always executed, its results shown. Sometimes you can skip/ignore the results of the Prerequisite Check.
Provide the installation archive for SAP Host Agent, unless the archive had already been found as shown above.
SAP Host Agent will receive an own SAPSID, default SAP. SAP Host Agent also requires an OS-level user, here sapadm.
Also provide the path to the installation media used for the database installation during SAPinst, in this case SAP MaxDB and set the destination drive for the SAP MaxDB Client Software.
Provide the path to the Installation Export 1 and 2 packages and set the destination drive for the SAP MaxDB Server Software.
Confirm or change the (master) password for important database users.
Please adapt the location and size of the log volumes to your needs.
Please adapt the location and size of the data volumes to your needs.
The password for the database schema of your SAP MaxDB is set to the master password by default. You can change this password now or later. In this course we recommend to use the master password.
The option to Enable the declustering / depooling of all ABAP tables will be the default for the SAP database table layout for SAP Products based on AS ABAP 7.50 and higher. For SAP systems based on earlier AS ABAP releases, you might be offered the choice seen above. When installing a new SAP system, SAP recommends to use this option.
The database load process can use several CPU resources in parallel, which will decrease the installation run time. Note that the parallel processing will be using CPU resources and the database system itself will be also using CPU resources (defined earlier). Therefore, we recommend that you match the number of parallel jobs to the CPU capacity you assigned to the database system. Overall do not use more CPU capacity than your server or environment offers. Additionally, many import jobs running in parallel might require the database system to create MANY lock entries. On high-performance hardware, if the number of parallel import jobs has been set too high, the default number of possible locks (as defined by SAP delivery) might become a bottleneck
The figure above shows the selection screen for setting the instance numbers for the Primary Application Server (PAS) and the ABAP Central Services (ASCS) of the SAP system. The two-digit instance number needs to be chosen from the numbers between 00 and 97 and they must be unique on an individual host.
The instance number defines several port numbers used for communication by your SAP system. For example, an ABAP dispatcher process communicates via port 32## where ## signifies the instance number. Therefore, in case any software on your SAP host uses ports in the range of 3200 to 3299 (for example), this need to be taken into consideration. SAPinst can only list ports used by SAP instances — so further restrictions need to be consider by you.
The default values of the ABAP message server port and the internal ABAP message server port are determined by your previous entry for the Central Instance. The port number for the ABAP message server is 36## and the port number for the internal ABAP message server is 39##, where ## is the value that you specified for the ASCS. You can choose different port numbers (even outside the 36## and 39## range) if those port numbers are not already in use.
When an installed component offers an Internet Communication Manager (ICM) process then you are prompted to enter a password for the user webadm. This user can access administration functions offered by ICM via Web interface.
To increase the security of your SAP system, you can create a Message Server Access Control List (ACL) that can be used to limit access to the Message Server. In this training, we do not create such an ACL because we would be required to delete it before installing an Additional Application Server. For more information, please read the SAP Notes mentioned on the screen shot above.
You can select additional components to be installed as part of the ASCS instance.
When you choose to install additional components into the ASCS, those might require additional parametrization, as shown for SAP Web Dispatcher above.
You can enhance the security of your SAP system by generating an individual key for the secure store of SAP system.
Save the information shown in the Message Box you can see in the figure above. Store this information in a secure place.
On the screen above you can confirm the default user IDs for users that are stored within the SAP Solution Manager ABAP system and are used by the SAP Solution Manager Java system. Usually, you should refrain from changing these user default names.
Please note, that when installing the SAP Solution Manager Java system you should replace the (THEN) proposed user IDs by those used during the installation of the SAP Solution Manager ABAP system:
J2EE_ADM_<SID> needs to be replaced by J2EE_ADMIN and
J2EE_GST_<SID> needs to be replaced by J2EE_GUEST.
SAPJSF needs to stay unchanged.
You are also prompted for the password of the administrator user and the communication user. The default values for the passwords are the master password.
You can set individual passwords for SAP system users DDIC and SAP* – different from the master password.
When you start SAPinst with providing an Stack-XML file, you will encounter this additional option: to configure the Transport Management system of the system to be installed. In case you select this option, the TMS will be configured very simple and further installation options become available, as shown in the next slides.
In case you let SAPinst configure the TMS, SAPinst can import a SPAM/SAINT update at the end of the installation.
In case you let SAPinst configure the TMS, you can also provide a directory with transport files (data and cofiles) – those transport requests will be imported at the end of the installation.
SAPinst can also start the SUM (after extracting an archive that you need to provide), for this option to be shown, the configuration of TMS is mandatory as well.
Note
Please note that it is highly recommended to execute some post installation activities right after installation, BEFORE starting (and using) SUM. For example, the SUM Master Guide can ask you to apply certain SAP Notes, Kernel Patches or Database Patches BEFORE you use SUM to update the SAP system.
SAPinst can import additional SAP system languages at the end of the installation. For this you have to provide the corresponding language packages.
The following screen show the Parameter Summary. You can select individual parameters and choose to revise them. If you don’t select at least one parameter, the button Revise will remain grayed out.
The installation phase Import ABAP takes a significant amount of time.
Congratulations: The installation of your SAP Solution Manager ABAP system finished successfully!