Installing initial Global Mailbox and Sterling B2B Integrator nodes

To set up your data center to use the Global Mailbox system, you must install the initial Global Mailbox node after installing and configuring all the prerequisites.

1. Open a command prompt and do one of the following tasks to start the Installation Manager:
   1. Go to the IM_<operating_system> directory and type ./userinst or userinst.exe (Windows) for the following scenarios:
      • If you do not have the Installation Manager installed and are using the Installation Manager agent that is provided with package.
      • If you have a 64-bit Installation Manager installed.
      • If you have the Installation Manager installed on a platform that has only one download available for Installation Manager. For example, AIX, HP, zLinux.
   2. Go to <installation directory>/Installation Manager/eclipse (for Windows system, replace / with \) and type ./IBMIM or IBMIM.exe (Windows), if you have 32-bit Installation Manager installed on a Linux or Windows system.
   Attention: It is suggested that you record a response file when installing Sterling B2B Integrator or later and Global Mailbox. For more information, see Recording a response file.
2. On the Installation Manager home page, click Install.
   Important: If IM_<operating_system>, gmrepo, and b2birepo directories are not in the same directory or if you already have Installation Manager installed, then you get a message saying that there no packages to install or Installation Manager could not connect to the repositories. You must add the Global Mailbox and Sterling B2B Integrator repository files to the Installation Manager repository. For more information about adding repository files, see Repository preferences.
3. On the Install Packages screen, select IBM Sterling B2B Integrator and Global Mailbox. This action selects the versions also. Click Next.
4. Read the license agreement, accept it, and click Next.
5. Click Browse and specify the shared resource directory and click Next. You can choose to retain the default directory.

   The shared directory is used to store files that can be shared by multiple packages. For example, Sterling B2B Integrator and the Global Mailbox node.

6. Click Browse and specify the installation directory for Sterling B2B Integrator and click Next. You can choose to retain the default directory.

   The installation directory is used to store files specific to Sterling B2B Integrator.

7. Select the translation (language) to install and click Next.

   The language selection is for the Installation Manager, or the installer only.

8. Select the required Sterling B2B Integrator features and select Initial Global Mailbox Node under Global Mailbox <version>, where <version> is the Global Mailbox version you are installing. Click Next.
9. Enter the host name or IP address of the ZooKeeper nodes in all data centers and click Add. If the default client port number is not used when you installed the ZooKeeper nodes, change the port number.
   The Global Mailbox node you are installing is a client. The client connects to the ZooKeeper nodes you define in this step. Zookeeper nodes are part of the Zookeeper ensemble that manages resource locks used by Global Mailbox.

   Important: When installing the initial Global Mailbox node, you must provide information about the ZooKeeper, Cassandra, and WebSphere MQ nodes in all the data centers. The ZooKeeper nodes that you are adding here must be started and running. ZooKeeper configuration information is stored in the global.properties file.

   If you do not want to connect to the ZooKeeper node or made a mistake when entering the node details, then you can choose to remove the node. To remove a node, select the node and click Remove. Removing the ZooKeeper node does not stop or uninstall the ZooKeeper node. If you remove a ZooKeeper node in this step, the Sterling B2B Integrator or Global Mailbox nodes do not connect to the node.

