View comments | RSS feed
Invoking LiveCycle ES Using APIs > Invoking LiveCycle ES Using LiveCycle Remoting

Invoking LiveCycle ES Using LiveCycle Remoting
Processes created in LiveCycle Workbench ES can be configured so that you can invoke them through LiveCycle Remoting. That is, you can invoke a short-lived or long-lived process from a Flex application. This is a specialized feature based on the standard LiveCycle Data Services ES remote object feature. (See Understanding processes.)
Note: When using LiveCycle Remoting, it is not recommended that you invoke LiveCycle ES services directly. Instead, invoke processes that were created in Workbench ES. For information about creating processes in Workbench ES, see LiveCycle Workbench ES Help.
Note: When LiveCycle ES is not configured to allow anonymous access, LiveCycle Remoting requests from a Flex client to the server result in a web browser challenge and the user must enter user name and password credentials.
This section discusses invoking the following LiveCycle ES short-lived process, named EncryptDocument, using LiveCycle Remoting.
When this process is invoked, it performs the following actions:
Obtains the unsecure PDF document that is passed as an input value. This action is based on the SetValue operation. The name of the input parameter is inDoc and its data type is document. (The document data type is an available data type from within Workbench ES.)
Encrypts the PDF document with a password. This action is based on the PasswordEncryptPDF operation. The name of the output value for this process is outDoc and represents the password-encrypted PDF document. The data type of outDoc is document.
Note: The EncryptDocument process is not based on an existing LiveCycle ES process. To following along with the code examples that are located in this section, create a process named EncryptDocument using Workbench ES.
Note: For information about using LiveCycle Remoting to invoke a long-lived process, see Invoking Human-Centric Long-Lived Processes.

Invoking LiveCycle ES Using APIs > Invoking LiveCycle ES Using LiveCycle Remoting

Programming with LiveCycle ES (LiveDocs)
Adobe LiveCycle ES Update 1


Serhat GĂ–KSEL said on Mar 16, 2009 at 2:00 AM :
[RPC Fault faultString="com.adobe.idp.dsc.DSCInvocationException : Invocation error. : com.adobe.livecycle.encryption.client.EncryptionServiceException: preparePasswordEncryptionSpec: No Permission or Document Open Password.

-- (error code bin: 1, hex: 0x1)
Caused By: preparePasswordEncryptionSpec: No Permission or Document Open Password. (ValidationHelper.java98)" faultCode="Server.Processing" faultDetail="null"]
at mx.rpc::AbstractInvoker/[C:\autobuild.2.0\frameworks\projects\rpc\src\mx\rpc\]
at mx.rpc::Responder/fault()[C:\autobuild.2.0\frameworks\projects\rpc\src\mx\rpc\]
at mx.rpc::AsyncRequest/fault()[C:\autobuild.2.0\frameworks\projects\rpc\src\mx\rpc\]
at NetConnectionMessageResponder/statusHandler()[C:\autobuild.2.0\frameworks\projects\rpc\src\mx\messaging\channels\]
at mx.messaging::MessageResponder/status()[C:\autobuild.2.0\frameworks\projects\rpc\src\mx\messaging\]
smacdonald2008 said on Apr 2, 2009 at 1:34 PM :
Thanks for your comment. It looks like there is an issue with the process that you are invoking. To follow along with the code example, create a short-lived process named EncryptDocument. The first action si a SetValue operation.

The 2nd operation is EncryptUsingPassword. You can specify the open and permission password values in this operation. The only input to the process is a PDF document. Ensure that the data type is document. To match the code -- ensure that the name of the input document is inDoc.


RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: