Managing Containers; Full Versus Delta Export/Import Containers

Objective

After completing this lesson, you will be able to protect your environment.

Manage Containers

Preserving Your Environment

In managing SAP environments, it's critical to ensure that the configurations, settings, and data you’ve meticulously built are protected against accidental loss or can be transitioned smoothly across different tenants. Let's delve into the methods and concepts involved in preserving your environment effectively.

The image displays the Administration section of an application, including options for managing tenant settings, tenant connections, containers, and archives. The numbers next to each option indicate the quantity of items associated with that section. The Manage Containers Administration section has 20 items, and the Manage Archives Administration section has 8 items.

Why Preserve Your Environment?

There are two primary scenarios where preserving your environment becomes essential:

Avoiding Accidental Deletion:

Scenario: You have built a comprehensive environment configuration. If accidentally deleted, recovering it can be complex or sometimes impossible.

Solution: Implement strong preservation measures to ensure that you can restore your environment to its previous state quickly and efficiently.

Migrating Changes Across Tenants:

Scenario: You've made significant changes or updates in a development tenant and must move those changes to a QA or production tenant.

Solution: Preserving the environment allows you to export configurations from one tenant and import them into another, ensuring that changes are replicated accurately.

Key Concepts: Containers and Artifacts

To understand preservation methods, you must familiarize yourself with some key concepts:

Container:

Definition: A container in SAP is like a digital vessel that holds and manages the various configurations, settings, and data of your environment.

Function: It bundles all changes, settings, and data, making it easier to export or import them as a single package.

Export and Import Types:

Full Export and Import:

It involves taking a complete snapshot of the environment. It captures the entire state of the environment, which can then be restored or transferred entirely.

Delta Export and Import:

It deals with changes made since the last export. It captures only the modifications, thus enabling incremental backups or updates without needing to export/import the entire environment.

In the app Manage Containers you can manage your environments across tenants where you can skip the manual modeling per tenant. Using this application you can expect a smoother, more efficient process of transferring environment. This requirement can be fulfilled by performing: Export, Download, Upload, Import. Which we will be discussing in the next slides.

The image appears to be a container management interface for an application. It displays a list of containers, including their names, file information, description, delta status, creation date, and creator. The containers include DEMO3, UNDEMIO, DEMONOTR, PADEMO, and several IMPORTDATA and PA containers. The interface allows for searching, sorting, and filtering the container information.

Manage Environments

Managing environments effectively requires a clear understanding of the processes involved in exporting, downloading, uploading, and importing your configurations and data. Here's a detailed guide that explains each step and provides insights into handling these tasks efficiently.

The image depicts a set of four blue rectangular buttons labeled Export, Download, Upload, and Import, with downward-pointing arrows beside each button.

1. EXPORT: Creating a Container

A container in SAP is essentially a package summarizing your environment along with its dependencies and artifacts. Here's how you create an export:

Introduction:

A container is a ZIP file encapsulating your environment. The size can be up to 30MB and depends on the components included—such as functions, fields, and model data.

Exportable Artifacts:

The export can include various artifacts like data models, workflows, configurations, processes, and more.

These artifacts ensure that the entirety of the environment is replicated accurately when imported into another tenant.

Process:

Navigate to the Manage Containers application.

Initiate the export process, selecting the environment and artifacts you wish to include.

The system generates a ZIP file containing the environment's JSON files and other necessary data.

2. DOWNLOAD: Storing the Export Locally

Once the export is complete, the next step is to download the exported container:

Action:

Download the generated ZIP file to your local system.

The ZIP file contains various JSON files representing your environment's configurations and data.

Importance:

This step ensures you have a local copy of your environment, which is essential for transferring to another tenant or for backup purposes.

3. UPLOAD: Transferring to the Target Tenant

After downloading the export container, the next step involves uploading it to another tenant for further actions:

Initiate Upload:

Log into the target tenant where you want to import the environment.

Navigate to Manage Containers and select the Create button.

Upload Process:

Under the General Information section, select the Upload file option and choose the ZIP file downloaded previously.

It makes the exported environment from the original tenant available in the target tenant, ready for the import process.

4. IMPORT: Finalizing the Transfer

The final step is importing the uploaded container into the target tenant's environment:

Preparation:

After the container upload, you have the option to import the environment.

Options for Import:

Import Environment: Directly imports the environment as it is.

Import as New: Imports the environment but allows you to create it as a new instance, which can be useful for testing or development.

Activation Setting:

By default, the environment does not activate automatically (Activation set to No).

Setting Activation to Yes is crucial if you want all runtime-dependent artifacts—such as processes, activities, teams, and reports—to be included during the import.

Completion:

