TIBCO iProcess(R) Engine (SQL) 11.8.0 HotFix 006 is available

TIBCO iProcess(R) Engine (SQL) 11.8.0 HotFix 006 is available

book

Article ID: KB0101315

calendar_today

Updated On:

Products Versions
TIBCO iProcess Engine (SQL) 11.8.0

Description

This is a full distribution set.

 For detailed installation instructions, see TIBCO iProcess Engine Installation for Windows.
 
================================================================================
Affected Files for 11.8.0_HF-006 (This Release)

 This is a full distribution set.
    
================================================================================
Closed Issue in 11.8.0_HF-006 (This Release)

  Defect Id: IPE-5434
 
  iProcess Objects Server crashes when getting subcase audit message, while installing iProcess Engine on Windows platform.

  Corrected.

  Defect Id: IPE-5296
 
  iProcess Objects Server crashes and dump files are created when JUMPTO operation is performed between sub procedure and main procedure.

  Corrected.

  Defect Id: IPE-5295
 
  iProcess Objects Server crashes and dump files are created when case history is viewed.

  Corrected.

  Defect Id: IPE-5294
 
  iProcess Objects Server crashes and dump files are created when a participant is removed.

  Corrected.

================================================================================
Closed Issue in 11.8.0_HF-005

  Defect Id: IPE-5404
 
  Windows Slave upgrade generates response file with incorrect entry.

  Corrected.

  Defect Id: IPE-5403
 
  iProcess Engine Schema-only upgrade is either unavailable, or fails.

  Corrected.

  Defect Id: IPE-5402
 
  Windows Slave iProcess Engine upgrade creates 64-bit DSN. But the DSN Configuration is changed to Integrated Windows Authentication.
        
Corrected.

================================================================================
Closed Issue in 11.8.0_HF-004

Defect Id: IPE-5396

The  cache procedure for the iProcess Objects Server fails with multiple errors due to Composite field.

Corrected.

================================================================================
Closed Issue in 11.8.0_HF-003

Defect Id: IPE-5375

When loading some imported procedure definitions, iProcess Objects Server crash.

Corrected.

================================================================================
Closed Issue in 11.8.0_HF-002

Defect Id: IPE-5330 (Parent IPE-5277)

IAPJMS to connect with EMS over SSL.
        
Corrected.

Note: If you need to configure SSL for EMS connection then, follow the below mentioned steps.

    a. Back up the following existing files to a safe location that should be outside of the $SWDIR directory:
    - $SWDIR/etc/iapjms.properties
    - $SWDIR/etc/iapjms_classpath.properties

    b. Update $SWDIR/etc/iapjms.properties file - add entries required to enable SSL.
    
        Following is the FULL list of properties that are supported by IAPJMS for connecting EMS over SSL:
        
        IAPJMSConnect.SecurityProtocol                    
        IAPJMSConnect.SSLEnableVerifyHost                    
        IAPJMSConnect.SSLEnableVerifyHostName                            IAPJMSConnect.SSLExpectedHostName                    
        IAPJMSConnect.SSLTrustedCertificates                    
        IAPJMSConnect.SSLIdentity                    
        IAPJMSConnect.SSLPassword                    
        IAPJMSConnect.SSLTrace                    
        IAPJMSConnect.SSLDebugTrace                    
        IAPJMSConnect.SSLVendor                    
        IAPJMSConnect.SSLAuthOnly                    
        IAPJMSConnect.SSLPrivateKey                    
        IAPJMSConnect.SSLPrivateKeyEncoding                    
        IAPJMSConnect.SSLIdentityEncoding                    
        IAPJMSConnect.SSLIssuerCertificates                    
        IAPJMSConnect.SSLCipherSuites                    
        IAPJMSConnect.SSLHostNameVerifier
        
        Here is an example of an EMS over SSL enabled iapjms.properties file:
        
        IAPJMSConnect.InitialContextFactory=com.tibco.tibjms.naming.TibjmsInitialContextFactory
        IAPJMSConnect.InitialURL=tibjmsnaming://ems-host:7243
        IAPJMSConnect.TopicConnectionFactory=SSLTopicConnectionFactory                    
        IAPJMSConnect.SecurityPrinciple=NR                    
        IAPJMSConnect.SecurityCredentials=NR                    
        IAPJMSConnect.SecurityEncryption=PLAIN                    
        IAPJMSConnect.Persistent=Y                    
        IAPJMSConnect.Priority=4                    
        IAPJMSConnect.TimeToLive=0                    
        IAPJMSConnect.SecurityProtocol=ssl                    
        IAPJMSConnect.SSLEnableVerifyHost=true                            IAPJMSConnect.SSLEnableVerifyHostName=true                    
        IAPJMSConnect.SSLExpectedHostName=server
        IAPJMSConnect.SSLTrustedCertificates=/swserver/EMS/certs/server_root.cert.pem
            IAPJMSConnect.SSLIdentity=/swserver/EMS/certs/client_identity.p12                    
        IAPJMSConnect.SSLPassword=<encrypted password>                   
        IAPJMSConnect.SSLTrace=true
    
    c. Update $SWDIR/etc/iapjms_classpath.properties file. (This step is applicable for EMS version 8.3 or below. This step is required only for applicable versions of EMS. Eg., tibcrypt.jar, slf4j-simple-1.5.2.jar,slf4j-api-1.5.2.jar are not available from EMS 8.4.)
          
        - Copy the slf4j related jars from EMS installation host to the <classpath.basedir.ems> location on IPE host.
        - Append slf4j jars to <classpath.ems.1> property.
        
        Here is an example iapjms_classpath.properties file :
        
        classpath.basedir.ems=/swserver/EMS/libs
        classpath.ems.1=jms-2.0.jar,tibjms.jar,tibjmsadmin.jar,tibcrypt.jar,slf4j-simple-1.5.2.jar,slf4j-api-1.5.2.jar
        
        
    d. If step #b requires <IAPJMSConnect.SSLPassword> property, run swconfig tool to generate and set encrypted password to <IAPJMSConnect.SSLPassword>, that directly updates in $SWDIR/etc/iapjms.properties file.
        swconfig -s


================================================================================
Closed Issue in 11.8.0_HF-001

  Defect Id: IPE-5347
 
  Issue in creating 64-bit ODBC with Integrated Windows authentication, while installing iProcess Engine.

  Corrected.

  Defect Id: IPE-5346
 
  In silent upgrade, Node_Cluster table is not updated with Cluster Name.

  Corrected.

  Defect Id: IPE-5333
 
  iPE Installer crashes while getting the cluster machine name during the upgrade, irrespective of the number of nodes when run on the Windows Cluster.

  Corrected.

Environment

This hotfix applies to TIBCO iProcess Engine 11.8.0 running on the following platforms and databases: Platforms: Microsoft Windows 10 64-bit on x86-64 Microsoft Windows Server 2016, 2019 64-bit on x86-64 Supported Databases Microsoft SQL Server 2016, 2017, 2019

Resolution

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.8.0/hotfix006

Issue/Introduction

TIBCO iProcess(R) Engine (SQL) 11.8.0 HotFix 006 is available

Additional Information

TIB_ipe-sql_11.8.0_HF006_readme.txt