We launched LiveCycle Data Services (LCDS) 3 public beta yesterday on http://labs.adobe.com/technologies/livecycle_dataservices3/.
The tooling has been enhanced and flex application development has been simplified. You can now develop new fully functional flex applications with no server code in just minutes.
There are a few videos to help people get started http://labs.adobe.com/technologies/livecycle_dataservices3/videos/.
The 64-bit version of WebSphere Application Server 6.1 ND does not come with a "Profile Management Tool" (PMT). IBM expects people to use the manageprofiles (.bat or .sh) script in the /bin folder of the WebSphere installation (C:\WebSphere\AppServer\bin\ for example). It is a good idea to create a dedicated WebSphere profile for LiveCycle instead of default ones named AppSrv01, AppSrv02 etc.
Here is a sample command (SUSE Linux Enterprise Server 10 example) to create a WebSphere profile called "LiveCycle":
./manageprofiles.sh -create -profileName LiveCycle -profilePath /opt/WebSphere/AppServer/profiles/LiveCycle -templatePath /opt/WebSphere/AppServer/profileTemplates/managed
If the command succeeds, the response would be something like this:
INSTCONFSUCCESS: Success: Profile LiveCycle now exists. Please consult /opt/WebSphere/AppServer/profiles/LiveCycle/logs/AboutThisProfile.txt for more information about this profile.
If you navigate to /opt/WebSphere/AppServer/profiles/, you will see that there now is a folder called LiveCycle there containing the new profile.
Change folder to the /bin folder of the new LiveCycle profile and federate the node to your cell. Make sure that the Deployment Manager process that manages the WebSphere cell is running. Run a command that looks like this (SUSE Linux Enterprise Server 10 example):
./addNode.sh DMgr.company.com DMgr_SOAP_ADDRESS
where DMgr.company.com is the DNS name of the server running the Deployment Manager process that manages the WebSphere cell.
If successful, you will get a response such as this:
Node ServerDNSNameNode01 has been successfully federated.
Here ServerDNSName is the DNS name of the node you just federated without its DNS suffix. This will also start the Node Agent for the node.
This new node (ServerDNSNameNode01 ) will now be visible in the WebSphere Admin Console. You are now ready to create the server and/or clusters to deploy LiveCycle. Please note that the LiveCycle Configuration Manager (LCM) only configures servers and/or clusters. It does not create them for you.
Here is a sample command (SUSE Linux Enterprise Server 10 example) to delete an existing WebSphere profile called "LiveCycle":
./manageprofiles.sh -delete -profileName LiveCycle
If successful, you will get a response such as this:
INSTCONFSUCCESS: Success: The profile no longer exists.
Workbench ES is LiveCycle ES' development IDE. It is Eclipse-based and hence is a desktop Java application. Java applications cannot utilize of all of the memory (RAM) available on the desktop unless they are explicitly allowed. This is specified by means of two JVM init arguments, namely -Xms (minimum memory to grab from Windows on startup) and -Xmx (maximum memory to grab if required, and never more).
-Xms and -Xmx can be configured in the workbench.ini file located in %WORKBENCH_INSTALL_ROOT%/Workbench/. If you are a frequent user of the 'Record and Playback' feature in Workbench, and if you use process variables in your orchestrations that can potentially hold large documents, the default JVM memory settings will cause OutOfMemoryExceptions. To avoid these, set -Xms and -Xmx to 256 MB and 1024 MB respectively, assuming that your desktop has enough RAM to spare.
1) Stop Workbench
2) Edit workbench.ini and save the changes
3) Start Workbench
Afterwards, the workbench.ini should look something like as follows (only the initial part shown):
#Product Runtime Configuration File
-vmargs
-Xms256M
-Xmx1024M
...
...
Now available on Adobe Labs are the public beta releases of Adobe Flash Builder 4 (formerly Flex Builder), Adobe Flash Catalyst and the Flex 4 Framework. Flash Builder 4 is the next evolution of Flex Builder, and includes a long list of feature improvements, new data-centric development features, and a new design-develop workflow with Flash Catalyst. Flash Catalyst, also now available in public beta, is a new interaction design tool for rapidly building application user interfaces without coding. Both Flash Builder and Flash Catalyst are based on the updated Flex 4 framework, also available for beta download.
Visit Adobe Labs to find out more and to download the installers.
