You can configure the Connector to automatically load and update its configuration. This is useful in the following scenarios:
- upgrading your instance of the Connector
- moving your installation to a new environment
- copying your installation to a new environment
To export your configuration from the Connector:
Each Connector configuration page corresponds to an XML configuration file. The table below indicates which Connector configuration page corresponds to a particular configuration file.
- To download all these configurations as a single ZIP file, click Admin Tools > Configuration in the Lionbridge Connector rail. For information on opening the Lionbridge Connector rail, see Configuring the Connector.
The Configuration page opens.
- At the bottom of the Configuration page, click Export All Configurations.
Alternatively, for pages marked below with an asterisk (*), you can download the individual configuration files from those pages. For detailed instructions, refer to the last column in the table.
|Configuration Page||Corresponding Configuration File||For Details, See…|
- configuration options *
- translation options *
|ctcconfig.xml||Configuring Connector Global Settings|
|Language Mapping page *||languagemapping.xml||Configuring Connector Languages|
|Component Mapping page *||fields4trans.xml||Configuring which Components and Properties to Send Out for Translation|
|LSP and Keys page *
Note: You cannot import license-key settings from 3.x versions of the Connector to 4.x versions, because they use different license-key formats.
|lspkeys.xml||Configuring Translation Providers and License Keys|
|Advanced Settings page *||advancedSettings.xml||Configuring Advanced Settings in the User Interface|
|Team Profiles page||teamprofiles.xml||Configuring Team Profiles|
|Queue Scheduler||queueschedules.xml||Scheduling Translation Jobs to Send Out Content from the Translation Queue|
|Custom Asset Handlers||assethandlers.xml||Creating a Custom Asset Handler|
To set up the Connector to automatically import configuration files from the Configuration page:
Click the Import Configuration button on the Configuration page.
Choose the xml file to import then click the Upload button.
After clicking the Upload button, you can see an Imported Successfully message. Now close the pop up window.
Note: The following procedure is not applicable for the AEM Cloud Connector.
To set up the Connector to automatically import configuration files from the default location:
- Place the files to import in the following location: AEM_QuickStart_Folder\CTC_Configs\Import. The Connector monitors this location and imports any new files.
To set up the Connector to automatically import configuration files from any location:
Create the CTC_INIT_HOME environment variable on the Adobe Experience Manager server.
In Windows, you create an environment variable by clicking the Environment Variables button in the Advanced tab of the System Properties dialog box, which you can open from the Control Panel.
In Linux, you can add the environment variable by adding the following export statement to one of the files described in the table below:
|~/.bash_profile||This file runs when the local user profile logs in to a terminal window. If you start Adobe Experience Manager by typing the start command, then you can use this file so that CTC_INIT_HOME is always available when you run Adobe Experience Manager.|
|/etc/environment||This file is the global UNIX configuration file. After adding the export statement above and rebooting the machine, CTC_INIT_HOME will be available everywhere.
Note: This file is intended specifically for system-wide environment variable settings. It is not a script file, and it consists of one assignment expression per line.
|startup script: crx-quickstart/bin/start||This file is the startup script of your Adobe Experience Manager instance. Adding the export statement to this file initializes the CTC_INIT_HOME variable locally, within the Adobe Experience Manager process.|
Set the value of this environment variable to a directory with read and write permissions that is accessible to the Adobe Experience Manager process or instance, for example:
Linux: export CTC_INIT_HOME=/var/adobe/ctcdata/init_config
Restart the Adobe Experience Manager server.
The Connector now monitors this directory and automatically loads any configuration files in this directory. It saves the configuration files to the following location on the Adobe Experience Manager server: /etc/ctctranslation.
To specify which configuration files to import:
- Copy the configuration files exported previously into the directory specified by the CTC_INIT_HOME environment variable.
The Connector automatically loads these configuration files and updates its configuration.