Posts tagged ADEP
- Mayank Gupta, Computer Scientist @ Adobe
Steps to add a custom service in Correspondence Management solution are as follows:
- The implementation for this user story involves code changes and rebuilt. So, one is required to setup the development environment via steps mentioned @ Setting up development environment.
- Add your sample custom service interface and implementation class in the CorrespondenceManagementSolutionTemplate/Services project for example @ com.adobe.icc package in the source code. See the sample @ http://blogs.adobe.com/LiveCycleHelp/files/2012/06/SampleCustomService1.zip.
- Now define your service as a spring bean. For this, add the following entry in your CorrespondenceManagementSolutionTemplateServicesresourcesMETA-INFspringcmadobe-cm-spring-config.xml file: <bean id=”sampleCustomService” class=”com.adobe.icc.SampleCustomServiceImpl” />
- Now expose your spring bean as a osgi-service. For this, add the following entry in your CorrespondenceManagementSolutionTemplateServicesresourcesMETA-INFspringosgi-context.xml file: <bp:service interface=”com.adobe.icc.SampleCustomService” ref=”sampleCustomService” > <bp:service-properties><entry key=”connectors.httpinvoker” value=”true” /> <entry key=”connectors.httpinvoker.alias” value=”/sampleCustomService” /> <entry key=”connectors.remoting” value=”true” /> <entry key=”connectors.remoting.id” value=”sampleCustomService” /> </bp:service-properties> </bp:service>
- Rebuild and redeploy the Solution template to view the changes. For information on rebuilding and redeploying, see Building and deploying the Solution Template.
The other day Darren asked about how to access a properties file with some settings from within a Livecycle ES resp. ADEP DSC on the livecycle developers mailing list. I responded there, but I thought it’d be useful to post the solution here as well.
Essentially a Livecycle/ADEP DSC is nothing else but a .jar file that’s been crafted in a certain way. Darren wanted to have the .properties file within the DSC and needed to know how to access the file from Java code within the DSC. Here’s a working approach how this can be done:
Read the complete post at Blog In Black.
Problem Scenario: LiveCycle uses Quartz scheduler. Typical use case is when “watched folder” endpoint related schedules get translated as quartz triggers. Quartz takes care of executing the trigger based on frequency and updates a table with the latest execution count. … Continue reading →
– Neal Davies
I’m pleased to announce that the first service pack for ADEP/LiveCycle v10 is now available. It is made up of two parts; Document Services SP1 for the LiveCycle Modules (Forms, Output, Reader Extensions, Process management …) and Experience Services SP1 … Continue reading →
Complete article at http://blogs.adobe.com/ADEP/2011/12/adeplivecycle-v10-sp1-now-available.html.
While not as complex a process as Barcoded Forms the process of dynamically rendering PDFs from the LiveCycle Repository is a common process that gets used very often. There may be instances where an application needs a simple static PDF. Perhaps it’s a form that’s not quite ready for online submission. You could store these files on a web server and access them directly but it would be better and easier for future development to store them in the LiveCycle Repository and render them with a call to a REST service that is created when the process is deployed. The path to the document to render is passed into the process via a URL variable and the static PDF or the XDP file converted to PDF is returned to the browser.
For this LiveCycle Hands On the process is very simple. Besides rendering a simple static PDF, it’s also setup to render a simple XDP using LiveCycle Output ES.
Download the LCA here: Render_Form_Demo.lca_.zip
(Right click and select View Image to see the full size image)
Complete article at http://www.underprise.com/2011/06/01/dynamically-rendering-pdfs-from-the-livecycle-repository/.
Look at these videos that demonstrate how you can use LiveCycle ES to build a process and an AIR application to publish tweets to a corporate Twitter account where you have control on what’s published or not. Part 1 focuses on building the client with Flash Builder 4 with the LC Service Discovery plugin. In part 2 you will see how to archive all tweets in a PDF/A format within LiveCycle Content Services.
Original article at http://www.drflex.eu/2010/01/building-a-controlled-twitter-solution-using-adobe-livecycle-es-part1/.
– Holly Schinsky
Flex folks, first of all, today there’s a new official statement out on the Adobe website about Adobe’s commitments to the Flash Platform including plans for Flex that you should be aware of. Secondly there’s a new post from the Product Management team out now summarizing the recent Flex Q&A. There’s been a lot of frustration in the community (which I understand and can personally relate to having been part of the community myself for a very long time) and I wish that the sequence of events (and frankly the communication) did not happen as it did, but it is what it is at this point and we need to carry on. I hope people can see this move of Flex to an Apache model with dedicated full-time engineering resources in San Francisco as the good news that it is!! Flex is alive and well and will continue to grow as the dust settles. Even now we can build amazing applications over many other technologies in half the amount of time with it in its current state. And the growth in Flex and AIR for mobile is allowing us to do some super cool and fun stuff which is about to just get better with the upcoming release of Flex 4.6 in a couple weeks!
I know many of you are having to answer some tough questions from your clients and management about all of this, I hope today’s statements can help in that respect. If there was a way I could change how things happened myself or wave a magic do-over wand I would in a heartbeat . This has not been easy for any of us. I just hope we can now start channeling our frustrations into something more positive and productive and get back to having some fun!
I will continue to post any updates on the move to Apache as I find out. Start thinking about how you might be able to contribute !
Original article at http://devgirl.org/2011/11/17/flex-is-alive/.
– Kevin Schmidt
With all the Adobe news lately, I wanted to make sure everyone knew the future of Adobe LiveCycle. Here is the statement from Arun Anantharaman, vice president and general manager, LiveCycle and Adobe Connect.
“Since Adobe’s entry into the Enterprise market in 2002 with the acquisition of Ottawa-based Accelio, we have built a large portfolio of LiveCycle customers. We will continue to sell and support our LiveCycle products in the government and financial services markets, two areas where the LiveCycle value proposition remains especially strong. Outside of those markets, we are now planning to focus our Enterprise efforts on products targeting the digital marketer, including the Digital Marketing Suite and Web Experience Management solution. In addition, Adobe is fully committed to the success and satisfaction of our customers and we intend to build long term strategic relationships with them. We will continue to support all existing and future customers of our solutions.”
So, there you have it, feel free to ask any questions in the comments and I will do my best to get them answered for you.
Original article at http://www.underprise.com/2011/11/11/the-future-of-adobe-livecycle/.
Session re-writing is the practice of adding the session identifier to the HTTP request URL instead of passing the session identifier as a session cookie. Session re-writing is usually used when cookies have been disabled on the client. It is an easy way to let clients that do not allow or support cookies maintain session state with the server but it poses some security risks. The session identifier is passed in the URL which means that it is not encrypted even if the request is made over SSL/HTTPS. Because of the security risks associated with session re-writing, the Open Web Application Security Project (OWASP) recommends that session re-writing only be used for low-value sites. In this article, I will show you how to disable session re-writing in BlazeDS and LCDS to help secure your application.
In BlazeDS and LCDS, the session identifier is typically either the JSessionId (for servlet based endpoints in BlazeDS or LCDS) or AMFSessionId (for NIO HTTP based endpoints in LCDS).
Note that the RTMP protocol doesn’t use HTTP, so the issue of session re-writing doesn’t apply to RTMP endpoints.
When the BlazeDS or LCDS server receives a request with no session identifier (either a session cookie or session id URL parameter) a couple things happen. A new session is created. A Set-Cookie header with the session id is added to the response. Also, an AppendToGatewayURL header with the session id is added to the AMF or AMFX response message.
When LiveCycle became ADEP Document Services all of the existing modules were ported over but I thought it would be useful to revisit them all and see what as new. This post gives a summary of the modules which are available to any Document Services solution (excluding the foundation services which come with all Document Services modules) and should be familiar to those who have worked with LiveCycle ES1/ES2 in the past.
Business Process Management
Adobe Digital Enterprise Platform Document Services – Process Management 10.0
Process Management allows the designer to create processes which assign and move tasks around a business. End users can login using the Workspace web application to view and update any task assigned to them. This module is commonly used in conjunction with the Forms modules in order to create workflows for forms built by the designer. ADEP Mobile also comes as part of this module allowing your end users to interact with their tasks on the go.
As described in one of my earlier posts this one has now been deprecated. It’s still included for legacy purposes but you should really be using the new CRX service.
Adobe Digital Enterprise Platform Document Services – Forms 10.0
The bread and butter of many ADEP solutions, Forms is what allows data to be merged and retrieved from forms rendered to PDF, HTML or Guides. It also allows forms to be assembled from fragments. If you are designing to form to be dynamic and it doesn’t have a fixed layout then you will almost certainly need the Forms module. Together with the Process Management module it allows for some fancy data collection and presentation to your end users!
Adobe Digital Enterprise Platform Document Services – Adobe Reader Extensions 10.0
If you need to distribute those forms you’ve just designed to external parties then chances are you’ll probably run into the need for Reader Extensions. A “rights-enabled” form opened in Adobe Reader allows the end user to perform tasks that are normally reserved for the commercial Acrobat software such as adding attachments, saving a PDF form locally (the most common use case) and digitally signing forms. Can be used standalone or as part of a workflow.