Bundle Your Application Artifacts
As a service administrator, you can manage snapshots of your application artifacts as bundles.
About Bundles
Bundles are snapshots of your application artifacts such as configurations and customizations at a certain point in time.
- Package custom development by defining a bundle that represents a subset of application artifacts in an environment such as development, test, or production.
- Migrate custom development and deploy the bundle on a target environment.
- Synchronize instances by promoting changes from one environment to another such as production to test.
- Restore the system when something goes wrong with an environment and you need to do a complete system restore.
- Create a backup of the environment or subset of application to save current state of the artifacts.
- Restore artifacts by importing from a bundle to restore state of the relevant artifacts to what was in the bundle.
You can bundle your application artifacts as:
- Data Config bundle: This includes pipeline parameters, report parameters, activation metadata, and data augmentations. You can install this bundle in an existing environment after a hard data reset. This is useful to leave content as-is and reset data pipeline.
- Semantic Model bundle: This includes main branch, tags, custom branch, duty and data roles for semantic extension.
- Security bundle: This includes custom groups, application roles, and custom security.
- Content bundle: This includes snapshots of Oracle Analytics Cloud folders, projects, dataset definitions, KPIs, decks, and duty roles for content.
- Composite bundle: This includes one or more of the other bundles.
- Environment bundle: This includes all artifacts of a specific environment to revert to a known state of system. For example, at the end of every week, the service administrator can create a bundle called DevEnv_YYMMDD to maintain a backup of the environment. You must first deploy the data configuration bundle or manually activate your data pipelines before deploying the environment bundle.
Note:
Ensure that you've activated the functional areas and data is available prior to working with the semantic models or content. Either manually configure and activate your data pipelines in the target environment or deploy a Data Config bundle to ensure that configurations and activations are at the same level as the source environment. Only then, it makes sense to deploy an Environment bundle, Semantic bundle, or Composite bundle since they depend on data.Create a Bundle
Create a snapshot of your application artifacts to save their current state. You can view the bundles that you created on the Bundles page.
Publish a Bundle
Publish a bundle from the source environment. This action generates a snapshot of the application artifacts and saves the snapshot to a repository.
Export a Bundle
Export the bundle .aab file from your source system to a repository or your local machine.
Import a Bundle
Import the bundle .aab file into the target environment from your computer to restore the state of the application to the checkpoint represented by the bundle.