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.