Install - inRiver 6.3

Prerequisites

There is a number of things that must be in place before you can start the configuration of the translation connector. The installation and set-up should always be carried out by a competent Solution Integrator or suitably qualified person.
    An agreement and a Freeway account must be set up, and you need the log in credentials.
    You must have a list of possible source and target languages verified.
    The translation process and decided upon the services.
    Get a list of mappings between the PIM languages and the Translation languages.
Technical
    A InRiver PIM 6.3 or later
    Ports open for https traffic

Step 1. Installation

    Stop the InRiver Integration (inRiver Connect 6) service
    Move the References folder provided to the inRiver AB/inRiver Connect directory.
    Copy the provided Lionbridge Connector file from the OutboundConnectors folder to the OutboundConnectors directory in the inRiver Connect installation directory.
    Open inRiver.Integration.exe.config with a text editor in the inRiver Connect folder and paste the following anywhere inside the section system.serviceModel:
    1
    <bindings>
    2
    <basicHttpBinding>
    3
    <binding name="logonEndpoint">
    4
    <security mode="Transport" />
    5
    </binding>
    6
    <binding name="serviceEndpoint"
    7
    maxReceivedMessageSize="20000000"
    8
    maxBufferSize="20000000"
    9
    maxBufferPoolSize="20000000">
    10
    <security mode="Transport" />
    11
    </binding>
    12
    </basicHttpBinding>
    13
    </bindings>
    14
    <client>
    15
    <endpoint address="https://fwapi.demo.lionbridge.com/obvibundles/freewayauth.asmx" binding="basicHttpBinding" bindingConfiguration="logonEndpoint" contract="FreewayAuth.FreewayAuthSoap" name="FreewayAuthSoap" />
    16
    <endpoint address="https://fwapi.demo.lionbridge.com/obvibundles/service.asmx" binding="basicHttpBinding" bindingConfiguration="serviceEndpoint" contract="FreewayService.ServiceSoap" name="ServiceSoap" />
    17
    </client>
    Copied!
Endpoints - the endpoints detailed above are for the demo environment during the testing and confirguration stage. The Lionbridge Connector team will supply you with updated Endpoint urls for the Live Production environment during deployment process.
In the same file, a hint to the inRiver Integration service where our references can be found must be added.
Look for the assemblyBinding section inside the runtime section, inside the configuration section. Inside the assemblyBinding section there should be an already existing probing section, with a privatePath attribute.
In a default inRiver installation the value for the privatePath attribute should be: InboundConnectors;OutboundConnectors
We need to add References to this attribute, so it should end up looking like this: InboundConnectors;OutboundConnectors;References
Now the inRiver Integration service will be able to find the additional dll files needed by the Lionbridge Connector.
You can now save the file, and restart the inRiver Integration service.

Step 2. Setup the Connector

    Go to the Publish view
    In the menu, select "Add New Connector"
    Name it TranslationConnector
    Select the Lionbrigde.Translation.Connector.Outbound.OutboundConnector
    After creating the connector, go to the connnector settings and configure the settings
    Example settings
Setting
Value
Note
jobUpdateIntervalMinutes
30
Minutes - The interval for updating translation status
jobManagerUpdateIntervalMinutes
30
Minutes - The interval for look for automated translations in PIM
jobManagerUser
pimuser1
Username - User that created the query
jobManagerQuery
Products
Query name - The name of the query that selects entities that need translation
sendOnlyTranslatableData
True
Boolean (True/False) - Whether or not to send more than just the translatable data on an entity (Sends all field data on the entity)
translateLocaleCVL
False
Boolean (True/False) - Whether or not to send LocaleString CVL values for translation, that are in use by the entities that are being translated.
lionbridgeUsername
XXX
Username - Freeway account username
lionbridgePassword
XXX
Password - Freeway account password
translationFileEntityLimit
1000
Integer - Max number of entities that can be added to each translation file sent to Lionbridge Freway before the file is split into multiple files
translationConfiguration
XML file content - Configuration XML file content
criteriaConfiguration
XML file content - Criteria system XML file content
ignoreDateModifiedForLocaleStrings
False
Boolean (True/False) - disable/enable a check whether the source language have a later modified date then the target language. (Default is False)

Automated Translation System

If you want to use the automated translation system, then you need to create a query that the connector can use to find the Entities that should be translated. If you don't want to use the automated translation system, you can leave the jobManagerUser and jobManagerQuery setting empty, and ignore the rest of this section.
    The default behavior is to create a Query called Entities that need translation.
    Save the query in a Personal Workspace.
    Update the connector setting jobManagerUser to match the name of the user that created the query.
    Update the connector setting jobManagerQuery to match the name of the query.
    Start the Connector

CVL Translation

CVL is a key-value container related to a field on a Entity. One CVL value is normally used by multiple Entities. CVL values in use by entities sent for translation are also sent to be translated, if the translateLocaleCVL setting specifies it.
A key thing to know is that CVL values with a value present for a specific language is considered to be permanently translated, and you will need to clear the existing value if you want a language's value to be translated again.

Step 3. Setting up the translation configuration file

Some settings are multi-dimensional, therefor we have created a XML configuration file for some of the connector settings.
Look at the following article for information on how to set up this configuration. Configuring the translation configuration

Step 4. Configure the inRiver Data Model

Details on how to configure the inRiver data model can be found in the following article. Install - inRiver Data Model

Step 5. Verification

Instructions on how to verify the configuration is correct can be achieved by creating a test translation, more details in the following article. Testing the Lionbridge Translator

Log

The Translation Connector logs all actions in the C:\inRiver\inRiver Connect\Log folder.
    After installation check the log file and make sure there was no errors.
    Check the log if you for example get a Imported with errors, status.
Last modified 1yr ago