Casemanagement with Camunda CMMN

I’m getting many customer questions about BPMN and CMMN. Customer cases are not really sequential nor parallel steps, but they need to have managed and traced steps. How to do it?

The answer is very simple, user Casemanagement. You will have a process model but your business steps can be executes in different orders. every case is handled on a different way. Some are dependance steps and others not. From each step you can decide to close the case(process). Some steps can be mediatory others not. Documents can be added to build the case, decisions can be made based on input.

In below I will try to explain a customer case which is handeling interruptions noticed by customer.

Customers fills in a form on web about a system interruption,

  • Service desk checks the details to determine if it is an interruption.
  • The customer will be contacted
  • the contact will be reviewed, based on the outcome of the review..
  • documents cane be requested..
  • documents can be reviewed and based on the review outcome..
  • more technical info can be requested.
  • in this case, it is also possible to create a customer case to close end the process at any time based on the step input.

In these steps you can even call a BPM to handle an approval process based on hierarchical decision.

Apache ActiveMQ Artemis on Oracle WebLogic 12c

The aim of this blog is to describe the configuration of WLS to connect to Artemis QM. 

This is based on a POC create for this purpose. 

  • Configuration for writing queue 
  • Created a project with a businessService to write the queue.
  • The Queue ‘DSLTEST’ created on the Artemis server.

Create JMSServer “Artimis_JMSServer_SOA_1” target it on soa_server1

  • Create JMS Module
  • ArtemisJMSModule
  • Create ForeignServer inside the module

Configure the JNDI connection URL and user the “org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory” as JNDI initial context Factory.  

Configure destination. Note that the Remote JNDI Name should start with dynamicQueue/<queuename>

Create a connection factory as Remote JNDI Name ‘QueueConnectionFactory’

Subdeployment should be like:  

Create a BusinessServer to write the queue

Create an oracle SB Proxy to read from the queue. The most important is that you use a ServiceAccount to authenticate the user.

Any Question? drop me a message