Setup guide

Migrating a Media Services Engine
29
Port Usage for the Media Services Engine
To enable the Media Services Engine to communicate with the editors and the provider
clients, the network must allow TCP traffic on the following ports:
• Listen for editor clients (SOAP): 8080 TCP
• Listen; RMI protocol for providers and Status/Admin tool: 1099 TCP
• If 1099 is not available: 42000 - 42060 TCP
Determining Whether to Migrate the Media Services Engine Database
The only way to move your old Media Services Provider profiles to a new server is to
migrate the old database. This is an advanced procedure that requires knowledge of SQL
databases. In most cases it is easier to write down or take screen captures of the settings for
the profiles you are using and then recreate them when after you install the Media Services
Engine on the new AS3000 server. You only need to migrate the database if you have a large
number of profiles that you do not want to recreate.
For details on migrating a Media Services database, see “Migrating a Media Services
Database” on page 40.
Copying Profiles
If you plan to either write down or take screen captures of your existing profiles, you may
find it useful to copy representative profiles. For example, you may have a number of
profiles that perform transcodes at different resolutions but all of the profiles use the same
target workspace.
To determine which profiles to copy:
1. Examine the profiles in each profile set and determine which ones should be copied.
The following illustration shows a Media Services Engine with several types of profiles.