inRiver Translation Connector
  • Introduction
  • Architecture
  • Workflow
  • Install - inRiver PMC
  • PMC install - inRiver Data Model Configuration
  • Updating Connector - inRiver iPMC
  • Install - inRiver 6.3
  • On-premise (6.3) Install - inRiver Data Model Configuration
  • Translation Configuration
    • Sample Translation Configuration
  • Language Configuration
  • Using the Lionbridge Connector (Manual Workflow)
    • Entity Translation Status
    • Translation Job Status & Actions
    • Linked Entities Translation Status
    • Cancelling Translation Jobs
    • Deleting Translation Jobs
    • Translation of CVL values
    • Translation of Specifications
    • Sending Entity Images for Reference.
    • Sending non-LocaleStrings for Reference
  • Using the Lionbridge Connector (Automatic workflow)
  • Appendix 1: Lionbridge Language List
  • Appendix 2: Troubleshooting
  • Upgrade - 6.3 > PMC
  • Upgrade - 6.3
  • Upgrade - 3.2.2 -> 3.3
    • inRiver 6.3
    • inRiver PMC
  • Language Configuration - Upgrading
  • Logging
  • Criteria Configuration
    • Criterias
  • TLS 1.2
  • Release Notes
Powered by GitBook
On this page
  • Log4Net
  • iPMC Control Center logging
  • Serilog with Seq

Logging

PreviousLanguage Configuration - UpgradingNextCriteria Configuration

Last updated 2 years ago

Log4Net

Used to log everything for the inRiver 6.3 connector

iPMC Control Center logging

The Connectors extensions log messages will appear with all other inriver in the Control Center.

Serilog with Seq

An optional way of logging to a remote Seq server endpoint.

Functional support in the following minimum versions of the connector: inRiver PMC Extension: 3.4 inRiver 6.3 Connector: 3.4.1

How to enable

You will need a logging server URL and a valid Seq logging api key. The Connector Support team can provide these details during On Boarding, or contact Lionbridge (connectors@lionbridge.com)

inRiver PMC

Navigate to the inRiver control center, and go to Server Settings.

Add the following server settings:

  • LOG_CUSTOMER_KEY

  • LOG_SERVER_URL

inRiver 6.3

Option 1: Using the inRiver Model Tool

  1. Open the inRiver Model Tool

  2. Click the Server Settings tab

  3. Add the following server settings

    • LOG_CUSTOMER_KEY

    • LOG_SERVER_URL

Option 2: Using the inRiver web GUI

  1. Navigate to the inRiver web GUI

  2. Click the "System" web app

  3. Click "Settings" in the navigation bar to the left

  4. Add the following server settings

    • LOG_CUSTOMER_KEY

    • LOG_SERVER_URL

logging