Oracle BPEL & XE: Part 2
Today when reading through the BPEL forum (here) I found an entry named "oracle XE and BPEL - Clemens -". Funny, for the first time someone wrote to me personally on the forums. Well anyway - back to work ..
After reading the entry, it looks like my entry was not clear enough - so I thought to clarify a little bit.
Some while ago I blog'ed about using bpel and oracle xe as its dehydration store. And in of the comments, it's about changing the datasource(s) to use the newly built schema. For convenience - here it is .. (for BPELServerDataSource, the same applies to the other 2 ones, named BPELSamplesDataSource, and AdminConsoleDateSource)
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="BPELServerDataSource"
location="jdbc/BPELServerDataSourceWorkflow"
xa-location="BPELServerDataSource"
ejb-location="jdbc/BPELServerDataSource"
connection-driver="oracle.jdbc.OracleDriver"
max-connections="50"
min-connections="10"
connection-retry-interval="30"
max-connect-attempts="10"
username="orabpel101202"
password="orabpel"
url="jdbc:oracle:thin:@localhost:1521:XE"/>
The bold marked values, differ from your datasource for Oracle Lite!
Having questions? send your feedback on Oracle BPEL PM and XE here
1 Comments:
Clemens,
People should do one more step: to bump up the 'processes' and 'sessions' parameters at the database side otherwise BPEL server will run out of connections to the dehydration database under load. That is because there are 3 database connections pointing to the dehydration database and each of them create minimum 10 connections. The XE database side by default only has 40 processes open. They get run out very quickly.
connect system/welcome
alter system set processes = 100 scope = spfile;
alter system set sessions = 115 scope = spfile;
Please note you must re-start the dehydration database for the the changes to take effect.
11:27 PM
Post a Comment
<< Home