Sharper Image GT800 Especificações descarregar pdf (Página 41)

LIVECYCLE ES4 OVERVIEW

Document information and security

Last updated 1/15/2015

Here is an example of how Rights Management works:

1 The document owner or administrator creates policies by using the Rights Management web application accessible

through Administration Console. Document owners can create user policies accessible only to them.

Administrators can create organizational policies within policy sets that are accessible to permitted users, and can

also designate policy set coordinators. The policies are stored in a database that connects to the application server.

Developers can also automate the creation of policies by using the Process Design perspective in Workbench or the

Rights Management API.

2 The document owner applies the policy, and saves and distributes the document by using the web pages or Adobe

Acrobat 7.0 or later. The document can be distributed by email, through a network folder, or on a website.

Developers can also automate the application of policies to documents. They can also automate the distribution of

these documents to end users by using the Process Design perspective in Workbench or the Rights Management API.

3 The document recipient opens the document in Acrobat 7.0 or later or Adobe Reader 7.0 or later. The recipient can

use the document according to its policy.

4 The document owner, policy set coordinator, or administrator can track documents and modify access to them by

using the web pages. Developers can also track documents by using the Process Design perspective in Workbench

or the Rights Management API.

Programmatically applying policies

On a mass production environment such as generating monthly invoices for a telecom company, creating and

applying policies that are specific to each document can become a resource-intensive process. In such cases, you can

use the Rights Management Java API to create and apply policies that are specific to users, rather than to documents

based on abstract policies. The license generated for a user is later used for all documents that are accessible to the user.

Using the APIs, you create an abstract policy that is a policy templates with all policy attributes such as document

security settings and usage rights, except the list of principals. Administrators can create any number of policies from

the abstract policy with different principals who should have access to the documents. Changes made to the abstract

policy do not affect the actual policies that are generated from the abstract policies.

In the case of monthly invoice generation of a telecom company, you create an abstract policy, users, and then generate

the licenses for each user that is later applied to the documents for each user.

You cannot create the abstract policy from the Rights Management Web pages. You can, however, administer the

policies that you create from the abstract policy from the Rights Management web pages. Policies that are created using

this method are identical in behavior to those created from Rights Management web pages.

See Programming with LiveCycle for more information.

Rights Management security

To ensure the confidentiality of documents that are protected by policies, Rights Management implements three layers

of security:

• Authentication

• Authorization

• Document confidentiality

1 2 ... 36 37 38 39 40 41 42 43 44 45 46 ... 67 68

Sem comentários

Sharper Image GT800 Especificações Página 41