Database Reference
In-Depth Information
customizations, support packages, and new releases. This dilemma is solved by using an integrated
SAP Java Development Environment (JDI) that consists of a central source file storage location
(DTR) and executing the build for the entire software via a central build service (CBS).
SAP JDI environment consists of
◾
System Landscape Directory (SLD) that defines the products and its software components
◾
Design Time Repository (DTR) that administers the source files
◾
Central Build Service (CBS) that administers the archives (runtime objects)
◾
Change Management Service (CMS) that arranges the access to the source and object files
via DTR and CMS
The issues cited previously get further exacerbated when customers customize delivered prod-
ucts to suit the specific requirements of their enterprise, business units, or operational sites. This
dilemma is solved by the DTR, which has inherent facilities to detect such version conflicts even
after the files have been transported into production.
All these problems are addressed and handled adequately by the SAP NetWeaver JDI through
the very architecture and structure of the product coupled with the engendered development pro-
cess enabled by the various development tools of the SAP JDI environment.
11.2.1 SAP Java Development Infrastructure (JDI)
As collaborated development is very critical for large teams of developers and since existing Java
development environments did not provide an equivalent centralized development environment
like the ABAP Workbench, SAP embarked on an effort to build a reliable and efficient equivalent
environment in Java called the SAP Java Development Infrastructure (JDI). It consists of tools
like DTR, CBS, and CMS that support team-based software development in Java within the
SAP world and are directly integrated with the Integrated Development Environment (IDE), the
NetWeaver Developer Studio (NWDS). The development follows the SAP component model.
The JDI environment is available in SAP Web AS 6.40 and later versions and includes compre-
hensive features for version management, change management, and automated deployment of
components.
NWDS is the centralized place for developing presentation logic accompanied by the cor-
responding business logic including data persistence and retrieval. NWDS has evolved into a
comprehensive SAP development environment that spans across the whole cycle of a Java proj-
ect including configuration and transport management. It provides full support for developing
large-scale Java projects as well as standard technologies like J2SE, J2EE, XML, and Web Services
and SAP technologies like Web Dynpro and Java Dictionary. Large projects are apportioned into
a number of projects sharing clearly defined dependencies. These projects can be undertaken by a
large number of teams distributed across geographical distances.
JDI represents the main difference of the NWDS from other Java IDEs. It makes it easy
for developers to collaborate and enables NWDS to support hundreds of programmers within a
project. JDI links the central and local development environments. A simple file import makes
the project development objects available centrally. These objects can be transferred into the local
environment, creating a flexible development environment wherein Java developers can continue
to work locally, while the central development environment provides the necessary synchroniza-
tion for teamwork.
