You are on page 1of 20

Upgrade Guide

SAP Liquidity Management for


Banking 6.2 (LMS 6.2)
LAST REVISED: Jun, 2017

Copyright © 2005-2017 SAP SE

All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software compon-
ents of other software vendors. National product specifications may vary.

These materials are provided by SAP SE and its affiliated companies (“SAP Group”) for informational
purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for er-
rors or omissions with respect to the materials. The only warranties for SAP Group products and ser-
vices are those that are set forth in the express warranty statements accompanying such products and ser-
vices, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or re-
gistered trademarks of SAP SE in Germany and other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trade-


mark information and notices.

Disclaimer

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and


notices.

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/


Table of Contents
Introduction .............................................................................................................. iv
1. Before You Start ...................................................................................................... 1
2. New Features (LMS 6.1 to LMS 6.2 and 6.2.1 to 6.2.2) ................................................... 2
2.1. Adapter changes ............................................................................................ 2
2.2. Changes to user authentication ......................................................................... 2
2.3. New LMS Runtime Application ....................................................................... 2
2.4. .template and master.conf changes .................................................................... 2
2.5. Oracle and SAP® IQ upgrade script .................................................................. 2
2.6. Changes to rh-context-lists .............................................................................. 3
2.7. Data restrictions ............................................................................................ 3
2.8. Miscellaneous ............................................................................................... 4
3. New Features (LMS 6.2.2 to LMS 6.2.3 and LMS 6.2.3 to LMS 6.2.4) .............................. 5
3.1. New Queues and Adaptors .............................................................................. 5
3.2. ISO20022 camt.053 message parsing ................................................................ 5
3.3. RTAI ISO 20022 Message .............................................................................. 5
3.4. Support for LJS 1.1.16 ................................................................................... 5
3.5. Oracle and SAP® IQ upgrade script .................................................................. 5
4. New Features for LMS 6.2.4 to LMS 6.2.5 ................................................................... 7
4.1. New Queues and an Adaptor ........................................................................... 7
4.2. Oracle and SAP® IQ upgrade script .................................................................. 7
4.3. UTC Time Zone ............................................................................................ 7
4.4. Running the Update Scripts ............................................................................. 7
4.5. Master.Conf ................................................................................................. 7
4.6. Uncommitted Credit Limit .............................................................................. 7
4.7. Database Restrictions ..................................................................................... 7
5. New Features for LMS 6.2.5 to LMS 6.2.6 ................................................................... 9
5.1. Removed Queue ............................................................................................ 9
5.2. Change in configurations from 6.2 SP 05 to 6.2 SP 06 .......................................... 9
5.2.1. Change in base configuration ................................................................ 9
5.2.2. Change in Alerter configuration ........................................................... 11
5.2.3. Change in Balance Transfer ................................................................ 13
5.2.4. Change in Purge configuration ............................................................ 13
5.2.5. Change related to Release Handler ....................................................... 14
5.2.6. Change configuration for adpt_Preprocessor .......................................... 15
5.2.7. Static configuration for new UI ........................................................... 15
5.3. Oracle upgrade script ................................................................................... 15

iii
Introduction
Note
The LMS product has been restructured under the new name of SAP Liquidity Management for
Banking where two optional add-ons are available: SAP Payment Flow Control and SAP Col-
lateral Management.

In following SAP Liquidity Management for Banking and LMS will be used as synonyms.

This guide covers the upgrade from LMS 6.1 onwards to LMS 6.2.4

There were some important changes between those two releases, and we invite you to familiarize your-
self with those changes by reading the Release Notes.

Please also familiarize yourself with the installation instructions.

Should you decide to implement any new functionality, we recommend that this is treated as a separate
task or project from the upgrade itself. After a successful installation, your previous configuration con-
verted into the modified database schema should work as it did previously. Positions shown by the sys-
tem should not change, other than what is dependent on time stamps, for example Position Freeze in-
formation.

iv
Chapter 1. Before You Start
1. Review carefully the new installation guide. There are some important changes in the procedures
compared to the previous releases. Even if you have installed the system many times you must go
through this document carefully.

2. Always start from a fresh full installation. It may be tempting to install a new release on top of a
working installation, or if you hit a difficulty to revert to a previous version of a component or con-
figuration file. Do not do this.

3. Never mix components and configuration files between releases. If you hit a problem, do not at-
tempt to work around it by using older component versions, even if they appear to work correctly,
but contact SAP support for help.

4. It is recommended to backup the files given below before you start the upgrade.

• The file master.conf from <Install_Base>/lms_services.

• The file lms.properties from <Install_Base>/applicationserver/webapps/


LMS-CFM-PFC-CMM-oracle/WEB-INF for Oracle database and the file
<Install_Base>/applicationserver/webapps/LMS-CFM-PFC-CMM/WEB-INF
for HANA database.

Additional files and a folder to be backed up where AD FS configuration based authentication is de-
ployed.

• The file default-server.xml from


<Install_Base>/applicationserver/config_master/org.eclipse.gemini
.web.tomcat

• The file java.login.config from


<Install_Base>/applicationserver/configuration/
com.sap.security.auth.service

• The folder com.sap.security.sam12.cfg from


<Install_Base>/applicationserver/config_master

5. Make sure your fresh installation works correctly and satisfy yourself that you understand the in-
stallation before moving on to the upgrade process itself and reapplying any customization.

6. We also recommend that you recreate from scratch the keystores used by the application.

7. While in previous releases we offered deployment of ASP and LMS backend code on Solaris, this
option is no longer available and these components can only be deployed on RedHat Linux 5.7™ or
later

8. This does not affect where external components such as WebSphere MQ and Oracle are deployed.

1
Chapter 2. New Features (LMS 6.1 to LMS 6.2 and 6.2.1
to 6.2.2)
2.1. Adapter changes

Now LMS makes use of the SAP® ESP distribution of OpenAdaptor and only contains some LMS spe-
cific components, such as SWIFT parsers. This means that if you have customized adapters the config-
uration will need adjusting to reference the ESP OpenAdaptor distribution.

SAP® ESP OpenAdaptor must be downloaded from SAP service market place. This distribution also
uses SAP license control module, so make sure you also download this license.

Note
There should be no reason to modify the configuration of LMS internal adapters, other then
what is done by the updateconfig.sh script. Configuration that requires modification
should only be linked to adapters at the LMS boundary (receiving or sending messages to other
systems within the Bank).

2.2. Changes to user authentication

From this version we replace NTLM based authentication by SAML V2.0 authentication. While we sup-
ply a test Identity Provider, it is not intended for production use and you must use such a provider as part
of the Bank secure infrastructure.

If the user id returned by the Identity provider is different from the one returned by previous authentica-
tion mechanism you will need to update the operator file with these new ids.

2.3. New LMS Runtime Application

LMS now runs on its dedicated LMS Application Runtime to replace Tomcat and WAS. The LMS Ap-
plication Runtime as well as the SAP JVM are fully supported by SAP. This change may require adapta-
tions on monitoring scripts (in particular log monitoring) and any automated startup and shutdown
scripts. This server is the only deployment server supported for LMS.

We also advise you to compare the lms.properties with the newly delivered
lms.properties.template, as some custom properties can be directly maintained in this file
rather than by the updateconfig.sh script.

2.4. .template and master.conf changes

Note
Please refer to installation guide for precisions on master.conf and template files.

New parameters were added and old parameters were removed from master.conf.

For this reason, we recommend that you only use the previous releases of master.conf purely as a
reference and follow the installation procedure for a new system as per Installation Guide.

If you have created customized versions of .template files, these files need to be compared to the
newly delivered ones and adjusted as necessary. Expect the changes to be concentrated around the con-
nection properties to ESP having replaced the ASP properties.

2.5. Oracle and SAP® IQ upgrade script

2
New Features (LMS 6.1 to LMS 6.2 and 6.2.1 to 6.2.2)

Note
Please ensure that you retain a backup of the original databases for future reference after con-
version. The scripts will create tables corresponding to the new definitions, load the data from
the existing tables into the new, and as a second stage drop the tables with the old definitions
and rename the new tables to the correct schema name.

There were some changes in the Oracle schema between version 6.1 and 6.2 requiring a conversion of
the schema. SAP provides a conversion script in two parts :

• lms-v6_1-to-v6_2-oracle-upgrade.sql

• lms-v6_1-to-v6_2-oracle-upgrade-drop-working-tables.sql

There were some changes in the Oracle schema between version 6.2 SP01 and 6.2 SP02 requiring a con-
version of the schema. SAP provides a conversion script:

• lms-v6_2_1-to-v6_2_2-oracle-upgrade.sql

If you are on a version prior to 6.1 you will need to run the update scripts in sequence.

If you use LIM-IQ, you will need to execute the corresponding scripts

• lms-v6_1-to-v6_2-iq-upgrade.sql

• lms-v6_1-to-v6_2-iq-upgrade-drop-working-tables.sql

2.6. Changes to rh-context-lists

This file contains the list of channels which are processed by the release module of payment flow con-
trol (PFC).

The format of the file has changed and you will need to update it. Please refer to the LMS Administrat-
or’s Guide for information.

2.7. Data restrictions

As part of this release, SAP has conducted several security scans of LMS source code, and systematic-
ally fixed all major security risks that were identified, in conformity with SAP standards. As a con-
sequence we had to enforce some restrictions in allowed characters within some fields in the database or
screens to avoid the possibility of injecting malicious queries into the system.

Branch Disabled characters: apostrophe, quotation mark, backslash, semicolon

'"\;

Channel Id Disabled characters: apostrophe, quotation mark, backslash, semicolon

'"\;

Depository Id Disabled characters: apostrophe, quotation mark, backslash, semicolon

'"\;

3
New Features (LMS 6.1 to LMS 6.2 and 6.2.1 to 6.2.2)

Function (normally not user modified, as used in Profiles definitions) Disabled Characters: apostrophe,
quotation mark, backslash, semicolon

'"\;

Profile Disabled characters: apostrophe, quotation mark, backslash, semicolon

'"\;

Category (as in Channels) Disabled Characters: apostrophe, quotation mark, semicolon, whitespaces

'";

Transaction Id could contain the following alphanumeric characters: Letters a-z and A-Z, numerals 0–9,
backward slash (\), forward slash (/), hyphen(-), asterisk (*), underscore (_), pipe (|), dot (.) and colon (:)

Operator (Remote User, the user id when using the application front-end) Disabled characters: quotation
mark, semicolon

";

2.8. Miscellaneous

As was the case in previous releases, SAP does not distribute WebSphere MQ libraries or the Oracle JD-
BC driver.

The installation procedures describe the process for linking LMS to these libraries.

Note
Note that we do not advise updating the Oracle JDBC driver past version 1.4 because of differ-
ence in behavior between different versions of the driver. Please contact SAP support for de-
tails if you want to perform this upgrade.

4
Chapter 3. New Features (LMS 6.2.2 to LMS 6.2.3 and
LMS 6.2.3 to LMS 6.2.4)
3.1. New Queues and Adaptors

In order to enhance the performance of reading from queues and writing to ESP and Database, the exist-
ing queue, QUEUE_LMS_PREPROCESSOR_OUT is split into four queues and corresponding adaptors
as below. These new queues need to be available in WebSphere MQ. The queue split is also refleted in
preprocessor.conf.template and so it is advisable to review the changes if this particular con-
figuration was customized.

• QUEUE_LMS_ESP_EVENT — > To send Events data to ESP.

• QUEUE_LMS_DBMSLOAD_EVENT — > To send Events data to Database.

• QUEUE_LMS_ESP_PPTXN — > To send Transaction data to ESP.

• QUEUE_LMS_DBMSLOAD_PPTXN — > To send Transaction data to ESP.

The corresponding adaptors are :

• adpt_esp_events — > To read data from QUEUE_LMS_ESP_EVENT and write to ESP.

• adpt_dbmsload_events — > To read data from QUEUE_LMS_DBMSLOAD_EVENT and write to


Database.

• adpt_esp_transactions — > To read data from QUEUE_LMS_ESP_PPTXN and write to ESP.

• adpt_dbmsload_transactions — > To read data from QUEUE_LMS_DBMSLOAD_PPTXN and


write to Database.

3.2. ISO20022 camt.053 message parsing

New queue, QUEUE_XML_ISO20022_BALANCESshould be available in Webshere MQ for ISO20022


camt.053 message parsing functionality to work.

3.3. RTAI ISO 20022 Message

A new adaptor, adpt_isoin and a new queue, QUEUE_ISO_IN need to be available in WebSphere
MQ to support RTAI ISO 20022 message inquiry.

3.4. Support for LJS 1.1.16

