Integrating With Livecycle Policy Server; Configuring Livecycle Products To Integrate With Livecycle Policy Server - Adobe LIVE CYCLE 7.2 - INSTALLING AND CONFIGURING Manual

Security products for jboss
Hide thumbs Also See for LIVE CYCLE 7.2 - INSTALLING AND CONFIGURING:
Table of Contents

Advertisement

11

Integrating with LiveCycle Policy Server

This chapter describes how to integrate LiveCycle Reader Extensions and LiveCycle Document Security
with LiveCycle Policy Server. Product integration enables the following functionality:
LiveCycle Reader Extensions can open policy-protected PDF documents using the openPDFWithAPS
API method.
LiveCycle Document Security uses the PDF Manipulation Module API to programmatically access a
policy from LiveCycle Policy Server and encrypt PDF documents with the policy.
LiveCycle Document Security can also save or decrypt a policy-encrypted document and remove the
encryption from a policy-protected document.
Configuring LiveCycle products to integrate with
LiveCycle Policy Server
If LiveCycle Document Security and LiveCycle Reader Extensions are installed on a separate application
server than the one where LiveCycle Policy Server is installed, you must configure the first application
server to allow the two products to integrate with the LiveCycle Policy Server deployment that is running
on the second application server.
If LiveCycle Document Security and LiveCycle Reader Extensions are installed on the same application
server where LiveCycle Policy Server is installed, this configuration is already completed as part of the
LiveCycle Policy Server configuration process.
If LiveCycle Reader Extensions or LiveCycle Document Security are installed on separate application
servers, the application servers must be on the same subnet or port access might be blocked.
All products must also be running on the same application server type. For example, if
LiveCycle Reader Extensions or LiveCycle Document Security is running on JBoss, then
LiveCycle Policy Server must be running on JBoss.
The APS Proxy Module enables LiveCycle Document Securityand LiveCycle Reader Extensions to
communicate with LiveCycle Policy Server. To integrate with LiveCycle Policy Server during the
configuration process, you need to indicate to LiveCycle Reader Extensions or
LiveCycle Document Security the LiveCycle Policy Server host name, RMI Port, and application server
initial context factory.
The values vary depending on the application server you use. You can configure these properties during
the configuration process. If you are not ready to configure the integration with LiveCycle Policy Server
when you install LiveCycle Reader Extensions or LiveCycle Document Security, you can use
Configuration Manager to configure the APS Proxy Module properties later. Configuration Manager lets
you modify the contents of the APS Proxy Module archive file without extracting the contents.
69

Advertisement

Table of Contents
loading

This manual is also suitable for:

Livecycle 7.2

Table of Contents