Are you a developer or administrator looking for more control in migrating your customizations in your Remedy OnDemand environments? If so, a great utility is now available to Remedy OnDemand Administrators and Developers who are at Remedy 9 or higher. The utility, the AR System Deployment Management Console, or D2P (slang for Dev to Prod) as it is commonly referred, provides an effortless interface to promote workflow customizations across environments (Development, QA, and Production). This includes the promotion of both new and modified Service Request Definitions. D2P provides a simple method that consumes less time and increases your control of code promotions.


The process to build and migrate packages contains 5 quick and straightforward steps:

  2. BUILD (and validate)


To get to the D2P utility, you need to be an administrator and log on to a BMC AR System Server, go to the AR System Administration tab, and then to the AR System Deployment Management Console.


When you create a package, it allows you to search and select the objects that will be included in the package. You can use this utility to migrate both data and definitions.  Examples of definitions that can be included in D2P packages are:

  • Form
  • Filter
  • Active Link
  • Menu
  • Escalation
  • Container
  • Application
  • Image
  • Associations


As mentioned previously, the steps are very easy and consist of the following:


CREATE: This function allows you to add definitions to your package. The names of your definition items must match how they are entered in Developer Studio.  There is a sequence field that is auto populated as you add contents to the package and is used to determine the sequence in which package items are built, validated and deployed. Once you have created the package, it will show up in your list with a status of “Draft”.


BUILD: When you select “Build”, your package is validated and compiled for use. After the package is built, it will have a status of “Ready to Deploy”, and is ready for use. Note: You may need to refresh your browser to see the updated status.  If there is an error during validation/compilation, the reason for the error will be displayed in the Status field and the state will return to “Draft”.


EXPORT: Exporting the package creates a zip file that gets downloaded to your computer with all relevant files included.


IMPORT: To import the file, you would then log onto a BMC AR System Server in the appropriate environment and maneuver again to the AR System Deployment Management Console. Select Import and select the zip file exported from the previous server. Once imported, the package will show a status of “Ready to Deploy”. NOTE: If you are making changes to existing workflow, it is a BEST PRACTICE to back up existing files by exporting them before you import anything new.


DEPLOY: Select the imported package and Select “Deploy”.


Utilizing the AR System Deployment Management Console, Dev to Prod (D2P) promotion is streamlined with best practices for code promotion in mind. With straightforward packaging, each set of objects promoted is clearly defined for developers and admins who come behind you, version control is simple to manage, and everything is consolidated in a single easy to use interface. Simply put, D2P allows you to work effectively and reliably across all platforms, all while saving you valuable time.