Академический Документы
Профессиональный Документы
Культура Документы
R19
No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.
No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.
Document history
Author Version Date Details
Angalappan 1.0 25-Apr-2019 Added EDGE,IRIS and RP defects and
enhancement details
3
Browser and Interaction Framework Release Notes
1 Introduction
This document details the new changes that are included in the current Browser release &
all the components released along with that IRIS and its dependant components like RP &
T24 Adapter
1.2 Dependencies:
For this release to work, the following components must be present.
Name Version Packaged in this
release?
</t24CatalogServiceVersion> </t24CatalogServiceVersion>
<tComponentFrameworkVersion> <tComponentFrameworkVersion>
4
Browser and Interaction Framework Release Notes
OLD_VERSION 19.12.0
</tComponentFrameworkVersion> </tComponentFrameworkVersion>
2.2 Defects
2.2.1 Client Defects
RTC ID Description Solution Description
N/A
N/A
N/A
5
Browser and Interaction Framework Release Notes
3.2 Enhancements
N/A
3.3 Defects
3.3.1 Client Defects
RTC ID Problem Description Solution Description
N/A
N/A
N/A
6
Browser and Interaction Framework Release Notes
4 EDGE
4.1 Enhancements
RTC ID Summary Description
N/A
4.2 Defects
4.2.1 Client Defects
RTC ID Problem Description Solution Description
N/A
N/A
N/A
5 Configuration Required
The other files are ancillary and provided for clients who would have already made their 1st
generation. Thereafter maintain the files themselves.
7
Browser and Interaction Framework Release Notes
=================
Browser.war login screen made a direct connection to T24 via JDBC, it bypassed IRIS completely
because IRIS is not capable of authentication.
This is (was) only meant to be temporary until we switched to use remote authentication.
The other limitation to the old method was that Browser.war had to be run on the same server
asT24, also not ideal for security.
================
We now run Authenticator.war on the same server as T24 and IRIS, but we run Browser.war in a
DMZ, a safer way to split the applications.
For Browser.war to authenticate, it will make a connection to Authenticator.war to get past the login
screen. Once authenticated, the communication is then directly to IRIS.war
For testing, we run all war files on the same server. The new behaviour is still required
,e.g Browser.war uses Authenticator.war to login, then IRIS.war takes over. Browser.war never
makes connection to T24 directly.
=================================
The new way is checked into master and all branches derived from master will behave in the new
way (e.g 201708, 201710, R17)
Configuration changes
==================
We removed override.IRIS_ROOT from the webserver startup so that the one in Browser.dsf is used
instead
8
Browser and Interaction Framework Release Notes
The default context-root for Browser.war is "Browser" and to deploy the Browser.war under a
different context-root, we would need to do the below step based on the application server it’s
getting deployed.
Please note that, we had to rename the Browser.dsf and Browser.ifp to the new context-root name
with the previous releases but it’s not needed anymore and so changing the <context-root> in xml
would be enough to deploy the Browser.war in a different name
Timeout configuration can been done by setting a value for “methodTimeOut” attribute in
"resourceProviderServiceContext.xml" which is part of runtime properties.The suggested time is to
be any value lesser than DB timeout value in seconds.
Eg:
<bean id="RuntimeProperties" class="com.temenos.soa.services.RuntimeProperties">
<constructor-arg>
<map>
</map>
</constructor-arg>
</bean>
9
Browser and Interaction Framework Release Notes
The below mentioned parameter will minify & bundle the JavaScript & css files and it is disabled by
default in the browser.dsf, which is available under the path Browser.war/WEB-INF/Browser.dsf. For
minify & bundling version of browser, kindly set the below parameter to 'Y'
-Dbrowser.options.forceUpdateOfLastLoginTimestamp=Y
The menuroot.properties file will be created like menuroot_XXX.properties file where XXX is the
folder on which code is generated.(e.g menuroot_core.properties , Menuroot_L3.properties).Hence
merging the properties file is not required and can place both the files in the same path since they
are in the different name.
The below JVM argument which was suggested earlier to launch pop up window from command line
is no longer required as new icon for is provided near command line for the same . So kindly remove
them.
-DENABLE_COMMAND_LINE_POPUP=Y
Please add / update below mentioned Java system property in the invocation of the JVM for the
server where UXP Browser web application is deployed. This will disable INFO,DEBUG,WARN logs.
-DedgeSystemPropertyUpdaters=com.temenos.connect.system.BRPProductionProperties
10
Browser and Interaction Framework Release Notes
If above mentioned java system property is used, please remove any use of java system
property –Dlog.off as it’s not required in production.
IRIS:
PFB the attached sample iris configuration to stop appending logs in standard out.
logback.xml jboss-deployment-str
ucture.xml
Patch path:
browser-iris.war\WEB-INF\classes\logback.xml
browser-iris.war\WEB-INF\jboss-deployment-structure.xml (only in JBoss)
11
Browser and Interaction Framework Release Notes
–Dbrowser.options.max.dropdown.results = <value>
IGNORE.RESOURCE.STARTSWITH=<value>
OR
IGNORE.RESOURCE.ENDSWITH=<value>
12