SDN Contribution

© 2006 SAP AG 1

Applies to:

SAP NetWeaver 2004s.

Summary

This paper aims to document the experience and key learnings from setting up the NetWeaver 2004s stack in a Solaris 10 Container.

Authors: Vasanth Bhat and Shankar Selvaraj

Company: Sun Microsystems India Pvt. Ltd.

Created on: 19 May 2006

Author Bio

Vasanth Bhat is a Lead Engineer in SAP Partner Engineering Team at Sun Microsystems India Pvt. Ltd. Shankar Selvaraj is a SAP NetWeaver Specialist in SAP Partner Engineering Team at Sun Microsystems India Pvt. Ltd.

© 2006 SAP AG 2

Table of Contents

Chapter 1: Executive Summary....................................................................................................... 3

Chapter 2 Background Information................................................................................................ 4

2.1 SAP NetWeaver 2004s .......................................................................................................... 4

2.2 Solaris 10 ............................................................................................................................... 4

2.3 Solaris 10 Containers............................................................................................................. 4

2.4 Solaris Resource Manager .................................................................................................... 4

2.5 Fair Share Scheduler ............................................................................................................. 4

Chapter 3 Environment Setup ......................................................................................................... 5

3.1 Hardware Environment .......................................................................................................... 5

3.2 Software Environment............................................................................................................ 5

Chapter 4 Planning & Preparation................................................................................................... 6

4.1 System Landscape................................................................................................................. 6

4.2 System Preparation for SAP Installation................................................................................ 6

Chapter 5 SAP NetWeaver 2004s Setup ...................................................................................... 10

Chapter 6 Installation Time Inputs............................................................................................... 24

Chapter 7 Conclusion .................................................................................................................... 25

Chapter 8 References.................................................................................................................... 26

Disclaimer & Liability Notice .......................................................................................................... 27

© 2006 SAP AG 3

Chapter 1: Executive Summary

Customers planning for setup of SAP NetWeaver 2004s stack in Solaris 10 containers can use this document as a guideline for their setup.

The data in this document is based on a project carried out at NetWeaver Sun Lab, located in SAP campus in Bangalore, India. The NetWeaver Sun Lab aims to bring value to customers running NetWeaver on Sun Platform through a process of continuous improvement.

This document aims to:

• Share the experience and key learnings from the study

• Be a useful addition to the standard Installation Guides

• Provide inputs on the time required for different phases of the setup

For the project we used the Minimal Landscape configuration (A single setup consisting of both ABAP & J2EE and all the NetWeaver components) with Oracle 10g, running in a Solaris container on Sun Fire v890 server.

We hope this document will help the customer in quicker deployments of SAP NetWeaver 2004s on Solaris 10 Containers. In our project studies the complete setup was carried out in less than 24 hours.

© 2006 SAP AG 4

Chapter 2 Background Information

2.1 SAP NetWeaver 2004s

SAP NetWeaver provides an open integration and application platform and permits the integration of the Enterprise Services Architecture. SAP NetWeaver 2004s is the latest release of SAP NetWeaver. More details on NetWeaver are available at http://www.sap.com/solutions/netweaver/

2.2 Solaris 10

The Solaris 10 OS provides leading innovation with proven scalability, availability, performance, and security on SPARC, AMD Opteron, and Intel Xeon-based systems. Solaris 10 ships with over 600 new breakthrough features, including new Security Features, Predictive Self-Healing, Dynamic Tracing capabilities (DTrace), Solaris ZFS (zettabyte file system), Service Management, Solaris Containers technology, and more. So far more than 4 million copies of Solaris 10 have been downloaded. Solaris 10 is available at no cost and is also open sourced through OpenSolaris. More details are available at http://www.sun.com/solaris and http://www.opensolaris.org/

2.3 Solaris 10 Containers

Solaris Containers isolate software applications and services using flexible, software-defined boundaries. This gives businesses the ability to ensure service levels by dynamically controlling applications and resources priorities. Each application being given a private environment, virtually eliminates error propagation, unauthorized access and unintentional intrusions. Solaris 10 containers reduce management costs through server consolidation, increase resource utilization and provide flexibility. More details on Solaris Containers are available at http://www.sun.com/software/solaris/utilization.jsp