LMS now support LJS 1.1.16 which is delivered along with the package. It is recommended to update
the version of LJS to a version supported by the current package.

3.5. Oracle and SAP® IQ upgrade script

Note
Please ensure that you retain a backup of the original databases for future reference after con-
version. The scripts will create tables corresponding to the new definitions, load the data from
the existing tables into the new, and as a second stage drop the tables with the old definitions

5
New Features (LMS 6.2.2 to LMS 6.2.3 and LMS 6.2.3 to LMS 6.2.4)

and rename the new tables to the correct schema name.

There were some changes in the Oracle schema between version 6.2 SP03 to 6.2 SP04 requiring a con-
version of the schema. SAP provides a conversion script in two parts :

• lms-v6_2_3-to-v6_2_4-oracle-upgrade.sql

• lms-v6_2_3-to-v6_2_4-oracle-upgrade-drop-working-tables.sql

Note

• Note that we do not advise updating the Oracle JDBC driver past version 1.4 because of difference
in behavior between different versions of the driver. Please contact SAP support for details if you
want to perform this upgrade.

• All the new queues need to be updated in master.config file before running updateconfig.sh

6
Chapter 4. New Features for LMS 6.2.4 to LMS 6.2.5
4.1. New Queues and an Adaptor

To support the functionality of purge.sh command , two new queues, QUEUE_LMS_PURGE_ESP and
QUEUE_LMS_PURGE_DB are created. To read the transactional data from these two queues , an ad-
aptor , adpt_purge is also created.

4.2. Oracle and SAP® IQ upgrade script

There were some changes in the Oracle schema between version 6.2 SP04 to 6.2 SP05 requiring a con-
version of the schema. SAP provides a conversion script in two parts :

• lms-v6_2_4 to-v6_2_5-oracle-upgrade.sql

• lms-v6_2_4 to-v6_2_5-oracle-upgrade-drop-working-tables.sql

4.3. UTC Time Zone

LMS uses the UTC time zone as the default one for sending and retrieving data from the databases. A
new property, Platform.disableUTCTimeZone property is added in
db2platform_static.properties.template ,
db2platform_dynamic-ORACLE.properties.template and
db2platform_dynamic-HANA.properties.template files. This property is set to false by
default.

4.4. Running the Update Scripts

If the LMS version that you are running is prior to 6.2.5, you need to run the update scripts in sequence.
If you use the LIM-IQ, you will need to execute the corresponding scripts:

lms-v6_2_4-to-v6_2_5-iq-upgrade.sql

lms-v6_2_4-to-v6_2-5-iq-upgrade-drop-working-tables.sql

Note
The JDBC driver for ORACLE is upgraded for LMS and now it supports the version, ojd-
bc6–11.2.0.2.0

4.5. Master.Conf

All the new queues need to be updated in the master.conf file before running the updateconfig.sh .

4.6. Uncommitted Credit Limit

If you wish to capture a balance as Uncommitted Credit Limit (UCL), please add a new balance type,
UCL in the static data of LMS.

4.7. Database Restrictions

For security reasons, some restrictions in allowed characters within the database or screens to avoid the
possibility of injecting malicious queries into the system have been enforced. The database restricted
characters are as below.

7
New Features for LMS 6.2.4 to LMS 6.2.5

colon (:), addition sign (+), subtraction (-), backward slash (\), dot (.), forward slash (/), percentage sign
(%), asterisk mark (*), less than (<), greater than (>), equal to (=), string “javascript:”, string “vbscript:”,
double quote (”), and single quote (’)

8
Chapter 5. New Features for LMS 6.2.5 to LMS 6.2.6
5.1. Removed Queue

Following queues are no more required in 6.2 SP 06 and can be removed

• QUEUE_LMS_PURGE_ESP

• QUEUE_LMS_ESP_EVENT

• QUEUE_LMS_ESP_PPTXN

• QUEUE_SWIFT_MT9XX

5.2. Change in configurations from 6.2 SP 05 to 6.2 SP 06

There are few change in the LMS configuration from 6.2 SP 05 to 6.2 SP 06 as mentioned below.

5.2.1. Change in base configuration

The base configuration – mainly technical settings – have been consolidated in sys-
tem.java.properties.template. The file system.conf.template has been removed.

