Types of deployment packages
You can create and customize a codeless application in the following environments:
In a Developer Sandbox environment which you can provision yourself at developers.bmc.com
In a Tailoring environment, one of the three provided to customers who purchase BMC Helix Platform
After you create a codeless application, you can create an Install package for fresh installations of the application. An Update package is used for applying incremental updates to existing applications in an environment. Additionally, when you customize an application that you have purchased, you can create a content package to manage moving your changes and data from one environment to the next.
The following image provides information about the different types of packages that you can create:
Requirement for creating a deployment package
The following table helps you to determine which package you can create based on your requirements:
|Condition||Install package||Update package||Content package|
All the application data, such as the JAR files, definitions, and configurations.
Cannot include specific data only, such as JAR files, definitions, or configuration data in an install package.
|Only the changed items. Importing configuration data is optional.|
Custom code, original objects, customizations of objects in the bundles to which the objects are applied, configuration data, Foundation data, and application data.
|Version||Every package has a version number that you can modify according to your requirement.||Every package has a version number that you can modify according to your requirement.|
Every package has a version number which is the same as the version of the original application.
You cannot modify the version number of a content package.
|File naming convention|
<developer ID>.<application name>-<application version>-install.zip format.
For example, com.example.workorder-2.0.0-install.zip.
<developer ID>.<application name>-<update from version>-to-<update to version>-update.zip> format.
For example, com.example.workorder-1.0.0-to-2.0.0-update.zip.
<developer ID>.<application name>-<application version>-content.zip> format.
For example, com.example.workorder-1.0.0-content.zip.
Where to go from here
|Create and deploy entire application to test or production environments.|
|Create and deploy incremental changes of applications to test or production environments.|
Create and deploy tailoring changes or customizations of other people's applications to Tailoring, QA, and Production environments.
|Redeploy entire applications to test or production environments.||Reinstalling codeless applications|
Remove unnecessary applications from BMC Helix Innovation Studio.
|Uninstalling applications by using Innovation Studio|