Transport Your Private Content Through File System
Learn how to move content between systems in .tgz
files.
Who does this apply to?
- Users with Read, Maintain, and
Share permissions for
Lifecycle.
- Admin and BI Admin standard
application roles.
About Transporting Using TGZ Files
You can export a package in a .tgz file and then import it to another system.
You can export the following:
- Analytic Applications
- Dimensions
- Currency tables
- Roles
- External connections, including Import Data Connections, Live Data
Connections, and Smart Data Integration (SDI) connections
- Allocation steps and processes
- Wrangles
- Legacy value driver trees
- Data locking
- Validation rules
- Data actions
- Multi actions
- Public files including folders, stories, models, and Digital Boardroom
presentations
When you import or export content through Transport, you name
and save the details of the imports and exports as units or
delivery units. The units are listed in the
Import and Export windows, along
with details such as their status, and start and finish times. This allows you to
examine and manage your import and export history. For example, you can open a
delivery unit to view what content was imported or exported, such as dimensions. You
can also open a unit again and reuse a unit, or change its details and export it
again if necessary.
Caution
It is not recommended to use exports to archive content.
Content can only be imported in the same version of the application from which
it was exported, or the subsequent version. After your system is upgraded again,
you cannot import the content.
For the maximum file sizes, see System Sizing, Tuning, and Limits.
Note
If you're exporting large files, then the option Enable Job for Export
and Import should be enabled. By default, it is set to
OFF. You can find this option at .
Exporting Content
You can export content in .tgz file and then move it across different
systems.
Procedure
-
Select .
-
Go to File System.
-
Choose the
(New) icon.
The New window opens. The left-hand pane contains
nodes that list the content that can be exported. This includes
dimensions, models, connections, currencies, roles, KPIs, value driver
trees, and files.
The Files node contains items saved within the
system's Public folder including stories, boardroom agendas, templates,
and uploaded files. You cannot export private files.
Note
If there are dependencies between contents, its dependent content is
automatically selected. You can deselect the dependent content.
If the file you are exporting contains content dependencies, those
dependencies must also exist in the Public folder.
When you export a connection, its credentials are not included in the
export for security reasons. You can manually enter the credentials
in the Connections page after importing the
connection.
When you export a model based on data imported from one of the
following sources, all of the schedule settings for importing data
to the model are included in the export. This allows you to continue
replacing or appending data for a model that is imported together
with its connection:
-
SAP Business Planning and Consolidation
(BPC)
-
SAP Business Warehouse (BW)
-
SAP BusinessObjects BI platform universe (UNX)
query
-
SAP ERP Central Component (SAP ECC)
-
SQL Databases
-
Salesforce.com (SFDC)
-
OData
-
SuccessFactors
-
Concur
-
In the left-hand pane, select the content you want to export.
To select all the items, choose the
Select All
checkbox. To search for items, enter a search term in the
Search box and choose the
(
Search) icon.
The items selected for export appear in the pane on the right.
-
If you want to export the data for the items you selected, select the
Data checkbox for the items in the pane on the
right.
Dimensions have master data, models have transaction data, and currencies
have currency data.
-
Select Export.
-
Enter a name for the export unit and select whether to include the audit
data for the items. Select OK.
The name for the window changes from New to
the name that you provided for the unit. A progress bar at the top of the
window shows how the export is being processed.
Results
Once complete, the export unit history appears in the
list of unit histories in the main
Export window. You can
open that unit to make changes to your previous selections and export the unit
again.
Importing Content
You can import content that is available in .tgz format.
Procedure
-
From the side navigation, choose .
-
In the Import window, select
Upload.
-
In the Upload dialog, select Upload from
Local File, choose Select Source
File, and browse for the file you want to upload.
-
Select OK.
-
In the Preview dialog, check that the file is what
you want to upload, and then choose Upload.
A New window opens that lists the content of
the upload.
-
If required, amend the import by selecting or deselecting the checkboxes
for the listed content.
-
Choose the Import icon and select options for
overwriting data during the import.
-
If an object selected for import does not exist on your system, the object will be
created and its data will be imported. The sharing settings will
be inherited from the folder that you import it to.
-
For objects that already exist in your system, your selections in the
Options window determine whether to
overwrite the object and update its data. By default, existing
objects will not be updated or overwritten.
Note
Depending on your selection, if the import contains any files or
objects with the same ID as a file or object in your system, the
version on your system may be deleted and replaced by the imported
content, or updated with new data. Its sharing settings may also
change.
In the
Options dialog, you can select:
- Update existing object:
If an object selected for import
already exists on your system, the object on your system is
overwritten and its data is updated. The sharing settings will not
be updated.
For models, however, the Model Data
Privacy setting and the access permissions assigned
to roles remain unchanged during the import.
- Import data only:
For objects that already
exist in your system, data is imported into each object, but the
objects themselves are not updated.
The Model Data
Privacy and Data Access
Control settings for models, as well as the
permission settings for users and roles, remain
unchanged.
- Drop Objects:
If an object selected for
import already exists on your system, the object on your system is
overwritten and its data is updated. The object's sharing settings
are inherited from the folder that you import it to. For imported
models and dimensions, the Model Data Privacy
settings and Data Access Control settings are
updated by the imported content, and the corresponding permissions
assigned to each role are reset.
-
Select OK to set the options.
-
Select Import to start the import.
The name for the window changes from New to
the name that you provided for the unit. A progress bar at the top of the
window shows how the import is being processed. The import unit history will
also appear in the list of units in the main Import
window.
-
For import data connections and live data connections, you may be prompted
to specify credentials. Select Go to Page to open the
Connections list. The names of connections that
are missing credentials appear in red. Select a connection and choose
(Edit Connection) to enter credentials for
it.
If you imported models based on a live data connection that was also
imported, data for the models will be available after you enter the
credentials for the connection.
If you imported one of the following connections and a model based on it,
any scheduled jobs for importing data to the model will continue to run.
You can edit the settings in the page to reschedule a data import to the model:
-
SAP Business Planning and Consolidation
(BPC)
-
SAP Business Warehouse (BW)
-
SAP BusinessObjects BI platform universe (UNX)
query
-
SAP ERP Central Component (SAP ECC)
-
SQL Databases
-
Salesforce.com (SFDC)
-
OData
-
SuccessFactors
-
Concur
If you imported a model based on one of these data sources, and its
connection does not exist in the new system, you cannot schedule a data
import for the model. To resolve this issue, import the model together
with its connection.
-
For Smart Data Integration (SDI) connections, you must perform the
following steps.
SDI connections are used to enable blending with live data connections.
For more information, see Blend Data.
-
Update your HANA XS Password.
- From the side navigation, go to .
- Select the imported agent, and click
(Edit Agent
Registration).
- Under HANA XS Password, select
(Reset Password). Note the
new password.
- Select Save.
-
Open an Administrator prompt on the Window or Linux host where the
SAP Data ProvisioningAgent is installed, and run the following
commands:
- Set the environment variable.
On
Linux:
export DPA_INSTANCE=<DPAgent_root>
On
Windows:
set DPA_INSTANCE=<DPAgent_root>
- Start the Data Provisioning Agent.
On
Linux:
<DPAgent_root>/bin/agentcli.sh --configAgent
On
Windows:
<DPAgent_root>/bin/agentcli.bat --configAgent
You
must start the agent, if it has not been started
already: Select option 2. Start or Stop
Agent, and then option 1.
Start Agent.
Select
q. Quit to exit the
script.
This pattern of stopping and then
starting the agent is required whenever you make a
configuration change to the agent.
- Set the credentials for the HANA XS user.
On
Linux:
<DPAgent_root>/bin/agentcli.sh --setSecureProperty
On
Windows:
<DPAgent_root>/bin/agentcli.bat --setSecureProperty
-
Restart the agent.
-
Update the remote source.
- In SAP Analytics Cloud, return to the Data Source
Configuration area.
- Edit and use the respective credentials to log into each
remote source that uses the imported agent.
Results
Once complete, the import unit history appears in the
list of unit histories in the main
Import window. You can
open that unit to make changes to your previous selections and re-import the
unit.