GlobalLink Connector

Hint: The GlobalLinkConnectorV2, introduced in version 7.2.1 for brXM 16, integrates with TransPerfect's REST APIs.

Warning: The GlobalLinkConnector is deprecated as of version 6.0.0 for brXM 15.

The GlobalLinkConnector is deprecated because it uses an outdated Java API to connect to the GlobalLink Project Director API. For more information, see the GlobalLink Connect API Java repository.

This Java API requires an implementation of javax.xml.ws.spi.Provider in the JVM. Java 11 and later do not include Java EE, so this implementation is not available by default.

You can continue to use the connector, but you must provide the required implementation. One solution is to add the following Maven dependency to your CMS project. Be aware that this dependency will introduce several transitive dependencies.

<dependency>
  <groupId>com.sun.xml.ws</groupId>
  <artifactId>rt</artifactId>
  <version>2.3.5</version>
  <scope>runtime</scope>
</dependency>

Connector Repository Configuration

After installing the GlobalLink connector, the configuration is stored at:

/hippo:configuration/hippo:modules/translation-services-daemon/hippo:moduleconfig/translationsaddon:connector-globallink
  className=com.bloomreach.cms.translations.connector.globallink.GlobalLinkTranslationConnectorV2

For versions prior to 7.2.1, use the class com.bloomreach.cms.translations.connector.globallink.GlobalLinkTranslationConnector.

Obtain configuration values from your GlobalLink / TransPerfect account. Contact TransPerfect to request an account if you do not have one.

All configuration properties are set on the translationsaddon:connector node.

The following table describes each property. Review the description column for required fields and additional information.

String property	Default value	Description
globallink.externalServiceUrl		URL in the format `https://gl-pilot1.transperfect.com/PD`
globallink.username		Username for authentication, sent in the request body
globallink.password		Password for authentication, sent in the request body
globallink.userAgent	Bloomreach V2	Used for technical tracking
globallink.project		Used if no project is selected during submission creation
globallink.submissionPrefix		Used if no submission name is provided by the editor
globallink.fileFormat	Default_Bloomreach_XML	Used if no file format is selected during submission creation
globallink.maxWaitDays	5	Maximum number of days to wait for a translation
globallink.token		Required since 7.2.1. Base64-encoded basic token, passed in the Authorization header
globallink.accessTokenValidity	20	Required since 7.2.1. Set a higher value only if your TransPerfect account uses a custom default
globallink.grantType	password	Required since 7.2.1
globallink.localesMap	`{"en":"en-US", "de":"de-DE", "nl":"nl-NL", "fr":"fr-FR", "en_GB":"en-GB"}`	Required since 7.2.1. Keys are Bloomreach locales; values are the corresponding locales in your TransPerfect account

Info: The properties globallink.username, globallink.password, globallink.token, globallink.accessTokenValidity, and globallink.grantType are required for authentication. Refer to the TransPerfect API documentation for details.

Enable the Translation Results Processing Scheduler Job

To ensure translation results are imported into the repository, enable the scheduler job trigger at:

/hippo:configuration/hippo:modules/scheduler/hippo:moduleconfig/translationsaddon/TranslationResultsProcessor/hipposched:triggers/every-minute

Set the hipposched:enabled property to true and save your changes.

TransPerfect recommends polling no more frequently than once per hour. For the GlobalLink connector, configure the trigger to run three minutes past the hour (for example, 10:03, 11:03, 12:03). Consult your TransPerfect representative for optimal polling intervals.

You can modify the hipposched:cronExpression property to control how often the job checks for translation results on the remote server.