The JMS/MQ settings for each LMS service are now retrieved from this file only. The settings are pre-
fixes with messageService. By default we deliver a JMS connection factory implementation for Web-
SphereMQ. All relevant settings are applied from master.conf file.

Property Name Common JMS Settings

messageService.connectionFactoryFactory JMSConnectionFactory factory; defaults to


com.aleri.dataaccess.jms.wmq.WMQConnectionFa
ctoryFactory; if you want to use your own connec-
tionFactory factory you need to implement
com.aleri.dataaccess.jms.ConnectionFactoryFactor
y

messageService.user User

messageService.password Password

messageService.credentialsFolder CredentialsFolder; without closing /; if no pass-


word specified, you must use this setting and the
corresponding keystore.jks file

messageService.reconnectInterval Reconnect Interval in seconds

messageService.reconnectAttempts Reconnect attempts

messageService.reconnectErrorCodes Vendor specific reconnect error codes

messageService.reconnectFilter Vendor specific reconnect filter implementation to


analyze error codes; defaults to
com.aleri.dataaccess.jms.wmq.WMQConnectionR
9
New Features for LMS 6.2.5 to LMS 6.2.6

Property Name Common JMS Settings

econnectFilter; if you want to use your own recon-


nectFilter you need to implement
com.aleri.dataaccess.jms.ConnectionReconnectFilt
er

messageService.batchSize Default batch size

messageService.waitInterval Wait interval between polls

Property Name WMQ specific settings

messageService.wmq.ccsid

messageService.wmq.channel

messageService.wmq.connectionNameList

messageService.wmq.pollingInterval

messageService.wmq.queueManager

messageService.wmq.receiveExit

messageService.wmq.securityExit

messageService.wmq.sendExit

messageService.wmq.sslCipherSuite

messageService.wmq.sslPeerName

The database specific settings are provided in system.java.properties.template as well.

Property Name Database Settings

database.persistenceMode Persistence mode; currently supported values are


HANA and ORACLE

database.url JDBC url

database.owner Owner

database.user User

database.password Password

10
New Features for LMS 6.2.5 to LMS 6.2.6

Property Name Database Settings

database.credentialsFolder CredentialsFolder; without closing /; if no pass-


word specified, you must use this setting and the
corresponding keystore.jks file

database.ddsEnabled Enable/Disable data dependent security

5.2.2. Change in Alerter configuration

Alerter uses properties from file alerter.properties from now on (see folder business). They are injected
using the Spring framework (ContextConfiguration). The Alerter start app has been renamed to
AlerterApplication; in order to start the app, you need to pass JVM argument -
Dlms.configuration.dir="<path to config>".

All Alerter application settings have been moved from system.java.properties.template to alert-
er.properties.template. The Alerter properties are the following:

# ---------------------------------------------------------------------
# Alerter Definition
# ---------------------------------------------------------------------
# List all alerter names configured for the system separated with
# commas. For each alerter provide its own configuration section as
# 'alerter.<alert-name>'
alerter.name = THRESHOLD, GEMH
# ---------------------------------------------------------------------
# THRESHOLD Alerter Configuration
# ---------------------------------------------------------------------
# This alerter uses the ThresholdAlerter class which is a custom
# implementation of interface 'com.sap.lms.alerter.impl.Alerter'. The
# configuration subset is 'alerter.THRESHOLD'. All properties defined
# with this prefix are specific for this alerter. You can define your
# own alerters by implementing the interface
# 'com.sap.lms.alerter.impl.Alerter'. Your custom implementation then
# needs to be assigned to the 'alerter.<name>.class' property below.
alerter.THRESHOLD.class = com.sap.lms.alerter.impl.ThresholdAlerter
# Polling interval (in milliseconds) to query the database
alerter.THRESHOLD.pollInterval = 60000
# Customer property: alert interval (in milliseconds)
# This is the interval between two alerts for a channel
alerter.THRESHOLD.alertInterval = 60000
# Customer property: maximum iterations
# Maximum number of iterations to perform
alerter.THRESHOLD.maxIterations = 1000
# Converter configuration
# This alerter uses the Map2SoapConverter class to convert data to a
# SOAP string. The following converters are available including their
# properties:
# com.sap.lms.alerter.converter.Map2SoapConverter
# showNulls (default: false)
# elementType (default: DATA)
# category
# cause
# reference
# distributionList
# com.sap.lms.alerter.converter.Map2SoapConverter

