Required steps for patch updates for Sterling Integrator

Useful link for interim fixes: ftp://ftp.ecurep.ibm.com/fromibm/other/b2bcommerce

CorrelationSearch:
If you are using other than MySQL Database then

1. Look at the row count in the database table - CORRELATION_SET table.

If you are using a non-MySQL database and you have less than the threshold number of rows in the CORRELATION_SET table, the patch installs all items and the value of the new useNewCorrelationSearchproperty is set to True after the patch install.

The threshold is 10 million rows for Oracle and MSSQL databases, and 5 million for other databases, such as DB2® UNIX and DB2 iSeries®

2.  If you are using a non-MySQL database and you have more than the threshold number of rows in the CORRELATION_SET table, the patch process is two-step process. The value of theuseNewCorrelationSearch property is False after the first step in this process and it is True after the second step.

• • The first step in this process is to install the patch, which applies the minimal items required and displays a message prompting you to run a command-line based tool called cs_conversion_tool.sh orcs_conversion_tool.cmd. This tool is run from the install_dir/bin/ directory.
  • The second step is to run the command-line based tool and, once the command-line based tool completes, you must restart the Sterling B2B Integrator. For relatively large enterprise databases, theSterling B2B Integrator will be shut down for the minimal tasks, but other patch install tasks are performed in online mode.

You do not need to take any action in regard to this property unless you want to use the old functionality for some reason. In that case, you need to access the install_dir/properties/cssearch.properties file and set the useNewCorrelationSearch property to False. This will enable you to return to the previous state (using the old correlation search functionality), without impacting your system

3. Placement of Indexes

The DDL statements create a minimal set of indexes for general use. You might need to create more indexes to suit your business needs. Contact IBM Professional Services or IBM Customer Support to create more indexes. You should also maintain a list of the indexes added and ensure that they are present after you upgrade Sterling B2B Integrator and monitor its usage. These indexes may or may not be added to the Sterling B2B Integrator and is specific to your operating environment.

You might want to create more table spaces for storing indexes in addition to those table spaces for the base tables. Table spaces should have multiple data files for I/O load balancing.

Important: Indexes can also be separated out into different storage areas. This action should be done in coordination with your database administrator. However, if you are moving tables to different storage areas, do so only in coordination with IBM Professional Services to prevent upgrade issue in the future.

Database tables that can substantially grow

The following table lists some of the tables that are defined in Sterling B2B Integrator experience substantial input, output, and rapid growth.

Table name	Table function
DATA_TABLE	These tables hold the binary payload of documents that are used for processing within Sterling B2B Integrator.
DOCUMENT CORRELATION_SET	Contain document metadata that is used for searchability and enablement of various document processing tasks.
WORKFLOW_CONTEXT	Contains step status and business process flow information.
ARCHIVE_INFO	Holds lifespan information that pertains to all business processes and document storage in the system.

These tables are candidates for moving to a table space or segment that is separate from the rest of the database.

Important: Move these tables only in coordination with IBM Professional services. When patches or upgrades that need to re-create a table are installed, the installation attempts to create them in the default table space