Working With Information Rights Manager Working With WebCenter Spaces

8-4 Administrators Guide for Oracle Imaging and Process Management If the Oracle IPM document is subject to a freeze in Oracle URM and you attempt to delete the document from Oracle IPM, you will recieve the error The documents cannot be deleted because they are in a legislative hold in the repository. You will be unable to update the document in Oracle IPM, or move or copy the document to another application. Only the Oracle IPM or Oracle UCM Administrator will be able to delete documents which are frozen. Once unfrozen, the restrictions within Oracle IPM are removed.

8.1.4.1.1 Using Oracle URM 10g If Oracle IPM is connected with a system using Oracle

URM 10g, content associated with Records-only Categories are subject to the same restrictions.

8.1.4.1.2 Using Oracle URM 11g If Oracle IPM is connected with a system using Oracle

URM 11g, content associated with categories using the Restrict Edits, Restrict Revisions or Restrict Deletes, designators are subject to the same restrictions in Oracle IPM.

8.1.4.2 Synchronizing with Oracle UCM Adapter for Oracle Content Server

When using the Oracle UCM Adapter for Oracle Content Server to allow Oracle Universal Records Manager to use multiple Oracle Content Server repositories, you must ensure that security groups are consistent between the Oracle Content Server and Oracle URM. The Oracle UCM Adapter does not synchronize security groups created by Oracle IPM with Oracle URM. If an application is created in Oracle IPM that adds security groups to the Oracle Content Server repository, you must manually configure the same security groups on Oracle URM that was created by Oracle IPM. This should be done prior to uploading any content to the Oracle IPM application. Additionally, if there is any modification to an Oracle IPM application or to document security in an application, you must manually update the security groups in Oracle URM.

8.1.5 Working With Information Rights Manager

Oracle IPM does not automatically assign application documents to an IRM classification. However, by modifying an application profile and profile rules, you can automatically assign documents to an IRM classification. 1. Add a new profile rule and make note of the name. For example App_X_IRM.

2. Select the IRMProtection field xIRMProtection and set the Type to Info Only.

3. Enable Use default value and set the default value. This value must match an

Oracle IRM context. This allows people using the Oracle Content Server check in form to see the assigned IRM classification. WARNING: The rule used to associate content with an Oracle URM category must be carefully constructed per the instructions for integrating with Oracle URM. Failure to create this rule correctly may assign Oracle IPM content to records categories or allow them to be frozen, which restricts an Oracle IPM users ability to modify the document if necessary. Note: Oracle IPM metadata fields are not propagated to Oracle URM at all, so documents in Oracle URM do not have any indication of the values specified in Oracle IPM. Working with Oracle UCM 8-5

4. Enable Is derived field and set the default value. This value must match an Oracle

IRM context. This allows the value to be set upon check in from any source, including Oracle IPM upload. 5. Edit the application profile for the Oracle IPM application you wish to modify and add the rule defined above to the Rules tab.

8.1.6 Working With WebCenter Spaces

Oracle IPM documents are not automatically accessible within WebCenter Spaces, but documents can be automatically assigned to Folders visible within WebCenter Spaces. Manual configuration and modification of an application profile and profile rules are required to ensure that IPM documents will be accessible. 1. Configure Oracle Content Server and Oracle IPM to use the same LDAP-based identity store that Oracle WebCenter has been configured to use. For information on configuring WebCenter and Oracle Content Server to use an LDAP identity store, see Oracle Fusion Middleware Administrators Guide for Oracle WebCenter. 2. Configure Oracle Content Server as the bridge between IPM and WebCenter Document Service using an IPM supported version of Java. 3. WebCenter Spaces Document Service uses the Folders component, and IPM must be configured to automatically specify Folders for checked in content. For more information regarding configuring IPM with Folders, see the section Section 8.1.3, Working With Folders. For further information regarding WebCenter Spaces integration with Oracle Content Server, see Oracle Fusion Middleware Administrators Guide for Oracle WebCenter.

8.2 Understanding Document Storage

Conceptually, applications represent containers of documents with common characteristics as defined and enforced by the application. A single instance of Oracle Content Server may not be able to handle the multiple applications required by an organization. In order to scale a solution to handle the multiple applications required, multiple Oracle Content Server instances can be used. However, an application cannot be divided across multiple Oracle Content Server instances. To support multiple Oracle Content Server instances, you must associate each application with its target Oracle Content Server instance. To represent this at the Oracle IPM level, a new object has been added to the public API known as the repository. The repository object is responsible for keeping track of the connection information to each Oracle Content Server instance. Each application will be associated with a particular repository. For more information about creating connections to repositories, see Section 7, Managing Connections. Note: If IRM is not configured correctly, or the value does not match a valid context, you will be unable to check content into Oracle Content Server because it will fail IRM validation. Note: If an application is modified in Oracle IPM, and the modification includes an application name change, then the rule you just added to the application profile will need to be added again.