Oracle Lite and SOA Suite

The Oracle SOA Suite bundles a number of Oracle products (BPEL Process Manager, ESB, Oracle Business Rules and Web Services Manager) to provide complete set of service infrastructure components for building, deploying, and managing SOAs. For the windows platform it also comes with slimmed down version of Oracle Lite, an embedded database.

Why Oracle Lite?
Oracle Lite has a lot of great features including data synchronisation, device management, as well as support for SQL92 and ACID transactions amongst other things. It is the embedded relational database features that are used for the ‘basic’ installation of SOA Suite on windows. Antony Reynolds recently posted a great article on basic and advanced installation options which really puts an emphasis on the fact that Oracle Lite is intend to get you developing fast and not for production environments.

In the development environment the SOA Suite will use Oracle Lite under the hood and generally you don’t need to access this database. Of course, there are always the odd occasions when you do, such as tracing an error, or doing an upgrade.

Connecting to Oracle Lite
Over the summer a patch set was released to upgrade Oracle Application Server (SOA Suite) to The patch (#6148874) is available on metalink. The post installation steps involve running a database script. Since the SOA Suite is distributed with a slimmed down Oracle Lite there is no Mobile Client Workspace, i.e. webtogo web app, to manage the database, so the Mobile SQL Client is your easiest option.

Mobile SQL Client ($ORACLE_HOME\Mobile\Sdk\BIN\msql.exe) is used to connect to an Oracle Lite version 9 and upwards database. For earlier versions SQLPlus can be used. The version distributed with SOA Suite is The usage is quite like SQLPlus:

msql system/manager@jdbc:polite:

For the SOA Suite there are three databases: orabpel, oraesb, orawsm. Connecting to the database used by Oracle BPEL Process Manager looks like this:

D:\msql system/manager@jdbc:polite:orabpel

Oracle Lite MSQL Version
Copyright (c) 1997, 2005, Oracle. All rights reserved.

Connected to: Oracle Lite ORDBMS
Database Name: ORABPEL (Read Write)
Database Version:
Auto Commit: off
Driver Name: oracle.lite.poljdbc.POLJDBCDriver (OLite 4.0)


Another option to using Mobile SQL Client is to use Oracle SQL Developer a free graphical tool for database development. Just use the same JDBC connection properties that you can find in the Enterprise Manager, and ensure the olite*.jar files (in Mobile/SDK/bin) are in the classpath.

Oracle Lite is OK for a small SOA Suite development environment and even the slimmed down version that is distributed provides access to the databases via the Mobile SQL Client.

6 thoughts on “Oracle Lite and SOA Suite

  1. The ESB folks are kind enough to provide a script to connect to the ESB Olite db. BPEL wasn’t so kind. A slight modification of the delivered ESB Olite script worked for me. Prior to that, MSQL.exe wasn’t finding the right JRE, but the batch script set the environment is a sample for windows set BIN_HOME=E:\product\\OracleAS_1\Mobile\Sdk\BINset CLASSPATH=%CLASSPATH%;E:\product\\OracleAS_1\Mobile\Sdk\BIN\olite40.jarset PATH=E:\product\\OracleAS_1\jdk\jre\bin\server;%PATH%%BIN_HOME%\msql.exe system/manager@jdbc:polite4@ %*I was able to connect in JDev, but couldn’t figure out how to get SQL*Worksheet to execute a SQL Script without copying and pasting the actual script contents and running it line by line manually in JDev.


  2. Thanks for this short describtion of Oracle Lite. That, I was missing when I tried to install Oracle Soa Suite (with patches).Regards,


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s