This user hasn't shared any profile information
Posts by moderator
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.
Don’t worry – this is not going to be a lengthy, complicated, super-advanced tutorial. I thought about writing a post on Adobe LC DSCs for a while, but never got round to. Today, I got kind of pushed over the edge by seeing that my friend Duane and his partner Matt from Überity have published a super-simple DSC to integrate an LC process with the Twilio SMS/TXT services.
You have no idea what I’m talking about? Ok – here’s the gist: A DSC is a Document Service Component in LiveCycle. Basically it’s a component wrapper for some custom logic or external service integration that one can write and use within the LiveCycle Process Management Engine. One of my biggest complains about and issues with LiveCycle are the lack of community contribution and the lack of good and advanced documentation around the product. So, let’s take this opportunity to compile a few interesting resources around DSCs.
If you’re ever in the need of extending LiveCycle (and most serious users I know are at some point), writing a Document Service Component is one of the easiest ways. To get started, use a tutorial Adobe provides here:
Read the complete post at Blog In Black.
1) Create a Flex-LCDS sample application using WTP tool in Flash Builder: http://harpreetsingh2602.wordpress.com/2012/03/11/create-combined-flex-and-java-project-4/
2) Create connector between Apache WebServer and your two LCDS Tomcat server(see apache connector configuration doc).
3) Create a folder “LCDS_Configuration” (any name) in the WebApps folder of your Tomcat servers.
4) Open the .flexProperties file of your sample application and make sure the “serverContextRoot” is /LCDS_Configuration.
5) Place the content of WebContent from your sample application inside the “LCDS_Configuration” folder of both the Tomcat server.
6) Most importantly compile your application against the services-config.xml placed at the location …LCDS_Configuration/WEB-INF/flex.
7) Create a folder “Flex” (any name) in the htdocs of your WebServer.
8) Place the content of bin-debug inside the “Flex” folder of Apache.
9) Dont miss to add JkMount in the mod_jk.conf file.
# Send everything for context /LCDS_Configuration to worker ajp13
JkMount /LCDS_Configuration ajp13
JkMount /LCDS_Configuration/* ajp13
Below are some simple steps to give a remoting call to LCDS server.
1) create a Flex-LCDS project, refer link: http://harpreetsingh2602.wordpress.com/2012/03/11/create-combined-flex-and-java-project-4/.
2) write the remote object tag defining the destination in the mxml file.
3) write a java class and create a method to return any string.
3) create a button in the mxml file and on its click handler call the method of your java class.
4) Define the destination in the remoting-config.xml file and keep the services-config file as default. We will use the my-amf channel.
Download the code from here: RemoteExample. Convert .doc to .zip after download.
- Ameeth Palla, Technical Account Manager, Adobe
A topic that has come up several times in the recent past is about testing Adobe LiveCycle Workspace. I thought it will be useful to provide some information around this for the benefit of a larger LC community.
If the objective is Load testing, in-house Adobe uses a commercial tool call Silk Performer which can capture and replay the AMF3 interactions between Workspace and the server for scalable load generation. There are other tools that work with AMF3.Some people have asked if QTP can be used for load testing – It is unlikely that QTP is a good fit, since it is not suited to scalable load generation.
Adobe recommends using Silk Performer or Neotys Neload for load testing of Workspace. Check out the links below that may provide more insight into this topic:
If the objective is Functional testing then Workspace is configured for QTP testing out of the box. If you install QTP, restart your computer, then install the Flex plug-in for QTP, restart your computer then you can start automating your Workspace tests. However for QTP automation you should use the Workspace automation URL rather than the default URL. So rather than http://server:port/Workspace/Main.html you would use http://server:port/Workspace/Main-auto.html.
Read the complete post at http://blogs.adobe.com/livecycle/2012/03/testing-livecycle-workspace.html.
Adobe LiveCycle ES3 includes a FIPS 140 Certified RSA BSAFE Crypto-J 3.5 (cert#590) encryption module. FIPS mode is configured in the product installer.
Original article at http://blogs.adobe.com/livecycle/2012/03/fips-validation-certificate-for-livecycle-es3.html.
- Juergen Hauser, Sr. Product Manager – LiveCycle Data Services
Read the complete post at http://blogs.adobe.com/livecycle/2011/12/livecycle-data-services-for-java-ee-4-6-now-available.html.
- Dave Welch, Senior Director – LiveCycle
We are pleased to announce the release of Adobe LiveCycle Enterprise Suite 3 (ES3). LiveCycle ES3 contains the document and data services capabilities, including electronic forms and business processes, which were formerly part of the Adobe Digital Enterprise Platform (ADEP), a brand that is being retired.
The new LiveCycle ES3 release incorporates:
- Document services capabilities available with ADEP and the recent ADEP Document Services service pack 1
- LiveCycle Data Services 4.6.1
- Updates to LiveCycle Connectors for Microsoft® SharePoint® and IBM® FileNet
LiveCycle offers a number of components that help extend the value of existing back-end systems by better engaging users, streamlining processes, managing correspondence, and strengthening security.
Read the complete post at http://blogs.adobe.com/livecycle/2012/03/livecycle-es-3-release-now-available.html.
On Friday Uberity Technology Corporation launched a free and open source code Adobe LiveCycle ES SMS module that allows LiveCycle Services and Processes to integrate SMS messaging into the process flow.
The SMS module was written by Matt MacKenzie using the Twilio SMS service. To make it work, you can download the source from Uberity, read the instructions, get an account from Twilio and you’re good to go.
GitHub Project - https://github.com/uberity/uberity-lc-twilio
Twilio Account Setup - http://www.twilio.com/
Uberity LiveCycle ES Blog - http://blog.uberity.com/2012/02/extending-adobe-livecycle-es-to-use-sms-in-business-processes/