Administering iHub System
Administering an iHub System includes the following tasks:
Setting up users, roles, groups, channels, folders, files, and other administrative tasks
An administrator creates, configures, and manages users, roles, groups, files, folders, and channels, including assigning and updating privileges, managing security role and group memberships, and providing access to channels. User, role, group, and channel privileges selectively control access to the Encyclopedia volume and its data objects.
Scheduling jobs to run designs and generate documents
Each stand‑alone iHub and node in an iHub cluster has a job scheduler and dispatcher. A job dispatcher send 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 allow iHub System to scale processing to handle thousands of scheduled jobs at the same time.
Reviewing logs and auditing the information to diagnose system problems
iHub can capture usage and error information in log files to assist an administrator in evaluating resource usage and troubleshoot problems. The usage and error logging applications are open framework applications, which are available as DLLs in Windows and shared libraries in Linux.
Configuring a cluster using automated installation programs and cloud computing base images
The administrator can run the installation program to configure iHub or deploy a prepared image of an installed iHub run-time environment. Each cluster node gets its configuration from a template in acserverconfig.xml, located in a shared configuration home directory. Nodes with the same cluster ID, running on the same sub-net, automatically detect and join each other to form the cluster.
Using Actuate iHub Integration Technology scripts and tools to develop client applications and extend iHub functionality
The Actuate Information Delivery application programming interface (IDAPI) supports integrating and administering iHub using extensible markup language (XML) and the simple object access protocol (SOAP). Using the IDAPI, developers can create applications that perform such tasks as scheduling a custom event, running an Report Server Security Extension (RSSE) application to manage users and roles in an external system such as an LDAP server, and installing and customizing usage and error logging and performance monitoring extensions.
An iHub administrator uses the Actuate Information, Management, and Configuration Consoles, command-line utilities, and iHub 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:
Installing BIRT iHub for Windows or
Installing BIRT iHub for Linux Describes iHub System architecture. Provides detailed instructions on how to use automated installation programs and command-line utilities to install stand‑alone iHub and clustered nodes that store Encyclopedia volume metadata in an external, third-party RDBMS, such as DB2, Oracle, PostgreSQL, or SQL Server. Also describes Actuate licensing policies and procedures and backup and recovery operations.
Managing an Encyclopedia Volume Describes how to use Management Console and command-line options to perform tasks such as managing Encyclopedia volume user accounts, assigning privileges, scheduling jobs, and distributing documents.
Configuring BIRT iHub Describes how to use Configuration Console to perform tasks such as managing an iHub cluster, adding Encyclopedia volumes to iHub, connecting to a database, updating the license, and configuring iHub properties, such as logging levels, e-mail notification, and printing.
Using BIRT iHub Integration Technology Provides information about application programming using the SOAP‑based Actuate Information Delivery API (IDAPI), including a Java developer guide and sections on logging, auto archiving, and using the Java Report Server Security Extension (RSSE).