Before you can begin using IBM® Enterprise
Records after upgrading the software,
you must configure the Process Region for IBM Enterprise
Records, restart Component Manager,
and verify that the settings for FileNet® Records
Manager V4.0, V4.5, or IBM InfoSphere™ Enterprise Records V4.5.1 are still in place.
- After the Component Manager starts, the list of available component
queues displays and indicates whether the queues started correctly.
- If the queues do not start, verify the account information specified
on the Advanced tab of the Component Manager
is correct.
To configure a process region:
- Refer to the planning checklist you completed for values
you might need to complete these steps. See the link at the end of
this topic.
- Set the minimum and maximum heap size for Destroy Disposition
Sweeps
To avoid out-of-memory errors while running Destroy
Disposition sweep, increase the heap size of the Application Engine Component Manager to 1GB.
- Open Process Task Manager.
- Under the Component Manager node,
select the appropriate Component Manager.
- Stop the Component Manager.
- Click the Advanced tab.
- Append to any existing values in the JRE
Parameters field: -Xmx1024m.
- Click Apply.
- Restart the Component Manager.
For more information about tuning IBM Enterprise
Records, see the IBM FileNet P8 Performance Tuning
Guide.
- Launch the Process Configuration Console.
- Sign in to Application Engine or Workplace XT as a user that is a member
of the Process Engine Configuration
Group, is assigned the PWConfiguration access role, and the Records
Administrator role.
Tip: Sign in from the Application Engine or Workplace XT server, or from an alternate
machine if the Application Engine or Workplace XT browser does not support
the use of Java applets.
- Select the Admin page (Application Engine) or (Workplace XT).
- Launch the Process Configuration Console.
- Click the connection point to start it.
- Import the IBM Enterprise
Records workflow
configuration file.
Important: In the RMWorkflowConfiguration.xml file, TrackingAttachment is
set to false which will make the Scan Physical
Items feature not work. If you do want to use the Scan Physical Items
feature, you can change TrackingAttachment to true in
the RMWorkflowConfiguration.xml file now or modify
it later through the Process Configuration Console Application Engine or Workplace XT. Enabling this tracking
feature can cause a serious Process Engine performance issue and it might take
a long time to finish the IBM Enterprise
Records workflow
configuration file importing process if you have large amount of work
items in Process Engine.
Purge unneeded event log records and tracker work items from Process Engine first to limit the impact.
For information on the Scan Physical Items feature and on purging
the event log records, refer to the links at the end of this topic.
- From the Process Configuration Console, right-click
the connection point and select Import from XML file.
- Click Browse and select the RMWorkflowConfiguration.xml file.
This file is available in the ier_install_path/Workflow/configureRMworkflow directory
on the Application Engine or Workplace XT server.
Tip: If
you have launched Application Engine or Workplace XT from a server other than
the Application Engine server, you
must ensure that the RMWorkflowConfiguration.xml configuration
file is copied onto the browser machine, and you must select it from
that location.
- Select the Merge option.
- Click Import, then click Yes to
proceed with the import.
The status of the import displays.
- Click Details to view the details
of the import, and then click Close.
- Click Close to close the dialog
box.
- After the import completes, expand the Work
Queues node and verify that the IBM Enterprise
Records queues are listed.
- Update the adaptor settings for the RM_Workflow_Util and
RM_Operations component queues, as follows:
- From the Process Configuration Console, expand the Component
Queues node for the connection point you are using.
- Right-click RM_Operations and
select Properties or double-click and it opens
automatically.
- Select the Adaptor tab.
- Under JAAS credentials, enter the user name and password
of a user who has both the Records Administrator and Process Engine Administrator roles.
If using the DoD Classified data model, the user must also have Top
Secret clearance as defined in the Classified Records Security Personnel
marking set.
- In the Configure Content text box, type CELogin.
- Click OK.
- Right-click RM_Workflow_Util and
select Properties or double-click and it opens
automatically.
- Select the Adaptor tab.
- Under JAAS credentials, enter the user name and password
of a user who has both the Records Administrator and Process Engine Administrator roles. If
using the DoD Classified data model, the user must also have Top Secret
clearance as defined in the Classified Records Security Personnel
marking set.
- In the Configure Content text box, if it does not say
so already, type CELogin.
- Click OK.
- Right-click the connection point name and select Commit
Changes or click the disk icon at
the top.
The Process Configuration Console dialog box
displays.
- Right-click Continue.
- When the changes have been saved, click Close.
- Set the base URL address of the IBM Enterprise
Records web application, as follows,
to make the IBM Enterprise
Records step
processors display correctly:
- From the Process Configuration Console, right-click
the connection point and select Properties or
double-click the connection point.
- Select the Web Applications tab.
- Type the URL of the IBM Enterprise
Records web Application in the
Server Base URL column for the row specifying your records management
software. The format of the URL is:
http://RM_web_application_server:port#/RM_application_name
For
example: http://myserver:7001/EnterpriseRecords
- Click OK.
- Right-click the connection point name and select Commit
Changes or you can click the Save icon at
the top. The Process Configuration Console dialog box displays.
- Click Continue.
- When the changes have been saved, click Close.
- Assign groups to the IBM Enterprise
Records work
queues to specify who can process work queue items, as follows:
Tip: For a brief description of the IBM Enterprise
Records work queues, use the guidelines
presented in the table See IBM Enterprise
Records work
queues descriptions to assign groups to IBM Enterprise
Records work queues.
For
each IBM Enterprise
Records work queue,
complete the following steps:
- From the Process Configuration Console, expand Work
Queues.
- Right-click a work queue and select Properties or
double-click the queue.
- Select the Security tab.
- Using the search facility, locate the LDAP users and
groups to be given access to the queue.
Important: Ensure
that only Records Administrator users and Records Manager users can
process and query the work items in the IBM Enterprise
Records work queues. For Records
Administrator users and Records Manager users, select the Query and
the Process check boxes. Allow Records Reviewers
and Records Users to only query the work items in the work queues.
For Records Reviewers and Records Users, select only the Query check
box.
- Click OK to save the changes.
- After all the queue updates have been made, commit the
changes as follows:
- Right-click the connection point and select Commit
Changes or click the disk icon at
the top. The Process Configuration Console dialog box displays.
- Click Continue.
- When the changes have been saved, click Close.
- Close the Process Configuration Console and restart Component
Manager to implement the changes you made.
Tip: At this point, when the Component Manager is restarted,
a number of
IBM Enterprise
Records components
do not start. These components require the
IBM Enterprise
Records JAR files that will be
configured in
Configuring component queues during an
installation and in
Restarting Component Manager during
an upgrade, after which the components can be started.
- Verify the assignment of groups to work queues.
- Sign in to Application Engine as
an Application Engine Administrator.
- Select the Tasks tab.
- Click Public Inboxes to verify
that only those queues for which the user has security access are
displayed.
- Sign out and then sign in as a user with different IBM Enterprise
Records privileges.
- Select the Tasks tab.
- Click Public Inboxes to verify
that only the queues for which the user has security access are displayed. For example:
- Sign in as a user assigned the Records Manager role and click Public
Inboxes. The RecordsManagerApproval queue should be visible.
- Sign in as a user assigned the Records User role and click Public
Inboxes. The RecordsManagerApproval queue should not be
visible.