Deploying BAM artifacts

Compared to SOA and OSB, BAM is definitely an outlier in terms of functionality as well as a method of migrating code into various environments. To begin with, the development of BAM artifacts is done on the server, whereas SOA and OSB development is primarily done in JDeveloper.

Note

OSB services can also be developed through the Service Bus Console.

This means that in some ways the deployment process is much easier, since there are really only two steps for exporting and importing BAM artifacts. Both of these steps are accomplished with the same tool, BAMCommand.

BAM artifacts, as mentioned earlier, can take the form of data objects, business queries, KPIs, business views, dashboards, alerts, or parameters.

Note

BAMCommand is the successor of ICommand, which was used in the earlier versions of Oracle SOA Suite 10g and 11g.

It is similar in many respects, but provides some additional commands, making it possible to import artifacts and data from 11g into the new 12c environment...