Administering BIRT iHub System

An administrator creates, configures, and manages users, user groups, files, and folders, including assigning and updating privileges and managing group memberships. User and user group privileges selectively control access to the volume and its data objects.

Each node in an iHub cluster has a job scheduler and dispatcher. The job dispatcher sends jobs to the local resource group factories.

In this loosely coupled cluster model, the dispatcher sends a job from the pending queue to available factories, balancing the load across the cluster. Multiple job schedulers running on the nodes in a cluster allows the systemto scale processing to handle a large number of scheduled jobs at the same time.

BIRT iHub Logging and Monitoring System (LMS) can capture usage and error information in log files to assist a system administrator in evaluating resource usage and troubleshooting problems. The usage and error logging applications are open framework applications, which are available as DLLs in Windows and shared libraries in Linux.

It is best to set up the iHub system so that System Console and the LMS server are on a separate computer. This allows system administrators to access system logging information when iHub is busy, and also reduces the memory requirements on the iHub computer.

The system administrator can run the installation program to configure BIRT iHub. Each cluster node gets its configuration from a template in acserverconfig.xml, located in a shared configuration directory. Nodes with the same cluster ID, running on the same sub-net, automatically detect and join each other to form the cluster.

Using BIRT iHub Integration Technology scripts and tools to develop client applications and extend functionality

The Actuate Information Delivery application programming interface (IDAPI) supports integrating and administering BIRT iHub using extensible markup language (XML) and the simple object access protocol (SOAP). Using the IDAPI, developers can create an application that performs such tasks as scheduling a custom event or running a Report Server Security Extension (RSSE) application to manage users and user groups in an external system, such as LDAP or Active Directory.

A BIRT iHub administrator uses the System Console, Visualization Platform, command-line utilities, and Integration Technology components to perform these tasks.

Please consult the following iHub documentation for more information on how to administer the system using these components:

Provides detailed instructions on how to use automated installation programs and command-line utilities to install BIRT iHub modules, such as Visualization Platform, System Console, Metrics Management, and BIRT Analytics.

Describes how to use System Console to perform tasks such as managing a cluster, connecting to a database, adding a volume, setting up user accounts and groups, updating the license, and configuring other BIRT iHub properties, such as logging levels, notification, and printing. Also describes BIRT iHub system architecture, and backup and recovery operations.

Describes how to use Visualization Platform to perform volume administration tasks such as executing designs, viewing documents, and scheduling jobs.

Provides information about application programming using the SOAP‑based Actuate Information Delivery API (IDAPI), including a Java developer guide and sections on logging and using the Java Report Server Security Extension (RSSE).