This guided activity takes you through the steps of creating a deployment plan, which collects information that pre-populates installation screens. The IBM
® Media Manager runs on Linux
™ and Microsoft
™ only. The media manager is comprised of three components: Proxy/Registrar, Conference Manager, and Packet Switcher. In an enterprise deployment, you should install these Media Manager components on separate machines for better performance.
Before you begin
The instructions below assume you have decided what type of deployment plan you are setting up for the Media Manager. A small deployment uses one machine and one deployment plan. An enterprise deployment typically distributes each Media Manager component on a separate machine and therefore uses multiple deployment plans. In addition, you can cluster the Proxy/Registrar and Conference Manager components, which requires a deployment plan for the component's primary node and another deployment plan for secondary nodes. Clustering is not available for the Packet Switcher; it is also not available for an "All Components" installation of the Media Manager, which includes the Packet Switcher.
- Small deployment prerequisite
You must have installed a Sametime Community server using a deployment plan.
- Enterprise deployment prerequisites
The SIP Proxy and Registrar requires that you have installed a Sametime Community server using a deployment plan.
The Conference Manager requires that you have installed a Sametime Community server and a SIP Proxy and Registrar using deployment plans.
The Packet Switcher requires that you have installed a Sametime Community server and a Conference Manager using deployment plans.
Create deployment plans and install each component in this order to meet prerequisites:
- SIP Proxy and Registrar
- Conference Manager
- Packet Switcher
About this task
Follow these steps to store a deployment plan on the Sametime
System Console to be used when you run the installation program for Sametime
Media Manager or one of its components. To install a cluster of servers, create one deployment plan for the primary node and one for all secondary nodes you plan to install.
- Plan a product installation.
In the Install Sametime Media Manager portlet, click Create a New Deployment Plan, and then click Next.
- Deployment Name.
Give the deployment plan a unique, recognizable name, which will be shown only in the Sametime System Console, and then click Next.
The name should include the installation and node type, such as stMedia_primary or stMediaProxReg_primary. You can include multibyte characters, symbols, and spaces in the name. The name can be up to 256 characters and is not case sensitive.
- Deployment Product Version Selection.
Select the product version you want to install, and then click Next.
- Media Manager Feature Installation.
Select which components to install, and then click Next
Click Install All Components
to install all media manager components on the same computer.
Select the component to install on the current computer.
- Install Proxy/Registrar
- Install Conference Manager
- Install Packet Switcher
The Packet Switcher can only be deployed with Conference Managers that have already been installed and registered with the Sametime
System Console. You can deploy multiple Packet Switchers for a single Conference Manager; the Packet Switchers cannot be clustered but the Conference Manager distributes the workload among them.
- Choose the configuration type.
Select Primary Node if this is the first server of its type or if you are installing a Packet Switcher. Select Secondary Node for additional Proxy/Registrar or Conference Manager servers. Then click Next.
The Cell option is reserved for special-use cases in which the server must be self-contained. If you select Cell, you must provide a host name, user ID, and password when prompted to do so.
- Node Federation at Install Time.
This panel appears if you selected Primary Node or Secondary Node. You can only federate one Primary Node for this type of server in the cell. Select the Sametime System Console cell that will manage this server and then click Next.
Attention: Each Deployment Manager (including the Sametime System Console when it is used as a Deployment Manager) can support one cluster of each Sametime product. For example, a single Deployment Manager can support a Sametime Proxy server cluster, a Media Manager cluster, and a Meeting server cluster. To create additional clusters for a particular product, install the first server using Cell as the configuration type, which designates it as the Deployment Manager and the primary node for the cluster.
- WebSphere® Profile Settings.
- Type the fully qualified host name of the server where you will be installing the media manager component.
- Enter a user name that does not contain any spaces to be used as the WebSphere Application Server administrator on the Sametime server. Supply a password, and then click Next.
If you must create a user name that contains a space, you may notice that the system console portlet does not appear in the WebSphere Application Server Integrated Solutions Console for the first time. This can be resolved by restarting the system console.
Important: This must be a unique user ID that does not exist in the LDAP directory.
- Connect to Community Server.
Select the deployment plan that represents the Community Server to which this Media Manager component (or components) connect, and then click Next.
For a Conference Manager deployment plan, also select the existing Proxy/Registrar deployment plan. For a Packet Switcher deployment plan, also select the existing Conference Manager deployment plan.
- Deployment Summary.
Review the summary screen, and then click Finish.
The deployment plan is ready to be used for the server installation. If you need to make any changes, click Modify an Existing Deployment Plan and update the plan. All changes must be made prior to running installation.
Repeat this guided activity for each media manager component you plan to install on a separate computer.
What to do next
Installing a media manager on Linux or Windows
Parent topic: Preparing to install a Sametime Media Manager on Linux or Windows