Prerelease announcement: Download will be available by the 14th October 2011
The Content Repository Connector DSC allows process designers to easily integrate from Document Services (with or without Process Management) to the JCR running in Experience Services. The basic use case is one deploys the DSC through Workbench, sets configurations on both servers, then in Workbench, drag and drop operations into processes that can do CRUD activities to the Content Repository. This is a highly requested feature, because while integration was supported before, it required a fair level of programming.
The prerelease DSC will be available from the ADEP prerelease website that originally released ADEP on earlier this summer. If you signed up for that at the time you will be able to log in and get the content when we post it. If you are not signed up yet, don’t worry, we still allow new registrations.
The DSC will release for production in mid November (roadmap statement, so potentially subject to change, but it is all looking good at this point)
What does the DSC do?
This DSC is implemented by the same team that did the original Content Services DSC. So it replaces that DSC (notionally, they can run in parallel) and has some enhancements and specializations for interoperating with the Content Repository (was previously the Day Software’s JCR). It handles authentication, communication protocols and other plumbing as one would expect so that process authors can focus on what they need to accomplish visually and with configurations.
There are many use cases where this DSC will be used, ranging from simple CM storage and retrieval to process/action invocation from the Document Services side to the Experience Services side (store in the JCR can trigger publishing or other events on the Experience Services side).
What is a DSC?
A DSC is a component that can be installed on a Documents Server and introduces new functionality. It stands for Document Service Component. Most product components are DSCs but customers can write their own DSCs to create new integrations or functionality that require a higher level of sophistication than is appropriate with the use of standard integration options (e.g SOAP) or scripting/process maps. They are basically POJOs with nifty enterprise configurations around them that allow enterprise class life cycle, versioning and configuration (e.g. in an enterprise BPM system you don’t necessarily want a new version of a component to alter the way an inflight process is operating, or how a completed process reports audit data…) or even have to bounce the server to change the implementation of the DSC. It is definitely part of the secrete sauce of LiveCycle/ADEP Document Services.