Release Notes

UP Framework™®
Release 3.2.2

7 Dec 2015
ACI Worldwide
Offices in principal cities throughout the world
www.aciworldwide.com

Americas +1 402 390 7600

Asia Pacific +65 6334 4843
Europe, Middle East, Africa +44 (0) 1923 816393

Publish Date: December 2015

© Copyright ACI Worldwide, Inc. 2015
All information contained in this documentation, as well as the software described in it, is confidential and proprietary to ACI
Worldwide, Inc., or one of its subsidiaries, is subject to a license agreement, and may be used or copied only in accordance
with the terms of such license. Except as permitted by such license, no part of this documentation may be reproduced,
stored in a retrieval system, or transmitted in any form or by electronic, mechanical, recording, or any other means, without
the prior written permission of ACI Worldwide, Inc., or one of its subsidiaries.
ACI, ACI Payment Systems, the ACI logo, ACI Universal Payments, UP, the UP logo and all ACI product names are
trademarks or registered trademarks of ACI Worldwide, Inc., or one of its subsidiaries, in the United States, other countries
or both. Other parties’ trademarks referenced are the property of their respective owners.

About ACI Worldwide

ACI Worldwide, the Universal Payments Company, powers electronic payments and banking for more than 5,000 financial
institutions, retailers, billers and processors around the world. ACI software processes $13 trillion in payments and
securities transactions for more than 250 of the leading global retailers, and 21 of the world’s 25 largest banks. Through our
comprehensive suite of software products and hosted services, we deliver a broad range of solutions for payments
processing; card and merchant management; online banking; mobile, branch and voice banking; fraud detection; trade
finance; and electronic bill presentment and payment. To learn more about ACI, please visit www.aciworldwide.com. You can
also find us on Twitter @ACI_Worldwide.
 Product enhancements

Contents
About this document ............................................................................................................................. 4
Important notes ......................................................................................................................................4
UPF 3.2.2 Upgrade and Rollback Matrix ....................................................................................................5

Section 1: Product enhancements .................................................................................................. 6

Section 2: Product Fixes ............................................................................................................... 23

Section 3: Known issues ............................................................................................................... 38

Section 4: Additional information ................................................................................................. 39

Release artifacts ................................................................................................................................... 39
Installation of the UPF ........................................................................................................................... 39
Upgrading the UPF ................................................................................................................................ 40
Upgrade prerequisites ....................................................................................................................... 40
UPF 3.2.1-1 and above requires a minimum of Java 7 ......................................................................... 40
Legacy Business Services PIM and POS Cartridge Backward Compatibility............................................. 40
Default IP Ports for EUA Connection Changed ..................................................................................... 41
Upgrading Configurations from earlier UPF versions ............................................................................ 41
New license required when upgrading from releases prior to UPF 3.1-1 and change to Batch Toolkit as a
new licensable module in 3.2.1-1 and above ................................................................................... 41
Upgrading from a previous release using Oracle Column Level TDE ...................................................... 42
Upgrading from version 3.1-0 and 3.1-0-1 .......................................................................................... 42
Upgrading from UPF 3.2.1-1 to a newer UPF release on the Windows platform ..................................... 42
Upgrading from a previous release using the UPF Desktop with BASE24-eps......................................... 42
Improvements to configuration property and field validation ................................................................ 42
TCP/IP port validation ....................................................................................................................... 43

Copyright information ......................................................................................................................... 44

UP Framework Release 3.2.2 3

Release Notes — 12/7/2015
 Product enhancements

About this document

The UPF 3.2.2 release is built on top of the previous UPF 3.2.1-1 product release and
contains a number of enhancements and fixes to assist with the deployment and usage of
the UPF.

Important notes
• Customers upgrading from versions of the UPF earlier than 3.1-1 require a new license
from ACI
• The batch toolkit is now a licensable module and must be purchased and licensed for
use; as a consequence, a new license is required if this module is to be used in release
3.2.1-1 and above
• Upgrades from 3.1-0 and 3.1-0-1 include offline schema changes. See the upgrade
section for additional details
• Upgrades may require manual pre-upgrade steps to be carried out. See the Legacy
Business Services PIM and POS Cartridge Backward Compatibility section for more
information
• Oracle 12 is supported from 3.2.2 and above however, customers must install the
appropriate Oracle 12c patch associated with Oracle bug ID 19703301 available from Oracle
• When installing the UPF in Core Infrastructure mode the UPF-<releaseversion>-
ExternalLibraries.zip (Windows) OR UPF-<release-version>-ExternalLibraries.tar.gz
(UNIX/Linux) files will need to be expanded to include required 3rd party libraries. Please
see GEN-15802 below
• With the enhancement to allow Endpoints to be packaged into a user cartridge,
endpoints from a previous release configuration will now be shown under the "Legacy
Endpoints" section in Configuration Builder. There is no user action mandated with this
change and these will continue to operate as before. Please refer to GEN-15365 below for
additional information

UP Framework Release 3.2.2 4

Release Notes — 12/7/2015
UPF 3.2.2 Upgrade and Rollback Matrix

UPF Version Upgrade Support Rollback Support

3.2.1-11 Yes Yes

3.2-0 Yes Yes

3.1-1 Yes Please contact ACI Support

3.1-0-1 Yes Please contact ACI Support

3.1-0 Yes Please contact ACI Support

3.0-3-3 Please contact ACI Support Please contact ACI Support

1
Upgrading on Windows is only available from UPF 3.2.1-1 and needs a patch to be applied to UPF 3.2.1-1 install
before the upgrade process. Please contact ACI customer support to acquire a patch for your 3.2.1-1 installation.

Contact ACI support if the version of UPF you are running is not documented in the above
matrix.

UP Framework Release 3.2.2 5

Release Notes — 12/7/2015
Section 1: Product enhancements
This release of the UPF contains the following enhancements:
Key Summary
GEN-14219 Addition of encode/decode
scripting functions
GEN-14670 Support format conversion in
the MQ channel/route
component
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
Two scripting functions have been added:
* encode: to convert the internal value of a
field into its on-the-wire representation
* decode: to convert a sequence of bytes into
the internal value of a field
Both functions use the definition of the field in
the endpoint model to perform the operation.
Refer to the online help for more information.
The enhanced functionality is provided by the
use of ICE-XS and the ICE-XS WebSphere MQ
Route.
Please refer to GEN-15037 and the product
documentation for additional information.
6
Key Summary
GEN-14688 WSDL/XSD Endpoint
enhancements including ICE-
XS integration
GEN-14778 Request for Security Context
Support
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
Enhance WSDL/XSD Endpoint import wizard to
support ICE-XS integration.
The Wizard has been enhanced with additional
help text at every step, an outline of manual
configuration which must be performed
following the import and new options
including:
* Whether SOAP Envelope needs to be
created.
* Whether Default BSI/XSD dateTime
translations should be created.
Other improvements include:
* Support for multiple WSDL files.
* Namespace attributes added to root fields
* Custom parameters for default namespaces
values
* Generated outbound handling scripts to
populate namespaces.
* Added translations between long/epoch and
XSD dateTime formats.
* Including custom parameters to define the
on-wire XSD format.
Endpoint Builder has been enhanced to include
both inbound and outbound translation scripts
which may be used to translate the
inbound/outbound values with UP Script
UPF now supports Security Context handling
using ICE-XS and its WSAPI link protocol. WS-
Security meta-data received by ICE-XS can
optionally be forwarded to the endpoint in UPF.
The WSAPI Header has a new configuration
parameter to enable Security Context
handling. If this is enabled on the UPF
endpoint and ICE-XS sends Security Context
data then this data will be available in the
ctx.wsapi.sec_ctx variable. This data can be
used to pass the Security Context on to other
participants in the transaction flow, e.g. to BSI
service providers. This can improve the end-to-
end auditing and traceability.
7
Key Summary
GEN-14914 Support variable length file
formats
GEN-15003 Move data offload and data
retention parameters from
entity set up to Platform
Settings
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
To support adopting product File processing
requirements, below changes are introduced
=>
a. Added 3 new length type =>
1-or-2-byte : Length is dynamic, can be 1 or 2
bytes i.e., check the first bit if set, indicates
that for length read two byte.
1-hex-pad-byte : The hex byte decimal value
indicates the length of the field.
If length is even then the data contains one
extra pad byte in cursor so skip that byte.
2-hex-pad-byte : The hex byte decimal value
indicates the length of the field.
If length is odd then the data contains one
extra pad byte in cursor so skip that byte.
Added 4 new functions:
* IBMIEEE754FloatToDecimal : To convert hex
value to decimal from IEEE 754 IBM format.
* DecimalToIBMIEEE754Float : To convert
decimal to hex value in IEEE 754 IBM format.
* DecimalToIEEE754BinaryFloat : To convert
hex value to decimal from IEEE 754 Binary
format.
* IEEE754Binary64FloatToDecimal : To convert
decimal to hex value in IEEE 754 Binary
format.
'Data Offload' and 'Data Retention' parameters
for the RDBMS entities have been exposed
under Platform Settings. The corresponding
configurations under entity-models will act as
default configurations and will be replicated
under Platform Settings unless modified by
user under Platform Settings.
8
Key Summary Description

GEN-15037 HAR replacement with ICE-XS ICE-XS, an advanced communications provider

for ACI applications, is now integrated with the
UPF as a new type of HA Router. The existing
MCAS HA Router continues to be supported
however ICE-XS is now also available. ICE-XS
provides the following new Route types and
services:

* ICE-XS HTTP Server Route

Provides the ability for UPF to operate as a
HTTP(S) server, receiving HTTP requests from
client applications and browsers.

* ICE-XS HTTP Client Route

Provides the ability for UPF to connect to
remote HTTP(S) servers.

* ICE-XS WebSphere MQ Route

Provides the ability for UPF to connect to IBM
WebSphere MQ queues in client or server
mode, and features such as:
- MQMD manipulation for fields such as expiry,
persistence, encoding.
- MQCIH Header for CICS
- Multiple MQ client connection names for
automatic fail-over
- Convert On Get for message encoding
conversion
- MQGET wait interval configurable
- Browse Lock support
- MQ client SSL options
and more...

* SSL/TLS support
Provides the ability to operate SSL/TLS over
the HTTP connections, supporting up to TLS
version 1.2.
Provides the ability to use CRL and OSCP to
revoke certificates.

* SOAP Web Service support

Provides the ability for UPF to invoke remote
SOAP Web Services or be invoked as a SOAP
Web Service, over any of the ICE-XS Route
types.

* WS-Security (WSS) support

Provides the ability for UPF to secure Web
Service calls, via the following token profiles:
UP Framework Release 3.2.2 X.509 Certificates, Kerberos tickets, 9
Release Notes — 12/7/2015 username/password.

* LDAP support for Authentication

HTTP or WSS credentials can be authenticated
Key Summary
GEN-15038 Support for Oracle 12
GEN-15039 RedHat 7 Operating System
Support
GEN-15043 Tx Tracing - add the ability to
enable the whole variables
object to be traced at any
stage.
GEN-15044 Create POS Framework for
use with toolkit
GEN-15047 UPP POS DUKPT encryption
support
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
UPF has been enhanced to include support for
Oracle 12.
Note: Customers must install the appropriate
Oracle 12c patch associated with Oracle bug ID
19703301 for Oracle 12 support.
UPF has been enhanced and now includes
support for RedHat 7 operating system.
Added an option "Detailed Output" with a
check-box widget to add/update trace
commands. When checked, it enables tracing
of all non-null variables inside the Variables
object for different stages.
The POS user cartridge has been created. It
contains the terminal model and other plugins
and components that can be used to create the
drivers to acquire POS transactions. The POS
user cartridge is now released independently of
the core switch.
Various utilities have been provided to facilitate
the creation of custom drivers and endpoints:
creation of session handler for a particular BSI
service, creation of ISO1987 meta
configuration and message protocol. They
reduce the amount of manual work required to
complete the configuration.
The configurations of BSI security operations
(Data Encryption, Mac Authentication, Key
Management) have been streamlined and
enhanced.
Security Configuration in Endpoints now allows
configuration of the BSI DUKPT MAC Verify and
BSI DUKPT MAC Generate services.
10
Key Summary Description

GEN-15056 Addition of Rules support UPF now supports user-defined rules. Rules
offer an easy way to customize and extend the
business rules of an application.

Entity Builder can be used to define new rule

set definitions. A rule set definition describes
the structure of the rules, e.g. what conditions
governs the firing of rules, what actions are
taken when rules fire, etc.
The actual rules are part of Component
Entities. Component Entities may have one or
more properties that reference rule set
definitions. When Component Entities get
configured the properties – including the rules
– are entered by the user.

Rules can be used in various parts of the

configuration, e.g. inside endpoint processing,
session processing, etc. To use rules they need
to be first looked up (by locating the
appropriate Component Entity instance) and to
be executed (using the new executeRules()
function or the new ‘Execute Rules’ session
step).

The UPF tracing facility has been enhanced to

provide details of the rules processing to
facility troubleshooting of issues related to
rules execution.

UP Framework Release 3.2.2 11

Release Notes — 12/7/2015
Key Summary Description

GEN-15057 Component Entity Static
Scripts
UPF now supports Static Scripts that can be
optionally configured for a Component Entity.
This promotes re-usability within the UPF
configuration because Component Entities and
their associated Static Scripts can be used in
Endpoints (e.g. External Message Rules), Rule
Set Definitions (e.g. inside Actions), Sessions
(e.g. Script Steps), and Scheduled Scripted
Tasks.

A Static Script has a unique name within the

Component Entity. The globally unique name is
derived from the globally unique name of the
Component Entity concatenated with the Static
Script name. It is encouraged to use
Component Entities as a grouping mechanism
for script libraries that functionally belong
together. Because Component Entities are not
required to have any property defined it is
possible to have Component Entities that only
contain Static Scripts. In some cases it makes
sense to have Component Entities that have
properties as well as Static Scripts. Note that
Static Scripts are called static because the
scripts do not have a reference to the
Component itself, i.e. if the Static Script needs
the Component for its computation then the
Component must be passed in explicitly as an
input parameter.

Static Scripts can have zero or more input

parameters, an optional output parameter and
the script itself. To reduce the fully qualified
name of Static Scripts it is advisable to use
short identifiers and prefixes.

Example:
- Entity Model Id is 'libs' and prefix is 'common'
(note that 'aci' prefix is reserved for ACI
Worldwide)
- Component Entity 'validations'
- Static Script 'ValidateAmount' (input
parameter is 'amount', return type is boolean)

To call the above Static Script:

common.libs.validations.ValidateAmount(1000
0)

UP Framework Release 3.2.2 Important: 12

