|Oracle Dynamic Services User's and Administrator's Guide
Part Number A88783-01
A storage place that maintains the application security profile governing service access. Registering service consumer applications allows the service administrator to choose the services that are to be visible to a particular application.
A Lightweight Directory Access Protocol (LDAP) registry that is the main registry that can communicate with multiple Dynamic Services engine instances each containing its own registry cache. Using the DSAdmin utility, a service administrator can update the central master registry, broadcast a message to all other instances of Dynamic Services engines to manually synchronize their registry cache with the central master registry. Using a central master registry in this manner increases the scalability of Dynamic Services.
A service package that invokes one or more other services and typically includes one additional file, a jar file, which contains all Java classes and stylesheets needed by the compound service package.
The unique name of a directory entry in Oracle Internet Directory (OID). It includes all the individual names of the parent entries back to the root. The Distinguished Name tells you exactly where the entry resides in the directory's hierarchy. This hierarchy is represented by a directory information tree (DIT).
A component of the Internet computing model that delivers a specialized value-added function. A dynamic service typically comprises some content, or some process, or both, with an open programmatic interface.
An engine that provides storage, access, and management of dynamic Internet and Intranet services.
An open, Java-based programmatic framework for enhancing Oracle as the Internet platform to incorporate, manage, and deploy dynamic Internet services. The framework includes a Dynamic Services engine, a set of dynamic services, and users of these services (service consumer applications). Oracle Dynamic Services makes it easy for application developers to rapidly incorporate existing services from a variety of Web sites, local databases, or proprietary systems into their own applications.
Handles communication using either HTTP, HTTPS, or Java Messaging Services (JMS) communication protocol between the service consumer application and the Dynamic Services engine, which is running in the Dynamic Services gateway. Because the Dynamic Services Java client library does not contain the Dynamic Services Java engine, the Dynamic Services Java client library is referred to as a Dynamic Services thin Java client library. This is the Java (HTTP/JMS) deployment view of the Dynamic Services framework.
Handles communication using direct Java calls between the service consumer application and the Dynamic Services engine. When the Dynamic Services Java engine is running on the machine hosting the service consumer application it is using the thick Java client library, which contains the Dynamic Services Java engine. This is the Java deployment view of the Dynamic Services framework.
A routine that executes a service request in a particular flow. A flow could be as simple as relaying a request, to contacting a service provider, or as complicated as relaying a request to a service provider and relaying the response to another service provider.
A routine that post-processes the service input from service consumer applications to produce the standard service input that is fed to the underlying service.
A set of services (profiler, logger, and smartlog) that are configured in the MonitorProperties.dss file for monitoring event messages generated by the Dynamic Services engine.
A routine that transforms the raw output from the underlying service into the standard service response.
A routine that transforms the standard service request into the input needed by the underlying service, using the underlying protocol.
A component within the Internet computing model that delivers a specialized value-added function.
The person who performs administrative tasks for the Dynamic Services engine, such as enabling or disabling of services, tuning caching parameters of a service, and so forth.
An application that uses Dynamic Services to collect Web services from service providers and provide a dynamic service to their customers.
An XML schema file that defines the behavior of a service and contains service developer information, a description of service features, service management information, service input adaptors, service output adaptors, and other service provider-specific information, such as secure access, caching parameters, and so forth.
A business partner or application developer who provides and manages the content of a service for the Dynamic Services execution engine; typically, the service provider is the owner of some data resource or process, such as, the owner of a currency exchange rate Web site. Also, someone who provides content for a service.
A storage place that maintains the service package information of registered services that enables Dynamic Services engines to set up and execute a service and access distributed sources from service providers.
A service that is bundled into a simple service package and modeled as a local directory. This directory contains at least a
MANIFEST file that points to the service descriptor XML file, which is the key XML document that describes the service and points to the following descriptor (.xml) and definition (.xsd) files: