Event Management 2018.1 Release Notes PDF

Release Notes
JDA® Event Management
Release 2018.1
Last updated: 8 March 2019
Legal notice
Rights to the content of this document
Copyright © 2018-2019 JDA Software Group, Inc. All rights reserved.

Printed in the United States of America.
Reproduction of this document or any portion of it, in any form, without the express written consent of JDA Software
Group, Inc. ("JDA") is prohibited.
These materials are protected by the Copyright Act of 1976, as amended, as an unpublished work and the foregoing
notice and legend shall not be deemed to constitute publication or an intent to publish thereunder. These materials
are proprietary and confidential information of JDA and may be disclosed and used only as authorized in a signed,
written agreement controlling such disclosure or use.
The fact that a particular name or logo does not appear on this notice does not constitute a waiver of any intellectual
property rights that JDA has established in any of its products, feature or service names, or logos.
Trademark, Registered, and Service Mark notices
JDA is a registered trademark of JDA Software Group, Inc. JDALearn is a service mark of JDA Software Group, Inc.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. SAP and SAP HANA are trademarks or
registered trademarks of SAP SE in Germany and in several other countries. Microsoft, Encarta, MSN, and Windows
are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Autodesk and Revit are registered trademarks or trademarks of Autodesk, Inc., in the USA and other countries. All
other product names and company names may be the trademarks/service marks or registered trademarks/service
marks of their respective owners.
Throughout this document, certain designations may be used that are trademarks that identify the goods of third
parties. Although this document attempts to identify the particular trademark owner of each mark used, the absence
of a trademark symbol or other notations should not be taken as an indication that any such mark is not registered or
proprietary to a third party. Use of such third-party trademarks is solely for the purpose of accurately identifying the
goods of such third party. The information contained herein is subject to change without notice.
Modifications to the contents of this document
JDA reserves the right, at any time and without notice, to change these materials or any of the functions, features,
and specifications of any of the software described herein. JDA shall have no warranty obligation with respect to
these materials of the software described herein, except as provided in the JDA software license agreement with an
authorized licensee.
Rights to the functionality of this document
Described functionality may not be available as part of a customer's maintenance agreement or the JDA Investment
Protection Program. New features and products are subject to license fees. JDA warranty and support obligations
apply only to the documentation as delivered by JDA, and are void if the documentation is modified or supplemented
by anyone other than JDA. This document embodies JDA valuable trade secrets, is confidential to JDA, and must be
kept in confidence and returned upon the expiration or termination of your JDA license agreement. You are not
permitted to copy, extract, distribute, transfer, or share the contents of this document with anyone except authorized
individuals within your organization.
Technical documentation
NOTICE: This design or technical documentation is supplied as a courtesy only and does not form part of the
"Documentation" as defined in your JDA license agreement. This design or technical documentation is supplied in the
English language only and is supplied "as is" and without warranties. JDA, at its discretion, may choose to offer this
document in additional languages, but is under no obligation to do so. JDA undertakes no obligation to update this
design or technical documentation.
Patents
This product may be protected by one or more United States and foreign patents. Please see the JDA Patents website.
Provide feedback on this document
JDA values your opinion and strives to ensure that the documentation you receive is clear, concise, and
provides the appropriate information required for you to use each JDA application efficiently.
If you would like to provide feedback on this document, you can submit your questions or suggestions to
the JDA Documentation Management team and they will be forwarded to the appropriate development
teams for review and consideration in a future release.
In addition to the provided documentation, many additional resources are available to help you understand
and work with your JDA applications. For more information on these resources, see the JDA Services
website.
Table of Contents
Chapter 1. Release overview 1
Event Management enhancements 1
2018.1.2.0 1
Enforce a single login for an SCE application 1
Expire a session after a password change 1
Single user account supports both OpenID Connect and application authentication 2
User authentication through PingFederate integration 2
Extensions 2
2018.1.1.0 3
Extensions 3
2018.1.0.0 4
Case Insensitive Passwords policy now disabled by default 4
Page Builder page health check and portal server communication monitoring available under
new menu 5
Save default state button now an icon 5
User password format policies now enabled for better password security 5
Extensions 6
User documentation 8
Shared applications enhancements 9
2018.1.2.0 9
MOCA 9
2018.1.1.0 9
Monitoring and Diagnostics 9
2018.1.0.0 10
MOCA 10
Chapter 2. Installation and upgrade 12

Technical specifications 12
Required hotfixes 13
New client installation application 13
New portal server installation application 13
Installation package name changes 13
Installation notes 14
Discontinued support for Windows Server 2012 R2 14
Oracle Database driver requirement 14
Removal of RPUX product layer 14
One portal server instance per server 15
Web archive files no longer deployed to LES directory 15
Integration overview 15
Chapter 3. Resolved issues 16

Event Management 16
2018.1.2.0 16
2018.1.1.0 16
2018.1.0.0 16
Shared applications 16
2018.1.2.0 16
2018.1.1.0 16
2018.1.0.0 16
MOCA 16
MOCA client 17
Portal server framework 18
Chapter 4. Information alerts 19
2018.1.0.0 19
Portal server framework 19
Certificate issues identified for HTTPS over TLS clustered configurations 19
Chapter 1. Release overview

This chapter provides information on the JDA Event Management 2018.1 release.
Event Management enhancements