Once the import process is completed successfully, the new environment appears in Manage Environments.

Verify that all components and artifacts have been imported correctly.

The Export Environment

Effectively managing your environment across different tenants involves a structured approach to exporting, downloading, uploading, and importing. Here's a comprehensive guide to understanding each step in detail.

The image shows a software interface for managing containers. It displays a table with information about various containers, including their name, file, description, delta, creation date, and creator. There is also an Export Environment dialog box that appears to allow the user to export the environment for a selected container.

1. Export Environment

To transfer your environment to another tenant, begin with the export process. Here’s how to do it:

Initiate Export:

Button: Locate and click on the Export Environment button in the Manage Containers application.

Environment ID: You are prompted to enter the Environment ID of the environment you wish to export.

Execution:

Confirm Export: After providing the Environment ID, initiate the export process. The system starts creating a container for the environment.

Details in Container:

Container Information: Once the export process is complete, a new ZIP file (called a container) appears in the list.

Metadata: This container includes basic information such as the person who executed the export, the date and time of the export, and other relevant metadata.

After the full Export you will see it in the list in the container.

The image shows a software interface displaying a table with information about various containers, including their name, file, description, delta status, creation date, and creator. The table can be sorted and filtered, and there are options to export, import, and manage the containers.

Export Delta: For Incremental Updates

For incremental changes after the initial full export, use the Export Delta feature:

When to Use:

If you've made more changes to the already exported environment and must transfer just those updates.

How to Export Delta:

Prerequisite: A full export of the environment is required before a delta export.

Enable Delta Export: In the Manage Containers screen, select the prerequisite container (full export).

Action: Click on the Export Delta button.

New ZIP File: A new ZIP file containing only the changes made since the last full export appears in the list.

Purpose of Delta Export:

Efficiency: Importing just the changes (Delta) to the next tenant avoids the need for a full environment import every time, saving time and resources.

Practical Example Scenario: Updating Production with Incremental Changes

Imagine you’ve made some additional configurations in the development environment after the initial full export:

Full Export: Export the full environment and download the initial ZIP file.

Apply Changes: Make necessary incremental updates in the development tenant.

Export Delta: Use the Export Delta feature to create a ZIP file with just the changes.

Upload Delta: Log into the target tenant and upload the delta ZIP file using the same steps as for a full environment.

Import Delta: Import the delta container, ensuring consistency without reimporting the entire environment.

The Import Environment

When transferring your SAP environment to a new tenant, the import process offers two options: Import and Import as New. Understanding the difference between these options is crucial for managing your environments effectively.

Before that, you must choose the Create button and select your zip file (environment).

The image shows a web application interface for managing containers. It displays a list of container details, including their names, file dependencies, and creation information. The interface also allows users to search, view, and create new containers.

Import: Overwrite Existing Environment

Functionality:

When you choose the Import option, it replaces the existing environment with the one you are importing.

This means that all the current configurations, settings, and data in the existing environment are overwritten by the newly imported environment.

When to Use:

Use this option when you want to update the entire environment and replace its current state.

For instance, if you’re confident that the new environment is an improved or updated version of what currently exists, this option ensures that all changes are applied thoroughly.

Considerations:

Risk of Data Loss: Be cautious, as this operation overwrites any existing configurations. Ensure you have appropriate backups if needed.

Consistency: This option is useful for maintaining consistency, ensuring the entire environment is updated to reflect recent changes or improvements.

Import as New: Create a Copy

Functionality:

The Import as New option creates a new instance of the environment. It does not overwrite the existing environment but instead adds the imported environment as a separate entity.

You can assign a different name to the new environment, keeping the original environment intact while duplicating its content.

When to Use:

Opt for this method when you want to test changes or modifications without affecting the current environment.

It’s beneficial for scenarios where you wish to compare the new environment with the existing one or when you simply need a clone for different purposes such as testing, staging, or development.

Considerations:

Name Change: You can rename the new environment to distinguish it from the existing one.

Resource Management: While this option helps in testing and development, be mindful of the resources as having multiple environments can consume more space and processing power.

The image shows a web application interface for managing containers and environments. It displays details of a specific container, including its file dependencies and general information. The interface also allows users to import new environments and shows a list of existing environments, including one named PA which is currently active.

Import Delta

To upload the environment to the next tenant a functionality called Import Delta is also available. The procedure and logic of the Delta Environment has already been explained. And just like normal transport or import, to be able to Import Delta of environment, it is mandatory that the environment with the same version is already present in the tenant before you can import the succeeding changes.

The image shows a web application interface for managing containers. It displays details of a specific container, including its file dependencies, general information, and the option to delete the container.

Next lesson