Express BPEL Engine Installation Guide 1.0

smuthhomelyServers

Nov 17, 2013 (3 years and 11 months ago)

174 views

EXPRESS BPEL
ENGINE


Installation

Guide

Express BPEL
Engine

Installation
Guide 1.0

Volume

1


EXP RESS BP EL
ENGI NE
-

I NSTALLATI ON

GUI DE

































Express BPEL

207 Dream Meadows • Brookfields

Bangalore , India 560
0
45

Phon
e 9880014665

• Fax
20
3.
5
5
5
.
0168




T
able of Contents
1.

Introduction

................................
................................
.........

1

2.

Standard Apache Release


Windows 7
...........................

2

1.

JRE 1.5.0_15 Installation

................................
............................

2

2.

Apache
TomCat 5.5.15 Installation

................................
...........

3

3.

Axis Server Installation

................................
................................

7

4.

PostGreSQL Installation
................................
..............................

8

1.

Express BPEL Database

................................
............................

11

2.

Express BPEL Engine Tables

................................
.....................

12

5.

Express BPEL Engi ne Core

................................
.....................

16

3.

Express BPEL Engine Software Install ation

................................
.

16

4.

Express BPEL Engine Confi guration
................................
............

17

3.

BPEL Engine Startup and Verification
.............................

20

INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0


1

1.

Introduction

This document intends to serve as the
Installation Guide for the
Express BPEL
Engine

(Standard Apache
)

Release

1.0
.
The Express BPEL Engine will be
available over multiple platforms and the following table describes the different
platforms including the
Standard Apache Release 1.0

Platform environment.


The target platform’s can be classified into the following,

-

Standard
Apache
Release

-

Standard JBOSS Release

The following table describes the Platform environment in detail


Platform

Name

Web Server
Container

WS

Stack

JRE

RDBMS

Operating
System

Current Release

Standard

Apache

Release



Apache Tomcat
5.5.15

Axis 1.4

JRE 1.5.0_15

PostGreSql

8.4.4
-
1

Windows 7


Windows

Se
rver(ver

??)


Linux

(ver ??)


Solaris

(ver ??)


Standard

JBoss

Release

JBoss (ver ??)

Axis 1.4

JRE 1.5.0_15

PostGreSQL
8.4

Windows
Server


Linux


Solaris




The following section will describe the Installation of the Standard Apache release
on the different operating systems.
Chapter

1

INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0




2.

Standard Apache Release


Windows 7



The Standard Apache Release on the Windows 7 environment requires the
following software to be set up for running the Express BPEL Engine,

-

JRE 1.5.0_15

-

Apache TomCat 5.5.15

-

Axis 1.4

-

PostGreSQL 8.4.4
-
1 (For Windows)

-

Express BPEL Engine 1.0


This section
will take the user through the installation and verification steps of
each of the above components.


The release consists of the zip file “
EBEngineApacheRelease1.0
-
Win7.zip


file. The user needs to unzip this into a temporary staging area to proceed with
the
installation. The location of the temporary staging directory is referred to as the
$STAGING_DIR
throughout the rest of this document.



1.

JRE 1.5.0_15 Installation


To install the JRE 1.5.0_15 version on the machine
,

-

Unzip the “
jdk1.5.0_15.zip
” found in the
$STAGING_DIR
\
3rdParty

directory to a location on the target machine. Typically the preferred
location is
C:
\
Program Files
\
Java
\
JDK1.5.0_15

directory.

-

Set the following environment variables in Windows,

o

JAVA_HOME
, pointing to the
location wh
ere jdk1.5.0_15.zip file
was unzipped.

o

Append the existing
PATH

variable with
$JAVA_HOME
\
bin

This completes the installation of JRE 1.5.0_15. To verify the installation, open a new
windows command prompt and type the following commands,


C:>
echo %JAVA_HOME%


C:>echo %PATH%

This should display the environment variables

pointing to the correct JRE Path.


Note that the jdk1.5.0_15.zip file is included for convenience and has no changes from the
JRE1.5.0_15 Release. The user could download th
e JRE1.5.0_15 directly from the Java
website and follow the above steps to complete the installation.



INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



2.

Apache TomCat 5.5.15 Installation

The Apache Tomcat 5.5.15 installer should be present in the following location
$STAGING_DIR
\
3rdP
arty
\
apache
-
tomcat
-
5.5.15.exe
.

The rest of the section
will describe the installation procedu
re using the installer
.

