Operations Actions Management modules

Operations Actions Management modules are predefined workflows that interact with multiple vendor implementations of system type, versus a system from a specific vendor. To achieve this level of autonomy from vendor-specific terminology and data structure, Operations Actions Management modules leverage a common data model, also known as a concept.

In addition to providing a critical layer of vendor independence, the concept provides the following benefits:

  • Provides a means to persist the schema of a data structure
  • Allows the persisted data structure to be accessible by workflows of different modules
  • When assigned to a context item, it creates a container in which values can be assigned to the elements of the concept
  • When assigned to a context item, it provides the means to individually access the elements of the data structure

Organization of Operations Actions Management modules

Operations Actions Management modules are grouped into the following functional modules, which are based on the IT Infrastructure Library (ITIL) and the types of systems to which they interface:

  • Change Management
  • Configuration Management
  • Credentials Store Management
  • DNS Integration
  • Event Management
  • Incident Management
  • IP Address Management
  • Problem Management
  • Storage Management
  • Task Management
  • Virtual Server Management
  • Workorder Management

Integration using Operations Actions Management modules

The operations action modules use the native API calls provided by the external system and builds transaction-based.

Example

The Virtual Server Management module contains the following transaction-based basic actions: Create Virtual Machine, Find Virtual Machine, and Delete Virtual Machine. Other actions in the Virtual Server Management module, such as Add CPU to Virtual Machine and Snapshot Virtual Machine, are composed of multiple API system calls.

In the case of Add CPU to Virtual Machine, the power status must first be determined, and if it is up, the virtual machine must be shut down. Next, the CPU is added; then the virtual machine is powered up.

Using BMC Atrium Orchestrator Operations Actions Management workflows, these steps are combined into a single action, hiding the mechanics of the integration interface from the integration solution. Using a single action simplifies the integration and shortens development time.

By using the Operations Actions Management modules to develop an integration solution, you reduce the upgrade task to replacing the Operations Actions Management modules.

Related topics

For more information, see the Operations-Actions-Management-Modules-and-Utilities section in the latest baoc201501 online technical documentation.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*