...
Install WebLogic and configure a WebLogic domain with an AdminServer.
Prepare oracle database and deploy camunda to the WebLogic AdminServer as described in https://docs.camunda.org/manual/7.7/installation/full/wls/manual/ . This involves creation of schema camunda and the camunda tables as well as the dataSource for camunda.
Create a new schema for the outbox tables:
Log into SQL Plus (sys as sysdba) and create user TASKANA_TABLES for the outbox schema
Code Block > ALTER SESSION SET "_ORACLE_SCRIPT"= TRUE; > Create USER TASKANA_TABLES identified by <password for TASKAN_TABLES>
Log into SQLPlus as user taskana_tables
create schema taskana_tables via taskana-outbox-schema-oracle.sql script from the sql directory of taskana-adapter-camunda-listener-<version>.jar. Before running the script, change
%schemaName% --> TASKANA_TABLES
%camundaSchemaName% --> CAMUNDAgrant rights to camunda
Code Block GRANT INSERT,UPDATE,SELECT,DELETE ON TASKANA_TABLES.OUTBOX_SCHEMA_VERSION to camunda; GRANT INSERT,UPDATE,SELECT,DELETE ON TASKANA_TABLES.EVENT_STORE to camunda; GRANT CONNECT, RESOURCE, DBA TO camunda
Enable Taskana ParseListener and TaskListener:
copy taskana-adapter-camunda-listener-<version>.jar to <WebLogicDomainRoot>/lib
copy slf4j-api-1.7.30.jar and slf4j-simple-1.7.30.jar to <WebLogicDomainRoot>/lib to enable log entries from the taskana components.
find camunda-oracle-weblogic-service.jar in the subtree below <WebLogicDomainRoot>. We found it at <WebLogic-Domain>\servers\AdminServer\tmp_WL_user\camunda-bpm-platform\o3p2c6.
Edit this jar file, navigate to META-INF and modify META-INF/bpm-platform.xml
Add the taskana engine plugin:
<plugin>
<class>pro.taskana.adapter.camunda.parselistener.TaskanaParseListenerProcessEnginePlugin</class>
</plugin>
in the plugins section.
You might prefer to modify bpm-platform.xml in the downloaded Camunda distribution for WebLogic. In this distribution, you find bpm-platform.xml in the "modules\camunda-oracle-weblogic-ear-$VERSION.ear\camunda-oracle-weblogic-service.jar\META-INF" folder. If you modify bpm-platform.xml in this location, you must do it before you install camunda to WebLogic.Supply an external common property file for the ParseListener, TaskListener and the outbox REST api:
create 'properties - directory', e.g. <WebLogicDomainRoot>/taskanaconfig
modify <WebLogic-DomainROOT>/bin/setDomainEnv.cmd. 'Un-comment' the line that sets the PATCH_CLASSPATH and edit it so that it points to the fully qualified pathname of the 'properties - direcotory'
Place taskana-outbox.properties into the 'properties - directory'. This property file must contain the properties
taskana.adapter.outbox.schema (taskana-tables, the schema name of the outbox tables),
taskana.adapter.outbox.datasource.jndi (the jndi name of the datasource that can be used to access the outbox tables. You can use camunda's datasource or define an own one).
and it should contain the property taskana.adapter.create_outbox_schema=false, since this schema was created manually
Start WebLogic and install taskana-adapter-camunda-outbox-rest-<version>.war via the WebLogic admin console
...