The Graphic Hub solution consists of these applications:
The physical back end server where the database content is stored (see General Database Information).
Graphic Hub makes the database available to clients in a network. To log in and work with Viz Artist, a User must connect to a running Graphic Hub, on a machine in the network. In normal circumstances a Graphic Hub is started through the Graphic Hub Terminal, and shut down, logged in to or logged out of, from the Graphic Hub Manager.
Various parameters can be defined in the Graphic Hub Terminal before a Graphic Hub is started, for example the name and the data directory to where the database should have its root folder.
The integrated multi-user database serves as the central point for storing all assets of a standalone machine or for all machines. This asset management database provides efficient file-handling while maintaining data consistency.
Consistent data storage: Objects are always aware of their references and stay consistent where ever you move them. Accidental deletions of objects are prevented and scenes remain usable.
Reference model: Guarantees that changes of a special object/type affects all scenes using it, such as a corporate logo or font-style.
Flexible data organization: Organizing scenes and all relevant objects together in projects, simplifies the task of handling complex designs.
Data locking: Exclusive access to scenes or objects is assured by applying a lock.
Audio: Supports audio streaming.
Administrative tool Graphic Hub Manager: Serves to migrate archives and data pools from version 2.x. Graphic Hub Manager also serves as a tool for adding users, keywords, permissions, statistical information regarding disk usage, connected users and server traffic as well as assisting the user in finding duplicates.
User management: Enables you to protect crucial assets and track changes.
Search functionality: All object properties can serve as search criteria and new search keywords can be included.
Messaging/notification: Broadcast information to all connected clients via a customized notification system and/or online collaboration between single users.
Graphic Hub Terminal
The Graphic Hub Terminal is the user interface used to configure, start, stop and restart both Graphic Hub and the Graphic Hub Naming Service. See Graphic Hub Terminal.
A Graphic Hub Terminal is installed along with every Graphic Hub and provides the following functionality:
Starting, stopping and monitoring Graphic Hub and the Graphic Hub Naming Service processes.
Configuring Graphic Hub.
Status Display and monitoring.
Execution of scheduled tasks: shutdown (with automated backup), deletion of Journal Entries, deletion of expired items, cleanup of Viz Pilot data elements, cleanup of Viz Pilot changelog.
Backup and Restore.
Graphic Hub Manager
The Graphic Hub Manager is used to administer one or more Graphic Hubs. For example, the server files and access levels for users and groups can be managed from this application. See Graphic Hub Manager.
Graphic Hub Manager serves to:
Migrate Viz Pilot data from Oracle to Graphic Hub.
Migrate archives and data pools from version 2.x.
As a tool for adding users, keywords, permissions, statistical information regarding disk usage, connected users and server traffic as well as assisting the user in finding duplicate.
When you are running in a Main/Replication Cluster, you can check Server differences and Copy via DDC from one server to another.
Graphic Hub REST
The Graphic Hub REST is a web-service for a Graphic Hub. It is an interface to retrieve and send data to and from a Graphic Hub through HTTP requests. See Graphic Hub REST.
Supports browsing, administration, simple manipulation of datasets, monitoring, deploy agents, and much more. It provides the access to all data on a Graphic Hub. A client is able to retrieve any kind of metadata from Scenes, Images, etc., like Owner, Creation Date, etc. Also, all metadata, like Users, Types, Keywords, can be retrieved.
Graphic Hub REST is also an open HTTP API to Graphic Hub. Any skilled web developer and designer can build an application based upon the Graphic Hub Interface Agent. For example, if a scene from the Super Bowl contains an image of the quarterback, this image can be retrieved by an external application, like a blog, by a search on the Graphic Hub Interface Agent. The blogger is also able to insert this in an article and publish to the web.
Graphic Hub Deploy Agent
Upgrades the Graphic Hub solution with a powerful service to copy directories/projects/files with all necessary data (referenced directories/projects/files) from one server to another. See Graphic Hub Deploy Agent.
Graphic Hub Deploy Agent upgrades your Graphic Hub solution with a powerful Service to copy directories/projects/files with all necessary data (referenced files, directories/projects) from one server to another with different options of deployment. It is possible to have more than one agent running in your network environment. To copy between your servers, you can create tasks in Graphic Hub Manager. In these tasks you define the source and destination servers and properties of the deploy task.
It is possible to deploy to multiple destination servers. Every task can have different schedule modes. These modes are Once, Recurring, Recurring forever and Real-Time. So it is possible to distribute your Graphic Hub content according to schedule to all your servers automatically day by day.
Graphic Hub ImEx Agent
The Graphic Hub ImEx Agent (Import / Export agent) is a service that imports image media assets from file-system folders or HTTP sources to Graphic Hub. See Graphic Hub ImEx Agent.
Graphic Hub ImEx Agent upgrades your Graphic Hub solution with a powerful Service to stage (import) external media assets (images) available through HTTP through the Media Sequencer (MSE) to Graphic Hub through Graphic Hub REST. It is possible to have more than one agent running in your network environment that can utilize multiple Graphic Hub RESTs.
Dedicated destination directories can be configured. The import can be parallel on multiple Graphic Hub RESTs bound to the same Graphic Hub.