10. Click Next.
11. Complete the following steps to provide Cassandra, replication, storage, and WebSphere MQ topology configuration information. The Global Mailbox node you are installing is a client, which connects to the nodes you define here.
    Important: When installing the initial Global Mailbox node, you must provide information about the ZooKeeper, Cassandra, and WebSphere MQ nodes in all the data centers.
    1. Specify the host name or IP address of each Cassandra node and click Add.
       The Global Mailbox node you are installing is a client. The client connects to the Cassandra nodes you define in this step. Cassandra nodes are part of the Cassandra cluster that manages metadata replication in the Global Mailbox system.

       Important: The Cassandra nodes that you are adding here must be started and running. Cassandra configuration information is stored in the global.properties file.

       The Cassandra nodes that you specify in this step are initialized during the installation of the initial Global Mailbox and Sterling B2B Integrator nodes. Ensure the Cassandra nodes are not preinitialized.

    2. Optional: If you had specified a custom client port when installing Cassandra, specify the port number here.

       The client port is populated by default. It is suggested to retain the default port number for all nodes. If you had used a different port number when installing Cassandra, use that port number now.

       If you do not want to connect to the Cassandra node or made a mistake when entering the node details, then you can choose to remove the node. To remove a node, select the node and click Remove. Removing the Cassandra node does not stop or uninstall the Cassandra node. If you remove a Cassandra node in this step, the Sterling B2B Integrator or Global Mailbox nodes do not connect to the node.

    3. Click Continue to Step 2.
    4. To define the shared storage location for each data center, select the data center, type the shared storage location for the data center, and click Add.
       Restriction: When installing Global Mailbox on a Windows server, you must specify the path to shared folder in the format <drive_name>:\<shared_foldername>. For example, C:\Storage or a mapped drive or Z:\Storage. A UNC path is not supported for Windows. When mounting mapped drives, you must follow the procedure specified in How to map network shares into drives to a Windows service permanently.

       When you install the initial Global Mailbox node, storage buckets (1st_provisioned and global_mbx) and the first variant (0) are created. By default, Global Mailbox uses the global_mbx bucket to store message payload. When installing the initial Global Mailbox node, you must also specify the storage base path for all other data centers. After installing the initial Global Mailbox node, the storage buckets and the configuration information (global.properties and installinfo.properties files) are copied to the storage base path specified for other data centers.

    5. Click Continue to Step 3.
    6. Type the host name and port for the replication server:

       Local Host Name

       Default is the host name of the local machine.

       Secure Server Port

       Default is 33001.

    7. Click Continue to Step 4.
    8. Select the data center where you are installing the initial Global Mailbox and Sterling B2B Integrator nodes.
    9. Click Continue to Step 5.
    10. To define the WebSphere MQ topology for each data center, select the data center, type the host name or IP address, specify the port, and click Add.
        Important: You must provide the list of WebSphere MQ servers for each data center.

        The port is populated by default. If you had used a different port number when configuring the WebSphere MQ node, use that port number now. To remove the WebSphere MQ node, select the required node and click Remove.

    11. Click Continue to Step 7.
    12. To define the WebSphere MQ configuration, complete the following steps:
        Important: The queue name, channel name, user name, and password must be same across the WebSphere MQ cluster. The installer validates if it can establish connection with the queue that is specified here. At least one queue must be present and must be active per data center for the installation to proceed, else the installation is failed. The WebSphere MQ configuration specified here is stored in the installinfo.properties file in the /config directory, along with the global.properties file.

        1. Select the data center name, type the queue manager name, and click Set.
        2. Type the queue name and channel name.
        3. Type the user name, who is authorized to use the queue.
        4. Type the password for the user name.
12. Click Next.
13. Click Select Folder and specify the JDK directory for Sterling B2B Integrator installation.
14. Specify configuration information for the Sterling B2B Integrator features you have opted to install and click Next.
15. Click Select File and select the Java™ Cryptography Encryption (JCE) policy file. Click Next.
    Important: You must use unrestricted JCE policy file to use Global Mailbox with Sterling B2B Integrator.
16. If you want to override the default host name and IP address for Sterling B2B Integrator installation, specify the alternative host name and IP address, or else, you can choose to retain the default. Click Next.
17. Type the system passphrase, confirm the passphrase, and click Next.
    Important: System passphrase is used to secure your Sterling B2B Integrator node. You must provide the passphrase when starting Sterling B2B Integrator or when installing a patch. The system passphrase provided for Sterling B2B Integrator configuration is also used as the Global Mailbox storage passphrase initially. However, changing the system passphrase does not change the storage passphrase or changing the storage passphrase does not change the system passphrase.
18. Type the following email information and click Next:
    1. Email address to which you want the system alert messages to be sent.
    2. The SMTP mail server (IP address or host name) that you want to use for system alert messages and other administrative notices.
19. Specify the following database-related information and click Next:
    1. Select the database vendor.
    2. Do not select This installation is for a cluster node 2 or higher as this installation is for the initial node.
       Important: In a cluster setup, run the startCluster command after installing the first node (node 1) from the /install_dir/bin directory, on the host where you installed the node. The syntax is startCluster.sh nodeNumber true. Replace nodeNumber with 1. After you run the startCluster command for the first node, the subsequent nodes will have clustering automatically started by the installer when they are installed.
    3. Select Apply database schema automatically to apply the database schema automatically. To manually create the database schema, clear the Apply database schema automatically check box and continue with the remaining installation steps.
       Important: If you manually apply the schema, the installation stops without error later in the installation process so that you can manually apply the schema.
20. Specify the database connection information, add the JDBC driver, and click Next.
21. Select Verbose install? if you want to generate a detailed installation log and click Next.
    Important: If you select Verbose install?, the details of the events that occur during the installation are recorded in the InstallSI.log file, or else, install events without much detail are recorded in the InstallSI.log file.
22. Do not select This installation is an upgrade from a prior version because this is a new installation.
23. Determine the performance configurations that apply to this installation and click Next. Accept the default value or type the appropriate value.
    1. Number of Processor Cores
    2. Physical Memory (MB) allocated to Sterling B2B Integrator
24. Click Install.
25. Review the installation package summary information. Notice the installation progress in the Repository Information section.
26. Click Finish.
    Important:

    • The Cassandra schema is initialized by default during the installation of the initial Global Mailbox node.
    • After you complete the installation of Sterling B2B Integrator and the initial Global Mailbox node, some warning messages are displayed. The warning messages are generated by the Cassandra drivers and can be ignored.