Media Exchange (MX) Deployment Options

1) Media Exchange Basic Configuration – Minimal Ports

The following diagram illustrates a basic Media Exchange configuration with the addition of minimal ports:

Media Exchange Deployment 1

Configuration Overview: Install Signiant Manager where it is accessible to remote users; configure both Manager and Agents with default options.

Recommended for: Non-production testing or minimal effort setup.

Pros:

  • Easiest to configure.
  • Minimizes port usage.

2) Media Exchange Relayed Configuration

The following diagram illustrates a Media Exchange configuration that uses a relay:

Media Exchange Deployment 2

Configuration Overview: Install Signiant Manager and Relay Agent where both are accessible to remote users. Enable the relay agent for Media Exchange. Place the Media Exchange-enabled agent behind the firewall. Assign the user’s Media Exchange agent to the ‘Media Exchange Enabled Agent’. (Users are always assigned to their Media Exchange enabled-agent., even if they cannot see it in any way.)

Recommended for: Simple configuration where access to content is behind firewall and all users are remote.

Pros:

  • Minimizes inbound port use.
  • Can be used to obscure internal server names; user does not need to know or resolve the MX enabled agent.

3) Media Exchange Load Balanced

The following diagram illustrates basic Media Exchange configuration that uses relays with load-balanced MX servers:

Media Exchange Deployment 3

Configuration Overview: Install Signiant Manager and Relay Agent where both are accessible to remote users. Enable the relay agent for Media Exchange. Place the Media Exchange-enabled, load balanced group behind the firewall. Assign the user to the Media Exchange-enabled load balanced group.

Recommended for: Simple configurations where access to content is on shared storage behind firewall and all users are remote. Assume that each Media Exchange-enabled agent server can handle 10 concurrent downloads/uploads. Each Media Exchange-enabled relay agent can handle 20 relayed connections.

Pros:

  • Minimizes inbound port use.
  • Can be used to obscure internal server names; user does not need to know or resolve the Media Exchange-enabled agent.
  • Provides load balanced access to content store.

4) Media Exchange Fully Load Balanced

The following diagram illustrates a Media Exchange configuration that provides load-balanced relays and agents:

Media Exchange Deployment 4

Configuration Overview: Install Signiant Manager and Relay Agent where both are accessible to remote users. Enable the relay agent for Media Exchange. Place the Media Exchange-enabled, load balanced group behind the firewall. Assign the user to the Media Exchange-enabled load balanced group.

Recommended for: Simple configurations where access to content is on shared storage behind firewall and all users are remote. Each MX server can handle 10 concurrent downloads/uploads. Each relay agent can handle 20 relayed connections.

Pros:

  • Minimizes inbound port use.
  • Can be used to obscure internal server names; user does not need to know or resolve the MX server. Provides load balanced access to content store.

5) MX Relayed Configuration – Fully Load Balanced (with MX Web Server)

The following diagram illustrates a Media Exchange configuration that provides load-balanced relays and agents:

Media Exchange Deployment 5

Configuration Overview: Install Media Exchange Web Server and Relay Agents where all are accessible to remote users. Enable the relay agents for Media Exchange. Place the MX Manager and Media Exchange servers behind the firewall. Assign the users to the load balanced MX enabled agents.

Recommended for: More secure configurations where access to content is on shared storage behind firewall and all users are remote. Each MX server can handle 10 concurrent downloads/uploads. Each MX relay agent can handle 20 relayed connections.

Pros:

  • Minimizes inbound port use.
  • Can be used to obscure internal server names; user does not need to know or resolve the MX server.
  • Provides load balanced access to content store.