This section describes the new features introduced in Event Management.
2018.1.2.0
Enforce a single login for an SCE application
Starting with the 2018.1.2.6 release, the application has been enhanced with the ability to ensure that a
user can only be logged into a single portal server web client and a single SCE client at a time. The following
configuration options support this enhancement:
l Single web client login for portal server: The configuration option, singleSessionPerUser, is
available in a new portal server application installation or upgrade. If this option has a value of true,
when a user attempts to log in to a web client, the application verifies whether the user is already
active in a current session. A single session can include multiple tabs opened in the same browser. If
so, then the portal server application prevents the user from logging into a second web client.
Note: This option limits all users, including super users, to a single web client login.
If the option has a value of false, then during the log in attempt, the portals server application does
not verify whether the user is already logged into another web client, and the user can log in to
multiple web clients simultaneously.
For a new portal server application installation, the singleSessionPerUser option has a default value
of false. To enable this feature, you must manually update the settings/rpweb.xml file to include
the option with a value of true.
l Single SCE client login: The configuration, concurrent-dlx-sessions-config=block, is available in a

new application server installation or upgrade. When added to the registry file under the
SECURITY section, the application server verifies whether the user is already logged into another
SCE client. If the setting does not exist in the registry file, or has a value other than block, the
application server instance allows multiple logins to the SCE client.
Note: This setting does not prevent super users from logging into the SCE client multiple times.
For a new application server installation, to enable this feature, you must manually update the
registry file by adding the concurrent-dlx-config=block setting under the SECURITY section.
Note: Enforcing a single login is not available for Web Enablement applications, voice devices, or other
third-party devices.
Expire a session after a password change

Starting with the 2018.1.2.3 release, you can now define whether an SCE client or Web Enablement
application expires a user's session when the password associated with a user account is changed. When a
session expires, the user is logged out of the application. To resume the session, the user must log in using
the new password. This feature is enabled or disabled by the following policies:
JDA Event Management Release Notes 1

© Copyright 2018-2019 JDA Software Group, Inc. - Confidential
l Revoke User Session on Password Change: This policy is disabled when a new application
server instance is installed. You can configure the Revoke User Session on Password Change policy
in Policy Maintenance in the SCE client window.
l Revoke Session on Password Change: This policy is enabled when a new Web Enablement
server instance is installed. You can configure the Revoke Session on Password Change policy in the
Admin Console under Session.
In addition, when a user's password is changed in portal server, the user is automatically logged out of the
portal server application. This action is not configurable.
Single user account supports both OpenID Connect and application

authentication
Previously, you could configure a Supply Chain Execution (SCE) user account for OpenID Connect
(OIDC) authentication; however, the user was limited to web sign on to portal server applications. If the
user also required access to the SCE client and RF devices, a second user account was required that used a
password to authenticate the user through the application.
Now, you can configure a single SCE user account to use both OIDC authentication for the web client and
application authentication for the SCE client and RF devices. OIDC authentication can be performed
through a customer's Identity Provider (IdP) using OpenID Connect and OAuth 2.0 standards. To enable
both OIDC and application authentication for a single user account, a system administrator must update
the portal server instance configuration file to perform user authentication using the IdP and configure the
SCE user account for both application and OIDC authentication.
Note: You can still define an SCE user account to use external authentication only with OIDC
authentication to limit the user to web sign on.
For more information about user authentication configuration, see the Supply Chain Execution
Applications Administrator Guide.
User authentication through PingFederate integration

User authentication for SCE applications web sign on can now be performed through a PingFederate
integration using a customer's Identity Provider (IdP). PingFederate provides browser-based Single Sign On
(SSO) to provide authentication for a portal server instance.
To enable authentication with PingFederate, the portal server's configuration file settings must be updated
by a system administrator and SCE user accounts must be defined in the SCE application. For more
information about user authentication configuration, see the Supply Chain Execution Applications
Administrator Guide.
Note: You can configure a single SCE user account to use both PingFederate authentication for the web
client and application authentication for the SCE client and RF devices. See "Single user account
supports both OpenID Connect and application authentication" (on page 2).
Extensions
This section introduces the new features related to the extensions functionality.
Ability to modify drop-down list and lookup fields

Starting with the 2018.1.2.2 release, for Page Builder form and grid type pages, you can now use Field
Editor to modify the configuration of drop-down list and lookup fields so that the field is displayed as an
alternative field type. For example, a lookup field type can be displayed as either a drop-down list or text
box, and a drop-down list field type can be displayed as a text box.

Drop-down list and lookup fields are configured in the Configurable Web Service resource and linked actions
that comprise a web service associated to a Page Builder page. Rather than modifying the web service
resource or actions to change the field type, you can use Field Editor to modify the field configuration with
the following attributes:
l Field Type: Determines the type of control in which the field is rendered, such as a text field, drop-
down list (referred to as a combo box), or lookup field.
l Validate Data: Requires that users enter a value that matches one of the allowed values defined
by the Configurable Web Service resource and linked actions. For example, you can configure a
lookup field to be displayed as a text box and still require that the user enter one of the valid values
from the lookup. This attribute is available when the Text Field field type is selected.
Page Builder supports adding external pages

Using Page Builder, you can now add an external type page to embed additional web-based content within
a portal server web client. An external type page supports an iframe (a frame within a page) that displays
URL content, such as a web page or a web-based application.
Note: The server on which the portal server instance is installed, or the portal server instance itself, may
be configured with security restrictions (such as content security policies or protocol restrictions) that
prevent content from being displayed in an embedded iframe. A system administrator may need to
update the server security settings or the portal server instance configuration settings to allow external
content to be displayed within the web client.
After the page is added to a menu using the Menu Editor, you can view and interact with the web page or
application without having to log out of the web client.
Page Builder supports drop-down list and lookup fields

