note 737368 - hardware requirements of java development infrastructure.pdf

8/22/2019 Note 737368 - Hardware requirements of Java Development Infrastructure.pdf

http://slidepdf.com/reader/full/note-737368-hardware-requirements-of-java-development-infrastructurepdf 1/5

06.08.2013 of 5

SAP Note 737368 - Hardware requirements of JavaDevelopment Infrastructure

Note Language: English Version: 7 Validity: Valid Since 16.07.2012

Summary

Symptom

You plan to use the SAP NetWeaver Development Infrastructure (NWDI) to

develop your own Java applications or to adjust Java applications delivered

by SAP.

Other terms

Sizing, hardware requests, system requirements

Reason and Prerequisites

To use the NWDI, the NWDI components must be installed on one or several

NetWeaver servers. Various factors determine how many servers you require

and how the individual servers have to be set up. This note describes the

configurations recommended by SAP.

Solution

The NWDI consists of the following components:

o DTR - Design Time Repository

o CBS - Component Build Service

o CMS - Change Management Service

These 3 components are always installed together on a NetWeaver, but they

can be used separately. In this way, you can distribute the NWDI components

between several servers. The components you have to use and the number of

servers you need for this essentially depends on which of the NWDIscenarios you use, and how many developers work simultaneously with the

NWDI. For a description of the scenarios, see the manual "Working with the

SAP NetWeaver Java Development Infrastucture".

Scenario 1: Development in a team

In this scenario, only the Design Time Repository (DTR), which is installed

on a J2EE server, is used. Test operation:

Test operation:

For testing purposes with 1-5 developers, we recommend that you install the

DTR on a server with a processor and 1 GByte RAM.

Production operation:

For the productive use of scenario 1, we recommend that you install the DTRon a server, which should be set out as follows:

o 1 - 10 developers: 1-2 processors; 1-2 GByte RAM

o 10 - 50 developers: 2 processors; 2-4 GByte RAM

o > 50 developers: 4 processors; 4-8 GByte RAM

Scenario 2: Development with components

The same recommendations apply to this scenario as to scenario 1. This

scenario optionally provides for the use of the System Landscape Directory

(SLD). In this case you can use an existing SLD in your landscape, or youcan use the SLD on the server on which you install DTR.



06.08.2013 of 5


Scenario 2+: Development with a Track

All NWDI components and the System Landscape Directory are needed for this

scenario.

Test operation:

For testing purposes with 1-5 developers, all NWDI components and the SLD

are installed on a J2EE server. A server with 1-2 processors and 2 GByteRAM is recommended.

Production operation:

All NWDI components are generally installed on a single server to use

scenario 2+ live. The SLD can also be installed on this server, or you can

use an SLD that is already a part of the landscape. Depending on the number

of developers and the expected load, the following configuration is

recommended:

o 1 - 10 developers: 2 processors; 2-4 GByte RAM; 500-1500 SAPS

o 10 - 50 developers: 4 processors; 4-8 GByte RAM; 1500-2500 SAPS

o > 50 developers: 4-8 processors; 8 GByte RAM; 2500-5000 SAPS

If you would like to modify applications delivered by SAP (for example,

Employee Self Services), a server with at least 4 processors and 4 GByte

RAM is recommended even if only few developers are supposed to work with

the NWDI.

Can the NWDI server also be used for other tasks?

A system landscape is planned for scenario 2+, which consists of a central

development system, a test system and a production system. With certain

restrictions, the server that is used as a test system can be used also as

an NWDI server. On the other hand, using the production system or the

central development system as NWDI server is not recommended. When you use

the test system as an NWDI server, consider the following:

o Depending on the type of the application that you develop or use,

the execution of the application in the test system will impair the

performance of the NWDI. For example, the developers must expect

worse response times when checking in and checking out files.

o Some components delivered by SAP, like Guided Procedures, require

you to restart the server during deployment. The deployment of such

components onto the server where the NWDI is installed is not

currently possible with the NWDI. The deployment of these

components can be carried out using SDM only. Therefore, the

quality assurance process planned in scenario 2+ cannot be used forthese components.

If many (> 50-100) developers are working with the NWDI or if a very high

number (more than 10,000) of development components are being processed and

the performance is insufficient even though you are using a separate NWDI

server with 8 CPUs and 8 GByte RAM, for example, you can improve the

performance by storing the Component Build Service on a separate server.

This is described in the following section for scenario 3.

Scenario 3: Layered development

Usually you will begin with scenario 2+ and add more tracks to the

development landscape. Therefore the same recommendations apply initially

