| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2020-12-17 |
SAP, {{site.data.keyword.cloud_notm}} SAP-Certified Infrastructure, {{site.data.keyword.ibm_cloud_sap}}, SAP Workloads, network connectivity, routes, AIX, Linux, NTP, time server, |
sap |
{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:external: target="_blank" .external} {:pre: .pre} {:table: .aria-labeledby="caption"} {:note: .note} {:tip: .tip} {:important: .important}
{: #power-vs-aix-nw}
The following information provides an introduction for customers who are new to IBM Power Infrastructure environment.
{: #power-vs-aix-nw-ssh_tunneling}
This section describes SSH tunneling for specific SAP methods such as SAP GUI and Software Provisioning Manager (formerly known as SAPINST).
{: #power-vs-aix-nw-ssh_connection}
For a stable SSH connection, use the ServerAliveInterval and ServerAliveCountMax SSH options when you connect to {{site.data.keyword.powerSys_notm}} by using a public network interface.
ssh -o ServerAliveInterval=60 -o ServerAliveCountMax=600 <user>@<Public IP Address>
{: #power-vs-aix-nw-sap_gui}
Establish an SSH tunnel from your client machine to the cloud server. For example, if your client machine is running on a Windows operating system, run the following command:
ssh -o ServerAliveInterval=60 -o ServerAliveCountMax=600 -4 -L 3200:localhost:3200 -N -f -l root <Public IP Address> -p 22
In this command, 3200 is the port number that is used to connect to an application server with instance number 00. You might have to change it to connect to a different application server, for example, 3202 for instance number 02.
{: #power-vs-aix-nw-swpm}
Establish an SSH tunnel from your client machine to the cloud server. For example, if your client machine is running on a Windows operating system, run the following command:
ssh -o ServerAliveInterval=60 -o ServerAliveCountMax=600 -4 -L 4237:localhost:4237 -N -f -l root 149.81.129.28 -p 22
4237 is the default port that is used by Software Provisioning Manager. You might have to change it if the Software Provisioning Manager execution suggests a different port.
{: #power-vs-aix-nw-swpm-ssh}
ssh -o ServerAliveInterval=60 -o ServerAliveCountMax=600 -4 -L $localport:localhost:$remoteport -N -f -l root $host -p 22
For more information about SSH port forwarding and SAP ports, see SSH Port Forwarding with PuTTY{: external}.
{: #power-vs-aix-nw-ssh-config-issues}
For SSH tunnelling, missing SSH host keys must be generated. For more information, see Setting up an SSH client{: external}.
{: #power-vs-aix-nw-ntp_time_server_netweaver}
A newly provisioned {{site.data.keyword.powerSys_notm}} might not show the correct time when you run the date command. The initial time setting on the server often differs by 10 - 15 minutes from the correct time. This time difference can cause problems when you install and run your SAP system on the server, or when you connect the SAP system to your on-premises landscape.
You can keep the time current by configuring an NTP daemon that receives the correct time from an NTP time server. To set up NTP on AIX, see How to configure NTP in your Environment and common issues{: external}.
To enable the AIX virtual server to synchronize with the NTP server, add the network IP address of your company’s NTP server or a public NTP server to the NTP configuration file /etc/ntpd.conf.
Be sure to configure NTP to use the SLEWING option -x as recommended in the following SAP Notes:
- 1972803 - SAP on AIX: Recommendations{: external}
- 2456565 - Set NTP with SLEWING option in AIX{: external}
After you complete the configuration, check that the NTP daemon runs with the -x argument as follows:
root@ibmdemnw01:/home/root> ps -ef | grep -i xntpd
root 32309530 1 0 00:13:24 - 0:00 /usr/sbin/xntpd -x
{: #power-vs-aix-nw-nim_service_handler}
If you plan to run a NIM Service Handler (NIMSH) on your AIX virtual server to connect to a NIM server, make sure that you avoid the following port conflict.
The NIM client daemon (NIMSH) uses reserved ports 3901 and 3902 (see Using the NIM service handler for client communication{: external}). If you install an SAP Central Services Instance with instance number 01 or 02 on the same virtual server, a conflict is generated. By default, the SAP Central Services Instance installation configures port number 39XX for SAP Message Server internal communication, where XX is the two-digit SAP instance number.
An SAP installation places the port number into the SAP profile file DEFAULT.PFL. For example, the following entry in DEFAULT.PFL is for an SAP Central Services instance number 01:
rdisp/msserv_internal = 3901
To avoid port conflicts, do one of the following actions:
- Use instance number 00 for your SAP Central Services instance or another instance number that is not 01 or 02.
- Change the value of the
rdisp/msserv_internalprofile parameter to a port value that does not conflict with the reserved ports of NIMSH or any other program on your server.
You can check the status of the NIM components on the AIX server as follows:
# lssrc -a |grep -i nim
nimsh nimclient inoperative
nimhttp inoperative
{: #power-vs-aix-nw-adding_storage}
Configure additional space in the rootvg for third-party vendor prerequisite checks. After provisioning the AIX server, the rootvg has approximately 8 GB of free space. To prevent issues with prerequisite checks when you install database software, add another disk with a partition size of 30 GB.
-
During virtual server instance provisioning, create a new storage volume that is 30 GB.
-
After the AIX server is provisioned, run the
lspvcommand for an overview ofhdisks. The output shows one disk that belongs to the rootvg and another disk that does not have a physical volume identifier and a volume group assigned:# lspv hdisk0 none None hdisk1 00f6db0af58e9775 rootvg active -
To extend the
rootvgvolume group, run the following command:extendvg rootvg <new hdisk>
{: #power-vs-aix-nw-extending_tmp}
SAP installations as well as Db2 and Oracle Database software installations use PREINSTALLER checks to make sure that your system is database-ready. One of the checks is the amount of free space in /tmp. For example, at least 5 GB of available space is expected for Oracle installations. For Db2, the free space check expects 512 MB.
To extend /tmp:
-
Check the space available in the
rootvg. Run the following command:lsvg rootvg | grep "FREE PPs"If more storage is required, you should have sufficient space to extend
/tmpbecause you already added an extra disk. -
Run the following command:
chfs -a size=5G /tmpThe size of the logical volume on which
/tmpresides (typicallyhd3) and the file system capacity is increased to 5 GB.
You can run the same command with +5G /tmp to append the size of the file system and add 5 GB to the existing size.
You can enter a higher value to extend the file system further, for example, if you need more capacity, or if there are issues with free space in either “/” or /tmp during the PREINSTALLER check.
{: #power-vs-aix-nw-extending_paging_space}
Prechecks can include a paging space check, which analyzes your system and determines whether your server has sufficient paging space for the database or application installation.
Some databases require at least 32 GB. Instead of increasing the size of the current paging space hd6, create a second paging volume when you define additional storage for the database or application volume groups.
After you create volume groups for applications and databases, you can create the new paging space to reside on the volumes within the volume groups.
The lsps -s command shows the total amount of paging space on your system, for example:
root@ibmdemnw01:/swrepo/AIX> lsps -s
Total Paging Space Percent Used
25760MB 0%
The lsps -a command shows the distribution of the paging space that is defined on your system, for example:
root@ibmdemnw01:/swrepo/AIX> lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type Ch
hd6 hdisk4 rootvg 160MB 20 yes yes lv
paginglv hdisk2 fr02swreposvg 25600MB 0 yes yes lv
root@ibmdemnw01:/swrepo/AIX> I
This example shows that a paging space was defined in the volume group fr02swreposvg on hdisk2 called paginglv in addition to the standard paging space hd6 in the rootvg.
If your new AIX server instance doesn't have sufficient paging space when you begin the implementation phase of your database or application, it can lead to multiple errors, for example, PGSPACE_KILL where the VMM starts to prune system processes. Be sure to follow third-party software recommendations for their products.
{: #power-vs-aix-nw-aix_toolbox}
When you download SAP packages from the SAP Marketplace{: external}, sometimes the files are packed into multispanning archives. Tools are required to decompress the files and rebuild the packages.
For more information, see SAP Note 886535 - Downloading multispanning archives (RAR archive){: external} and SAP Note 960755 - Unpacking ZIP archives in Unix{: external}.
The required tools, unrar and unzip, can be downloaded from the AIX Toolbox For Linux Applications{: external}. Download the tools and use RPM to install them on your AIX system. You might need to install additional filesets as a prerequisite. These files might already be in the limited AIX repository that is supplied when the AIX server is provisioned.
Additional installation files can be found on the /usr/sys/inst.images mountpoint.
The vnc package is another useful tool in the AIX Toolbox for Linux Applications. After you install the vnc package into your AIX server, you will be able to start a VNC server on your AIX server. Then you can use a VNC viewer such as TightVNC on the jump server or another desktop to connect to your AIX server to start an SAP installation by using Software Provisioning Manager (formerly known as SAPINST) with the web front end. For more information, see Software Provisioning Manager{: external} and Installing by using a jump server.
{: #power-vs-aix-nw-filesets_for_db}
{: #power-vs-aix-nw-oracle_12_filesets}
Oracle 12 is supported on AIX 7.1 and 7.2. For a list of required operating system filesets and APARs, see the system requirements{: external}.
Run the following command to check whether the filesets are available:
lslpp -l |egrep -w 'bos.adt.base|bos.perf.libperfstat|bos.adt.lib| bos.adt.libm|bos.perf.perfstat|bos.perf.proctools|xlC.aix61.rte|xlC.rte'
{: #power-vs-aix-nw-oracle_19_filesets}
Oracle 19 is supported on AIX 7.1 and 7.2.
For a list of operating system filesets and APARs, see the system requirements{: external}.
{: #power-vs-aix-nw-requirements_for_db2}
Before you install IBM Db2, make sure that the system requirements are met.
For the software requirements for Db2 and SAP, see Installation of SAP Systems Based on the Application Server ABAP and DB2{: external}.
For dependencies and download details for Db2, see System requirements for IBM Db2 for Linux, UNIX, and Windows{: external}.
The following additional filesets must be installed for Db2 installations:
- bos.adt.* - Base Application Development
- bos.perf.* - Performance and diagnostics tools
- perfagent.tools - Performance monitoring tools
You can run the following command to check whether the filesets are available:
lslpp -l |egrep -w 'bos.adt.base|bos.perf.libperfstat|bos.adt.lib| bos.adt.libm|bos.perf.perfstat|bos.perf.proctools'
{: #power-vs-aix-nw-requirements_for_sap_maxdb}
Before you install SAP MaxDB, make sure that the required AIX filesets are installed. Run the following command:
lslpp -l | egrep -w 'bos.mp64|bos.rte.libc*|xlC.aix61.rte|xlC.sup.aix50.rte'
- bos.mp64 - Base Operating System 64-bit
- bos.rte.libc - libc Library
- xlC.aix61.rte - IBM XL C++ Runtime for AIX 6.1
- xlC.sup.aix50.rte - XL C/C++ Runtime for AIX 5.2
- bos.mp64 - Base Operating System 64-bit
- bos.rte.libc - libc Library
For more information about the required AIX filesets, see SAP Note 720261 - System prerequisite AIX - liveCache/MaxDB 7.4-7.9{: external}.
I/O usage is intensive during the Software Provisioning Manager installation phase. If there isn't enough paging space to complete the Software Provisioning Manager MaxDB tasks, the stability of the system can be impacted. Before you install third-party tools, make sure that sufficient paging space is provisioned according to the third-party software manufacturer's space recommendations. {: important}
{: #power-vs-aix-nw-storage_aix_lvm}
Follow these recommendations on creating storage and the AIX Logical Volume Manager (LVM) for the database and application layer.
{: #power-vs-aix-nw-storage_volume_affinity}
When you create storage by using the {{site.data.keyword.cloud}} console, specify volume affinity to prevent issues with new volume discovery on existing virtual server instances. Keep the following points in mind:
- You can't mix Tier 1 and Tier 3 storage.
- After you provision storage with volume affinity, you can't go back and change it. Carefully plan your storage layer and make sure that your configuration is correct.
- After you provision new volume, you can toggle bootable and sharing switches. Sharing is especially useful for an Oracle RAC implementation.
For more information about volume affinity, see Adding network block storage.
{: #power-vs-aix-nw-storage_aix_lvm_mount_points}
Be sure to follow the recommendations of third-party software vendors about the configuration of logical volumes and mount points for the file systems. For more information, see the following links:
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver with IBM DB2{: external}
SAP Note 2172935 - Installation - SAP Systems based on SAP NetWeaver : Oracle Database{: external}
Directory and Filesystem Structure for MaxDB{: external}
{: #power-vs-aix-nw-storage_aix_lvm_mount_points-more-recommend}
- Create separate volume groups for database and applications. For example, for an Oracle installation, create the
oraclevg. For SAP products, create theappsvgorsapvg, depending on the products that you choose to install. - Allocate sufficient storage to each of the volume groups and follow a standard naming convention when you create logical volumes. Add your preferred SID to the logical volume name.
{: #power-vs-aix-nw-storage_aix_swpm}
SAP Software Provisioning Manager requires additional files that will be used for the installation of SAP products such as exported images, SAP kernel files, and database clients. The disk space requirements depend on the SAP product and database that you plan to install.
Calculate the sum of SAP packages on the SAP Marketplace{: external} that are required for your installation. Before you install SAP products by using Software Provisioning Manager, provide the required storage.
Create a dedicated volume group and logical volume and mount it on /swrepo/SAP.
{: #power-vs-aix-nw-installation_overview}
Before you install the system by using Software Provisioning Manager (SWPM), follow these preliminary steps:
-
Create a user in the
smitty usermenu calledswpmuserso you can avoid running the installation as therootuser. If you didn't create a separaterootgrp, keep the primary group assystem. Also include this user in the system and root groups so it is basically an administrative user. You will use this user when you start the Software Provisioning Manager tool as a Remote Access Tool user. -
Create the following directory structure under your software repository mount point
/swrepo/SAPfor Software Provisioning Manager and other required software as recommended here: Creating separate storage for an installation repository.
| Directory | Purpose |
|---|---|
/swrepo/SAP/SWPM/ |
Location to unpack the Software Provisioning Manager SAR file |
/swrepo/SAP/SWPM/tmp |
Temporary storage and cache for Software Provisioning Manager installation |
/swrepo/SAP/kernel |
Location for the SAP kernel files |
/swrepo/SAP/export |
Location for the export files needed |
/swrepo/SAP/DB |
Location for the database product and client software |
/swrepo/SAP/others |
Location for miscellaneous software such as saphostagent |
/swrepo/SAP/prereqcheck |
Location for the prerequisite check output |
| {: caption="Table 2. Software repository directory structure" caption-side="top"} |
{: #power-vs-aix-nw-installing_client_machine}
Follow these steps to install the system by using a client machine.
-
Set up SSH tunneling on the client machine. For more information, see SSH tunneling.
-
Set a variable on the server for
TMPDIRon the AIX server:export TMPDIR=/swrepo/SAP/SWPM/tmpOtherwise, Software Provisioning Manager uses the system-wide
/tmpdirectory forsapinstdirlogging and quickly runs out of space. -
Unpack the Software Provisioning Manager SAR file on the server.
-
Unpack the installation into the respective folders.
-
Run the Prerequisites Check to make sure that all requirements are met for the installation.
- Go to the
/swrepo/SAP/prereqcheckdirectory. - Run the Software Provisioning Manager
sapinstexecutable as follows:/swrepo/SAP/SWPM/sapinst SAPINST_REMOTE_ACCESS_USER=swpmuser SAPINST_HTTPS_PORT=443
- Go to the
-
Open a browser on your client machine and go to this URL:
https://<Public IP address of your AIX server>:443/sapinst/docs/index.html -
In login box, enter the swpmuser and the password that you defined.
-
Open the Prerequisites Checker. For example, for Db2: On the Welcome page, select SAP NetWeaver 7.5 > IBM Db2 for Linux, UNIX, and Windows > Preparations > Prerequisites Check.
-
On the Prerequisite Checker Options page, select the first three options.
-
Click Next to proceed through the wizard until the Prerequisites Checker Results are displayed.
If you see a swap size MEDIUM result, check that you have sufficient swap space on your system. {:note}
After you complete the prerequisites check, you can proceed with the SAP NetWeaver installation for the application server, central services, and database installation.
{: #power-vs-aix-nw-installing_jump_server}
Follow these steps to install the system by using the jump server and tools that are installed on your AIX virtual server.
{: #power-vs-aix-nw-on_aix_server}
- Set a password. The VNC executable can be started multiple times and open multiple channels. Set a password to prevent other people from working on your channel.
- Go to the
/home/root/.vncdirectory. - Run the
vncpasswdcommand. - Set the password for your connection.
- Go to the
- In the
rootdirectory, run thevncservercommand to start a vncserver session.
{: #power-vs-aix-nw-on_laptop_or_jump_server}
{: #power-vs-aix-nw-open_terminal}
-
Connect the VNC Viewer software to the AIX server. In the VNC Viewer window, enter the address that was displayed when you started the vncserver on AIX. To use a hostname, make sure to update the
/etc/hostsfile so that the hostname resolves to IP.Your new server must be resolvable in the Windows or operating system of your laptop (for direct connections) and in your jump server. If an encryption warning is displayed, click Continue. When prompted, enter your password and click OK. {:important}
-
Open a terminal. Enter
xtermoraixtermon the command line.
{: #power-vs-aix-nw-set_variables}
When you run SAPINST, set variables to ensure that there are enough resources to start the executable and that it exports the correct details about you and your system.
-
Echo the
$DISPLAYvariable. The output should show the same details as the connection. -
Run the
xhost +command to disable access control. -
Run the
xauthcommand to list the currently assigned keys that are needed to connect.Make a copy of the entries. If you need to switch to an SAP ACCOUNT for any reason, you can add the keys, access the session, and export the $DISPLAY again. {:tip}
-
Set the following variables for the installation session that are needed for SAPINST:
export SAPINST_REMOTE_ACCESS_USER=<Your User ID here, root or swpmuser> export SAPINST_USE_HOSTNAME=<Hostname or Virtual Address> export LIBPATH=/sapmnt/<SID>/exe export CPIC_MAX_CONV=500 export JAVA_HOME=/usr/java8_64 export PATH=$JAVA_HOME/bin:$PATH export TMP=/swrepo/SAP/SWPM/tmp export TEMP=/swrepo/SAP/SWPM/tmp export TMPDIR=/swrepo/SAP/SWPM/tmp umask 022 ulimit -n 32000 ulimit -d unlimited ulimit -s unlimited ulimit -f unlimited ulimit -m unlimited- The
$LIBPATHvariable should point to your/sapmnt/<SID>/exedirectory, which should already be on your system. JAVA_HOMEshould point to the/usr/javaX_64version installed on your server.- The exports for the
TEMP;,TEMPDIR, andTMPdirectories ensure that SAPINST doesn't use the/tmpdirectory on AIX for the installation. - Make sure that the temp exports are set to a dedicated filesystem where you have unpacked SAPINST.
- The
umaskandulimitsettings are recommended.
- The
{: #power-vs-aix-nw-test_sapinst}
-
In the SAPINST directory, run the following command:
./sapinst SAPINST_SLP_MODE=true -
When prompted to confirm, enter
y. -
In your browser, go to the following URL:
https://:4237/sapinst/docs/index.html
For example:
https://ibmdemnw01.local.demo:4237/sapinst/docs/index.html -
When prompted, log in with the Software Provisioning Manager user or root user.
-
Select your preferred product and proceed to install.
{: #power-vs-aix-nw-port_forwarding}
If you're using a Windows operating system and the VNC port isn't working or it's closed, you need to tunnel to make the port for VNC 5901 usable. If you're using a recent version of Windows PowerShell, an SSH server is included so you can use SSH commands on the command line. For more information, see SSH tunneling.
{: #power-vs-aix-nw-common_issues} Here are some common issues that occur with Software Provisioning Manager:
-
Capacity of the
/tmpdirectory during the pre-flight checks. The recommendation is at least 5 GB. -
Make sure that there's at least 32 GB of paging space. This can be adjusted after the AIX server is installed with the required database and applications. The recommendation is to run the required workload and tune the I/O resources.
-
Extend
hd4or “/” to 150 MB. Otherwise, you get a WARNING during the prerequisite tests for Db2 and Oracle. -
Check
/etc/security/login.cfgduring installation. For more information, see SAP Note 2360008 - 3004-703 Check "/etc/security/login.cfg" during installation. -
Required EXPORT750 (Folder EXP1) missing- If you want to install the system in another language, download the EXP1 compressed file and associated LANG .zip files. Download them to the jump server orswreposfilesystem and specify them when the Software Provisioning Manager installer requests them. -
R3load TestConnect fails - To resolve this issue, refer to the following SAP Notes:
SAP Note 1875902 - R3load -testconnect fails during using SWPM in step testDatabaseConnection
SAP Note 2805859 - A1EEGEN 000 (DBS) DbSlErrorMsg rc = 28 'no connection info in DBCON found'
{: #power-vs-aix-nw-information_resources_netweaver}
The following links will assist you in the installation and configuration of your {{site.data.keyword.powerSys_notm}} instances and databases with SAP products. Links with numbers in the title point to the SAP Support Portal.
{: #power-vs-aix-nw-cloud_resources}
| Link | Description |
|---|---|
| 2855850 - SAP Applications on {{site.data.keyword.IBM_notm}} Power Systems Virtual Servers | Supported SAP applications on {{site.data.keyword.powerSys_notm}}s |
| 1380654 - SAP support in IaaS environments | IaaS environments |
| 2923984 - SAP on {{site.data.keyword.IBM_notm}} Power Systems Virtual Servers: Support prerequisites | Support prerequisites |
| 2947579 - SAP HANA on {{site.data.keyword.IBM_notm}} Power Systems Virtual Servers | SAP HANA and virtual server instances |
| 2923962 - Check SAP HANA NUMA Layout on {{site.data.keyword.IBM_notm}} Power Systems Virtual Servers | Checking the NUMA layout |
| 2932766 - Key Monitoring Metrics for SAP on {{site.data.keyword.IBM_notm}} Power Systems Virtual Servers | Key Monitoring Metrics |
| {: caption="Table 3. Cloud-related resources - {{site.data.keyword.IBM_notm}} Power Systems Virtual Servers" caption-side="top"} |
{: #power-vs-aix-nw-os_aix}
| Link | Description |
|---|---|
| 1780629 - AIX: Minimal OS Requirements for SAP Kernel | Minimum operating system requirements for AIX |
| 2267287 - Using SAP systems with AIX 7.2 | SAP Systems on AIX 7.2 |
| 1541935 - Using SAP systems with AIX 7.1 | SAP Systems on AIX 7.1 |
| 1972803 - SAP on AIX: Recommendations | Guidance on how to optimally configure AIX for SAP |
| 2630086 - Avoid signal 33, out of memory on AIX | Signals paging and memory situations - recommended |
| AIX Service Strategy and Best Practices | The AIX journey and strategy |
| IBM Knowledge Center AIX | A central link for AIX information |
| Troubleshooting AIX 7.2 | Useful problem solving |
| IBM Fix Central | Fix Central for your AIX filesets and operating system upgrade source |
| Services and Support Best Practices POWER9 | Download the PDF and see the command reference |
| Fix Level Recommendation Tool - FLRT | Cross-compatibility and fix recommendations tool |
| IBM AIX Developer | AIX developer website |
| IBM AIX Enhancements and Modernization | The latest updated IBM Redbook for AIX |
| {: caption="Table 4. Operating systems - AIX" caption-side="top"} |
{: #power-vs-aix-nw-os_linux-aix}
{: #power-vs-aix-nw-db_db2}
| Link | Description |
|---|---|
| Installation of SAP Systems Based on the Application Server ABAP and IBM DB2 | Downloadable as a PDF File |
| System requirements for IBM Db2 for Linux, UNIX, and Windows | System requirements DB2 |
| IBM POWER9 and SMT performance for IBM Db2 | IBM POWER9 and Db2 |
| Currently supported DB2 software levels and Fixpacks | Db2 software levels + Fixes |
| Currently supported database features DB2 | Db2 feature support |
| Required File systems for DB2 and SAP Netweaver | Filesystem overview and mountpoints |
| {: caption="Table 6. Databases - Db2" caption-side="top"} |
{: #power-vs-aix-nw-db_oracle}
{: #power-vs-aix-nw-db_maxdb}
{: #power-vs-aix-nw-applications_sap}
| Link | Description |
|---|---|
| SAP Guide Finder | Recommended for all installations |
| 1704753 - Inst.Systems Based on NetWeaver on UNIX - Using Software Provisioning Manager 1.0 | Software Provisioning Manager information for version 1.0 |
| Installation Guides - Application Server Systems - Software Provisioning Manager 1.0 | Additional content |
| {{site.data.keyword.IBM_notm}} Power Systems Planning and Monitoring Best Practices for SAP Applications | IBM Redbook for planning and monitoring SAP |
| {{site.data.keyword.IBM_notm}} Power Systems Infrastructure I/O for SAP Applications | IBM Redbook for infrastructure planning and SAP |
| 2158828 - Minimal DB system platform requirements for SAP NetWeaver 7.5 | Platform requirements for NW7.5 |
| 2329005 - Minimal DB system platform requirements for NW AS ABAP 7.51 INNOVATION PKG | Platform requirements for innovation package 7.51 |
| {: caption="Table 9. Applications - SAP" caption-side="top"} |