Defining a package

To create a release package

1. In the AR System Deployment Management Console, on the Manage Package tab, click Create.
   The Deployment Package Information console is displayed.
   

1. In the Deployment Package Information console, enter or select the appropriate data for the following fields:
   • Package Name— Enter the unique name by which you want to create the package.
   • Package Version—Enter the unique version number for the package.
   • Package Details—Enter the detailed description of the package.
   • Add File—Upload a file that you want to attach to the package. Click Add to browse and attach a file to the package. To prevent inadvertent inclusion of malicious code to the package, consider white-listing the attachment files. Before you attach a file, consider setting restrictions on file uploads. For more information, see Restricting-users-from-uploading-and-viewing-files-with-specific-extensions.
   • Notification Email—Enter the email addresses to receive email notifications about the status of your package. You can configure single or multiple email IDs (separated by semi colon) or, an email distribution list.
   • State—Select the current status of the package. This field shows the current condition or situation of deployment package in a specific stage. 
   • Status—Select the details describing the build status. This field shows the intermittent stage during the deployment of a package.
     For example, a deployment package might have the Build Pending status and is in a Building state. 
   • Status Reason—Enter the reason describing the current status of the package.

   • In the Deployment Package Information console, when all fields are read-only and you cannot enter information into the fields, perform the following steps:

     a. Log in to Mid Tier.
     b. Click Cache Settings.
     c. Click Flush Cache.

2. On the Deployment Package Contents panel, enter the information in the following fields to add contents to the package.

   • Content Type—Select the content that you want to add to the package. The following table describes the type of file that you might add to the package. You must have appropriate permissions for using the Content Type. For more information about permissions, see Deployment-Application-roles-and-permissions.

     Content Type	Description
     Add Packing List	Adds the packing list along with the contents from the Developer Studio to the current package. Use this option to add a packing list to an application package.
     Add AR Definition	Adds the objects to the current package. You can add the following AR objects to an application package: Active link guide Application Packing list Filter guide Webservice
     Delete AR Definition	Adds a delete object command to the package. The referenced object is deleted from the environment where the package is deployed.
     Add Data	Adds data to the current package. A package deployer can create a package by using this content type.
     Add Static Data	For BMC internal purposes only.
     SRM	Adds Service Request Management objects, like service request definitions (SRDs), process definition templates (PDTs) and supporting data to the current package. You can also add custom advanced interface (AIF) forms and custom workflows. A package deployer can create a package by using this content type. For more information about using the AR System Deployment Console to migrate Service Request Management objects and data, see Migrating BMC Service Request Management objects and data.
     HRCM	Adds solutions from BMC HR Case Management to the current package. A package deployer can create a package by using this content type.
     Application Object	Deploys templates such as, Incident template, Change template, and task template efficiently and reliably across environments. You can also deploy a custom application by using this content type. For example, if you have a task or a task group template on your AR System server then you can relate that task template or task group template with any application, such as Change Management or Incident Management. Application object offers the following options: Task template or task group template Incident template Change template Work Order template Custom application Service Targets
     Deployment Payload	Creates and deploys binary payload across environments. Binary payload is a set of binary files, configurations files, batch or Shell scripts, and executable files.
     Smart IT Definition	Imports or exports the Smart IT customizations without making any changes in the code. For example, you can configure the provider action for a specific field for running the attached workflows without changing the code.
     BMC Helix CMDB	Adds CMDB CDM definitions to the package. An Administrator can create a package by using this content type.

     For more information, see Adding-content-to-a-package.

   • Content Description—Enter the name of the content you want to add to the package.
   • Sequence—Select the sequence field is used to define the order in which the objects will be built, validated, and deployed. This field is auto-populated based on the number of contents you add to the package. You can use the increment or decrement buttons to change the order of the contents.
   • Status—Select the current status of the contents added to the package.
   • Status Reason—Select the reason describing the current status of the contents added to the package.
3. (Optional) Click Manage Pre-Check to build qualification for the package. 
   For more information about Pre-Check, see Defining-a-precheck-for-deploying-a-package.
4. Click Add, and then click Save.