Installing a proof of concept node on Linux with the X Window System

A proof of concept installation is an installation that by default includes one node with all four members (informational, operational, catalog, container). You can use this installation for demonstrations and small production installations.

Before you begin

Use the installation launchpad, Installation Manager, and commands to install a proof of concept node of B2B Advanced Communications on Linux with the X Window System.

Before you install the minimum high availability cluster, perform the following tasks:

  • Access the media package of files that includes the installation launchpad.
    Important: You must use the installation launchpad to install B2B Advanced Communications. You cannot use a stand-alone installation of the Installation Manager. The launchpad automatically configures the Installation Manager with the repository file that is required for the installation.
  • To set up the correct permissions in your Linux system, enter umask ugo+rx.
  • Do the following to set up your launchpad and Installation Manager environment:
    • Install the X Window System in your Linux installation.
      Important: Launchpad does not start and run the Install Manager if the X Window System is incorrectly configured or missing certain libraries: libXtst, libXmu, and xorg-x11-xauth. For more information about troubleshooting the X Window System to install B2B Advanced Communications, see ../com.ibm.help.meg.troubleshooting.doc/b2bac_tshooting_x11.html.
    • Install the Mozilla Firefox browser. For more information about the supported level of Firefox, see the system requirements.
Restriction: You cannot upgrade this proof of concept installation. To use a newer version of B2B Advanced Communications, you must uninstall this installation and install a new proof of concept installation with the newer version.

About this task

You can use the proof of concept installation as a small production installation before you set up your full production installation.

The installation of a proof of concept node requires much less configuration than the installation of a production node. Much of the configuration is built in to the installation. The differences include the following items:

  • You do not need to set up an external database. The open source Derby database is a default part of the installation.
  • You do not need to set up a message provider. WebSphere® eXtreme Scale is used as the message provider.

Most fields require user input. Those fields that are not required are designated as optional. If you do not enter information for a required field, and you click Next to go to the next screen, the installation stops. The fields that need information are identified with red X marks.

Important: If you are installing B2B Advanced Communications and Sterling B2B Integrator together on one server that has less than 16 GB of random access memory (RAM), you must start each application separately.

Procedure

  1. Start the installation launchpad by performing the following task:
    1. Open the directory where you extracted the downloaded installation files.
    2. To launch the launchpad, enter launchpad.sh.
    The Product Overview window of the launchpad is displayed.
  2. 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.
  8. Select the Proof of Concept (POC) Installation feature and click Next.
  9. Change any of the default values for the four different members.
    • Catalog
      • Member name (default value of MEG_CS cannot be changed)
      • JMX port (defaults to 17443)
    • Container
      • Member name (defaults to MEG_CONT)
      • JMX port (defaults to 18443)
      • Grid zone name (defaults to DefaultZone)
    • Operational
      • Member name (defaults to MEG_OP)
      • JMX port (defaults to 9443)
    • Informational
      • Member name (defaults to MEG_INFO)
      • HTTP(S)/JMX port (defaults to 19443)
    Click Next after you enter the member configuration information.
  10. 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.

  11. 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, check the box at the Install Java Cryptography Extension (JCE) Unlimited Strength Jurisdictional Policy field and access the JCE file at the JCE file field.
  12. 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. Enter a certificate alias for the PKCS12 file (defaults to System).
    2. In the PKCS12 system certificate archive field, select the PKCS12 file.
    3. Enter a password for the PKCS12 file.

    After you enter the security information, click Next.

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

    When the installation completes, click Finish.

  14. Close the Installation Manager by clicking File > Exit.
  15. If you are manually creating queues, see ../com.ibm.help.meg.planning.doc/meg_plan_topology_config_WMQ.html.
  16. Open a command-line window.
  17. Navigate to the [Installation directory]/Members/bin directory.
  18. To start the node, type execute member start all.
  19. 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.

  20. Access the installation at https://[Installation Hostname or IP address]:[Informational port number]/advcomm.
  21. 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.

What to do next

You can now configure the rest of B2B Advanced Communications, including organizations, user credentials, and exchange profiles.