======================================================================
Product Name	 : TIBCO iProcess(R) Engine (SQL Server)
Release Version	 : 11.9.0
Release Date	 : August 2022

======================================================================
Introduction 

TIBCO iProcess Engine provides the runtime execution
environment for business processes developed using TIBCO
Business Studio(TM), TIBCO iProcess(R) Workspace (Windows) and
other TIBCO iProcess(R) Suite components.

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

This is a full distribution set.

For detailed installation instructions, see TIBCO iProcess
Engine Installation.

===============================================================================
Affected Files for 11.9.0_HF-002
This is a full distribution set.

===============================================================================
Closed Issue in 11.9.0_HF-002

IPE-6011
The SPO/WQS process crashes intermittently on updating keys and
in the event of concurrent log-in sessions.

===============================================================================
Closed Issues in 11.9.0_HF-001

IPE-5954 (Parent Id: IPE-5891) The WQS process crashes in the
event of concurrent log-in sessions. 

IPE-5942 When iProcess Engine is upgraded from 11.7.0 to
11.9.0, on opening the EAIDB step in an existing procedure, the
Database name is incorrectly fetched as
Server name.

======================================================================
Supported Platforms

   Microsoft Windows
      10 64-bit on x86-64
   Microsoft Windows Server
      2016, 2019 64-bit on x86-64

Additional Information 

   For Windows Server, Standard Edition is the minimum edition
   supported.
   The supported platforms listed above are those that have been
   validated by TIBCO. Any subsequent service
   packs/patches/updates/fix packs for the same major version are also
   supported.
   
   ===============================================================================
   
   Additional Information
   
   Defining the Database Stored Procedure to call a ‘Process Step’
   or a ‘Withdraw Step’ can be categorized with respect to
   populating the Stored Procedure drop-down as follows:
   
   1. With Server and/or Database name in input: The Stored Procedure
   drop-down populates the list of stored procedures fetched from the
   given details and in the following format.
      <SCHEMA>.<StoredProcedure> – all procedures from the given
   database and that are accessible to the foreground user are
   displayed (with schema name). The behavior is same for the new
   EAIDB step or an Edit step.
   
   2. Without Server and Database name in input: The Stored Procedure
   drop-down for new step populates the list of stored procedures
   fetched from the iProcess Engine’s database and in the following 
      formatted lists.
   
      a) <SCHEMA>.<StoredProcedure> – stored procedures from the
   non-default schema of the foreground user (all other schemas from
   the iProcess Engine database, other than your default schema) are
   displayed with the schema name.
      b) <StoredProcedure> – stored procedures from the default
   schema of the foreground user are displayed without schema name.
   There is a process attribute to suppress this behavior. For
   example, in the event when you want to view the procedures from
   default schema along with schema name.
      The 'DEF_SCHEMA_PROCS_FORMAT' process attribute controls the
   display format of the stored procedures from default schema. This
   attribute has no effect 
      on the stored procedures 'point a' display.   
      The role or behavior of process attribute value is described as
   follows:
      1 - displays the stored procedures from default schema in the
   <StoredProcedure> format
      2 - displays the stored procedures from default schema in the
   <SCHEMA>.<StoredProcedure> format   0 or not set – behaves the
   same as 1
      Note: This is applicable only to 'point b'.
    
      Edit has a different behavior occasionally as the Stored
   Procedure drop-down can be populated from two paths:
      a. When the dialog is loaded after clicking the new step:
      The drop-down list format matches with the already configured
   procedure name to retain the designed format and respect your
   original intention. 
      The 'DEF_SCHEMA_PROCS_FORMAT' process attribute has no effect on
   the step initial load.
   
      b. When ‘Refresh’ is clicked: The drop-down list format
   matches with the already configured procedure name. You have an
   option to override this behavior by setting the 
      'DEF_SCHEMA_PROCS_FORMAT' process attribute. The role or
   behavior of process attribute value is described as follows:
      1 - displays the stored procedures from default schema in the 
   <StoredProcedure> format
      2 - displays the stored procedures from default schema in the 
   <SCHEMA>.<StoredProcedure> format
      0 or not set – displays the stored procedures in the format of
   the already configured procedure name.
      Note: 
         a) Overriding the behavior might result in procedure name
   mismatch error that was configured earlier, and is expected if you
   intend to modify the
      procedure name or the associated parameters.  
      b) To view optional parameters in store procedure EAIDB step
   correctly, you must provide the 'View Definition' permissions to
   the stored 
      procedure. This is applicable only if you connect to an external
   database or server.
    From the 11.9.0 version, '@' is removed from the parameter name.
   For all the previous versions, steps are auto-migrated for display
   and a permanent change is applied on the step's first edit.

