Importing Content from a .tgz File

Create an import to move content into your system from a .tgz file.

Prerequisites

If you're importing 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 Start of the navigation path Next navigation step System Administration End of the navigation path .

Procedure

Select Deployment Import.
In the Import window, choose 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. If you want to include the object's sharing settings in the import, you can import it again with the Update existing object option selected.
- For objects that already exist in your system, your selections in the Options window determine whether to overwrite the object and update its data and sharing settings. 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 are also updated to match the settings of the imported object.
  
  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. If the object selected is an analytic application, in addition to the analytic application itself, its bookmarks are overwritten as well. 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.
Choose OK to set the options.
Choose 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 Connection Schedule Status 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 Blending Data.
1. Update your HANA XS Password.
  1. Go to (Main Menu) System Administration Datasource Configuration.
  2. Select the imported agent, and click (Edit Agent Registration).
  3. Under HANA XS Password, select (Reset Password). Note the new password.
  4. Select Save.
2. 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
3. Restart the agent.
4. Update the remote source.
  1. In SAP Analytics Cloud, return to the Datasource Configuration area.
  2. 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.