Media Server 25.3
Media Server Help

# Configure the Upstream Media Server

This section describes how to configure Media Server to send records to another Media Server.

To send records to another Media Server

1. Create a new configuration to send to Media Server with the `process` action, or open an existing configuration that you want to modify.

2. In the `[Session]` section, add a new task by setting the `EngineN` parameter. You can give the task any name, for example:

       [Session]
       Engine0=Ingest
       Engine1=...
       Engine2=RemoteAnalysis

3. Create a new configuration section by typing the task name inside square brackets. Then, set the following parameters:

   `Type` | The analysis engine to use. Set this parameter to `RemoteAnalysis`.
   `Host` | The host name or IP address of the Media Server to send records to.
   `Port` | The ACI port of the Media Server to send records to.
   `ConfigName` | The name of the configuration file that the downstream Media Server must use to ingest and analyze the records (this file must be present in the folder specified by the `ConfigDirectory` configuration parameter on the downstream Media Server).
   `Input` | The name of the track to send to the remote Media Server for remote analysis. You can provide an alias to simplify the track name when you configure the other Media Server. To do this specify the track name as `Alias:TaskName.TrackName`, where: `Alias` is the track name to present to the remote Media Server. `TaskName` is the name of the task that produced the track. `TrackName` is the name of the track. NOTE: You cannot send audio tracks to a downstream Media Server.
   `Output` | A comma-separated list of tracks, generated by the remote Media Server, to output from the remote analysis task. These tracks are then available for further processing on this Media Server. Specify the track names as `Alias:TaskName.TrackName`, where: `Alias` is the track name to present to subsequent tasks on this Media Server. `TaskName` is the name of the task, on the remote Media Server, that produced the track. `TrackName` is the name of the track, on the remote Media Server.

   For example:

       [RemoteAnalysis]
       Type=RemoteAnalysis
       Host=gpu-mediaserver
       Port=14000
       ConfigName=RemoteFaceRecognition
       Input=DetectedFaces:Crop.Output
       // where "Crop" is a transform task to crop images of
       // detected faces from the face detection ResultWithSource track
       Output=RecognizedFaces:FaceRecognition.Result
       // makes results available to subsequent tasks
       // as RemoteAnalysis.RecognizedFaces

4. Save and close the configuration file. OpenText recommends that you save your configuration files in the location specified by the `ConfigDirectory` parameter.

Copyright 2025 Open Text
Version 25.3 | Last updated July 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery Media Server 25.3

Topic Title: Configure the Upstream Media Server