Page Builder form and grid type pages can now display values in drop-down list or lookup field types, when
the page is sourced from a web service built using the Configurable Web Services framework. These field
types are configured within the resource and linked actions that comprise the web service.
The Configurable Web Services framework includes a new foreign key (fk) element (belonging to the
property element within an XML-based resource) that provides the metadata required by the Page Builder
Discoverability API to enable these field types. A configuration on the resource's LIST action controls
whether the field is displayed as a drop-down list or lookup.
For information about the Configurable Web Services enhancement, see "Configurable Web Services
support modeling relationships between resources" (on page 9).
2018.1.1.0
Extensions
Batch Actions Summary Report

Page Builder grid type pages configured with batch actions now display a summary report when one or
more actions in the batch fails to execute. The Batch Actions Summary Report window displays a list of all
actions or the actions that failed (optionally). When you highlight an action in the list, information relating
to the selected action is displayed that describes either the completed successful action or attributes of the
failed action.
The Batch Action Summary Report window is not displayed if all actions in the batch are completed
successfully.

Export grid data on Page Builder grid type pages

You can now export grid data from Page Builder grid type pages. The export icon is displayed on a grid
type page so that you can export data to the following file types:
l CSV (comma-separated value) file that can be opened in Microsoft Excel or other spreadsheet
programs
l PDF (portable document file) that can be viewed in Adobe Reader or other PDF readers
When a grid type page includes both parent and child grids, you have the option to export one grid or both
grids to either format. When you export multiple grids, the data from each grid is exported to its own file.
Before exporting grid data, you can limit and modify the information that is displayed by filtering the
information or modifying the grid.
The export icon is displayed on all grid type pages added using Page Builder.
Page Builder grid type page filter field supports multiple values
For Page Builder grid type pages, you can now access a window from a filter field that lets you enter a value
for multiple attributes. Previously, you had to enter a value for one attribute at a time. If you required
multiple values to filter the information, you had to enter each criteria (value and attribute
combination) separately.
Now, when you click the filter field, the Filter using multiple fields button provides access to a window
that displays all available attributes for use within the filter. You can enter one or more values and filter the
information in one step. The filters are displayed in the Ad-hoc filter area, and the displayed information
is limited by the indicated criteria.
This feature is compatible with the filter field configuration. When a page includes a filter field
configuration, an asterisk (*) is displayed by each attribute that is required to indicate that a value must be
entered for that attribute to display information in the grid.
You can save the ad-hoc filter for use on the page in the future. Saved filters can be identified as favorites,
and can be accessed quickly using the Load Saved Filter button.
2018.1.0.0
Case Insensitive Passwords policy now disabled by default
For a new Supply Chain Execution (SCE) application installation, the Case Insensitive Passwords policy is
now disabled by default. The Case Insensitive Passwords policy converts all alpha characters in a user-
entered password to uppercase, removing the requirement for case-sensitive validation of a password. This
policy was disabled as it conflicts with the Format Rules Progression policy that is now enabled to verify
password complexity. See "User password format policies now enabled for better password security" (on
page 5).
IMPORTANT: Based on the updated default policy settings, you are now required to match the case
when entering the password for the SUPER user account. If you do not know the password, contact your
JDA project team.

Page Builder page health check and portal server communication

monitoring available under new menu
An Administrator can now view health checks for Page Builder page configurations and the details of portal
server node communications using the Monitor page. The Monitor page displays the following links:
l Health Checks: Displays a list portal server framework health checks that verify whether the Page
Builder pages are functional and supported by the selected web service resources. A health check is
a test or check that assesses an application's state, configuration, or data.
l Download Support Zip: Downloads the portal server support ZIP file, which contains files that
help you resolve system issues during troubleshooting.
The Monitor page also displays all portal server instance connections to other nodes in a network diagram.
A node is a single installed instance that may be combined on a network with other nodes to make up a
cluster. The diagram includes portal server, application server, and proxy server or load balancer nodes.
You can select a node to view more information. For example, for a portal server node, you can view
detailed configuration files, such as the rpweb.xml, and information about the physical server on which
the portal server instance resides.
You can find the Monitor page under the SYSTEM MANAGEMENT menu.
Save default state button now an icon

The Save Default State button is now an icon . The functionality of the button has not changed.
Note: The save default state icon is only available on pages that contain state-enabled components,
such as a grid, and is only available to super users.
User password format policies now enabled for better password security
With the increased focus on securing user access, Administrators are routinely responsible for
implementing secure password standards. To assist with quickly establishing these standards, a new
application server installation now enables the Format Rules Progression policy. This policy validates the
format of a new or modified password using commands that check whether the following criteria are met:
l Complexity: Does the password have the required upper and lowercase letters, numbers, and
symbols?
l Minimum length: Does the password meet the minimum length requirement?
l Reused recently: When a password is changed, is the new password a repeat of a previous
password?
If any of the above checks fail, the password is rejected. To support these password checks, the following
policy data is distributed:
l History Check Parameters policy: Controls how often a user can repeat a password within a given
time period using the following values:
o Previous Passwords to Check field default value is 6. For example, a user cannot repeat
any of the last 6 passwords that were used.
o Previous Days to Check field default value is 356. For example, a user cannot repeat a
password used within the last 356 days.
l Minimum Length Check Parameters policy: Defines the minimum number of characters that are
allowed. The Minimum Length field default value is 8.

