1-6 Oracle Fusion Middleware Users Guide for Oracle IRM Desktop
If you are the owner or creator of sensitive documents, you can work with the rights administrator or, in Oracle IRM terms, the domain manager to create one or more
contexts to protect that information. For example, if you are developing a new product, you might create contexts to protect the requirements, specifications, designs,
market projections, competitive information, legal information, patents, and so on. Your domain manager can help you decide whether you need new contexts, or
whether existing contexts are suitable for your information.
1.5 About Connecting to Oracle IRM Server
Before you can create or read sealed documents, your installation of Oracle IRM Desktop must be connected to the server Oracle IRM Server that holds the user and
context information for the documents to be created or read.
If you have been sent a sealed document and want to read it, simply opening the document will initiate connection to the server. You may be asked to provide login
details, after which you will be able to use the sealed document to the extent that your rights allow. You will find that the server to which you have been connected is listed
on the Servers tab of the Oracle IRM Desktop Options dialog.
If you wish to seal a document to a context hosted by a server that is not yet listed on the Servers tab, you will need to connect to that server manually. See
Section 7.3, Connecting to Oracle IRM Server Manually
.
1.6 About Synchronizing with Oracle IRM Server
If you are permitted to work offline, your local cache of rights is updated by synchronizing to connected servers. This will allow you to keep working with sealed
documents even when you are disconnected from the network and cannot contact the server. Typically, your cached rights allow you to keep using documents for several
days before being required to contact the server.
Synchronization is almost completely automatic. Typically, it runs daily during standard office hours, but the schedule is controlled by the administrator of the server.
If synchronization fails for any reason, the application displays a failure message and automatically retries at intervals.
You can initiate synchronization manually at other times: for example, if someone notifies you that your rights have changed, and you want to synchronize immediately
rather than wait for the automatic process. See Section 7.4, Synchronizing Your Rights
Manually .
1.7 About Sealed Document Item Codes
By default, all documents in a given context are subject to the same rights. However, the need may arise for exceptions to be made for specific documents. For example, it
might be necessary to allow an auditor access to a specific secret merger document, but not to all secret merger documents.
To support such exceptions, every sealed document has an item code. In most cases, item codes are allocated and managed automatically. In rare cases, users
may be authorized to allocate and change item codes manually. This enables a user to, for example, create several different documents all with the same item code, enabling
the documents to be handled as a unit for the allocation of rights.
About Oracle IRM and Sealed Content 1-7
Item codes are changed or retained depending on your rights. If you have the Seal right, then when you save or save as any edits to a document, a new item code will
be created for that document. If you have the Reseal right, then every time you save the document, the same item code will be used.
1.8 About Sealed Email
