Services Overview 

The J2EE Engine contains the following services by default (in alphabetic order):

●      ABAP Communicator – this service is used by SAP Web AS to start and stop the J2EE Engine and to send information from the J2EE Engine to the Web AS

●      Administration Adapter – this service is part of the distributed services level of the JMX infrastructure. It provides a remote connection to the MBean server, as well as interfaces for working with the MBeans registered by the Basic Administration Service.

●      Application Client – runs deployed application clients by invoking their main() methods. It starts a separate Java Virtual Machine (JVM) for each application client. In addition, the Application Client Service provides communication with the system services that the application clients need.

●      Application Locking – this service is used by J2EE applications when they want to set or release a lock. The service acts as an interface for the applications to the locking manager and the enqueue service.

●      Basic Administration – provides instrumentation of the kernel and the server components (services, libraries and interfaces). It also registers MBeans that can be used for management of a single cluster node or of the whole cluster.

●      Bi/mmr/deployer – deploys metamodels and metadata of the metadata model repository (MMR).

●      Caf/runtime/connectivity/impl – executes and manages configuration data for external operations using RFC and SOAP.

●      Caf/um/metadata/imp – allows the deployment of UME metadata.

●      Caf/um/relgroups/imp – adds major type implementation to the UME.

●       ClassLoader Viewer – this service graphically displays the relations between different loaders on a selected cluster element

●      Classpath Resolver – use this service to set dependencies to the Compilation Library API from any J2EE Engine component. You can point the dependency that is required by the library to compile the source, that is, to point the JARs in the naming required for the compilation.

●      Configuration Adapter – enables you to manage the Configuration Manager and the configuration objects in the database. It uses the interfaces that the Configuration Manager provides, enabling you to access and modify configurations.

●      Connector Container – manages the overall connectivity to back-end resource systems. It provides a runtime environment for resource adapters that enable you to connect to heterogeneous Enterprise Information Systems (EIS).

●      CentralUnificationLayer – enables the technical configuration of a system.

●      Deploy – manages the deployment of J2EE applications and the distribution of their modules to the corresponding containers across the cluster

●      Destination – specifies the HTTP(S) or RFC connections initiated by the J2EE Engine. Destinations for Web services are created automatically using this service.

●      Distributed Statistics – writes distributed statistics records (DSRs) and forwards them to the CCMS agent

●      Document Services Binaries – provides a common services infrastructure to the Adobe document services.

●      Document Services Data Manager – provides common data services to the other Adobe document services.

●      Document Services DestProto Service – provides support of the SAP “destination” protocol to the XML Form Manager service.

●      Document Services Configuration – provides a configuration UI for the Document Services Trust Manager Service.

●      Document Services Font Manager – container for providing fonts on the server.

●      Document Services License Service – provides the License UI and validation for the Adobe document services.

●      Document Services License Support Service – provides the database support for caching and licensing.

●      Document Services Trust Manager Service – provides support to the PDF Manipulation Module for certificates, credentials, trusted roots, passwords, and certificate revocation lists.

●      EJB Container – provides options for the administration of the J2EE Engine EJB Container and the enterprise beans running on the J2EE Engine EJB Container at runtime

●      File Transfer – this service is used to upload or download files on J2EE Engine

●      HTTP Provider – carries out the communication over HTTP protocol and provides a functional HTTP-based web server implementation. It is closely related to the Web Container Service and represents the underlying communication module that transfers HTTP responses back to the client.

●      HTTP Tunneling – transfers information over an HTTP protocol and provides features for proper remote communication between the client and a particular service if a proxy or a firewall stands between them

●      IIOP Provider – provides an implementation of the standard Internet Inter-ORB Protocol (IIOP) used for interoperability between CORBA and Java objects. It is also capable of serving Java-to-Java remote objects communication.

●      JDBC Connector – a resource adapter based on the Java Database Connectivity (JDBC) standard that enables you to connect to databases. It provides functions for creating and managing DataSource objects, as well as database connection pooling.

●      JCo RFC Provider – processes ABAP to Java requests. It dispatches the calls to a stateless session bean, which is registered in the J2EE Engine naming system

●      JMS Connector – provides connectivity to Java Message Service (JMS) systems. Enables the use of JMS resources in both local and distributed transactions.

●      JMS Provider – enables you to manage the JMS destinations and connection factories on J2EE Engine

●      JMX Adapter – manages the configuration and lifecycle of the MBeanServer and provides access to it for applications, services, and libraries

●      JMX Notification – this service is responsible for the distribution of the MBeanServer notifications throughout the cluster. MBeanServer notifications inform all the clients within the cluster about recently registered MBeans and the removal of MBeans from the MBeanServer.

●      JNDI Registry – a connected set of contexts of the same type that perform naming-related operations. The service provides functions based on the JNDI 1.2 Specification, as well as some additional features related to its work in a cluster.

