Installing the Sametime Media Manager's Conference Manager

Use IBM® Installation Manager to install an IBM Sametime® Media Manager's Conference Manager. Be sure to install the Sametime Video Manager prior to installing the Conference Manager. If your configuration includes the Sametime Video Manager Server, install the Sametime Video Manager Server prior to installing the Conference Manager.

Procedure

  1. On the computer where you will install the Conference Manager component, log on as root (Linux™) or as the system administrator (Windows™).
  2. Find the software packages you need to download.
  3. Download the packages.
  4. Extract all downloaded packages.
  5. Install IBM Installation Manager.
  6. Install IBM WebSphere Network Deployment.
  7. If Installation Manager is not running already, start it now:
    • Linux: Open a command window and change to the location where you installed Installation Manager. The default location is /opt/IBM/InstallationManager/eclipse.

      Start Installation Manager by running the following command: ./IBMIM

    • Windows: Click Start > All Programs > Installation Manager > Installation Manager.
  8. Set the repository location by completing the following steps:
    1. In the Installation Manager window, click File > Preferences.
    2. On the Preferences page, click Repositories.
    3. Add the repository for the Sametime Conference Manager installation package:

      All Media Manager components use the same repository.

      1. On the Repositories page, click Add Repository.
      2. On the Add Repository page, click Browse.
      3. On the Select Repository page, browse to the location where you stored the extracted files for Sametime Conference Manager, and open the IAV subdirectory.
      4. Click the repository.config file to select it, and then click Apply.
      5. Deselect any listed repositories that you will not use for installing the Sametime Conference Manager.
    4. Click OK.
  9. Back in the main Installation Manager window, click Install.
  10. Accept the terms in the license agreements, and click Next.
  11. Select a package group option and accept the installation directory. Then click Next.

    Select Create a new package group if you have not installed any other Sametime software on this computer.

    Leave Use the existing package group selected if you are installing several Sametime servers on the same computer.

  12. Select IBM Sametime Media Server 9.0.1 as the feature to install.
  13. Select Use Sametime System Console to install, and then click Next.
  14. Specify the location of the WebSphere Application Server and then click Validate.
  15. In the Common Configurations window, supply values for connecting to the Sametime System Console:
    • Host Name: Provide the fully qualified domain name in the Host Name field for the Sametime System Console.

      The host name was determined when you installed the Sametime System Console. The host name must be the actual host name and not a DNS alias.

    • Use SSL: Leave this option selected to run the server over a secure connection.
    • HTTPs Port: Leave 9443 as the default value.
    • User ID and Password: Provide the WebSphere Application Server User ID and password that you created when you installed the Sametime System Console.
  16. Provide the fully qualified host name for the computer you are currently using, which is the same name you used when you created the deployment plan for this installation.

    Do not use an IP address or short host name.

  17. Click Validate to log in to the Sametime System Console.
  18. When you are logged in, click Next.
  19. Select the Conference Manager deployment plan, and click Next.
  20. Review the deployment settings, then click Validate. When the button changes to Validated, click Next.
  21. Review the summary, then click Install to start the installation.
  22. When installation is complete, click Finish.
  23. Click Exit to close the Installation Manager.
  24. Start the Sametime Conference Manager by completing the following procedure: Starting and stopping servers running on WebSphere Application Server.