View and Restore Performance Configuration Settings

Edit online

You can view current performance configuration settings to verify whether a particular performance configuration setting is correct and restore previous performance configuration settings.

View Performance Configuration Settings

You can view the current performance configuration settings to verify if they are correct. The Performance Tuning page displays all settings that are currently set and suggested changes. The suggested changes displayed in this page are also displayed if you are tuning the performance using the performance tuning utility. For more information about using the performance tuning utility, refer to the topic Edit Performance Configuration Settings.

To view your performance configuration settings:
  1. From the Administration menu, select Operations > System > Performance > Tuning.
  2. In the Performance Tuning page, under View, next to View Performance Configuration, click Go!.
  3. In the Performance Settings page, review the performance configuration settings, which include information on:
    • 1) System
    • 2) JVM Parameters for Server
    • 3) JVM Parameters Container Nodes
    • 4) BP Queue
    • 5) Cache
    • 6) Purge Settings
    • 7) Database Connection Pool
    • 8) Queue Settings
    • 9) Memory
  4. Click Return to return to the Performance Tuning page.

Restore Performance Configuration Settings

You can manually restore performance configuration settings to return Sterling B2B Integrator to the previous performance state. In the Restore Tuning page, the properties that will change if you restore the previous performance configuration settings are displayed in blue color text and bold format.

The User ID, along with the user name, and the time when the last performance configuration settings were last edited are displayed under the Restore tab in Performance Tuning page.

You can restore your performance configuration settings only once. If you try restoring the performance settings more than once, there will be no changes in the settings. You can restore the performance configuration settings under the following conditions, but not limited to:
  • Previous performance setting was more efficient than the current setting.
  • When you are testing performance by setting optimum values, restoring to the previous setting is convenient.
  • Testing under varying load conditions to benchmark performance configuration settings.
To restore your performance configuration settings:
  1. From the Administration menu, select Operations > System > Performance > Tuning.
  2. In the Performance Tuning page, under Restore, next to View/Restore Previous Configuration, click Go!.
  3. On clicking Go, the Performance Tuning UI lock-enabled message is displayed:

    Performance Tuning UI lock enabled. Lock will be released only by clicking on Cancel or Finish in the wizard.

    Click OK. If the lock is not released or if you close the page without clicking Cancel or Finish, you must use the Lock Manager function to release the lock.

  4. In the Restore Tuning Configuration page that is displayed, the properties that will change if you restore the previous performance configuration settings are displayed in blue color text and bold format. Review the performance configuration settings and perform one of the following tasks:
    • To abandon restoring the previous performance configuration settings, click Cancel.

    • To restore the previous performance configuration settings, click Finish. The Restore Tuning Properties page appears after the restoration is complete. The following message appears: The system update completed successfully.

      If you restore the previous configuration settings, click Return to return to the Performance Tuning page.

  5. From the Administration menu, select Operations > System > Troubleshooter.
  6. From the System Troubleshooting page, click Soft Stop. This runs the softstop script, allowing all active business processes to complete on a node before stopping the system. The script is run through a series of interactive steps in the UI. For more information about the softstop process, refer to Completing a Soft Stop of Sterling B2B Integrator from the System Troubleshooter.
  7. From the install_dir/bin directory, run one of the following commands:
    • (UNIX or Linux®) setupfiles.sh
    • (Windows) setupfiles.cmd

    The performance configuration changes populate the initial setup files that are used during startup.

  8. For Docker, after the performance tuning properties are updated from the user interface of Sterling B2B Integrator, follow these steps for the changes to take effect:
    For Docker version 17.06.2-ee-13:
    • Run docker exec -it <container-id> /ibm/b2bi/install/bin/hardstop.sh.
    • Run docker exec -it <container-id> bash.
    • Go to /ibm/b2bi/install/bin and run ./setupfiles.sh.
    • Run exit and come out of the Docker container.
    • Run docker stop <container-id>.
    • Run docker start <container-id>.
    For Docker version 18.06.0-ce:
    • Run docker exec -it <container-id> /ibm/b2bi/install/bin/hardstop.sh.
    • Run docker exec -w /ibm/b2bi/install/bin [container-id] ./setupfiles.sh.
    • Run docker stop <container-id>.
    • Run docker start <container-id>.
  9. From the install_dir/bin directory, start Sterling B2B Integrator by running one of the following commands:
    • (UNIX or Linux) run.sh
    • (Windows) startWindowsService.cmd

    Sterling B2B Integrator starts and the previous performance configuration settings are applied. The properties in the tuning.properties file will have the same values as the corresponding properties in the tuningPreviousSetting.properties file. In addition, the tuningPreviousSetting.properties file will have these properties:

    • jdbcService.[database]UIPool.buffersize
    • jdbcService.[database]UIPool.initsize
    • jdbcService.[database]UIPool.maxsize
    • jdbcService.[database]Pool_NoTrans.buffersize
    • jdbcService.[database]Pool_NoTrans.initsize
    • jdbcService.[database]Pool_NoTrans.maxsize
    • jdbcService.[database]Pool_local.buffersize
    • jdbcService.[database]Pool_local.initsize
    • jdbcService.[database]Pool_local.maxsize
    • jdbcService.[database]ArchivePool.buffersize
    • jdbcService.[database]ArchivePool.initsize
    • jdbcService.[database]ArchivePool.maxsize
    • jdbcService.[database]Pool_Select.buffersize
    • jdbcService.[database]Pool_Select.initsize
    • jdbcService.[database]Pool_Select.maxsize
    • jdbcService.[database]Pool.buffersize
    • jdbcService.[database]Pool.initsize
    • jdbcService.[database]Pool.maxsize

View and Restore Performance Configuration Settings on a Certified Container Setup

You can use the View option to see the applied properties for ASI nodes only. The section for container nodes is blank as AC pods are independently running in a Certified Container deployment.
Note: The Restore wizard is disabled.