Note: The Format Rules Progression policy is not enabled when an application server instance is
upgraded.
You can configure the Format Rules Progression policy and related policy data in Policy Maintenance within
the SCE client window.
Extensions
Configurable Web Services support batch operations

The Configurable Web Services framework is updated with a new action type, BATCH, to support batch
operation processing between the web client and application server. BATCH actions can be configured to
execute the same action against multiple records or entities with a single HTTP request to the MOCA
server. A single Configurable Web Services resource can be configured to include multiple BATCH actions.
Previously, the Configurable Web Services framework supported only a single Create Read Update Delete
(CRUD) action per web service call.
The MOCA server sends a response that includes a status for each time the action was processed in the
batch, either a success or failure. If the application server fails to process the batch, such as the request
cannot be read, or the batch from the client is too large, the MOCA server sends an error message to the
web client.
This enhancement supports Page Builder grid type pages batch actions. Now, when using a Configurable
Web Services resource for a Page Builder grid type page, you can configure the page attributes to display
the batch action option in the Actions drop-down list and to map the database values to the web service
endpoints. For more information about batch type actions on grid type pages see "Page Builder grid type
pages support batch actions " (on page 8).
Data loading options for Page Builder grid type pages

Page Builder grid type pages now support auto load and filter field configurations. The configurations let you
determine whether grid data is loaded when the page is opened. You can also configure which columns
must be used as search criteria for retrieving data into an empty grid. These configurations can be used to
enhance performance by limiting the amount of data that is loaded into a grid and when the data load
occurs.
In grid configuration, you can configure a filter field using one of the following approaches:
l You can turn off the option to automatically load data in the grid when the page opens. With this
configuration, the page displays an empty grid and the user is required to enter search criteria. The
user has the flexibility to pick any attribute in the filter field to create an ad-hoc filter.
l You can select the filter field search criteria that the user is required to use. With this configuration,
the page displays an empty grid with a message that indicates the required search criteria. The user
enters a value and selects the indicated attribute from the filter field to create an ad-hoc filter.
In either configuration option, a user can save the ad-hoc filter for use on the page in the future. Saved
filters can be identified as favorites and can be accessed quickly using the Load Saved Filter button.
Import pages built using Page Builder in the web user interface

In Page Builder, you can now import a page into an instance using the web user interface (UI). Previously,
the process of importing a Page Builder page involved multiple steps that were performed manually to load
the data in both the portal server instance and the application server instance. If the page was part of a
menu, you had to separately export the menu data using Menu Editor and repeat the steps to import the
menu data.

Now, Page Builder includes the following import and export feature enhancements:
l Automated import process: A new import icon ( ) is available to support an automated import
process. The import process validates that a selected ZIP file contains the required folders and files,
and deploys the page, menu, and configuration files into the portal server instance, and if applicable,
deploys Configurable Web Service resources into the application server instance.
l Export ZIP file includes menu and resource data: To support the automated import process,
the export process now includes the associated menu data (if applicable) and the Configurable Web
Services resources (if used to support the page) in the ZIP file.
Note: The export process only copies Configurable Web Service resources. If the page that you
are exporting is supported by a user-defined Java-based web service, you must transfer the web
service files from one instance to another manually.
Page Builder supports adding and modifying form type pages

In addition to grid, chart, and dashboard pages available in Page Builder, you can now add or modify a form
type page and use the Menu Editor to add the page to a menu. A form type page supports performing a
single action, such as printing a label, and requires a configurable web service action to provide the data for
the page. The action must be available to the Page Builder Discoverability API, either within a web service
resource, or as a standalone web service.
After the page is added to a menu, you can view the page, define additional page layout configurations
including the context in which the page is displayed, and define the following page attributes:
l Whether the layout is 1 or 2 column format
l The fields that are displayed and how each field is configured
l The position of each field on the page
Note: Page Builder also adds form type pages to support the add and edit actions of a grid type page;
however, the form type page that is associated with the grid type page cannot be added to a menu and is
removed when the grid type page is deleted.
Page Builder chart type pages support expanded data resources

For Page Builder chart type pages and chart widgets displayed in a dashboard type page, chart values
support navigation to one or more pages that expose APIs, such as Page Builder pages. However, when the
resource that supports the chart type page only provides summary data, the navigation links do not
contain enough data to support usable ad-hoc filtering on the destination page.
To support meaningful context navigation from a chart, you can now select a full data resource for a chart
type page and map the summary chart and full data resource properties. After a full data resource is
selected, each chart resource property is displayed as a drop-down list. The full data properties displayed in
each drop-down list match the data type of the chart summary resource. For example, if the chart
summary resource property is Item, only string data type properties from the full data resource are
displayed in the list.
A full data resource is user-defined either as a JAVA-based web service written using the MOCA web service
framework, or a configurable web service that uses MOCA components, commands, and configuration files.
See the information on web services and configurable web services in the MOCA Developer Guide.

Page Builder grid type pages support batch actions

