Exporting Objects to the HANA Repository

While HANA tables are generated directly to the catalog, analytic, attribute, and calculation views are exported to the HANA repository from where they will be deployed. PowerDesigner provides a wizard to allow you to export your objects to the HANA repository and catalog as appropriate in a single action.

1. Select  Database  Apply Model Changes to HANA Repository  to open the wizard, and specify your deployment model:
   • Repository [default] - Generate directly to the HANA repository.
   • HDI - Generate files for loading to HANA. You must specify:
     • Generation Path - Specify the path to generate files.
     • HDI Namespace - Specify the starting namespace for all objects.
2. Click Next.

   If you selected to check the model, the wizard checks your model for consistency and displays any errors which may compromise the generation.

3. [repository environments] Enter your HANA repository connection parameters and then click Next to connect:

   Parameter	Description
   Connection Name	Select an existing connection from the list or use the tools to the right of the Connection field to create a new connection profile, review the properties of the existing profile, or delete it. HANA connection profiles are stored in the registry.
   Host name	Specifies the network name of the HANA appliance.
   Instance number	Specifies the HANA instance number.
   Mode	If your HANA system is installed in multiple-container mode, you must specify the container to connect to: Single container - [default] Single tenancy HANA system. Sets the port number to 3<nn>15 (where <nn> equals the instance number). Multiple containers - Multitenancy HANA system. You can connect to: System database container - sets the port number to 3<nn>13 Tenant database container - Enter the Name of your container. Sets the port number to 3<nn><xx>, where <xx> is a number greater than 40, allocated to your database by the system.
   User name/ password	Specifies the credentials to connect with. Note The account with which you connect must have at least the CONTENT_ADMIN, MODELING, and PUBLIC roles.

4. Select HANA packages in your model in the left pane to make their contents available to export. Select the analytic, attribute, and calculation views to export in the right pane, and then click Next.
   When you select an analytic view (fact) to export, its supporting attribute views (dimensions) are automatically selected too.

   Note If you have previously imported objects from HANA, the archive model helps to determine model changes since that point (see Archive PDMs).
5. On the Catalog Objects tab, PowerDesigner automatically selects any catalog tables and views required by the selected analytic, attribute, and calculation views for export. Select additional objects to export from the lists, and then click Next.
   Note You can select additional schemas from the list to make their objects available for selection.
6. Review the objects that will be exported and then click Finish:
   • Repository environments - PowerDesigner generates the objects to the HANA repository and catalog as appropriate.

     Note If PowerDesigner detects conflicts between changes made in the model and changes to the same objects on the server, then a merge dialog (see Core Features Guide > Modeling with PowerDesigner > Comparing and Merging Models) will open to allow you to select, for each conflict, which of the conflicting changes will prevail. The resolutions that you select will first be applied to the model, and then your changes will be exported to the server.

   • HDI environments - PowerDesigner generates the appropriate files for loading and activation to the specified path.