Installing a single production node on Linux with the X Window System

A single production node includes one to four members (catalog, container, informational, operational). Use this procedure for stand-alone production installations.

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.
2. In the Product Overview window of the launchpad, take one of the following actions:
   • If you did not install the Installation Manager, click Install IBM Installation Manager. After the installation completes, close the Installation Manager and reopen the launchpad to install B2B Advanced Communications.
   • If you installed the Installation Manager, click Install IBM B2B Advanced Communications.
   The Installation Manager is displayed.

   You now use the information that you recorded in your Installation Manager worksheet.

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 - Initial installation feature and click Next.
9. Configure the WebSphere MQ message provider with the following information:
   • Connection name list

     If you are using a multi-instance queue manager, you must type a comma-separated list of all of the queue manager instances that are managed by the queue manager.

   • Queue manager name
   • Server connection channel name
   • User name
   • Password

   Click Next after you enter the configuration information.

   The Data source configuration page is displayed.
10. On Data source configuration page, slect the database.
11. Optional: If you want to automatically create the database schema in the specified data sources, select the box for that feature.
12. Optional: If you are automatically creating the database schema, specify whether you want to drop existing tables before you create the schema.
13. (Oracle and SQL Server only) Select the database driver.
14. Configure each data source by using the following guidelines:
    • If you want to use the same server name, port, user name, and password for all four of the data sources, perform the following task:
      1. Click Use a common server and security configuration for all datasources.
         Important: Do not select this check box if you want to install B2B Advanced Communications using an Oracle database.
      2. Enter the unique database names for all four of the data sources.

         For Oracle, you can use the database service name, instead of using the database name or database service ID (SID) in the Database name field. To use the service name, select Use an Oracle database service name and type the name in the Service name field.

      3. (DB2® only) Enter the schema name for the DB2 database for all four of the data sources.
      4. Enter the following information for just the Identity data source:
         • Server name
         • Port (defaults to 50000 for DB2, 1521 for Oracle, or 1433 for SQL Server)
         • User name
         • Password
    • If you do not want to use the same server name, port, user name, and password for all four of the data sources, enter the following information for each data source:
      • Database name

        For Oracle, you can use the database service name, instead of using the database name or database service ID (SID) in the Database name field. To use the service name, select Use an Oracle database service name and type the name in the Service name field.

      • (DB2 only) schema name
      • Server name
      • Port (defaults to 50000 for DB2, 1521 for Oracle, or 1433 for SQL Server)
      • User name
      • Password
    • (Oracle and SQL Server only) If you need more information for a data source than what the fields allow, click Provide a datasource URL. Then, enter a user name, password, and JDBC URL. An example of a JDBC URL is jdbc:database:driver_type:[username/password]@database_specifier.

    Click Next after you enter the data source configuration information.
    The Data grid configuration page is displayed.
15. Enter the following information that is used by each member of the node to authenticate to the data grid:
    • User name
    • Password
    • Password confirmation
16. Enter 1 for the number of catalog servers that you are using.
17. Enter the following information for the catalog server that you are using:
    • Catalog host name
    • Catalog server name (defaults to CATALOG_1)
    • Listen port (defaults to 2809)
    • Client port (defaults to 6600)
    • Peer port (defaults to 6601)

    Click Next after you enter the data grid configuration information.

    Restriction: You cannot enter localhost or 127.0.0.1 for the catalog server name. Ensure that you use a valid hostname or IP address.
    The Member configuration page is displayed.
18. 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. Then, configure the information that is displayed under the member.
    Important:

    • If this installation is a stand-alone installation, you must configure all four members.
    • If you add another node to create a cluster, the member names and the container grid zone name do not have default values.

    • Operational
      • Member name (defaults to OPERATIONAL_1)
      • JMX port (defaults to 9443)
    • Informational
      • Member name (defaults to INFORMATIONAL_1)
      • HTTPS/JMX port (defaults to 19443)
    • Container
      • Member name (defaults to CONTAINER_1)
      • JMX port (defaults to 18443)
      • Grid zone name (defaults to ZONE_1)
    • Catalog
      • Member name (defaults to CATALOG_1)

        This name must match the catalog server name that you entered on the Data grid configuration page.

      • JMX port (defaults to 17443)

    Click Next after you enter the member configuration information.
    The Security page is displayed.
19. 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.

20. 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.
21. 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.
22. Click Install to populate the installation directory with the configuration information.

    When the installation completes, click Finish.

23. Close the Installation Manager by clicking File > Exit.
24. If you are manually creating queues, see ../com.ibm.help.meg.planning.doc/meg_plan_topology_config_WMQ.html.
25. Open a command-line window.
26. Navigate to the [Installation directory]/Members/bin directory.
27. To start the node, type execute member start all.
28. To configure the storage system, type execute storage -provision -a.

    For more information about provisioning storage, see ../com.ibm.help.meg.configuring.doc/meg_stor_provisioning_storage.html.

29. Access the installation at https://[Installation Hostname or IP address]:[Informational port number]/advcomm.
30. 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 ../com.ibm.help.meg.configuring.doc/meg_config_defaultaccountcreds.html.