Installation Guide | PUBLIC Software Provisioning Manager 2.0 SP09 Document Version: 1.9.0 – 2021-06-21
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 This Guide is Valid for SAP Systems based on the Following SAP Product Versions: - SAP BW/4HANA 1.0 Support Release 1 company. All rights reserved. affiliate
THE BEST RUN 2021 SAP SE or an SAP © Content
1 About this Document - SAP Host Agent as a Separate Installation - Using Software Provisioning Manager 2.0...... 4 1.1 About Software Provisioning Manager 2.0...... 4 SAP Products Supported by Software Provisioning Manager 2.0...... 6
2 Accessing the SAP Online Documentation...... 7
3 Installing the SAP Host Agent Separately...... 8 3.1 Preparation for IBM i...... 11 Checking the Transport Directory...... 11 Qp2Term, Qp2Shell, and the Portable Application Solution Environment...... 12 Installing the Qshell...... 13 Checking and Adjusting Operating System Values...... 13 Adjusting Startup Program QSTRUP...... 18 Adding a User ASP...... 19 Configuring TCP/IP...... 21 Adjusting the Relational Database Name...... 28 Installing English as a Secondary Language...... 29 Preparing the SAP Installation User on IBM i...... 29 Enable the User QSECOFR...... 31 Distribution of Libraries on ASPs...... 31 3.2 Downloading and Extracting the Software Provisioning Manager 2.0 Archive...... 32 3.3 Downloading the SAPHOSTAGENT Archive...... 34 3.4 Copying the Installation Media Manually to Your IBM i...... 34 3.5 Prerequisites for Running the Installer...... 36 3.6 Running the Installer...... 38 Useful Information about the Installer...... 40
4 Uninstalling the SAP Host Agent Separately...... 43
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 2 PUBLIC Content Document History
Note
Before you start reading, make sure you have the latest version of this installation guide, which is available at: https://help.sap.com/viewer/swpm20guides
The following table provides an overview on the most important document changes:
Version Date Description
1.9.0 2021-06-21 Updated version for Software Provisioning Manager 2.0 SP09 (SL Toolset 1.0 SP32)
1.8.0 2021-02-15 Updated version for Software Provisioning Manager 2.0 SP08 (SL Toolset 1.0 SP31)
1.7.0 2020-10-05 Updated version for Software Provisioning Manager 2.0 SP07 (SL Toolset 1.0 SP30)
1.6.0 2020-06-08 Updated version for Software Provisioning Manager 2.0 SP06 (SL Toolset 1.0 SP29)
1.5.0 2020-01-20 Updated version for Software Provisioning Manager 2.0 SP05 (SL Toolset 1.0 SP28)
1.4.0 2019-09-16 Updated version for Software Provisioning Manager 2.0 SP04 (SL Toolset 1.0 SP27)
1.3.0 2019-05-27 Updated version for Software Provisioning Manager 2.0 SP03 (SL Toolset 1.0 SP26)
1.2.0 2019-01-21 Updated version for Software Provisioning Manager 2.0 SP02 (SL Toolset 1.0 SP25)
1.1.0 2018-09-17 Updated version for Software Provisioning Manager 2.0 SP01 (SL Toolset 1.0 SP24)
1.0.0 2018-04-23 Initial version for Software Provisioning Manager 2.0 SP00 (SL Toolset 1.0 SP23)
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Document History PUBLIC 3 1 About this Document - SAP Host Agent as a Separate Installation - Using Software Provisioning Manager 2.0
Under certain circumstances you need to install SAP Host Agent separately. Apart from performing this installation manually, you can also do this using Software Provisioning Manager 2.0 - the “installer” for short.
SAP Host Agent is an agent that can accomplish several life-cycle management tasks, such as operating system monitoring, database monitoring, system instance control and provisioning. When you install a new SAP system or instance, the SAP Host Agent is in most cases installed automatically on the SAP system or instance host.
It is only required to install the SAP Host Agent separately if there is no SAP system or instance on the host.
Section Installing the SAP Host Agent Separately [page 8] describes how to perform the installation using Software Provisioning Manager 2.0 SP09.
Software Provisioning Manager 2.0 SP09 (the “installer” for short) is part of Software Logistics Toolset 1.0 SP32. For more information about supported SAP system releases, see SAP Products Supported by Software Provisioning Manager 2.0 [page 6]. For information about supported operating system and database platforms, see the Product Availability Matrix at https://support.sap.com/pam .
Installing the SAP Host Agent Without Using Software Provisioning Manager
You can also install SAP Host Agent by downloading the SAPHOSTAGENT.SAR archive and running the installation from the command line. For more information, see the SAP Host Agent documentation at:
For more information, see the SAP Online Documentation [page 7] at: Solution Life Cycle Management SAP Host Agent SAP Host Agent Installation Installing SAP Host Agent Manually
1.1 About Software Provisioning Manager 2.0
Software Provisioning Manager 2.0 is the new release of Software Provisioning Manager 1.0. Software Provisioning Manager as such is the successor of the product- and release-specific delivery of provisioning tools, such as SAPinst and R3setup.
Make sure that you read the most recent version of SAP Note 2568783 (Release Note for Software Provisioning Manager 2.0).
Before you run Software Provisioning Manager 2.0, we recommend that you always download the latest version of it. Software Provisioning Manager 2.0 is - as Software Provisioning Manager 1.0 - part of the Software Logistics Toolset 1.0 (“SL Toolset” for short) which is quarterly shipped. This way, you automatically get the
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 About this Document - SAP Host Agent as a Separate Installation - Using Software 4 PUBLIC Provisioning Manager 2.0 latest fixes and supported processes. For more information about Software Provisioning Manager 2.0 as well as products and releases supported by it, see SAP Note 2568783 and http://scn.sap.com/docs/DOC-30236 .
Software Provisioning Manager 2.0 Versus Software Provisioning Manager 1.0
The Software Provisioning Manager 2.0 SP09 exists in parallel to Software Provisioning Manager 1.0 SP32. Both Software Provisioning Manager versions are part of Software Logistics Toolset 1.0 SP 32. However, they cover system provisioning for different product versions. The decision matrix is as follows:
● Software Provisioning Manager 2.0 is used for: ○ Installation, system copy, and system rename of ABAP single stack systems on SAP HANA 2.0 database, based on the following products: ○ SAP BW/4HANA 1.0 Support Release 1 ○ SAP Web Dispatcher installation and rename.
Note
For SAP Web Dispatcher, you can either use Software Provisioning Manager 2.0 or Software Provisioning Manager 1.0.
○ SAP Host Agent standalone installation.
Note
For SAP Host Agent standalone installation, you can either use Software Provisioning Manager 2.0 or Software Provisioning Manager 1.0.
● Software Provisioning Manager 1.0 is used for: ○ Installation, system copy, system rename of SAP Solution Manager 7.X and Diagnostics Agent. ○ Installation of standalone engines and clients.
Note
For SAP Web Dispatcher or SAP Host Agent standalone installation, you can either use Software Provisioning Manager 1.0 or Software Provisioning Manager 2.0.
○ Installation, system copy, system rename, and dual-stack split of SAP systems whose database is not SAP HANA. ○ Installation, system copy, and system rename of Dual-stack and Java single stack systems. ○ Installation, system copy, and system rename of ABAP single stack systems whose database is SAP HANA database, but whose release is one of the following: ○ SAP BW/4HANA 1.0 or lower ○ SAP S/4HANA 1709 or lower ○ SAP NetWeaver AS for ABAP 7.52 or lower
For more information, see https://blogs.sap.com/2018/05/15/software-provisioning-manager-1.0-vs.- software-provisioning-manager-2.0/ .
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 About this Document - SAP Host Agent as a Separate Installation - Using Software Provisioning Manager 2.0 PUBLIC 5 Naming Conventions
“SAPinst” has been renamed to “Software Provisioning Manager” (“installer” for short), but the terms “SAPinst” and “sapinst” are still used in:
● The name of the technical framework of Software Provisioning Manager. For more information about the SAPinst Framework, see SAP Note 2393060 . ● Texts and screen elements in the Software Provisioning Manager GUI ● Names of executables, for example sapinst ● Names of command line parameters, for example SAPINST_HTTPS_PORT ● Names of operating system user groups, such as the additional group sapinst
In this documentation, we generally refer to Software Provisioning Manager as the “installer”. We only use the term “Software Provisioning Manager” if this is required for technical reasons, and “Software Provisioning Manager 2.0” if there is a significant difference compared to “Software Provisioning Manager 1.0”.
1.1.1 SAP Products Supported by Software Provisioning Manager 2.0
Here you can find the list of SAP products supported by Software Provisioning Manager 2.0.
SAP Product Based on
SAP BW/4HANA 1.0 Support Release 1 SAP NetWeaver 7.5
More Information
For more information about recommended application server platforms, see SAP Note 2620910 .
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 About this Document - SAP Host Agent as a Separate Installation - Using Software 6 PUBLIC Provisioning Manager 2.0 2 Accessing the SAP Online Documentation
This section contains the paths for the product-specific online documentation referenced from this documentation.
The references to the SAP Online Documentation in this guide always refer to the following on the SAP Help Portal:
● SAP systems based on SAP S/4HANA Foundation 2020 (“ABAP Platform 2020” for short): https://help.sap.com/s4hana <2020 Latest> Discover Product Assistance SAP S/4HANA Enterprise Technology ABAP Platform ● SAP systems based on SAP S/4HANA Foundation 1909 (“ABAP Platform 1909” for short): https://help.sap.com/s4hana <1909 Latest> Discover Product Assistance SAP S/4HANA Enterprise Technology ABAP Platform ● SAP systems based on foundation on ABAP Platform 1809, version for SAP HANA (“ABAP Platform 1809” for short): https://help.sap.com/s4hana <1809 Latest> Discover Product Assistance SAP S/4HANA Enterprise Technology ABAP Platform ● SAP systems based on SAP BW/4HANA 2.0: https://help.sap.com/viewer/p/SAP_BW4HANA 2.0
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Accessing the SAP Online Documentation PUBLIC 7 3 Installing the SAP Host Agent Separately
This procedure tells you how to install an SAP Host Agent separately.
Context
The SAP Host Agent is installed automatically during the installation of new SAP instances with SAP kernel 7.20 or higher (integrated installation). This procedure is only for hosts with no SAP Host Agent running on them, due to the following reasons:
● There is no SAP system or instance on the host. ● The SAP system or instance running on the host has a kernel release lower than SAP kernel 7.20 and the host does not yet have an SAP Host Agent. ● You have upgraded your SAP system to a release with a kernel release lower than SAP kernel 7.20 and the host of the upgraded system or instance does not yet have an SAP Host Agent.
SAP Host Agent has the following executable programs and services:
● The SAPHostExec service ● The sapstartsrv service SAPHostControl ● The operating system collector saposcol ● The DB4STATS program and command ● The SAP ILE daemon
Note
The installed programs are automatically started when the host is booted.
Note
On IBM i, the installed programs are started by the auto-start job (ADDAJE)SAPINIT in subsystem QUSRWRK, which was created during the installation. The subsystem QUSRWRK automatically restarts after every initial program load (IPL).
Note
On IBM i, the installed programs are started by the auto-start job (ADDAJE)SAPINIT in subsystem QUSRWRK, which was created during the installation. The subsystem QUSRWRK automatically restarts after every initial program load (IPL).
Caution
You must leave the subsystem QUSRWRK in the program QSTRUP (or whatever name you have chosen for your current startup program). This is the default. Otherwise, the SAP Host Agent does not work.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 8 PUBLIC Installing the SAP Host Agent Separately Caution
You must leave the subsystem QUSRWRK in the program QSTRUP (or whatever name you have chosen for your current startup program). This is the default. Otherwise, the SAP Host Agent does not work.
The following procedure describes the steps you have to perform on the host where you install the SAP Host Agent separately.
Procedure
1. Set up the required file system for the SAP Host Agent and make sure that the required disk space is available for the directories to be created during the installation.
The SAP Host Agent has only local directories as shown in the following figure:
Directory Structure for the SAP Host Agent
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 9 Directories Description Required Disk Space
/usr/sap/hostctrl Contains the following directories: 100 MB
○ exe Contains the profile host_profile ○ work Working directory of the SAP Host Agent
2. Complete the preparation for IBM i [page 11]. 3. Download and unpack the Software Provisioning Manager 2.0 archive on the host where you want to install the SAP Host Agent as described in Downloading and Extracting the Software Provisioning Manager 2.0 Archive [page 32] . 4. Make the latest patch level of the SAPHOSTAGENT
For more information, see Downloading the SAPHOSTAGENT Archive [page 34].
5. To install the SAP Host Agent, you start the installer [page 38] and choose Generic Options SAP HANA Database Preparations SAP Host Agent on the Welcome screen of the installer. 6. Follow the instructions on the installer screens and enter the required parameters. 7. When the installation has finished, the installer shows the message: Execution of SAP Host Agent has completed. Post-Installation 8. Check that the SAP Host Agent is installed and running by entering this command: /usr/sap/hostctrl/exe/saphostexec –status If the SAP Host Agent is running, you see something like this: saphostexec running (pid = 21942) 9. If the SAP Host Agent is installed but not running, enter the following: /usr/sap/hostctrl/exe/saphostexec -restart 10. Check whether the installed services are available: a. Log on as user with administration rights similar to QSECOFR. b. Check whether the following services are available: ○ The control program saphostexec Note
On IBM i , check the program using the following command:
WRKJOB JOB(SAPADM/SAPHOSTEXE)
○ The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode) Note
On IBM i, check the program using the following command:
WRKJOB JOB(SAPADM/SAPSTRSRV)
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 10 PUBLIC Installing the SAP Host Agent Separately Note
On IBM i, the installed programs are started by the auto-start job (ADDAJE)SAPINIT in subsystem QUSRWRK, which was created during the installation. The subsystem QUSRWRK is automatically restarted after every IPL.
Next Steps
For more information about the SAP Host Agent, see the following documentation:
For more information, see the SAP Online Documentation [page 7] at: Application Help Function-Oriented View: English Solution Life Cycle Management SAP Host Agent
3.1 Preparation for IBM i
You have to complete the following preparations for IBM i, which are described in more detail in the linked sections:
● You check the transport directory [page 11]. ● You check Qp2Term, Qp2Shell, and the Portable Application Solution Environment [page 12]. ● You install the Qshell [page 13]. ● You check and adjust system values [page 13]. ● You adjust startup program QSTRUP [page 18]. ● You check distribution of libraries on ASPs [page 31]. ● You add a user ASP [page 19]. ● You configure TCP/IP [page 21]. ● You adjust the relational database name [page 28]. ● You install English as a secondary language [page 29]. ● You prepare the SAP installation user onIBM i [page 29]. ● You enable the user QSECOFR [page 31].
3.1.1 Checking the Transport Directory
The transport host has a directory structure that is used by the SAP transport system to store transport data and metadata. The transport system stores the change information, such as ABAP programs, data dictionary data, and customization data as well as SAP support packages from SAP Help Portal in files that are located in this directory structure. If you do not intend to use the directory structure of the system you are going to install, you need to prepare the directory structure on the transport host.
● If the directory structure already exists, you must set up security for it to allow the new system to write into the structure.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 11 ● If the directory structure does not yet exist, you must create the core directory structure and a share to make it available for other computers as well as setting the security on core directory structure.
Solution Life Cycle Management Software Logistics Change and Transport System Change and Transport System – Overview Basics of the Change and Transport System Transport Management System – Concept
Prerequisites
The transport directory /usr/sap/trans only exists on your IBM i after you successfully finished an SAP system installation. If there is already a directory /usr/sap/trans this directory should be linked to the local directory /sapmnt/trans. However, if this link points to a remote host using QFileSvr.400 (/QFileSvr.400/
Procedure
If there is a link /usr/sap/trans on your host pointing to a remote host, you have to create the following users on this remote host:
● Installation user ●
Note
When using QFileSvr.400, the passwords must be the same for each user on every host.
For more information about how to create an installation user on the remote host, see Preparing the SAP Installation User on IBM i [page 29]. For more information about how to create
3.1.2 Qp2Term, Qp2Shell, and the Portable Application Solution Environment
Use
The Portable Application Solution Environment delivers similar UNIX command line flexibility such as the Qshell. IBM PASE for i (PASE for i) is more than just a shell interpreter, it is an entire programming environment based on the AIX Application Binary Interface.
The Qp2Term program runs an interactive terminal application on the IBM i, similar to the Qshell command line.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 12 PUBLIC Installing the SAP Host Agent Separately The Qp2Shell programs allow you to execute a shell script or a PASE for i application. Qshell accomplishes these features by a command wrapper that either starts the Qshell command line, or executes scripts non interactively.
You call the Qp2Term and Qp2Shell programs using command CALL mechanism.
Recommendation
We recommend that you use Qp2Term instead of QShell.
Procedure
If not already installed, install option 33 of the license program 57nnSS1, the Portable Application Solution Environment. For more information about Qp2Term, Qp2Shell and installing PASE for i, see the documentation in the IBM Knowledge Center.
3.1.3 Installing the Qshell
Use
You must install the Qshell on your IBM i. This gives you greater flexibility in dealing with stream files because you can use a large set of utilities that are common on UNIX systems, for example, grep, tail, or ls.
In addition, Qshell is compatible with ksh scripts in UNIX.
Procedure
Install option 30 of the Qshell (license program 57nnSS1).
Note
For more information about Qshell, see the IBM documentation.
3.1.4 Checking and Adjusting Operating System Values
Use
To allow the SAP system to run optimally on IBM i, you have to adjust a number of operating system values.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 13 Prerequisites
● You have entered the following command to switch on work control block compression: CHGIPLA CPRJOBTBL(*ALL) This allows work control block space to be reused. ● The recommendations given below for system values QACTJOB, QTOTJOB, QADLACTJ, and QADLTOTJ assume that only the SAP system is running on the IBM i. If you are also running other applications, you might need to preallocate more jobs. The values QACTJOB and QTOTJOB are used for initial space allocation at initial program load (IPL) time for the number of active jobs and the total number of jobs that are in the system at any one time. If the allocated number of active or total jobs is reached, the system values QADLACTJ and QADLTOTJ determine how many additional jobs are to have space allocated. ● Check and adapt your TCP/IP configuration on IBM i. For more information, see SAP Note 92589 .
Caution
Do not forget to perform an IPL after any change. Otherwise, your changes do not work.
● You have applied all installed PTFs on your IBM i. To check this, enter the following command: DSPPTF PTFs with the state Permanently applied, Temporarily applied or Superseded are integrated in the system or are superseded by a newer PTF. PTFs with another state such as Not applied, Save file only, Damaged or Cover letter only are not currently active.
Recommendation
We recommend that you install all required PTFs. They should be applied and active.
Procedure
● To display all system values, enter the following command: WRKSYSVAL SYSVAL(*ALL) OUTPUT(*PRINT) ● To display or change individual system values, enter the following command: WRKSYSVAL SYSVAL(
Note
To avoid having to run an initial program load (IPL) several times, we recommend that you delay the IPL until you have made all the necessary changes to the system values and, if necessary, have added a user ASP [page 19].
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 14 PUBLIC Installing the SAP Host Agent Separately Checking and Adjusting Operating System Values
System Value Recommended Value Description
QMCHPOOL 10–15% of the entire main storage is as The fault rate in the *MACHINE pool should be as signed to the machine pool low as possible, usually, lower than 5 (see SAP Note 49201 ); otherwise, the pool must be in creased. A change to this system value takes ef fect immediately.
QACTJOB 1000 Set system value QACTJOB to a value close to the number of jobs typically on your system. (To find out the number of jobs, enter the command WRKACTJOB. For a two-tier system, this is about 1000).
QTOTJOB 2000 Set system value QTOTJOB to 2000. When you have worked with the SAP system for a while, ad just this value to the value you typically see in the field Jobs in system on the WRKSYSSTS com mand.
QADLACTJ 500 Set system value QADLACTJ to 500 and system value QADLTOTJ to 1000. and 1000
QADLTOTJ
QSECURITY 30 or 40 System value QSECURITY controls the level of se curity enforced on your system. Set QSECURITY to at least 30 to ensure object security for the SAP objects to be installed.
Security levels 10 and 20 are theoretically possi ble. However, we do not recommend that you use either of these values. Security level 10 provides neither password nor object protection. Security level 20 provides no object protection.
To activate this system value, you must perform an initial program load (IPL).
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 15 System Value Recommended Value Description
QCTLSBSD QCTL When you start your IBM i, the program specified in system value QSTRUPPGM (the default is QSTRUP) is called. This startup program is re sponsible for starting the subsystems. When this startup program runs, system value QCTLSBSD is queried. The specifications made for this value determine whether subsystem QBASE or subsys tems QCTL,QINTER,QBATCH,QSPL,QCMN, and QSERVER are started.
Two settings are possible for system value QCTLSBSD (controlling subsystem):
● QBASE The controlling subsystem is QBASE. Subsys tem QBASE is started. ● QCTL The controlling subsystem is QCTL. Subsys tems QCTL,QINTER,QBATCH,QSPL,QCMN,QSERV ER are started. Your change is activated the next time the IBM i is started. To activate the subsystems, you have to restart the IBM i.
QDATE Check the system date and adjust if necessary. (The date format is determined by system value QDATFMT.)
QTIME Check the system time and adjust it if necessary.
QJOBMSGQFL *WRAP or *PRTWRAP System value QJOBMSGQFL allows you to specify how you wish the job message queue to be han dled if it overflows. The default value is *NOWRAP. If this value is set, the IBM i sends a message when the queue is full and ends the job that is currently running. When an SAP system is installed, a large amount of information is sent to the job message queue. For this reason, system value QJOBMSGQFL is automatically changed to *WRAP during installation. If the queue becomes full, the oldest entries are deleted and the current job is not interrupted. Once the installation is complete, the system value is automatically re turned to its original value.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 16 PUBLIC Installing the SAP Host Agent Separately System Value Recommended Value Description
QPFRADJ 0 If you have adjusted the size of the IBM i pools as described in SAP Note 49201 , you have to set the system value QPFRADJ to 0. This deactivates automatic performance adjustment and prevents your settings from being lost after an IPL.
QSTRUPPGM To cause your adjusted startup program to be started after an IPL, change Startup program to QSTRUP and Library to QGPL.
QAUTOCFG 1 To allow device descriptions to be configured au tomatically, set system value QAUTOCFG to 1.
QINACTITV *NONE IBM i V7R3 and higher: When running the SWPM the system value QINACTIV must be set to *NONE. Otherwise, the installation is maybe sud denly ended by the operating system without an error message in the installation logs. For more information, see SAP Note 2672715 .
QBASACTLVL When installing an SAP system, the value QBASACTLVL is the activity level of the base stor needs to be increased. Use the following age pool. This value indicates how many system formulas to calculate the increase: and user threads can compete at the same time for storage in the base storage pool. This pool is specified in the subsystem descriptions as *BASE. QBASACTLVL depends on the types of jobs run in this storage pool. The lower limit for QBASACTLVL is 1.
Note: This value does not affect only SAP work processes but also processes and threads that belong to other applications running on your sys tem.
Note
In the past the Max Act value had an influ- ence on the database optimizer, but this has changed.
Caution
You should not set the system variable QIBM_PASE_CCSID. Do not leave this variable empty. Make sure that QIBM_PASE_CCSID is deleted at least for the time while you are installing your SAP system using the following command:
RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)
Changing TCP buffer size:
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 17 1. To change the following values, enter the following command: CHGTCPA TCPRCVBUF(1048576) TCPSNDBUF(1048576) 2. To activate the changes, restart TCP/IP by entering the following commands: ENDTCP STRTCP or perform an IPL.
For more information, see SAP Note 484548 and 92589 .
Changing Expert Cache
Activate the expert cache for the storage pool in which the subsystem of the SAP system runs. Usually, this is the *BASE pool.
To activate the expert cache, enter the following command:
WRKSYSSTS
This will display the storage pools. Now change the default value in the column for the paging option from *FIXED to *CALC. The paging option defines whether the system is to dynamically adjust the paging characteristics of the storage pool to achieve optimum performance in each case. *CALC can be used to improve the performance of the database read accesses and the database write accesses so that larger blocks can be read to the main storage and the changed data does not have to be removed from the main storage.
Result
You have made the necessary adjustments to IBM i values to enable the SAP system to run correctly on IBM i.
Note
When a new SAP system is created a special entry is made automatically in the System Reply List. These entries make sure that changes of tables attributes work without problems. Do not change or delete this entry after the installation!
System Reply List Entries
Sequence Reply List Entries Message ID Reply
3201 CPA32B2 I
3.1.5 Adjusting Startup Program QSTRUP
Use
When you use the operating system IBM i to start a partition or a server, the system automatically executes a startup program that is used to start services, servers, and subsystems. The customers can change the startup program that is delivered with the operating system.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 18 PUBLIC Installing the SAP Host Agent Separately Recommendation
We highly recommend to start the services, servers and subsystems in the order shown below.
Procedure
To ensure that SAP Host Agent and SAP systems can start and work correctly, the following functions must be executed by the startup program:
1. Automatic start of TCP/IP 2. Automatic start of the host servers 3. Start of the EDRSQL server 4. Only for Java systems: Start of the DDM-TCP/IP server 5. Automatic creation of directory entries under /QFileSvr.400 6. Start of the subsystem QUSRWRK
For more information about how to setup the startup program for SAP, see SAP Note 1703667 .
3.1.6 Adding a User ASP
Use
If you decide to store the database libraries and journal receiver libraries in separate auxiliary storage pools (ASPs), make sure that you follow these guidelines:
1. The disk units in the ASP that is holding the journal receiver libraries must be protected by mirrored protection or a different parity set than the disk units in the ASP that is holding the database libraries. 2. For performance reasons, the ASP that is holding the journal receiver libraries should have a minimum of three disk arms. 3. The ASP that is holding the journal receivers should be large enough to hold all journal receivers that are generated while your SAP system is running, until the receivers can be detached, saved, and deleted. If the journal receivers grow too quickly and the ASP is full, some data might overflow into the system ASP. In this state, you can no longer perform data recovery after disk failures that result in the loss of the system ASP.
Before you can specify a different ASP during the SAP installation, you must configure the ASP in IBM i and assign disk units to it. The procedure consists of two steps:
1. You check if a user ASP with sufficient space has been set up. 2. You add or extend a user ASP if required.
Procedure
Checking the User ASP
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 19 1. Enter STRSST (Start System Service Tools). 2. Sign on with a valid service tools user ID and password. 3. Enter option 3 (Work with disk units). 4. Enter option 2 (Work with disk configuration). 5. Enter option 1 (Display disk configuration). 6. Enter option 2 (Display disk configuration capacity). You can see whether a user ASP exists and if it contains enough disk units. On the Display disk configuration screen, you can also use option 5 (Display device parity status) to verify that your user ASP is in a separate parity set.
Note
In early releases of IBM i, user ASPs could only contain objects of type journal receiver or save file. The libraries to address these objects where kept in the system ASP. If an existing user ASP contains journal receivers or save files, while the library that contains these objects is in the system ASP, you cannot create additional libraries in this user ASP and the installation fails. If you have sufficient disk space, we recommend that you work around this problem by adding a second user ASP (for example, ASP 3). The alternative would be to remove the old journal receivers or save files from the user ASP, or to create the SAP journal receivers in the system ASP. For more information, see the IBM i documentation Backup and Recovery (SC41-5304).
Adding a User ASP
1. Perform a manual initial program load (IPL) of your IBM i. ○ Set the mode to manual on the control panel ○ Enter the following command: PWRDWNSYS *IMMED RESTART(*YES) 2. Enter option 3 (Use Dedicated Service Tools (DST)) from the menu that appears. 3. Sign on by entering your DST user and password. 4. Enter option 4 (Work with disk units). 5. Enter option 1 (Work with disk configuration). 6. Enter option 3 (Work with ASP configuration). 7. Enter option 6 (Move units from one ASP to another). 8. Specify the ASP to which you wish to move specific units by entering the number of the ASP next to the relevant unit in the column New ASP. 9. Choose ENTER . 10. In the next screen, choose ENTER to confirm that you want to continue. The Confirm Move of Units screen appears. 11. To confirm your choices, choose ENTER .
Note
Moving units takes several minutes.
12. Continue the procedure and complete the IPL. 13. Switch back to normal mode.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 20 PUBLIC Installing the SAP Host Agent Separately 3.1.7 Configuring TCP/IP
Use
This section describes how to integrate IBM i into your TCP/IP network.
Prerequisites
Before configuring TCP/IP, you must do the following:
● Make sure that you have the following information: ○ The interface of your IBM i to which the Local Area Network is attached ○ The IP addresses of your IBM i, subnet mask, and router or Gateway ○ The local domain name ○ The IBM i host name ● Decide on your IBM i host name. The host name cannot be longer than eight characters although SAP allows 13 characters as of Release 4.6. For more information, see SAP Note 611361 .
Note
The TCP/IP configuration on IBM i is case sensitive. Do not enter your host name once in uppercase and then in lowercase characters. It is important that you enclose your host name entry in single quotation marks. Otherwise, the IBM i interprets the characters as uppercase characters.
Procedure
Note
An IP address is a unique address in a TCP/IP network for a particular IBM i. A subnet mask is a mask used to divide a single network address into multiple logical networks.
1. To change the name of the computer, enter the command chgneta and prompt F4 . You must then enter the following information and choose ENTER : ○ System name ○ Local network ID ○ Default local location name
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 21 The following screen appears:
2. To set up the description line, enter the command WRKHDWRSC TYPE(*CMN) and proceed as follows: 1. On the Work with Communication Resources screen, enter option 5 (Work with configuration descriptions) for the port and choose ENTER . 2. On the Work with Configurations Description screen, enter option 1 (Create) to enter the description gigaline or ethline and choose ENTER . On the following screen, enter the line speed and duplex and then press F10 and page down two screens.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 22 PUBLIC Installing the SAP Host Agent Separately On the Create Line Desc (Ethernet) (CRTLINETH) screen, make sure the autocreate controller is set to *yes.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 23 3. To call the TCP/IP configuration menu, enter the command CFGTCP and proceed as follows: 1. To work with interfaces, enter option 1 (Work with TCP/IP interfaces).
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 24 PUBLIC Installing the SAP Host Agent Separately The following screen appears:
You need at least two entries: one for the loopback entry and one for the IP address of your IBM i. The loopback address always takes the IP address 127.0.0.1, subnet mask 255.0.0.0 and line description *LOOPBACK. To add an entry, enter option 1 (ADD) and choose ENTER . Add entries for the first three fields and accept the default values for the other fields. 2. To work with routes, enter option 2 (Work with TCP/IP routes).
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 25 The following screen appears:
If the route to the remote host, in this case the PC workstation, is through a Gateway or if the remote host resides in a different network or subnetwork to the local host, you need to configure a route. 3. To change the domain information, enter option 12 (Change TCP/IP domain information).
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 26 PUBLIC Installing the SAP Host Agent Separately The following screen appears:
Note
It is important that you enclose your host name entry in single quotation marks. If you do not, the IBM i interprets the characters as uppercase characters.
If you have one or more remote name servers, you need to define the IP address here. Note that the Host name server priority must be set to *LOCAL.
Testing the TCP/IP Connection
Before proceeding with the SAP installation (that is, the installation of the executable programs), check that this TCP/IP connection has been set up correctly. To do so, enter the command ping (Network Connection) specifying your own system as Remote system. Do this twice, once specifying only
Example
In this example we assume that the host name is as0008 and the domain name is wdf.sap.corp. In this case, your entries are the following:
● ping 'as0008'
● ping 'as0008.wdf.sap.corp'
After installing the SAP system kernel, check the TCP/IP connection again with the command:
WRKLNK '/QFileSvr.400/
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 27 Your host name should be displayed under Object link, for example, as0008 for the host in the example given above.
For more information about TCP/IP configuration, see the IBM documentation in the IBM Knowledge Center.
Result
The IBM i is integrated into your TCP/IP network.
3.1.8 Adjusting the Relational Database Name
Use
You use the following procedure to adjust the local relational database name (RDB name) so it is the same as the TCP/IP host name.
Note
The *Local database name must match the TCP/IP host name for the SAP system to work properly.
Procedure
1. Log on to your database host as user QSECOFR. 2. To display your TCP/IP host name, enter the following command and press F4 : CHGTCPDMN 3. Search for the contents of HOSTNAME. This is your TCP/IP host name. 4. Before you can adjust the local RDB name, you have to check if the entry remote location equals *Local exists. To do this, enter the following command: WRKRDBDIRE 5. Depending on the outcome, proceed as follows: ○ If an entry for RDB name exists and you want to adjust the name to the TCP/IP host name
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 28 PUBLIC Installing the SAP Host Agent Separately To do this, enter the following command: ADDRDBDIRE RDB(
3.1.9 Installing English as a Secondary Language
Use
On every IBM i where English is not the primary language, you must install English as the secondary language library. This is necessary for SAP to be able to provide support.
Note
To check if English is already installed on your IBM i as a secondary language, enter GO LICPGM on the IBM i command line and use option 20. If one of the following secondary language libraries is displayed, you have already installed English as a secondary language library:
QSYS2924, QSYS2938, QSYS2959, or QSYS2984.
Procedure
1. On the IBM i command line, enter GO LICPGM 2. Enter option 21 (install secondary languages). 3. Enter option 1 to select any of the following libraries: QSYS2924, QSYS2938, QSYS2959, or QSYS2984.
3.1.10 Preparing the SAP Installation User on IBM i
For running the installer, you must create the SAP installtion user profile on the IBM i host.
The following requirement applies:
● The SAP installation user profile on IBM i must have user class *SECOFR and all special authorities that belong to the user QSECOFR.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 29 Procedure
Note
The user name SAPIUSR and the password SAP are used as examples. You can use a different user name for the SAP installation user. Make sure you do not user SAP as the password as this is not secure.
To create the SAP installation user profile, enter the following command:
CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('SAP installation user') SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)
Caution
You should not set the system variable QIBM_PASE_CCSID. Do not leave this variable empty. Make sure that QIBM_PASE_CCSID is deleted at least for the time while you are installing your SAP system using the following command:
RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)
Note
In previous releases, we recommended that you create the user SAPINST on IBM i to install the SAP system. In the current release, a group SAPINST is created generically on all platforms and is used for the installation of the SAP system. If the user SAPINST already exists on your system, you must delete this user. If you do not want to delete this user for any reason, you must add to the user profile SAPINST the feature of a group by adding SAPINST to the group of a SAP installation user profile such as SAPIUSR. To do this, use the following command:
CHGUSRPRF USRPRF(SAPIUSR) GRPPRF(SAPINST)
Now the user SAPINST can also be used as a group by the installer.
Note
If you have already an old SAP installation user and you want to make sure this user is configured correctly for your next SAP system installation, enter the following command:
CHGUSRPRF USRPRF(SAPIUSR) USRCLS(*SECOFR) TEXT('SAP installation user') SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)
Note
In a distributed environment, the SAP installation user must have the same name and password on all hosts so that the required remote access permissions are available. For example, the profile directory on the global host should be accessible to the SAP installation user of a remote additional application server instance.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 30 PUBLIC Installing the SAP Host Agent Separately 3.1.11 Enable the User QSECOFR
The user QSECOFR is the standard administrator user on IBM i. This user has the most authority. For running the installer on IBM i, the user QSECOFR must be enabled. Although for running the installer you only require the installation user, the SAP kernel tools on IBM i need some adopted permissions from the user QSECOFR. If the user QSECOFR is disabled this will lead to errors when SAP kernel tools such as CRTR3INST are called.
Note
If the SAP Host Agent release 7.21, patch level 43 and higher is used, the QSECOFR can be disabled. Whether the QSECOFR needs to be disabled depends on the customer's security concept. As of SAP Host Agent release 7.21, patch level 43, the installation no longer requires an enabled QSECOFR.
For more information, see SAP Note 1031096 - Installing Package SAPHOSTAGENT.
Procedure
1. To check the status of the user profile QSECOFR use the following command using your installation user: DSPUSRPRF USRPRF(QSECOFR) 2. To enable the user QSECOFR use the following command using your installation user: CHGUSRPRF USRPRF(QSECOFR) STATUS(*ENABLED)
Note
In a distributed environment, the installation user must have the same name and password on all hosts so that the required remote access permissions are available. For example, the profile directory on the global host should be accessible to the installation user of a remote additional application server instance.
Recommendation
Check also if the password of the user QSECOFR is expired. To do this, login as QSECOFR. When the password is already expired you will be asked for a new password. Set a new password and the password of QSECOFR is then no longer expired.
Only when the password of the QSECOFR is not expired the installation procedure will finish successfully.
3.1.12 Distribution of Libraries on ASPs
Disk units that are attached to an IBM i server are combined into one or multiple auxiliary storage pools (ASPs). You always have an ASP 1, also known as system ASP. Optionally, you can configure one or multiple additional ASPs. These are called user ASPs.
Before you run the installer to install your SAP system, you must decide on the following:
● Which ASP you want to use to install new libraries for ABAP
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 31 ● How you want to distribute the libraries that hold the SAP system data on ASPs
For a production system, we recommend that you use two different ASPs for the database library and database journal receiver library. Make sure that the database library and the database journal receiver library are located on separate physical disks and not merely on different virtual ASPs that reside on the same physical disk. This is necessary to prevent that a single hardware failure of a disk unit destroys both the database and the database journal receiver. For test and quality assurance systems, both the database and journal receiver libraries can be installed on the same ASP.
Note
● The database and journal receiver libraries can be installed only in the same ASP group. ● The database library can only be installed on the system ASP (1), user ASP (2-32) or on a primary independent ASP. ● The journal receiver library can be installed on a system ASP (1), user ASP (2-32), on a primary independent ASP or on a secondary independent ASP.
3.2 Downloading and Extracting the Software Provisioning Manager 2.0 Archive
You must always download and extract the Software Provisioning Manager 2.0 archive from the SAP Software Download Center because you must use the latest version.
Context
You require the SAPCAR tool to be able to unpack and verify software component archives (*.SAR files). *.SAR is the format of software lifecycle media and tools that you can download from the SAP Software Download Center. For more information about how to get this tool, see the Procedure section below.
Procedure
1. Download the latest version of the Software Provisioning Manager 2.0 archive SWPM20SP
https://support.sap.com/sltoolset System Provisioning Download Software Provisioning Manager 2. We recommend that you copy the Software Provisioning Manager 2.0 archive to the IFS of the IBM i host. 3. If you did not do so already, make sure you have configured your TCP/IP as described in SAP Note 92589 . Do not forget afterwards to perform an IPL to make the change effective. Otherwise, the file copying is very slow from your local Windows optical media drive or Windows file system to the IFS on your IBM i.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 32 PUBLIC Installing the SAP Host Agent Separately 4. Make sure that you use the latest version of the SAPCAR tool when manually extracting the Software Provisioning Manager archive.
Note
An older SAPCAR version might extract archive files in a wrong way and this could prevent the installer from working consistently.
Proceed as follows to get the latest version of SAPCAR:
a. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES By Category SAP TECHNOLOGY COMPONENTS SAPCAR . b. Select the archive file for your operating system and download it to an empty directory. c. Rename the executable to sapcar.exe.
For more information about SAPCAR, see SAP Note 212876 . 5. Using the latest version of SAPCAR, you can verify the signature of the downloaded SWPM20SP
1. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES and search for “sapcryptolib”. 2. Select the archive file for your operating system and download it to the same directory where you have put the SAPCAR executable. 3. Go to the SAPCAR directory and use the following command to extract the SAPCRYPTOLIB archive to the same directory where you have put the SAPCAR executable: ./sapcar –xvf sapcryptolibp_84…sar 4. Download the Certificate Revocation List from https://tcs.mysap.com/crl/ crlbag.p7s and move it to the SAPCAR directory. b. Verify the signature of the downloaded SWPM20SP
Note
Check SAP Notes 2178665 and 2568783 whether additional information is available.
Note
Make sure that all users have read permissions for the directory where you want to unpack the installer.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 33 Caution
Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not unpack it to the same folder as other installation media or archives.
3.3 Downloading the SAPHOSTAGENT Archive
Make the latest patch level of the SAPHOSTAGENT
Context
The signature of installation archives is checked automatically by the installer [page 38] during the Define Parameters phase while processing the Software Package Browser screens. The installer only accepts archives whose signature has been checked. After scanning the archives and verifying the signature, an info file is written where you can find detailed information about matching and non-matching archive files. You can access this info file by choosing the info file link in the Archive Scanning Result section of the Software Package Browser screen. The info file contains only the results of the latest archive scan. For more information, see SAP Note 2393060 .
Procedure
Make the latest patch level of the SAPHOSTAGENT
Download it from the following path: https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES By Category SAP Technology Components SAP HOST AGENT SAP HOST AGENT 7.22
Recommendation
It is highly recommended that you always choose the highest SP version of the SAPHOSTAGENT
3.4 Copying the Installation Media Manually to Your IBM i
This section describes a secure way to copy the required installation media from your Windows PC to your IBM i using OS version V7R2 and higher. To copy the media, you have to use a binary share TMPSAP. This guarantees
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 34 PUBLIC Installing the SAP Host Agent Separately that the content of the media is copied correctly from the Windows PC to your IBM i. No copied content is corrupted, and no copied files with longer file names are shortened by a converting share.
Note
This procedure should not be used on a V7R1 IBM i host. On V7R1, you must use an alternative method such as FTP.
Note
In the past, we suggested to create a binary share pointing to the root directory / on your IBM i host. We do not recommend this because it is not considered secure anymore.
Procedure
Creating a Binary Share on IBM i
If you do not already have a binary share TMPSAP on your IBM i, and you want to copy manually media from your Windows PC into the IFS of your IBM i, you have to create this share manually using the IBM Systems Director Navigator for i. To do so, proceed as follows:
1. Start the IBM Systems Director Navigator for i on your Windows PC. 2. Connect to your IBM i using My Connections. 3. To create or change the share TMPSAP, choose File Systems File Shares . 4. Right-click File Shares Open i5/OS Netserver . A new screen i5/OS Netserver appears. 5. Click the folder Shared Objects to see the shares. 6. To check the already existing share TMPSAP or create a new share TMPSAP, right-click New File .
Note
The share TMPSAP must have the access permission Read/Write and the path name should be /tmp/ SAP. If the directory /tmp/SAP does not exist directly create it manually as QSECOFR or installation user using the following command:
mkdir /tmp/SAP .
7. On the Text Conversion tab, do not select Allow file text conversion. 8. To save the share TMPSAP, press OK.
Now you have created the share TMPSAP on your IBM i.
Copying the Installation Media Manually Using the Binary Share TMPSAP
1. To open the command prompt on Windows, choose Start Run . 2. Enter cmd.exe. 3. Press OK.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 35 The command prompt appears. 4. In the command prompt, enter net use. All network connections to shared resources are displayed. 5. To change to the new network drive, enter X: in the command prompt. 6. Create the subdirectories in your IFS where you want to copy the required media. For each media, enter:
Note
You must avoid blanks or commas in the media path name.
7. Copy the installation media from your Windows drive (for example D:\) or your download directory to the IFS of your IBM i host by entering the following command:
Note
You must copy the root directory of the media respectively of the
8. For each required media, create a subdirectory and copy the required media.
3.5 Prerequisites for Running the Installer
Make sure you fulfil the following prerequisites before running the installer.
● For the SL Common GUI, make sure that the following web browser requirements are met: ○ You have one of the following supported browsers on the device where you want to run the SL Common GUI: ○ Google Chrome (recommended) ○ Mozilla Firefox ○ Microsoft Edge ○ Microsoft Internet Explorer 11 or higher. Always use the latest version of these web browsers. ○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.
Caution
The installer uses a self-signed certificate, which is used temporarily only while the installer is running. This certificate is not trusted by the browser unless it is imported manually by the user running the installer. This behavior is intentionally designed in this way because - unlike ordinary public web servers - the installer has different usage patterns. You must configure your browser do trust the self-issued certificate of the installer after carefully performing the “thumbprint” verification described in Running the Installer [page 38] . For more information about adding trusted certificates, see the documentation of your browser.
For more information about the SL Common GUI, see Useful Information about the Installer [page 40].
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 36 PUBLIC Installing the SAP Host Agent Separately ● Make sure that you have logged on to your host as an installation user with similar authorization rights to QSECOFR. For more information about how to create an installation user, see Preparing the SAP Installation User on IBM i [page 29]. ● Check the value of the temporary directory set in the environment if available:
Shell Command
Command prompt WRKENVVAR
Qp2Term echo $TEMP, echo $TMP or echo $TMPDIR
● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry. ● Each SAP instance requires a separate installation directory.
Recommendation
We recommend that you keep all installation directories until the system is completely and correctly installed.
● Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the installer executables. You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation directory as described in section Useful Information About the Installer [page 40]. ● Make sure that the following ports are not used by other processes: ○ Port 4237 is used by default as HTTPS port for communication between the installer and the SL Common GUI. If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTPS_PORT=
Example
CD DIR('
CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_HTTPS_PORT=
○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing. The filled-out evaluation form is then sent to SAP using HTTPS. If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTP_PORT=
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 37 3.6 Running the Installer
This section describes how to run the installer.
Prerequisites
For more information, see Prerequisites for Running the Installer [page 36].
Context
The installer has a web browser-based GUI named “SL Common GUI of the Software Provisioning Manager” - “SL Common GUI” for short.
This procedure describes an installation where you run the installer and use the SL Common GUI, that is you can control the processing of the installer from a browser running on any device.
For more information about the SL Common GUI, see Useful Information About the Installer [page 40].
Procedure
1. Log on to the installation host as the SAP installation user. For more information, see Preparing the SAP Installation User on IBM i [page 29].
Caution
Make sure that the installation user has not set any environment variables for a different SAP system or database or database by using the command WRKENVVAR.
If your security policy requires that the person running the installer is not allowed to know QSECOFR like credentials on the installation host, you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst1745524 . 2. Start the installer from the directory to which you unpacked the Software Provisioning Manager archive by entering the following commands:
CD DIR('
CALL PGM(QP2TERM) PARM('./sapinst')
3. The installer is starting up.
The installer now starts and waits for the connection with the SL Common GUI.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 38 PUBLIC Installing the SAP Host Agent Separately You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.
... ************************************************************************ Open your browser and paste the following URL address to access the GUI
https://[
Logon users: [
************************************************************************ ...
Note
If the host specified by
Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer [page 36]).
Caution
After opening the browser URL, make sure that the URL in the browser starts with “https://” to avoid security risks such as SSL stripping .
Before you reach the Welcome screen, your browser warns you that the certificate of the sapinst process on this computer could not be verified.
Proceed as follows to avoid security risks such as a man-in-the-middle attack:
1. Click on the certificate area on the left hand side in the address bar of your browser, and view the certificate. 2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones displayed in the console output of the installer. Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate printed in the installer console: 1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the installer has extracted itself: /home/
The SL Common GUI opens in the browser by displaying the Welcome screen. 4. On the Welcome screen, choose the required option:
To install the SAP Host Agent, choose Generic Options SAP HANA Database Preparations SAP Host Agent .
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 39 5. Choose Next.
Note
If there are errors during the self-extraction process of the installer, you can find the log file dev_selfex.out in the temporary directory.
6. Follow the instructions on the installer screens and enter the required parameters. 7. To start the installation, choose Next.
The installer starts the installation and displays the progress of the installation. When the installation has finished, the installer shows the message: Execution of
Note
This step is only required, if you did not specify during the Define Parameters phase that the group SAPINST is to be removed from the operating system users after the execution of the installer has completed.
10. For security reasons, we recommend that you delete the .sapinst directory within the home directory of the user with which you ran the installer:
/home/
3.6.1 Useful Information about the Installer
This section contains some useful technical background information about the installer and the installer GUI.
● Software Provisioning Manager (the “installer” for short) has the web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common GUI” for short. The SL Common GUI uses the SAP UI Development Toolkit for HTML5 - also known as SAPUI5 - a client- side HTML5 rendering library based on JavaScript. The benefits of this new user interface technology for the user are: ○ Zero foot print, since only a web browser is required on the client ○ New controls and functionality, for example, view logs in web browser. As of version 2.0 SP01 Patch Level (PL) 5, Software Provisioning Manager comes with a new look and feel of the SL Common GUI. For more information, see https://blogs.sap.com/2018/11/10/new-look-for- software-provisioning-manager/ . The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of Software Provisioning Manager - running on the installation host using the standard protocol HTTPS.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 40 PUBLIC Installing the SAP Host Agent Separately For the SL Common GUI the installer provides a pre-generated URL at the bottom of the shell from which you are running the installer . If you have a supported web browser installed on the host where you run the installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser supported by the SL Common GUI on any device and run the URL from there. For more information about supported web browsers see Prerequisites for Running the Installer [page 36]. If you need to run the SL Common GUI in accessibility mode, apply the standard accessibility functions of your web browser.
● As soon as you have started the sapinst executable, the installer creates a .sapinst directory underneath the /home/
Shell Used Command
Command prompt ADDENVVAR ENVVAR(TEMP) VALUE('
Qp2Term export TEMP=
Note
When you leave your Qp2Term session, all changes of the environment variables done by the command export are reverted.
Caution
Make sure that the installation directory is not mounted with NFS, or there might be problems when the Java Virtual Machine is started.
The installer records its progress in the keydb.xml file located in the sapinst_instdir directory. Therefore, if required, you can continue with the installer from any point of failure, without having to repeat the already completed steps and without having to reenter the already processed input parameters. For security reasons, a variable encryption key is generated as soon as the sapinst_instdir directory is created by the installer. This key is used to encrypt the values written to the keydb.xml file.
Recommendation
We recommend that you keep all installation directories until the system is completely and correctly installed.
● The installer extracts itself to the temporary directory. These executables are deleted again after the installer has stopped running.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Installing the SAP Host Agent Separately PUBLIC 41 Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory after the installer has finished. You can safely delete them. The temporary directory also contains the log file dev_selfex.out from the self-extraction process of the installer, which might be useful if an error occurs.
Caution
If the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.
● To see a list of all available installer properties, enter the following commands: CD DIR('
● If required, stop the installer by choosing the Cancel button.
Note
If you need to terminate the installer, press Shift + Esc then 2 on your IBM i host.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 42 PUBLIC Installing the SAP Host Agent Separately 4 Uninstalling the SAP Host Agent Separately
This section describes how to delete a standalone SAP Host Agent with the Uninstall option of the installer.
Prerequisites
● You have installed your SAP Host Agent with standard SAP tools according to the installation documentation. ● You are logged on as user QSECOFR or as a user that has the same authorizations as QSECOFR. ● You do not have to stop the SAP Host Agent. The SAP Host Agent is stopped automatically during the uninstall process. ● When starting the uninstall, make sure that there are no SAP system user sessions still open.
Context
● During the uninstall process, all file systems and subdirectories of the selected SAP system or single instance are deleted. Before you start uninstalling, check that you have saved a copy of all files and directories that you want to keep to a secure location. ● The uninstall process is designed to remove as much as possible of the SAP system to be deleted. If an item cannot be removed, a message informs you that you have to remove this item manually. You can do this either at once or after the uninstall process has finished. As soon as you confirm the message, the uninstall process continues.
Procedure
1. Start the installer as described in Running the Installer [page 38]. 2. On the Welcome screen, choose:
Generic Installation Options
On the General SAP System Parameters screen, deselect Profiles Available and select Uninstall Standalone SAP Host Agent.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Uninstalling the SAP Host Agent Separately PUBLIC 43 Note
To find more information on each parameter during the Define Parameters phase, position the cursor on the required parameter input field , and choose either F1 or the HELP tab. Then the available help text is displayed in the HELP tab.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 44 PUBLIC Uninstalling the SAP Host Agent Separately Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information. About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information. ● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External Platforms
Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up. The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 2.0 Important Disclaimers and Legal Information PUBLIC 45 www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.
Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.
THE BEST RUN