to this scenario as to scenario 2+.If you have performance bottlenecks, because, for example, meanwhile more

developers are working with the NWDI than first planned and your hardware



06.08.2013 of 5


is not set up for this, you have several options to improve the

performance.

1. Transferring the Component Build Service (CBS) to an extra server:

A considerable part of the load on the NWDI server is caused by the CBS.

Therefore, it is useful to configure the CBS on a separate server, as soon

as there are performance bottlenecks on the existing NWDI server. In

comparison with moving DTR or CTS, moving the CBS for existing tracks is

possible without a lot of effort. Therefore we recommend that you firstly

transfer the CBS to another server when there are performance bottlenecks

with existing tracks.

Note: CBS is optimized for use on a server with several processors and for

use on a cluster. Therefore, when there are performance bottlenecks with

the CBS, it is useful to add further clusters to the CBS server or to

increase the number of processors of the existing servers.

The following is a recommendation for the hardware for a separate CBS

server:

o Up to 50 developers and up to 10,000 development components (DCs): 4

processors; 4-8 GByte RAM; 1500-2500 SAPSo 50-150 developers and 10,000-40,000 DCs: 4-8 processors; 8 GByte RAM;

2500-5000 SAPS

o More than 150 developers and more than 40,000 DCs: 8 processors; 8

GByte RAM; more than 5000 SAPS

2. Using several CBS or DTR servers:

If you need several tracks, in which many (> 50-100) developers are

supposed to work, it is useful to distribute the load onto several DTR and

CBS servers. For each track you can determine which DTR and CBS server are

used.

To ensure that system performance is satisfactory, adhere to the following

guide values:

DTR:

We recommend to run the DTR server with three cluster nodes. The capacity

of the used database and the size of the managed data have a significant

impact on the performance of the DTR. The number of active developers has a

minor impact. The following recommendations apply to a server with the

following hardware:

o 64-bit system

o 16 processors

o 64 GB RAM; 48 GB of these are used for the database

With this, you can efficiently manage a compressed data volume of

approximately 150-200 GB (this corresponds to approximately 400 GB grown

data volume) if the database runs on an RAID 1 system. The size of the

temporary tablespace should be approximately 5% of the data volume. It is

essential that the table statistics are renewed every day; all data records

must be taken into account during this (usually, the number of data records

that are considered is reduced to 1% or lower for large data volumes,

depending on the manufacturer). In addition, an administrator should carry

out a specific configuration of the database; for this, no generalrecommendations can be made.



06.08.2013 of 5


Note: If you use several DTR servers, note that with transports between

different DTR servers, the data must be exported and imported, which is not

necessary with transports within a DTR server. Therefore it is useful for

tracks, between which you expect a high volume of transport (for example,

development and repair tracks), to use a common DTR server.

CBS:

During the compilation, a high number of temporary data is created and kept

on the hard disk. A data carrier with a good I/O performance has a positive

impact on the performance of the CBS. We recommend the following hardware:

o 64-bit system

o 8 processors

o 32 GB RAM

With this, you can set up approximately 500 development components per

hour. We recommend that you compile the source code assigned to a CBS at

night to free the required capacity for the activation requests of the

developers during the day. If you assume that no development takes place

for eight hours, you have a guide value of 4000 development components for

each CBS. This value can be increased by using several data carriers per

CBS server for the temporary data and by increasing the number of cluster

nodes accordingly.

To summarize:

< Less than 50-100 developers:

o All JDI components on a server

More than 50-100 developers:

o 1. Expansion phase:

- Expansion phase: A server for CMS and DTR

- A server for CBS

o 2. Expansion phase:

- More servers in each case for DTR and CBS

Caution: If you use several servers for the NWDI, then you must make sure

that these servers are always on the same Support Package level.

Header Data

Release Status: Released for Customer

Released on: 16.07.2012 10:23:11Master Language: German

Priority: Recommendations/additional info



06.08.2013 of 5


Category: Installation information

Primary Component: BC-CTS-DI Development Infrastructure

(NetWeaver)

Secondary Components:

BC-CTS-DTR Design Time Repository

BC-CTS-CBS Component Build Server & Component

Infrastructure

BC-CTS-CMS Change Management Service

The Note is release-independent

Related Notes

Number Short Text

1145663 Initial Configuration of Usage Type DI: Common problems

956078 CTC Installer - Usage Type DI

889038 Collective note: NWDI server component configuration

865160 NWDI server configuration: DB2 UDB database parameters

848708 Oracle Database Configuration for NWDI server

note 737368 - hardware requirements of java development infrastructure.pdf

Documents