Defining a package
A package is a set of workflow object definitions, data, Service Request Management objects or service targets that you create in a development environment so you can promote the package across environments, such as QA or production.
To create a release package
- In the AR System Deployment Management Console, click Create from the Manage Package tab in the navigation pane to view the Deployment Package Information form.
In the Deployment Package Information console, enter or select the appropriate data for the following fields:
Package Name—The unique name by which you want to create the package.
Package Version—The unique version number for the package.
Package Details—A detailed description of the package.
Notification Email—Email address 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—The current status of the package.
Status—The details describing the build status.
A state is the current condition or situation of a deployment package, whereas a status is an intermittent stage during the deployment of a package.
Status Reason—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:
i. Log in to Mid Tier.
ii. Click Cache Settings.
iii. Click Flush Cache.
On the Deployment Package Contents panel, enter the information in the following fields to add contents to the package.
Content Type—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 2019-10-21_03-49-49_BMC Remedy Deployment Application roles and permissions.
Content Type Description Add Packing List
Adds the packing list along with the contents from the BMC Remedy Developer Studio to the current package. For more information, see Adding a packing list to a package.
BMC recommends using this option to add packing list to an application package.
Add AR Definition
Adds the objects to the current package. For more information, see Adding a definition file to a package.
Also, enables you to add the following AR objects to an application package:
- Active link guide
- Packing list
- Filter guide
For more information, see Adding AR object to an application package.
Delete AR Definition
Adds a delete object command to the package. The referenced object is deleted from the environment where the package is deployed. For more information, see Deleting a definition file from a package.
Adds data to the current package. A package deployer can create a package using this content type. For more information, see Adding data to a package.
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. For more information, see Adding SRM to a package. A package deployer can create a package using this content type.
For more information on using the AR System Deployment Console to migrate BMC Service Request Management objects and data, see .
HRCM Adds solutions from BMC HR Case Management to the current package. A package deployer can create a package using this content type. For more information, see Add HRCM Data to a package.
The Application object allows you to deploy templates such as, Incident template, Change template, and task template efficiently and reliably across environments. You can also deploy a custom application using this content type.
For example, if you have a task or a task group template on your AR 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
Work Order template
For information about adding an out-of-the-box Application Object to a package, see Add an application object to a package.
The Deployment Payload allows you to create and deploy binary payload across environments. Binary payload is a set of binary files, configurations files, batch or Shell scripts, and executable files. For information about adding a Deployment Payload to a package, see Add a Deployment Payload to a package.
Smart IT Definition
The SmartIT Definition offers to import or export the SmartIT 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 code. For more information about adding a SmartIT Definition to a package, see Add a SmartIT Definition to a package.
CMDB Adds CMDB CDM definitions to the package. An Administrator can create a package using this content type. For more information, see Add a CDM definition to a package.
Content Description – The name of the content you want to add to the package.
Sequence – 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 – The current status of the contents added to the package.
Status Reason – The reason describing the current status of the contents added to the package.
- (Optional) Click Manage Pre-Check to build qualification for the package.
For more information about Pre-Check, see Defining Pre-Check.
Click Add, and then click Save.