Release Notes — 12/7/2015 The following are known limitations with Static
Scripts:
1. Recursive calls are not supported, i.e. a
Static Script cannot call itself
Key Summary
GEN-15067 Support for IBM Java 8
GEN-15075 UPF Installer has been
enhanced to add MQ into
existing installation
GEN-15088 Added support for block
queries (pagination style) in
RDBMS entities
GEN-15130 Simplification of Oracle
GoldenGate configuration with
Asynchronous Replication
GEN-15153 Script support for HMAC / SHA UPP Script has been enhanced to provide
256
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
UPF has been enhanced to include support for
IBM Java 8
The UPF installer has been enhanced to allow
the addition of MQ into an existing UPF
installation.
The 'Select' operation of an RDBMS entity now
supports block queries. The first select fetches
up to the specified maximum number of rows.
Subsequent select operations can use the
offset to indicate that the rows after the offset
should be fetched rather than the ones from
the beginning.
This feature can be used to retrieve blocks of
data at a time (e.g. for pagination purposes).
Note that the query should use 'order by' that
include the unique primary key or a timestamp
to ensure consistent results.
The UPF GoldenGate configuration support is
enhanced to allow security information to be
added when generating GoldenGate
configuration.
Prior to this change, an operator required to
manually augment the generated GoldenGate
configuration files to include security
information if required. Refer to the "UPF
Asynchronous Guide" for further information
regarding this area.
HMAC and SHA256 functionality
13
Key Summary
GEN-15181 Task definition has been
separated from task
scheduling
GEN-15183 Endpoint builder enhanced to
support a custom reject logging
operation
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
The creation of scheduled tasks such as Batch
Command Task, Batch Cleanup Task, Scripted
Tasks is now separated into definition and
scheduling steps to better reflect the
operational aspects of these two tasks.
The tasks themselves need to be defined under
Task Definitions and then scheduled under Task
Scheduling. Previous "Scheduled Tasks" has
now been renamed to Task Scheduling.
Previously defined tasks are still supported and
will be visible in Configuration Builder under
Task Scheduling.
A 'Custom Reject Logging Operation' has been
added to the logging section of endpoint
builder. When defined this takes precedence
over the default mcas_rejectlog. Any entity
with operations defined on it can then be used
for reject logging. The user will need to fill in
the logging operations as they do for other
endpoint logging.
14
Key Summary
GEN-15224 Improved JMX support for
RDBMS entities
GEN-15228 Removed legacy 'install-upp-
license' option
GEN-15250 The UPF now supports MSSQL
database when installing in
"Core Infrastructure" mode
GEN-15268 UPF-Installer has been
upgraded to use the APSF
1.4.0.7 release artifacts
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
RDBMS entities can now be exposed as
"expanded" JMX MBeans, i.e. one MBean per
row stored in the underlying database table.
Changes to the entity like inserting new rows,
updating existing rows, and deleting rows will
be reflected in real-time. The existing Manager
JMX MBean (i.e. singleton MBean for all
resources) that can be used to do CRUD or
view-only access can still be used.
To activate this feature the "Expose as
Expanded Resource" checkbox need to be
ticked in the "Manageability" section of the
entity configuration (previously this section
was called "Platform Manager"). It is possible
to only expose selected entities as expanded
resources.
The tooltip help providers more details on the
configuration of expanded resources. Note that
this feature should be used sparingly because
it creates additional overhead for the UPF
runtime. The intention of this feature is to
expose small amounts of data (10s of rows)
stored in the database directly as managed
resources.
The legacy 'install-upp-license' option which
was used for the old legacy license format has
been removed
The UPF has been enhanced and tested to run
using MSSQL database for "Core
Infrastructure" mode when installed on
supported Windows platforms
UPF is now enhanced to support APSF 1.4.0.7
release artifacts.
15
Key Summary Description

GEN-15275 Command line support for The cartridgemgmt operations script now support
loading and activating user the loading and activating of user cartridges from
cartridges. the command line. The new commands available
include:

loadusercartridge Options:
--filename=<file> Where <file> is the filename
referencing a user cartridge

activateusercartridge Options:
--name=<name> Where <name> is the name of
the user cartridge
--version=<version> Where <version> is the
version of the user cartridge
--updateMode=<option> Where <option> is one
of: NON_DISRUPTIVE_UPDATE |
DELAYED_DISRUPTIVE_UPDATE |
DISRUPTIVE_UPDATE

GEN-15286 RDBMS limits can now be
applied in real time
A new flag (Update Existing Limit) has been
added to RDBMS Limits entity to allow the user
to choose to update existing limit entries with
updated limits. This would allow the user to
change a limit on the fly after a limit has been
created. The previous behavior would require a
new limit period to be started for the change in
limit to take effect.

GEN-15317 Prompt to trim spaces for text When saving a config entry, if one or more
fields in Config Builder when editable text fields contain leading/trailing
saving a config entry space(s), a warning dialogue is shown asking
the user if they want to trim the space(s).

GEN-15336 Print database version on boot UPF has been enhanced to print the version of
the database driver and server at a set interval
which defaults to 3600000 ms (1 hour) but can
be configured by setting the option
{{"mcas.db.version.interval}}

UP Framework Release 3.2.2 16

Release Notes — 12/7/2015
Key Summary
GEN-15342 listLMS command added to
show information related to
Large Message Support
GEN-15343 LMS flag now displayed in
monitor output in UPF and
HAR.
GEN-15345 Introduction of a new shared
"fileCtx" variable across all
messages for file processing
GEN-15352 HTML trace enhanced to show
UPF version in the header
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
A new command named listLMS has been
added to show Large Message Support state,
relevant system properties and options.
Added monitor output for LMS Flag on switch
and HAR log files.
HAR Log example:
Tue Aug 04 15:25:59 EST 2015: ---------------
-------------------------2015/08/04 15:25:59.6:
[ LMS: on Mem: 24/178 ]
UPF Log example:
15:27:50 TPS=0 Act=0[0] Com=0[0]
Ver=3.2.2-SNAPSHOT.001 Sch=0 Tmr=15 CC-
Mem=2778/950/15/0 CPU=17
Pool=0/s hit=0% Script=0/s@0us Group
out=6[5] in=6[5] LMS=on WAN rcv=0 msg=0
lat=n/a CP d=0.0k s=0.0k
A new shared variable named "fileCtx" has
been introduced that is shared across all
records when processing files.
This can be used for functionality such as
storing header information and totals.
The "fileCtx" variable is created once per file
and shared across all records. Upon the
completion of processing, this variable must be
disposed.
UPF Version information is now visible on HTML
trace file header
17
Key Summary Description

GEN-15365 Cartridge Management Artifact generation changes

Enhancements Optimized artifact generation process so that
each cartridge would generate only the
artifacts associated with its own plugin entries.

Endpoints plugin
Until now Endpoints lived in a node property of
the Switch service. Consequently you cannot
define endpoints in two separate cartridges
(e.g. a user one and the config cartridge). With
this change endpoints live in their own plugin
(called nodes).
For the moment you will see two entries in
Config builder: Endpoints – the new nodes
plugin, and Legacy Endpoints – the Switch
service location. You won’t be able to add new
nodes to the Legacy Endpoints (only edit and
remove). There is no runtime difference
between the endpoints defined in those two
locations. To future proof your configuration
consider moving your endpoints from the
Legacy Endpoints to the new Endpoints
section.

UP Framework Release 3.2.2 18

Release Notes — 12/7/2015
Key Summary
GEN-15371 Performance and non-
functional enhancements for
3.2.2
GEN-15415 Addition of management
command to store user
cartridges from URL.
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
A number of performance improvements have
been made in this release.
The two main improvements relate to the
following areas:
1. batch loads (and consequently some types
of file loads), and
2. large columns (especially BLOBs) in Oracle.
1. Batch load improvements were made that
increase the batch throughput achievable on a
single endpoint. In particular this means that
file loads that load into batches for later
processing (e.g. files of payments) will now
run faster.
2. Improvements were made around the way
we store database BLOBs when using Oracle
by reducing the amount of data copying that
was occurring. This has direct benefits in
reducing latency and also has flow on effects
such improving ability for the CPU caches to
work more effectively which can allow higher
throughputs to be achieved.
By default this mode is disabled but can be
enabled by setting the system property
DIRECT_BUFFER to the value 2 in the switch
startup configuration:
-DDIRECT_BUFFER=2
In future releases this will be the default
behavior.
New management commands have been added
on Config service to support storing user
cartridges from a URL. Complementary
commands to remove, list and summarize user
cartridges have also been added.
19
Key Summary
GEN-15425 Receive step added for
session builder
GEN-15429 Enhanced process to move
configuration items between
cartridges
GEN-15438 Support ‘is null’ and ‘is not
null’ operations in streaming
operations
GEN-15443
Oracle optimizer chooses index
scan when min and max are used
in a single query on time column
GEN-15449 User Cartridge version
modification
GEN-15498 Add ability to filter configuration
changes by their type
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
A new 'Receive' step has been added into
session builder. It can be used for receiving
additional messages from an endpoint.
Note: due to the way that aliases work the
receive step will only work on endpoints that
have previously had a message sent to them.
This is because the slave session and alias
needs to be setup in order for the message to
be routed back to the master session. This
feature cannot be used for receiving messages
from a completely new endpoint.
The Configuration Builder wizard to move
configuration entries between cartridges has
been enhanced to improve user productivity.
The new "Move Plugin Entries to Cartridge"
wizard allows a user to move multiple
configuration items from a number of
cartridges to a target cartridge.
Operators ‘is null’ and ‘is not null’ are now
supported in the streaming framework.
Optimization of queries for Oracle to not select
aggregate functions such as min, max, count
in the same select statement
Added ability to update user cartridge
information.
Users can now update the version,
compatibility, and description of user
cartridges.
Added ability to filter configuration changes by
their type.
This new feature is available for all dialogs
where we a panel with a configuration changes
tree is available.
Feature allows filtering of changes which are
not of interest to the end user.
20
Key Summary
GEN-15505 New operational script called
"ssm_tool" has been added to
generate HMAC Key
GEN-15564 Addition of UP script functions
for URL encoding/decoding
GEN-15572 UPF has been enhanced to use The UPF now uses the ACI Universal Payments
PIM 1.5 Information Model (PIM) version 1.5 as the
default PIM version.
GEN-15591 Configuration Builder
enhanced to hide empty root
entry nodes from the Config
Explorer Tree
GEN-15593 UPF Installer has been
enhanced to minimize manual
workarounds when installing
UPF in Async mode
GEN-15650 Guard against
misconfiguration of
offloadable log entities
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
New operational script "ssm_tool" can now be
used to generate encrypted HMAC key from
keystore keys
Added two new functions to UP script:
* urlEncode – encodes a string into URL
encoded format
* urlDecode – decodes a string from URL
encoded format into raw format
With this enhancement the usability of
Configuration Builder has been improved.
Functionality has been added to hide readonly
empty root nodes for configuration and
cartridge view of the Config Explorer Tree
panel.
e.g; "Legacy Endpoints" node is a read-only
root node which lists the endpoints that were
defined in configuration from previous
releases. Users can view and modify entries
under "Legacy Endpoints" but they can't add
new entries under it. If there are no entries
under "Legacy Endpoints" the node is not
shown in Configuration Builder.
In previous releases of the UPF Installer there
was no possibility to regenerate Oracle Golden
Gate configuration files. Introduced new utility
for generating Oracle Golden Gate
configuration files.
Optimizes the offloading of log entities’ data by
ensuring that the framework will use only the
known set of properties to determine what
needs to be offloaded.
21
Key Summary Description

GEN-15691 The UPF installer has been

The UPF installer has been enhanced to
enhanced to support upgrade
support upgrade for Windows. For upgrading
from 3.2.1-1 onward for
from 3.2.1-1 to 3.2.2 customers need to
Windows
contact ACI support before attempting to
upgrade to release 3.2.2 on Windows to
receive a patch for their existing version.

GEN-15802 Installation of the UPF in Core

When installing the UPF in Core Infrastructure
Infrastructure mode now
mode there are additional 3rd Party libraries
separates out 3rd Party
that must be manually added to the installer
libraries during installation
prior to performing the install.
These libraries are available in 2 formats:
* UPF-3.2.2-ExternalLibraries.zip
* UPF-3.2.2-ExternalLibraries.tar.gz
The contents of each are identical, and you should
choose whichever library is more convenient for the
platform you are installing on (e.g. .zip on Windows,
.tar.gz on Linux)
After unpacking the installer, go to the root of
the installer (directory containing install script)
and unpack the ExternalLibraries
This will extract the extra libraries into the
correct place under src/apsf

UP Framework Release 3.2.2 22

Release Notes — 12/7/2015
Section 2: Product Fixes

This release of the UPF software includes the following fixes:

Key Summary Description

GEN-11704 Configuration Builder does
not display type of
Authentication Realm
Due to a defect in Configuration Builder the type
of Authentication Realm was missing in the
Authentication Realms panel (which is located in
Platform Settings). This has been fixed and the
type is now shown.

GEN-12913 Add the ‘Merchant Channel The property ‘eps_ch_prfl’ has been added to the
Profile’ property to POS terminal model. It represents the Merchant
terminal model Channel Profile defined by BASE24-eps, and
should be used to populate the field
ConfigurationPOSChannelSpecific.MerchantChanne
lProfile in various BSI transaction services.

GEN-13055 XSD import for endpoint
may mark fields as
Mandatory when the
actual definition in the
XSD is not mandatory
Optional XSD fields which contain simpleType
definitions are now imported with the correct
minOccurs and maxOccurs values (presence=’M|O’
repeated=’[0-10000]’)
Case# 02095271

GEN-13302 Improved error reporting More detailed and appropriate error messages are
on command line tools now provided to the end user.
such as mcascmd

GEN-14186 Importing PIM from wsdl
on windows versus linux
produces different results.
The PIM import wizard within Entity Builder
provides additional control at import time.
The user may now import a subset of WSDL files
from the import directory / zip file, providing more
granular control of the services that are
supported.

GEN-14662 UPF installer - initializing Fixed and installation failure due to a null value
offload database is failing being inserted in not 'nullable' column.

GEN-14677 Race condition between Serialize the handling of database recovery/offline

database polling & events.
handling of database Case# 01881116
de/activation

UP Framework Release 3.2.2 23

Release Notes — 12/7/2015
Key Summary
GEN-14825 No user friendly error
reported if invokeService()
function fails to find
service provider
GEN-14869 Remove ISO8583 endpoint
from the list of base
endpoint types in Config
Builder
GEN-14907 Cartridge Management:
Prevent user from “Apply
Config” action when in
cartridge mode
GEN-14950 Entity based limits can
cause consistency
problems
GEN-14960 File processing, in
window’s environment,
after processing the file,
its moved to archive
directory. However the file
name is not changed back
to original. Its retained as
“pending-*”
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
The invokeService script function calls script error
if an internal error occurs.
Prior to this change the script function returned
the error code as a primitive rather than the
associated PIM result structure.
Returning the error via scripting error allows the
UPF error handling to include these errors into
places like the session trace for better visibility.
ISO 8583 Endpoint and ISO 8583 Sim endpoints
have been removed from the list of base endpoints
in Configuration builder. ISO 8583 based message
protocol is now available in Universal Endpoint.
When a configuration is loaded in cartridge editing
mode in Configuration builder, following
configuration specific actions will no longer be
available-
1. Apply Configuration Changes
2. Compare and View Changes
3. Import from XML
4. Export to XML
5. Export to file
‘RDBMS Entity Limits’ have now been deprecated.
Users are encouraged to change any existing
RDBMS Limits with a Type of ‘RDBMS Entity Limit’
to ‘Scripted Limit’. This will mean that the user
needs to define their own limits table and query to
obtain the limits prior to performing the limits
update.
Previously, UPF file processing on Window’s
platform did not correctly cleanup files in the
archive directory. After processing a file and
moving it to the archive directory, the file name
was not changed back to original. It was retained
as “pending-*”. Fixed.
24
Key Summary Description

GEN-15028 MD5 check sums for install Installer check sums have been upgraded to use
artefact now use a stronger sha256 hash. To verify the check sum for
stronger hash (sha256) package installer refer documentation.

GEN-15051 For EUA connection errors like
timeout, error message should
state the reason of connection
failure
For EUA connection errors due to ‘timeout’ or
‘unknown host’ a generic error message was
displayed. This has been modified to state the
cause of failure in case of ‘Timeout’ and ‘Unknown
Host’ error.
Case# 01991832

GEN-15097 Fix the number of
messages in/out reported
in the Load Generation
panel
Previously, under load, the number of messages
in/out reported in the Load Generation panel is
incorrect.
For instance, in sunny day scenario (no error, no
timeout), the number of messages in, is not the
same as the number of messages out.

This has now been fixed.

GEN-15145 Toggling Async Mode to Previously, the UPF Installer did not correctly
Sync Mode option doesn’t toggle the Async Mode to Sync Mode option. This
reset number of sites has been fixed.

GEN-15161 Irrecoverable database Mapped ORA-24816 as a DB_KNOWN_ISSUE to

error on DB1 – ORA-24816 better handle this Oracle issue

GEN-15198 UPF MCAS crashes with Fixed the issue which crashes UPF MCAS with “Blocked
“Blocked thread” error when thread” error when applying configuration to switch.
applying configuration Case# 02015668

GEN-15209 BSI filter protocol pattern BSI URL validation has been modified to accept
not complete valid hostnames.

GEN-15221 Added support for XML The UPF can now process XML messages that
comments contain XML comments (<!-- .... -->). The XML
comments are simply ignored during the parsing
of XML messages. In previous releases of the UPF
the presence of XML comments could cause
decoding errors.

UP Framework Release 3.2.2 25

Release Notes — 12/7/2015
Key Summary Description

GEN-15222 Script Editor does not Fixed issue with validating and highlighting of
work for Load Generators GroovyEditor e.g.; editor widget in Sting Load
– changes are lost Generator causing class cast exception.

GEN-15225 model driver produces an The UPF is unable to send messages greater than
ArrayIndexOutOfBoundsEx 8192 bytes when also including the following
ception when increasing headers: header/link header/endpoint header.
the buffer size
The outbound buffer is calculated correctly when
adding the header/s to the buffer preventing an
ArrayIndexOutOfBoundsException occurring.

Case# 02024174

GEN-15230 Issue with sharing local A defect in UPF script prevented closures with local
closures in UPF script scope to be shared, i.e. a closure with local scope
could not be used by more than one other local
closure.

Example:
def sharedClosure = { … }
def closure1 = {
sharedClosure()
}
def closure2 = {
sharedClosure()
}
// works
closure1()
// doesn’t work
closure2()

This has been fixed and local closures can be

shared now.

GEN-15232 RDBMS Total entities Some of the total entities panels were not
panels were not displaying displayed in Platform Manager due to failure in
in Platform Manager identifying the entity type. The total entities are
now properly recognized and displayed in Platform
Manager.

UP Framework Release 3.2.2 26

Release Notes — 12/7/2015
Key Summary Description

GEN-15237 SSL client certificate UPF was not correctly checking the root certificate
matching broken when against the trusted certificates in the scenario
using 3-level cert chain where there was a certificate chain of more than
and server only supplies two levels and the other side only supplied the leaf
leaf cert certificate. Fixed.
Case# 02028134

GEN-15240 An empty else block in An empty else block in UPP Script could cause a
UPP Script causes a bad bad variable assignment.
variable assignment
For example. With the following script…

myCode = 5
if (myCode == 5) {
a = ‘ACCP’
} else {
// x=0
}
shouldBeWw = ‘ww’

The value of shouldBeWw should have value ‘ww’

but with commented or empty else block, this
would be set to a value of ‘ACCP’.

Fixed.
Case# 02029849, 02107068

GEN-15242 Croatian and Romanian Currency tables have been updated to match ISO-
currency names need to 4217 Amendment 60, published 2015-06-19
be updated as per ISO
4217 Amendment Number
160

GEN-15244 UPP Scripting The Scripting documentation that was present in

documentation from 3.1 the 3.1 manuals but missing in the 3.2 and 3.2.1-
manual missing in 1 manuals has been restored in the 3.2.2
subsequent releases manuals.

GEN-15283 Entity Builder doesn’t Improved validation for “name” property on

prevent configuring component entity to prevent the use of reserved
properties with invalid words.
names like “type”
Case# 02037579

UP Framework Release 3.2.2 27

Release Notes — 12/7/2015
Key Summary
GEN-15308 In UP script a captured
closure variable cannot be
updated
GEN-15324 Config Builder raises
“Illegal tag ‘silentError’”
exception when importing
old configuration
GEN-15334 Channel state can get lost
during node migration
when switch restarts
GEN-15349 Fatal error when sending
to hold-queue endpoint
due to Oracle Error ORA-
01461
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
Fixed UP scripting engine to remove class cast
exception that prevented variables captured by a
closure from being updated.
Case# 02034138
An issue has been fixed that is preventing the
loading of old configurations into Configuration
Builder with an error message “Illegal tag ‘silent
error’”
When a switch instance is restarted, and
endpoints migrate back to that instance, the
endpoint/channel state may not be correctly
recovered, preventing the affected endpoints to
process transactions.
The issue is due to a race condition between the
creation of the channels (when they try to retrieve
the state from the previous primary instance) and
the activation of the endpoint (when the instance
becomes primary). If the endpoint (on the current
instance) is activated first, the previous primary
instance would have been deactivated, and
therefore would NOT send back any state.
Endpoint and channel states are now stored in a
distributed map to avoid the above race condition.
Case# 02090247
Version entities can fail persisting records with
columns containing data greater than 4000 bytes.
Version entities include file load and batch
functionality used by the UPF.
This fix allows columns with data greater than
4000 bytes to be inserted by version entities.
Case# 02053360
28
Key Summary
GEN-15354 Opcode ‘M6’ should not be
used for MAC generation
on Thales HSM if the
required MAC size is more
than 4 bytes
GEN-15366 URLConnectorHeader has
a hard coded
MAX_HEADER_SIZE
GEN-15368 Unexpected replication
errors caused by “ORA-
00001: unique constraint
(ACI.MCAS_CRON_TASK_S
TATE_PK) violated
GEN-15373 MQ remote port should
NOT have restrictive
validation limiting to ports
above 1024
GEN-15385 Exporting an empty
configuration causes some
system plugins to be
incorrectly exported to the
config cartridge
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
The op-code ‘M6’ was used for MAC generation,
due to Thales documentation that states that it
superseded op-codes ‘MQ’ and ‘MS’. However this
is incorrect, as it only produces 4-bytes MAC, and
therefore is unsuitable to use for Voca.
The op-code ‘M6’ is still used by default. However
it will be replaced by:
- ‘MS’, if the option mcas.security.facade.iso.ms-
mac is set, or if the required MAC size is more
than 4 bytes, and the algorithm/encryption
method is ISO9797.3 / X9.19
- ‘MQ’, if the option mcas.security.facade.iso.mq-
mac is set, or if the required MAC size is more
than 4 bytes, and the algorithm/encryption
method is ISO9797.1 / X9.9
The MAC size and encryption method can be set in
the endpoint Payment Security Configuration / ISO
Security Standard.
Case# 02050840
Added the configurable mcas.coresw.max-url-
header-size to override the default max size of
header (1024) to allow for larger header size.
Case# 02061304
Ensure database transactions are executed in the
same order on all active databases and ensure
that the id of the cron tasks are unique
Case# 02066870
Relaxed validation of remote MQ ports to allow
port numbers less than 1024
When empty configuration (configuration without
any additional user configurations) is exported to
XML configuration, some of the system plugins
were exported. This has been fixed to prevent
system plugins being written while exporting
configuration.
29
Key Summary Description

GEN-15387 Operations are duplicated Invoke session step now clears any queued
when logged within database operations when invoking a child so as to
session invoked by prevent the operation being logged twice.
another session
Case# 02063207

GEN-15401 Changes made in some In Configuration Builder, changes made in some of

input fields are not saved the fields are not saved when changes are
accepted. This is because the fields were read only
fields but Configuration Builder displayed them as
editable. The issue has been fixed so that the
fields meant to be read only are not modifiable in
Configuration Builder.
Case# 02071320

UP Framework Release 3.2.2 30

Release Notes — 12/7/2015
Key Summary Description

GEN-15405 UPF issues when installing This fix is related to the asynchronous deployment
in an Asynchronous of the UPF. The UPF handles old values stored in
environment the MCAS_CONFIG_VERSION (MCV) table.

The Oracle Golden Gate rule generation function

has been modified to prevent the replicated MCV
table from having an empty entry when the source
table updates the same data. This can occur on
initial installations and prevents the secondary site
UPFs from booting to an empty UPP system. The
current work around is using sqlplus to delete and
re-insert the entry in the MCV table in the primary
site.

Select * from mcas_config_version;

delete mcas_config_version;
insert into mcas_config_version values (‘${Value from
the select}’);

Async Upgrading Actions Required

When the OGG CDR configuration files are
propagated during upgrade the sql script
upf/init.storeProcedures.sql must be run on both
databases and then restart the configuration
replication streams (in both directions). The
summary of commands are:

# After the siteP/S.zip files are propagated and

expanded to the appropriate

# databases, the following commands are to be run on

both sites.

# Action: defines the new store procedure required

sqlplus <ogguser/oggpswd>@database @
upf/init.storeProcedures.sql

# Action: restarting configuration replication

replicat processes
# start ggsci (and ensure it is logged in to the
database)
stop c*rep
start c*rep

After these commands are performed the obey

UP Framework Release 3.2.2 diroby/resume command is performed (as per 31
Release Notes — 12/7/2015 the async documentation).
Key Summary Description

GEN-15455 Unnecessary verbose diag This has been fixed to only display when
logged after install: appropriate.
File.based.audit

GEN-15466 Endpoint Templating had While creating a template from a cloned

limited parameter configuration, users were only able to select some
selection of the parameters. The issue has been fixed so
that users can now select all available parameters.

GEN-15469 Config Builder won’t start Could not start Config Builder and Platform
after ACI JRE update to Manager with run scripts on Windows OS after
jre1.8.0_60 updating Java to version 1.8.0_60. This has been
fixed.
The application parameters for Configuration
Builder have been moved to builder.properties and
Platform Manager has been moved to
manager.properties.
Case# 02115401

GEN-15472 Date/time formatting with
milliseconds incorrect
Formatted values with milliseconds were being
cached as though they had a granularity of a
second so if a previous format had occurred in the
same second then any subsequent values within
that second were being returned that previous
value. Fixed so that we don’t cache formatted
values when the format string specifies
milliseconds.
Case# 02098655

GEN-15476 Filtering criteria on There was an issue preventing import of

XSD/WSDL import does XSD/WSDL when using ‘operations’ as filtering
not work criteria. This issue has been fixed

UP Framework Release 3.2.2 32

Release Notes — 12/7/2015
Key Summary Description

GEN-15478 Timer Service has a The MCAS Timer implementation, LPTimer, allows
maxDelay of 5 mins which timers to be added that exceed the internally
is not modifiable configured maximum period (default 5min). Prior
to this change, a timer period that exceeded the
maximum period was reduced to the maximum
period.

The system property “mcas.lptimer.bounded-

delay”, if set to true, reverts the LPTimer to the
previous behavior.

With this change, a mis-configured timer that

behaves as expected due to the bounded period,
can behave differently. Review all configured
timers are correct prior to installing this release.
Case# 02088059

GEN-15487 SAF commands to When an operator performs a SAF related

acknowledge and resend command on a UPF system containing many UPFs
are broadcast to all UPFs and databases i.e.system configured with 4 UPFs
rather than the UPF with and 4 databases, the system becomes unstable.
the associated endpoint Most, if not all databases can be deactivated,
having the potential to cause a full outage.

The resolution is for the 3 SAF related commands,

“Resend”, “Acknowledge” and “UnPause SAF” to be
configured to execute on only the UPF running the
active node.

GEN-15491 Asynchronous script Asynchronous script callbacks can cause problems

callbacks can cause in session builder resulting in strange session
problems in session behavior when asynchronous functions are used.
builder Fixed

GEN-15494 Syntax error in In previous releases of the UPF the generated

dynamically generated SNMP MIB file (using the ‘snmpmgmt’ command
SNMP MIB file line tool) contained a misplaced ‘}’ character
which prevented the importing of the MIB file into
standard SNMP management tools. This has been
fixed and the generated file will now have the
correct syntax.
Case# 02105523

UP Framework Release 3.2.2 33

Release Notes — 12/7/2015
Key Summary Description

GEN-15496 Audit is incorrectly The channel state changes have been corrected
reporting channel state and spurious audit evens are no longer reported
changes and filling the
Audit Log file

GEN-15500 Imported User Cartridge is Performing an 'activate' command through the

not loaded by the change log, or deploying user cartridges to a multi
remainder of the UPFs in instance platform now support activation of the
the platform new configuration across the entire platform
rather than just the instance initially signaled.

GEN-15521 Attached inbound Fixed session to ensure attached inbound logging

operations are lost when a
session cannot deliver a
message to issuer
operations are not lost on issuing channel loss.
The session now takes a copy of the operations
when sending outbound and will check if they are
restored on a channel loss (or timeout) if they
have not already been logged. This only works
when checkpointing is enabled as the session uses
the checkpoint table to determine if the message
was logged or not.
Case# 02088786

GEN-15524 SAF Panel in platform
manager is not updating
even after acknowledging
the records
SAF Panel in platform manager is not updating
even after acknowledging the records. The
acknowledge records were still shown confusing
users whether the record was acknowledged or
not. This issue has been fixed.
Case# 02117200

GEN-15534 Handle UPF configurations When errors occur during configuration changes,
getting out of sync in multi the UPF will always raise a restart required alarm
UPF environment on the target instance.
If a change has been made that targets version
*{{B}}*of the configuration, and an instance is
running version *{{A}}* of the configuration, UPF
will simply activate the configuration *{{B’}}*