You can now configure one or more batch actions for a grid. A batch action is a task that a user can perform
on multiple rows in a grid simultaneously, rather than having a separate action performed for each record.
You select multiple rows, and then select the action from the Actions drop-down list to display a page on
which you perform the action in batch.
Batch actions are defined within a resource that is associated to the grid as part of the configurable web
services framework and must be configured in the page attributes to display on the grid. The name of the
batch action displayed in the Actions drop-down list and the name of the batch action page is based on the
definition in the page resource. The batch action page provides the fields needed to complete the action,
and standard functions including the ability to display selected records within a batch and the ability to
update a single record within the batch.
For more information about the Configurable Web Services support, see "Configurable Web Services
support batch operations" (on page 6).
Page Builder grid type pages support parent and child grid configuration
Page Builder grid type pages now support a multiple (parent and child) grid layout. The parent and child
layout displays two grids on one page, such as a parent grid displaying orders and a child grid displaying
order lines. When you select a row in the parent grid, the related child grid data is displayed. To support this
feature, Page Builder has the following new enhancements:
l Child grid configuration: When you add or modify a grid type page, you can access child grid
configuration to select a resource for the child grid, and then map resource properties between the
child and parent grids to support loading data into the child grid.
Note: A resource is a web service endpoint that provides the data used in the grid. A grid can be
supported by one of the distributed resources or a user-defined resource. See the information on
web services and Configurable Web Services in the MOCA Developer Guide.
l Parent child grid configuration: After a grid type page using the parent and child layout is added
to a menu, you can access parent and child grid configuration to set the page context, set the grid
alignment, determine the size ratio of parent to child grid display, and access the standard grid
configuration attributes for both the parent and child grids.
Parent and child grid configuration can be applied to any grid type page.
User documentation
This section lists user documents that are either new or revamped for this release.
Supply Chain Execution Applications Administrator Guide

The Supply Chain Execution Applications Administrator Guide is now available. An Administrator can use
this guide to configure application server and portal server features after a successful installation or
upgrade. This guide includes separate chapters for each type of server instance with relevant configuration
tasks and settings, and a chapter that describes system-wide configuration, such as setting up an external
user authentication method.
MOCA Developer Guide
The information relating to application server instance configuration, such as configuration files, clustering,
and security is now added to the Supply Chain Execution Applications Administrator Guide and will no
longer be published in this guide. The MOCA Developer Guide content now supports development tasks
only, such as developing components and applications in Java and C, developing Configurable Web
Services, and extending database tables.

MOCA technical guides
The MOCA Configuration Guide and MOCA Diagnostics Guide are discontinued, because the content is now
added to the Supply Chain Execution Applications Administrator Guide.
MOCA Console User Guide

The MOCA Console User Guide is renamed to the Supply Chain Execution Applications Console User Guide.
Shared applications enhancements

This section describes the technical enhancements that were designed to enhance server performance,
development processes, and implementations. While the following enhancements may ultimately affect
what end users can see and do within their applications, they are of primary interest to developers and
project teams.
2018.1.2.0
MOCA
Configurable Web Services support modeling relationships between resources
The Configurable Web Services framework includes a new element that allows resources to model
relationships by referencing other resource properties as foreign keys. The fk element now allows you to
specify a resource ID and resource property to create a relationship between two or more resources.
When a web service built using the Configurable Web Service framework is used to source a Page Builder
form or grid type page, this enhancement enables either a drop-down list or lookup field for the resource
property data. These field types are configured within the resource and linked actions that comprise the
web service. The following two configurations are available:
l If the resource is linked to a LIST action with no listConfig properties specified, the values are
displayed in a drop-down list field.
l If the resource is linked to a LIST action that is configured with the filterable listConfig property, the
values are displayed in a lookup field.
For more information about using the fk element when developing Configurable Web Services resources,
see the MOCA Developer Guide.
2018.1.1.0
Monitoring and Diagnostics
Monitoring and Diagnostics version 4.2 supports Zabbix version 3.4
Monitoring and Diagnostics (M&D) version 4.2 is available and supports integration with Zabbix version
3.4. For more information about the Zabbix version 3.4 enhancements, see Zabbix documentation.
The Monitoring and Diagnostics Zabbix Integration Guide and Monitoring and Diagnostics User Guide are
released with an updated version number, 2018.1.1.0, in support of the M&D version 4.2 release.

2018.1.0.0
MOCA
Simplified JMX integrations using standard Java RMI endpoint
In addition to registering a JMX server using the "/admin" endpoint, MOCA now supports Java's default
"/jmxrmi" endpoint. Using the standard Java RMI endpoint for JMX simplifies JMX integrations by allowing
you to use a simplified URL, <Host>:<RMI Port>.
Configurable Web Services support import and export web service functionality
The Configurable Web Services framework is updated with import and export web services for importing
and exporting resources and actions associated with Page Builder pages. These web services support the
Page Builder import and export functionality and are also exposed through web services directly.
Note: The Configurable Web Services import and export web services are only available for resources
and actions that are available as defined in the $LESDIR/data/ws directory.
Configurable Web Services support batch operations

The Configurable Web Services framework is updated with a new action type, BATCH, to support batch
operation processing between the web client and application server. BATCH actions can be configured to
execute the same action against multiple records or entities with a single HTTP request to the MOCA
server. A single Configurable Web Services resource can be configured to include multiple BATCH actions.
Previously, the Configurable Web Services framework supported only a single Create Read Update Delete
(CRUD) action per web service call.
The MOCA server sends a response that includes a status for each time the action was processed in the
batch, either a success or failure. If the application server fails to process the batch, such as the request
cannot be read, or the batch from the client is too large, the MOCA server sends an error message to the
web client.
This enhancement supports Page Builder grid type pages batch actions. Now, when using a Configurable
Web Services resource for a Page Builder grid type page, you can configure the page attributes to display
the batch action option in the Actions drop-down list and to map the database values to the web service
endpoints. For more information about batch type actions on grid type pages see "Page Builder grid type
pages support batch actions " (on page 8).
Console Log Files page update