2.4 Solaris Resource Manager

Solaris Resource Manager Software provides flexible resource management for the Solaris Operating Environment. The Solaris Resource Manager software provides the ability to allocate and control major system resources like compute, memory, storage, network etc. More details are available at http://docs.sun.com/app/docs/doc/817-1592

2.5 Fair Share Scheduler

Fair Share Scheduler (FSS) dynamically controls the allocation of available CPU resources among workloads, based on their importance. This importance is expressed by the number of shares of CPU resources that is assigned to each workload. More details on Fair Share Scheduler are available at http://docs.sun.com/app/docs/doc/817-1592/6mhahuojp?a=view

© 2006 SAP AG 5

Chapter 3 Environment Setup

3.1 Hardware Environment

The setup was carried out on the SF V890 Server. The server has the following configuration.

Model Sun Fire V890

CPU 8 UltraSPARC™ IV dual thread 64bit CMT @1.35-GHz (16 Threads)

RAM 32 GB

Storage 6 X 146 GB (10K-RPM FC-AL disks)

More details on the hardware can be found at http://www.sun.com/servers/midrange/v890/index.jsp 3.2 Software Environment

The environment was setup with the following software Environment

Software Version O.S Solaris 10

Database Oracle 10g, 10.1.0.4 SAP J2EE SAP J2EE 7.0 SP6 NetWeaver Components SAP Enterprise Portal 7.0 SP6

SAP Process Integration 7.0 SP6 SAP Development Infrastructure 7.0 SP6 SAP Mobile Infrastructure 7.0 SP6 SAP BI Java 7.0 SP6

The entire NetWeaver 2004s stack was setup on a single instance of ABAP+J2EE installation of Web Application Server 7.0.This configuration was chosen to keep the setup simple. The stack was patched to Service Pack 6

© 2006 SAP AG 6

Chapter 4 Planning & Preparation

4.1 System Landscape

The landscape included a central ABAP+J2EE installation with both the ABAP application server and the J2EE Engine on the SAP system. The mandatory instances of an ABAP+Java system, the central instance, the central services instance, and the database instance all running in a Solaris 10 Container

Figure 4.1: Minimal Landscape Configuration

4.2 System Preparation for SAP Installation

This section lists the steps carried out to prepare the system for the setup of NetWeaver 2004s. In our internal studies this step took roughly about 2 hours.

We started with the following activities to prepare the system for SAP Installation.

• Created a logical volume in RAID 0, striped configuration from the internal disks.

• Created the Unix File System (UFS) on the Logical volume.

• Create additional swap space of 96 GB ( 3 * RAM)

• Activated the Solaris resource manager and created the resource pools for use by the zones.

Figure 4.2.1: Create Resource Pools.

© 2006 SAP AG 7

Configured System to use the “Fair Share Scheduler” (FSS) to get the optimal utilization for the Server.

Figure 4.2.2: Enable Fair Share Scheduler

• Created two sparse zones, with the CPU resource shares of 60 and 20 respectively. We planned to use the first zone (hereafter referred to as nw04s_zone) for NetWeaver 2004s setup.

o Zone is initially created using the 'zonecfg' command and is assigned an IP address “10.53.129.129”.

o The zone is also assigned resources through resource pools.

o The file systems '/usr/sap' and '/sapmnt' as loopback file systems so that they are writable from inside the Zone.

o The Zone is assigned 60 CPU shares. This is used by the Fair Share Scheduler(FSS) to allocate the CPU resources to this Zone

Figure 4.2.3: Creation and Configuration of nw2004s_zone

© 2006 SAP AG 8

Figure 4.2.4: Zone Installation

Figure 4.2.5: Booting the Zone

Figure 4.2.6: Zone Post Install Configuration Start

Figure 4.2.7: Host Name configuration for the Zone

© 2006 SAP AG 9

Figure 4.2.8: DNS Configuration for the Zone

Configured the parameter settings for the nw04s_zone, by creating the OS users, groups and project with the associated parameters as specified in SAP Note 724713. We used the Sun Management Console (SMC) UI tool to perform these tasks, instead directly using the command line tool.

