Concepts (the common data model)

The BMC Atrium Orchestrator common data model structure consists of a collection of data models, each of which is called a concept. These concepts store general data components that are mapped to any structured elements or vendor-specific fields for interacting with third-party applications. These mappings are held globally for the workflow.

Concepts are used in BMC Atrium Orchestrator to pass structured data. Structured data in BMC Atrium Orchestrator is represented as an XML document. When stored in a concept, structured data can be easily accessed and transformed by using an assignment or simple xPath statements. BMC Atrium Orchestrator Development Studio provides a concept editor that is accessible through the Assign activity.

The following figure illustrates a simple change request concept that is used to close a change request:


Gliffy Macro Error

You do not have permission to view this diagram.

The top box depicts the values and elements in the change request concept input. The workflow uses a data map to translate between the change request concept and the target third-party data field. The target third-party application returns data, which is then remapped to the change request concept.

Using this example, within the Change Management module, the change request process calls the Update Change Request workflow. The Update Change Request workflow transforms information from the conceptual representation of the change to the target system data model representation, and then calls the adapter.

The adapter communicates with the target system (in this example, BMC Change Management) and sends a response back to the Update Change Request workflow. The workflow then maps the target system data back into the conceptual representation of the change.

Was this page helpful? Yes No Submitting... Thank you