The Console Log Files page now includes a check box next to each log file displayed on the page. This user
interface enhancement provides visibility that individual files can be selected and makes it easier to select
the individual files that you want to download at one time.
Previously, you could select multiple rows by pressing the Ctrl key and highlighting the desired rows.
Groovy script execution limited to Administrator roles

To reduce any security threats that could be posed by a Groovy script being sent from the client to an
application server, the adhoc script execution is now limited users with Console Administrator access.
Private session salt configuration

You can now configure a private session salt, so that the session keys generated by an application server
are unique. A salt is random data that is used as additional input to a generated session key. Setting the
salt to a unique value per instance helps protect the instance against request forgery attacks. The
session.private-session-salt registry file setting is added to support this configuration.

Session Security health check

The Session Security Check is now available to support the private session salt configuration. This health
check verifies that the security domain is configured with a public and private portion, and that there is a
session salt configured. The private portion of the domain and the session salt are components of the
session key that are known only to the application server instance, so setting these components to unique
values helps protect against request forgery attacks.
Health checks are a Monitoring and Diagnostics feature that can be run and viewed on the System Health
Checks page in the Console.

Chapter 2. Installation and upgrade

This chapter provides version-specific installation notes for Event Management. Review these notes in
addition to the Event Management Installation Guide.
Technical specifications
The following table provides an overview of the supported configurations for Event Management. For a
detailed list of system requirements, see the Event Management Installation Guide.
Component Supported configurations

Platform Not applicable
version
Server OS l IBM AIX 7.2 Technology Level 2 or later

l Red Hat Enterprise Linux 7.4 (64-bit)
l Microsoft Windows Server 2016 (64-bit)
Client OS l Windows 7 Service Pack 1 (64-bit)

l Windows 8.1 (64-bit)
l Windows 10 (64-bit)
Database l Oracle 12.2 (64-bit) (Standard or Enterprise) with or without Real Application
Clusters (RAC)
l SQL Server 2016 Service Pack 1
l SQL Server 2014 Service Pack 2
Application Not applicable

server
Middle tier Not applicable
Web server Not applicable
Portal server l Google Chrome

browser
l Internet Explorer 11
l Microsoft Edge
l Mozilla Firefox 52 or later
l Safari 10 or later
LDAP server Not applicable
Client Chinese (Simplified), Dutch, English (U.S.), French, German, Italian, Japanese, Korean,
languages Portuguese (Brazilian), Russian, Spanish
Note: The available version associated with each language may vary. Contact JDA
Support for the latest information on the language versions that are available.
Help English (U.S.)

languages

Required hotfixes
Contact JDA Support and request the required hotfixes implemented since the release, if any. If hotfixes
are required, after installing a new instance or upgrading an existing instance, you must install the
hotfixes. Follow the installation instructions that are included with each hotfix.
New client installation application

The JDA SCE client installation application has been completely rebuilt to provide an enhanced user
experience.
Along with a clean, modern appearance, the installer displays a progress pane that lists each step in the
installation process. Indicators show the steps that have been completed (green) and the user's current
location (yellow) in the process.
The client installation package provides a new sample properties file (Client.properties) that can be
configured for performing unattended (silent) installations.
The client installer is built using the same technology as the new portal server Windows installer, providing
a consistent user experience for Windows installations.
New portal server installation application

The JDA SCE portal server installation application has been completely rebuilt to provide an enhanced user
experience for Windows and UNIX installations.
In Windows, the installer displays a progress pane that lists each step in the installation process. Indicators
show the steps that have been completed (green) and the user's current location (yellow) in the process.
The new portal server installer requires fewer data entries from the user. For example, the installer no
longer prompts the user for the following information:
l Warehouse Reporting: Installed automatically.
l Stash and static content server URLs: Set based on the instance's server and port number.
l Authentication type: Set to Native.
The portal server installation package includes a new sample properties file for Windows
(PortalServer.properties) and for UNIX (portal-UNIX.properties) that can be configured for performing
unattended (silent) installations.
The portal server installer is built using the same technology as the new client installer, providing a
consistent user experience for Windows installations.
Installation package name changes

The names of the JDA SCE installation packages, distributed as compressed (ZIP) files, have been changed.
The new naming convention clearly indicates the installer type (application server, portal server, or client)
and operating system (AIX, Linux, or Windows). In addition, the application server and portal server
installations for UNIX are now packaged separately, as they had been for Windows.

The SCE installation packages are now distributed with the following file names:
l For AIX
o Application server: sce_server_aix7.2-powerpc_<Version>.zip
o Portal server: sce_portal_aix7.2-powerpc_<Version>.zip
l For Linux
o Application server: sce_server_linux3.1-x86_64_<Version>.zip
o Portal server: sce_portal_linux3.1-x86_64_<Version>.zip
l For Windows
o Application server: sce_server_win_<Version>.zip
o Portal server: sce_portal_win_<Version>.zip
o Client: sce_client_win_<Version>.zip
Installation notes
Discontinued support for Windows Server 2012 R2
Windows Server 2012 R2 is no longer supported as a server operating system for application versions
2018.1.0.0 and later. JDA will continue to support Windows Server 2012 R2 for existing customers
according the JDA Solution Investment Policy.
Oracle Database driver requirement

