ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: Ode.war; persistency with MySQL using BEA Weblogic Server
Date Fri, 30 Nov 2007 15:36:19 GMT
Hi again Vincent,

Could you open a Jira issue and attach your WLSFactory code there?

http://issues.apache.org/jira/browse/ODE

I'm asking because there's a little checkbox in Jira where you agree to
license your code to the ASF and it provides a clean IP trail for the
code....

TIA,
alex


On 11/30/07, Vincent <pimousse76@gmail.com> wrote:
>
> Hi Alex,
>
> Thanks for the answer. As you'll notice, I changed my "nickname" for
> my first name - this email is just
> another-email-that-can-be-spammed-as-I-do-not-care-about ;o)
>
> I just wanted to share my experiment on the mailing list - it may be
> useful one day for someone.
>
> I remind the context: BEA Weblogic Server 10.0 (WLS), Java 5, MySQL 5.
> What I did was to demonstrate the feasibility and assess the
> performances. So that's maybe not 100% clean.
>
> ========
> 1- Create a TransactionManager factory.
> As previously said, it is similar to the JBossFactory
> (
> http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.1/axis2/src/main/java/org/apache/ode/axis2/util/JBossFactory.java
> )
>
> I attached this factory to this email, see WLSFactory.java.
> Then add it somehow (either in an additional jar, or by updating ode's
> war) to the WLS classpath.
>
> ========
> 2-  Create the schema and tables in MySQL
> + Download and install a MySQL server
> + Create a schema called 'ode' and a user/pwd with appropriate
> credentials (grant select, insert, delete and update).
>
> + Add to the ode schema the tables listed at
>
> http://mail-archives.apache.org/mod_mbox/ode-user/200706.mbox/raw/%3cfbdc6a970706120754y62339783nf4accb5d758a4053@mail.gmail.com%3e/2
> .
> To generate this schema, a rake build is mandatory, refer to the
> mailing list:
> http://mail-archives.apache.org/mod_mbox/ode-user/200706.mbox/%3cfbdc6a970706120754y62339783nf4accb5d758a4053@mail.gmail.com%3e
>
> + Then the tables listed in ODE src at:
>
> http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.1/dao-hibernate-db/src/main/sql/\simplesched-mysql.sql
> .
>
> I sumed-up in an ode.sql file all the tables and indexes to create. I
> attached it to this email.
>
> ========
> 3- Create the 'ode-axis2.properties' file
> Add a ode-axis2.properties configuration file in ode.war/WEB-INF/conf
> Assuming that the datasource jndi name is 'mysql.jdbc.odePool.OdePool'
> and that the TransactionManager factory is
> org.apache.ode.axis2.util.WLSFactory:
>
> ode-axis2.db.mode=EXTERNAL
> # the datasource JNDI name:
> ode-axis2.db.ext.dataSource=mysql.jdbc.odePool.OdePool
> # the WLS TransactionManager factory:
> ode-axis2.tx.factory.class=org.apache.ode.axis2.util.WLSFactory
> # pay attention, the following class moved from
> 'org.apache.ode.daohib.bpel' pkg to 'org.apache.ode.dao.jpa' :
> ode-axis2.dao.factory=org.apache.ode.dao.jpa.BPELDAOConnectionFactoryImpl
> # not sure it has smth to see with persistency, but I found it in an
> example, so:
> ode-axis2.message.replicate.emptyns=true
>
> ========
> 4-  Create a datasource in WLS
> + Download and add the MySQL JDBC driver to the WLS classpath.
> + Start WLS and create a datasource (I defined the JNDI name as
> mysql.jdbc.odePool.OdePool).
>
> ========
> 5- Start WLS
> And redeploy the BPEL processes, it should work.
>
> ========
> Just few highlights about performances. I tried to figure out the
> impact of the <in-memory> setting on the persistency management.
> The following figures give a pretty good overview - but obviously they
> deserve a more detailed study.
>
> I attach it to this email, see figures.txt.
>
> Regards,
>
> Vincent
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message