Repository export scripts

Export behavior

The default export folder is defined in the ExportDirectory path specified in the configRepository.properties. The user can give a different path by setting the optional parameter in each command.

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.

The script export commands refer to the current application.

Export scripts

Script Description
exportComponent

Exports the component information from the registry into the specified export directory.

If the directory is not specified, it exports the component information into the path specified in the ExportDirectory section of the configRepository.properties file.

In the export directory, a new registry folder is created. The exported parameters are moved to registry.xml file created in the registry folder.

Parameters:

  • <componentName>
  • [ExportDirectory]

Example: exportComponent Designer

Exports the registry configuration of the Designer component into the ExportDirectory path.

exportDatasources

Exports the datasources from the current application into the specified directory.

If the directory is not specified, the Datasources are exported into the path specified in the ExportDirectory section of the configRepository.properties file. A new folder called "datasources" is created in the export directory.

Parameter: [ExportDirectory]

Example: exportDatasources C:/AI Suite/deploy

exportDictionaries

Exports dictionaries from the current application into the specified directory.

If the directory is not specified, the dictionaries are exported into the path specified in the ExportDirectory section of the configRepository.properties file. A new folder called "dictionary" is created in the export directory.

Parameter: [ExportDirectory]

Example: exportDictionaries C:/AI Suite/deploy

exportLibraries

Exports the libraries from the current application into the specified directory.

If the directory is not specified, the Libraries are exported into the path specified in the ExportDirectory section of the configRepository.properties file. A new folder called "libraries" is created in the export directory.

Parameter: [ExportDirectory]

Example: exportLibraries C:/AI Suite/deploy

exportSystemDictionaries

Exports the system dictionaries for the specified [componentTypeName] to the specified [ExportDirectory]

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

Parameters: <componentTypeName> [ExportDirectory]

Example: exportSystemDictionaries -c interplay C:/InterPlay/deploy

exportPassport

Exports the PassPort parameters from the registry into the specified export directory.

Parameters:

  • <componentName>
  • [ExportDirectory]

If the directory is not specified, the component information is exported into the path specified in the ExportDirectory section of the configRepository.properties file.

In the export directory, a new registry folder is created. The exported parameters are moved to registry.xml file created in the registry folder.

Example: exportPassport Designer

Exports the registry configuration of the Designer component into the ExportDirectory path.

exportQueries

Exports the selected folders and queries into an XML format file for the Datastore UI component specified.

If the query list is not specified, all the queries are exported.

Parameters:

  • [QueriesList] - list of full paths of the folders to be exported. Paths must be separated by commas.
  • -f <ExportFile> - name of the file that contains the exported query.
  • -c <componentName>

The generated file is created in the location set in the ExportQueriesDirectory parameter in the configuration.properties file if the user does not specify another absolute path for the export file in the command line.

Example:

exportQueries "f1/f11/QueryF11, f2, QueryRoot1" -f C:/export/export.xml -c ComponentName

Exports the queries QueryF11 that is found in the path ./f1/f11, all the queries in the folder F2 and the query named QueryRoot1 that is placed in the root folder.

exportPreferences

Exports the preferences in a file. The preferences file can contain preferences for more components. For Datastore Client, the following settings can be exported 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

Parameters:

  • -u <username> - if specified, the system exports all preferences for the specified user
  • -c <componentName> - if specified, the system exports all preferences for the specified component and for all users
  • exportFolder - the folder where the preferences are exported. A preferences.xml file is exported.

Example:

  • exportPreferences C:/export
  • Exports all user preferences for all components.
  • exportPreferences -u user1 C:/export
  • Exports all preferences of the user1 for all components
  • exportPreferences -u user1 -c DatastoreClient C:/export
  • Exports all preferences for user1 and for « DatastoreClient » component
exportRegistry

Exports the registry into the specified directory.

If the directory is not specified, the registry is exported into the path specified in the ExportDirectory section of the configRepository.properties file. A new folder called "registry" is created in the export directory.

You can use the exportRegistry command to backup your registry before running unregister in Administration.

Parameter: [ExportDirectory]

Example:

exportRegistry C:/Interplay/deploy

exportRegistry C:/Datastore/deploy

exportRegistry C:/AccountingIntegrator/deploy

All components are exported.

exportReportTemplates

Exports the report templates from the current application into the specified directory.

If the directory is not specified, the report templates are exported into the path specified in the ExportDirectory section of the configRepository.properties file. A new folder called "reportTemplates" is created in the export directory.

Parameter: [ExportDirectory]

Example:

exportReportTemplates C:/Interplay /deploy

exportReportTemplates C:/Datastore/deploy

exportReportTemplates C:/AccountingIntegrator/deploy

exportServerConfiguration

Exports the server configuration from the current application into the specified directory.

If the directory is not specified, the server configuration is exported into the path specified in the ExportDirectory section of the configRepository.properties file. A new folder called "serverConfiguration" is created in the export directory.

Parameter: [ExportDirectory]

Example: exportServerConfiguration C:/Interplay/deploy or exportServerConfiguration C:/Datastore/deploy

exportServerConfiguration C:/AccountingIntegrator/deploy

The server configuration is exported into the path C:/Interplay/deploy/serverConfiguration for InterPlay, or C:/Datastore/deploy/serverConfiguration for Datastore

C:/AccountingIntegrator/deploy/serverConfiguration for AccountingIntegrator

exportUIConfiguration

Exports the UI configuration into the specified directory.

The editors and the editor conditions that are automatically generated, are not exported.

If the directory is not specified, the UI configuration is exported into the path specified in the ExportDirectory section of the configRepository.properties file. A new folder called UIConfiguration is created in the export directory.

Parameter: [ExportDirectory]

Example:

exportUIConfiguration C:/Interplay/deploy

exportUIConfiguration C:/Datastore/deploy

exportUIConfiguration C:/AccountingIntegrator/deploy

Related Links