The Rights Management service tracks specific actions as they occur, such as when a policy is used to protect a PDF document or when a policy-protected document is opened. You can develop client applications that are able to search for Rights Management events. Because the Rights Management service exposes a public WSDL, you can create a proxy library that consumes the WSDL and use the proxy library in client applications built with development environments that support web services such as Microsoft Visual Studio.
When creating a proxy library that consumes that Rights Management WSDL, the proxy library has access to data types exposed by the Rights Management WSDL. These data types include
AuditSpec. For more information, see Searching for Events.
LiveCycle ES enables you to invoke processes created in Workbench ES using a client application built with Flex. A benefit of creating a client application with Flex and using it to invoke a process is that you have access to a rich set of Flex controls. That is, you can display process data in controls such as a pie chart or bar graph.
The Displaying LiveCycle ES process data in Flex graphs article discusses how to display process data in a client application built with Flex. Basically, you have to first create a process using Workbech ES. Then you can invoke the process from the client application and retrieve the process data. You can then use the process data to populate a control. For more information, check out Displaying LiveCycle ES process data in Flex graphs.
LiveCycle Content Services ES is an ideal location in which to store documents created by business processes. However, Content Services ES does not expose a public API or support a public WSDL. As a result, you cannot directly invoke its operations from a client application such as a Java or a Flex client.
That is why I decided to create an article that discusses what you have to do if you want to store a document in Content Services ES using a client application. Basically, you have to first create a process using LiveCycle Workbech ES. Then you can invoke the process from the client application. For more information, check out the article that I wrote,
Programmatically accessing LiveCycle Content Services ES.