Launching the installer should bring up the apache tomcat’s installation wizard
described in the screen below
.

Figure 1 : Apache Tomcat
5.5.15 Wizard


Clicking the Next button brings up the license agreement screen. Accepting the licence
agreement screen brings up the following screen. Please select the components as
shown below in the screen and click on “Next”

to select the install path
.

Figure 2 : Apache Tomcat Components


INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



4

Figure
-
3

shows the install path selection dialog, Please select the required path. Figure
-
3 shows the default path that Tomcat Installer uses whic
h in most cases should
suffice.This default path is referred to as
$CATALINA_HOME

throughout the rest
of this document.

Please note that the CATALINA_HOME specified in the dialog below must
not have any space
s, else the start/stop scripts for Tomcat server don’t work
correctly. The figure below is a bad example of the De
stination directory sine it
has a space in “Tomcat 5.5”, it could be fixed to “Tomcat5.5”.

Figure
3
-

Apache Tomcat Installation Path


Clicking on “Next” on takes the user to configure the basic parameters of Apache
Tomcat described in the Figure 4

below.


Figure 4



Apache Tomcat Basic Configuration


INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



5

Select the Connector port as
8080

and specify the password for the admin user and
click on “Next” to specify of JRE’s location required by Apache Tomcat.

Figure
5
-

Apache Tomcat JRE location


Specify the location where JRE1.5.0_15 was installed in the earlier Section 1 of this
document. Clicking on “Install” will complete the basic installation of Apache Tomcat
5.5.15.

Once Tomcat finishes the installation uncheck the “Run Apache Tomcat” optio
n in
the last screen as shown in the Figure
-
6
. This is because we don’t want tomcat to
startup now as a service as more configuration needs to be done.

Figure 6

: Apache Tomcat Completion screen


INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



6

After completing the basic installation follow the steps be
low to complete the
installation and configuration of Apache Tomcat.

-

The basic installation does not install scripts to start and stop the Apache tomcat
server from the command line. Unzip the file “apache
-
tomcat
-
scripts.zip” file from
the location $STAGIN
G_DIR/3rdParty location into the location where Apache
Tomcat was installed.
This adds the .bat files required for starting/stopping
the Tomcat server
.

-

Verify the basic installation with the browser by typing
http://localhost:8080
. This
should bring up the Apache Tomcat’s
default page as shown in Figure 7.

Figure 7


Tomcat Installation verification


Note that the default installation of Tomcat does not include the installation of the
Tomcat Administrator (hi
ghlighted in Figure 7). To install the Tomcat Administrator
follow the steps described below,

-

Unzip
the apache
-
tomcat
-
5.5.35
-
admin.zip from the $STAGING_DIR
\
3rdParty into a
temporary location

(
referred to as $TEMP).

-

Copy the file “admin.conf” from
$TEMP
\
conf
\
Catalina
\
localhost directory to
$CATALINA_HOME
\
conf
\
Catalina
\
localhost directory.

-

Copy the
$TEMP
\
server
\
webapps
\
admin directory into $CATALINA_HOME

\
server
\
webapps directory.

-

Create

the
admin

user
by adding the following line in the $CATALINA_HOME
\
c
onf
\
tomcat
-
users.xml
file.



<user

username="admin"
password="admin"

roles="admin,manager"

/>


INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



7

-

Restart

the Tomcat

server and try to access the Admin application. (

if clicki
ng
on Admin on the webpage
shows
an
error then refresh

the browser cache by
clicking on Shift key
)


This should bring up the Apache Admin Application. For further information
please refer to the Apache Tomcat website for installation of the Apache Admin
application if the above steps do not work.



3.

Axis Serve
r Installation

The Axis 1.4 distribution has been included in the Express BPEL Installable, to install
the Axis 1.4 software follow the steps described below,

-

Unzip the axis
-
1_4.zip found in the $STAGING_DIR/3rdParty directory into
a temporary location,
referred to as $TEMP_AXIS

-

Copy the $TEMP_AXIS
\
webapps
\
axis directory to $CATALINA_HOME
\
webapps directory.

-

Copy “activation.jar” file from the $STAGING/3
rd
Party directory into
$CATALINA_HOME
\
common
\
lib directory.

-

Complete the installation of Axis 1.4 on Ap
ache Tomcat environment by
restarting Apache Tomcat by shutting it down and starting it up using the
following commands on the command promp
t from $CATALINA_HOME
\
bin directory

> s
hutdown

> s
tartup


