===============================================================================
Product Name   : TIBCO iProcess(R) Engine (Oracle)
Release Version: 11.9.0_HF‐006
Release Date   : April 2024    

===============================================================================
Installation

1. Shut down TIBCO iProcess Engine.

2. Copy the following files from the given package to the following
   paths and leaving the permissions and ownership as they are.
   - $SWDIR/libs/libdbrun_11_9_0_6.ear
   - $SWDIR/libs/liborarun_11_9_0_6.ear
   - $SWDIR/util/swadm

3. Source the iProcess Engine environment and run below commands:
   sweaireg UNREG EAIDB -y
   sweaireg UNREG EAIORA -y
   sweaireg REG EAIDB -l $SWDIR/libs/libdbrun_11_9_0_6.ear
   sweaireg REG EAIORA -l $SWDIR/libs/liborarun_11_9_0_6.ear
   fixperms -R $SWDIR/libs

4. Edit the existing $SWDIR/swdefs line 1 to i11.9-o(0.6).

5. Restart TIBCO iProcess Engine.
 
===============================================================================
Affected Files for 11.9.0_HF‐006 (This Release)
- libdbrun_11_9_0_6.ear
- liborarun_11_9_0_6.ear
- swadm

===============================================================================
Closed Issue in 11.9.0_HF‐006 (This Release)

IPE-6431
EAIDB Ora wrongly interprets package name as database name.

IPE-6465
EAI DB Step Plugin Error with remote database not found.

===============================================================================
Additional Information

This fix effectively operates with TIBCO iProcess(R) Workspace (Windows)
11.9.0.6 and subsequent versions.

When configuring EAIDB step for a local database server, either leave the
Server field empty or set it to local Database Name (v$database value of
iProcess Engine DB, not TNS identifier nor Oracle SID). For a remote
database, use the remote DBLink name configured on the iProcess Engine
database.

With this fix, there is a provision to list procedures from multiple
schemas, but the Database field can only take a single schema (do not
enter comma-separated value as it leads to run-time failure), and the
extended list of schemas can be configured using below EAIDB_PROCS_SCHEMAS
process attribute.

The Stored Procedure drop-down for EAIDB step is displayed with the list
of Stored Procedures fetched from iProcess Engine schemas (SWUSER, SWPRO)
and list of schemas configured in  EAIDB_PROCS_SCHEMAS process attribute.
The stored procedure names are displayed in the following formats:

- <PackageName>.<StoredProcedure>: stored procedures from all packages.
  The stored procedure name is prefixed with packagename when
  displayed in the drop-down. DEF_SCHEMA_PROCS_FORMAT process attribute has
  no effect on this display.

- <StoredProcedure>: all stored procedures from given schemas. The
  procedure name does not display owner name in the drop-down unless
  the behavior is modified by DEF_SCHEMA_PROCS_FORMAT process attribute.
    
Two new process attributes have been introduced with this fix. These
attributes are applicable to design-time EAIDB step:

- DEF_SCHEMA_PROCS_FORMAT - To control the display format of the
  stored procedure names. Valid values are 0, 1 and 2.
- EAIDB_PROCS_SCHEMAS - To add additional schema names for procedure
  lookup. Valid Format : <schema>[,<schema>][,<schema@dblink>]...

Defining the Database Stored Procedure to call a ‘Process Step’ or
a ‘Withdraw Step’ can be categorized into:

1. New Step:

    The DEF_SCHEMA_PROCS_FORMAT process attribute can override the behavior
    of Procedure drop-down as follows:

    1 - displays the stored procedures in <StoredProcedure> format
    2 - displays the stored procedures in <Owner>.<StoredProcedure> format
    0 or not set – behaves the same as 1

2. Edit Step:

    The Edit Step has a different behavior depending on the action, the
    drop-down can be populated from two paths:

    a. When the dialog is loaded after clicking on ‘Edit’ step.    
       The drop-down list format matches the already configured Procedure
       Name. This is mainly to retain the designed format and respect
       the original intention of the user.
       
       Process Attribute 'DEF_SCHEMA_PROCS_FORMAT' has no effect on step
       initial load.

    b. When ‘Refresh’ is clicked.
       The drop-down list format matches the already configured
       Procedure Name. Here, user has an option to override this
       behavior by setting process attribute 'DEF_SCHEMA_PROCS_FORMAT'.  

The DEF_SCHEMA_PROCS_FORMAT process attribute can override
the behavior of the Stored Procedure drop-down as follows:

1 - displays the stored procedures in <StoredProcedure> format
2 - displays the stored procedures in <Owner>.<StoredProcedure> format
0 or not set – displays the stored procedures in the format of the
    already configured Procedure Name.

NOTE: The DEF_SCHEMA_PROCS_FORMAT process attribute gives the
flexibility of overriding the default format of the Procedure
Name drop-down, which is needed for backward compatibility with
existing iProcess Procedures. However, we recommend that you use
it cautiously. Otherwise, it may lead to design-time and/or
run-time failures.

TIBCO iProcess(R) Engine (Oracle) 11.9.0 HotFix 006 is available

This hotfix applies to TIBCO iProcess Engine 11.9.0 and above running on the following platforms and databases: Supported Platforms CentOS 7.6, 7.x, and 8.0 64-bit on x86-64 Oracle Linux 7.6, 7.x, 8.0, and 8.x 64-bit on x86-64 Red Hat Enterprise Linux Server 7.6, 7.x, 8.0, and 8.x 64-bit on x86-64 SUSE Linux Enterprise Server 12 SP2, 12.x, 15, and 15.x 64-bit on x86-64 Databases Oracle Database 12c 12.2.x (Oracle Client must be 19c) Oracle Database 18c 18.x (Oracle Client must be 19c) Oracle Database 19c 19.x (Oracle Client must be 19c) Oracle on Amazon RDS

The hotfix can be downloaded from the TIBCO Support Customer Portal Web UI,
using your username and password for the TIBCO Support Web.

Once logged on the hotfix can be found under the Downloads Menu:
AvailableDownloads/iProcess/engine/11.9.0/hotfix006

TIB_ipe-oracle_11.9.0_HF-006_readme.txt