Konica Minolta BIZHUB C30P - Manual (Page 20)

Installing MetaConsole
page 6
MetaConsole Architecture
The MetaConsole application architecture is three-tiered. Its major components are:
• MetaConsole Client: the front-end component that integrates with the console (or, in the
case of MetaConsole J, with the browser playing the console’s role).
There is one client per console managing all supported devices.
• MetaConsole Server: the back-end component that communicates with both the Meta-
Console clients and with the devices to be managed.
A MetaConsole server acts as an agent collecting data from the MetaConsole clients. It
can route queries and responses to and from other MetaConsole servers. A server that
acts as a proxy in this way is the preferred server for the client.
• MetaConsole Service Providers (referred to as PageScope EMS Plug-Ins in this User’s
Guide): these contain the knowledge necessary to communicate with a managed device
or service.
Figure 1.1 illustrates the relationship between the MetaConsole components and their various
functions:
Figure 1.1: MetaConsole Architecture
CONSOLE
Console Interface
DEVICE
MetaConsole
SERVER
Console-Specific Protocol
HTTP Client Layer
User
Interface
HTTP Request/Response containing XML
queries routed through the preferred server
HTTP Server
XML Query/Response
Service
Mapping
File
Translation
XML
Service Provider
Device Specific Protocol
CLIENT