JDA no longer provides the Oracle Java Database Connectivity (JDBC) driver with the SCE installation
package. As a result, when using an Oracle database, you must ensure that the proper version of the
Oracle JDBC driver resides in a directory on the server on which you plan to install or upgrade the
applications.
Note: The JDBC driver is included with an Oracle Database or Oracle Database Client installation. So if
the Oracle database is installed on a separate server, the JDBC driver file can be copied to a directory on
the application and portal server, or the Oracle Database Client can be installed on the application and
portal server to provide the JDBC driver.
During an application or portal server installation or upgrade, if the user selects Oracle as the database
type, then the user is prompted for the path to the directory that contains the JDBC driver. The installation
will not continue without a valid path to the required JDBC driver.
Removal of RPUX product layer

To simplify platform installation and maintenance, SCE application and portal server installations will no
longer include an RPUX product layer. This means that RPUX directories and registry entries will no longer
be included in an SCE product installation.
Previously, the RPUX directory was installed in the application server's instance directory and the portal
server's rpweb/deploy directory.
No functionality changes are associated with the removal of the RPUX directories. Instead, all required
functionality that was provided by the RPUX layer is now available to SCE products from a different product
layer (MCS, MOCA, or REFS).

One portal server instance per server

JDA supports the installation of one portal server instance per server; the server can be either a physical or
virtual server. The installation of multiple portal server instances on the same physical or virtual server is
not supported.
Web archive files no longer deployed to LES directory

Starting with the 2018.1.2.1 release, product web archive (WAR) files are now loaded directly from each
product’s own webdeploy directory and are no longer also deployed to the LES directory.
Specifically, the wsdeploy.exe file has been modified to no longer copy WAR files to the
$LESDIR/webdeploy directory. In addition, the wsdeploy.exe file has been reconfigured to remove
the WAR files from the $LESDIR/webdeploy directory that had been previously deployed there.
Integration overview
Event Management supports integration with the following applications:
l Integrator (Supply Chain Execution)
l JDA Track & Trace
l JDA Warehouse Labor Management
l JDA Warehouse Management
For detailed information on the integrations, see the appropriate integration or installation guide.

Chapter 3. Resolved issues

Event Management
This chapter describes the issues that have been resolved in this release of Event Management.
2018.1.2.0
Resolved issues are published in a separate document with each 2018.1 release. See the 2018.1 release
schedule and Supply Chain Execution Applications Release Notes of Resolved Issues on the JDA Support
website.
2018.1.1.0
website.
2018.1.0.0
There are no resolved issues in this release associated with a customer case.
Shared applications
2018.1.2.0
website.
2018.1.1.0
website.
2018.1.0.0
MOCA
Case ID
Resolved issue
(Defect ID)
1026398 MOCA RESTful web services and Configurable Web Services will now return an
error response body which provides support for multi-byte languages. MOCA
(MOCA-8422)
will continue to return a response reason phrase to maintain backwards
compatibility.
1036407 Jobs and Tasks can once again correctly use custom logging appender
overrides.
(MOCA-8424)
1056323 Handle connection so that it does not create concurrent connections.

(MOCA-8562)

Case ID
Resolved issue
(Defect ID)
1073739 Fixed timing issue when session context could be prematurely closed, which
could leave uncommitted transaction.
(MOCA-8585)
1091535 Fixed several memory leaks with C-based mocaxml library.