GEN-15537 Unable to change session User Session Timeout under PCI DSS
timeout above 15 mins Authentication Policy is updated to allow
configuration of session timeout in the range from
1 minute to 15 minutes.

UP Framework Release 3.2.2 34

Release Notes — 12/7/2015
Key Summary
GEN-15550 Oracle Database Patch
Required with Oracle 12c
GEN-15557 Entity Builder – Handling
of sensitive data at the
role level not working for
RDBMS Entities other than
Log RDBMS Entities
GEN-15563 ‘Accessed disposed value’
error may be issued if
totals are used during file
load.
UP Framework Release 3.2.2
Release Notes — 12/7/2015
Description
When using the UPF with Oracle Database version
12c the patch for bug ID 19703301 must be
applied.
This patch was first included with…
* 12.1.0.2.4 (Jul 2015) Database Patch Set
Update (DB PSU)
* Subsequent PSU’s such as 12.1.0.2.5 Oct 2015
will also include it
* Or it can be individually acquired as a single
patch from this link
https://updates.oracle.com/download/19703301.h
tml
Please work with Oracle to obtain the appropriate
Oracle Database software patches.
Entity Builder now handles sensitive data levels
and role compensation controls for all RDBMS
entities. Previously only Log RDBMS entities were
handling that correctly.
If totals are updated during a file load, and the
usage type of the totals is ‘Mainly recurring
entries’, the ‘Accessed disposed value’ error may
be reported, which results in the failure of the
load.
When this type of totals is used, the updateTotal
function results first in an ‘update’ database
operation. If the operation failed because the
totals record does not exist, a retry will be
executed with an ‘insert’ operation followed by an
‘update’.
Due to an error in the code, the message variables
data is prematurely released before the retry
operation is performed, causing the reported error.
This problem has been fixed.
A work-around (before the fix) is to change the
usage type to ‘Mainly unique entries’, which
always enforced the ‘insert’ operation first.
Case# 02128360
35
Key Summary Description

