Using Runtime Services 

Purpose

The server platform comprises a series of Web Dynpro runtime services, which you can use to customize a Web Dynpro application. The abstract description of these Web Dynpro runtime services is known as the Server Abstraction Layer (SAL). Because the Web Dynpro runtime environment accesses the individual services using corresponding interfaces, the runtime environment remains independent from:

·        The server-platform implementation

·        The underlying application server

·        The technological infrastructure

In general, each service contains two interfaces: One interface is visible for the Web Dynpro application and is located in the api subpackage. The second interface is only visible to the Web Dynpro Framework and is located in the core subpackage.

The following services are available for the customizing of your Web Dynpro application:

·        Deployment

·        Configuration

·        User Management

·        Internationalization

·        URL Generation

·        SAP Java Connector Client

·        System Landscape Directory

The Java packages described below represent the individual Web Dynpro runtime services. The short description of the packages gives you an idea of the service features.

Service	Package	Description
Deployment of the Application	com.sap.tc.webdynpro.services.sal.deployment	Supports accessing deployable objects.
Configuration	com.sap.tc.webdynpro.services.sal.config	Enables you to read configuration data.
User Management	com.sap.tc.webdynpro.services.sal.um	Provides the authentication of users, authorizations, roles, and user profiles.
Internationalization	com.sap.tc.webdynpro.services.sal.localization	Supports processing language-specific resources.
URL Generation	com.sap.tc.webdynpro.services.sal.url	Generation of Web addresses (URLs) for Web Dynpro applications and Web sources.
SAP Java Connector Client	com.sap.tc.webdynpro.services.sal.jcoclient	Enables you to describe the settings for accessing a back-end system using the SAP Java Connector (JCo).
Administration	com.sap.tc.webdynpro.services.sal.admin	Returns system information.
System Landscape Directory	com.sap.tc.webdynpro.services.sal.sl	Supports accessing the System Landscape Directory (SLD).
Web Context Adapter	com.sap.tc.webdynpro.services.sal.adapter	Returns methods with which you can access the URL parameter of a request.
Look and Feel	com.sap.tc.webdynpro.services.sal.laf	Returns methods with which you can access the optical appearance of an application.

Accessing the Web Dynpro Runtime Services

The top-level Java package, in which the Web Dynpro runtime services are defined, is com.sap.tc.webdynpro.services.sal.

The agreed naming convention is: All interfaces visible to the application start with the prefix IWD and all classes visible to the application start with the prefix WD (WD stands for Web Dynpro).

To be able to access the individual services, each service has a class that provides static methods for the creation of the requested services and their access. The following source code text allows access to the development service:

Source code example:

/** All used classes are contained in package   com.sap.tc.webdynpro.services.sal.deployment.api   get deployable object for deployed application “Test” using factory */ IWDDeployableObject deplObj =    WDDeployableObject.getDeployableObject(“ Test ”);

For more information, including a definition of the deployable object, see Deployment Service.