(MOCA-8529)
1092566 Threaded tasks that are configured to auto-restart on failure will no longer fail
to restart after failing to update the start or end date of the task.
(MOCA-8559)
1140146 Discontinued the use of Java's Unicode canonical equivalence regex option in
MOCA's query restriction subsystem because Java has outstanding defects
(MOCA-8633)
which make it unreliable.
1140662 Upgraded Groovy version from 2.4.8 to 2.4.15 to include latest Groovy bug fix
for possible deadlocks (https://issues.apache.org/jira/browse/GROOVY-8067).
(MOCA-8589)
(MOCA-8373) The server.arg-blacklist registry setting can now be used to specify arguments
that should not be shown in any visible command or sql statement visible in
mbeans or the Console.
(MOCA-8389) Fixed an issue where a native process crash during the precommit phase could
leave an active database connection open if it happened during a transaction.
(MOCA-8476) Changed Quartz scheduler threads to run as daemon, so that they do not
prevent a process from exiting when the main thread terminates through
return. This was preventing Integrator InboundAdapterRunnerMain task to
normally return to the command-line when running it from command-line
with "run once" (-1) argument.
MOCA client
Case ID
Resolved issue
(Defect ID)
01052421 Updated Authorization Maintenance, Copy Users functionality so when a user
is copied, all attributes from the original user are copied to the new user.
(MCS-10802)
01159593 Updated the Web Enablement User Maintenance page to use the source user
ID when copying a user record.
(MCS-10851)
(MCS-10791) Successful Login message will be logged after validating password and
privileges.
(MCS-10822) For a Web Enablement instance, fixed an issue that prevent the time from
displaying in the correct time zone.
(MCS-10839) Updated UserService's LIST command to include the same warehouse /

directed work details as the GET.

Portal server framework

Case ID
Resolved issue
(Defect ID)
1037329 The download request now has the correct CSRF token to authenticate and
download correctly.
(REFS-1670)
1045866 Fixed some inconsistencies in how paging works in Page Builder grid pages.
(REFS-1751)
1071783 Fixed an issue that could cause files to be omitted from exported menus and
custom pages.
(REFS-1753)
1109342 Restyled the Save Default State button, which is displayed at the top of grid
pages.
(REFS-1867)
1126970 Fixed some date parsing issues in Page Builder pages.

(REFS-1893)
1127096 Forms associated with a Page Builder grid's edit and custom actions no longer
throw an error when customized if they contain many fields.
(REFS-1900)
(REFS-1569) Updated the portal server framework Windows Service tool (nssm) to fix defect
on Windows versions 7 and 10
(REFS-1671) MonthPicker now correctly localizes the months that are displayed.
(REFS-1704) Date fields in Page Builder grid type pages now accept empty values.
(REFS-1718) All filters added to a grid will remain added to the grid after a store reload.
(REFS-1768) Navigating to a page will always replace its local context with the URL's
context.
(REFS-1829) Added missing metadata to exportable grid columns.
(REFS-1865) Fixed an edge case where the value shown in a currency field could be using a
different currency code than the one shown.
(REFS-1887) Fixed an issue where exported field configuration / extensibility data would fail
to import into other environments.
(REFS-1921) Cleaned up some situations where buttons displaying a record count could
show the wrong number.

Chapter 4. Information alerts
Chapter 4. Information alerts

This chapter provides alert information for this release of Event Management.
2018.1.0.0
Portal server framework
Certificate issues identified for HTTPS over TLS clustered configurations
Starting with the 2017.2.1.4 release of portal server, certificates used with clustered portal server
instance communications may no longer validate portal server instances. You may notice one or more of
the following issues:
l A warning that your certificate is invalid
l Errors on web client pages that communicate with other portal server instances, such as the
Monitor page
l Starting a trace for an application server instance (using Ctrl+Shift+L) does not save any data
These issues are a result of one or more of the following changes:
l Third-party library removed support for Subject Common Name value: The third-party
client library, OkHttp, no longer supports using the Subject Common Name (CN) value to identify an
instance within a certificate. In adherence to standard RFC-2818, the Domain Name System
(DNS) name value is now used. This change affects self-signed certificates that rely solely on the CN
value. If your certificates include the DNS name in a Subject Alternative Names (SANs) segment
(self-signed or CA-signed), this change does not impact your certificate.
l Portal server framework uses machine name for node identification: For clustered
communications, a portal server instance uses the machine (or computer) name to identify itself
and other nodes in a cluster, not the fully qualified DNS name. This change impacts self-signed and
CA-signed certificates as neither is likely to include the machine name only as a DNS name in a SAN
segment.
Note: While certificates often include the fully qualified DNS name (that includes the machine
name), it is uncommon to have the machine name only as a DNS name value included in the SAN
segment.
To resolve these issues, perform one of the following tasks:
l If your certificate does not include a DNS name value, replace the certificates by deleting the old
certificates, recreating the key pair and certificates specifying the instance machine name in a SAN
DNS entry, and importing the new key pair and certificates into each portal server instance keystore
and portal server instance and application server (MOCA) instance JVM Truststore.
l If your certificate includes a fully qualified DNS name value, modify each portal server instance’s
COMPUTERNAME environment variable to match the DNS name value listed in the certificate used
with the instance.


Event Management 2018.1 Release Notes PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Event Management 2018.1 Release Notes PDF

Uploaded by

Copyright:

Available Formats

Release Notes

JDA® Event Management

Copyright © 2018-2019 JDA Software Group, Inc. All rights reserved.

Chapter 2. Installation and upgrade 12

Chapter 3. Resolved issues 16

Chapter 1. Release overview

Event Management enhancements

l Single SCE client login: The configuration, concurrent-dlx-sessions-config=block, is available in a

Expire a session after a password change

JDA Event Management Release Notes 1

Single user account supports both OpenID Connect and application

User authentication through PingFederate integration

Ability to modify drop-down list and lookup fields

JDA Event Management Release Notes 2

Page Builder supports adding external pages

Page Builder supports drop-down list and lookup fields

Batch Actions Summary Report

JDA Event Management Release Notes 3

Export grid data on Page Builder grid type pages

JDA Event Management Release Notes 4

Page Builder page health check and portal server communication

Save default state button now an icon

l Minimum length: Does the password meet the minimum length requirement?

JDA Event Management Release Notes 5

Configurable Web Services support batch operations

Data loading options for Page Builder grid type pages

Import pages built using Page Builder in the web user interface

JDA Event Management Release Notes 6

Page Builder supports adding and modifying form type pages

l Whether the layout is 1 or 2 column format

l The position of each field on the page

Page Builder chart type pages support expanded data resources

JDA Event Management Release Notes 7

Page Builder grid type pages support batch actions

Supply Chain Execution Applications Administrator Guide

JDA Event Management Release Notes 8

MOCA Console User Guide

Shared applications enhancements

JDA Event Management Release Notes 9

Configurable Web Services support batch operations

Console Log Files page update

Groovy script execution limited to Administrator roles

Private session salt configuration

JDA Event Management Release Notes 10

Session Security health check

JDA Event Management Release Notes 11

Chapter 2. Installation and upgrade

Component Supported configurations

Server OS l IBM AIX 7.2 Technology Level 2 or later

Client OS l Windows 7 Service Pack 1 (64-bit)

Application Not applicable

Middle tier Not applicable

Web server Not applicable

Portal server l Google Chrome

LDAP server Not applicable

Help English (U.S.)

JDA Event Management Release Notes 12

New client installation application

New portal server installation application

l Warehouse Reporting: Installed automatically.

l Authentication type: Set to Native.

Installation package name changes

JDA Event Management Release Notes 13