GEN-15605 Changing an option may This outage caused by a deadlock condition has
create an outage when been fixed.
running a 4-stack Case# 02129350
installation (4 UPF
instances)

GEN-15612 Pending op returns too Ensure that all preceding transactions are
early committed on all active database before allowing
the switch application to read from one of them.
Case# 02134237

GEN-15649 Timeouts to re-used tasks Fixed session to check which session a task is
can be delivered to the associated with before delivering a timeout event
wrong session to it. This prevents old timers from being delivered
to tasks that have been re-used in a new session.
Case# 02139299

GEN-15663 UPP322: Fatal Error in In UP script, when a typed variable is not

Session and Unexpected 36initializer and then used, it can cause
Runtime Error unexpected errors. Types variables should be
assigned a default value if no explicit 36initializer
is provided.

GEN-15669 Async Configuration In asynchronous mode, the configuration

replication stream needs replication stream can have instability issues if an
to support replication in operator performs incompatible actions to UPF
both directions. internal tables. Once in this state the Golden Gate
replicat process continually ABENDS attempting to
replicate data to either mcas_files or
mcas_files_data tables.
The Golden Gate configuration files generated by
the UPF are more tolerant to data changes in
these tables.

GEN-15674 Occasional “No route A coding bug in the BSI endpoint with the pooling
found” safeguard when of route address objects can lead to a response
running load involving BSI message having the wrong route assigned to it.
traffic When the response message returns to the
originating endpoint to be sent back to the
originator the endpoint looks up the route and
discovers that the route does not exist on that
endpoint and an error is reported and the
message is dropped.

UP Framework Release 3.2.2 36

Release Notes — 12/7/2015
Key Summary Description

GEN-15680 NullPointerExecption in Fixed NPE when ext buffer fields was not set.
FileBasedAlarmReporterV2

GEN-15688 Config Builder, the move Moving up and down of entries in table was not
up and move down is not happening correctly, the order would not be maintained.
working correctly Problem has been fixed.

GEN-15716 The interval controlling This has been fixed and the rollover time can now
sdiag file rollover time be configured to a different value than the default
"com.distra.pm.sdiagfileint 1 hour rollover.
erval" does not work when
changed in switch.conf file

GEN-15788 Added new Entity Models
to ensure compatibility
with imported PIM entity
models
UPF now ships with two additional Entity Models to
enhance compatibility of the Service Registry with
the PIM (including imported PIM):
- PIM Primitives including all the primitive types
from PIM 1.5 and Service Registry
- PIM Common including the intersection of PIM
and Service registry (including the BASE24-eps
Business Services PIM)

GEN-15812 UPP_Seed_Data There was a dash missing in comments section for

oracle_autoprovision.sql oracle_autoprovision.sql which has been fixed.
has an invalid comment
Case# 02161657

GEN-15815 UPF on Windows now UPF installer has been enhanced to support
supports “rollback” from Rollback for Windows.
the 3.2.2 to 3.2.1-1
release

UP Framework Release 3.2.2 37

Release Notes — 12/7/2015
Section 3: Known issues

Key Summary Description

GEN-13601 When the UPF Scenario:

