Known Issues in Quantum Fabric V9 SP1

Installer

• Issue

  Advanced push notifications are blocked for the combination of a JBoss app server and an Oracle database.

  Workaround

  Add the ojdbc8.jar file to the kpns/war/libs directory, and then restart the server.

• Issue

  While the execution of a Service Task in a Workflow Service, the service task fails with the following error:

  com.kony.component.service.common.ServiceComponentException: Service call unsuccessful. Possible input parameter mismatch in service configuration : Property access failed in MVEL script causing exception [Error: could not access property (firstName) in: java.lang.String].

  Workaround

  To avoid this issue, perform the following step:

  1. Navigate to the installed application server folder and open the system file.

     For example,

     • For Tomcat
       • Windows : catalina.bat
       • Linux: catalina.sh
     • For JBoss
       • Linux: standalone.sh
       •  Windows: standalone.bat
     • For JBoss Multinode
       • domain.sh
     • For WebSphere Liberty
       • jvm.options
  2. Add the mvel2.compiler.allow_override_all_prophandling=true as follows:

     -D property. (-Dmvel2.compiler.allow_override_all_prophandling=true )

  3. Restart the application server.

• Issue

  On certain system display resolutions, the Windows Installer UI may get distorted and you may face difficulties in proceeding with the installation.

  Workaround

  You must lower the scaling factor and/or resolution of your system and restart the installer.

• Issue

  Upgrading a Fabric installation on WebSphere Basic profile to IBM Liberty profile is currently unsupported.

• Issue

  Upgrade from 8.2.1.3 GA to V9.x gets reverted.

  Workaround

  Before the upgrade, execute the following SQL statement from admin database

  For MySQL
  ------------ delete from <admindb>.schema_version where script = 'V62.1__konyadmin-mysql-8.2.0.0.sql';
  
  For SQLServer
  --------------- delete from <admindb>.schema_version where script = 'V62.1__konyadmin-sqlserver-8.2.0.0.sql';
  
  For Oracle ---------- delete from <admindb>.schema_version where script = 'V62.1__konyadmin-oracle-8.2.0.0.sql';
  

• Issue: While upgrading from MobileFabric 7.3 to Quantum Fabric V9 and then upgrading to a version after V9, the upgrade fails due to the following error:"java.sql.SQLSyntaxErrorException: Table 'prefixidglobaldbsuffix.schema_version' doesn't exist".

  Workaround

  To avoid this issue, perform the following step:

  • Delete the idglobaldb schema before upgrading to the version later than V9.

 

• Issue: When you setup Quantum Fabric (On-Premises) on WebSphere Liberty Profile using the Command Line Installer (CLI) the publish of the Storage application fails. The failure occurs when you enter the database type input in upper or mixed casing. The storage database type is a case-sensitive field which accepts only lowercase inputs. For example: oracle, mysql, mssql and mariadb.

  Workaround

  Change the database name in the following sets of schemas and tables:

  • Schema: ADMINDB

    Table: SERVER_CONFIGURATION

    Field / value: storage_database_type = oracle / mysql / mssql / mariadb

  • Schema: ACCOUNTS

    Table: FEATURES

    Field / value: {"storagedatabasetype":"oracle / mysql / mssql / mariadb","serverdatabasetype":"oracle / mysql / mssql / mariadb"}

• Issue: The publishing of a Storage application fails on an environment that uses the SQLServer with Windows authentication.

  Workaround

  In the server_configuration table of the Integration database(admindb) insert the key KONY_SERVER_IS_WINDOWS_AUTHENTICATION_ENABLED with value set to true. Restart the application server.

• Issue: While upgrading Identity from MobileFabric 7.0/7.1 to Quantum Fabric V9.x with the selected database as MSSQL, the upgrade fails due to the following errors that occur due to the Flyway tool version upgraded from 3.x to 4.x:

  • Failed to DROP INDEX "<auth_schema>"."schema_version_ir_idx"
  • Failed to DROP INDEX "<auth_schema>"."schema_version_vr_idx"

  Workaround

  To avoid this issue, perform the following steps:

  Remove the version_rank column from the schema_version table in the authglobaldb by following queries before the upgrade.

  DROP INDEX schema_version_ir_idx ON dbo.schema_version
  GO
  DROP INDEX schema_version_vr_idx ON dbo.schema_version
  GO
  ALTER TABLE dbo.schema_version DROP CONSTRAINT schema_version_pk
  GO
  ALTER TABLE dbo.schema_version DROP COLUMN version_rank
  GO
  ALTER TABLE dbo.schema_version ADD CONSTRAINT schema_version_pk PRIMARY KEY CLUSTERED (installed_rank)
  GO
  ALTER TABLE dbo.schema_version ALTER COLUMN version nvarchar(50) NULL
  GO