PXE-BPEL howto.

["Quinlan, Daire (Daire)" <dq...@avaya.com>]

Theres been some discussion lately about getting PXE working correctly.
I got it working a while back and seem to have lost my notes as to how
exactly I did it , so this is from memory (uh-oh). Theres a couple of
things. Again, some of these might have been fixed since I was hacking
around with it. 

The pxe SA I build from the head revision on the SVN repo. Last time I
built it was the 2nd of march or so. The binary distribution I typically
use to compile and sanity check my processes is pxe-rc2-00145 or
whatever the name is, something similar to that.

Servicemix is a fairly recent release candidate binary distrib, forget
which one exactly.

so here you go, pretty random I'm afraid...

1. Theres a jar mismatch between the antlr that ships with SM
(antlr-2.7.5.jar) and the one that ships with pxe (slightly more up to
date version). I just renamed the one in the servicemix dist to
antlr-2.7.5.jar.bak and that did the job. I presume there's other more
complicated workarounds for this if you wanted to use both. Not doing
this gives you (IIRC) hibernate errors when the container is trying to
install the pxe service engine.

2. commons-attributes-api-2.1.jar must be in the classpath (I just
copied it into the lib dir)

3. in the servicemix.xml, when instantiating the jndi bean, org.xbean...
is now org.apache.xbean...

4. The shipped HSSQL doesn't work. (or at least didn't). I'm using MySQL
as my database, this requires changes to the hibernate.properties file
and (unfortunately) code changes the PxeLifecycle.java in the JBI
adapter. The relevent one is in trunk/pxe/jbi and change the
initHibernate method to your own data properties. Now, I can't remember
whether or not I tested this just be changing the hibernate.properties
but my gut feeling is that I did and it didn't make any difference
because the HSSQL dependency was hardcoded into the PxeLifeCycle class.

5. the provider for the internal bus services for pxe is
provider="uri:jbiBridge" NOT whatever is in the examples (iirc its just
jbi or something)

lastly, a good sanity check if the pxe-engine and the bpel process both
deploy correctly, is to fire up jconsole and check out the pxe engine
hanging off the servicemix JMX address
(service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi).
Both the pxe engine and the deployed process ought to be listed and
running.

D.

Re: PXE-BPEL howto.

[Guillaume Nodet <gn...@gmail.com>]

Thanks a lot for these informations.
I hope we will be able to provide an updated PXE demo soon based on
your feedback.

Cheers,
Guillaume Nodet

On 3/31/06, Quinlan, Daire (Daire) <dq...@avaya.com> wrote:
>
> Theres been some discussion lately about getting PXE working correctly.
> I got it working a while back and seem to have lost my notes as to how
> exactly I did it , so this is from memory (uh-oh). Theres a couple of
> things. Again, some of these might have been fixed since I was hacking
> around with it.
>
> The pxe SA I build from the head revision on the SVN repo. Last time I
> built it was the 2nd of march or so. The binary distribution I typically
> use to compile and sanity check my processes is pxe-rc2-00145 or
> whatever the name is, something similar to that.
>
> Servicemix is a fairly recent release candidate binary distrib, forget
> which one exactly.
>
> so here you go, pretty random I'm afraid...
>
> 1. Theres a jar mismatch between the antlr that ships with SM
> (antlr-2.7.5.jar) and the one that ships with pxe (slightly more up to
> date version). I just renamed the one in the servicemix dist to
> antlr-2.7.5.jar.bak and that did the job. I presume there's other more
> complicated workarounds for this if you wanted to use both. Not doing
> this gives you (IIRC) hibernate errors when the container is trying to
> install the pxe service engine.
>
> 2. commons-attributes-api-2.1.jar must be in the classpath (I just
> copied it into the lib dir)
>
> 3. in the servicemix.xml, when instantiating the jndi bean, org.xbean...
> is now org.apache.xbean...
>
> 4. The shipped HSSQL doesn't work. (or at least didn't). I'm using MySQL
> as my database, this requires changes to the hibernate.properties file
> and (unfortunately) code changes the PxeLifecycle.java in the JBI
> adapter. The relevent one is in trunk/pxe/jbi and change the
> initHibernate method to your own data properties. Now, I can't remember
> whether or not I tested this just be changing the hibernate.properties
> but my gut feeling is that I did and it didn't make any difference
> because the HSSQL dependency was hardcoded into the PxeLifeCycle class.
>
> 5. the provider for the internal bus services for pxe is
> provider="uri:jbiBridge" NOT whatever is in the examples (iirc its just
> jbi or something)
>
> lastly, a good sanity check if the pxe-engine and the bpel process both
> deploy correctly, is to fire up jconsole and check out the pxe engine
> hanging off the servicemix JMX address
> (service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi).
> Both the pxe engine and the deployed process ought to be listed and
> running.
>
> D.
>
>
>