Installing an additional production node on Linux with the X Window System

Use this procedure for multiple node production installations when you are adding nodes after the initial installation.

1. Start the installation launchpad by performing the following task:
   1. Open the directory where you extracted the downloaded installation files.
   2. To start the launchpad, enter launchpad.sh.
   The Product Overview window of the launchpad is displayed.
2. Click Install IBM B2B Advanced Communications. The Installation Manager is displayed.
3. Click Install.
4. Select the installation package for your version of B2B Advanced Communications and click Next.
5. Accept your user's license by checking the option I accept the terms in the license agreement and clicking Next.
   Important: This license is a general license that applies to all installations of B2B Advanced Communications. A different and unique license determines your type of installation.
6. Select a shared resources directory and click Next.
7. Select or create an installation directory and click Next.
   Restriction:

   • The installation directory must not contain any files.
   • Do not use non-ASCII characters like é or ö in the directory path. You cannot start or uninstall B2B Advanced Communications if the installation directory path includes non-ASCII characters.
   A screen is displayed that shows the available features and the available disk space for your installation.
8. Select the Production - Extend an existing cluster feature and click Next.
9. Click Install.
10. Choose one of the following types of configuration:
    • If you are bootstrapping the data grid, import the configuration from message fabric, data grid, and data source properties files of the first node.

      Browse for the SystemConfigurationMFLoader.properties, SystemConfigurationXSLoader.properties, and SystemConfigurationDSLoader.properties files that were installed in the first node. These files are in the install_dir/Members/resources directory.

    • If you are not bootstrapping the data grid, retrieve the configuration from the data grid.

      Enter the following information from the first node:

      • Catalog server host
      • Catalog server port
      • WebSphere® eXtreme Scale data grid user name
      • WebSphere eXtreme Scale data grid password
11. Click Next.
12. Select the database that you used for the existing nodes.
13. Optional: If you want to automatically create the database schema in the specified data sources, select the box for that feature.
14. Optional: If you are automatically creating the database schema, specify whether you want to drop existing tables before you create the schema.
15. If you are using the Oracle or the SQL Server database, select the database JDBC driver that you used for the existing nodes and click Next. If you are using the DB2® database, you do not need to select a JDBC driver.
16. Decide what members to deploy on the node that you are installing. Configure a member by first checking the Deploy member_type member check box of the member. Then, configure the information that is displayed under the member.
    Important: The member names have default values for only the first node that you install. The member names on additional nodes must be unique.
    • Operational
      • Member name
      • JMX port (defaults to 9443)
    • Informational
      • Member name
      • HTTP(S)/JMX port (defaults to 19443)
    • Container
      • Member name
      • JMX port (defaults to 18443)
      • Grid zone name
        Important: Each container member in a high availability installation must be in a uniquely named zone.
    • Catalog
      • Member name

        This name must be different from the names of the catalog members on other nodes. This name must match the name of one of the catalog names that you created when you set up the data grid.

      • JMX port (defaults to 17443)
17. Enter and confirm a system passphrase that is used to start the system, access protected system information, and create the keystore.

    You can later change this passphrase by using the passphrase set command.

18. Decide whether you want to use the default JCE file that is included in the installation or the stronger JCE file that you must download from IBM.
    Attention: The default JCE file does not provide strong encryption.
    • If you want to use the default JCE file, do not check the box at the Install Java Cryptography Extension (JCE) Unlimited Strength Jurisdictional Policy field.
    • If you want to use the stronger JCE file, select the box at the Install Java Cryptography Extension (JCE) Unlimited Strength Jurisdictional Policy field and access the JCE file at the JCE file field.
19. If you want to install a custom system certificate for securing the user interface and Java™ Management Extensions (JMX), select the box for that feature. Then, complete the following fields.

    If you do not select the box, a self-signed certificate is generated for securing the user interface and JMX.

    1. In the PKCS12 system certificate archive field, select the PKCS12 file.
    2. Enter a password for the PKCS12 file.
    3. Enter a certificate alias for the PKCS12 file (defaults to System).

    After you enter the security information, click Next.

    The Install Packages page is displayed.
20. Click Install to populate the installation directory with the configuration information.

    When the installation finishes, click Finish.

    • All of the installation files are in the installation directory.
    • The members have all been enabled. Start the members from a command line.
21. Close the Installation Manager by clicking File > Exit.
22. If you are manually creating queues, see Manually creating queues in WebSphere MQ.
23. Open a command-line window.
24. Navigate to the [Installation directory]/Members/bin directory.
25. To start the node, type execute member start all.
26. To configure the storage system, type execute storage -provision -a.

    For more information about provisioning storage, see Provisioning storage from the command line.

27. Access the installation at https://[Installation Hostname or IP address]:[Informational port number]/advcomm.
28. Log in to the installation with the default account that you were assigned. The two default accounts are System Administrator, sysadmin, and Master Account Administrator, maccountadmin. For more information about default account credentials, see Configuring default account credentials.