The SAP Note 724713 gives the parameter settings for Solaris 10. In doing so it mentions about setting using the commands. All these settings can also be done through the Sun Management Console (SMC). This is a full featured GUI based tool and is bundled as a part of the Solaris 10. This tool can be used to perform lot of Solaris administrative tasks from the GUI, without knowing the details of the command syntax.

Figure 4.2.9: Project Creation in SMC

© 2006 SAP AG 10

Figure 4.2.10: Project Resource Parameter configuration using SMC.

Chapter 5 SAP NetWeaver 2004s Setup

We have opted for the 2004s minimal landscape, with ABAP+J2EE configuration with oracle 10g database. All components were installed on the same instance of the SAP Web Application Server. In our internal studies the installation of NetWeaver 2004s stack took us about 14.5 hours.

The following Screen Shot shows some of the key steps during the Installation Process.

Figure 5.1: Installation Start

© 2006 SAP AG 11

The above Screen Shot shows the beginning of the SAP NetWeaver 2004s installation. We choose the Central System installation for Minimal Landscape setup.

Figure 5.2: NetWeaver Component Selection

In the component selection screen we select all the components for the minimal landscape setup.

Figure 5.3: Specify JAVA DVD Location

© 2006 SAP AG 12

Figure 5.4: Specify JDK Location

During the process of Installation the SAPInst tool installs the JCE policy files in the JDK/JRE directories. For this step to work you need to make sure that the JDK/JRE directories must be writable from Solaris local Zone.

There are two ways to achieve this. One option is to have the self extracting version of the JDK/JRE installed locally in the Solaris local Zone. This approach ensures that this installation of JDK/JRE is visible only inside this Zone. We selected this approach, and installed the JDK under /opt/j2se using the self extracting binaries.

An alternate approach is to explicitly mount the /usr/j2se or usr/jdk directory from the Global Zone as a read/write loopback file system inside in the Solaris local Zone.

We recommend using JDK version 1.4.2_09. When we tried 1.4.2_10 the installation hanged during the step “import java dump” in the J2EE Engine Installation. The SAP Note 716604 specifies clearly not to use the JDK 1.4.2_10.

© 2006 SAP AG 13

Figure 5.5: Specify SAP system Parameters

Figure 5.6: Specify Database Schema

We used the same value for both the SAP system ID and the Database ID.

© 2006 SAP AG 14

Figure 5.7: Specify Database Schema Parameters

Specify the parameters for ABAP and J2EE Schema. As a practice specify ABAP Schema as SAP<SID>. The J2EE Schema can be SAP<SID>DB.

If you encounter a problem in which the installation fails with the error “Administrator Longer than maximum length of users”, then follow the instructions in SAP Note 851251.

Figure 5.8: Specify passwords for standard DB users.

© 2006 SAP AG 15

Figure 5.9: Specify DB Import Parameters.

As a rule of thumb keep the number of Parallel jobs to a value smaller than the total number of cpu’s/cores in the system. We have experienced errors on occasions when we had bigger values.

Figure 5.10: Specify DB Statistics parameters.

