Installation checklist: Global Mailbox and Sterling B2B Integrator (initial install)

Use the checklist to record setup information for initial Global Mailbox and Sterling B2B Integrator installation.

Table 1. Initial Global Mailbox and Sterling B2B Integrator installation checklist
List of items for Global Mailbox and Sterling B2B Integrator Your entry Comments
Review your IBM contract to ensure that you are licensed to use Global Mailbox.    
Decide and procure the type of security certificates to use:
  • The default self-signed SSL (Secure Sockets Layer) certificate that is automatically installed.
  • A Certificate Authority-related certificate that you install before you install Sterling B2B Integrator.
    
If you are using an Oracle, Microsoft SQL Server, or DB2® database, decide whether to manually or automatically apply Database Definition Language (DDL) statements (schema) to the database.    
If you are using an Oracle 11.1 database, you must set it up for native compilation by allocating space and by setting the plsql_native_library_dir parameter.    
Determine whether the database password must be encrypted.    
Record login credentials to the host where you plan to install Global Mailbox and Sterling B2B Integrator nodes.    
Download and extract the Sterling B2B Integrator package to the server where you plan to install the nodes.    
Determine the installation mode:
  • Wizard mode
  • Silent mode
    
For Silent mode, prepare the response file. You must edit the provided example or use one you generated during a previous installation.    
Record the directory where you plan to install Global Mailbox and Sterling B2B Integrator nodes. It is suggested to retain the default directory.    
Record the data center names where you plan to install the Global Mailbox and Sterling B2B Integrator nodes.    
Record the number of Global Mailbox and Sterling B2B Integrator nodes that you plan to have in each data center.    
Record the host name or IP address of the server on which you plan to install Global Mailbox and Sterling B2B Integrator nodes.    
Record the host names or IP addresses of the servers where ZooKeeper and Cassandra nodes in all the data centers are installed.    
If you defined custom ports for Cassandra and ZooKeeper, record the port numbers.    
Record shared storage location for all data centers.    
Record the host name of the servers where WebSphere® MQ is installed and configured.    
Record the following WebSphere MQ configuration information:
  • Queue manager name
  • Queue name
  • Channel name
  • User name (who is authorized to access the queue)
  • Password
Important: 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, or else the installation fails.
   
Record the path to the JDK.    
Record the path to the JCE file.
Important: You must use unrestricted JCE policy file to use Global Mailbox with Sterling B2B Integrator.
    
Record the base port number for Sterling B2B Integrator.    
Ensure that your firewalls are configured to allow connections to the ports. For more information, see Firewall considerations.    
Record the system passphrase.    
Record the email address and the SMTP mail server IP address.    
Record the cluster number.    
Record the database vendor name.    
Record the database user name.    
Record the database password.    
Record the database (catalog) name.    
Record the database host name.    
Record the path and file name for the JDBC driver or drivers.