Managing the Development to Production (D2P) Package

A 'Development to Production' (D2P) package is a ZIP file which is imported from the Action Request System (AR System) web interface. It creates all jobs, transformations, indexes, data set and so on. The advantages of D2P package are:

  • To be usable with the Action Request System (AR System) containers as it does not require a physical access to the machine.
  • To have a smaller package which is easy to install and debug.

Download the package from the following EPD page: 

BMC Client Management, 21.02.02 Open link

D2P is supported from the Action Request System (AR System) Server version 9.1.4 and later. It cannot be installed on the previous versions.

For Action Request System (AR System) Server version 9.1.4 to 1808 patch 0, you need to perform a manual step before importing the package. For the Pentaho plugins, you need to add the following dependency (js-1.7R3.jar) in the ARSYS.ARDBC.PENTAHO and CMDB.ARDBC.PENTAHO sections of the pluginsvr_config.xml file. The file is located at C:\Program Files\BMC Software\ARSystem\pluginsvr\pluginsvr_config.xml.

<pathelement type="location">C:\Program Files\BMC Software\ARSystem\diserver\data-integration\lib\js-1.7R3.jar</pathelement>

Restart the plugin server or kill the plugin server process after editing this configuration file.

To import the BMC Client Management D2P package

  1. Use a BMC Client Management D2P package.
    1. Open the BMC Remedy Deployment Management Console.
    2. Click Transfer Package > Import.
    3. Select Browse from the pop-up window to navigate to the folder from where you want to import the package.
    4. Select the package that you want to import and click OK.
      The package is displayed on the list with the 'Deployable' state and the 'Ready to deploy' status.

  2. Deploy a package.
    Deploying the package extracts the contents package and imports the content to Action Request System (AR System). If the package is deployed successfully, the status of the package is updated to Deployed.

    To deploy a package, select the package from the table with status Ready to Deploy and click OperationsDeploy.

    To view the progress of the deployment, click Manage Package > View. A list of all the validations to be performed is displayed. Once all the validations are successful, the package status changes to Deployed.



    1Creating the FPIntegrationId index.
    2Creating the FPAssemblyId index.

    Creating the BCMBMC Client Management:Configuration form.

    4Adding a conditional statement to the form: Only one entry is possible.
    5Adding a conditional statement to the form: The 'Default' entry cannot be deleted.
    6Adding the 'Default' configuration entry.
    7Creating the BMC.FP.ASSETCORE dataset.
    8-16Creating the Reconciliation and Merge jobs with side elements.
    17-20Creating the Purge job with side elements.
    21Importing jobs and transformations. (You can find them using the UDM:Import form.)
    22Adding entries to SHARE:Application_Properties about adapters and dataset.
  3. Access the BMC Client Management form to modify the configuration.

    Previously, when the InstallerFramework package was used, the file contained the database configuration details. Now, with removal of this file, this configuration is done through a new form called BCM:Configuration. You have to access this form and modify the configuration or use the default values. To modify the BMC Client Management configuration form:
    1. Use the following URL to open the form in the Action Request System (AR System).
      http://localhost:8080/arsys/forms/<ARSystem server hostname>/BCM:Configuration
      The form is displayed.
    2. Type Default in the Short Description field and click Search.
      The result is displayed. 

    For BMC Client Management SQL Server installations, use the DB owner and the SQL Server Schema prefix for the search.

  4. Modify the database connection.

    1. Go to Spoon and open a job from the repository. 
      Under the Database Connections node, the AtriumDB and BCMDB connections are displayed.
    2. Double-click the connections and modify them to make them valid.
    3. Click OK.
    Connection settings are now modified globally.

    To use the modified jobs, close the open job first and then open the job that you want to run.

To rollback the BMC Client Management D2P Package

  1. Select the deployed BMC Client Management D2P Package.
  2. Click OperationsRollback and wait for the status change to 'Rolled back'.
  3. Click Manage Package > Delete.
Was this page helpful? Yes No Submitting... Thank you