11
New Features for LMS 6.2.5 to LMS 6.2.6

# showNulls (default: false)


# elementType (default: DATA)
# category
# cause
# reference
# distributionList
# You can define your own alerter by implementing the interface
# 'com.sap.lms.alerter.converter.Converter'. The subset of all
# properties with prefix 'alerter.<name>.converter' are passed to the
# converter implementation. Your custom implementation then needs to be
# assigned to the 'alerter.<name>.converter.class' property below.
alerter.THRESHOLD.converter.class =
com.sap.lms.alerter.converter.Map2SoapConverter
alerter.THRESHOLD.converter.showNulls = true
alerter.THRESHOLD.converter.category = THRESHOLD ALERT
alerter.THRESHOLD.converter.cause = TRIGGERED
alerter.THRESHOLD.converter.reference =
alerter.THRESHOLD.converter.distributionList = [ALERTDISTRIBUTIONLIST]
# Sink configuration
# This alerter uses the JmsSink class to send messages to a JMS
# provider like WebSphere MQ. The following sinks are available
# including their properties:
# com.aleri.dataaccess.sink.ConsoleSink
# com.aleri.dataaccess.sink.FileSink
# fileName (mandatory)
# com.aleri.dataaccess.sink.JmsSink
# destination (mandatory)
# com.aleri.dataaccess.sink.LogSink
# You can define your own sink by implementing the interface
# 'com.aleri.dataaccess.sink.Sink'. The subset of all properties with
# prefix 'alerter.<name>.sink' are passed to the sink implementation.
# Your customer implementation then needs to be assigned to the
# 'alerter.<name>.sink.class' property below.
alerter.THRESHOLD.sink.class = com.aleri.dataaccess.sink.JmsSink
alerter.THRESHOLD.sink.destination = [QUEUE_LMS_ALERTS]
# ---------------------------------------------------------------------
# GEMH Alerter Configuration
# ---------------------------------------------------------------------
# This alerter uses the GenericAlerter class to produce alerts. This
# is the default class if property 'alerter.<name>.class' is not
# defined.
# Polling interval (in milliseconds) to query the database
alerter.GEMH.pollinterval = 60000
# Custom property: sql
# Query to produce alerts. Supported variables that can be used:
# - $(CURRENTRUNTIME) - datetime for the current
query in yyyy-MM-dd HH:mm:ss format
# - $(LASTRUNTIME) - datetime for the previous
query in yyyy-MM-dd HH:mm:ss format
alerter.GEMH.sql = SELECT CurrentId\, OriginalAmount\,
Currency\, ValueDateTime\, ResponsibleUnit from TransactionAlertFilter
WHERE Handler = ‘ALERT’ AND string(ProcessedDateTime) >= '$(LASTRUNTIME)'
# Converter configuration
alerter.GEMH.converter.class =
com.sap.lms.alerter.converter.Map2SoapConverter
alerter.GEMH.converter.showNulls = true
alerter.GEMH.converter.category = GEMH ALERT
alerter.GEMH.converter.cause = TRIGGERED
alerter.GEMH.converter.reference =
alerter.GEMH.converter.distributionList = [ALERTDISTRIBUTIONLIST]

12
New Features for LMS 6.2.5 to LMS 6.2.6

# Sink configuration
alerter.GEMH.sink.class = com.aleri.dataaccess.sink.FileSink
alerter.GEMH.sink.filename =
[INSTALL_BASE]/lms/output/external-msg/gemh.xml

THRESHOLD and GEMH use sample implementations. The implementation has been adjusted, the
Alerters query data from the database directly

The property alerter.name is a comma-separated list now. Don’t use multiple properties with name
alerter.name anymore.

alerter.<name>.pollinterval has been renamed to alerter.<name>.pollInterval. alert-


er.<name>.alertinterval has been renamed to alerter.<name>.alertInterval. alerter.<name>.iterations has
been renamed to alerter.<name>.maxIterations.

alerter.<name>.formatter has been renamed to alerter.<name>.converter.class. All converter specific set-


tings are now assigned to alerter.<name>.converter. shownulls has been renamed to showNulls and to to
distributionList

alerter.<name>.outputter has been renamed to alerter.<name>.sink.class. All sink specific settings are
now assigned to alerter.<name>.sink. queue has been renamed to destination

Custom Alerters can be implemented as well. You need to implement interface


