Technical Operations Manual of the SAP NW JDI 

This list leads you to the topics you need to administer the SAP NetWeaver Java Development Infrastructure (JDI).

In the SAP NetWeaver Java Development Infrastructure, you use the following services:

·        Common user management of the development infrastructure.

·        SLD and Name Service: in the System Landscape Directory, you find the Software Catalog and the landscape description; a Name Service, which guarantees the uniqueness of object names, is also located there.

·        CMS: You use the Change Management Service to configure the development environment in the JDI and to administer the software logistics.

·        DTR: You use the Design Time Repository to administer the source files.

·        CBS: You use the Component Build Service as the central build environment.

·        Tools for monitoring the development infrastructure are available.

Overview of the development process using the SAP NetWeaver Java Development Infrastructure.

User Management in the SAP NetWeaver JDI

The services of the JDI are tightly interwoven, which is why the authorizations for this environment are described together.

·        Configuring the User Management of the SAP NW JDI: To access the SAP NetWeaver Java Development Infrastructure, you need roles and permissions. You can create them separately for administrators, developers, guests, and so on.

System Landscape Directory and Name Service

The SAP System Landscape Directory (SLD) helps you to administer your system landscape. SLD is a server application with which a client application communicates entirely via Hypertext Transfer Protocol (HTTP). The SLD server contains component information, system landscape descriptions and a name reservation based on the Standard Common Information Model (CIM).

·        Administrative tasks: In order for the SLD service to work properly, you must perform the following administrative tasks for server administration and data management. This topic also describes how to set up and log on to the SLD.

·        Technical system landscape: You can use the Technical System Browser to display all registered application systems. From there, you can start other activities for technical systems.

·        Software Catalog: Gives you information on products and software components (SCs) and tells you how to define dependencies between software components.

·        Name reservation: To avoid name conflicts, the SAP System Landscape Directory (SLD) offers a name reservation service (also known as Name Server), which allows you to "reserve” globally unique names.

·        Data Supplier for the SAP System Landscape Directory: The Data Supplier for the SAP System Landscape Directory (SLD) collects data on the systems installed in its system landscape and sends it to the SLD.

Change Management Service

Administration of the Change Management Service. Introduces you to the documentation on CMS administration. You use the CMS within the entire JDI for configuring the development environment and for software logistics administration. You use the CMS to perform the following administrative tasks:

·        Configuring tracks: Tracks determine the frame data for the development based on components. You manage and edit tracks in the Landscape Configurator.

¡        Configuring a Domain

¡        Creating an XI Track

¡        Editing a Track

¡        Connecting Tracks

¡        Deleting a Track

·        Transporting and creating software component versions: You administer transports in the Transport Studio.

¡        Checking-In Archives

¡        Performing Imports

¡        Creating Software Component Versions (Assembly)

¡        Performing Quality Assurance (Approval)

Design Time Repository

The tasks you actually perform as an administrator in the DTR, also depend on the selected development scenario. In scenario 1, no CMS is used for software logistics, which is why you must perform many steps in the DTR manually; in other systems, these steps are performed automatically and are therefore not required in the DTR. If this applies for a task, it is mentioned below.

·        Administration of the Design Time Repository Server. Introduces you to the documentation on DTR administration.

·        User Authentication and Authorization in the DTR: For the DTR, you can grant permissions individually for each object.

·        Frequently required tasks in the DTR: You must perform these tasks more frequently if you do not use CMS. They are described here for the command-line client. For a list of all commands, refer to the command reference. To create workspace folders and workspaces and to maintain authorizations, you can also use the DTR administrator plug-in, which offers a graphical UI.
These tasks consist of:

¡        Creating workspace folders and workspaces: This is required only in scenario 1, in which no CMS is used.

¡        Finding and listing activities: This can be of advantage in all scenarios, but is especially necessary in scenario 1.

¡        Integrating activities: This can be of advantage in all scenarios, but is especially necessary in scenario 1.

¡        Managing propagation lists: This can be of advantage in all scenarios, but is especially necessary in scenario 1.

·        Logging: Administrators can find important information on the state of the DTR server in the DTR Server Log.

Component Build Service

The Component Build Service is available only in development scenarios, in which the entire JDI is used. For the software logistics, the CMS is used. This includes creating and preparing buildspaces for the development.

·        Administration of the Component Build Service Server. Introduces you to the documentation on CBS administration.

·        CBS Web UI: The Component Build Service (CBS) provides a web user interface that can be used both by developers and administrators. With the CBS Web UI, users can view the state of the various entities of the CBS like buildspaces, compartments, build requests, activities, development components, build variants etc.

·        CBS command-line tool: The CBS command line tool is an addition to the CBS Web UI. It allows retrieving CBS status information and performing administrative tasks in a shell-oriented environment. Besides using this tool in an interactive mode it can also be embedded into batch processing. Here, you find an alphabetical list of the commands in the CBS command-line tool.

The CBS command line tool provides some commands, which are related to software logistics. These commands are the following:

·         downloaddcarc

·         downloadsca

·         uploaddcarc

·         uploadsca

It is strongly recommended not to use those commands to bypass CMS. You should execute all tasks related to software logistics in the Change Management Service.

·        Configuring the Component Build Service: Provides information on:

¡        Checking Access to the Component Build Service

¡        CBS Logging

¡        CBS Service Properties

¡        Database Tuning

·        Troubleshooting in the CBS

Monitoring the SAP NetWeaver JDI

Monitoring the SAP NetWeaver Java Development Infrastructure: Offers several tools to monitor the functions of the SAP NetWeaver Java Development Infrastructure:

·        Monitoring the SAP NetWeaver JDI with JARM (Java Application Response Time Management)

·        Monitoring the DTR and CBS with JMX (Java Management Extensions)

·        Monitoring the SAP NetWeaver JDI with GRMG (Generic Request and Monitoring Generator)