Getting Started
Table of Contents
Chapter 3. Installation
Procedure
Chapter 4. Starting
and Stopping BSOA
Chapter 5. Access
to the BSOA Console
Chapter 6. Launching
Zenflow: the BPEL Designer
Chapter 7. Launching
BPEM: the Orchestra Monitoring Tool
Chapter 9. Configuring
a Database With the Resource Adaptor
Chapter 10. Configuring
Loggers
List of Tables
Table 1‑1. Content of BSOA CD-ROM
Table 8‑1. System Resources Used by BSOA
Preface
This document provides the essential information for getting started with the BSOA Orchestra software.
BSOA CD-ROM
Table 1‑1. Content of BSOA CD-ROM
|-Linux® |
//Contains BSOA for Linux®. |
|-Windows® |
//Contains the BSOA executable for Windows®. |
·
BSOA requires Java Development Kit (jdk) 1.4.
Go to http://java.sun.com/j2se/1.4/.
·
BSOA requires JOnAS Application Server version 4.7.2.
Go to http://jonas.objectweb.org/download/index.html
.
Download the JOnAS 4.7.2 release build (JOnAS4.6.3-Tomcat5.5.12.exe for Window platform or jonas4.6.3-tomcat5.5.12.tgz for Linux® platform).
Go to the JOnAS installation procedure
(see http://jonas.objectweb.org/current/doc/howto/install_j2ee.html).
A 1 GHz processor and 512 Mo of RAM is recommended.
First, copy the file BSOA_Orchestra_'version'.tgz (which is
on the BSOA CDROM in the linux/ repository) to the hard disk. Untar the archive
with the command "tar zxvf BSOA_Orchestra_'version'.tgz". This
operation creates a repository named BSOA_Orchestra_'version'/ and representing
your_bsoa_repository.
· Step 1: Make sure that the JAVA_HOME, ANT_HOME and JONAS_ROOT environment variables are set.
· Step 2: Set a JONAS_BASE environment variable to the directory where the configuration files will be located.
· Step 3: Set BPEL_HOME environment variable to "the_repository_where_you_installed_bsoa/BPEL".
·
Step 4: Make sure the PATH contains
$BPEL_HOME/bin/unix, $JAVA_HOME/bin, $ANT_HOME/bin and
JONAS_ROOT/bin/unix
· Step 5: go to the directory where BSOA has been extracted and type "./install.sh".
To install the Bull Service-Oriented Architecture Platform, first install ANT and JOnAS.
·
Step 1: Make sure that the JONAS_ROOT and
ANT_HOME environment variables are correctly set and that the PATH contains
$JAVA_HOME/bin, $ANT_HOME/bin and JONAS_ROOT/bin/nt.
· Step 2: Then double click on "BSOA_Orchestra_'version'.exe", which is on the BSOA CD-ROM and follow the instructions.
Warning: Remember to run “configure-first.bat” at the end of the installation
To run BSOA, type "bsoap start".
To stop BSOA, type "bsoap stop".
To run BSOA go to the Start menu, Programs, BSOA, then click on start.
To stop BSOA go to the Start menu, Programs, BSOA, then click on stop.
To access the Orchestra Administration Console, connect to the following URL
http://Your_Host:Your_HttpPort/jiapAdmin (user bsoa, password bsoa).
(Default: http://localhost:9000/jiapAdmin).
To launch Zenflow, go to the directory BSOA_Orchestra_'version'. Then type zenflow.sh.
To launch Zenflow go to the Start menu, Programs, BSOA, BPEL Designer, then click on Zenflow.
To launch BPEM, BSOA must be running. Go to the directory BSOA_Orchestra_'version', then type bpem.sh.
To launch Zenflow, BSOA must be running. Go to the Start menu, Programs, BSOA, BPEL Monitoring tool, then click on BPEM.
The following table shows the system resources used by BSOA:
Table 8‑1. System Resources Used by BSOA
Parameter |
Default Value |
Described in file |
HTTP Host |
localhost |
Host name used by Orchestra Web start applications to get the connection |
HTTP Port Number |
9000 |
The port where the JOnAS Application Server listens to HTTP requests |
JRMP Port |
1999 |
The port Used by Orchestra Web start applications to get the connection |
JMS Port |
16082 |
Another port used by Orchestra Web start application to get the connection |
DataBase |
9001* |
The HSQL Database is used by BSOA to store JOnAS authentication parameters, and Orchestra user profiles. The HSQL database server listens on port 9001. |
Edit or create a $JONAS_BASE/conf/{datasource}.properties
file and add the following lines to configure the database:
datasource.name bpel
datasource.url {url} (e.g. jdbc:postgresql://localhost:5432/db_bpel)
datasource.classname {Driver} {e.g. for postgreSQL : org.postgresql.Driver}
datasource.username {username}
datasource.password {password}
datasource.mapper {mapper} {e.g. for postgreSQL : rdb.postgres}
# JDBC connection checking level.
# 0 = no special checking
# 1 = check physical connection is still open before reusing it
# 2 = try every connection before reusing it
jdbc.connchecklevel 1
jdbc.connmaxage 30
jdbc.connteststmt select 1
Create a database instance and add the jdbc driver to the CLASSPATH, except for HSQL that is already packaged and installed with JOnAS.
· Create an rar file. The following information explains how to migrate from dbm to JDBC RA:
- use the following command line to create the rar:
On Linux®:
RAConfig
-dm -p $JONAS_BASE/conf/HSQL1 $JONAS_ROOT/rars/autoload/JOnAS_jdbcDM
DM_HSQL_BPEL
On Windows®:
RAConfig -dm -p
%JONAS_BASE%\conf\HSQL1 %JONAS_ROOT%\rars\autoload\JOnAS_jdbcDM DM_HSQL_BPEL
This command will create a file DM_HSQL_BPEL.rar based on the file HSQL1.properties (remember to modify the HSQL1.properties file per the instructions stated above before running this command).
-
Copy the rar file to $JONAS_BASE/rars:
cp
DM_HQSL_BPEL.rar $JONAS_BASE/rars
·
Add the rar to the list of resource service in the
jonas.properties file.
For example:
jonas.service.resource.resources
DM_HSQL_BPEL
Edit $JONAS_BASE/conf/trace.properties.
The following lines are located at the end of the file:
#
-----------------------------------------------------------------------
# For Orchestra
# -----------------------------------------------------------------------
handler.orchestraFile.type File
handler.orchestraFile.output orchestra.log
handler.orchestraFile.pattern %d : %l : %h : %O{1}.%M : %m%n
logger.orchestraFile.additivity false
handler.orchestraConsole.type Console
handler.orchestraConsole.output Switch
handler.orchestraConsole.pattern %d : %l : %h : %O{1}.%M : %m%n
#logger.orchestra.handler.0 orchestraFile
#logger.orchestra.handler.1 orchestraConsole
logger.orchestra.level INFO
#logger.orchestra.engine DEBUG
#logger.orchestra.engine.traceBPI.level DEBUG
#logger.orchestra.engine.traceBPU.level DEBUG
#logger.orchestra.engine.traceEngine.level DEBUG
#logger.orchestra.engine.traceSM.level DEBUG
#logger.orchestra.traceManager.level DEBUG
#logger.orchestra.traceTimer.level DEBUG
#logger.orchestra.traceData.level DEBUG
#logger.orchestra.traceMonitoring.level DEBUG
#logger.orchestra.traceRestart.level DEBUG
#logger.orchestra.traceAdmin.level DEBUG
#logger.orchestra.traceBF.level DEBUG
#logger.orchestra.traceWS.level DEBUG
#logger.orchestra.trace.level DEBUG
The default configuration is “no logger”. This configuration can be changed by uncommenting some/all of the configuration lines.