Configurations for Unix/Linux

If you are using a Unix or Linux operating system, you must perform certain operating system configuration tasks before you upgrade Sterling B2B Integrator.

AIX

During the upgrade process, you must specify the name of the installation directory. The installation process creates this directory and beneath it, a directory called install. To ensure that /<install_dir>/install has the necessary permissions, AIX users must run the following command on the parent directory of /<install_dir>/install before installation:

chmod -R a-s <absolute path>/install_dir_parent

where <install_dir_parent> is the directory in which /<install_dir>/install is created.

For example, to specify

AIX_1/applications/test1/<my_install> as your installation directory, run the command from the AIX_1/applications directory (directly above the test1 directory):

chmod -R a-s test1

or from another location on the file system:

chmod -R a-s /AIX_1/applications/test1

This ensures that when the <my_install> directory is created during installation, it inherits the correct permissions from test1.

Linux

You can either enable or disable SELinux feature by editing the SELinux property value to Enforcing or disabled under /etc/sysconfig/selinux.

Ensure that /etc/hosts has short-names first for all entries. For example, 127.0.0.1localhostlocalhost.localdomain

If the base locale is English, verify:
  • LANG variable is en_US
  • LANG variable is exported

Red Hat Enterprise Linux 6.x, 7.x, and 8.x versions

Make the following system changes:

  1. If the base locale for the system is English, for Red Hat Enterprise Linux 6.x versions, edit the /etc/sysconfig/i18n file by changing the SUPPORTED variable from en_US.utf8 to en_US. You can also allow multiple locale support with the following format: en_US.utf8:en_US. For Red Hat Enterprise Linux 7.x or higher versions, edit /etc/locale.conf to make sure that LANG=en_US not LANG=en_US.utf8.
  2. Save and close the /etc/sysconfig/i18n file. Edit the /etc/security/limits.conf file by adding the following lines:
    • * hard nofile 8196
    • * soft nofile 4096
    • * hard memlock 3000000
    • * soft memlock 3000000
    • * hard nproc 16000
    • * soft nproc 16000
    • * hard stack 512000
    • * soft stack 512000

    This updates the system ulimits.

    For nofile, the values shown are examples. The possible values are unlimited, so the numbers for hard nofile and soft nofile can be much larger. Revise these values as appropriate for your business needs.

  3. Save and close the /etc/security/limits.conf file.
  4. Reboot the system.
Note: IBM Installation Manager in UI mode may fail to start on an RHEL 6.1 or higher x86_64 (64-bit) OS because Installation Manager is a 32-bit application and is dependent on some of the 32-bit libraries. For information on installing the required 32-bit OS libraries, refer to the IBM Support Website (https://www-304.ibm.com/support/docview.wss?uid=swg21459143).
CAUTION:
Due to a known issue with the IBM JDK on RHEL 6.1 or higher, a performance degradation might be seen in comparison to previous RHEL releases. To avoid this issue, disable the CFS on RHEL 6.1 or higher.

To disable CFS:

  • Log in as root
  • Edit /etc/sysctl.conf and add "kernel.sched_compat_yield = 1"
  • Reboot the system

For more information go to the IBM SDK and Runtime Environment Java Technology Edition Version 6 Information Center and search for known limitations on linux.

SUSE Linux

Make the following system changes:

  1. If the base locale for the system is English, edit the /etc/sysconfig/i18n file by changing the SUPPORTED variable from en_US.utf8 to en_US. You can also allow multiple support with the following format: en_US.utf8:en_US
  2. Save and close the /etc/sysconfig/i18n file. Edit the /etc/security/limits.conf file by adding the following lines:
    • * hard nofile 8196
    • * soft nofile 4096
    • * hard memlock 3000000
    • * soft memlock 3000000
    • * hard nproc 16000
    • * soft nproc 16000
    • * hard stack 512000
    • * soft stack 512000

    This updates the system ulimits.

    For nofile, the values shown are examples. The possible values are unlimited, so the numbers for hard nofile and soft nofile can be much larger. Revise these values as appropriate for your business needs.

  3. Save and close the /etc/security/limits.conf file.
  4. Reboot the system.