Macromedia live cycle 7.2 Manual

Installing and Configuring LiveCycle for JBoss

 Configuring JBoss for BAM Server     77

If you are installing LiveCycle Workflow and manually deploying to JBoss, you must manually install and 
configure JBoss for BAM Server to run correctly.

BAM Server must be deployed on a different instance of JBoss than the one where 
LiveCycle Workflow Server is deployed. You must configure the following areas on the instance of JBoss 
that runs BAM Server:

●

Install the database drivers that JBoss requires to communicate with the Business Activity Monitor 
metadata database and the LiveCycle database. (See 

●

Create a data source file so that BAM Server can connect to the Business Activity Monitor metadata 
database. (See 

.)

●

Create a data source file so that BAM Server can connect to the LiveCycle database. (See 

●

Configure the Java virtual machine (JVM) that runs the JBoss application server (See 

.)

●

Change the thread configuration on JBoss. (See 

.)

●

Configure JBoss so that Business Activity Monitor events are not duplicated in JBoss logs. (See 

●

Change JBoss ports to avoid conflicts with other applications that are running on the same computer. 
(See 

To enable BAM Server to connect to the Business Activity Monitor metadata database and the LiveCycle 
database, you need to install the drivers for the types of databases that you are using.

➤

1. Obtain the mysql-connector-java-3.0.15-ga-bin-jar file from the MySQL website at 

2. Copy the file to the [jboss bam root]/server/default/lib directory.

➤

●

Copy the SQL Server 2000 database driver files (msbase.jar, mssqlserver.jar, msutil.jar) to the 
[jboss bam root]/server/default/lib directory.

LiveCycle and BAM Server run in completely different JBoss trees, which means drivers are 
needed in each tree, as a result you will have to reinstall these drivers for BAM Server. (See