Professional Documents
Culture Documents
Legal notice
Rights to the content of this document
Copyright 2007-2008 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.
To the extent a name or logo does not appear on this list does not constitute a waiver of any intellectual property rights that JDA
has established in any of its product, feature or service names, or logos.
Translation notice
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 undertakes no obligation to update this design or technical documentation. This design
or technical documentation 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 design or technical documentation outside of authorized individuals within your organization.
0706a
Table of contents
CHAPTER 1. INSTALLATION AND UPGRADING ......................................................................... 1
Installation notes......................................................................................... 1
JDA Analysis and Discovery Environment .................................................................................... 1
Upgrading the EP Mid-Tier and JADE Administrator software from a previous version where both are
installed on the same server ..................................................................................................... 2
Upgrading the JADE Administrator software from a previous version where it is installed by itself ...... 2
7.5.0 ......................................................................................................... 4
JADE ...................................................................................................................................... 4
EKB Structure Services............................................................................................................. 4
7.4.0 ......................................................................................................... 4
EKB Configuration Services (EKBCS) .......................................................................................... 4
EKB Facts Datasource .............................................................................................................. 5
JDA Analysis and Discovery Environment .................................................................................... 5
Message Logging
See "Install Enterprise Planning mid-tier component software" in the Enterprise Planning Suite
Server Installation Guide.
JADE Administrator
The JADE Administrator is installed separately on the mid-tier. See "Install JADE
Administrator" in the Enterprise Planning Suite Server Installation Guide.
Installation notes
JDA Analysis and Discovery Environment
JADE installation requirements
See "Installation requirements: Application server machine" in the Enterprise Planning Suite
Server Installation Guide for installation requirements.
JADE may install without these components, but will not run successfully.
EKB Configuration Services 7.5.x must be installed on only one server on the network
before JADE is installed. It can be installed on a JADE primary or secondary physical
server or on another server.
JDABIApplicationServer
JDABIMessageLog
JADEAdminServer
Note: If services are not stopped manually, the uninstall procedure will complete
successfully. However, an installation attempt may fail. If services are not stopped and
the installation fails, then the machine must be restarted before proceeding with the
new installation.
Open the JADE Administrator and connect to the JADE server you are upgrading.
2.
Export the current JADE settings. Follow the instructions in the "Import or export JADE
Administration Tool settings" section of the Enterprise Planning Suite Server
Administrator Guide.
3.
Use the Add/Remove Programs tool to perform a complete uninstall of the JADE
Administrator before installing the 7.5 version.
4.
5.
6.
7.
Launch the JADE Administrator and point it to the newly installed EP-Mid Tier.
8.
Import the saved JADE settings from the saved file created in Step 2. Follow the
instructions in the "Import or export JADE Administration Tool settings" section of the
Enterprise Planning Suite Server Administrator Guide.
Use the Add/Remove Programs tool to perform a complete uninstall of the JADE
Administrator before installing the 7.5 version.
2.
7.5.0
JADE
JADE has been enhanced to support Assortment Planning. The JADE Administration application
is used to configure and create Assortment Definition Contexts (ADC) in EKBS. Assortment
plans that are automatically created by the assortment planning client are created and stored
at a single location on a designated file directory location. The assortment measure plan,
created by the clients, has common configuration information that is shared by all assortment
plans. It is possible to configure the attributes an assortment context contains and the
attributes that can be set to filter the ADC, as with a standard EKB Context. In addition,
assortment plans can be configured to contain display attributes.
To learn how to configure these features, see "Configure Assortment Planning" in the
Enterprise Planning Suite Server Administration Guide for details of the new JADE features in
support of Assortment Planning.
The JADE Administration tool has been enhanced to provide support for the EKBS cache
service. See "Configure EKB Structure connectivity" in the Enterprise Planning Suite Server
Administration Guide for details.
Portions of the settings configured in JADE Administrator are now stored in the EKB
Configuration Service (EKBCS). (This has been true since 7.4.) EKBCS stores settings used by
EKB in a central location for use by JADE and EKB. The settings include EKBF Foundation and
Quartz cube configuration and EKBS configuration information. The settings stored in EKBCS
are not exported by the JADE Administrator, nor can they be imported into JADE
Administrator. To learn more about using EKBCS, see the Enterprise Planning Suite Server
Administrator Guide.
The Connect dialog box no longer displays the option to select a connection type for Enterprise
Planning. Only option existed in the drop-down list, and it remains the only option in 7.5, so
the drop-down list was removed. The connection type always defaults to Enterprise Planning in
7.5.
7.4.0
EKB Configuration Services (EKBCS)
EKB Configuration Services is new with this release. In previous releases, configuration files
existed on each mid-tier server and required manual synchronization. With this release, a
single configuration server exists and components of the Enterprise Planning Server Edition
refer to a common repository on that server eliminating the need for synchronization.
Additionally, a user interface for maintaining configuration information is provided in this
release via the JADE Administrator. See "EKB Configuration Service entries for EKB Facts" in
the Enterprise Planning Suite Server Administrator Guide.
EP Suite Mid-Tier Release Notes - 4
2007-2008 JDA Software Group, Inc.
Confidential
RegistryContextID rcid
[SUBDIR sub-dir]
Removed parameters
[CubeName cubename]
[SubcubeName subcubename]
[CubeSet subcubeset]
[ConfigSet config_name]
For the updated full command set to invoke the Planning Structure Engine, see "How to run
PSU" in the Enterprise Planning Suite Client Administrator Guide.
Copy versions
A new component of JADE has been implemented to support the need to copy a version of
data to a different version of data within EKBF. By having the EP mid-tier (JADE) do the
processing, it reduces the total amount of data transfer that happens between EKBF and the
EP Client. See "Managing copy measures job status" in the Enterprise Planning Suite Server
Administrator Guide.
Retrieve correct local culture date format into the Admin Plan
The JADE PSE will convert a date and time data type into a readable date string. Only the date
portion of the data type will be converted to a string. The hours/minutes/seconds information
will not be converted because the EP client does not use the time information.
To get the proper date, the Windows culture setting on the EP Client and JADE mid-tier server
must be set to the proper local culture. See "Retrieve the correct local culture date format for
the admin plan" in the Enterprise Planning Suite Server Administrator Guide.
General
64-bit Windows platforms
Enterprise Planning mid-tier components targeted at Windows platforms contain only 32-bit
executables. These components are NOT certified nor considered viable by JDA for operations
on 64-bit Windows OS platforms.
We welcome customer-reported feedback and experience in all environments; however,
Enterprise Planning components are only supported in certified environments. JDA plans for
testing viability or potentially enabling certification for use of 32-bit components in 64-bit
Windows environments, along with eventual production of 64-bit components, are currently
under review for future releases, as we continue to gather and factor customer and market
input.
JADE
Context updates
When a user updates a structure context, for example, by adding attributes for filtering or
display, JADE automatically builds the underlying context snapshot to ensure EP is reading
current data. Depending on the size of the context being updated, this may result in a longer
than expected save operation.
EP Suite