-

To verify the Axis 1.4 installation
restart Apache Tomcat by try accessing the
fo
llowing webpage on the browser
http://local:8080/axis/
.
The page should
show that axis has been installed
. Further verify the installation by clicking on
the “Validation”

link. Clicking on this link should display the

“Axis Happiness
Page” which should show that all the mandatory jars were found. (Ignore any
message that states that optional jars were not found for now).
INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



4.

PostGreSQL Installation

For this release of Express BPEL PostGreSQL
-
8.4.4
-
1 for Windows needs to be
installed. The PostGreSQL has been included in the BPEL Installable and its locations
is
$STAGING_DIR
\
3rdParty
\
postgressql
-
8.4.4
-
1
-
windows.exe
.

The PostGreSQL installer is a wizard

based installer and when brought up displays the
following
screen


Figure 8 : PostGreSQL Installer Start screen


Clicking on “Next” should display the dialog box shown in Figure
-
9 that shows the
location where PostGreSQL will be installed, the user
can accept the default location
specified by the installer.


Figure 9 : PostGreSQL Install location

INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



Clicking on “Next” brings up the following screen where the data directory location
needs to be specified where PostGreSQL

will store the database and its contents. The
default suggested by the installer can be accepted by the user.

Figure 10 : PostGreSQL Data Directory Location


Selecting “Next” brings up the database password creation dialog. Enter a password of
choice.

Figure 11 : Password Entry

INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



Clicking “
Next
” takes the user to the screen to specify the port on which the database
to listen on for database connections. The default port is
5432
, the user can change the
port if required.

Figure 12 :

Port Number


The next screen allows the user to specify the default locale that will be used by
PostGreSQL server. Please enter “English, United State” in this dialog box.

Figure 13 : Default Locale

INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0




The parameters specified by th
e user are used by the installer to install the database.
After the Database installation is completed the user needs to create the following
entities in the Database required by the Express BPEL Engine software.

1.

Express BPEL Database

To create the Databa
se required by Express BPEL Engine the user must launch the

PGAdminIII
” application from the Windows
-
>All Programs
-
>Postgres SQL 8.4
-
>pgAdminIII menu.

After lauching the pgAdminIII application the user must double
-
click on the
PostgresSQL 8.4
tree
item,
doing so will bring up the password entry screen where the
user needs to enter the database password specified during the installation phase.
[The
PostgresSQL 8.4 (localhost:5432) tree item is highlighted in the Figure
-
14]

The following screens shows
the

Connect to Server” dialog asking for the password.


Figure 14 : Opening connection to database server.


Once the database connection has been established the user can create the database
required by Express BPEL by selecting the “
New Database

popup
-
menu item that
can be seen by right
-
clicking on the “
Databases(1)”

tree item. Selecting the “New
Database” popup menu item brings up the “
New Database
” dialog box as shown in
Figure
-
15 below.

In the “
New Database
” dialog the user needs to specify th
e following values for the
fields,
(as shown in the Figure
-
15 below)



Name




as

ExpressBPELDB

INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



12



Owner




as postgres



Tablespace


as pg_default


Figure 15 : Create Database Screen


Inputting the values mentioned above and clicking on “OK” should create the
ExpressBPELDB Database.

2.

Express BPEL Engine Tables

Express BPEL Engine software requires the following tables to be created in the
ExpressBPELDB

Database for its operations,



EBPro
cessTable



EBProcessidgen

To

create the EBProcessTable click on the “
New Table
” popup
-
menu item that can
be seen by right clicking on the “ExpressBPELDB
-
>Schemas (1)
-
>public
-
>Tables
(0)” leaf of the tree (as shown in Figure 16).
Clicking on the “New Table”
menu item
the “
New Table…
” dialog box appears as shown in Figure
-
16.

INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



13

Figure 17 : New Tables Dialog Box


To create the “
EBProcessTable
” database table, follow the steps outlined below,



Enter “
Name
” as “
EBProcessTable




Select “
pg_default
” as the “
Tablespace
”.

as shown in
Figure
-
18
.



Figure
-
18 : EBProcessTable Table creation


INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0



14

Specify the following column specification in the “Columns” tab of the “New
Table…” screen.
An example of the “New Column…” screen is shown in Figure
-
19.


Figure
-
19 : New
Column screen


The
EBProcessTable

requires the following columns to be present with properties as
specified in the table below

Column

Name

Column

Type

Is NULL

Is Primarykey

Proessid