com.sap.lms.alerter.impl.Alerter. The class needs to be assigned to property alerter.<your_alerter>.class.
The entire properties for your alerter are passed into the init() method. Sinks can be implemented as well
using interface com.aleri.dataaccess.sink.Sink. Default sinks are JmsSink, FileSink, ConsoleSink, and
LogSink.

The former GEMH alerter was querying data from TransactionAlertFilter stream / derived table. This
has been changed: The alerter now selects data from Transactions stream / derived table using an addi-
tional where clause Handler = ‘ALERT’. TransactionAlertFilter is not relevant anymore, references
could be removed.

5.2.3. Change in Balance Transfer

Balance Transfer uses properties from file baltran.properties (see folder business). They are injected
using the Spring framework (ContextConfiguration). The Balance Transfer start app has been renamed
to BalanceTransferApplication; in order to start the app, you need to pass JVM argument -
Dlms.configuration.dir="<path to config>". The supported application arguments are “d” to set the exe-
cution time, “o” to set the offset in seconds, “s” to set the server time, and “h” to get help.

MQ.Queue.Baltran has been renamed to baltran.output.destination. File.Output.Baltran has been re-


named to baltran.output.filename

In addition, the property baltran.input.destination has been added. Instead of querying ESP, this queue is
used to schedule balance transfers. This requires a new queue (see master.conf
QUEUE_LMS_BALTRAN_INPUT).

Messages in the input destination queue must carry the ALERI_OPS attribute in order to be able to dis-
tinguish between inserted, rescheduled, or canceled balance transfers.

5.2.4. Change in Purge configuration

Purge uses properties from file system.java.properties from now on. They are injected using the Spring
framework (ContextConfiguration). The Purge start app has been renamed to PurgeApplication; in order
to start the app, you need to pass JVM argument -Dlms.configuration.dir="<path to config>". The sup-
ported application arguments are “t” to set the query tag name (for partitioning), and “m” to set the

13
New Features for LMS 6.2.5 to LMS 6.2.6

mode explicitly to Purge.

All Purge application settings have been moved from system.conf.template to sys-
tem.java.properties.template. The Purge properties are the following:

# ---------------------------------------------------------------------
# Purge Configuration
# ---------------------------------------------------------------------
# Default mode for purge tool; could be either 'Purge'
purge.defaultMode=Purge
# Flag to indicate whether RTAIMessage shall be purged
purge.rtaiMessagePurge=true
purge.eodBranches=[EOD_RP_BRANCHES]
purge.cmmEnabled=[CMM_ENABLED]
# Settings for output sink
purge.sink.class=com.aleri.dataaccess.sink.FileSink
purge.sink.purge.Events.filename=
[INSTALL_BASE]/lms/output/log/PurgeEvents.xml
purge.sink.purge.Transactions.filename=
[INSTALL_BASE]/lms/output/log/PurgeTransactions.xml
purge.sink.purge.BalanceMovements.filename=
[INSTALL_BASE]/lms/output/log/PurgeBalanceMovements.xml
purge.sink.purge.RTAIMessages.filename=
[INSTALL_BASE]/lms/output/log/PurgeRTAIMessages.xml
purge.sink.purge.CMEvents.filename=
[INSTALL_BASE]/lms/output/log/PurgeCMEvents.xml
purge.sink.purge.CMTransactions.filename=
[INSTALL_BASE]/lms/output/log/PurgeCMTransactions.xml
purge.sink.purge.IssueDetails.filename=
[INSTALL_BASE]/lms/output/log/PurgeIssueDetails.xml
# Set JMS destinations for purge and archive mode
#purge.sink.purge.Events.destination=[QUEUE_LMS_PURGE_DB]
# Settings for partitioned queries
#purge.partitionQuery.{tag} = {where clause}

EOD_PURGE_DATE_CRITERIA has been renamed to purge.defaultMode. The supported options are


either Purge or Archive. EOD_RESPONSE_PURGE has been renamed to purge.rtaiMessagePurge. The
supported options are true and false. EOD_BRANCH has been renamed to purge.eodBranches. As be-
fore this setting is prefilled from master.conf setting [EOD_RP_BRANCHES]. CMM_ENABLED has
been renamed to purge.cmmEnabled. As before this setting is prefilled from master.conf setting
[CMM_ENABLED].

