 | The system administration client is a single, graphical user interface for managing the Content Manager system. You can use the system administration client to model data, authorize users, manage object retrieval, manage document routing, and more. | V8 Capabilities: | Benefits |
|---|
| V8.3 Export and import of system administration data | Data exported into an XML readable file can be imported into another system server, enabling easier system setup for like systems. The user can list the system administration object names in a IBM Content Manager system into an XML file. |
|---|
Authentication - Content Manager
- LDAP - Administration utilities can import LDAP users as well as synchronize Content Manager V8 with an LDAP directory.
| Passwords may be managed by Content Manager, eliminating the requirement to define users to other security systems. This improves ease of use and efficiency for IT.
LDAP support enables IBM® WebSphere® single sign-on. Using the utilities to import users or exits to authenticate users helps reduce administrative costs. |
|---|
Access Control - Tight integration with document and metadata operations -- including update, delete and text search, resource operations, and document routing
- APIs to extend the out-of-the-box privilege settings.
- Improved privilege processing with pre-computed access control list on the Library Server
| Tight integration offers performance benefits and ensures that information is delivered only to parties with the right level of authorization. |
|---|
| Administrative domains can be created in the Library Server to distribute administration responsibility to sub-administrators with limited privileges and scope. | Administrative domains streamline and distribute the user management in a Content Manager configuration with a large user base divided among many departments, improving the system adminstrator's productivity.
Application Service Providers who manage Content Manager implementations for multiple corporate clients can divide a Content Manager system among them with positive assurance that one client company cannot access another company's documents. |
|---|
Logging/auditing. Different levels of logging can be defined to capture functions performed against certain documents or folders. The logging facility will capture - Create, Retrieve, Update, or Delete operations on Items
- Document Routing information such as the process and work nodes through which an Item was routed. Information includes UserID, Timestamp, Process ID, Workbasket/Node ID (both from and to), resume time for "suspend", and Event Code for each of the possible actions.
| System use can be audited. Information can be fed to billing programs with usage statistics. The way work moves through business processes can be tracked and analyzed |
|---|
| An ItemType may include an optional Retention Period which calculates an expiration date. | Removing items no longer required releases dedicated storage space
Possibly more important, it also supports records management. The function can tag and track items for expiration and then purge them according to the retention requirements of your business. |
|---|
| A single System Administration client supports both Information Integrator for Content and Content Manager | ...eliminates the need for duplicate user id and aids IT productivity. |
|---|
| Find and filter functions for user listings | ...simplifies and improves performance in locating users or groups when there are thousands defined. |
|---|
| Support for multiple servers on the same tree | ...enables simultaneous administration of multiple servers, including switching between the Information Integrator for Content and Content Manager servers |
|---|
| System administration APIs in Java and C++ | ...supports inclusion of administration functions in application development |
|---|
| |
|
