Renew BAM demodata

Recently I did a POC with BAM 12c at the customer. In a series of post’s I will describe my findings/experiences.
In the first post of this series I described the initial situation (Impact of ACM Implementation on BAM). This post ended up with the following challenge.

We have a ACM Case consisting of about thirty Case Activities. The Case and the individual Case Activities are housed in a private composite (1 + ~30 composites).

Challenge: How can we group/filter in BAM by ‘specific’ metrics that are present in each Composite. For example ‘ Department ‘.

In the Fourth post (Populating BAM using JMS) I described that I have used an oracle tutorial to Populate BAM in SOA using JMS. This tutorial and sample project can be found on the Oracle website. In the image below, you see the corresponding composite.

5image1

By calling this RequestService from different BPM processes BAM can be loaded with data via JMS). After that I went to work with this data in BAM to create dashboards. Hereby I ran into the following problem:
The dashboards that have to be developed have a data scope of 2 weeks. To test this properly I need at least 2 weeks of data. For this I created a dataset that contains data for 2 weeks. This data set, however, concerns the last 2 weeks. This means that the data actually been directly out-dated.

My challenge: How can it be ensured that the data is up to date?

Using the commandline tool bamloadgen it is possible to provide BAM with data. With this tool it is even possible to use placeholders to renew the data. But the options are limited to today and yesterday (For details see Oracle documentation). This means that bamloadgen is not suitable to renew data from 2 weeks.

I made my own solution.

Continue reading

Humantask Assignment: Names and Expressions Assignment via Rules

This blog post is part of a series of posts about humantask assignment. You can find the starting point of this series by following the next link.

In this post I will give an example of task assignment by Names And Expressions using Oracle Business Rules. I will use the same BPM process as in most of the other posts in this series.

image1

Continue reading

Humantask Assignment: Assignment by Names And Expressions

This blog post is part of a series of posts about humantask assignment. You can find the starting point of this series by following the next link.

In BPEL it is not possible to assign a task to a lane participant. The most simple assignment in BPEL is by Names and Expressions. In this post I will show this kind of assignment for both a BPEL and a BPMN process. In fact there is no difference between BPEL and BPMN. In this example I created a composite with a BPM component and a BPEL component. Both the BPEL process and the BPM process only contain a humantask. Actually it is the same humantask as show in the picture below.

image1

Continue reading

Humantask Assignment: sequential participants (four-eyes principle & sticky user)

This blog post is part of a blog post serie about humantask assignment. You can find the starting point of this series by following the next link.

If you look at the example in Humantask Assignment: not the same lane participant as previous task (four-eyes principle) you see two sequential humantasks. If these humantasks are both connected with the same task form there might be another method available to model the four-eyes principle. Namely: assigning participants sequentially to the same humantask. This means that there will be only one humantask in the process model.

image1

Continue reading

Humantask Assignment: not the same lane participant as previous task (four-eyes principle)

This blog post is part of a blog post serie about humantask assignment. You can find the starting point of this series by following the next link.

This post handles the assignment of a task to a different participant as the one who handled the previous task (four-eyes principle). This is the opposite of the blog Humantask Assignment: same lane participant. The difference is in the definition of the second humantask. For the rest it’s all the same. The following picture shows the resulting composite.

image1

Continue reading

Humantask Assignment: same lane participant as previous task (sticky user)

This blog post is part of a blog post serie about humantask assignment. You can find the starting point of this series by following the next link.

This post handles the assignment of a task to the same participant as the one who handled the previous task (sticky user). To demonstrate this I have extended the example of the blog Humantask Assignment: current lane participant. A second humantask is added to the process. This task is assigned to the same participant as the previous task. The following picture shows the resulting composite.

image1

Continue reading

Humantask Assignment: current lane participant

This blog post is part of a blog post serie about humantask assignment. You can find the starting point of this series by following the next link.

Assigning a task to the current lane participant is more or less the default setting when using humantasks.

To demonstrate the assignment of the humantask to the current lane participant I have created a simple BPM process that only contains a humantask activity. The following picture shows the resulting composite.
image1

Continue reading