In blogpost I will show you the steps how to get this working on the WebLogic 12c JEE container and in Oracle Enterprise Pack for Eclipse as IDE.
First step is to download OEPE , Coherence and WebLogic 12c and install WebLogic with OEPE.
Next step is to start Eclipse and create a workspace.
After the initial eclipse setup, we can add the Activiti designer plugin to Eclipse. Go to Help menu and Install New Software
Use http://activiti.org/designer/update/ as value in the Work with field and select Activiti BPMN Designer
Finish the installation.
Download Activiti ( I used 5.12 version ) and extract the zip.
We need to update the WebLogic Jackson Core and Mapper JSON jars so these matches with the two demo application wars ( else you get some jackson reporting errors )
cp ../activiti-5.12/wars/activiti-explorer/WEB-INF/lib/jackson-core-asl-1.9.9.jar /Oracle/Middleware12.1/modules/org.codehaus.jackson.core.asl_184.108.40.206_1-8-3.jar
cp ../activiti-5.12/wars/activiti-explorer/WEB-INF/lib/jackson-mapper-asl-1.9.9.jar /Oracle/Middleware12.1/modules/org.codehaus.jackson.mapper.asl_220.127.116.11_1-8-3.jar
Now we can add a new server to your Eclipse workspace and create a new WebLogic domain.
For the Rest Activiti demo which uses its own basic authentication we need to disable the WebLogic authentication interception. You can do this by opening the config.xml of the WebLogic domain in an editor and add
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials> just above the end tab of the security-configuration element
Next steps is to extract the two demo applications. This way we can deploy these wars as WebLogic exploded folders. Now we can easily change the Activiti configuration files without making new wars ( change what you like and restart WebLogic server).
The demo activiti-explorer and activiti-rest applications need to have its own repository database , I will use MySQL ( tried Oracle as database but this will give me a lot of SQL group by and Month , Year errors ).
Here are my MySQL statements.
create database activiti;
create database activiti2;
create user 'activiti'@'%' identified by 'activiti';
grant all on activiti.* to 'activiti'@'%';
grant all on activiti2.* to 'activiti'@'%';
create user 'activiti'@'localhost' identified by 'activiti';
grant all on activiti.* to 'activiti'@'localhost';
grant all on activiti2.* to 'activiti'@'localhost';
mysql activiti -u activiti -pactiviti < ../activiti-5.12/database/create/activiti.mysql.create.engine.sql
mysql activiti -u activiti -pactiviti < ../activiti-5.12/database/create/activiti.mysql.create.history.sql
mysql activiti -u activiti -pactiviti < ../activiti-5.12/database/create/activiti.mysql.create.identity.sql
mysql activiti2 -u activiti -pactiviti < ../activiti-5.12/database/create/activiti.mysql.create.engine.sql
mysql activiti2 -u activiti -pactiviti < ../activiti-5.12/database/create/activiti.mysql.create.history.sql
mysql activiti2 -u activiti -pactiviti < ../activiti-5.12/database/create/activiti.mysql.create.identity.sql
Next we can update the db.properties file in activiti-explorer/web-inf/classes folder
Also update the db.properties file of the activit-rest application also in /web-inf/classes folder
Deploy these exploded web applications to WebLogic.
After a successful deployment of these two application we can shutdown the WebLogic container so we can disable the second time demo data generation. ( the rest demo application does not have demo data )
For this we need to update the activiti-standalone-context.xml in activiti-explorer/web-inf/classes
put these demoDataGenerator entries to false
<bean id="demoDataGenerator" class="org.activiti.explorer.demo.DemoDataGenerator" init-method="init">
<property name="processEngine" ref="processEngine" />
<property name="createDemoUsersAndGroups" value="false" />
<property name="createDemoProcessDefinitions" value="false" />
<property name="createDemoModels" value="false" />
<property name="generateReportData" value="false" />
Startup WebLogic and so we can test the demo applications.
Go to http://localhost:7001/activiti-explorer
use kermit as username / password
use kermit as username / password
Go to Vacation request proces and click Start Process
Complete the Form
The manager must approve
Claim and complete the task
Optionally look at the activity reports.
Or manage the repository.
For the Rest Activiti demo application we first need to fill the user, groups tables.
Add an admin record to act_id_group
Add the kermit user
Assign admin group to the kermit user
Next steps we can test the rest services
I will use the Advanced Rest Client plugin of Google Chrome browser.
First check the login of the kermit user
Next step is to retrieve the kermit user details.
We need to provide Authorization: Basic HTTP Header property with kermit:kermit as value in base64 encoding
The last part is the Activiti Designer in Eclipse.
Create an Activiti Project and after that import or add an Activiti Diagram.
Open the BPMN process
Design your process.
Export your process from the Package Explorer.
Upload the generated bar export file to the activi-explorer application or to the rest application ( use basic authentication, upload the bar file and use application/x-www-form-urlencoded as Content-Type )
I also greated a LDAP module so you can use Activiti with a LDAP repository as Active Directory, OpenLDAP or the internal WebLogic LDAP.