●      Java Mail Client – allows you to add e-mail and news capabilities to applications deployed on the J2EE Engine. The service provides APIs for access to SMTP, POP3, IMAP4, and NNTP mail servers, for transporting, storing, and accessing a message or news on Internet or your network.

●      Key Storage – enables you to manage certificates and credentials on the J2EE Engine

●      Licensing Adapter – provides a runtime control for licensing the J2EE Engine.

●      Leak Detector – used to analyze memory problems by tracking the size of the Java collections.

●      Locking Adapter – establishes the interface between the J2EE Engine and the Enqueue Service. You can display and manage locks, carry out tests, and display statistics. See Managing Locks.

●      Log Configurator – enables the initial configuration of logging and tracing for server components. Provides means for runtime management of the logging and tracing configuration and for configuration of logging and tracing for applications that are deployed on the J2EE Engine.

●      Log Viewer – provides an interface for the Log Viewer clients (Online Log Viewer in the Visual Administrator, Standalone Log Viewer, Logs and Traces plug-in in the SAP NetWeaver Administrator) to query and read the logs on the J2EE Engine.

●      Memory Info – stores information about the level of memory usage in J2EE Engine

●      Message Info – this is the interface between the J2EE Engine and the Message Server. You use it to monitor and administrate the Message Server.

●      Migration Service – used by the migration framework for migrating applications between major releases of the J2EE Engine.

●      Monitoring – creates monitors responsible for monitoring all J2EE Engine vital parameters. Provides a runtime control for displaying the monitored data.

●      Performance Tracing – provides the ability to use traces for carrying out problem analysis. Through the Performance Tracing runtime you can manage application traces, single activity traces (SAT), application response times, SQL traces, and HTTP sessions tracing.

●      P4 Provider – provides the implementation of the SAP specific P4 protocol for communication between Java remote objects. This protocol is an alternative of the standard Java RMI protocol for Java-to-Java remote communication.

●      PDF Manipulation Module - Low Encryption – provides capabilities for manipulating the data in PDF files.

●      PMI Service – is necessary in order to use the SAP Process Monitoring Infrastructure from within the J2EE engine. The PMI Service collects the data from PMI Java agents and sends them to the central monitoring system.

●      Remote Object Container – a container for the implementations of the server-side remote objects. It manages the life cycle of those objects, and provides them with access to the existing protocols for remote objects communication on the J2EE Engine (such as P4 and IIOP protocols).

●      Runtime Info Provider – provides a list of runtime properties to be used by the system components

●      SAML – the J2EE Engine supports the use of the Security Assertion Markup Language (SAML) for Single Sign-On. SAML is an XML-based document format that is being developed and standardized by the Organization for the Advancement of Structured Information (OASIS). It is used for exchanging security-related information between communication partners.

●      SLD Data Supplier – manages the data transfers to the System Landscape Directory (SLD) server

●      SSL Provider – implements the Secure Sockets Layer (SSL) protocol, which provides privacy and secures the connection between two communicating applications.

●      Secure Storage – applications and services can use this service to encrypt and store sensitive data, such as passwords.

●      Security Provider – enables you to manage the security policy, the users, the authentication and authorization mechanisms on the system, and to restrict access to the resources or the applications deployed on the J2EE Engine.

●      Session Failover – carries out serialization of HTTP sessions and supports failover for both stateless and stateful objects.

●      Shell Administration – provides the core commands for the Shell Console Administrator.

●      Telnet Provider – provides Telnet clients with remote administration using the Telnet protocol. It offers a distributed, scalable Telnet server that supports remote shell administration performed by Telnet clients.

●      Timeout – this service is a non-distributed system used only internally by the J2EE Engine.

●      Transaction – The Transaction Service manages all transactions on the J2EE Engine server elements.

●      TREX – The TREX service is a service in the J2EE Engine by which an SAP application can access the search, retrieval, and classification functions of Search and Classification (TREX). The TREX service is technically implemented as the TREX JAVA Client, which communicates with the TREX Web Server by HTTP/HTTPS. The TREX Web server then forwards requests from the application to the TREX server.

●      User Storage – provides the default user store on J2EE Engine. This service is used by the Security Provider Service and can also be used by the security implementations of the Java Connector Architecture.

●      Virus Scan Provider – provides functions for defining a virus scanner, virus scan type, virus scan adapter and server.

●      Web Services Security – handles the security information for Web services

●      Web Container – represents a container that provides managed environment for running Servlets and JavaServer Pages. Enables Web applications life cycle management and helps developing and running session- and security-aware Web applications.

●      Web Services Container – provides a set of options for configuring specified Web services

●      User Management Engine– initializes the User Management Engine (UME) according to the properties maintained in its property sheet. It is also responsible for the creation of the UME default roles.

●      WebDynpro – a container for Web Dynpro applications. It is responsible for the loading of the Web Dynpro runtime environment on J2EE Engine.