Integrating a custom application with BMC Remedy Deployment Application
BMC Remedy Deployment Application has an extensible framework that allows you to promote objects from your custom application across development, QA, and production environments. You can also promote data from out-of-the-box Remedy IT Service Management application objects that are currently not supported by the Development-to-Production functionality.
For example, consider your organization uses a custom Remedy application that you use to manage contract employees details. The HR Manager periodically updates the data in this custom application with renewed or terminated contract information. You can easily and reliably promote these updates to contract objects across environments by integrating the custom application with an application object.
You must have appropriate permissions to promote a custom application object. For more information about roles and permissions, see BMC Remedy Deployment Application roles and permissions in BMC Remedy AR System online documentation.
Application object definition in BMC Remedy Deployment Application
An application object is a collection of data in a set of forms that jointly represent a certain entity of a Remedy application; for example, a contract or a template.
When you transfer such an entity from one Remedy instance (for example, development) to another Remedy instance (for example, test or production) you must also package all the related data from the different forms, transfer it to the target environment and then deploy it.
Sample forms available to integrate the custom application
BMC provides the following sample forms. You can use these sample forms while integrating a custom application with an application object:
Form type | Form name | Examples |
---|---|---|
Primary form | RDA:SampleApplicationObject_Primary | |
Staging form 1 | RDA:SampleApplicationObject_Primary_Staging | |
Secondary form | RDA:SampleApplicationObject_Secondary | |
Staging form 2 | RDA:SampleApplicationObject_Secondary_Staging |
Prerequisites
- The custom application that you want to integrate with an application object must have a primary form. Use the primary form to export data.
- Related secondary forms, if any, must be identified.
On the primary form, secondary forms, and on the staging forms the following fields are mandatory in addition to the out-of-the-box fields:
Field Name Field ID Parent_job_GUID 304287140 z1D Action 1000000076
Workflow to integrate your custom application
You must integrate your custom application with the application object so that you can promote the custom application by using BMC Remedy Deployment Application. The following graphic illustrates the different stages involved in packaging and deploying a custom application:
This table describes the steps to integrate your custom application with an application object:
Step | Action |
---|---|
1 | Register the custom Application Object |
2 | Add workflows to stage data |
3 | Add workflow to perform validation |
4 | Add workflow to perform promotion |
5 | Register the validation errors |
Where to go from here
Packaging and deploying a custom application object
Comments
Log in or register to comment.