Integer

NOT NULL

Yes

Processname

Character varying

NOT NULL

No

State

Integer

NULLABLE

No

Startdate

Date

NULLABLE

No

Enddate

Date

NULLABLE

No

CompletionStatus

Integer

NULLABLE

No

CompletionStatusMsg

Character Varying

NULLABLE

No


After adding the columns to the EBProcessTable, click “OK” in the “New Table…”
dialog box
to create the table.

INSTALL GUIDE


EXPRESS BPEL ENGINE
(STANDARD APACHE
) RELEASE 1.0




Similar steps must be followd to create the “ebprocessidgen” table with the following

column definition shown in the able below.


After
creating the “Ebprocessidgen” table the user needs to create a row in the table
with the following SQL statement as shown in the Figure
-
20.
Note that the screen
shown below gets displayed when the user clicks on the “Inserts Scripts” submenu of
the “Script
s” popup menu that can be viewed when the user right
-
clicks on the
“ebprocessidgen” leaf within the tree. Running the scripts as shown below should add
a single row with the value 1.

Figure
-
20 Insert Row Script



Adding the row in the table completes the

PostGreSQL setup required by the Express
BPEL Engine software.

Column

Name

Column

Type

Is NULL

Is Primarykey

pid

Integer

NOT NULL

Yes



16



5.

Express BPEL Engine Core

Installation of the BPEL Engine Core involves the following steps,

-

Software Installation

-

ExpressBPEL

Engine Configuration



3.

Express BPEL Engine Software Installation

To install the software follow the steps outlined below,

-

Unzip the express
-
bpel.zip file found in $STAGING_DIR
\
ExpressBPEL
directory into $CATALINA_HOME
\
webapps directory.
[ 4]

-

Copy the fol
lowing jar files from the $STAGING_DIR
\
ExpressBPEL directory
to $CATALINA_HOME
\
common
\
lib directory [9]



cloning
-
1.7.jar



commonj
-
twm.jar



commons
-
discovery
-
0.2.jar



jaxen
-
1.1
-
beta8



jaxrpc.jar



objenesis
-
1.2.jar



postgresql
-
8.4
-
701.jdbc3.jar



saaj.jar



wsdl4j
-
1.5
.1.jar



xercesImpl.jar



mail.jar [19]



log4j.jar [22]

-

Copy the following jar files from $STAGING_DIR
\
ExpressBPEL directory
into $CATALINA_HOME
\
shared
\
lib directory

[10]



ae_axisweb.jar



ae_rt.jar



ae_rtaxis.jar



ae_rtaxisbpel.jar



ae_rtbpel.jar



ae
-
rtbpelsvr.jar



ae_tamino.jar



ae_wsio.jar



axis
-
jaxrpc
-
1.4.jar



castor
-
0.9.6
-
xml.jar



TaminoAPI4J.jar



TaminoJCA.jar



xml
-
apis.jar



xml
-
apis.kar



xmlParsetAPIs.jar



17


-

Copy the following files into
$CATALINA_HOME

\
webapps
\
axis
\
WEB
-
INF
\
lib

[14]

-

xercesImpl.jar

-

xml
-
api
s.jar

-

activation.
jar

-

mail.j
ar


-

Copy the “
axis.jar
” file from $CATALINA_HOMe
\
webapps
\
axis
\
WEB
-
INF
\
lib
directory to $CATALINA_HOME
\
common
\
lib directory. [17]


-

Copy the “
bpr
” directory found in $STAGING_DIR
\
ExpressBPEL

into
$CATALINA_HOME
\

directory. [7]


This completes the installation of the Express BPEL Engine


4.

Express BPEL Engine Configuration


1.

ENGI NE CORE CONFI GUR
ATI ON


Configuration of Express BPEL Engine properties must be done in the file
Express
BPELConfiguration.properties

found in
$CATALINA_HOME
\

webapps
\
express
-
bpel
\
WEB
-
INF
\
classes
\

com
\
expressbpel
\
engine
\
servlet

directory.

The figure below shows the default configuration file.


<?xml version="1.0" encoding="UTF
-
8"?>

<!

BPEL Engine Configuration
--
>

<
ExpressBPELConfiguration >



<EBConfigItem name="EBAxisConfiguration">



<property name="AXIS_MSGAUTH_ENFORCED" value="false" />


</EBConfigItem>




<EBConfigItem name="
EngineConfiguration
">


<property name="BPRPath" value="
C:
\
\
Tomcat55
\
\
bpr" />


