
Mediator is based around an SOA (Service Oriented Architecture) design. All services are controlled by the central application server cluster. To enable Mediator to work well in a wider business, much of its functionality can be integrated using web service calls. These web service calls are delivered using XML over IP and can be used, for example, to query material metadata, start a transfer, notify workflow states or update a schedule.
The Pharos Mediator user interface is based on the latest web based technologies. The interface is presented to the user as a Flash application written using Adobe Flex. As the system become global, software updates no longer need to be deployed to every Mediator desktop. For client desktops, Mediator requires Flash, Java and QuickTime to be installed. All of which are downloadable from the Internet.
A base installation of the Pharos Exception alarm monitoring system is delivered as part of every system, offering group alarms for each blade and enclosure, giving notification to users of potential problems. Additional grouping, filtering, user notification and SNMP management is available through the full Exception product.
The Pharos Information Centre is a centralised web based administration tool for maintenance and configuration. In addition to local access, it allows Pharos Support Services to remotely administer Pharos systems. It is from here that the Alarm Viewer can be accessed to display all raw and group alarm data.
Mediator offers customers a significant reduction in setup costs through the new network based installation routines. The entire system including OS, database engine and Pharos software is deployed via an unattended install in a matter of hours.
Mediator is designed to be easily deployed, configured and maintained. Information gathered at the system's design stage is used to help auto-configure metadata schemas, transfer paths, transcoding profiles and other complex system attributes. All additional configuration is performed using the Pharos Information Centre and is stored centrally to allow fast restores should hardware failure occur.
Uploading of software upgrades is performed via the Information Centre. The new data is kept and can be reviewed from a web browser, and made live when the system Administrator decides. The old software and data is archived and can be rolled back or forward at any time should an issue arise.
The system can be easily expanded by the adding of additional blade servers. All expansion can be undertaken while the system is fully active. Once the configuration has been saved to the Mediator Core, the new functionality will be ready for use.
Should a blade fail, a pre-built replacement blade server is loaded in place of the faulty hardware. Since all configuration data is held centrally on the Mediator Core, the blade server will retrieve the current configuration and run the required processes within minutes.