======================================================================
Supported Third-party Software

   Application Server
     Apache Tomcat 8.5.53, 8.5.x
     IBM WebSphere Application Server 8.5.5.11 (As a JMS Provider)
     JBoss Enterprise Application Platform 6.4.0, 7.0.0
       6.4.0 - As a JMS Provider
       7.0.0 - As a JMS Provider
     Oracle WebLogic Server 12.1.3, 12.2.1, 14.1.1
       12.1.3 - As a JMS Provider
       12.2.1 - As a JMS Provider

   Database
     Azure SQL Database V12
     Microsoft SQL Server 2016, 2017, 2019

   Development Tool
     Oracle Java Development Kit 11, 11.0.x
     Oracle Java Runtime Environment 11.0.x

   Web Browser
     Google Chrome 76.0.x, 99.0.x
     Microsoft Edge Windows 10
     Microsoft Internet Explorer 11.0.x
     Mozilla Firefox 69.0.x, 98.0.x

======================================================================
Minimum Software Requirements

   Third-party Software:
     Microsoft SQL Server 2016
     POSIX Pthread Library 2.7.0
       32-bit - Only required on Windows Platforms
     Pthreads-win32 2.9.1
       64-bit - Only required on Windows Platforms

======================================================================
TIBCO Product Compatibilities

   TIBCO ActiveMatrix BusinessWorks(TM) 5.13.2 - 5.15.0
   TIBCO Business Studio(TM) - BPM Edition 3.5.2
   TIBCO Business Studio(TM) iProcess(R) Add-in 3.5.1
   TIBCO Enterprise Message Service(TM) 8.5.0 - 10.1.0
   TIBCO Hawk(R) 6.0.0 - 6.2.x
   TIBCO Rendezvous(R) 8.4.6 - 8.5.2
   TIBCO Runtime Agent(TM) 5.11.1 - 5.12.0
   TIBCO iProcess(R) Server Objects (.Net) 11.9.0 and above
   TIBCO iProcess(R) Server Objects (Java) 11.9.0 and above
   TIBCO iProcess(R) Technology Plug-ins 11.8.0 - 11.8.x
   TIBCO iProcess(R) Workspace (Browser) 11.9.0 and above
   TIBCO iProcess(R) Workspace (Windows) 11.9.0 - 11.9.x
   TIBCO iProcess(R) Workspace Lite 1.2.0 and above

======================================================================
Encoding Support

   Refer to TIBCO iProcess Engine Installation.

======================================================================
Product-Specific Information 

Only 64-bit executables are provided.

If you are using TIBCO iProcess Engine (SQL Server) on a
Windows platform, please ensure you MUST download the latest
version of pthread.dll using the download link provided with
TIBCO iProcess Engine 11.8.0 and install it as directed in the
installation guide BEFORE installation or upgrade to ensure it
works.

======================================================================
Documentation

Documentation for this and other TIBCO products is available on
the TIBCO Documentation site. This site is updated more
frequently than any documentation that might be included with
the product. To ensure that you are accessing the latest
available help topics, visit: https://docs.tibco.com.

======================================================================
TIBCO Product Support

You can contact TIBCO Support in the following ways:

  For an overview of TIBCO Support, visit
  http://www.tibco.com/services/support.

  To access the Support Knowledge Base and getting personalized
  content about products you are interested in, visit the TIBCO
  Support portal at https://support.tibco.com.

  To create a Support case, you must have a valid maintenance
  or support contract with TIBCO. You also need a user name and
  password to log in to https://support.tibco.com. If you do not
  have a user name, you can request one by clicking Register on
  the website.

======================================================================
Copyright (c) 2022. Cloud Software Group, Inc. All Rights Reserved.



