Posts tagged customization

Setting up the ICR development environment

This is the first blog post in the series on customizing the Adobe Integrated Content Review solution.

***

The Integrated Content Review solution ships with a solution interface and building blocks that you can customize as per your organization’s requirements. Before you set out to customize these components, you must first set up your development environment. Setting up the ICR development environment involves the following broad steps:

  1. Set up prerequisites
  2. Locate the solution interface and required dependencies
  3. Understand available projects
  4. Set up available projects in Flash Builder
  5. Set up Java projects in Eclipse
  6. Build and deploy the solution interface

For detailed information about each of these steps, refer to this PDF document (download).

Watch out this space for more customization scenarios for ICR!

——-
Original article at http://blogs.adobe.com/ADEPhelp/2011/08/setting-up-the-icr-development-environment.html.

Customizing LiveCycle Workspace 9.x using Flash Builder 4.x

- Gilbert Yu
When Customizing the LiveCycle Workspace ES2 User Interface [link] guide was released, it was before Adobe Flash Builder was available for us to do our certification testing. Technically, it is possible to use Flash Builder provided you use the Flex SDK version 3.4.1, ant-contrib.jar file version 1.0b2, and Ant-plug-in as described in the guide. For more information, see the LiveCycle Product blog for steps in the posting Customize LC Workspace ES2 UI using FB4 Premium on 64-bit O/S

In a future release, we plan to complete certification testing and update the guide with updated instructions, but in the meantime, here are some instructions for you to configure your environment to build Workspace customizations using Flash Builder 4. You must complete the last step in the blog when your development environment is a 64-bit operating system.

Happy customizing!

——-
Original article at http://blogs.adobe.com/livecycledocs/2011/02/customizing-livecycle-workspace-9-x-using-flash-builder-4-x.html.

Content Services: WebSphere stops responding when many concurrent threads are running

Samartha Vashishtha 

When the storeContent operation for Content Services 9 is invoked with more than 30 threads, the WebSphere application server may stop responding.

Follow these steps to resolve the issue:

  1. In WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers and then click a server name.
  2. In the right pane, click Thread pools under Additional Properties.
  3. Click WebContainer and, on the Configuration page, increase the value of the Maximum Size field by double the number of threads that you need to run. For example, increase the value of the Maximum Size field by 80 if you want to run 40 threads.
  4. Click Apply or OK.
  5. Click Save directly to the master configuration.
  6. Restart the WebSphere application server.

——-
Original article at http://blogs.adobe.com/livecycledocs/2011/02/content-services-websphere-stops-responding-when-many-concurrent-threads-are-running.html.

Setting up JBoss to auto reconnect after database outage

Darren Melanson

If you had a database outage or failure while JBoss was up, you’re likely in a situation where you would have to restart JBoss because the database connections didn’t get reconnected for you. You’re likely also faced with a massive set of log files due to the data source complaining about it not being able to connect to the database.

If you want JBoss to automatically reconnect the data source pool(s) for you, here’s some settings to use (only valid if using a “local-tx-datasource”):

1) <autoReconnect>true</autoReconnect>
2) <check-valid-connection-sql>an efficient select statement</check-valid-connection-sql>
3) <failOverReadOnly>false</failOverReadOnly>
4) <maxReconnects>50</maxReconnects>
5) <initialTimeout>15</initialTimeout>

In the above settings, if the data source connectivity is lost (database down or network failure) – then JBoss will automatically attempt to reconnect 50 times every 15 seconds. You can obviously set those numbers to values suitable to your environment. It’s also important to set the failOverReadOnly flag to false as it ensures that recovered connections are writable.

Additionally, some people prefer to include a valid and efficient SQL statement in the “check-valid-connection”, it’s completely optional but a good practice in environments where stale connections are common. Optionally, there’s also “new-connection-sql” which will check on newly created connections.

——-
Original article at http://blogs.adobe.com/livecycle/2011/03/setting-up-jboss-to-auto-reconnect-after-database-outage.html.

Go to Top