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 second post Filtering/grouping in BAM by ‘specific’ metrics (explored solutions) I have 10 recognized/examined solutions appointed for this challenge.
In this post I will cover the functionalities of BAMCommand that I have used in the implementation/rollout of the EMS configuration (Populating BAM using JMS).
But first, what is BAMCommand?
BAMCommand is the command-line utility to export, import, migrate, clear, and delete BAM metadata, data, and project artifacts.
You can find BAMCommand in the directory ‘FMW_HOME/soa/bam/bin’. By calling BAMCommand without parameters gives you an overview of the possibilities. This overview is shown below: