The GlobalLink Connector

The GlobalLinkConnector is deprecated because it's using an outdated Java API to connect to GlobalLink Project Director's API. See at https://github.com/translations-com/globallink-connect-api-java.

Moreover, this Java API depends on an implementation of 'javax.xml.ws.spi.Provider' being present in the JVM, which is no longer the case on Java 11, since Java EE is absent.

Projects can still use the connector but will have to provide such implementation. A known solution is to add this Maven dependency to the CMS, but note that this pulls in a lot of other dependencies.

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

Connector repository configuration

Having installed the GlobalLink connector, it resides here in the repository:

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

Configuration settings are to be taken from your  GlobalLink / Translations.com account. Apply for one if you don't have one yet.

All configuration at the translationsaddon:connector node:

Turn on translation results processing scheduler job

As also mentioned at the Configuration page, be sure have translation results pulled into the repository, by enabling the trigger at

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

Set the property hipposched:enabled to true (checked) and save the changes.

You can also change the value of hipposched:cronExpression to adjust the time interval this job runs to check translation results on remote server.