This user hasn't shared any profile information
Posts by moderator
Correspondences created in enterprises would typically have to be integrated to a back-end process for further distribution (via email, fax, print), document processing (apply digital signatures, encryption, etc.) or archival of the correspondence.
The Adobe Correspondence Management solution provides a convenient way to achieve this by leveraging orchestrations/processes on the ADEP Document Services platform for defining the back-end process (that can use one or more Document Services, based on the enterprise requirements), and providing the ability to easily bind them to a given correspondence template.
Read more about creating a postprocess for the CM solution on the Document Server.
Once such processes are created on the Document Server, can then be mapped to a Letter template in the Postprocess drop down of the Letter Template Editor (as shown below), where the available postprocesses (as defined on the Document Server) are listed:
Tip: If you create a new process, with an existing Manage Assets UI session opened, your process will not be listed in the Postprocesses dropdown until you relaunch or refresh (F5) the Manage Assets browser window (or open the Manage Assets UI in a new browser window).
When the correspondence creation is complete (using the Create Correspondence UI), users can Submit the correspondence (see snapshot below indicating the Submit button), which invokes the associated/mapped postprocess for that Letter template, with the final correspondence PDF and XML data (used to generate the PDF). The postprocess, which would be an orchestration, can then act upon the document (PDF) as necessary.
Original article at http://blogs.adobe.com/saket/cm-postprocess/.
For IBM WebSphere, see here.
LiveCycle ES2′s Configuration Manager (LCM) provides you two options for configuring JDBC data sources in WebLogic:
1) Package it inside the EAR files (more secure)
2) Create it in the WebLogic Admin Console
Choice #2 provides a lot more flexibility when it comes to configuring the data sources for database failover. Runtime configuration changes such as increasing the pool size can be done without having to un-deploy and re-deploy EAR files.
To ensure that the connections in the connection pool are valid, the following additional configuration changes are necessary. This is based on an actual customer deployment against an active-passive SQL Server database cluster. You can make changes as necessary to fit your IT environment.
1) In the ‘Connection Pool‘ tab for the JDBC data source, in the ‘Advanced‘ section, ensure that the checkbox for ‘Test Connections on Reserve‘ is checked
2) Set ‘Test Frequency‘ to 10 seconds
3) Set ‘Test Table Name‘ to “DUAL” or “EDCJOBENTITY”
4) Set ‘Seconds to Trust an Idle Pool Connection‘ to 5 seconds
5) Set ‘Init SQL‘ to “SQL SELECT * FROM DUAL” or “SQL SELECT COUNT(*) FROM EDCJOBENTITY”
6) Set ‘Connection Creation Retry Frequency‘ to 12 seconds
7) Set ‘Login Delay‘ to 0 seconds
8) Set ‘Inactive Connection Timeout‘ to 0 seconds
9) Set ‘Connection Reserve Timeout‘ to 10 seconds
Original article at http://blogs.adobe.com/livecycle/2011/04/configuring-livecycle-jdbc-data-sources-in-weblogic-for-db-failover.html.
LiveCycle ES2: UnsupportedClassVersionError: (oracle/jdbc/OracleDriver) bad major version at offset=6
If you are attempting to configure Adobe LiveCycle server using the LiveCycle Configuration Manager (LCM) with an Oracle database, you may encounter the following exception during the DB configuration step:
Caused by: java.lang.UnsupportedClassVersionError: (oracle/jdbc/OracleDriver) bad major version at offset=6 at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:258) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151) at java.net.URLClassLoader.defineClass(URLClassLoader.java:589) at java.net.URLClassLoader.access$400(URLClassLoader.java:123) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1034) at java.security.AccessController.doPrivileged(AccessController.java:279) at java.net.URLClassLoader.findClass(URLClassLoader.java:491) at java.lang.ClassLoader.loadClass(ClassLoader.java:631) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:597) at java.lang.Class.forNameImpl(Native Method) at java.lang.Class.forName(Class.java:130) at com.adobe.livecycle.cdv.validator.DBValidator.validateDB(DBValidator.java:174)
This error can occur if you are not using the correct Oracle DB driver, or the correct Java JDK for your platform.
You should check the Oracle DB driver and JDK version required in the relevant platform matrix. With LiveCycle ES2 for example the platform matrix is located here:
So if you were to install LiveCycle ES2 on AIX 5.3 with WebSphere 7, you should be using the 64-bit JDK 1.6 SR7 provided by WebSphere (WAS_HOME/AppServer/java), and the ojdbc6.jar Oracle driver.
Be sure to set the JAVA_HOME and PATH environment variables as instructed in http://help.adobe.com/en_US/livecycle/9.0/prepareinstallsingle.pdf
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/.
- David McMahon
If you have installed a patch or service pack for LiveCycle ES you may need to uninstall this at a later date, or you may have a requirement to document this process fully as part of your installation/configuration documentation.
This information is outlined in the readme file provided with each patch or service pack, and I will just expand on that giving some more detail here. In this example I will discuss uninstalling LiveCycle ES Update 1 SP4 (18.104.22.168), to go back to LiveCycle ES Update 1 SP3 (22.214.171.124) on Windows.
Before installing/uninstalling any patch you should take note of the current versions installed so you can verify your steps have been successful later. Take a screenshot of the About screen, and the Service Management screen from the AdminUI.
AdminUI > About screen (note the Patch version “SP4″ and Service Pack version “8.1.5192.1.284202.47″, and the Patch level of each deployed component “SP4″):
AdminUI > Services > Applications and Services > Service Management screen (note the Component Versions “8.1.5192.1.284202.47″, “8.1.5193.1.279333.70″, etc…):
Before running through the uninstallation process it would advisable to make a backup of your existing configuration in case any unexpected problems should arise. To do this, you should make a copy of the entire LiveCycle installation directory (excluding the MySQL folder if it exists within the LiveCycle directory).
You should also take note of the following configuration properties from AdminUI > Settings > Core System Settings > Configurations:
- Location of temp directory
- Global document storage root directory (Changing this value will result in data loss unless you also manually move the data)
- Location of the Adobe Server Fonts directory
- Location of the System Fonts directory
If you have LiveCycle Content Services ES installed, you should also have the location of the Content Services root directory which you entered during the original installation/configuration process.
Read the full blog post at http://blogs.adobe.com/dmcmahon/2011/12/20/livecycle-es-how-to-uninstall-a-patch-or-service-pack/.
There is a confusion about what features of Acrobat and PDFs in general offer by way of securing documents. I would like to do a very cursory overview of the items that I have so far seen users consider “security.”
To be clear, by “security” I mean the ability or inability to access the contents of the PDF, thus safeguarding information from entering the wrong hands.
1) Not Security-Oriented
Unlike on your Dollar, Euro or Pound notes (etc), the watermark is NOT a guarantee of integrity, veracity or anything at all.
In the PDF world, a visible watermark only exists as a notification mechanism. If a watermark says “Confidential,” it is only warning the viewer that the content is confidential, but will not otherwise try to make itself indelible.
It is meant to be a very visible mark on the page, with the added property of not completely obfuscation the items underneath (allowing readability to be maintained)
A Certified PDF carries a digital signature certifying that certain things can and cannot be done with it. Namely:
-A PDF certified to run privileged scripts can run scripts requiring special privileges, such as writing to the hard drive.
-A PDF certified to be unmodified means that so long as the PDF has been modified withing given parameters (fields filled in for example), then the certification will hold. If a visual aspect of the PDF changes though, the certification will be broken, and Acrobat will report an error.
Certification covers a number of other use cases as well, but I hope the above illustrates sufficiently why this is a not a security-related item, rather a usability concern.
c) Reader Extensions Usage Rights
Acrobat and LiveCycle can extend the usability of PDFs to Adobe Reader, the free PDF viewing application. By extending usability features, you can allow Reader users to fill in forms and save that content, add comment annotation, and other functionality.
However, if the same extended form is opened in Acrobat, the user can do to the PDF pretty much anything that Acrobat has at its disposition.
REUR adds functionality to Reader. Any extra functionality it does not add is a restriction that Reader already had.
a) Password Protection
Using password protection, you can encrypt the PDF so it can only be opened by a person who has the password. You can also prevent the PDF from being used in certain ways, such as modifying the pages.
You cannot however track who has opened the PDF, when and at what IP. That is the domain of Rights Management.
b) LiveCycle Rights Management (aka Policy Server)
LiveCycle 7 introduced Policy Server, later renamed to LiveCycle Rights Management. Adobe LiveCycle/ADEP Rights Management protects your documents from being accessed by parties you have not authorized to do so.
This allows the document publisher to:
-protect with a user ID/password combination
-force the identification to go to a remote server
-restrict usage rights depending on the user’s group
Read the full article at http://blogs.adobe.com/an_tai/archives/176.
- 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.