|
The services tier is the nucleus of the Enterprise Blocks architecture. Enterprise Blocks Services are APIs with a hybrid web services/object-oriented design. Each service has a set of methods that support a particular scope of functions. Calls to Enterprise Blocks services are made either directly or indirectly by programming individual classes themselves. These calls can be made using Microsoft .NET Remoting or from any client environment that can consume XML web services including Java/.NET/COM running on Windows or UNIX.
|
Although Enterprise Blocks services provide the entry and exit point for all information requested from a client, they do not work directly against any source environment. Service providers are the "connectors" or "adaptors" for these environments and provide the context for services within the Enterprise Blocks architecture. Services provide the interface for consumers and security and state management services for providers. Services load providers that interact with a specific environment and return data from that environment.
Download | Buy
|
|
Click here to see how the services and service providers fit into the architecture of Enterprise Blocks.
|
|
|
There are two types of Enterprise Blocks services and corresponding service providers. Each is described below.
|
Database Services
These services allow a client environment to interact with a target database retrieving both record data and meta data from the database. Click here for a listing and description of the different Enterprise Blocks database service providers.
|
Catalog Service
This service is used to organize and provide access to objects such as reports, charts, custom members, and saved filters stored inside a meta data repository. This repository can be any number of environments including an enterprise portal, a BI product report repository, or a simple Windows file system. Click here for a listing and description of the Enterprise Blocks catalog service providers.
|