The property purge.sink.class is new. You can now define the sink to which the Purge app shall put the
messages. Default is a FileSink, but you could also directly update JMS for instance.

EOD_PURGE_EVENTS has been renamed to purge.sink.archive.Events.filename and


purge.sink.purge.Events.filename. Depending on the mode either the archive or purge sink are used. The
same applies to EOD_PURGE_TRANSACTIONS, EOD_PURGE_BALANCEMOVEMENTS, and
EOD_PURGE_RTAIMESSAGES. In addition, the Purge app now creates separate files for CMEvents
and CMTransactions, and it supports purge/archive of IssueDetails (when CMM is enabled).

PURGE_QUERY_<tag> has been renamed to purge.partitionQuery.<tag>.

5.2.5. Change related to Release Handler

Release Handler uses properties from file release.properties (see folder business). They are injected us-

14
New Features for LMS 6.2.5 to LMS 6.2.6

ing the Spring framework (ContextConfiguration). The Release Handler start app has been renamed to
ReleaseHandlerApplication; in order to start the app, you need to pass JVM argument -
Dlms.configuration.dir="<path to config>".

StreamPollInterval is obsolete and removed LimitRetryInterval has been renamed to releasehand-


ler.limitRetryInterval ScriptEngine has been renamed to releasehandler.scriptEngine RawMessageIn-
Transaction has been renamed to releasehandler.rawMessageInTransaction Platform.xxx properties have
been removed.

MQ.Queue.Preprocessor has been renamed to releasehandler.output.destination.Preprocessor.


MQ.Queue.External has been renamed to releasehandler.output.destination.External. MQ.Queue.Alert
has been renamed to releasehandler.output.destination.Alert.

File.Output.Preprocessor has been renamed to releasehandler.output.filename.Preprocessor.


File.Output.External has been renamed to releasehandler.output.filename.External. File.Output.Alert has
been renamed to releasehandler.output.filename.Alert. TRSubscribeTable has been removed. TRWPub-
lishTable has been removed.

ScriptFile has been renamed to releasehandler.scriptFile Rh.ContextList.File has been renamed to re-
leasehandler.contextListFile PreprocessorFields has been renamed to releasehandler.preprocessorFields
PartyFieldName has been renamed to releasehandler.partyFieldName

All SQLQuery entries have been renamed to releasehandler.SQLQuery and releasehand-


ler.xxx.SQLQuery respectively.

5.2.6. Change configuration for adpt_Preprocessor

The Queue QUEUE_SWIFT_MT9XX = [QUEUE_SWIFT_MT9XX] is removed instead of that new


queue QUEUE_SWIFT_STATEMENTS = [QUEUE_SWIFT_STATEMENTS] added in configuration.

Note
Please note as ESP and the ESP adapters are removed; all required procedures, configuration
items, scripts have been adjusted to reflect this removal. You will need to move your custom-
isations to the updated scripts

5.2.7. Static configuration for new UI

For new UI to work correctly, the static data available at


"<install_directory>/lms/init/data/init_data_sp05_to_sp06_static.xml_sample" file need to be uploded to
system.

5.3. Oracle upgrade script

Note
Please ensure that you retain a backup of the original databases for future reference after con-
version. The scripts will create tables corresponding to the new definitions, load the data from
the existing tables into the new, and as a second stage drop the tables with the old definitions
and rename the new tables to the correct schema name.

There were some changes in the Oracle schema between version 6.2 SP05 to 6.2 SP06 requiring a con-
version of the schema. SAP provides a conversion script in two parts as mentioned below.

The script lms-v6_2_5-to-v6_2_6-oracle-upgrade-drop-working-tables.sql is available as template lms-


v6_2_5-to-v6_2_6-oracle-upgrade-drop-working-tables.sql.template in package. You need to run up-
dateconfig.sh which convert this tmeplate to script. Please refer section Running the Update Configura-
tion Script from Installation Guide for running update config.

15
New Features for LMS 6.2.5 to LMS 6.2.6

• lms-v6_2_5-to-v6_2_6-oracle-upgrade.sql

• lms-v6_2_5-to-v6_2_6-oracle-upgrade-drop-working-tables.sql

You can execute above scripts in oracle client(Oracle Sql Developer) in above sequence.

Note
It is recommened to recompile all the database objects after upgrade.

16