Installing the deployment manager for a Sametime Gateway cluster on IBM i

Install the deployment manager for an IBM® Sametime® Gateway cluster on IBM i.

About this task

Use IBM Installation Manager to install IBM WebSphere® Network Deployment on the computer before installing Sametime Gateway.

Procedure

  1. On the computer where you will install Sametime Gateway, log on as user with the *ALLOBJ and *SECADM authorities.
  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. Navigate to the directory where you extracted the Sametime Gateway package and start the installation:
    • To run the installer in wizard mode, type the following command: installi5OS.bat
    • To run the installer in console mode, perform these steps:
      1. Copy the directory containing the extracted Sametime Gateway package (for example, /TMP/SametimeGateway) to the IFS of the IBM i system.
      2. Start a QSHELL session.
      3. Navigate to the directory containing the extracted Sametime Gateway package and type the following command: install.sh -console
        Attention: If one or more of the DNS addresses in your environment (for example: WebSphere Application Server installation host name, DB2® host name, or LDAP host name) refers to an IPv6-format address, add the following option to your install command to work around an IPv6-related issue with the installer:
        install.sh -console -V BypassWasInfoCheck=true

        Because your input will not be verified during installation, you should take extra care when typing values.

  8. Select the language for the installation wizard, and the click OK.
  9. On the Welcome page, click Next.
  10. On the Software License Agreement page, read the license agreement carefully, click Agree, and then click Next.
  11. Select Deployment Manager as the type of installation, and then click Next.
  12. Type the node name, cell name, host name, profile name, and starting port value for the WebSphere Application Server as follows, and then click Next.
    Table 1. Deployment Manager settings for WebSphere Application Server
    Field Value
    Node Logical name for the node. For example, exampleNode.
    Cell Name for the cell. Every WebSphere Application Server is created on a node inside a cell. A cell is a collection of nodes for administration and workload management. For example, exampleCell.
    Host name Fully qualified domain name of the computer on which you are installing WebSphere Application Server. For example: server1.example.com
    Profile name Name of the WebSphere Application Server profile that will be created and be installed with the Sametime Gateway Server. For example: STGW_Profile
    Starting port IBM i supports running multiple profiles and instances of WebSphere Application Server at the same time; to avoid port conflicts the profile created will not use the default ports. Select a port range of 50 consecutive unused ports on your system, and enter the first port number as your starting port. For example: 10000.
  13. Create a WebSphere administrator account by supplying a new user ID and password, and then click Next.
    The user must not exist in the LDAP directory. The password must not contain accented characters or any of the following characters:
    ;*!?"/<>|+&'`[]%^  
  14. Review the default directory path where Sametime Gateway Server will be installed, change it if necessary, and then click Next.

    To change the location, click Browse and select a location, or type a new path.

  15. Provide database properties for the Sametime Gateway database hosted on DB2 and then click Next.
    Table 2. Database properties for the Sametime Gateway database
    Database Properties Value
    Host name Fully qualified host name or TCP/IP address of the DB2 server.
    Port Port number of the DB2 server (typically 50000 on Windows™ and 50001 on AIX® or Linux™).
    Database name The name of the database that you created (the name is not case sensitive). If you used the default database name, type STGW.
    Application user ID The user ID of the DB2 administrator.
    Application password The password of the DB2 administrator.
    Schema user ID The ID for the user that has appropriate permissions to create tables in the database; typically the DB2 administrator.
    Schema password The password for the schema owner
  16. Choose whether to connect to the LDAP server now, or to defer that task until after installation is complete, and then click Next.
    • Configure LDAP now

      Configure the LDAP connection now if you will not require an SSL connection. If you choose to configure the connection now, continue to the next step.

    • Configure LDAP after the installation

      Configure the LDAP connection later if you will use SSL, if you do not know the host name and port number used by LDAP, or if there is a firewall between the LDAP server and this new Sametime Gateway server. If you choose to configure the LDAP connection later, skip to step 22.

  17. Select an LDAP host name from list of Registered host names and ports in your domain, or select Other and type a host name or IP address in the Host name field. Accept the default port or change it now, and then click Next.
  18. Choose whether to allow anonymous access, and then click Next..

    If your LDAP server is not configured to allow anonymous access, you will not see this option.

    • Anonymous access

      Select this option if you don't need authenticated access to the LDAP server, and skip to step 22.

    • Authenticated access

      Select this option if your LDAP server requires authenticated access, and continue to the next step. You must provide an authentication identity, including a bind distinguished name and password from the LDAP administrator.

  19. Enter the Bind distinguished name (DN) and Bind password values, and then click Next..
    • Bind distinguished name
      The bind distinguished name can be any user with read access to the LDAP server; this user does not have to be the LDAP administrator. For example:
      uid=ldapadmin,cn=users,l=shipley,st=kansas,c=us,ou=example,o=medical,DC=EXAMPLE,DC=COM
    • Bind password

      For example: 8M96l02CxyP

  20. In the Base distinguished name field, select a base distinguished name from the list of Suggested base distinguished names in your LDAP or provide one, and then click Next.
    Note: This page does not display if you are connecting to an IBM Domino® LDAP.

    The base distinguished name indicates the starting point for LDAP searches. For example, for the bind distinguished name given as an example in the previous step, you can specify the base DN as: DC=EXAMPLE,DC=COM. For authorization purposes, this field is case sensitive.

  21. On the Sametime Gateway Server installation summary page, review the installation settings, change them if needed, and then click Install.

    Click Back to make changes to installation settings.

  22. Read the installation summary, optionally click View log file to review the log, and then click Finish to close the wizard.

    To view the installation log after the wizard is closed, open the log file at stgw_server_root\logs\installlog.txt.

  23. Test the deployment manager installation and ensure that LDAP settings are correct:
    1. Navigate to the stgw_profile_root/bin directory.
    2. Start the deployment manager with the following command: ./startManager dmgr
    3. Log in into the Integrated Solutions Console WebSphere administrator user ID and password that you created.
    4. Test the LDAP connectivity. Click Users and Groups > Manage users.
    5. Verify that you can search and retrieve users in your LDAP directory.

What to do next

Leave the deployment manager node running as you install other nodes in the cluster.