During this phase the “brconnect” program is invoked with a value of Core/Thread count for option -p. This fails when this value is 16 or more. This problem is mentioned in SAP Note 851169. One solution is to opt for “Skip Statistics” if you have 16 or more processing units in your system. Another option ` would be to temporarily disable few processors using the 'psradm' command, during this installation step, and re-enable them after the completion of this step.

© 2006 SAP AG 16

Figure 5.11: Specify ABAP user Passwords

Figure 5.12: Specify location of RDBMS and Kernel DVD's.

© 2006 SAP AG 17

Figure 5.13: Specify Parameters for Local SLD Configuration

We opted for a Local SLD. If you have an existing configured central SLD, register the new system in the existing SLD.

Figure 5.14: Specify XI User Details.

© 2006 SAP AG 18

Figure 5.15: Specify DI User Details

Figure 5.16: Input Data Summary

© 2006 SAP AG 19

Figure 5.17: Installation Execution

Figure 5.18: Prompt for Oracle Installation.

After the Database extraction step the SAP Installer stops and prompts for Oracle Database Installation. Before launching the Oracle installer create the required directories for Oracle as shown in Figure 5.19

© 2006 SAP AG 20

Figure 5.19: Create directories for Oracle and SAP data

Figure 5.20: Missing Package Warning

In the above step, you can safely ignore the Warning and select to “Continue” the Installation

© 2006 SAP AG 21

Figure 5.21: Prompt for Script Execution

Figure 5.22: Script Execution

During the above step please make sure that the directory value mentioned is writable from the Zone and is included in the value of PATH environment variable.

Figure 5.23: End of Oracle Installation

© 2006 SAP AG 22

Figure 5.24: Resume SAP Installation

Figure 5.25: Specify DDIC User Password

Figure 5.26: Specify SAP* user Password

© 2006 SAP AG 23

Figure 5.27: SAP Installation Complete

Figure 5.28 Oracle Patch Installations

After the SAP installation is complete the Oracle 10g Database needs to be patched to Service Pack4. This is done by invoking the 'RUNINSTALLER' from the Oracle Patch DVD.

After the completion of the installation we verified the setup by making sure that each of the following components were installed and functioning properly.

• SAP NetWeaver Web Application Server ABAP.

• SAP NetWeaver Web Application Server J2EE.

• SAP NetWeaver Business Intelligence.

• SAP NetWeaver Enterprise Portal.

• SAP NetWeaver Development Infrastructure.

• SAP NetWeaver Mobile Infrastructure.

• SAP NetWeaver Process Infrastructure.

© 2006 SAP AG 24

Chapter 6 Installation Time Inputs

The following table gives the times taken for the major tasks during our internal Study.

Activities Duration (HH:MM)

1 Planning & Preparation Logical volumes, Volumes, File systems, FSS, Zones creation & configuration, NIS, DNS, inet Resource Pools, Parameter settings

02:00

2 NetWeaver 2004s Installation AS-ABAP, Oracle 10g DB, Oracle client, Oracle Patch AS-J2EE, EP, BW, BI, PI, DI, MI

14:33

3 Upgrade to Service Pack 6 (SR1) ABAP SP1->SP6, BASIS SP1->SP6 PI_BASIS SP1->SP6, SAP BW SP1-SP6 AS-J2EE, EP, BW, BI, PI, DI, MI SP4 -> SP6

06:09

4 Template Configuration CTC for BI, DI and BI SLD, ADS Manual Configuration

00:38

Total

23:20

As the figures above indicate, the entire process of complete setup of NetWeaver 2004s Stack with all the components, Updating to Service Pack6 and the complete Post Installation Configuration was completed in less than 24 working hours.

© 2006 SAP AG 25

Chapter 7 Conclusion

To summarize, SAP NetWeaver 2004s can be conveniently installed in a Solaris 10 Containers in less than 24 hours by following a few simple steps. The Tips and recommendation mentioned in the document helps you to avoid the problems and errors and enables quicker deployment of SAP NetWeaver 2004s on Solaris 10 Containers.

© 2006 SAP AG 26

Chapter 8 References

• SAP NetWeaver 2004s Installation guides http://service.sap.com/instguides

• SAP Note 851251 : SAP NetWeaver 2004s Installation on UNIX

• SAP Note 851169 : SAP NetWeaver2004s Installation on UNIX:Oracle

• SAP Note 870652 : Installation of SAP in Solaris 10 Zone

• SAP Note 724713 : Parameter settings for Solaris 10

• SAP Note 716604 : Access to Sun J2SE and recommended J2SE options

• Solaris Containers : http://docs.sun.com/app/docs/doc/817-1592

• Sun Fire V890 Server : http://www.sun.com/servers/midrange/v890/index.jsp

• Solaris Enterprise System : http://www.sun.com/solaris/

• Sun Bigadmin Portal : http://www.sun.com/bigadmin/home/index.html

• Oracle 10g database : http://www.oracle.com/database/index.html

• SAP Help Portal : http://help.sap.com/

© 2006 SAP AG 27

Disclaimer & Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.