PaaS Partner Community

Business Process Management
March 9, 2018

Oracle BAM 12c Security by Dan Atwood

Juergen Kress
PaaS & Middleware Partner Adoption

Oracle Business Activity Monitoring (BAM) 12c comes with Oracle SOA Suite and BPM, and it is a very powerful tool that should be used on most projects. Organizations are using it successfully today to graphically visualize trends in their data to make operational decisions and to send alerts before issues occur.

One of the difficulties organizations initially have after installing Oracle BAM 12c is determining how to define the security levels and permissions for its different types of users. Oracle BAM has both coarse grained security defined at the application role level down to very fine grained security defined at individual BAM artifact and data object row levels.
BAM Coarse Grained Security - BAM Application Roles
For many organizations today, different parts of the organization will each access and share the same BAM domain. For some, the coarse grained predefined BAM security groups and roles assignments will suffice. When left to the default coarse grained security, these three types of BAM users will exist:

BAM Administrators in an organization are able to access and edit any data object, EMS, or projects that other teams have created
BAM Designers in an organization can access and edit any BAM project and their queries, views, dashboards and alerts that other teams have created
BAM End Users in an organization can view any dashboard as long as they know the URL for the dashboard. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Facebook Wiki