Guided Activity: Install Sametime Meeting Server

In the Install Sametime Meeting Server guided activity, click Create a New Deployment Plan, and then click Next.

Type a name for the deployment plan, and then click Next. The name should be unique and descriptive. It is helpful to include the product and node type, such as stMeeting_primary. The name can be up to 256 characters in length, is not case sensitive, and can include special characters as well as spaces.

Select the product version you want to install, and then click Next.

Select one or more roles for this Meeting Server to perform, and then click Next:

• Configure Base Meeting Server

  A Base Meeting Server hosts online meetings. If you plan to cluster this Meeting Server, select only this role. The Base Meeting Server cannot be clustered if other Meeting Server roles are installed on the same computer.

• Configure Meeting Document Converter

  A Meeting Document Converter transforms files (stored in the Meeting Room Library) for optimal display. Typically, Meeting Servers that run on Microsoft™ Windows™ do not require conversion services because documents and presentations display clearly without any intervention. However, consider using a separate server to offload conversion tasks from the Base Meeting Server. Be sure to use the default path for the document conversion directory. This role cannot be clustered using WebSphere Network Deployment, but it can be clustered by deploying a load balancer in front of two or Document Converter servers.

• Configure Meeting Recording Capturer

  A Meeting Recording Capturer hosts the real-time recording feature for online meetings. If you want to enable recorded meetings, then at least one Meeting Server must be configured with this role. This role cannot be clustered using WebSphere Network Deployment, but it can be clustered by deploying a load balancer in front of two or Recording Capturer servers.

• Configure Meeting Recording Renderer

  A Meeting Recording Renderer opens files stored by the Capture Server, transforms them into movie files, and stores the files so that users can download and view them. This role cannot be clustered using WebSphere Network Deployment, but it can be clustered by deploying a load balancer in front of two or Recording Renderer servers.

Select a configuration profile for this installation, and then click Next:

• Select Primary Node to install the first Sametime Meeting Server.

  Only a server that includes the Base Meeting Server role can be installed as a primary node.

• Select Secondary Node to install an additional Sametime Meeting Server so that it can be clustered with a primary node or a cell.

• Select Cell to install a separate deployment manager with a federated primary node on the same computer.

  Only a server that includes the Base Meeting Server role can be installed as a cell.

If you are installing a cell profile, skip this step.

Select the Sametime System Console (or other deployment manager) that will manage this primary node or secondary node, and then click Next to federate the new node to the deployment manager.

Provide the profile settings and then click Next:

If you are installing a secondary node, skip this step.

Select the Sametime Meeting Server database that you created, and then click Next.

If you are installing a primary node or a secondary node, skip this step.

Select the LDAP directory for the Sametime deployment, and then click Next.

Fill in configuration information for each of the Meeting Server roles that you selected, and click Next.

• Base Meeting Server
  • URL for remote capture server

    Provide the URL of a Meeting Server that is configured with the Recording Capturer role. If you deploy multiple Recording Capturer servers, this URL points to the load balancer that fronts them. Remember that the Base Meeting Server includes the Meeting Capturer server; therefore, if you are deploying a Meeting Server with the Base Meeting Server role, you must complete this field. If you are not installing any Meeting Servers with the Recording Capturer role, leave this field blank.

• Document Conversion Server
  Attention: If you selected both the "Base Meeting Server" and the "Meeting Document Converter" configuration roles for this server, then leave both the Document Converter Server URL and the Meeting Server URL fields blank. If you select only the "Meeting Document Converter" configuration role, set the fields as follows:
  • Document Converter Server URL

    Provide the URL of a Meeting Server that is configured with the Document Converter Server role.

  • Meeting Server URL

    Provide the URL a Meeting Server that is configured with the Base Meeting Server role. If the Document Converter Server is also being configured with the Base Meeting Server role, use the same URL that you provided in the Meeting Server URL field. If you deploy multiple Base Meeting Servers, this URL points to the load balancer that fronts them.

• Capture Server

  All of these fields are required unless marked as optional.

  • Capture Server URL

    Provide the URL of a Meeting Server that is configured with the Capture Server role and will record online meetings.

  • Maximum recording duration in minutes

    Specify the maximum allowed length of a recording, in minutes.

  • URL of the Meeting Server that is configured with the Base Meeting Server role

    Provide the URL a Meeting Server that is configured with the Base Meeting Server role. If the Capture Server is also being configured with the Base Meeting Server role, use the same URL that you provided in the Meeting Server URL field. If you deploy multiple Base Meeting Servers, this URL points to the load balancer that fronts them.

  • Directory where Capture files will be stored

    Provide the path to the location where you will store Capture files, which contain recorded meetings in their raw format.

    Attention: This location must be a file system that is shared by all Capture Servers and Render Servers in the deployment. This directory must exist on the server prior to installation.
  • User ID for Capture Server to record meetings
    Accept the default user ID, or create a new one; this ID is used only for recording meetings.

    Important: Do not use an existing user from the LDAP directory, and do not use this server's WebSphere administrator account. Using the WebSphere administrator account here will prevent the server from installing properly.
  • Password for Capture Server

    Create a password for the Capture Server user ID.

  • Hostname for the local audio capture application. This host name must be resolvable and routable from the SIP Proxy/Registrar.

    This is typically the same host name as the Capture Server that you are deploying; it uniquely identifies the local Capture Server that is recording meetings. Specify the fully qualified domain name for the server.

  • Port on which the local audio recorder application listens for SIP invitations

    This is the port that the Capture Server is listening on for communications from the SIP Proxy/Registrar. Typically this is port 5060 (unsecured communications) or 5061 (encrypted communications).

  • Audio Recorder IP with outbound connectivity to TURN/MCU

    Provide the IP address that is configured for outbound access to the Video MCU. Be sure to enter a numerical IP address; a host name will not work.

  • SIP Proxy/Registrar host

    Provide the fully qualified host name of the preferred SIP Proxy/Registrar.

  • SIP Proxy/Registrar port

    Provide the port number of the preferred SIP Proxy/Registrar.

  • SIP Proxy/Registrar transport

    Select the preferred transport protocol.

  • TURN host

    Optional. Provide the fully qualified host name of the TURN Server.

  • TURN transport
    Optional. Select the preferred transport protocol, and then do the following:

    • If you selected TLS, click TURN uses TLS.
    • If you selected TCP or UDP, provide the TURN Server's port number.
• Render Server
  • Directory where Render files will be stored

    Provide the fully qualified path to the location where the Render Server will store movie files. If you install the Capture and Render servers on the same computer, use the same path for both servers; for example, C:\CaptureRenderFiles. If you install the Capture and Render servers on separate computers, set up a shared network drive that most computers can access and specify that path here.

  • Horizontal resolution in output movie files

    Specify the width, in pixels, of the displayed recording. The most common display resolution uses 720 pixels for the width.

  • Vertical resolution in output movie files

    Specify the height, in pixels, of the displayed recording. The most common display resolution uses 1028 pixels for the height.

  • Number of days that recordings are valid for download

    Specify how long recorded meetings should remain available for users to download.

  • Number of days until expired recordings are deleted

    Specify how long expired recordings should be saved; when the time expires, the recordings will be deleted.

  • Number of simultaneous renders allowed per processor core

    Specify the number of renders that will be allowed to run at the same time on each processor core; typically this is limited to 2 renders on each processor core.

Review the summary screen, and then click Finish.

The deployment plan is ready to be used for the server installation.