EHP3 for SAP CRM 7 Installation (Windows Server & DB2)

Prerequisites

You have installed and downloaded all the required medias for EHP3 SAP CRM 7 ABAP. This activity will be executed on Windows Server 2008 R2 and DB2 database environment.

Basically, below files are required to complete the activity,

• Windows Server 2008 R2
• DB2 database
• Software Provisioning Manager (SWPM)
• EHP3 SAP CRM 7 installation export for ABAP
• Kernel, SL Controller

You must also ensure the hardware (RAM, CPU, hard disk space, swap) are met with the SAP recommendations (You have to read the master and installation guide)

Execution

1. Launch the SWPM installer and navigate to the following tree,

SAP Business Suite 7i 2013 Support Release 1 > EHP3 for SAP CRM 7.0 ABAP Support Release 1 > IBM DB2 for Linux, UNIX and Windows > SAP Systems > Application Server ABAP > Standard System > Standard System

CRM7 - Welcome to SAP Installation

2. Choose Custom.

Parameter - Custom

3. On the next screen, click OK to log off. Wait for a few seconds, then log in back.

4. Define the SAP System ID (SID).

SAP System ID

5. Enter the DNS domain name for the SAP system to calculate the FQDN (fully qualified domain name). If not, just uncheck and click on Next.

DNS Domain Name

6. Enter the unicode kernel directory.

Media Browser - UC Kernel

7. Define the Master Password.

Master Password

8. Our installation is in Local Domain. Click Next.

Windows Domain

9. If you are using the same password as Master Password, just click Next. Else, define a different password for Operating Users password.

OS User Passwords

10. Enter the database name (will be the same as SID).

Database Identification

11. Click Next.

Dabatase Connect User Domain

12. Click Next again.

Database Connect User AS ABAP

13. Click Next to accept the default DB2 software location directory. Else, you can maintain a different directory.

Database Software Location

14. Click Next (for the same password as Master Password – If not, enter a new password specifically for database administrator).

Database Administrator

15. Do the same as step number 14.

ABAP Database Connect User Password

16. Click Next.

SAP Host Agent User Domain

17. Click Next.

SAP System Administrator OS Password

18. Locate the installation export folder. (sorry! we accidentally deleted the screenshot)

19. Locate the DB2 database folder. (sorry! we accidentally deleted the screenshot)

20. Accept the default value of database communication port. Click Next.

DB2 Communication Port

21. Locate the DB2 CLI and JDBC driver.

DB2 CLI & JDBC Driver

22. Specify the DB2 database drives. In this activity, we have only 1 drive (C:/), so the selection will be greyed out.

Database DB2 Drives

23. Specify the DB2 database memory.

Specify DB2 Database Memory

24. Specify the minimization of database size.

DB2 Minimization Database

DB2 Data Compression
Tables are compressed using DB2’s (static) row compression during installation. As of DB2 V9.7, indexes are also compressed using DB2 index compression. In addition, as of DB2 V9.5, the global compression option is set to YES, that is, row compression is enabled for tables that are created after the installation. If you want to use DB2 row and index compression, make sure that you have a valid license for this function. If you have purchased your DB2 license from SAP (an SAP OEM license), DB2 row and index compression is already part of your license agreement.

Note: If you do not want to use data compression now, you can activate the global compression option later using the DBA Cockpit. In addition, you can compress single tables (including indexes) later.

Deferred Table Creation
Empty tables consume a considerable amount of disk space. With deferred table creation, tables that do not contain any data are not created on the database until the first data is inserted. The table creation at INSERT is entirely transparent to the application. You can use the DBA Cockpit (transaction DBACOCKPIT –> Space –> Virtual Tables) to reverse this status and create the empty tables that have not yet been created.

Note: If you do not want to use this feature now , you can remove empty tables from the database by using the DBA Cockpit (transaction DBACOCKPIT –> Space –> Virtual Tables).

25. Specify the storage management and tablespaces.

DB2 Storage Management & Tablespace

26. Specify to use Declustering / Depooling option for optimization of SAP Business Suite.

DB2 Declusterin & Depooling Option

Table declustering / depooling is the process of converting SAP cluster and pool tables to transparent database tables. For more information, see SAP note 1892354.

Select Do not decluster/depool ABAP tables in the following cases:
– You want to install the target system without using declustering / depooling.
– The table types of your target system are the same as in the source system.

Select Force declustering/depooling of all ABAP tables if you want to decluster / depool all ABAP tables in your target system. To compensate for the increased space consumption of your declustered / depooled SAP system, we recommend that you activate database compression features as described in SAP note 1892354.

27. Specify the database load import parameter. The load parameter is based on the CPU hardware resource. Normally, 1 CPU can be use to process 2-3 database import load.

Database Import Load Parameter

28. Enter the PAS & ASCS instance number value.

PAS & ASCS Instances

29. Accept the default value (or change to value you desired) and click Next.

ABAP Message Server Port

30. Click Next.

ICM User Management

31. Enter the information of SLD destination (We set to No SLD Destination because no SLD is configured in the user’s landscape now)

SLD Destination

32. Click Next to unpack the archives.

Unpack Archives

33. We choose not to install the Diagnostic Agent for now. You can select the option to install it. Click Next.

Install Diagnostic Agent

34. The parameter summary screen. Before you hit the installation button, ensure to double check the parameters you defined earlier. Once confirmed, you can start the installation.

Parameter Summary

35. The installation is now begin. Depending on hardware resources (CPU, RAM, abap loads and etc..) , the installation will take around 5-7 hours (or less) to be completed. You can take coffee now and monitor the progress closely.

EHP3 CRM 7 Installation

36. Complete!

EHP3 CRM7 Installation Complete

Note

You will be receiving a key ID during the execution. Please store and keep a backup of this key.

The secure storage will be encrypted with the following key:
Key ID: xx
Key Value: xxxxxxxxxxx

Caution: Before choosing OK, make a backup of the Key ID and of the -character Key Value, and keep it in a secure place for disaster recovery.
When you are in the process of system installation and want to use this system as source for a system copy or system rename, you must provide this backup to restore access to the encrypted data in the copied system.
Choose Cancel to return to the secure storage dialog without change.

You May Also Like

Leave a Reply?