is deployed
A new configuration is applied to the UPF, requiring a
with the UPF
manual restart to make the configuration active. This
Desktop (that
action is only required when the configuration changes
is, in Core
cannot be applied in real-time (the majority of
Infrastructure
configuration changes can actually be applied in real-time
mode), the
and do not require a restart). After the restart, the actions
actions for
(if any) of the new managed resources do not show up in
some
UPF-Desktop.
resources may
not show in the Workaround:
UPF-Desktop
Go to Platform Manager and stop mcas/apsfmgt service
from Platform Manager (Platform > Services and Process
Tab).
Delete all the files present at following locations (Retain
the directory, only delete the files inside it):
<UPF_Installation_Dir>/install/<UPF_Version_No>/apsfm
gmt/configpath/*
<UPF_Installation_Dir>/install/<UPF_Version_No>/apsfm
gmt/storepath/*
Start mcas/apsfmgt service from Platform Manager
(Platform > Services and Process Tab).
Restart the UPF.

GEN-14583 UPF may not After a successful upgrade, the UPF may require the
shut down “switchctl stop” command to be executed a second time in
after upgrade order to shut down the UPF MCAS process.
Once executed a second time the UPF will terminate

GEN-15829 Endpoints BSI Endpoints that are generated by the BSI

generated from Configurations may be exposed in the Endpoints section
BSI within Configuration Builder. If these generated BSI
Configuration Endpoints are modified they become a concrete part of the
are visible as configuration. Any changes to the BSI Configuration for
Endpoints the modified Endpoints will be ignored.
Removing the BSI Endpoint from the 'Endpoints' section of
Configuration Builder will restore the expected behavior.

UP Framework Release 3.2.2 38

Release Notes — 12/7/2015
Section 4: Additional information

Release artifacts
This release includes:
• The UPF Installer:
UPF-3.2.2-installer.tar.gz (AIX/Linux) (sha256sum:
f2eaa6366ced093c692ad67df9cc0abbc0350c6edcf1c317ebfaa5897d97ce0a)
UPF-3.2.2-installer.zip (Windows) (sha256sum:
b710327e55115e0a72c500c67a5854b98bccc87ac8172b16110336146931a04b)
• The EUA (Configuration Builder and Platform Manager) installer:
AciEUAInstaller-3.2.2.jar (sha256sum:
c2199eb7eecae8fc3458fd048fe3c394c66ac32a8b413bdc702b37921c37fc19)
• The UPF External Libraries compressed files:
UPF-3.2.2-ExternalLibraries.zip (Windows) (sha256sum:
c5c7e946a7818b8bcd1fbe5fa4ec9a93658ad207ce38c348b863091dfd2bc872)
UPF-3.2.2-ExternalLibraries.tar.gz (AIX/Linux) (sha256sum:
ae8493049246c28ab3ac39a940140105c48003cf86af04bfa032d59afeb995f5)
• The ICEProbe Trace Viewing Utility Installer:
ICE Probe 32bit.zip (sha256sum:
57dd7dfeca4dcee906f6ce605709de8eb70e49e5a04848ed19c77933a373047e)
ICE Probe 64bit.exe (sha256sum:
c97f9115144be995848e545614763fc503800f35e52cbfa98a1466806ed108f7)
• The NetBeans zip file used for installation of end-user applications (for ACI internal
distribution only):
netbeans-platform-8.0.2.zip (sha256sum:
edbe4ee56fbfcbe0e5085d5b7a9a7ab2d31efb3aebf7b5349c78423d19d48695)

Installation of the UPF

UPF 3.2.2 is a standalone UPF installation and supports an upgrade as well as full
installation.
Follow the installation instructions provided in the 3.2.2 UPF Installation Guide for a new
install of the UPF.

UP Framework Release 3.2.2 39

Release Notes — 12/7/2015
Upgrading the UPF
Follow the upgrade instructions provided in the 3.2.2 UPF Installation Guide and review the
following for additional installation and upgrade information that may be applicable to your
environment.

Upgrade prerequisites
It is important to back up the databases and the configuration from existing UPF
environments before the upgrade. Before starting, ensure that the UPF is running and no
active alarms need to be addressed.
Please review the upgrade and rollback matrix contained in these Release Notes for support
upgrade and rollback paths.

UP F 3.2.1-1 and above requires a m inim um of Java 7

Customers must have a minimum of Java 7 installed before installing or upgrading to UPF
3.2.1-1 or above. Please refer to the UP Framework Platform and Sizing Guidelines for
additional information on supported platforms.

Legacy Business Services P I M and P OS Cartridge Backw ard

Com patibility
This note is applicable for those installations upgrading from a release prior to UPF 3.2.1-1.
With UPF 3.2.1-1 the UPF has been updated to ship with support for ACI Universal Payment
Information Model version. Previously the UPF shipped with a BASE24-eps Business Services
PIM which contained no support for other ACI products. This marks a significant change and
will enhance supportability and compatibility going forward.
As a result of this change the POS Entity Model shipped with UPF in versions 3.2-0 and
below has been removed. Both the POS Entity Model and the BASE24-eps compatible
Business Services PIM have been converted to User Cartridges that ship with UPF 3.2.1-1
and above but are not installed as part of the standard installation. New solutions which will
depend on these artefacts can simply import the cartridges post installation.
For existing installations, there may be some pre-upgrade steps that need to be taken to
ensure the success of the upgrade. Installation where any of the below statements is true
should contact the ACI UPF Support team for assistance upgrading:
• BASE24-eps integrated solution
• Custom Business Services PIM imported
• Custom PIM imported which depends on items in the ‘com.aciworldwide.sba’
namespace
• Solution has modified or extended the ‘POS’ entity model

If there is any doubt please contact the ACI UPF Support team for assistance.

UP Framework Release 3.2.2 40

Release Notes — 12/7/2015
The steps for upgrading one of the impacted solutions is outlined below. Given the upgrade
path may require the installation of User Cartridges to proceed successfully it may be
necessary to upgrade older installations of UPF to 3.2-0 first as this was the first release of
UPF to support the required cartridge management functionality.
• Upgrade to UPF 3.2-0-1
• Install the BusSvcsPim User Cartridge (BusSvcsPim-3.2-0-cartridge.jar) into the 3.2-
0 UPF
• Install the POS EP User Cartridge (POS-3.2-0-cartridge.jar) into the 3.2-0 UPF. This
step is only required if the solution has modified or extended the POS entity model
shipped with UPF versions 3.1-0 to 3.2-0-1
• Upgrade to your new version of UPF
The UPF 3.2.1-1 and above installer contains the 3.2.1-1 versions of the BusSvcsPim and
POS EP User Cartridges. To obtain the 3.2-0 compatible versions please contact ACI UPF
Support.

Default I P P orts for EUA Connection Changed

From release UPF 3.2, the default IP ports on which the EUA Tools (e.g., Configuration
Builder and Platform Manager) have been changed for new installations. For customers
upgrading from a previous release, the IP ports will remain the same. For additional
information, please refer to the tooltip and online help in the EUA tools.

Upgrading Configurations from earlier UP F versions

The recommended way of upgrading a configuration created prior to this UPF release is to
upgrade a running UPF platform. In some cases this may not be possible in which case the
configuration can be merged within Configuration Builder from a previous binary
configuration into the current UPF.
Please refer to the following Configuration Builder User Guide sections for further
information on importing, exporting and merging configuration:
• Import and export UPF configurations
• Compare and view changes between configurations

New license required w hen upgrading from releases prior to UP F

3.1-1 and change to Batch Toolkit as a new licensable m odule in
3.2.1-1 and above
With the introduction of the new licensing system, customers now need to obtain a new
license from ACI when upgrading from a release prior to UPF 3.1-1.
This new license needs to be installed as part of the upgrade process using the standard
license installation procedure.
In UPF Version 3.2.1-1 and above, the batch toolkit is a licensable module and must be
purchased and licensed for use; as a consequence a new license is required if this module is
to be used in UPF 3.2.1-1 and above.

UP Framework Release 3.2.2 41

Release Notes — 12/7/2015
Note: If a "rollback" to a previous version of the UPF is required, then the previous license
will need to be re-installed. Ensure that the previous license is backed up.

Upgrading from a previous release using Oracle Colum n Level TDE

With the introduction of large message size support in the UPF in version 3.1-0, customers
who use Column Level TDE need to change their system to use either disk-level encryption
or Oracle Tablespace TDE to encrypt sensitive data.
This is a requirement as Oracle Column Level TDE does not support blob field types that are
required for larger message sizes.
Contact ACI for additional information if you are an existing customer using Oracle Column
Level TDE and migrating to this release.

Upgrading from version 3.1-0 and 3.1-0-1

Upgrading from 3.1-0 and 3.1-0-1 to this release requires offline schema changes. Refer to
the “Offline schema changes” topic in the UPF Installation Guide for additional information
on this process.

Upgrading from UP F 3.2.1-1 to a new er UP F release on the

W indow s platform
When upgrading from 3.2.1-1 to a newer version customers need to contact ACI support
before attempting to upgrade on the Windows platform as their existing installation will
require a patch before upgrade.
Please contact ACI support if upgrading from UPF 3.2.1-1 on the Windows platform.

Upgrading from a previous release using the UP F Desktop w ith

BASE24-eps
The UPF supports version 1.4 and above of the UPF Desktop. Customers using the UPF
Desktop environment must first upgrade the UPF Desktop to a supported version before
installing this version of UPF.

I m provem ents to configuration property and field validation

Configuration property and field validation may be improved with new releases within
Configuration Builder and Entity Builder to assist users with the creation of valid
configurations.
This additional validation may expose existing errors in customer configurations that may
need to be amended.
The running UPF is not impacted by this change; however, if a configuration is changed in
this area on a running UPF, then the configuration properties in error will need to be
amended.

UP Framework Release 3.2.2 42

Release Notes — 12/7/2015
TCP/ I P port validation
TCP/IP port validation may impact customers who have TCP/IP ports configured greater
than 32767 for communication between the HAR and MCAS.
Previous behavior would allow TCP/IP ports to be configured above the 32767 range for HAR
to MCAS communications. This created issues as it clashed with the ephemeral port range
used by the operating system.
If your configuration uses port numbers outside of this range, then you need to update the
configuration before performing the upgrade process. The steps are as follows:
1. Obtain the current running configuration from the UPF using Configuration Builder.
2. Clone the existing route on the Endpoint Channel.
3. Delete the existing route.
4. Build a new route from the cloned route and set the UPF Port [RouteId] to use a port
within the valid range 1024-32767.
5. Apply the configuration to the running UPF.
Note: If your configuration is not updated, the upgrade will be successful but the UPF will
fail to start generating the error:
Attribute “switchPort” has illegal value “XXXXX”

UP Framework Release 3.2.2 43

Release Notes — 12/7/2015
Copyright information

UP Framework Release 3.2.2 44

Release Notes — 12/7/2015