Repository import scripts

About import behavior

Imports scripts use an optional parameter that specifies the path where the exported resources are generated. If a directory is not specified, the import will be made from the path specified in the ImportDirectory section of the configRepository.properties file. Depending on the commands, a specific folder structure may be required in the <ImportDirectory> section for the files that are used by the import script.

If the configuration file is modified, the command tool must be stopped and restarted in order to take the changes into account in the configRepository.properties file.

Import scripts

Script Description
importDatasources

Imports the datasources from the specified directory.

If the directory is not specified, the Datasources are imported from the path specified in the [ImportDirectory] section of the configRepository.properties file. Datasources must be grouped in the

"datasource" predefined directory.

Parameter: [ImportDirectory]

importDictionaries

Imports the dictionaries from the specified directory.

If the directory is not specified, the dictionaries are imported from the path specified in the [ImportDirectory] section of the configRepository.properties file. Dictionaries must be grouped in the predefined directory "dictionary".

Parameter: [ImportDirectory]

importSystemDictionaries

Imports dictionaries for the specified [componentTypeName] from specified [ImportDirectory]

Possible values for componentTypeName: configRepository | aisadmin | reportServer | datastoreRuntime | datastoreClient | ruleserver

Parameters: <componentTypeName> [ImportDirectory]

importLibraries

Imports the libraries from the specified directory.

If the directory is not specified, the Libraries are imported from the path specified in the [ImportDirectory] section of the configRepository.properties file. Libraries must be grouped in the "datasource" predefined directory.

Parameter: [ImportDirectory]

importLicense

Imports a licence key in the Repository .

Parameter: <licence_key>

importRegistry

Imports the registry from the specified directory.

If the directory is not specified, the registry is imported from the path specified in the [ImportDirectory] section of the configRepository.properties file. The registry.xml file must be in the "registry" predefined directory.

Parameter: [ImportDirectory]

importReportTemplates

Imports the report templates from the specified directory.

If the directory is not specified, the report templates are imported from the path specified in the [ImportDirectory] section of the configRepository.properties file. Report templates must be grouped in the "report Templates" predefined directory.

Parameter: [ImportDirectory]

importServerConfiguration

Imports the server configuration from the specified directory.

If the directory is not specified, the server configuration is imported from the path specified in the [ImportDirectory] section of the configRepository.properties file. This command can also be used to update the configuration of the current application. If differences are detected, the version of the application is increased as well as the version of the items that have been discovered as modified. Configurations must be grouped in the

"importServerConfiguration" predefined directory.

Parameter: [ImportDirectory]

importQueries

Imports queries from the specified import file into the specified Datastore UI component.

Parameters:

  • -f <ImportFile> - name of the file to be imported from the location specified in the ImportQueriesDirectory parameter of the configuration.properties file.
  • -c <componentName>

At the end of the import, an execution report displays the:

  • Number of imported folders
  • Number of imported queries
  • Number of folders and queries that have not been imported because they already exist or because the user does not have the right to do so
  • List of the queries and folders that have not been imported and why they have not been imported.

Example :

importQueries -f queries.xml -c AISClient

Note:

If a query/folder name contains an ASCII character lower than code 32 or the ‘/’ character, it will not be imported

importPreferences

Imports the preferences file previously exported. The preferences file can contain preferences for more components.

For Datastore Client, the following settings can be imported as user preference:

  • selected language
  • quick filter panel width
  • history panel width
  • queries and histories preferences
    • column width
    • column visibility
    • text alignment
    • text color
    • background color

Parameter:

importFolder - folder where the preferences file is located. The system looks for a « preferences.xml » file in the specified folder and imports it.

Example:

importPreferences C:/export

importUIConfiguration

Imports the UI configuration from the specified directory.

If the directory is not specified, the UI configuration is imported from the path specified in the [ImportDirectory] section of the configRepository.properties file. Configuration must be grouped in the "importUIConfiguration" predefined directory. The file that contains the description must be called globalUIConfiguration.xml.

Parameter: [ImportDirectory]

Related Links