Professional Documents
Culture Documents
Release 2018.1
Last updated: 8 March 2019
Legal notice
Rights to the content of this document
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
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.
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.
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.
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.
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.
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.
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.
2018.1.1.0
Extensions
This section introduces the new features related to the extensions functionality.
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.
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.
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 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
This section introduces the new features related to the extensions functionality.
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.
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.
l The fields that are displayed and how each field is configured
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 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.
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.
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.
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.
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
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.
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.
l Stash and static content server URLs: Set based on the instance's server and port number.
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.
The SCE installation packages are now distributed with the following file names:
l For AIX
l For Linux
l For Windows
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.
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.
Integration overview
Event Management supports integration with the following applications:
For detailed information on the integrations, see the appropriate integration or installation guide.
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
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.0.0
There are no resolved issues in this release associated with a customer case.
Shared applications
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
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.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)
Case ID
Resolved issue
(Defect ID)
1073739 Fixed timing issue when session context could be prematurely closed, which
could leave uncommitted transaction.
(MOCA-8585)
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.
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)
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-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.
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 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
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.
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.