Multitenancy support on Oracle 19c

You can install Sterling B2B Integrator on Oracle Multitenant environment.

Preparing the Oracle database software

Before you begin, you must prepare the Oracle database software to enable its functioning in a multitenant environment. For more information, see the Oracle Multitenant Administrator's Guide.

Run the following query after the Oracle database server is ready.


SQL> SELECT CDB FROM V$DATABASE;
CDB
---
YES
SQL>

The Oracle database is now enabled in a multitenant environment.

Installing Sterling B2B Integrator on Oracle

Sterling B2B Integrator and Oracle recommends to use the Service Name to connect to the database and install Sterling B2B Integrator.

You must follow certain important steps for IIM and Silent installations to install on Oracle Multitenant environment.

Using IIM

Select the option Use the database catalog name as an Oracle Service name instead of an SID in the DB Vendor Selection screen during installation in the IIM wizard.
```
For example:
Catalog Name – pdb1.in.ibm.com or the custom name that you provide while configuring the container database.
```
Follow the remaining steps to install Sterling B2B Integrator as in the case of a new installation.

Using Response File

Set the statement to true.


<data key='user.sb.USE_SERVICE_NAME,com.ibm.sterling.integrator.install.offering' value='true'/>
For example:
<data key='user.sb.DB_DATA,com.ibm.sterling.integrator.install.offering' value='pdb1.in.ibm.com'/>

Follow the remaining steps to install Sterling B2B Integrator as in the case of a new installation using the Response File.

Upgrading Sterling B2B Integrator on Oracle

The following are the recommendations when you want to upgrade from previous Sterling B2B Integrator versions to the latest version on Oracle Multitenant environment.

There is no change in the process of Sterling B2B Integrator application upgrade, if you are already on the container database (CDB) or pluggable database (PDB).
It is recommended to first upgrade the Sterling B2B Integrator application from an older versions to v6.1.0.1 and then perform the database (Oracle) upgrade, assuming that there is no change in the database Port and Service Name.
It is recommended to first upgrade the Sterling B2B Integrator application from an older versions to v6.1.0.1 and then perform the following changes, if there is a change in the database Port and Service Name.
1. Update with the new Port and Service Name details in the sandbox.cfg properties file.
```
Port

YANTRA_DB_PORT=1529
DB_PORT=1529
ORACLE_JDBC_URL=jdbc\:oracle\:thin\:@10.15.103.54\:1529/orclx.in.ibm.com
ORA_PORT=1529

Service Name

DB_DATA=orclx.in.ibm.com
ORA_DATA=orclx.in.ibm.com
ORACLE_JDBC_URL=jdbc\:oracle\:thin\:@10.15.103.54\:1529/orclx.in.ibm.com
YANTRA_DB_DATA=orclx.in.ibm.com
```
2. Run setupfiles.sh for Linux/Unix or setupfiles.cmd for Windows from the <Install Dir>/bin/ location.
3. Run deployer.sh for Linux/Unix or deployer.cmd for Windows.
4. Start the Sterling B2B Integrator services using run.sh for Linux/Unix or runAll.sh/startWindowsService.cmd for Windows.

For more information on upgrading and converting a non-CDB to PDB, see Upgrading and Converting Non-CDBs to a PDB with the Same Operating System.

After converting the database to CDB, verify the database is up and running using any database clients. (For example: You can use SQL Developer to connect the database and verify multitenancy is enabled).

Note:

If you use SID as Catalog Name to install Sterling B2B Integrator, then you can convert non-CDB to CDB at root level. You cannot convert this as a pluggable database, since PDB uses Service Name to connect the database.
It is strongly recommended to use the Service Name to connect to Oracle as it is only supported in the CDB database models.
Oracle recommends you to upgrade with necessary patches while upgrading Oracle database to 19c on the same file system to avoid issues while converting non-CDB database to CDB/PDB database.