Database Reference
In-Depth Information
NWDS also supports a local development process that does not utilize the JDI,
refrains from external referencing, and, in the absence of a central repository, also
stores all the project resources locally.
JDI environment consists of two parts: local and central. The local part consists of the NWDS
as the IDE, the local system as the temporary storage for all new development objects, and usu-
ally a local installation of the J2EE as a testing environment. The NDWS connects the developer
to the other part, the central JDI. The SLD is used to load the development of the corresponding
configuration of the CMS into the NWDS. This enables access to both the source file storage in
the DTR workspace for regular work and the buildspace in CBS. Created objects are checked by
the name service for the uniqueness of the name. The CMS is used for deployment to the central
system. The development cycle within JDI starts with the import of a development configuration
file into the NWDS. The local system is synchronized with the centralized DTR and the CBS.
This is followed by the usual development process involving local application development, build
process, and automatic deployment to the test environment. After a successful test, the objects are
checked into the DTR. Once the central build of the archives is run, they are automatically loaded
into the CBS that initiates the build process. Once the central build is successful, the elements are
released automatically.
NWDS provides an optimum infrastructure and tools to access a centralized deployment and
test environment. The facilities of JDI enable easy implementation of reusability and maintenance.
Control of distributed versions coupled with access to the corresponding development objects
enables efficient management of large geographically distributed projects.
11.2.1.1 Overview of the Development Process in SAP JDI Using SAP NWDS
We present an overview of the release cycle using SAP NetWeaver Developer Studio (NWDS)
and Java Development Infrastructure (JDI).
The development process is given as follows:
1. A product release is defined in the SLD with details of name, release, and used Software
Components (SCs) along with the constituting development components (DCs) and the
corresponding use dependencies.
2. The corresponding
track
is created for this release in the CMS consisting of logical devel-
opment systems that define the access to the source files and archives (runtime objects)
required for the project.
3. Central Development Environment:
a. SLD is used to import the development configuration using the name and URL of
the configuration into every local development environment NWDS of the developer
group.
b. Download into local NWDS by synchronizing the source files from DTR.
c. Download into NWDS by synchronizing the archives (runtime objects) from CBS.
4. NWDS Local Development Environment:
a. Create new objects (DCs or packages) or check out the existing ones and change them.
b. Call Name Service to ensure uniqueness of names while creating new objects.
