LiveCycle Doc team

Here's the list of Knowledge Base tech notes that the LiveCycle ES team has published in the past two months:

• LC ES Workspace: how to change the language of Workspace
• LC ES: OOO Delegation/Queue sharing tasks not appearing in delegee's worklist
• Access Control - Adding permissions in LiveCycle Workbench
• Comic Sans MS font - Italic style
• PDF/A Metadata missing extension schema" during PDF/A conversion (LCES821SP2)
• WRL 3D images manipulation in LC PDFG ES 3D
• Initialization failure after failed migration
• Policy for third party components in Adobe LiveCycle products
• LiveCycle ES Processes Do Not Support Collections of Collections

Posted by Tasmina Patel at 1:59 PM | Permalink | Comments (0)

Recently, I was developing a LiveCycle ES component that uses Java APIs that are new to me. As I was thinking about how to implement the functionality that these new APIs offered into a LiveCycle ES component, a development pattern occurred to me. This pattern can be used by any LiveCycle ES component developer.

Because a LiveCycle ES component runs as a service, there isn't an easy way to debug the application logic. That is, how can I set a breakpoint in the Java code and step through it? How can I ensure that these APIs are doing what they are supposed to do?

The answer is to use Java APIs inside a test Java console application. Then, you can set a breakpoint and step through your Java application logic to ensure the application logic works properly. Once you are satisfied the application works, copy the application logic from your test Java project to your Java project that creates a custom component.

This worked for me. The new Java APIs I was using were proxy Java APIs that consume a web service that returns real-time weather information. That is right - I wanted to embed a custom service into LiveCycle ES that returns real-time weather information so I can embed weather information into a PDF document. And using this pattern, I was able to ensure that the Java APIs worked before I used them inside a LiveCycle ES component.

Note: If you are interested in knowing how to create a custom LiveCycle ES component that invokes an external web service, then keep an eye out for a future development article titled Invoking Web Services using Custom Components to appear on the LiveCycle ES developer center. As a component developer, this is an article you won't want to miss.

Posted by Scott MacDonald at 2:00 PM | Permalink | Comments (0)

Let's say you have configured LiveCycle ES with an enterprise domain that retrieves user information from an LDAP directory server. If you decide to move those users to another LDAP directory server, there are steps you should follow to retain the same user IDs and prevent users from losing tasks that are currently in their To Do lists in LiveCycle Workspace ES.

Here's what you do:

1. Make sure the new LDAP directory server contains entries for all of the users that you want to migrate.


2. Log in to LiveCycle Administration Console as an administrator.


3. Click Settings > User Management > Domain Management and select the checkbox next to the domain associated with the old LDAP directory server. Click the Sync Now button. This pulls user information from the old LDAP directory server into your User Management database.


4. On the Domain Management page, click the name of the domain. This opens the Edit Enterprise Domain page. Click the Directory Provider.


5. On the Edit Directory page, click the Directory Users tab. Change the Unique Identifier to a user attribute that is common between the old and new LDAP directory servers (e.g. dn or mail) and then click Finish.


6. Go back to the Domain Management page and re-synch the domain containing the old LDAP directory server. This migrates your users' unique IDs to the user attribute that you specified in the previous step.


7. On the Domain Management page, click the name of the domain, and then click the Directory Provider.


8. Click the Server Settings tab. Change the Server and Port settings, along with any other settings that are different for the new LDAP directory server.


9. Click the Directory Users tab. Leave the Unique Identifier value as-is, but change the rest of the settings according to the new LDAP directory server and then click Finish.


10. Go back to the Domain Management page and re-synch the domain, which now contains details about the new LDAP directory server. This migrates your users from the old LDAP directory server to new LDAP directory server, based on the Unique Identifier.


11. On the Domain Management page, click the name of the domain, and then click the Directory Provider.


12. Click the Directory Users tab and change the Unique Identifier back to the new LDAP server-specific Unique ID (for example, objectguid for Active Directory).


13. Go back to the Domain Management page and re-synch the domain.

From now on, your users will be synchronized from the new LDAP directory server, and any existing users will still have access to the items in their LiveCycle Workspace To Do list that were there before the migration.

Posted by Melanie Jackson at 3:13 PM | Permalink | Comments (0)

Looking for a new way to learn about LiveCycle? Prefer watching TV to reading books? If so, you might like Adobe TV: http://tv.adobe.com, which contains videos on LiveCycle and other Adobe products. You can browse or search for topics that you're interested in, save your favorite videos to "My Library" or share them on social networking sites, and subscribe to RSS feeds of your favorite shows.

Posted by Melanie Jackson at 9:44 AM | Permalink | Comments (0)

After installing LiveCycle ES, there are a number of URLs that you use to access various LiveCycle ES web applications. Here's a cheat sheet for those URLs.

Where:

[host name] is the name of the server where you installed LiveCycle ES. Type localhost if you are logged onto the server.
[app port number] is the default port number for these supported application servers:

• JBoss : 8080


• WebLogic: 7001


• Websphere: 9080

Example:

If you installed LiveCycle ES on a JBoss application (named LC-SERVER) and wanted to use the LiveCycle Reader Extensions ES web application, type http://LCSERVER:8080/ReaderExtensions in a web browser. Please note the capitalization!

Posted by Gilbert Yu at 9:04 AM | Permalink | Comments (0)