<property name="WebAppRoot" value="
C:
\
\
Tomcat55
\
\
webapps" />


<property name="ApacheRoot" value="
C:
\
\
Tomcat55
" />


<property name="AxisServerConfiguration" value="
c:
\
\
Tomcat55
\
\
webapps




\
\
express
-
bpel
\
\

ebaxisconf.wsdd" />


<property name="Port" value="5367" />


</EBConfigItem>




<EBConfigItem name="
Persistence
">


<property name="hostname" value="localhost" />


<property name="port" value="5432" />


<property name="d
atabase" value="ExpressBPELDB" />


<property name="username" value="postgres" />


<property name="password" value="postgres" />


</EBConfigItem>


</ExpressBPELConfiguration>



18


In the
EngineConfiguration

section the user needs to modify the
path of the
following variables to point to the Apache Tomcat installation,

-

BPRPath

-

WebAppRoot

-

ApacheRoot

-

AxisServerConfiguration


Essentially this involves replacing the existing path “
C:
\
Tomcat55
” with the actual
path of the Apache Tomcat installed on
the machine.


In the Persistence section the user might want to change the following variables to
match the installation,

-

Port
, by default the value is 5432 but if the user specified a different port when
installing PostGreSQL Database, that port number s
hould replace the default
value.

-

Username,
the default value suggested by the PostGreSQL installed is
“postgres” but if the user specified a different name then it must replace the
default value in the configuration file.

-

Password,
the user must specify t
he password specified during the installation
of the PostGreSQL database.




2.

ENGI NE LOGGI NG CONFI
GURATI ON
[ 8]


The Express BPEL Engine uses log4j framework for logging me
ssages and errors. The
log4j configuration file “log.properties” is present in the
directory
$CATALINA_HOME
\
webapps
\
express
-
bpel
\
WEB
-
INF
\
classes
\
com
\

expressbpel
\
engine
\
servlet directory.

Figure below shows the default
log.properties

file. The user can change the location
of the log files by changing the log file pathname specified for t
he “
file
” and “
debug

appender. The current default values are “
C:
\
log
\
info.log
” and

C:
\
log
\
debug.log
” respectively.

The user must manually create the log path specified in this file (whether modified or
not) for log4j to be able to find the directory to

create the log files. Eg. If the user
accepts the default location specified in the file then the directory
c:
\
log

must be
created.





19



This completes the configuration required to be done for Express BPEL Engine
software installed in the previous section.


<?xml version="1.0" encoding="UTF
-
8"?>

<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd" >

<log4j:configuration>


<app
ender name="
file
"



class="org.apache.log4j.RollingFil eAppender">



<param name="maxFileSize" value="100KB" />



<param name="maxBackupIndex" value="5" />



<param name="File" value="c:/log/
info
.log" />



<param name="threshold" value="info" />



<layout
class="org.apache.log4j.Patt ernLayout">



<param name="ConversionPattern" value="%d{ABSOLUTE} %5p %c{1}:%L
-

%m%n" />


</layout>


</appender>



<appender name="
debugfile
"



class="org.apache.log4j.RollingFil eAppender">



<param name="maxFileSize" value="10
0KB" />



<param name="maxBackupIndex" value="5" />



<param
name="File" value="c:/log/info
.log" />



<layout class="org.apache.log4j.Patt ernLayout">




<param name="ConversionPattern"




value="%d{ABSOLUTE} %5p %c{1}:%L
-

%m%n" />



</layout>



<filter cl
ass="org.apache.log4j.vari a.LevelRangeFilter">




<param name="LevelMin" value="debug" />




<param name="LevelMax" value="debug" />



</filter>


</appender>


<root>


<priority value="debug">


</priority>



<appender
-
ref ref="debugfile" />


<appender
-
ref
ref="file" />

</root>




20

3.

BPEL Engine Startup and Verification

This section describes the startup a
nd process to verify if the installation and
configuration was successful.

To start the Express BPEL Engine restart the Apache Tomcat application by issuing
the following commands on a command prompt terminial.



Cd %CATALINA_HOME%
\
bin



Shutdown



Startup

Th
is should bring up the ApacheTomcat server which internally will bringup the
ExpressBPEL Engine. The ApacheTomcat console should display the following
messages if the EB Engine was installed successfully.

[ To be added ] .

Also check the log files produc
ed by Express BPEL Engine in the log file “info.log”
which show the following messages if the BPEL Engine is operational.






21