Installing an SAP Solution Manager Java System

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.

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. 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. This allows us to connect to our training server using the names listed.

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 Software Provisioning Manager (SWPM). These options depend on the version of SWPM.

Within Software Provisioning Manager (started by calling the executable SAPinst), drill down to the installation that you would like to conduct.

The figure above highlights the selection (Standard System) that will install all AS Java-based elements of an SAP Solution Manager 7.2 Java Support Release 2 using the database SAP MaxDB.

Other installation options offer the distribution of components (Database, PAS, SCS) 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 Software Provisioning Manager (started by calling the executable 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 mode Custom. It allows for setting each parameter explicitly; you are guided through each step. We select this setting for this course.

The parameter mode Typical presents a reduced set of steps. The final parameter check allows for the revision of each parameter – even those side-stepped by choosing typical parameter mode. In most circumstances, typical parameter mode is sufficient.

You can see that the first installation archive that is asked for is SAP Java Virtual Machine (SAP JVM).

SAPinst will ask for several installation media during the dialog-phase of the installation procedure.

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 always 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.

Above you see the request for installation media for SAP MaxDB - the installation of this database will be executed by SAPinst (SAP HANA and Oracle DB need to be installed before starting SAPinst).

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. We recommend that after installation, you set individual passwords for the different users.

On operating system Windows you can decide 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: The default for this password is the master password you chose previously. You can specify a different password for these users.

On the upper screen shot in the figure above you find the setting of the SID for the DB system (DBSID).

The lower screen above asks you to enter the path to the kernel archives that should be used for the installation. 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.

A Prerequisite Check is always performed, its results shown.

There is the option to upgrade an existing SAP Host Agent using a newer archive, also you are asked to decide on the location of the SAP MaxDB Client Software.

Later in this course, you will use the user control for SAP MaxDB.

Some important parameters for the database can be set during installation.

Please adapt the location and size of the Log and Data Volumes to your needs.

The figure above shows the selection screen for setting the instance numbers for the Primary Application Server (PAS) instance and the Central Services (SCS) instance of your 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.

As you can see on the screen above, certain number are already in use: 80 and 81. 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.

On the screen above, you can also decide on how the number of Java server nodes will be determined. When set to Manually, you can set the number of Java server nodes on this screen.

The default value of the Internal Java message server port is determined by your previous entry for the Central Services Instance. The internal port number for the Java message server is 39##, where ## is the value that you specified for the SCS instance. 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.

When installing an SAP Solution Manager 7.2 Java system, you are required to connect it to the SAP Solution Manager ABAP system. For this, you need to select Use External ABAP System.

When installing an SAP Solution Manager 7.2 Java system, you are required to connect it to the SAP Solution Manager ABAP system. For this, you need to provide connection data, as shown above and below. Remember that the passwords you provide here are passwords for users in another SAP system, the SAP Solution Manager ABAP system.

When installing a new SAP system, you are offered to connect it to an already existing System Landscape Directory (SLD) or to set up this connection at a later time — in which case you choose No SLD destination on the screen shown above.

Decide for the cryptographic key – but beware of legal restrictions!

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 decide on including an SAP Web Dispatcher into the SCS instance of your SAP Solution Manager Java system.

If you decide to include SAP Web Dispatcher into the SCS instance of your SAP Solution Manager Java system, you can provide some central parameters on the screen shown above.

If you decide to create own applications for the SAP Solution Manager Java system, you might want to prepare the SAP Solution Manager Java system to be installed for NWDI (SAP NetWeaver Development Infrastructure) integration. If you choose this option, all installed software components archives will be copied the transport directory, for later use in the NWDI.

The screen above shows the first part of 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.

Congratulations: The installation of your SAP Solution Manager Java system finished successfully!