Failed on ‘Verifying JBoss for Adobe LiveCycle ES service is installed’
Windows turnkey service JBoss for Adobe LiveCycle ES does not exist

When checking in the Windows Service Panel, indeed there is no such service defined, even though the installer should have created it. I have not been able to replicate this issue, but it happened to me at a customer site and by searching Google it seems that others have run into it as well.

The Google search results tells us that some people forget to set the Java_Home system variable and that you should be using the right version of the JDK. However, this did not seem to be the problem in this case.

Through the install documentation you can find the steps needed to re-create the JBoss for Adobe LiveCycle ES service (page 62). You can use those to try and create the service ‘manually’. For our install, the problem seemed to be in the [LC_INSTALL_ROOT]\jboss\InstallJBossService.bat script file. Somehow the username / password did not seem to work, whatever we tried it failed. Well, sort off: strangely enought the command prompt output first mentions that there was an error, though still reports that the script was executed succesfully. Still no service created though.

The solution was too simple to come up with: just remove the username / password parameters from the script and execute it. This time the script did not fail and as expected created the service for us. Next thing to do is go into the service panel, select the ‘JBoss for Adobe LiveCycle’ service, right click to go to it’s Properties and in the Log On tab specify Log In As This Account. Then specify the username password (in my case “.\administrator” and the password), click OK and you are done.

Now run the LiveCycle Configuration Manager again and most likely it won’t fail anymore cause of the missing service. This seemed to have overcome our issue.

ps: When installing the turnkey solution, it is highly recommended to keep the right documentation at hand: Installing and Deploying LiveCycle® ES Using Turnkey.

Did you run into this issue as well? Please let us know if this worked for you or if you have additional tips for our readers.

___
This post was originally placed at the DrLiveCycle blog.

Not many people know that Adobe participates in quite some industry standards and supports their maturity/evolution such as BPMN, BPEL, BPDM and XPDL and that we are voting members of standard bodies such as OMG, OASIS and WFMC. Adobe is represented in all these standards bodies and actively participates in reviewing and authoring of these standards. We take a lot of that knowledge back into the decisions we make when developing our enterprise products, especially Adobe’s LiveCycle Enterprise Suite.

BPMN (Business Process Modelling Notation) is a specification for a couple of things:

• A graphical notation. E.g. How different activities are represented in a process diagram.
• Semantics of the graphical notation. E.g. What does it mean when you connect activities with a line.

From wikipedia:

The primary goal of BPMN is to provide a standard notation that is readily understandable by all business stakeholders. These business stakeholders include the business analysts who create and refine the processes, the technical developers responsible for implementing the processes, and the business managers who monitor and manage the processes. Consequently BPMN is intended to serve as common language to bridge the communication gap that frequently occurs between business process design and implementation.

Using the Process perspective in LiveCycle Workbench, one can visually create process maps that define and control your automated business processes. Since Workbench implements the main constructs for the graphical notation and the semantics of that notation as specified by BPMN, business analysts can create process diagrams using swimlanes, activities, events and associations following common modeling methodologies (we still have a gap to cover when it comes to modeling of Gateways).

To summarize: if you have been trained in BPMN, you will find it easy to model a process using LiveCycle Workbench.

If you want to read more on Adobe’s comments on BPEL and general standards, you should read this article on de LiveCycle DevNet:

ps: One should know that the current BPMN spec (v1.1) does not specify how a process diagram should be persisted by a modeling tool. There is no XML schema for example. However, there is another specification – XDPL – which does provide this and the BPMN v2 specification currently in review also has a defined schema for persistence. Since standards have not been defined or widely accepted, LiveCycle Workbench currently persist that process definition using custom XML for which Adobe has publish the XML Schema (which after installation can be found under the LiveCycle SDK/schema directory).