Administering Content Platform Engine

Use the Administration Console for Content Platform Engine to configure and administer the Content Platform Engine.

Authorization

As a Content Platform Engine Administrator for an environment, you have full administration access to the object store in that environment, including the Content Platform Engine workflow system.

Administration Console for Content Platform Engine settings

Do not change the following pre-provisioned Administration Console for Content Platform Engine settings:
Table 1.
  Settings
Object Store Configuration > General settings
  • Support table overflow
  • Compress database tables and indexes
Object Store Configuration > Properties
  • Database Index Storage Location, Database Table Storage Location, Database LOB Storage Location
  • Verity Partition Property, Verity Partition Interval, Verity Domain Configuration
  • Database Schema Name
  • Subscription Cache Max Entries and other parameters on the Properties tab that have a pre-set numeric value
  • Compress database tables and indexes
Object Store Configuration > Cache All settings
Object Store Actions > Run Security Script Wizard All settings
Object Store > Administrative > Index Areas > New All settings
Object Store > Administrative > Index Areas > index_area_name All General and Properties settings.
Object Store > Administrative > Storage All storage settings
Object Store > Workflow Systems > General Table Spaces, Workflow Systems Security Groups, Process Orchestration
Object Store: Browse, Data Design, Events, Actions, Processes, Roles, and Sweep Management Do not change pre-provisioned objects in these categories. In addition, do not change objects that were created as part of the Object Store add-on installation or as part of the IBM® Navigator feature enablement.

The following settings are not supported in cloud environments:

  • Object Store Configuration > Replication Class Mappings
  • Object Store > Administrative > Publishing Queue
  • Object Store > Workflow Systems > Configure Workflow Settings: UseFileNet® Process Designer to configure the workflow system. You can download FileNet Process Designer as part of the Content Platform Engine tools package.

Enabling Content Extended Operations

Content Extended Operations are Java™ methods that you can use in steps of a Content Platform Engine workflow to manipulate documents. To use these operations, you need to configure JAAS credentials in the Administration Console for Content Platform Engine.
  1. Create a set of service credentials and grant sufficient access to it for content-related activities.

    To create service credentials, you must have the Account Administrator role. If you don't have this role, get your account administrator to create the service credentials for you and provide you with the generated functional ID and password. For more information, see Creating and managing service accounts.

  2. Log in to the Administration Console for Content Platform Engine as a Content Platform Engine Administrator and navigate to the default object store, OS1.
  3. Click Administrative > Workflow System > Isolated Regions > OS1_IR1 > Component Queues > CE_Operations and go to the Adapter tab.
  4. For the JAAS user name and Password, specify the functional ID and password from step 1, then click Save.

For more information about Content Extended Operations and JAAS credentials, see Component Integrator operations.

Tracking object activity

As a Content Platform Engine Administrator, you can track critical object activities by enabling audit logging. Auditing logging tracks custom or system events that occur for objects. Most events that occur for Content Platform Engine classes can be audited, including events that pertain to security, content management, and business transactions.

Auditing is disabled by default. When auditing is enabled, the automatic logging of an event creates an audit entry in the audit log (the database Event table). Audit entries can also be programmatically created by custom applications. For regulatory compliance, the default retention period for log entries is 365 days. If your compliance policies require a retention period longer than 365 days, contact IBM Support.

Because auditing requires additional database interactions, it can have performance implications for your applications. To improve the performance and stability of your object stores, a preconfigured sweep job runs weekly to automatically remove log entries older than 365 days. The job runs at the following local times:
  • From Friday 10 PM to Saturday 6 AM
  • From Saturday 10 PM to Sunday 6 AM

For information about enabling audit logging, see Tracking object activity.