Event Management 9.1.2.0 Installation Guide

Installation Guide JDA® Event Management

Release 9.1.2.0

Legal notice Rights to the content of this document Copyright © 2007-2016 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. 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 (https://www.jda.com/legal/patents ).

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(mailto:[email protected]) and they will be forwarded to the appropriate development teams for review and consideration in a future release.

Table of Contents Chapter 1. Introduction ................................................................................................ 1 What you can install................................................................................................. 1 Who should use this guide......................................................................................... 1 Software implementation advisement .......................................................................... 1 Software support ..................................................................................................... 2 Terminology ........................................................................................................... 2 Installation tasks ..................................................................................................... 3 Upgrade tasks.........................................................................................................3 Interruption of the installation ................................................................................... 3 Chapter 2. Before you install or upgrade ............... ......... ........ ........ ........ ........ ......... ...... 4 Technical specifications............................................................................................. 4 Server requirements ........................................................................................ 4 Language support ......................................................................................... 11 Pre-installation and upgrade tasks for the server software ............................................ 11 Pre-installation tasks ..................................................................................... 11 Pre-upgrade tasks ......................................................................................... 13 Installation connection information ........................................................................... 15 Event Management server software .................................................................. 15 Portal server software .................................................................................... 16 Known installation or upgrade concerns ..................................................................... 17 Required hotfixes .......................................................................................... 17 Increase the Windows desktop heap settings ..................................................... 17 Remove obsolete registry settings.................................................................... 18 SQL Server upgrade requirements ................................................................... 19 SQL Server isolation level update ..................................................................... 20 19 Oracle upgrade requirements .......................................................................... Oracle database updates ................................................................................ 20 Oracle database tablespace requirements on upgrade ......................................... 20 Oracle registry requirements ........................................................................... 20 Windows user setup tasks ....................................................................................... 21 Windows user account types ........................................................................... 21 Task list....................................................................................................... 21 Create the Windows user account .................................................................... 22 Assign the user to an Administrators group........................................................ 23 Grant the user rights to log on as a service ........................................................ 23 Verify that the user has printer access .............................................................. 24 Frequently asked questions for the JDA SCE client software .......................................... 24 Do I have to do anything before I begin the installation?...................................... 24 What is the difference between a Typical installation and a Full client installation? .... 24 How do I change the type of client installation (Typical or Full)? ............................ 25 What is the difference between the JDA SCE client with WinMSQL and without WinMSQL?................................................................................................. 25 How do I remove WinMSQL? ........................................................................... 25 Can I add WinMSQL after the client is installed? ................................................. 25 When do I install the client software? ............................................................... 25 Can I install more than one client software at a time?.......................................... 26 Can I add client software to an existing client installation? ................................... 26 Can I install multiple versions of the client software?........................................... 26 Can I install multiple instances of the client software on the client workstation? ....... 26 What happens if I already have client software installed? ..................................... 27

Which operating system user group must a user be assigned to in order to access a JDA SCE application from a client workstation?.................................... 27 When starting the client and connecting to a server instance, the login window prompts me for a service. What is a service?................................................... 28 Is it always a good idea to have a default server connection? ............................... 28 How do I connect to an instance that is not the default? ...................................... 28 Pre-installation or upgrade tasks for the client software................................................ 29 Chapter 3. Windows server and client installations ........ ........ ........ ......... ........ ........ ..... 31 Introduction.......................................................................................................... 31 What you can install ...................................................................................... 31 Installation sequence ..................................................................................... 31 Before you begin........................................................................................... 31 Time requirement.......................................................................................... 31 Installation wizard window examples ................................................................ 31 Install the application server software ....................................................................... 32 Start the installation ...................................................................................... 32 Select the installation mode ............................................................................ 33 Initiate the installation ................................................................................... 34 Accept the license agreement .......................................................................... 35 Provide an environment name ......................................................................... 36 Specify the configuration file path .................................................................... 37 Select the setup type ..................................................................................... 38 Select the product and destination location ........................................................ 40 Provide the portal server instance connection information .................................... 42 Provide the port information............................................................................ 44 Provide the instance URL ................................................................................ 46 Provide the locale ID...................................................................................... 47 Select the service startup setting ..................................................................... 48 Select the database authentication method........................................................ 49 Provide the SMTP JDA SCE service user login information for OS user authentication ........ Provide the server information ................................................................ 51 50 Select the database type ................................................................................ 52 Provide the Oracle database information ........................................................... 53 Provide the SQL Server database information..................................................... 57 Select whether to change the database............................................................. 61 Select the database options ............................................................................ 62 Select the language database options ............................................................... 63 Select a customize tablespaces option .............................................................. 63 Start the file copy process .............................................................................. 64 Finish the installation ..................................................................................... 65 Start the service ........................................................................................... 65 What to do next ............................................................................................ 66 Install the portal server software .............................................................................. 66 Start the portal server installation.................................................................... 66 Provide a portal server instance name .............................................................. 67 Initiate the portal server installation ................................................................. 68 Accept the portal server license agreement........................................................ 69 Select the portal server setup type................................................................... 70 Specify the destination folder .......................................................................... 71 Select the features to install............................................................................ 72 Provide the portal server port information ......................................................... 73 Provide the Stash and static URLs .................................................................... 74 Provide the portal server locale ID ................................................................... 75 Select the language database options ............................................................... 75 Configure the portal server connections ............................................................ 76

Select the portal server authentication type ....................................................... 77 Provide the portal server authentication connection............................................. 78 Select the database type ................................................................................ 79 Select the database authentication method........................................................ 80 Provide the Oracle database information ........................................................... 81 Provide the SQL Server database information..................................................... 85 Select whether to change the database............................................................. 89 Select whether to start the portal server service ................................................. 90 Start the installation process ........................................................................... 91 Finish the installation ..................................................................................... 92 Start the service ........................................................................................... 92 What to do next ............................................................................................ 92 Install the JDA SCE client software ........................................................................... 93 Start the JDA SCE client installation wizard........................................................ 93 Select the installation mode ............................................................................ 93 Initiate the installation ................................................................................... 95 Accept the license agreement .......................................................................... 96 Specify the configuration file path .................................................................... 97 Select the setup type ..................................................................................... 98 Select the product and destination for client software .......................................... 99 Verify the product component list................................................................... 100 Specify the configuration file ......................................................................... 101 Provide the client connections to server instances ............................................. 102 Start the file copy process ............................................................................ 103 Finish........................................................................................................ 104 Chapter 4. UNIX server installations ......................................................................... 105 Introduction........................................................................................................ 105 What you can install .................................................................................... 105 Installation sequence ................................................................................... 105 Before you begin......................................................................................... 105 Time requirement........................................................................................ 105 Working and physical directories.................................................................... 106 Install the application server software ..................................................................... 106 Create the instance ..................................................................................... 106 Set the password for the UNIX user................................................................ 109 Select the products to install ......................................................................... 109 Configure the registry .................................................................................. 111 Check the login information and create the database schema ............................. 113 Load the distributed data .............................................................................. 114 Unmount the DVD ....................................................................................... 114 Start the service ......................................................................................... 114 What to do next .......................................................................................... 114 Install the portal server software ............................................................................ 115 Create the instance ..................................................................................... 115 Set the password for the UNIX user................................................................ 116 Select the products to install ......................................................................... 116 Run the database batch scripts ...................................................................... 119 Start the service ......................................................................................... 120 What to do next .......................................................................................... 120

Chapter 5. Application upgrades ............................................................................... 121 Upgrade an instance on Windows ........................................................................... 121 Time requirement........................................................................................ 121 Installation wizard window examples .............................................................. 121 Stop the IIS and JDA services ....................................................................... 121 Start the installation .................................................................................... 122 Select the installation mode .......................................................................... 123 Specify the configuration file path .................................................................. 124 Select additional applications ........................................................................ 125 Provide the portal server instance connection information .................................. 127 Provide the port information.......................................................................... 129 Provide the instance URL .............................................................................. 131 Provide the locale ID.................................................................................... 132 Select the language database options ............................................................. 132 Select the service startup setting ................................................................... 133 Select the database authentication method...................................................... 134 Provide the Reporting instance information ...................................................... 135 Provide the SMTP server information .............................................................. 136 Select whether to change the database........................................................... 137 Start the file copy process ............................................................................ 138 Adjust the registry Java settings .................................................................... 139 Finish the installation ................................................................................... 140 Upgrade the Integrator data ......................................................................... 140 Start the service ......................................................................................... 141 What to do next .......................................................................................... 141 Upgrade a portal server instance on Windows ........................................................... 141 Start the portal server installation.................................................................. 141 Initiate the portal server installation ............................................................... 143 Accept the portal server license agreement...................................................... 144 Select the portal server setup type................................................................. 145 Specify thefeatures destination folder ........................................................................ 147 146 Select the to install .......................................................................... Provide the portal server port information ....................................................... 148 Provide the Stash and static URLs .................................................................. 149 Provide the portal server locale ID ................................................................. 150 Select the language database options ............................................................. 150 Configure the portal server connections .......................................................... 151 Select the portal server authentication type ..................................................... 152 Provide the portal server authentication connection........................................... 153 Select the database type .............................................................................. 154 Select the database authentication method...................................................... 155 Provide the Oracle database information ......................................................... 156 Provide the SQL Server database information................................................... 160 Select whether to change the database........................................................... 164 Select whether to start the portal server service ............................................... 165 Start the installation process ......................................................................... 166 Finish the installation ................................................................................... 167 Start the service ......................................................................................... 167 What to do next .......................................................................................... 167 Upgrade an instance on UNIX ................................................................................ 168 Time requirement........................................................................................ 168 Shut down the instance ................................................................................ 168 Select the products to install ......................................................................... 168 Configure the registry .................................................................................. 170 Upgrade the distributed data......................................................................... 172 Upgrade the Integrator data ......................................................................... 173

Unmount the DVD ....................................................................................... 173 Start the service ......................................................................................... 173 What to do next .......................................................................................... 173 Upgrade the portal server software on a UNIX server ................................................. 174 Shut down the instance ................................................................................ 174 Select the products to upgrade ...................................................................... 174 Run the database batch scripts ...................................................................... 176 Start the service ......................................................................................... 177 What to do next .......................................................................................... 177 Upgrade or add the JDA SCE client software ............................................................. 177 When to perform......................................................................................... 177 Start the JDA SCE client installation wizard ...................................................... 177 Select the installation mode .......................................................................... 178 Initiate the installation ................................................................................. 180 Accept the license agreement ........................................................................ 181 Specify the configuration file path .................................................................. 182 Select the setup type ................................................................................... 183 Select the product and destination for client software ........................................ 184 Verify the product component list................................................................... 185 Specify the configuration file ......................................................................... 186 Provide the client connections to server instances ............................................. 187 Start the file copy process ............................................................................ 188 Finish........................................................................................................ 189 Chapter 6. After you install or upgrade....... ......... ........ ........ ........ ........ ......... ........ ..... 190 Start the web client.............................................................................................. 190 Start the JDA SCE client and connect to a JDA SCE application .................................... 190 Add a client connection......................................................................................... 194 Enable remote calls from an earlier version .............................................................. 196 Validate the integrity of your upgrade ..................................................................... 197 Post-installation or upgrade Perl location change ....................................................... 198 197 Post-upgrade folder maintenance ........................................................................... Uninstall the JDA SCE client software ...................................................................... 199 Chapter 7. Record of installation information ............................................................ 201 Installation-specific information.............................................................................. 201 Event Management server software ........................................................................ 201 Portal server software .......................................................................................... 202

Introduction

Chapter 1. Introduction This guide provides JDA supply chain execution (SCE) technical specifications, explains how to install or upgrade the JDA SCE server software on a Windows or UNIX server platform, and explains how to install or upgrade the JDA SCE client software on a workstation.

What you can install You can install and upgrade the following components as part of your server software installation: •

•

Event Management: Helps you proactively manage your logistics operations by alerting you, through various methods, to critical system and operational events at the time that they occur. Portal server: Provides the functionality to view and work with the web-based user experience introduced with the 8.3.0.0 release of Warehouse Management, 9.0.0.0 release of Event Management, and 9.1.0.0 release of Reporting. Portal server has a separate installation process and is installed in a separate instance on a web server. Portal server might also be referred to as REFS (External Facing Services). IMPORTANT: •

Portal server installation is required.

•

Portal server requires a database and login for the portal server instance that is separate from the application instance database.

Who should use this guide This guide is intended for the experienced system installer who wants to perform an efficient installation of a JDA application. System installers using this guide must have working knowledge for this installation of the following information: •

Application servers

•

Database servers

•

Web servers and web browsers (if applicable)

•

Server configuration (for example, installers must know how many physical servers the installation requires and which server software to install on each server)

Software implementation advisement IMPORTANT: Although JDA licenses packaged software, JDA solutions offer complex capability and scalability requiring trained, experienced personnel to install and implement. Even robust documentation is no substitute for JDA certified consultants. JDA implementation experience in addition to training, both on the JDA solutions and on their underlying technologies as defined in JDA solution documentation, are the keys to success. Given JDA’s mission to ensure customers achieve optimal results, JDA strongly recommends you use certified consultants who understand JDA applications and delivery methodologies. Without this guidance, you can expect to experience implementation challenges that cannot be will addressed effectively under your JDA support agreement. these circumstances, JDA Support Services refer you to the Consulting Services team who can be In engaged to answer questions and guide the implementation.

JDA Event Management Installation Guide © 2007-2016 JDA Software Group, Inc.- Confidential

1

Introduction

Software support The JDA Solution Investment Policy includes three support levels to maximize your benefit. By supporting only the newest software versions, JDA can provide you with exemplary service, enabling you to realize an evolving return on your software investment. Through the JDA Customer Support website (http://support.jda.com/), you can access a comprehensive summary of your licensed applications and their current levels of support.

Terminology You should learn the following terms in order to understand the material presented in this guide: •

•

Instance: A particular installation or variance of a JDA SCE application installation on a server. Each instance on a server is configured to meet unique installation or working requirements. For example, you may need to install a Training instance and a Production instance. Although the term instance is used throughout this guide, it is often used interchangeably with environment. Server: The computer on which the JDA SCE server software is installed to await and fulfill requests from client applications on the same or other computers. In general, a server is a computer (or computer software) that provides services to other computer applications.

•

Client: The requesting computer or application in a client-server relationship. Client-server describes the relationship between two computer software programs in which one program, the client, makes a service request from another program, the server, which fulfills the request.

•

Host: The customer's mainframe computer, usually referred to as a large server, that contains the customer's business data. This is the business computer with which JDA SCE applications share information.

•

Port number: A number on the server on which the JDA SCE server software is installed. The client uses the port number to access and send messages to the server. Each instance of a JDA SCE application on a server must have a different port number. For Windows servers, valid port numbers range from 1024 to 5999 and 6101 to 65535. For UNIX servers, contact the network administrator.

•

Service: The connection information that facilitates communication between the components (servers and clients) within a JDA SCE system configuration. Beginning with the 2010.1 release, communication is established through http protocol. Consequently, each instance is identified with a unique URL that consists of the server name and the port number for the instance, along with a constant value of service (for example, http://:/service).


2

Introduction

Installation tasks IMPORTANT: You must perform each installation procedure in the order specified. 1. Learn what you must do before you install. Review known installation concerns, and complete all applicable pre-installation tasks before you start the installation. 2. If applicable, install the server software on a Windows platform and verify the installation. The required order in which to install the server software (if not installed in one instance) is defined in the Windows server and client installations (on page 31) chapter. 3. If applicable, install the server software on a UNIX platform and verify the installation. The required order in which to install the server software (if not installed in one instance) is defined in the UNIX server installations (on page105) chapter. 17). 4. If applicable, install required hotfixes, if any. See Required hotfixes (on page 5. Install the JDA SCE client software (on page 93). 6. Review the remaining post-installation procedures and perform any that apply.

Upgrade tasks IMPORTANT: You must perform each upgrade procedure in the order specified. 1. Learn what you must do before you upgrade. Review known upgrade concerns, and complete all applicable pre-upgrade tasks before you start the server software upgrade. 2. Review the list of applications included with the upgrade. 3. If applicable, upgrade the server software on a Windows platform and verify the upgrade. 4. If applicable, upgrade the server software on a UNIX platform and verify the upgrade. 17). 5. If applicable, install required hotfixes, if any. See Required hotfixes (on page 6. Install the JDA SCE client software (on page 93). 7. Review the post-upgrade procedures and perform any that apply.

Interruption of the installation If you are interrupted and must terminate the installation process before it is complete, the setup program saves the information that you provided and saved up to that point in a temporary file. When you return to the installation, the setup program uses the information stored in the temporary file to display the values for previously requested information. Note: If you interrupt the process after you have provided all of the required information and started copying the files, no files are actually copied. For a complete installation, you must allow the file copying process to finish.


3

Before you install or upgrade

Chapter 2. Before you install or upgrade This chapter identifies tasks that are required before you install or upgrade the JDA SCE application server software to ensure your installation is successful.

Technical specifications Server requirements To explain the most complex physical server configuration, the technical requirements for each server software component are presented as if you are installing each on a separate physical server. However, this does not mean that each server software component requires its own separate physical server. IMPORTANT: •

The minimum disk space requirement for each server represents only the amount of disk space required to install the executables associated with this software for one instance. It does not account for any project-specific customizations or data; additional production, test or development instances; or general computer overhead concerns, such as swap files and log files. You need more than the specified amount of disk space to properly install and run the software. In addition, some configurations require a faster CPU (or multiple CPUs) and more memory to handle higher load volumes. For details about your specific hardware needs, contact JDA Support Services.

•

If you use applications inside VMware images and you experience issues, you are not required to recreate and troubleshoot every issue in a non-VMware environment. However, JDA reserves the right to request that you diagnose certain issues in a native certified operating system environment without the virtual image. JDA only makes this request when there is reason to believe that the virtual environment is a contributing factor to the issue.

Database server requirements •

Oracle requirements •

Supported version •

•

•

Oracle 12.1.0.2 (64-bit) Standard or Enterprise Edition with or without Real Application Clusters (RAC)

Configuration •

Be sure that you install Oracle patch releases before you install the application.

•

If your configuration requires multiple database servers, all of the servers must have the same version of Oracle.

SQL Server requirements •

Supported version •

•

SQL Server 2014 Service Pack 1

Configuration • If your configuration requires multiple database servers, all of the servers must have the same version of SQL Server. •

Must run in READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION modes.


4


Event Management application server requirements •

IBM AIX 7 requirements •

Platform •

•

•

•

pSeries

System •

Operating system: AIX 7.1, Technology Level 3 or later, and Service Pack 5 (7100-03-05-1524) or later

•

Minimum CPU: POWER7 or later chipset

•

Minimum disk space: 70 GB for JDA installed files and additional space for support files

•

Minimum memory: 16 GB

Software •

IBM 64-bit SDK for AIX, Java Technology Edition, Version 8 with Service Refresh 2 or later; available from IBM developerWorks(http://www.ibm.com/developerworks/java).

•

IBM XL C/C++ Enterprise Edition for AIX 12.1

•

Apache Ant 1.9.x (http://ant.apache.org)

Oracle Solaris 11 requirements •

Platform •

•

SPARC

System •

Operating system: Solaris 11.2 or later

•

Minimum CPU: SPARC Enterprise M-Series servers configured with SPARC64 VI, VII, or VII+ processors, or Oracle SPARC T-Series servers configured with T4 processors Note: T1, T2, and T3 processors arenot supported.

•

•


•


Software •

Java SE Development Kit 8 (64-bit) with update 60 or later; available from the Oracle Technology Network(http://www.oracle.com/technetwork/java)

•

Oracle Solaris Studio 12

•



5


•

Red Hat Enterprise Linux 7 requirements •

•

Platform •

AMD or Intel x64

•

VMware ESX 5.5 or later

System •

Operating system: Red Hat Enterprise Linux 7.1 (64-bit)

•

Minimum CPU: Intel Xeon Processor E5 or later, 2.13 GHz or faster; or AMD equivalent

•

•

•

Minimum disk space: 70 GB for JDA installed files and additional space for support files Minimum memory: 16 GB

Software •


•

The specified version or later of the following packages: •

ant 1.9.1

•

make 3.81

•

gcc 4.4.5

•

gcc-c++ 4.4.5

•

glibc 2.12

•

glibc 2.12 (32-bit)

•

glibc-common 2.12

•

glibc-devel 2.12 (32-bit)

•

glibc-devel 2.12

•

glibc-headers 2.12

•

libgcc 4.4.5

•

libgcc 4.4.5 (32-bit)

•

libstdc++ 4.4.5

•

libstdc++ 4.4.5 (32-bit)

•

libstdc++-devel 4.4.5

•

libstdc++-devel 4.4.5 (32-bit)

•

compat-libstdc++ 33-3.2.3

•

compat-libstdc++ 33-3.2.3 (32-bit)


6


•

Microsoft Windows Server 2012 R2 requirements •

Platform •

•

AMD or Intel x64 / VMware ESX 5.5 or later

System •

Operating system: Windows Server 2012 R2 (64-bit)

•


•


•

•

Minimum memory: 16 GB Software •

Microsoft .NET Framework 3.5

•

ActiveState ActivePerl 5.22 or later (32-bit) (http://www.activestate.com/activeperl/downloads ), or Strawberry Perl 5.22 or later (32-bit) (http://strawberryperl.com/)

•


•

Visual Studio 2008 Service Pack 1 or Visual C++ 2008 Express Edition Service Pack 1; only required if you will be building source code on this server

•

Apache Ant 1.9.x (http://ant.apache.org); only required if you will be building source code on this server

Portal server requirements •

IBM AIX 7 requirements •

Platform •

•

•

•

pSeries

System Operating system: AIX 7.1, Technology Level 3 or later, and Service Pack 5 (7100-03-05-1524) or later

•

Minimum CPU: POWER7 or later chipset

•


•


Software •

IBM 64-bit SDK for AIX, Java Technology Edition, Version 8 with Service Refresh 2 or later; available from IBM developerWorks(http://www.ibm.com/developerworks/java).

•



7


•

Oracle Solaris 11 requirements •

Platform •

•

SPARC

System •

•

Operating system: Solaris 11.2 or later Minimum CPU: SPARC Enterprise M-Series servers configured with SPARC64 VI, VII, or VII+ processors, or Oracle SPARC T-Series servers configured with T4 processors Note: T1, T2, and T3 processors arenot supported.

•

•


•


Software •


•


Red Hat Enterprise Linux 7 requirements •

•

•

•

•

Platform •

AMD or Intel x64

•

VMware ESX 5.5 or later

System •

Operating system: Red Hat Enterprise Linux 7.1 (64-bit)

•


•


•


Software •


•

The specified version or later of the following packages: ant 1.9.1

Microsoft Windows Server 2012 R2 requirements •

Platform •

•

AMD or Intel x64 / VMware ESX 5.5 or later

System •

Operating system: Windows Server 2012 R2 (64-bit)

•


•


•



8


•

Software •


•

ActiveState ActivePerl 5.22 or later (32-bit) (http://www.activestate.com/activeperl/downloads ), or Strawberry Perl 5.22 or later (32-bit) (http://strawberryperl.com/)

•


•

Apache Ant 1.9.x (http://ant.apache.org); only required if you will be building source code on this server

Client requirements •

JDA SCE client requirements •

Platform •

•

•

Operating system: Windows 7 Service Pack 1, 8.1, or 10

•

Minimum CPU: Single Core 2.5GHz or faster; Intel or AMD processor

•

Minimum disk space: 20 GB

•


•

Recommended memory: 8 GB

•

Graphics device: DirectX 9 graphics device with WDDM 1.0 or later driver

•

•

Intel x86/64

System

Display: 1280x1024 monitor resolution at 96 dpi (do not use the Windows Large fonts or 120 dpi settings)

Software •


•

Microsoft Office 2007 or later with the most current Service Pack, if you want to view exported data in Microsoft Excel or Microsoft Word

•

Adobe Reader DC (http://get.adobe.com/reader/)

•

iReport 5.2 (http://sourceforge.net/projects/ireport/files/iReport/ ) if you want to customize reports


9


•

Portal server web browser requirements Note: JavaScript must be enabled for all web browsers. •

Google Chrome 45 or later

•

Internet Explorer 11 Note: Not certified for Compatibility mode.

•

Mozilla Firefox 41 or later

•

Safari 9

•

Software •

Java 8 with update 60 or later; available from Oracle (http://www.java.com) if you will be viewing Jasper Reports using the JAVA Viewer Note: Java 8 is available in a 32-bit and 64-bit version. Install the correct Java version following the recommendation available from Oracle (http://www.java.com/en/download/faq/java_win64bit.xml ).

•

Tablet device requirements Notes:

•

•

•

Tablet performance is optimized with WiFi connection.

•

Use of a tablet device and these requirements are only applicable to the Warehouse Management and Event Management web-based functionality (installed with the platform server).

Apple •

Operating system: iOS 7, 8, or 9

•

Browser: Safari

•

Models: •

iPad Air 2 or later

•

iPad mini 2 or later

Microsoft Windows •

Operating system: Windows 8, 8.1, or 10

•

Minimum CPU: x86-based processor

•

Browser: Internet Explorer 11 (including Metro version) Note: Devices on which you want to install the client software, such as the convertible tablet PC (Windows Surface Pro), must meet the JDA SCE client requirements.

•

•

Display: Minimum 7" display at 600 dpi (optimized for display in landscape view)

•

Memory: 4 GB

Android •

Operating system: 4.4 or later

• •

Browser: Google Chrome Display: Minimum 7" display at 600 dpi (optimized for display in landscape view)

•

Memory: 4 GB


10


Language support Event Management is provided in the following languages: •

Chinese (Simplified)

•

Dutch

•

English (U.S.)

•

French

•

German

•

Italian

•

Japanese

•

Korean

•

Portuguese (Brazilian)

•

Russian

•

Spanish

Note: The available version associated with each language may vary. Contact JDA Support Services for the latest information on the language versions that are available. Each language version is tested on the associated language operating system and on an English operating system with the native language pack installed. The English version of the application is not tested on cross-language environments. OnLine Expert (Help) and other technical documentation is provided in English only.

Pre-installation and upgrade tasks for the server software It is crucial to the success of your JDA SCE application installation or upgrade that you perform each of the required pre-installation or pre-upgrade tasks.

Pre-installation tasks Before you begin the installation, you must be sure that the following pre-installation tasks are completed. 1. Understand your system configuration. Note: The physical server configuration for your application installation depends on your unique bandwidth and operational requirements. This information is typically determined with help from JDA before the installation. 2. Ensure that your system meets the recommended requirements and that all prerequisite software is installed on the servers and configured to work with your application. See Technical specifications (on page4).


11


3. Obtain the required access rights for each server on which you plan to install software. •

For Windows server installations, obtain administrator privileges.

•

For UNIX server installations, obtain a root user account.

4. Review the installation concerns and address any concerns that pertain to your installation. See Known installation or upgrade concerns (on page17). 5. Determine the database user authentication method that you will use for this installation. The following methods are available: •

Operating system (OS) user authentication : Performs authentication using a single operating system user that matches the database user.

•

Database user authentication: Performs authentication using specific database connection information.

6. Create the Windows user if any of the following conditions apply: •

You are using the OS user for database authentication.

•

You are using database user authentication and installing the Reporting software.

See Windows user setup tasks (on page21). 7. Set up your database management system (DBMS) instance and database: •

If you are using SQL Server: a. Configure the SQL Server instance: i.

Configure the following SQL Server trace flag (see the SQL Server documentation for the procedure to use the Configuration Manager to add a startup parameter): •

ii.

-T9481

Verify the SQL Server security settings.

b. Create and configure the application instance database: IMPORTANT: If portal server is part of your configuration, you must also perform the following steps to create a database and login for your portal server instance that is separate from your application instance database. i.

Create the database.

ii.

If you are using OS user authentication, grant the Windows user database privileges.

iii. If you are using database user authentication, create the login. iv. Verify that the database is case insensitive. v.

Enable the Read Committed Snapshot option for the Read Committed isolation level. Note: Enabling theRead Committed Snapshot option is required to minimize locking contention while protecting transactions from dirty reads of uncommitted data modifications.

•

If you are using an Oracle database and you are a JDA associate, see jNET for general guidance on best practice and Oracle installation information (within the DBS Documents folder) (http://jnet.jda.com/rp/DBS/Oracle/Forms/AllItems.aspx ).

8. Verify that your server has the proper version of Java installed according to the technical specifications for your JDA SCE application. If it does not, install the proper version of Java. See the JavaInstallHelp.txt file on your JDA SCE Windows DVD for detailed installation instructions.


12


9. Define the connection information that will facilitate communication between multiple server installations and between the servers and clients. See Installation connection information (on page 15). 10. When you are certain that all of the pre-installation tasks are complete, continue with the procedures to install your JDA SCE application server software. See Windows server and client installations (on page31) or UNIX server installations (on page105).

Pre-upgrade tasks Note: Before you begin an upgrade, you must determine the version of the application that you are currently using. If you are upgrading from a version earlier than 2010.1.x, then you must first upgrade to 2010.1.x (that is, the latest 2010.1 version). See the 2010.1 installation guide for your application for the upgrade instructions. You must obtain a new license key for this upgrade. If you do not have the required information, then contact JDA Support Services. 1. Review your system configuration, and then determine how many instances you need to upgrade. For example, if you installed JDA SCE application server software on two different physical machines, you will need to upgrade both server instances. 2. Verify the database management system (DBMS) instance and database for your application instance. •

If you are using SQL Server: a. Configure the following SQL Server instance trace flag (see the SQL Server documentation for the procedure to use the Configuration Manager to add a startup parameter): •

-T9481

b. Perform the following tasks on the application instance database: i.

Verify that the database is case insensitive.

ii.

Change the compatibility mode to 100.

iii. Enable the Read Committed Snapshot option for the Read Committed isolation level. IMPORTANT: Enabling theRead Committed Snapshotoption is required to minimize locking contention while protecting transactions from dirty reads of uncommitted data modifications. •

If you are using Oracle, ensure you have upgraded your Oracle instance to the version specified in Technical specifications (on page 4).


13


3. If you are upgrading a portal server instance that is earlier than 9.1.0.0, you must create a separate database and login for your portal server instance: •

If you are using SQL Server: a. Configure the following SQL Server instance trace flag (see the SQL Server documentation for the procedure to use the Configuration Manager to add a startup parameter): •

-T9481

b. Perform the following tasks on the application instance database: i.

Verify that the database is case insensitive.

ii.

Change the compatibility mode to 100.

iii. Enable the Read Committed Snapshot option for the Read Committed isolation level. IMPORTANT: Enabling theRead Committed Snapshotoption is required to minimize locking contention while protecting transactions from dirty reads of uncommitted data modifications. •

If you are using Oracle, ensure you have upgraded your Oracle instance to the version specified in Technical specifications (on page 4).

4. For Windows upgrades, obtain administrator privileges on the servers, and identify the name of the instance that you want to upgrade. 5. For UNIX application server upgrades, gather the following information: •

UNIX user's login and group name for the instance that you are upgrading

•

If using Oracle, the Oracle SID and the version number of the Oracle database that you are upgrading

•

If using SQL Server, the JDBC connection string for accessing the SQL Server database

•

Database user's login and password

•

Port number for the instance that you are upgrading

•

Path to the physical and working directories for the instance that you are upgrading

6. Review the installation concerns and address any concerns that pertain to your installation. See Known installation or upgrade concerns (on page17). 7. If you are using database operating system (OS) user authentication, or database user authentication and installing Reporting for the first time, set up the Windows user. See Windows user setup tasks (on page 21). 8. Verify that your server has the proper version of Java installed according to the Technical specifications (on page4). If it does not, install the proper version of Java. See the JavaInstallHelp.txt file on your JDA SCE Windows DVD for detailed installation instructions. 9. Back up the database. 10. When all pre-upgrade tasks are complete, continue with the procedures to upgrade your JDA SCE 121). application server software. See Application upgrades (on page


14


Installation connection information The following lists identify the connection information that you must provide when you complete the JDA SCE application installations. Note: It is recommended that you document the connection information in Record of installation information (on page 201).

Event Management server software •

Environment (for a UNIX installation) •

Environment name

•

UNIX login

•

UNIX group

•

Working directory

•

Physical directory

•

JDA product instance name

•

Instance URL (http://:/service)

•

User authentication method (database or operating system)

•

Windows User Login (if using OS user authentication in this instance)

•

•

•

User

•

Domain (if not local)

•

Password

SQL Server databases •

SQL Server version

•

SQL Server server name

•

SA user (if using database user authentication)

•

SA password (if using database user authentication)

•

Database name

•

Database user name (if using database user authentication)

•

Database user password (if using database user authentication)

•

SQL Server port number

•

JDBC URL

Oracle databases •

Oracle server name

•


•



15


•

Oracle SID

•

Oracle port number

•

Oracle user (if using database OS user authentication for a UNIX installation)

•

Version number

•

JDBC URL

•

Portal server instance URL and, for web page (form) customizations, directory location

•

IP address or network name for the Event Management SMTP email server

Portal server software •

Portal server instance name

•

Setup type

•

Installation destination folder, if different from the default

•

Installed features

•

Portal server port number

•

Server connection URLs •

Stash server URL

•

Static server URL

•

Locale ID

•

Authentication type (Native, Reverse Proxy, Federated SSO, or LDAP)

•

Authentication connection name

•

Connection information (for each connection)

•

•

Connection name

•

Connection type

•

Application type

•

Connection URL


SQL Server version

•


•


•


•

Database name

•



16


•

•


•



Oracle server name

•


•


•

Oracle SID

•

Oracle port number

Known installation or upgrade concerns Before you begin your installation or upgrade, you should consider the following known installation concerns.

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

Increase the W indows desktop heap settings When you install on a Windows platform, in order to provide enough memory for the application components (such as windows, menus, icons, and dialogs) to operate, you must increase the Windows desktop heap settings. 1. Log in as an administrator to the Windows server on which you want to install or upgrade the JDA SCE application server software. 2. Select Start > Run. 3. In the Open field, enter regedit, and then click OK. The Registry Editor window is displayed. 4. Navigate to the HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems folder. 5. Back up the Windows registry: a.

Select the SubSystems folder, and then select File > Export. The Export Registry File window is displayed.

File b. Locate the directory where you want to back up the Windows registry, and then in the name field, enter a name for the backup registry file. c.

Click Save.

6. Ensure that the SubSystems folder is selected. 7. On the right side of the Registry Editor window, select the Windows registry key. 8. Select Edit > Modify. The Edit String window is displayed.


17


9. In the Value data field, find the text "Windows SharedSection=". Note: The appropriate section is bolded in the following example: \Windows %SystemRoot%\system32\csrss.exe ObjectDirectory= SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16. 10. Change the third Windows SharedSection number to1024. Example: %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,1024 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16 11. Click OK. 12. Select File > Exit. 13. Restart the server to enable the change.

Remove obsolete registry settings To enhance existing support for internationalization and localization, specifically in those environments where multi-byte character sets are required, JDA SCE applications support the Unicode character set using UTF-8 encoding. The change to Unicode obsoletes the following registry settings that previously may have been made in your JDA SCE application instances: •

•

•

MOCA Java character set configuration : The MOCA_JAVA_CHARSET environment variable controlled how the MOCA server process encoded the character set strings coming from Java. External code page setting: The MOCA_EXT_CODEPAGE environment variable provided support for other code pages. JDBC connection string sendStringsAsUnicode parameter : For SQL Server databases, the sendStringsAsUnicode parameter controlled how the JDC driver sent strings.

If upgrading a JDA SCE application instance that is earlier than 2009.2, perform the following tasks to remove obsolete registry settings. On a Windows server: 1. Log in as an administrator to the JDA SCE application server. 2. Navigate to the LES\data folder for your instance. Example: :\JDA\\LES\data 3. Open the registry file in Notepad. 4. Scroll to the [ENVIRONMENT] section. 5. In the list of environment variables, if the MOCA_JAVA_CHARSET environment variable exists, delete it. 6. If the MOCA_EXT_CODEPAGE environment variable exists, delete it.


18


7. If you are using a SQL Server database, scroll to the[DATABASE] section, and then perform the following tasks: a.

Scroll to the URL line.

b.

Delete the following text string if it is displayed at the end of the line: sendStringParametersAsUnicode=false

c.

Select File > Save.

8. Close the registry window. On a UNIX server: 1. Log in as the UNIX user to the JDA SCE application server. 2. Determine whether the MOCA_JAVA_CHARSET, MOCA_EXT_CODEPAGE, or both, environment variables exist in the environment using the following commands from the $ prompt: •

set | grep MOCA_JAVA_CHARSET

•

set | grep MOCA_EXT_CODEPAGE

3. If either of the environment variables exist, perform the following tasks: a.

vi $LESDIR/.profile.local Edit .profile.local using the following command from the $ prompt:

b. Remove the lines that define the MOCA_JAVA_CHARSET, MOCA_EXT_CODEPAGE, or both, environment variables. c.

Save the changes.

4. Log out and then log in again. Note: There is no need to adjust the JDBC connection string sendStringsAsUnicode parameter because it applies only to SQL Server database connections.

SQL Server upgrade requirements If you are upgrading to a certified version of SQL Server from a previous version of SQL Server, you must first back up your database. When you restore your SQL Server database backup to your new database server, you must change the compatibility mode to 100.

SQL Server isolation level update For JDA Parcel databases that are versions 2009.1 and later, and for all other JDA SCE application databases that are versions 2010.1 and later, you must enable the READ_COMMITTED_SNAPSHOT option of the READ-COMMITTED isolation level. This action minimizes locking contention while protecting transactions from dirty reads of uncommitted data modifications. 1. In the Object Explorer select your database, and then select New Query. 2. Execute the following statements: ALTER DATABASE < DATABASE NAM E> SET ALLOW_SNAPSHO T_I SOLATI ON ON ALTER DATABASE SET READ_ COMMI TTED_SNAPSHOT ON


19


Oracle upgrade requirements This JDA SCE application may work with earlier versions of Oracle, but to avoid potential installation or run time problems, it is important that you use the Oracle version identified in the Technical specifications (on page4). If you are upgrading an earlier instance of this JDA SCE application, upgrade your Oracle instance to 4) before you complete the upgrade. the version identified in Technical specifications (on page IMPORTANT: If you upgrade your Oracle instance before you upgrade this JDA SCE application, do not run the JDA SCE application until you have completed its upgrade. The newer version of Oracle may not be compatible with your existing version of the JDA SCE application.

Oracle database updates Starting with the 2009.2 release, the following statement should be run to ensure that Oracle's temporary tablespaces in the Oracle database do not fill up due to the use of LOB data types (see Oracle SR 3-3210567741):

ALTER Syst em SET EVENTS ' 60025 t r ace name cont ext f or ever ' ; The following statement should be run to ensure that Oracle does not truncate values for fields (see Oracle SR 2-3052258):

ALTER Syst em SET EVENTS ' 10503 t r ace name cont ext f or ever , l evel 4000' ;

Oracle database tablespace requirements on upgrade IMPORTANT: If you are upgrading an earlier instance of this JDA SCE application, database tablespaces may have changed. For information on database tablespaces, contact JDA Support Services and your database administrator.

Oracle registry requirements If your JDA SCE application instance is installed on a Windows server and you upgraded your Oracle instance, then before you upgrade your JDA SCE application installation you must update the registry. 1. Log in as an administrator to the JDA SCE application server. 2. Navigate to the LES\data folder for your instance. Example: :\JDA\\LES\data 3. Open the registry file in Notepad. 4. Scroll to the [DATABASE] section. 5. Verify that the connection information is correct. If not, select the existing content, and then enter the correct connection information. 6. Select File > Exit. 7. Close the registry window.


20


Windows user setup tasks The Windows user account determines the shared resources, such as files, directories, and printer queues to which the service has access. Before you install the JDA SCE application server software on a Windows server, you must create a Windows user if any of the following conditions apply: •

You are using the operating system (OS) user for database authentication.

•

You are using database user authentication and installing the Reporting software. Note: During the installation, you are prompted for the user name and password for the Windows user. If you are using the OS user for database authentication, a separate Windows user for Reporting is not required. The Windows user account used for database OS user authentication provides the printer access for Reporting.

Windows user account types Windows user accounts can be either local or domain. The type of account that you must create depends on your system configuration. •

If the JDA SCE application server programs and database software reside on the same server, then you can create a local or domain user. Note: When all software is installed on the same server, it is suggested that you use a local account.

•

If the JDA SCE application server programs and database software reside on the different servers, you must create a domain user.

Task list When creating a local user account, perform the following tasks: IMPORTANT: The following instructions are for creating a local user account. While they can be used as a guideline for creating a domain user account, they do not include the exact steps for creating a domain user account, since those steps may be unique to your network. Domain users must be created by network administrators. If you must create domain user accounts, then verify your network security restrictions to avoid potential problems, such as expiring passwords. If the password for the user account expires, your installations will not work. 1. Create the Windows user account 2. Assign the Windows user to an administrative group 3. Grant the Windows user rights to log on as a service 4. Verify that the Windows user has printer access


21


Create the Windows user account Note: Domain users must be created by network administrators. For detailed instructions, contact your network administrator. 1. Perform one of the following tasks: •

If you are creating a Windows user for database OS user authentication, then log in as an administrator to the server on which you plan to install the JDA SCE application software.

•

If you are creating a Windows user for Reporting (because you are using database instead of OS user authentication), then log in as an administrator to the server on which you plan to install the Reporting software.

Administrative Tools > 2. From the Start menu, display the list of programs, and then select Computer Management. The Computer Management window is displayed. 3. Expand the System Tools folder, and then expand theLocal Users and Groups folder. 4. Right-click the Users folder, and then select New User. The New User window is displayed. 5. In the User name field, enter a name for the Windows user account. Note: A user name cannot be identical to any other user or group name on the computer being administered. It can contain up to 20 uppercase or lowercase characters with the exception of the following special characters: " / \ [ ] : ; | = , + * ? <> 6. If necessary, in the Full name field, enter a full name for the Windows user account. 7. In the Description field, e nter a description of the Windows user account. For example, enter Account used for running. 8. In the Password field, enter the password for the Windows user account. IMPORTANT: The password cannot be the same as the user name. For security purposes, this is a strong password. Strong passwords adhere to specific standards. For more information, see the topic on creating strong passwords in theMicrosoft Management Console Online Help . In addition, you may want to contact your IT department to determine whether they have implemented unique conventions for creating valid passwords. 9. In the Confirm password field, re-type the password. 10. Deselect the User must change password at next logoncheck box. 11. Select the User cannot change password check box. 12. Select the Password never expires check box. IMPORTANT: If the password expires, the service cannot start. If you do not select this option, then be sure that you have measures in place to ensure that the password does not expire. 13. Click Create. One of the following results occurs: •

If the password meets all password policy requirements, then it is accepted, and the information is cleared from the fields on the window.

•

If the password does not meet password policy requirements, then a message is displayed indicating that the password is not acceptable. Perform the following tasks: a. Click OK. b. Type a valid password. c. Click Create.

14. Click Close. The Computer Management window is displayed.


22


Assign the user to an Administrators group 1. Under the Local Users and Groupsfolder, select the Users folder. Properties. The 2. Right-click the name of the Windows user, and then click Properties window is displayed. 3. Select the Member Of tab. 4. Click Add. The Select Groups window is displayed. 5. In the Enter the object names to selectfield, enter Administrators, and then click Check Names. The computer name and the Administrators group are displayed. 6. Click OK. The Properties window is displayed. 7. Click Apply. The Windows user is assigned to the Administrators group. 8. Click OK. 9. Close the Computer Management window.

Grant the user rights to log on as a service 1. From the Start menu, display the list of programs, and then selectAdministrative Tools > Local Security Policy. The Local Security Settings window is displayed. 2. Expand the Local Policies folder, and then select User Rights Assignment. 3. In the list of policies, double-click Log on as a service. The Log on as a service Properties window is displayed. 4. On the Local Security Setting tab, click Add User or Group. The Select Users, Computers, or Groups window is displayed. 5. In the From this location field, make sure that location of the Windows user that you created is displayed. For example, when you are creating a local account, then the name of the local computer must be displayed. If the correct location is not displayed, perform the following tasks: a.

Click Locations.

b. In the Locations list, select the location of the Windows user. c.

Click OK.

d. In the Enter the object names to selectfield, enter the name of the Windows user, and then click Check Names. The location and name of the Windows user are displayed in the field. e.

Click OK. The location and name of the Windows user is displayed in the list of users on the Log on as a service Properties window.

6. Close the Log on as a service Properties window. 201). 7. Record the Windows user name and password in Record of installation information (on page


23


Verify that the user has printer access 1. Log in to the server using the Windows user account that you created. 2. From the Start menu, access the list of printers, and then select the printer. Note: A list of network printers associated with the server may be displayed in the list. 3. If no printers are displayed in the list, then perform the following tasks: a.

From the Start menu, access the list of p rinters, and then select Add Printer.

b.

Follow the instructions for adding a printer. Note: A local or network printer can be added for the Windows user. Because the local user will not have network access, when adding a network printer, you will need to type the path to a printer instead of browsing for the printer. When you type the path, you will be asked for a valid domain login.

c.

Start, and then access the list of To verify that the printer has successfully been added, select printers. If the name of the printer is displayed, it has been successfully added.

4. Print a test page. Note: It is suggested that you print a test page from the printers to ensure that the local user has access to them. If printing does not occur, delete the printers that are displayed in the list and then add them again.

Frequently asked questions for the JDA SCE client software Do I have to do anything before I begin the installation? Yes. To ensure that you can proceed through the client installation process efficiently, you should complete the pre-installation tasks. See Perform the pre-installation tasks for the JDA SCE client software (on page 29).

What is the difference between a Typical installation and a Full client installation? When installing the client software, you have the option to perform either Typical a or Full installation. •

Typical installation: Only the minimum software components that are required to start the client software are installed. When you use the client software to connect to a server instance for the first time, the server downloads only the files required to access the functionality for which you are authorized. That means, only the files that you use are stored on your workstation. Note: If you select theTypical installation option, users with restricted access cannot access the files. For information about user access rights, see Which operating system user group must a user 27). be assigned to in order to access a JDA application from a client workstation? (on page

•

Full installation: All software components, including all files required to access the applications, are installed on your workstation. Note: The Full installation option is recommended for installations with slow access to the server and is required for workstations accessed by users with restricted access.


24


How do I change the type of client installation (Typical or Full)? You can change the client installation between Typical and Full by reinstalling (upgrading) the client software. However, switching from a Full to Typical installation does not remove application files already installed on your workstation. If you want to change the installation type, and you do not want all of the application files on your workstation, then you must uninstall the client software and then perform a typical installation. For more information, see Uninstall the JDA SCE client software (on page 199) and Install the JDA SCE client software (on page93).

What is the difference between the JDA SCE client with WinMSQL and without W inMSQL? When installing the JDA SCE client software, you choose from the following options to determine whether to install the client with or without WinMSQL: •

•

JDA SCE Client w/WinMSQL: Install the JDA SCE client software with WinMSQL on administrative workstations at which users perform setup, configuration, system maintenance, and security setup (configuration of roles and users and assignment of menu options). When you install the JDA SCE client software with WinMSQL, users can run MOCA commands to directly access the database regardless of any authorization rights. TheJDA Client w/WinMSQLoption is recommended for workstations that are used only by system administrators. JDA SCE Client w/o WinMSQL: Install the JDA SCE client software without WinMSQL on enduser workstations where users perform their daily tasks. When you install the JDA SCE client JDA software without WinMSQL, users are prevented from accessing the database directly. The Client w/o WinMSQL option is recommended for end-user workstations. IMPORTANT: If you are upgrading or adding client software, theJDA Client w/o WinMSQL option does not remove WinMSQL. If you no longer want WinMSQL on the workstation, then you must first uninstall the existing client software. To learn more, see How do I remove WinMSQL? (on page 25).

How do I remove WinMSQL? Before the 2005.2 release, WinMSQL was automatically installed during the client software installation. If you want to remove WinMSQL from the workstation, then you must uninstall the existing client software, and then install the software selecting the JDA Client w/o WinMSQL option. For more 199) and Install the JDA SCE client information, see Uninstall the JDA SCE client software (on page software (on page 93).

Can I add WinMSQL after the client is installed? Yes. You can add WinMSQL to the JDA SCE client by reinstalling (upgrading) the client software and selecting the JDA Client w/ WinMSQL option. For more information, see Upgrade or add the JDA SCE client software (on page177).

When do I install the client software? You can install the client software on a workstation at any time after meeting the following requirements: •

•

All pre-installation tasks are completed. You want have to obtained the connection information for the JDA SCE application server instance to which you connect.

Note: The client software can be installed before the installation of the server software. However, you cannot confirm your client installation or connect to the server instance until the server software is installed. It is recommended that you install the server software before you install the client software.


25


Can I install more than one client software at a time? Yes. You can install all of the client software at the same time.

Can I add client software to an existing client installation? Yes. For example, you can add Activity Agent to an existing installation containing the JDA SCE client.

Can I install multiple versions of the client software? Yes. When you upgrade a client installation, the previous version remains, and the new version is added. You can then access server software that requires different client versions. If you do not want to keep and the old or version. other administrative reasons, then you mustthe uninstall theclient previous version thenversion install for thespace current For more information, see Uninstall JDA SCE software (on page 199) and Install the JDA SCE client software (on page93). IMPORTANT: When you uninstall a client instance that contains multiple versions, all versions are uninstalled.

Can I install multiple instances of the client software on the client workstation? Yes. Beginning with the 2012.1 release, when you upgrade a client installation, you are asked if you would like to install a new instance or maintain or update an older instance. If you select to install a new instance, the previous version remains and the new instance is added. Multiple instances of the client software let you work with different versions of an application, server customizations, server connections, and upgrade schedules. For example, if you use two different versions of a JDA SCE application, you can install the matching client software version for each application server instance version. Using a separate client version when connecting to the instance eliminates having to update the client framework to match the server instance version. A separate dedicated configuration file is created for each client software installation. For the initial installation: •

Directory location is C:\Program Files\RedPrairie\Client.default

•

Desktop shortcut isJDA SCE Client - default

For subsequent installations: •

Directory location is C:\Program Files\RedPrairie\Client.

•

Desktop shortcut isJDA SCE Client -

If you do not want to keep the old version for space or other administrative reasons, then you must uninstall the previous version and then install the current version. For more information, see Uninstall the JDA SCE client software (on page199) and Install the JDA SCE client software (on page93). IMPORTANT: When you uninstall a client instance that contains multiple versions, all versions are uninstalled.


26


What happens if I already have client software installed? If you already have client software installed on a workstation and want to connect to a later version of server software, then you must upgrade the client software. You can use the following methods to perform a client upgrade: •

Use the installation DVD: When you upgrade using the JDA installation DVD, during the installation process, a message asks you to accept the automatic restart of the installation software in an upgrade mode. After the installation software restarts, you can upgrade the current client installation or add other client software to the installation. For more information, see Upgrade or add the JDA SCE client software (on page177).

•

Download from an upgraded server instance : When you upgrade by connecting to the upgraded server instance, you can download the upgraded client core and framework components when asked to do so. This option is only available to users with administrator or standard access to the client workstation. For more information, see Start the JDA SCE client and connect to a JDA SCE application (on page 190).

IMPORTANT: Beginning with the 2010.1 release, communication between the client and the server is accomplished using http protocol. Consequently, before you can connect to a 9.1.0.0 server instance from a client version 2009.2 or earlier to perform an upgrade, you must open a port on the 9.1.0.0 server that enables communication using the legacy communication protocol. For more information, 29). see Perform the pre-installation tasks for the JDA SCE client software (on page

Which operating system user group must a user be assigned to in order to access a JDA SCE application from a client workstation? In order to access a JDA SCE application from a client workstation, a user must be assigned to one of the following types of operating system user groups on the client workstation: •

Administrator: Has complete and unrestricted access to the client workstation. Administrator access is required in order to install or upgrade the client software on the workstation.

•

Standard (Power): Has the ability to download client core and framework components from a JDA SCE application server to the client workstation. Users with standard access must have write C:\Program access to the registry and to the installed client software directory (typically, Files\RedPrairie) on the client workstation.

•

Restricted: Does not have the ability to download client core and framework components from a JDA SCE application server to the client workstation. However, users with restricted access must C:\Program have write access to the installed client software directory (typically, Files\RedPrairie) on the client workstation. Typically, a restricted user is assigned to a user who only accesses a JDA SCE application to perform basic work activities. If updated client core or framework components are available, then a user with administrator or standard access must download the components to the client workstation before they can be accessed by users with restricted access.

Note: A user's access to a JDA SCE application's functionality is based on the user's authorization as defined in Authorization Maintenance or System Administrator > Authorization (Warehouse Management).


27


When starting the client and connecting to a server instance, the login window prompts me for a service. What is a service? Beginning with the 2010.1 release, communication between the client and the server is accomplished using http protocol. Consequently, connecting to an application server requires a URL. Each application server instance (or service) to which you connect is identified with a unique URL that consists of the server name and port number for the instance and a constant value of service. When you are prompted for a service, you enter the URL. The following is an example of a valid service URL: http://:/service. If you are using a 9.1.0.0 client to connect to an application server instance that is version 2009.2 or earlier, then the service is not a URL. In this case, you enter to satisfy the legacy communication protocol.

Is it always a good idea to have a default server connection? No. When you define a default server connection, then when you start the client software, you are automatically connected to the default instance. This is a timesaving feature for users who only work with one instance of a JDA SCE application, but it can cause problems for users who frequently work with multiple instances of an application, or for those who connect to different JDA SCE applications. However, you can change connections at login.

How do I connect to an instance that is not the default? If you start the client software and are automatically connected to a default server instance, you can connect to another instance. 1. Perform one of the following tasks: •

If the JDA SCE client is open, select File > Logout. The JDA login window is displayed.

•

If the JDA SCE client is not open, from the Start menu, display the list of programs, and then select JDA Supply Chain Execution > Client > JDA SCE Client . The JDA login window is displayed.

Note: The login process automatically connects to a default server, but the login window remains open because your user ID and password are required to continue. As a result, you can select and connect to a different instance. 2. Perform one of the following tasks: •

•

To connect to a 2010.1 or later server instance, in theService field, enter or select the connection name or service URL for the JDA server instance to which you want to connect, and then click Go. To connect to a 2009.2 or earlier server instance, in theService field, enter the server name and port number for the instance in the following format,:, and click Go.

Notes: •

•

SUPER as the For a new installation in which users have not yet been configured, enter default user name and password. When the JDA SCE application is displayed, immediately access Authorization Maintenance and create a new user with administrative privileges. For security reasons, afterbecause creating your own administrative users, you should the SUPER user configuration this login provides users with full privileges to remove configure the application.

3. In the Username field, enter your user ID, and then press Tab.


28


4. In the Password field, enter your password. 5. If you are connected to a Warehouse Management or Warehouse Labor Management server Warehouse drop-down list, select the instance configured to have multiple warehouses, from the warehouse for which you are performing work. Note: If you are assigned to only one warehouse, then the identifier for that warehouse is displayed, and you cannot select a different warehouse. 6. Click Sign in.

Pre-installation or upgrade tasks for the client software You must perform the necessary pre-installation or upgrade tasks to ensure that your installation is successful. 1. If you are installing or upgrading the client software using the installation DVD, then obtain the JDA installation DVD. 2. Ensure that the workstations on which you are installing the client software meet the recommended system requirements. For more information, see Technical specifications (on page 4). 3. Ensure that you have administrative privileges for the workstations on which you will be installing. 4. Obtain the following connection information: •

Connection name: A visual aid for JDA SCE client end users who can change the server instance to which they want to connect. The connection name typically identifies the JDA SCE application server instance for this connection. This can be the name of the application instance on the server, but it is not a requirement.

•

Service: URL for the JDA SCE application server instance to which you want to connect. The URL includes the server name and port number for the instance to which you want to connect, and a constant value (service). Example:http://:/service

Note: The client software can be installed before the installation of the server software. However, you cannot confirm your client installation or connect to the server instance until the server software is installed. It is recommended that you install the server software before you install the client software. 5. To upgrade a version of the client software that is 2009.2 or earlier by accessing a 9.1.0.0 server instance and then downloading the upgraded client core and framework components, first update the registry file for the 9.1.0.0 server instance to enable communication from an earlier version of the client: a.

Log in as an administrator to the server on which the 9.1.0.0 instance is installed.

b.

Navigate to the LES\data folder for the instance. For example: :\RedPrairie\\LES\data.

c.

Open the registry file in Notepad.


29


d.

Under [SERVER], enter the following settings: •

CLASSIC-PORT= Note: You can use any port number that is not currently being used on the server. When you upgrade the client, you initially use this port number to connect to the 9.1.0.0 server.

•

CLASSIC-POOL-SIZE=50 Note: The default value for the classic pool size is 50. You can change that value to reflect your requirements.

Example:

6. Select File > Save. 7. Close the registry window. IMPORTANT: To upgrade the client, connect to the 9.1.0.0 server using the classic port number that you defined in the registry file. After the upgrade is complete, you connect to the server using the service URL for the 9.1.0.0 instance. When you have upgraded all necessary clients, it is recommended that you remove the CLASSIC-PORT and CLASSIC-POOL-SIZE entries from the registry file.


30

Windows server and client installations

Chapter 3. Windows server and client installations This chapter explains how to install the server software in one or multiple instances on a Windows server platform. It also explains how to install the client software.

Introduction What you can install Depending on your system configuration and requirements, you can install the following server components: •

Event Management

•

Portal server

Some of the server components can be installed in the same instance; however, other server components must be installed in separate instances. Specific component installation compatibility is described in the installation steps that follow in this guide and is validated by the installation program. Separate instances can be installed on the same server or different servers.

Installation sequence Depending on your configuration, you may need to install one or more of the server software applications in a different instance or on a different server. If performing multiple server installations, complete them in the following order: 1. Application server software 2. Portal server software 17). 3. Required hotfixes for each installed instance, if any. See Required hotfixes (on page

Before you begin Before you begin the server software installations, be sure that you have met all of the prerequisites and completed all of the pre-installation procedures identified earlier in this guide.

Time requirement Allow approximately 2.5 hours to complete the installation. This includes the time required to load the database tables and default (distributed) data.

Installation wizard window examples The installation wizard window examples that are displayed in this chapter are representative of the windows that you see when performing an installation. The example may not always display the exact information that you see.


31


Install the application server software Complete the following procedures to install the application server software. If your configuration requires you to install the server programs in multiple instances on one server, or on different servers, you must complete the following procedures for each instance that you have to install.

Start the installation 1. If you are using operating system (OS) user authentication, log in as the local or domain Windows user (that you assigned to the database) to the server on which you want to install the software. 2. If you are using database user authentication, log in as an administrator to the server on which you want to install the software. 3. Insert the JDA SCE Windows DVD into the CD/DVD drive. 4. On the desktop, double-click theMy Computer icon and then double-click the icon for the drive that contains the JDA SCE Windows DVD. 5. Double-click the Server folder, d ouble-click the windows folder, and then double-click setup.exe. 6. If a security warning asks to run thesetup.exe software, clickYes. The software launches the product setup program.


32


Select the installation mode The Installation Mode window enables you to select whether you are installing a new version of software, or upgrading or adding products to an installation that already exists.

1. Select the Install New Application Server Instancecheck box. 2. Click Next. If Java is installed properly, the Welcome to the InstallShield Wizard window is displayed. 3. If a message states that the Java version is too low or unknown, or there are two different results on the version test, perform the following tasks: a.

Click OK. The JavaInstallHelp.TXT file that provides step-by-step instructions on how to correct the issue is displayed.

b. Exit the installation program and correct the issue. c.

Restart the installation program.


33


Initiate the installation The welcome window enables you to initiate the server software installation.

Click Next.


34


Accept the license agreement To continue with the installation process, you must accept the license agreement.

1. Click Yes to accept the agreement. If an appropriate Perl version is installed, the Environment Name window is displayed. 2. If a message indicates that Perl is required, perform the following tasks: a.

Click OK. The installation program closes.

b.

Obtain a supported version of Perl, as indicated in the JDA product Technical Specifications.

c.

Manually install Perl, accepting the default settings on the installation wizard windows.

d. Restart the server, and then restart the installation program.


35


Provide an environment name The Environment Name window enables you to enter a unique name for the instance. It is suggested that you use standard naming conventions when providing an environment name. The following information provides examples of recommended naming conventions: •

JDA Warehouse Management Application Server : wm. For example, wmprod.

•

JDA Warehouse Labor Management Model Instance Application Server : wlm. For example, wlmmodel.

You can view the environment name after you display the list of programs on your server, and then Supply Chain Executionfolder (for upgrades, instances may be under the select the JDA RedPrairie folder). IMPORTANT: The name can contain up to 10 characters with the exception of the following characters: / : * ? " < > | \ - . or spaces.

1. In the text field, enter a unique name for the server environment (instance). IMPORTANT: If you enter an existing server environment name, the InstallShield Wizard gives you the option to perform an upgrade or reenter the instance name. 2. Click Next. A message states that the Microsoft Visual C++ 2008 re-distributable package is being installed.


36


Specify the configuration file path The Choose Configuration File Path window enables you to enter the path to the .ini file that contains license or server configuration installation information.

1. If you do not have a license or server configuration.ini file s aved on the server, accept the default information that is displayed. 2. If you have a license or server configuration.ini file saved on the server: a.

Click Browse. The Choose Folder window is displayed.

b.

Select the drive and folder in which the .ini file is located.

c.

Click OK.

3. Click Next.


37


Select the setup type The Setup Type windows enable you to narrow the product installation options (first by selecting the primary product, such as Warehouse Management or Warehouse Labor Management, and then by selecting the server installation type, such as application server or web server) so that only the applicable options are displayed later in the product selection window.

1. Select the following check box or check boxes: •

Other Supporting Products


38


2. Click Next.


Application Server

4. Click Next.


39


Select the product and destination location The Product and Destination Selection window enables you to select the JDA server software components you want to install.


Event Management

Note: As you select the products, the required and available disk space is calculated, and it is displayed at the bottom of the window. 2. If the available disk space is not sufficient, look for available disk space: a.

Click Disk Space. The Available Disk Space window is displayed.

b.

Select another drive to see the available disk space.

c.

When the available disk space is sufficient, click OK.

3. To change the default destination folder: a.


b. In the Directories list, select the folder in which to install the client software. The full path is displayed in the Path field. c.

Click OK. IMPORTANT: To ease the upgrade process, it is recommended that you use the default destination you choose to change theinclude destination folder, be sure that the path to that folder, location. including Ifthe folder name, does not spaces.


40


4. Click Next.

5. If the information is accurate, click Next; otherwise, click Back to make corrections before continuing with the installation.


41


Provide the portal server instance connection information The Portal server information window enables you to enter the portal server instance connection information. The portal server is installed in a separate instance, so if one of the following statements is true, you must provide the connection information to enable communication between the application and portal server instances: •

This application instance includes Warehouse Management.

•

This application instance includes Reporting.

•

This application instance includes Event Management.

•

This application instance includes JDA Parcel, and the optional JDA Parcel web services functionality is part of your configuration.

Otherwise, you can bypass the following installation windows.

Portal URL field, enter the URL for the portal 1. If portal server is part of your configuration, in the server instance. Example:http://:/


42


2. Click Next.

3. If your configuration includes customized web pages (forms), then select the path information for the portal server directory. The directory information is needed to allow customizations to compile and deploy to the portal server. a.


b.

Select the drive and installation folder.

c.

Click OK.

4. Click Next.


43


Provide the port information The Port Information windows enable you to enter port numbers for the MOCA server to listen for incoming requests from MOCA clients and Java to use for remote method invocation (RMI). Each instance of JDA SCE products on a server must have a unique port number for communicating with the JDA SCE client, and a unique port number for Java RMI. Note: Check with your network administrator for a valid server port number. Server port numbers range from 1024 to 5999 and 6101 to 65535. Port numbers 6000 to 6100 are not acceptable ports for JDA SCE connections as they are ports used for Windows and cannot be opened in firewalls.

1. In the text field, enter a port number for the installation, or accept the default. If you enter a port number that is already in use, a message asks whether to use the entered port number. To use the entered port number, clickYes. Note: Although each instance that you use must have a unique port number, you can enter a port number that is already in use. You might want to do this, for example, if you plan to uninstall the old instance that is currently using the port number or plan to only use one instance at a time (which is not typical for a production instance).


44


2. Click Next to provide additional port information.

3. In the text field, enter a port number for Java to use for RMI for the installation, or accept the default. If you enter a port number that is already in use, a message asks whether to us e the entered port number. To use the entered port number, clickYes. 4. Click Next.


45


Provide the instance URL The Service URL Information window displays a unique URL for the instance. Each instance that you install is identified with a unique URL that consists of the host name and the port number that you provided earlier in the installation process, and a constant value of service.

1. In the text field, accept the default or enter the URL for the instance. You should use the default value. The required format for the URL ishttp://:/service, where: •

: Domain name of the server on which you are installing the instance.

•

: Port number that you assigned to the instance earlier in the installation process.

2. Click Next.


46


Provide the locale ID The Locale Information window enables you to enter the locale ID. The locale ID, which defaults to United States English, controls the cultural features of the JDA SCE applications, such as language, calendar and date, and time formats. The client and server use locale ID to configure the userinterface to meet your language requirements.

1. In the text field, accept the default or enter a different locale ID for this instance. 2. Click Next.


47


Select the service startup setting The MOCA Component: Service Startup Setting window enables you to select whether you want the JDA SCE service to start automatically after a server restart, or you want to manually start the service after every server restart.

Auto Start MOCA Service. 1. To restart the service automatically after every server restart, select If you are installing a production instance, you should select this option. Manually Start MOCA Service. 2. To restart the service manually after every server restart, select If you are installing a non-production instance that does not need to be constantly available, such as one used for testing or development, you might want to select this option so that you do not have too many instances using memory or attempting to restart at the same time. 3. Click Next.


48


Select the database authentication method The Database Authentication Method window enables you to select whether you are using database user authentication (such as SQL Server) or OS user authentication (such as Windows) for the database.

1. To use database user authentication, selectUse Database User Authentication. 2. To use database OS user authentication, selectUse Windows Operating System User Authentication. 3. Click Next.


49


Provide the JDA SCE service user login information for OS user authentication If you are using OS user authentication, the MOCA Service Logon Credentials window enables you to enter the JDA SCE service user login information. The JDA SCE service user is the Windows user account that you created for OS user authentication.

1. In the User field, enter the name of the service user login that you have created. For more information, see Windows user setup tasks (on page21). 2. If the user account is on the network instead of being a local account, in the Domain field, enter the domain name. 3. In the Password field, enter the password for the service user. 4. Click Next.


50


Provide the SMTP server information If you are installing Event Management in this instance, the SMTP server information window enables you to enter the Event Management email server information. IMPORTANT: The SMTP server information is required in order to receive alerts from Event Management.

1. In the SMTP field, enter the IP address or network name for the SMTP email server that Event Management will use for sending email alerts. 2. Click Next.


51


Select the database type The Database Component: Select Database Driver window enables you to select the type and version of the database software that you are using for the JDA SCE installation.

1. If you are using an Oracle database, selectOracle 12. SQL Server 2014. 2. If you are using a Microsoft SQL Server 2014 database, select 3. Click Next. 4. If you selected an Oracle database, continue with Provide the Oracle database information (on page 53). 5. If you selected a Microsoft SQL Server database, continue with Provide the SQL Server database information (on page 57).


52


Provide the Oracle database information If you are installing an instance to work with an Oracle database, the Database Setup windows enable you to enter the database driver and connection information.

1. If you want to be prompted for each component needed in the JDBC connection string, select JDBC Thin Driver. 2. If you want to manually build the JDBC connection string with the details for accessing the Oracle database, select JDBC Url (Advanced). 3. Click Next.


53


4. If you selected JDBC Thin Driver: Note: If you are using OS user authentication, the Login information windows look slightly different than what is displayed in the examples.

a.

In the Server field, enter the Oracle server name.

User field, enter the Oracle database b. If you are using database user authentication, in the user name.


54


c.

Password field, enter the Oracle If you are using database user authentication, in the database user password, and then clickNext.

d.

In the SID field, enter the Oracle system identifier, which is typically the database name.

e.

If using OS user authentication, click Next.

f.

Port field), perform one of the In the DB Port field (or if using OS user authentication, in the following tasks: •

If the DB port listed is the default or only Oracle server instance, accept the default port number.

•

If you are using a non-default Oracle server instance, enter the port number for the appropriate instance.


55


5. If you selected JDBC Url (Advanced): Note: If you are using OS user authentication, the Login information window looks slightly different than what is displayed in the example.

a.

In the JDBC URL field, modify the default JDBC connection string with the details for accessing the Oracle database. For example, enterjdbc:oracle:thin:@srv001:1521:wlmp to access a database instance named wlmp on a server named srv001 and port number 1521.

User field, enter the Oracle database b. If you are using database user authentication, in the user name. c.

Password field, enter the Oracle If you are using database user authentication, in the database user password.

6. Click Next. A message states that the database connection is being verified. If the connection is successful, the next window is displayed and you can continue with the installation. OK, and perform one of 7. If an error message states that the database connection check failed, click the following tasks: •

•

Yes. If you want to change and revalidate the database connection information, click No. The If you want to continue without reentering the database connection information, click next window is displayed and you can continue with the installation. IMPORTANT: If you continue with an invalid database connection, your installation will be invalid and you will have to uninstall and reinstall the instance.


56


Provide the SQL Server database information If you are installing an instance to work with a Microsoft SQL Server database, the Database Setup windows enable you to enter the database driver and connection information.

1. If you are using database user authentication, select one of the following options: •

JDBC SourceForge: To specify a port number-based database connection.

•

JDBC SourceForge/Named Instance: To specify a named instance-based database connection.

•

JDBC SourceForge (Advanced): To manually build the JDBC connection string with the details for accessing the SQL Server database.

2. If you are using OS user authentication, select one of the following options: •

JDBC SourceForge/OS Authentication: To specify a port number-based database connection.

•

JDBC SourceForge/Named Instance/OS Au : To specify a named instance-based database connection.

•



57


3. Click Next. Note: If using database OS user authentication, the Login information windows look slightly different than what is displayed in the examples.

4. If you are not using advanced JDBC SourceForge, in theServer field, accept the default if it is correct, or enter the name of the server on which the SQL Server database exists. 5. If you are using advanced JDBC SourceForge, in theJDBC URL field, modify the default JDBC connection string with the details for accessing the SQL Server database. For example, enter jdbc:jtds:sqlserver://srv001/wlmp;instance=SQLSRVR02;useNTLMv2=true to access a database instance named wlmp stored in a SQL Server instance named SQLSRVR02 that is installed on a server named srv001. SA User field, enter the SQL Server system 6. If you are using database user authentication, in the administrator name or accept the default. IMPORTANT: The SA User field must be the system administrator name (usually sa) with the highest privileges in SQL Server. If the wrong name and password are entered in this window, the installation produces errors later in the process when creating schemas. If errors occur, you must uninstall and then reinstall the server software.


58


SA Pwd field, enter the SQL Server system 7. If you are using database user authentication, in the administration password and then clickNext.

8. If you are not using advanced JDBC SourceForge, in theDatabase field, enter the name of the database for this instance. This field is not displayed when using advanced JDBC SourceForge. 9. If you are using database user authentication: a.

In the User field, enter the database user's name.

b.

In the Password field, enter the database user's password.

10. Click Next. If you are using advanced JDBC SourceForge, a message states that the database connection is being verified. If the connection is successful and the Read Committed Snapshot option for the Read Committed isolation level is enabled, the next window is displayed and you can continue with the installation.


59


11. If you are not using advanced JDBC SourceForge, enter the database port number or SQL Server instance name. Note: If the connection is a named instance-based database connectionJDBC ( SourceForge/Named Instanceor JDBC SourceForge/Named Instance/OS Auwas selected at the beginning of this procedure), the window looks slightly different than what is displayed in the example.

DB Port field, perform 12. If the connection is a port number-based database connection, then in the one of the following tasks: •

If the SQL Server instance containing the JDA SCE database is the default or the only instance, accept the default port number.

•

If the SQL Server instance containing the JDA SCE database is a non-default instance, enter the port number for the appropriate SQL Server instance.

Instance field, 13. If the connection is a named instance-based database connection, then in the enter the name for the appropriate SQL Server instance. IMPORTANT: The value that you enter in theInstance field is the name of the SQL Server instance that your JDA SCE server software will access. It is not necessarily the same name as the host name of the server on which the SQL Server database exists. To view the SQL Server instances on the database server, start the SQL Server Management Studio. The SQL Server instances are listed in the Object Explorer. If there are multiple instances, then under each instance, expand the Databases folder until you see your database name. Use the instance name under which your database is displayed. 14. Click Next. A message states that the database connection is being verified. If the connection is successful and the Read Committed Snapshot option for the Read Committed isolation level is enabled, the next window is displayed and you can continue with the installation.


60


OK, and perform one of 15. If an error message states that the database connection check failed, click the following tasks: •

Yes. If you want to change and revalidate the database connection information, click

•

No. The If you want to continue without reentering the database connection information, click next window is displayed and you can continue with the installation. IMPORTANT: If you continue with an invalid database connection, your installation will be invalid and you will have to uninstall and reinstall the instance.

16. If a message states that the database does not have theRead Committed Snapshot option for the Read Committed isolation level enabled, click Yes, and then exit the installation program. 4) for more See the pre-installation or pre-upgrade tasks in Before you install or upgrade (on page information on theRead Committed Snapshot option. When the database setting has been updated, restart the installation process.

Select whether to change the database The Database Component: Skip Database Step window enables you to select whether to change the database during the initial installation or upgrade process. Typically, you want to change the database. However, if you are performing an initial installation or upgrade in a clustered environment where several instances use the same database, then only the first instance's initial installation or upgrade process should run the database-related scripts. For the subsequent instances' initial installations or upgrades, skip the change database step since the database was already changed with the first instance.

1. If the instance is in a non-clustered environment, or the first instance in a clustered environment Do not change database check box is where all instances use the same database, verify that the deselected. 2. If the instance is in a clustered environment where all instances use the same database and the Do not instance is not the first instance that you are initially installing or upgrading, select the change database check box. 3. Click Next.


61


Select the database options The Database Component: Database Options window enables you to select the data to load for the server software.

1. For a new installation, select the following check boxes: •

Create schema

•

Load BASE data

2. Click Next.


62


Select the language database options If language packs are available for the version, the NLS Language Data Loads window enables you to select additional language data if you want complete native language support for the applications that you are installing. 1. To load translation data, select the options that you need. Note: If more options are available than will fit on one window, click Next to access the next set of options. 2. Click Next. If the correct version of .NET Framework is installed on the server, then the next window in the installation sequence is displayed. 3. If a message states that the required .NET Framework version is not installed, perform the following tasks: a.

Click OK. The installation program closes.

b. Manually install the .Net Framework software on the server by running the install executable, which is located on the JDA SCE Windows DVD in the following folder: Server\3rdParty\dotnet35. c.


Select a customize tablespaces option If you are using an Oracle database, the Customize Tablespaces window enables you to indicate whether you want to customize the user's tablespace definition file. Note: For information on customizing the user's tablespace definition file, contact JDA Support Services. JDA Support Services will refer you to the Consulting Services team who can be engaged to answer questions and guide the customization.


63


1. To leave the default tablespaces unchanged, selectUse standard settings. This option assumes the required tablespaces are already created. 2. To view and customize the user's tablespace definition file, select Manually customize usrtbldef.h. Note: This option lets you edit theusrtbldef.h file. During the installation process, the file opens in text format so that you can make changes. After you make the changes and save the file, the installation process proceeds. 3. To use the default database user's tablespace for all tables, select Use dbuser's default tablespace for all tables. This is the recommended option. Note: This option is for environments where database performance is not an issue, such as development and demonstration environments. No tablespaces need to be manually created, since tables are automatically created in the default tablespace for the database user. 4. Click Next.

Start the file copy process The Start Copying Files window enables you to verify the installation information that you provided before starting the installation process. The information listed here (for example, products and connection specifics) should match selections that you made earlier in the setup process.

1. If the information is accurate, click Next to start copying the files; otherwise, clickBack to make corrections before continuing with the installation. Note: To cancel the setup after file copying begins, on the Setup Status window, click Cancel. 2. If a message states that IIS needs to shut down, clickYes. IIS then stops and restarts before the file copy process begins. The Setup Status window is displayed, to indicate the progress of the installation. Server installations can display several additional installation progress windows, such as Creating Database Schemas and Loading Data Sets.


64


Finish the installation The InstallShield Wizard Complete window is displayed to indicate that the installation process has successfully completed.

1. If the window states that you must restart your computer, perform one of the following tasks: •

To restart the computer now, selectYes, I want to restart my computer now .

•

To restart the computer later, selectNo, I will restart my computer later. IMPORTANT: The installation will not work correctly until the computer is restarted.

2. Click Finish.

Start the service If you did not choose to start the service automatically, perform the following tasks to start the service now: 1. From the Start menu, display the list of programs, then selectAdministrative Tools, and then select Services. Note: If you do not see Administrative Tools in the list of programs, then from theStart menu, select Control Panel, and then select Administrative Tools. 2. In the right pane, scroll down to the service that you want to start. Example: The service name is typically displayed as MOCA Server (). 3. Right-click the service and then select Start. Note: If the service is already started, the Start option is not enabled.


65


What to do next 1. To install the portal server software in a separate instance (on this server or another server), continue with Install the portal server software (on page 66). 2. If you have installed all of the server software that you want to install, continue with Install the JDA SCE client software (on page93).

Install the portal server software Complete the following procedures to install an instance of portal server.

Start the portal server installation 1. If you are using operating system (OS) user authentication, log in as the local or domain Windows user (that you assigned to the database) to the server on which you want to install the server software. 2. If you are using database user authentication, log in as an administrator to the server on which you want to install the server software. 3. Insert the JDA Windows DVD into the CD/DVD drive. 4. On the desktop, double-click the My Computer icon, and then double-click the icon for the drive that contains the JDA Windows DVD. 5. Double-click the RPWeb folder, double-click therpweb.iss folder, and then double-click setup.exe. Yes. The software 6. If a security warning asks if you want to run the setup.exe software, click launches the product setup program.


66


To install a new instance of portal server, select Install a new instance of this application . 1. To change or upgrade an existing instance of portal server: a.

Select Maintain or update the instance of this application selected below .

b.

Select the instance from the list.

2. Click Next.

Provide a portal server instance name The Enter Text window enables you to enter a meaningful name for the instance. Each instance must have a unique name since you can install more than one instance of portal server on a server. The following examples provide unique names for the instances described: • Portal server production instance for Warehouse Management connection: wmprtlprod •

Portal server test instance for Supply Chain Executive connections: scetest

•

Portal server development instance for more than one type of connection: portaldev

IMPORTANT: The name can contain up to 10 characters with the exception of the following characters: / : * ? " < > | \ - . or spaces.

1. In the text field, enter a name for the portal server instance. 2. Click Next.


67


Initiate the portal server installation The welcome window enables you to initiate the portal server software installation.

Click Next.


68


Accept the portal server license agreement To continue with the installation process, you must accept the license agreement.

1. Select I accept the terms of the license agreementto accept the agreement. 2. Click Next.


69


Select the portal server setup type The Setup Type window enables you to select the type of instance to install.

1. Select Event Management. 2. Click Next.


70


Specify the destination folder The Choose Destination Location window enables you to accept the default destination folder or specify a different folder.

1. To change the destination folder: IMPORTANT: To ease the upgrade process, you should use the default destination location. a.

Click Change. The Choose Folder window is displayed.

b. In the Directories list, select the folder into which you want to install the portal server software. c.

When the full path to the folder is displayed in the Path field, click OK. IMPORTANT: The Path field must not include spaces.

2. Click Next.


71


Select the features to install The Select Features window enables you to select the features to install. Note: As you select the features, the required disk space is displayed.

1. To install the Event Management and administration (such as user authorization) web-based functionality, make sure that the following check boxes are selected: •

RPWeb

•

Admin

•

Event Management System

2. Click Next.


72


Provide the portal server port information The Portal Server Configuration: Portal Server Port window enables you to enter the port number on which the portal server will run. The portal server is a server-side web server that provides common web server functionality, such as session management, security, single sign on authentication, internationalization and localization, and language management. The default port number is 8060. Note: Check with your network administrator for a valid server port number. Server port numbers range from 1024 to 5999 and 6101 to 65535. Port numbers 6000 to 6100 are not acceptable ports for portal server connections as they are ports used for Windows and cannot be opened in firewalls.

1. In the text field, enter a port number for the installation or accept the default. 2. Click Next.


73


Provide the Stash and static URLs The Portal Server Server Configuration: Stash and Static URL window enables you to enter the connection URLs for the Stash and static content servers.

1. Enter information into the following fields or accept the defaults: •

Stash: Full URL to the Stash server. The Stash server stores the client-side library that provides common components, such as calendars and other controls. The required format for the URL is http://:/stash.

•

Static URL: Full or relative URL to the static content server. The static content server provides standard, formatted information (such as text, images, and cascading style sheets) that is the same regardless of the user requesting the information. The required format for the URL is http://:/web.

2. Click Next.


74


Provide the portal server locale ID The Portal Server Server Configuration base locale window enables you to select the base locale. The base locale is used when a user-specific locale is not available. The locale controls the cultural features, such as language, calendar, and date and time formats. The client and server use the locale ID to configure the user interface to meet your language requirements.

1. From the drop-down list, select the base locale for this instance. 2. Click Next.

Select the language database options If language packs are available for the version, the Select Additional Language Data Loads window enables you to select additional language data if you want complete native language support for the applications that you are installing. 1. To load translation data, select the options that you need. 2. If more options are available than will fit on one window, click Next to access the next set of options.


75


Configure the portal server connections The Portal Server Connections Maintenance window enables you to enter configuration information for each of the instances that connect to this instance of portal server.

1. Enter the application server URL information: a.

Under Connections, click MCS.

b.

In the Connection URL field, enter the service connection that the portal server is to use to communicate with the Event Management application server. The required format for the URL is http://:/Service.

c.

Under Connections, click EMS.

d.


2. Perform one of the following tasks: •

To undo any changes to the fields on the window and revert back to the srcinal entries, click Discard Changes.

•

New. To add another application instance that will be connecting to the portal server, click

•

To delete one of the application instances that you connected to the portal server, under Connections, select the instance and click Delete.

•

To proceed with the installation, click NEXT.


76


Select the portal server authentication type The Portal Server Authentication Configuration window enables you to select the technology to use for authenticating and authorizing users for portal server functionality.

1. Select one of the following authentication types: •

Native: Use of a JDA SCE server (built-in federated authentication) or Cognos.

•

Reverse Proxy: Use of a trusted assertion from a third-party authority.

•

Federated SSO: Use of Enterprise Federated Authentication.

•

LDAP: Use of a Lightweight Directory Access Protocol server.

2. Click Next.


77


Provide the portal server authentication connection The Portal Server Authentication Configuration: Authentication Connection window enables you to enter a name for the connection to the instance of records for all authentication requests and user preferences, such as locale and time zone.

1. In the text field, enter a name for the connection to use for authentication or accept the default, such as MCS or EMS. 2. Click Next.


78



1. If you are using an Oracle database, selectOracle 12. SQL Server 2014. 2. If you are using a Microsoft SQL Server 2014 database, select 3. Click Next.


79



1. To use database user authentication, selectUse Database User Authentication. 2. To use database OS user authentication, selectUse Windows Operating System User Authentication. 3. Click Next. 4. If you selected an Oracle database, continue with Provide the Oracle database information (on page 81). 5. If you selected a Microsoft SQL Server database, continue with Provide the SQL Server database information (on page 85).


80



1. If you want to be prompted for each component needed in the JDBC connection string, select JDBC Thin Driver . 2. If you want to manually build the JDBC connection string with the details for accessing the Oracle database, select JDBC Url (Advanced). 3. Click Next.


81



a.




82


c.


d.


e.


f.



•



83



a.

b. c.

In the JDBC URL field, modify the default JDBC connection string with the details for accessing the Oracle database. For example, enterjdbc:oracle:thin:@srv001:1521:wlmp to access a database instance named wlmp on a server named srv001 and port number 1521. User field, enter the Oracle database If you are using database user authentication, in the user name. Password field, enter the Oracle If you are using database user authentication, in the database user password.


•



84





•


•



•

•

JDBC SourceForge/OS Authentication: To specify a port number-based database connection. JDBC SourceForge/Named Instance/OS Au : To specify a named instance-based database connection. JDBC SourceForge (Advanced): To manually build the JDBC connection string with the details for accessing the SQL Server database.


85


3. Click Next. Note: If using database OS user authentication or advanced JDBC SourceForge, the Login information windows look slightly different than what is displayed in the examples.



86





b.




87



a.

b.

DB Port field, If the connection is a port number-based database connection, then in the perform one of the following tasks: •


•


Instance field, If the connection is a named instance-based database connection, then in the enter the name for the appropriate SQL Server instance. IMPORTANT: The value that you enter in theInstance field is the name of the SQL Server instance that your JDA SCE server software will access. It is not necessarily the same name as the host name of the server on which the SQL Server database exists. To view the SQL Server instances on the database server, start the SQL Server Management Studio. The SQL Server instances are listed in the Object Explorer. If there are multiple instances, then under each instance, expand the Databases folder until you see your database name. Use the instance name under which your database is displayed.

12. Click Next. A message states that the database connection is being verified. If the connection is successful and the Read Committed Snapshot option for theRead Committed isolation level is enabled, the next window is displayed and you can continue with the installation.


88




•

No. The If you want to continue without reentering the database connection information, click next window is displayed and you can continue with the installation.

IMPORTANT: If you continue with an invalid database connection, your installation will be invalid and you will have to uninstall and reinstall the instance. 14. If a message states that the database does not have theRead Committed Snapshot option for the Read Committed isolation level enabled, click Yes, and then exit the installation program. 4) for more See the pre-installation or pre-upgrade tasks in Before you install or upgrade (on page information on theRead Committed Snapshot option. When the database setting has been updated, restart the installation process.




89


Select whether to start the portal server service The start service after installation window enables you to select whether you want the installation program to automatically start the portal server service after the installation completes.

1. To start the portal server service after the installation completes, select the Start service after install check box. 2. Click Next.


90


Start the installation process The Ready to Install the Program window enables you to review the information that you have provided, continue with the installation, or exit the Installation Wizard.

Click Install.


91



Click Finish.

Start the service If you did not choose to start the service automatically, perform the following tasks to start the service now: 1. From the Start menu, display the list of programs, selectAdministrative Tools, and then select Services. Note: If you do not see Administrative Tools in the list of programs, from theStart menu, select Control Panel, and then select Administrative Tools. 2. In the right pane, scroll down to the portal server service to start. Example: REFS (). 3. Right-click the service, and then select Start. Note: If the service is already started, the Start option is not e nabled.

What to do next 1. JDA If you have installed all of server 93). software that you want to install, continue with Install the SCE client software (onthe page 2. To access a portal server instance from a web browser, Start the web client (on page 190).


92


Install the JDA SCE client software Start the JDA SCE client installation wizard 1. Log in as an administrator to the workstation on which you want to install the client software. 2. Insert the JDA Windows DVD into the CD/DVD drive. 3. On the desktop, double-click theMy Computer icon, and then double-click the icon for the drive that contains the JDA Windows DVD. 4. Double-click the Client folder, double-click the windows folder, and then double-clicksetup.exe. Yes. If a security warning asks to run the setup.exe software, click

Select the installation mode The Existing Installed Instances Detected window is displayed if client instances are already installed on the PC. This window enables you to indicate whether you are installing a new version of client software, or upgrading or adding client software to an installation that already exists.


93


1. To install a new client instance: a.

Select Install a new instance of this application , and then click Next. The Enter Text window is displayed.

IMPORTANT: The client instance name can contain up to 10 characters with the exception of the following characters: / : * ? " < > | \ - . or spaces. b. In the text field, enter a unique name for the new client instance. This is the name that you see when you display the list of JDA SCE applications on your client workstation. c.

Click Next. The Welcome to the InstallShield Wizard for JDA SCE Client window is displayed.

2. To upgrade or add client software to an existing client instance: a.


b. In the list, select the instance. c.

Click Next. If a message states that another version of the client software is found and asks OK. you to accept the automatic restart of the installation program in an upgrade mode, click The Welcome to the InstallShield Wizard for JDA SCE Client window is displayed.


94


Initiate the installation The welcome window enables you to initiate the client software installation.

Click Next. The License Agreement window is displayed.


95


Accept the license agreement You must accept the license agreement to continue with the installation process. If you do not accept the license agreement, the installation stops.

1. Read the license agreement. 2. To accept the agreement, clickYes. The Choose Configuration File Path window is displayed.


96


Specify the configuration file path If you are performing an advanced installation, you must specify the configuration file path to tell the InstallShield Wizard where to find the .ini files containing the pre-defined license or client configuration installation information.

1. If you are performing an advanced installation: a.


b.

Select the drive and folder in which the files are located, and then click OK.

2. Click Next. The Setup Type window is displayed.


97


Select the setup type The Setup Type window enables you to select one of the following installation options that defines what files to install, upgrade, or add: •

Typical installation: Only the minimum software components that are required to start the client software are installed. When you use the client software to connect to a server instance for the first time, the server downloads only the files required to access the functionality for which you are authorized. That means, only the files that you use are stored on your workstation. Note: If you select theTypical installation option, users with restricted access cannot access files that they may need to access. For more information, see Which operating system user group must a user be assigned to in order to access a JDA SCE application from a client workstation? (on page 27)

•



To install the minimum software components that are required to start the client software, select Typical.

•

To install all of the software components, select Full.

2. Click Next. The Product and Destination Selection window is displayed.


98


Select the product and destination for client software The Product and Destination Selection window enables you to select the client software that you want to install, upgrade, or add, as well as specify the destination location for that software. You can install the following client software: Note: If you are completing a full installation as opposed to a typical installation, additional client software is available. •

JDA SCE Client w/WinMSQL: Install the JDA SCE client software with WinMSQL on administrative workstations at which users perform setup, configuration, system maintenance, and security setup (configuration of roles and users and assignment of menu options). When you install the JDA SCE client software with WinMSQL, users can run MOCA commands to directly access the database regardless of any authorization rights. TheJDA Client w/WinMSQLoption is recommended for workstations that are used only by system administrators.

•

JDA SCE Client w/o WinMSQL: Install the JDA SCE client software without WinMSQL on enduser workstations where users perform their daily tasks. When you install the JDA SCE client JDA software without WinMSQL, users are prevented from accessing the database directly. The Client w/o WinMSQL option is recommended for end-user workstations. IMPORTANT: If you are upgrading or adding client software, theJDA Client w/o WinMSQL option does not remove WinMSQL. If you no longer want WinMSQL on the workstation, then you must first uninstall the existing client software. For more information, see Uninstall the JDA SCE client software (on page199) and Install the JDA SCE client software (on page93).

•

Activity Agent: Install the Activity Agent software if any of the following conditions apply: •

You are installing the JDA SCE client software to work with Warehouse Labor Management.

•

You are the only user using the workstation.

•

You want to see your performance information throughout the day.


99


1. Select the client software that you want to install, upgrade, or add. Note: As you select, the required and available disk space is calculated and displayed. 2. For an initial installation, if the available disk space is not sufficient, look for available disk space: a.


b.


c.


3. For an initial installation, to change the default destination folder, browse for another location: a.


b. In the Directories list, select the folder into which you want to install the client software. c. When the full path to the folder is displayed in the Path field, click OK. Note: To ease the upgrade process, use the default destination location. 4. Click Next. The Product Component List window is displayed.

Verify the product component list The Product Component List window enables you to verify that you have selected all of the components that you want to install, upgrade, or add. Before you continue with the installation process, you must verify the information on this window. The client software listed on this window should match the selections that you made earlier.

1. Review the information. 2. If the information is accurate, click Next; otherwise, click Back to make corrections before continuing with the installation. The Choose Configuration file to use window is displayed.


100


Specify the configuration file The Choose Configuration file to use window enables you to provide the configuration .xml file to use when you are performing an advanced installation.


Click Browse. The Choose file to use window is displayed.

b.

Navigate to the drive and folder in which the .xml file is located, select it, and then click Open.

2. Click Next. The Client Connections window is displayed.


101


Provide the client connections to server instances The Client Connections window enables you to provide new or modify existing server connection information. You can define client connections for all of the JDA SCE applications and instances with which you will work from this client installation. Client connections include a name and the server instance connection URL.

1. Enter the connection information: Note: To enter connection information later, leave the fields blank. IMPORTANT: The client instance name can contain up to 10 characters with the exception of the following characters: / : * ? " < > | \ - . or spaces. a. In the Name column, enter a name for the connection. The name can be the same as the name of the server instance to which you want to connect (for example, Production, Training, DevServer, or ModelSvr); however, the name does not need to match (for example, Live1, Live2, or Train0673). Create a name that helps you understand the server instance to which your client instance is connecting. b.

In the Connection Url column, enter the URL that was created for the server instance during the server installation. Note: The URL consists of the server name and port number for the server instance and a constant value (service). Example:http://:/service

c.

If you will be using the client software to work with multiple JDA SCE applications or multiple instances of one JDA SCE application, continue to enter Name and Connection Url values until all of the client connections are defined. IMPORTANT: If users at this workstation work with multiple instances of a JDA SCE application or with multiple applications, do not create a default connection.

d.

To create a default connection that defines the server instance to which you connect each time you start the JDA SCE client software, in theDefault Server column select the check box.


102


2. Click OK. The Start Copying Files window is displayed. 3. If a message states that the required version of .NET is not installed, install it: a.

Click Cancel. The installation program is closed.

b.

Manually install the required version of .NET. Note: You can find thedotnetfx35.exe installation executable file in the 3rdParty folder on the JDA installation DVD.

c.


Start the file copy process The Start Copying Files window enables you to verify the installation information that you provided and start the installation process. The information listed (for example, client software and connection specifics) should match the selections that you made earlier.

1. Review the information. 2. If the information is not accurate, clickBack and make the necessary changes. 3. To start copying the files, click Next. The Setup Status window displays the progress of the installation. Note: To cancel the installation after file copying begins, click Cancel. 4. When a message asks to add shortcuts to the desktop, to install the desktop icons for accessing the applications, click Yes. If you click No, you must use theStart menu on your workstation to access the applications. The InstallShield Wizard Complete window is displayed.


103


Finish The InstallShield Wizard Complete window indicates that the client software installation successfully completed.

1. If a message states that the workstation must be restarted because a shared application core component was installed, perform one of the following tasks: •

To restart the workstation now, selectYes, I want to restart my computer now.

•

To restart the workstation later, selectNo, I will restart my computer later .

IMPORTANT: If restarting the workstation is required, the installation will not work correctly until it is performed. 2. Click Finish. 190). 3. Start the JDA SCE client and connect to a JDA SCE application (on page


104

UNIX server installations

Chapter 4. UNIX server installations This chapter explains how to install the server software in one or multiple instances on a UNIX server platform.

Introduction What you can install Depending on your system configuration and requirements, you can install the following server components: •

Event Management

•

Portal server

Some of the server components can be installed in the same instance; however, other server components must be installed in separate instances. Specific component installation compatibility is described in the installation steps that follow in this guide and is validated by the installation program. Separate instances can be installed on the same server or different servers.

Installation sequence Depending on your configuration, you may need to install one or more of the server software applications in a different instance or on a different server. If performing multiple server installations, complete them in the following order: 1. Application server software 2. Portal server software 17). 3. Required hotfixes for each installed instance, if any. See Required hotfixes (on page

Before you begin Before you begin the server software installations, be sure that you have met all of the prerequisites and completed all of the pre-installation procedures identified earlier in this guide. In addition, if you have installed a version of Perl that is different from the version that came with the operating system, verify the version: 1. Log in as a root user to the server on which you want to install the products. perl -v 2. Verify the Perl version with the following command from the # prompt: 3. When a message states the Perl version number, verify that it is 5.8.8 or later. If it is not, then you must manually download and install the correct version of Perl before proceeding with the installation.

Time requirement Allow approximately two hours to install the server software on a UNIX platform.


105


Working and physical directories The installer program prompts you to define a working and physical directory: •

The working directory is similar to a shortcut. That is, it lets you access the components from one location even though they are installed in multiple locations. Example: /opt/redprairie/wlmp

•

The physical directory is the location on the server in which the files for a component reside; that is, they physically take up disk space. The physical directory must have enough free disk space to accommodate the installation. Example: /mnt/d3/redprairie/wlmp When prompted during the installation, you should not accept the default physical directory unless it has enough free disk space to contain the components that are to be installed.

Install the application server software Complete the following procedures to install the application server software. If your configuration requires you to install the server programs in multiple instances on one server, or on different servers, you must complete the following procedures for each instance that you have to install.

Create the instance 1. Log in as a root user to the server on which you want to create the instance. 2. Insert the JDA UNIX DVD into the CD/DVD drive. 3. Access the directory in which the installer program resides with the following command from the # prompt: cd /mnt/dvdrom/unixserver/install ./RootInstall 4. Run the installer program with the following command from the # prompt: 5. On the Installer window, enter information into the following field: Do You Accept the license Agreement: Enter Y. 6. On the Set Distribution Source window, enter information into the following field: Distribution source: Path to the directory in which the installation files are located. Note: The distribution source value defaults to the full path for the directory that you accessed to start the installer program.


106


7. On the Set Environment Configuration window, enter information into the following fields: •

Environment name: Name for the instance. IMPORTANT: The name is case-sensitive so it must be entered in lowercase. Note: The unique instance name distinguishes the instance from any other JDA product instances that you may have installed on the server.

•

UNIX user’s login: Login name for the UNIX user. You should enter the name of a user that does not already exist. By using a new name, the./RootInstall installation program creates the new user and correctly sets up all of the operating system configuration, such as the user's home directory and login shell. However, if you specify a name that already exists as a user on the operating system, the installation program does not perform any additional operating system user configuration to avoid overwriting existing user information. Reusing an existing user typically results in installation issues because the operating system user configuration is not correctly set up. Note: If you are using OS user authentication, then be sure that the UNIX user matches the database user.

•

group: Group name for the UNIX user. IMPORTANT: When you enter (create) the UNIX user's login and group, you are defining the administrator for the instance. The names are limited to 10 characters, and they must be unique on the server. Typically, the login and group name are the same as the instance name. Be sure to record the UNIX user's login name because you will create a password for the user later in the installation process. You then use the user name and password to log in to the instance that you are installing to create the database schema and load the default data.

•

Auto startup: To automatically start, enterY; otherwise, enterN.

•

Port number: Unique port number for the instance on the server. Note: Check with your network administrator for a valid server port number.

•

RMI Port: Java remote method invocation (RMI) port for the instance on the server. Accept the default port number or enter a unique port number. Note: Check with your network administrator for a valid RMI port number.

•

Working directory: Working directory. Accept the default path value or enter the full path to the correct location. IMPORTANT: To ease the upgrade process, you should use the default destination location. If you choose to change the destination folder, be sure that the path to the working and physical directories, including the folder name, does not include spaces.

•

Physical directory: Physical directory. Enter the full path to the correct location. You should only accept the default path value if it has enough free disk space to contain the components that you are installing.

8. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation.


107


9. On the Set Administration Files Configuration window, enter information into the following fields: •

Start script name: Startup script name. Accept the default script name or enter a startup script name. IMPORTANT: To ensure that startup and shutdown occur in the appropriate sequence, you should use the default script names. If you change the startup and kill script names, be sure that their prefix numbers (for example, S95 and K05) fall in the appropriate sequence for startup or shutdown. For example, the product startup script must have a higher prefix number than the Oracle startup script.

•

Kill script name: Kill script name. Accept the default script name or enter a kill script name.

10. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 11. On the Set Perl Configuration window, enter information into the following field: Directory: Location of Perl. Accept the default directory or enter the full path to the directory in which the installation of Perl that you want to use exists. IMPORTANT: You should use the version of Perl in/usr/bin to ensure that the correct version is used. Note: The installer uses the version of Perl that comes with UNIX and is installed /usr/bin in . 12. If you are prompted again for theDirectory, enter the correct Perl location (the installer did not find Perl in the specified directory). 13. Press Enter to continue. 14. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 15. On the Web Server Configuration window, in theWill this install be a Web Serverfield, enter N. 16. On the Validating Configuration for Installation window: a.

If errors are reported: i.

Press Enter. The installer program exits.

ii.

Check the log files in the /tmp/redprairie directory to determine the cause of the errors, and then fix the errors.

iii. Run the installer program again. Repeat the process until no errors are reported during the information validation. Note: When you run the installer program again, all information that you previously defined is displayed as default values. Make the necessary changes to the default values to fix the errors. b. If errors are not reported, press Enter. The installation begins. When the installation is complete, a message states that the installation was completed successfully. The install program closes and a command prompt is displayed. Note: It is suggested that you also check warning messages in the log files; however, you are not required to correct warnings before you continue with the installation.


108


Set the password for the UNIX user 1. Log in as a root user to the server on which you created the instance. 2. Set the UNIX user's password with the following command from the # prompt: passwd 3. When you are prompted for a new password, enter the password for the UNIX user. 4. When you are prompted to confirm the password, enter the password again. A message states that the password was changed successfully. 5. Log out as the root user.

Select the products to install 1. Log in as the UNIX user to the instance. Note: For new installations, use the UNIX user's login name and password that you created earlier in the installation process. If you used an existing user's login name, execute .profile in the $LESDIR directory to set your MOCA environment. For upgrades, use the UNIX user's login name and password that you created when you initially installed or upgraded the instance using the UserInstall script. 2. Insert the JDA UNIX DVD into the CD/DVD drive. 3. Access the directory in which the installer program resides with the following command from the $ prompt: cd /mnt/dvdrom/unixserver/install java -jar 4. Run the installer program with the following command from the $ prompt: userinstall.jar 5. On the Installer window, enter information into the following field: Do You Accept the license Agreement: Enter Y. 6. On the Set Distribution Source window, enter information into the following field: Distribution source: Path to the directory in which the installation files are located. Note: The distribution source value defaults to the full path for the directory that you accessed to start the installation program. 7. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 8. On the Select major product(s) window, enterY for the prompts that correspond to the primary N for all others: product or product group from the following list; enter •


9. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 10. On the Select install type(s) window, enter Y for the prompts that correspond to the following option or options; enterN for all others: •

Application Server



109


Y for the prompts that correspond to the 12. On the Select Product Features to Install window, enter N for all others: components from the following list that you want to include in this instance; enter •

Event Management

13. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. \log directory. 15. Press Enter to continue. 16. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 17. On the Validating Configuration for Installation window: a.

If no errors are reported, pressEnter. The installation continues.

b. If errors are reported: i.

View the log files (typically located in /LES/log) for more information about the errors.

ii.

Press Ctrl+C to quit the installation program.

iii. Fix the errors. iv. Restart the userinstall.jar program. 18. When the installation is complete, press Enter. 19. On the Installing Products window: a.




ii.


iii. Fix the errors. iv. Restart the userinstall.jar program. 20. When the installation is complete, press Enter. 21. On the Installing Database Utils window: a.


b.



ii.


iii. Fix the errors. iv. Restart the userinstall.jar program.


110


Install.cfg: 22. After a message states that the installation program is persisting a.




ii.


iii. Fix the errors. iv. Restart the userinstall.jar program. 23. After a message states that the installation is complete: a.

If no errors are reported, pressEnter. The installation completes. Note: An exit status of 0 indicates a successful installation.



ii.


iii. Fix the errors. iv. Restart the userinstall.jar program. 24. Log out of the instance. IMPORTANT: If you do not log out of the instance, your installation will not perform as expected.

Configure the registry 1. If you did not log out at the end of the last procedure, then log out of the instance. 2. Log in as the UNIX user to the instance. The UNIX user prompt is displayed. Note: Use the same UNIX user's login name and password that you created earlier in the installation. 3. Change to the database directory with the following command from the $ prompt: cd dtbs/database java -jar 4. Run the registry program with the following command from the $ prompt: ./mocareg.jar Note: The registry program automatically loads the registry tasks. It can also be run again to make updates instead of manually editing theMOCA_REGISTRY file. 5. On the Modify Service Configuration window, enter information into the following fields: •

Host name: Name of the server that is hosting the instance.

•

Service URL: The value is defaulted tohttp://:/service.



111


7. On the Modify Java Configuration window, enter information into the following fields: •

•

64-bit Java path (vm): Location of the 64-bit JVM. 64-bit Java arguments (vmargs): Arguments to use when starting the 64-bit JVM. The minimum value must be-server -Xmx4096m -XX:MaxPermSize=192m .

8. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 9. On the Modify Database Connection Configuration window, enter information into the following fields: •

Choose database to use: Database software that is used to store data for this instance. Enter one of the following numbers:

•

•

•

1: Oracle 12

•

2: SQL Server 2014

•

3: None; a database is not needed for this instance. Continue with the next step.

JDBC connection string: Java Database Connectivity connection string for accessing the database. The installation program window displays examples of the URL that you should enter. For more information on the URL format, see the Oracle or SQL Server database documentation. Database User: Database user's login: Note: If you do not have the database login information, contact the database administrator.

•

•

If you are using database user authentication, enter the database user's login.

•

If you are using OS user authentication, leave the field blank.

Password: Database user's password: •

If you are using database user authentication, enter the database user's password.

•


Note: The password is redisplayed as encrypted text instead of cleartext. 10. If you are using an Oracle database, on the Customize Database window, indicate whether you want to customize the user's tablespace definition file. Enter one of the following options: •

To leave the default tablespaces unchanged, enter1 (Use standard settings).

•

2 (Manually customize To view and customize the user's tablespace definition file, enter usrtbldef.h). Note: Option 2 lets you edit the usrtbldef.h file. During the installation process, the file opens in text format so that you can make changes. After you make the changes and save the file, the installation process proceeds.

•

To use the default database user's tablespace for all tables, enter 3 (Use dbuser's default tablespace for all tables). IMPORTANT: Option 3 is the default, recommended option. Note: Option 3 is for environments where database performance is not an issue, such as development and demonstration environments. No tablespaces need to be manually created, since tables are automatically created in the default tablespace for the database user.


112


11. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 12. On the Modify Reporting Configuration window, enter information into the following field: Reporting url (if any): Leave blank. 13. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 14. On the Modify Event Management Configuration window, enter information into the following fields: •

Event Management url (if any): Leave blank (since you are installing Event Management in

•

this instance). Event Management SMTP: IP address or network name for the Event Management e-mail server. IMPORTANT: This server is the Simple Mail Transfer Protocol (SMTP) server that Event Management will use. The information is required to receive alerts from Event Management.

15. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 16. On the Modify Portal Server Configuration window, enter information into the following fields: IMPORTANT: The Portal Server url field is required if you are installing Warehouse Management, Reporting, or Event Management in the instance. Otherwise, leave the field blank. •

•

Portal Server url (if any): URL for the separate portal server instance. The required format for the URL is http://:/service. Portal Server dir (if any): If your configuration includes customized web pages (forms), then enter the path information for the portal server directory. The directory information is needed to allow customizations to compile and deploy to the portal server.

17. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 18. Several windows are displayed displaying the results of the registry configuration process. Press Enter to continue on each window.

Check the login information and create the database schema 1. If you are not already there, navigate to the$LESDIR/dtbs/database folder. 2. Verify that the user name, password and database tablespaces are accurate with the following command from the $ prompt:java -jar dbcheck.jar Note: If errors are reported, contact your database administrator before continuing with the installation. 3. When a message states that the database is ready for installation, create the database schema with the following command from the $ prompt:java -jar dbcreate.jar


113


4. When a message asks if you want to continue, enterY; otherwise, enter N. Entering Y displays the database schema creation progress. Entering N exits without creating the database schemas. 5. When the process is complete, perform one of the following tasks: •

•

If a message states that the database schema creation process was successful, continue with the procedure. If errors are reported, check the dbcreate-log file, which is located in the $LESDIR/log directory. The log file ide ntifies the log file in which the error is documented and the line on which the error is displayed. Contact your system or database administrator to fix the errors before continuing with the procedure.

Load the distributed data 1. Log in as the UNIX user to the instance. cd dtbs/database 2. Access the database directory with the following command from the $ prompt: java -jar dbload.jar 3. Load the data sets with the following command from the $ prompt: 4. When a message asks you to choose each data set that you want to load into the database, N enter Y for the data sets from the following list that you want to include in this instance; enter for all others: •

Load BASE Data: Required.

•

Load 3PL data: Select if third-party logistics (3PL) functionality is part of your configuration.

5. When a message asks if you want to continue, enterY; otherwise, enter N. Entering Y displays the data set load progress. Entering N, exits without loading the data sets. Note: The data set loading process takes approximately 45 minutes. 6. When a message states that the distributed data was loaded successfully, perform initial system java -jar postdbload.jar configuration with the following command from the $ prompt: 7. Exit the session.

Unmount the DVD 1. Log in as a root user to the server. umount /mnt/dvdrom 2. Unmount the DVD with the following command from the # prompt:

Start the service Before you can access the instance of the product from a client workstation, the service must be started. 1. Log in as the UNIX user to the instance. rp start 2. Start the service with the following command from the $ prompt:

What to do next 1. To install additional application server software, return to Install the application server software (on page 106). 2. To install portal server software in a separate instance (on this server or another server), continue with Install the portal server software (on page115). 3. If you have installed all of the server software that you want to install, continue with Install the JDA SCE client software (on page93).


114


Install the portal server software Complete the following procedures to install a separate instance of the portal server software.

Create the instance 1. Log in as a root user to the server on which you want to create the instance. 2. Insert the JDA UNIX DVD into the CD/DVD drive. 3. Access the directory in which the installer program resides with the following command from the # prompt: cd /mnt/dvdrom/rpweb ./RootInstall 4. Run the installer program with the following command from the # prompt: 5. On the Installer window, enter information into the following field: Do You Accept the license Agreement: Enter Y. 6. On the Set Distribution Source window, pressEnter to accept the default information or enter information into the following field: Distribution source: Path to the directory in which the installation files are located. Note: The distribution source value defaults to the full path for the directory that you accessed to start the installer program. 7. On the Set Environment Configuration window, enter information into the following fields: •

Environment name: Name for the instance. IMPORTANT: The name is case-sensitive so it must be entered in lowercase and contain no spaces. Note: The unique instance name distinguishes the instance from any other JDA product instances that you may have installed on the server.

•

UNIX user’s login: Login name for the UNIX user. You should enter the name of a user that does not already exist. By using a new name, the./RootInstall installation program creates the new user and correctly sets up all of the operating system configuration, such as the user's home directory and login shell. However, if you specify a name that already exists as a user on the operating system, the installation program does not perform any additional operating system user configuration to avoid overwriting existing user information. Reusing an existing user typically results in installation issues because the operating system user configuration is not correctly set up. Note: If you are using OS user authentication, then be sure that the UNIX user matches the database user.

•

group: Group name for the UNIX user. IMPORTANT: When you enter (create) the UNIX user's login and group, you are defining the administrator for the instance. The names are limited to 10 characters, and they must be unique on the server. Typically, the login and group name are the same as the instance name. Be sure to record the UNIX user's login name because you will create a password for the user later in the installation process. You will then use the user name and password to log in to the

•

instance that you are installing to create the database schema and load the default data. Auto startup: To automatically start, pressEnter to accept the defaultY; otherwise, enter N.


115


•

Port number: Unique port number for the instance on the server. Note: Check with your network administrator for a valid server port number.

•

Working directory: Working directory. Accept the default path value or enter the full path to the correct location. IMPORTANT: To ease the upgrade process, it is recommended that you use the default destination location. If you choose to change the destination folder, be sure that the path to the working and physical directories, including the folder name, does not include spaces.

•

Physical directory: Physical directory. Accept the default path value or enter the full path to the correct location.

8. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 9. On the Set Administration Files Configuration window, enter information into the following fields: •

Start script name: Startup script name. Accept the default script name or enter a startup script name. IMPORTANT: To ensure that startup and shutdown occur in the appropriate sequence, it is suggested that you use the default script names. If you change the startup and kill script names, be sure that their prefix numbers (for example, S95 and K05) fall in the appropriate sequence for startup or shutdown. For example, the product startup script must have a higher prefix number than the Oracle startup script.

•

Kill script name: Kill script name. Accept the default script name or enter a kill script name.

10. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. Enter. The 11. On the Ready to Install window, when you are prompted to start the installation, press instance is created.

Set the password for the UNIX user 1. Log in as a root user to the server on which you created the instance. 2. Set the UNIX user's password with the following command from the # prompt: passwd 3. When you are prompted for a new password, enter the password for the UNIX user. 4. When you are prompted to confirm the password, enter the password again. A message states that the password was changed successfully. 5. Log out as the root user.

Select the products to install 1. Log in as the portal server UNIX user to the instance. Note: For new installs, use the portal server UNIX user's login name and password that you created earlier in the installation process. If you used an existing user's login name, execute .profile in the $LESDIR directory to set your MOCA environment. For upgrades, use the portal server UNIX user's login name and password that you created when you initially installed or upgraded the instance using theUserInstall script. 2. Insert the JDA UNIX DVD into the CD/DVD drive.


116


3. Access the directory in which the installer program resides with the following command: $ cd /mnt/dvdrom/rpweb java -jar install_rpweb.jar 4. Run the installer program with the following command: $ 5. On the Portal Server Installation Information window, enter the portal server installation directory. 6. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 7. On the Portal Server Application window, enterY for the prompts that correspond to the product or products from the following list; enter N for all others: •

Portal Server

•

Event Management

8. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 9. On the Server Information window, enter information into the following fields: •

Server Port: Port number on which the portal server will run. The portal server is a serverside web server that provides common web server functionality, such as session management, security, single sign on authentication, internationalization and localization, and language management. The default port number is 8060.

•

Stash URL: Full URL to the Stash server. The Stash server stores the client-side library that provides common components, such as calendars and other controls. The required format for the URL is http://:/stash.

•


•

Base Locale: Identifier for the primary locale. The locale ID, which defaults to United States English, controls the cultural features, such as language, calendar, and date and time formats. The client and server use locale ID to configure your user-interface to meet your language requirements.

Enter. 10. If the information is okay and you are finished, press 11. On the Connection Information window, for EMS, enter information into the following fields: •

Connection Name: Site name of the connection.

•

Connection Type: Enter moca.

•

Application Name: Enter ems.

•

Address: Server connection that portal server is to use to connect to the Event Management application server. The required format for the URL is http://:/service.

Enter. 12. If the information is okay and you are finished, press


117


13. For MCS, enter information into the following fields: •


•


•

Application Name: Enter mcs.

•


Enter. 14. If the information is okay and you are finished, press 15. On the Authentication Information window, perform one of the following tasks: •

•

If you want a JDA SCE server to supply the infrastructure for authentication and authorization, enter information into the following fields: •

Authentication Type: Enter Native.

•

Authentication Site Name: Name of the instance of record for all authentication requests.

If you want an external entity to provide authentication, enter information into the following fields: •

Authentication Type: Enter Reverse Proxy.

•

Proxy Header: Header that will be used to find the user ID. Note: The contents of the header must contain the user ID of the user that is to be logged in.

•

•

•

SSO Close URL: Destination URL to be opened when portal server is closed.

To use Enterprise Federated Authentication, enter information into the following fields: •

Authentication Type: Enter Federated SSO.

•

Proxy Header: Header that will be used to find the federated token.

•

Federated SSO Validation Service: Token which is understood by the federated service.

•

SSO Close URL: Destination URL to open when portal server is closed.

To authenticate with an LDAP server, in theAuthentication Type field, enter LDAP.



118


17. On the Database Connection Information window, enter information into the following fields: •

Database Type: Database software that is used to store data for this instance. Enter one of the following types: •

oracle

•

sqlserver

•

JDBC Url: Java Database Connectivity connection string for accessing the database. The installation program window displays examples of the URL that you should enter. For more information on the URL format, see the Oracle or SQL Server database documentation.

•

User: Database user's login: •

•

•

•

•

If you are using database user authentication, enter the database user's login. If you are using OS user authentication, leave the field blank.



•


DBO User: Database administrator's login: •

If you are using database user authentication, enter the database administrator's login.

•


DBO Password: Database administrator's password: •

If you are using database user authentication, enter the database administrator's password.

•


Enter. 18. If the information is okay and you are finished, press 19. Press Enter. 20. Log out of the instance. IMPORTANT: If you do not log out of the instance, your installation will not perform as expected.

Run the database batch scripts 1. If you did not log out at the end of the last procedure, then log out of the instance. 2. Log in as the UNIX user to the instance. The UNIX user prompt is displayed. 3. Access the bin directory within the rpweb directory with the following command from the $ prompt: cd bin 4. Run the following batch scripts from the $ prompt: •

db

•

db all

•

Verify the portal sever installation by reviewing the db and db all logs within the rpweb/logs directory.


119


Start the service Before you can access the portal server instance from a web browser, the service must be started. 1. Log in as the portal server UNIX user to the instance. cd bin 2. Access the bin directory with the following command from the $ prompt: refs-server start 3. Start the service with the following command from the $ prompt:

What to do next Continue with Install the JDA SCE client software (on page 93).


120

Application upgrades

Chapter 5. Application upgrades This chapter explains how to upgrade an existing instance to this version on a Windows or UNIX platform. IMPORTANT: •

Before you begin the upgrade process, be sure that you have met all of the prerequisites and completed all of the pre-installation procedures identified in Before you install or upgrade (on page 4).

•

After upgrading an existing instance, you must install required hotfixes, if any. See Required hotfixes (on page 17).

Upgrade an instance on Windows Use the following procedure to upgrade a server software installation on a Windows server platform. IMPORTANT: •

If you are upgrading an instance that is earlier than 2010.1.x, you must perform another upgrade before you perform this upgrade. For more information, see Pre-installation or upgrade tasks for the server software (on page11).

•

The installation program upgrades all of the server software programs installed in a single instance. If you have the programs installed in multiple instances, for example, if you have the application server software installed in one instance and the Reporting software installed in another, then you must upgrade each server instance individually.

Time requirement Allow a minimum of two hours to complete the upgrade procedure. The actual time required to complete this upgrade is dependent upon the size of your database.

Installation wizard window examples The installation wizard window examples that are displayed in this chapter are representative of the windows that you see when performing an installation. The example may not always display the exact information that you see.

Stop the IIS and JDA services Although the installation wizard verifies that these services are shut down before the upgrade begins, complete the following tasks to ensure that the upgrade proceeds successfully. 1. Ensure that all users are logged off. 2. Log in as an administrator to the server on which the instance that you want to upgrade is installed. 3. From the Start menu, display the list of programs, then selectAdministrative Tools, and then select Services. Note: If you do not see Administrative Tools in the list of programs, then from theStart menu, select Control Panel, and then select Administrative Tools. 4. In the right pane, scroll down to IIS Admin Service. 5. Right-click the service and then select Stop.


121


6. If the Stop Other Services window is displayed listing the other services that will be stopped and asking if you want to stop those services, click Yes. Note: A message indicates that the service control is attempting to stop the service. When the service is stopped, the status on the Services window is cleared. 7. On the Services window, scroll down to and then right-click the JDA service that you want to stop. Example: The service name typically is displayed as MOCA Server (), RedPrairie (), or RedPrairie MOCA Server (). 8. Select Stop. 9. When the service is stopped, close the Services window.

Start the installation 1. If you are using operating system (OS) user authentication, log in as the local or domain Windows user (that you assigned to the database) to the server on which you want to install the software. 2. If you are using database user authentication, log in as an administrator to the server on which you want to install the software. 3. Insert the JDA SCE Windows DVD into the CD/DVD drive. 4. On the desktop, double-click theMy Computer icon and then double-click the icon for the drive that contains the JDA SCE Windows DVD. 5. Double-click the Server folder, double-click the windows folder, and then double-click setup.exe. 6. If a security warning asks to run thesetup.exe software, clickYes. The software launches the product setup program.


122


Select the installation mode The Installation Mode window enables you to select whether you are installing a new version of server software or upgrading (with or without adding components) an installation that already exists.

1. Select the Upgrade or Modify check box. 2. Click Next. If Perl and Java are installed properly on the server, a message states that the Microsoft Visual C++ 2008 re-distributable package is being installed. 3. If a message indicates that Perl is required, perform the following tasks: a.

Click OK. The installation program is closed.

b.

4). Obtain a supported version of Perl, as indicated in Technical specifications (on page

c.

Manually install Perl, accepting the default settings on the installation wizard windows.

d. Restart the server, and then restart the installation program. 4. If a message states that the Java version is too low or unknown, or there are two different results on the version test, perform the following tasks: a.

Click OK.

b. When the JavaInstallHelp.TXT file is displayed, review or print the file for step-by-step instructions on how to correct the issue. c.

Exit the installation program, and then correct the issue.

d.

After correcting the issue, restart the installation program.


123


Specify the configuration file path The Choose Configuration File Path window enables you to enter the path to the .ini file that contains license or server configuration installation information.

1. If you do not have a license or server configuration.ini file s aved on the server, accept the default information that is displayed. 2. If you have a license or server configuration.ini file saved on the server: a.


b.

Select the drive and folder in which the .ini file is located.

c.

Click OK.

3. Click Next.


124


Select additional applications The Product Upgrade - Additional Products window enables you to select any additional components you want to install with this upgrade.

1. Select the check boxes that correspond to the additional components that you want to install with this upgrade. IMPORTANT: If you are upgrading a version of Reporting that is 2011.2.0 or earlier, be sure to select Reporting, and if applicable Reporting - Web Enablement. Selecting the Reporting options installs the new Reporting components that are part of the 2011.2.1 Reporting enhancements, and are required for reports to generate. Note: The installation program will validate the selections. If you select a component that conflicts with the other software in this instance, a message indicates which component cannot be installed with this upgrade. Also, the installation program prevents you from upgrading from a version that is older than the minimum upgrade version requirement, if one exists. The minimum upgrade version validation helps prevent potential complications that cannot be handled automatically when upgrading from a much older version of the software.


125


2. Click Next.

3. If the information is accurate, click Next; otherwise, click Back to make corrections before continuing with the installation.


126


Provide the portal server instance connection information The Portal server information window enables you to enter the portal server instance connection information. The portal server is installed in a separate instance, so if one of the following statements is true, you must provide the connection information to enable communication between the application and portal server instances: •

This application instance includes Warehouse Management.

•

This application instance includes Reporting.

•

This application instance includes Event Management.

•

This application instance includes JDA Parcel, and the optional JDA Parcel web services functionality is part of your configuration.

Otherwise, you can bypass the following installation windows.

Portal URL field, enter the URL for the portal 1. If portal server is part of your configuration, in the server instance. Example:http://:/


127


2. Click Next.

3. If your configuration includes customized web pages (forms), then select the path information for the portal server directory. The directory information is needed to allow customizations to compile and deploy to the portal server. a.


b.

Select the drive and installation folder.

c.

Click OK.

4. Click Next.


128


Provide the port information The Port Information windows enable you to enter port numbers for the MOCA server to listen for incoming requests from MOCA clients and Java to use for remote method invocation (RMI). Each instance of JDA SCE products on a server must have a unique port number for communicating with the JDA SCE client, and a unique port number for Java RMI. Note: Check with your network administrator for a valid server port number. Server port numbers range from 1024 to 5999 and 6101 to 65535. Port numbers 6000 to 6100 are not acceptable ports for JDA SCE connections as they are ports used for Windows and cannot be opened in firewalls.

1. In the text field, enter a port number for the installation, or accept the default. If you enter a port number that is already in use, a message asks whether to use the entered port number. To use the entered port number, clickYes. Note: Although each instance that you use must have a unique port number, you can enter a port number that is already in use. You might want to do this, for example, if you plan to uninstall the old instance that is currently using the port number or plan to only use one instance at a time (which is not typical for a production instance).


129


2. Click Next to provide additional port information.

3. In the text field, enter a port number for Java to use for RMI for the installation, or accept the default. If you enter a port number that is already in use, a message asks whether to us e the entered port number. To use the entered port number, clickYes. 4. Click Next.


130


Provide the instance URL The Service URL Information window displays a unique URL for the instance. Each instance that you install is identified with a unique URL that consists of the host name and the port number that you provided earlier in the installation process, and a constant value of service.

1. In the text field, accept the default or enter the URL for the instance. You should use the default value. The required format for the URL ishttp://:/service, where: •

: Domain name of the server on which you are installing the instance.

•

: Port number that you assigned to the instance earlier in the installation process.

2. Click Next.


131


Provide the locale ID The Locale Information window enables you to enter the locale ID. The locale ID, which defaults to United States English, controls the cultural features of the JDA SCE applications, such as language, calendar and date, and time formats. The client and server use locale ID to configure the userinterface to meet your language requirements.

1. In the text field, accept the default or enter a different locale ID for this instance. 2. Click Next.



132


Select the service startup setting The MOCA Component: Service Startup Setting window enables you to select whether you want the JDA SCE service to start automatically after a server restart, or you want to manually start the service after every server restart.

Auto Start MOCA Service. 1. To restart the service automatically after every server restart, select If you are installing a production instance, you should select this option. Manually Start MOCA Service. 2. To restart the service manually after every server restart, select If you are installing a non-production instance that does not need to be constantly available, such as one used for testing or development, you might want to select this option so that you do not have too many instances using memory or attempting to restart at the same time. 3. Click Next.


133



1. To use database user authentication, selectUse Database User Authentication. 2. To use database OS user authentication, selectUse Windows Operating System User Authentication. 3. Click Next.


134


Provide the Reporting instance information If Reporting is not being installed in the instance, the MOCA Report Server: Report Server URL Step window enables you to enter the connection information to support communication between the products. If Reporting is not part of your configuration, you can bypass the installation window.

1. If Reporting is part of your configuration, in the text field enter the URL for the Reporting instance. The required format for the URL ishttp://:/service, where: •

: Domain name of the server on which the Reporting instance is installed.

•

: Port number assigned to the Reporting instance on the server specified by .

2. Click Next.


135


Provide the SMTP server information If you are installing Event Management in this instance, the SMTP server information window enables you to enter the Event Management email server information. IMPORTANT: The SMTP server information is required in order to receive alerts from Event Management.

1. In the SMTP field, enter the IP address or network name for the SMTP email server that Event Management will use for sending email alerts. 2. Click Next.


136



1. If the instance is in a non-clustered environment, or the first instance in a clustered environment Do not change databasecheck box is where all instances use the same database, verify that the deselected. 2. If the instance is in a clustered environment where all instances use the same database and the Do not instance is not the first instance that you are initially installing or upgrading, select the change database check box. 3. Click Next.


137


Start the file copy process The Start Copying Files window enables you to verify the installation information that you provided before starting the installation process. The information listed here (for example, products and connection specifics) should match selections that you made earlier in the setup process.

1. If the information is accurate, click Next to start copying the files; otherwise, clickBack to make corrections before continuing with the installation. Note: To cancel the setup after file copying begins, on the Setup Status window, click Cancel. 2. If a message states that IIS needs to shut down, clickYes. IIS then stops and restarts before the file copy process begins. The Setup Status window is displayed, to indicate the progress of the installation. Server installations can display several additional installation progress windows, such as Creating Database Schemas and Loading Data Sets.


138


Adjust the registry Java settings If the instance's MOCA registry Java virtual machine (vm) settings are set, but set too low, the Registry Java settings window enables you to adjust the values. Note: If the settings are not set in the MOCA registry, instead of displaying the Registry Java settings window for you to enter values, the installation program automatically updates the settings with the recommended values and continues with the upgrade. 1. If a message indicates that the Java vmargs check discovered that the existing registry values are Yes. lower than the recommended settings, and asks if you want to modify the settings now, click Note: While you typically want to use the recommended values for your instances, you might have an instance that has been to a lowerinstance value and do notthat want to update to the recommended settings; forintentionally example, a set development onyou a server does not have enough memory.

vmargs32 field, enter a 2. If the error check indicates that the vmargs32 value is too low, in the minimum of -client -Xmx128m. vmargs field, enter a minimum 3. If the error check indicates that the vmargs value is too low, in the of -server -Xmx4096m -XX:MaxPermSize=192m . 4. Click Next. If a message indicates that additional errors exist, repeat the steps to fix the issue; otherwise, the installation continues.


139



1. If the window states that you must restart your computer, perform one of the following tasks: •

To restart the computer now, selectYes, I want to restart my computer now .

•

To restart the computer later, selectNo, I will restart my computer later. IMPORTANT: The installation will not work correctly until the computer is restarted.

2. Click Finish.

Upgrade the Integrator data Upgrading the Integrator data is a manual process instead of an automated process to give you more control over what gets upgraded and when. IMPORTANT: The Integrator upgrade is required if you want to use the new functionality in this release; however, upgrading the data with the following procedure may affect customizations. If you are not certain that your customizations were created in the recommended format, then be sure to make a backup of your Integrator data before you proceed with this upgrade. If you choose not to upgrade the Integrator data, you may need to disable new triggers to avoid errors when using the application. 1. On the application server, open a command line prompt window: From the Start menu, display the list of programs, then selectAccessories, and then select Command Prompt. 2. On the Command Prompt window, change to theLES\data directory of your instance with the following command: cd \\LES\data


140


3. Type env.bat, and then press Enter to set the environment variables. 4. Navigate to the \\DCS\db\data\integrator directory. 5. Upgrade each transaction, with the following command: slUpgrade -f .slexp -v 6. When you are asked if you want to proceed, typeYes, and then press Enter. 7. When you are asked if you absolutely want to proceed, type Yes, and then Enter. 8. After the upgrade completes, close the Command Prompt window.

Start the service If you did not choose to start the service automatically, perform the following tasks to start the service now: 1. From the Start menu, display the list of programs, then selectAdministrative Tools, and then select Services. Note: If you do not see Administrative Tools in the list of programs, then from theStart menu, select Control Panel, and then select Administrative Tools. 2. In the right pane, scroll down to the service that you want to start. Example: The service name is typically displayed as MOCA Server (). 3. Right-click the service and then select Start. Note: If the service is already started, the Start option is not enabled.

What to do next 1. To upgrade another instance on a Windows platform, return to Upgrade an instance on Windows (on page 121). 2. To upgrade a portal server instance on a Windows platform, continue with Upgrade a portal server instance on Windows (on page141). 3. If you have upgraded all of the necessary server software, continue with Upgrade or add the JDA SCE client software (on page 177).

Upgrade a portal server instance on Windows Use the following procedure to upgrade a portal server software installation on a Windows server platform.

Start the portal server installation 1. If you are using operating system (OS) user authentication, log in as the local or domain Windows user (that you assigned to the database) to the server on which you want to install the server software. 2. If you are using database user authentication, log in as an administrator to the server on which you want to install the server software. 3. Insert the JDA Windows DVD into the CD/DVD drive. 4. On the desktop, double-click the My Computer icon, and then double-click the icon for the drive that contains the JDA Windows DVD.


141


5. Double-click the RPWeb folder, double-click therpweb.iss folder, and then double-click setup.exe. Yes. The software 6. If a security warning asks if you want to run the setup.exe software, click launches the product setup program.

To install a new instance of portal server, select Install a new instance of this application . 1. To change or upgrade an existing instance of portal server: a.


b.

Select the instance from the list.

2. Click Next.


142


Initiate the portal server installation The welcome window enables you to initiate the portal server software installation.

Click Next.


143


Accept the portal server license agreement To continue with the installation process, you must accept the license agreement.

1. Select I accept the terms of the license agreementto accept the agreement. 2. Click Next.


144


Select the portal server setup type The Setup Type window enables you to select the type of instance to install.

1. Select Event Management. 2. Click Next.


145


Specify the destination folder The Choose Destination Location window enables you to accept the default destination folder or specify a different folder.

1. To change the destination folder: IMPORTANT: To ease the upgrade process, you should use the default destination location. a.

Click Change. The Choose Folder window is displayed.

b. In the Directories list, select the folder into which you want to install the portal server software. c.

When the full path to the folder is displayed in the Path field, click OK. IMPORTANT: The Path field must not include spaces.

2. Click Next.


146


Select the features to install The Select Features window enables you to select the features to install. Note: As you select the features, the required disk space is displayed.

1. To install the Event Management and administration (such as user authorization) web-based functionality, make sure that the following check boxes are selected: •

RPWeb

•

Admin

•

Event Management System

2. Click Next.


147


Provide the portal server port information The Portal Server Configuration: Portal Server Port window enables you to enter the port number on which the portal server will run. The portal server is a server-side web server that provides common web server functionality, such as session management, security, single sign on authentication, internationalization and localization, and language management. The default port number is 8060. Note: Check with your network administrator for a valid server port number. Server port numbers range from 1024 to 5999 and 6101 to 65535. Port numbers 6000 to 6100 are not acceptable ports for portal server connections as they are ports used for Windows and cannot be opened in firewalls.

1. In the text field, enter a port number for the installation or accept the default. 2. Click Next.


148


Provide the Stash and static URLs The Portal Server Server Configuration: Stash and Static URL window enables you to enter the connection URLs for the Stash and static content servers.

1. Enter information into the following fields or accept the defaults: •

Stash: Full URL to the Stash server. The Stash server stores the client-side library that provides common components, such as calendars and other controls. The required format for the URL is http://:/stash.

•


2. Click Next.


149


Provide the portal server locale ID The Portal Server Server Configuration base locale window enables you to select the base locale. The base locale is used when a user-specific locale is not available. The locale controls the cultural features, such as language, calendar, and date and time formats. The client and server use the locale ID to configure the user interface to meet your language requirements.

1. From the drop-down list, select the base locale for this instance. 2. Click Next.



150


Configure the portal server connections The Portal Server Connections Maintenance window enables you to enter configuration information for each of the instances that connect to this instance of portal server.

1. Enter the application server URL information: a.

Under Connections, click MCS.

b.


c.

Under Connections, click EMS.

d.



To undo any changes to the fields on the window and revert back to the srcinal entries, click Discard Changes.

•

New. To add another application instance that will be connecting to the portal server, click

•

To delete one of the application instances that you connected to the portal server, under Connections, select the instance and click Delete.

•

To proceed with the installation, click NEXT.


151


Select the portal server authentication type The Portal Server Authentication Configuration window enables you to select the technology to use for authenticating and authorizing users for portal server functionality.

1. Select one of the following authentication types: •

Native: Use of a JDA SCE server (built-in federated authentication) or Cognos.

•

Reverse Proxy: Use of a trusted assertion from a third-party authority.

•

Federated SSO: Use of Enterprise Federated Authentication.

•

LDAP: Use of a Lightweight Directory Access Protocol server.

2. Click Next.


152


Provide the portal server authentication connection The Portal Server Authentication Configuration: Authentication Connection window enables you to enter a name for the connection to the instance of records for all authentication requests and user preferences, such as locale and time zone.

1. In the text field, enter a name for the connection to use for authentication or accept the default, such as MCS or EMS. 2. Click Next.


153



1. If you are using an Oracle database, selectOracle 12. SQL Server 2014. 2. If you are using a Microsoft SQL Server 2014 database, select 3. Click Next.


154



1. To use database user authentication, selectUse Database User Authentication. 2. To use database OS user authentication, selectUse Windows Operating System User Authentication. 3. Click Next. 4. If you selected an Oracle database, continue with Provide the Oracle database information (on page 156). 5. If you selected a Microsoft SQL Server database, continue with Provide the SQL Server database information (on page 160).


155



1. If you want to be prompted for each component needed in the JDBC connection string, select JDBC Thin Driver . 2. If you want to manually build the JDBC connection string with the details for accessing the Oracle database, select JDBC Url (Advanced). 3. Click Next.


156



a.




157


c.


d.


e.


f.



•



158



a.

b. c.

In the JDBC URL field, modify the default JDBC connection string with the details for accessing the Oracle database. For example, enterjdbc:oracle:thin:@srv001:1521:wlmp to access a database instance named wlmp on a server named srv001 and port number 1521. User field, enter the Oracle database If you are using database user authentication, in the user name. Password field, enter the Oracle If you are using database user authentication, in the database user password.


•



159





•


•



•

•

JDBC SourceForge/OS Authentication: To specify a port number-based database connection. JDBC SourceForge/Named Instance/OS Au : To specify a named instance-based database connection. JDBC SourceForge (Advanced): To manually build the JDBC connection string with the details for accessing the SQL Server database.


160


3. Click Next. Note: If using database OS user authentication or advanced JDBC SourceForge, the Login information windows look slightly different than what is displayed in the examples.



161





b.




162



a.

b.

DB Port field, If the connection is a port number-based database connection, then in the perform one of the following tasks: •


•


Instance field, If the connection is a named instance-based database connection, then in the enter the name for the appropriate SQL Server instance. IMPORTANT: The value that you enter in theInstance field is the name of the SQL Server instance that your JDA SCE server software will access. It is not necessarily the same name as the host name of the server on which the SQL Server database exists. To view the SQL Server instances on the database server, start the SQL Server Management Studio. The SQL Server instances are listed in the Object Explorer. If there are multiple instances, then under each instance, expand the Databases folder until you see your database name. Use the instance name under which your database is displayed.

12. Click Next. A message states that the database connection is being verified. If the connection is successful and the Read Committed Snapshot option for the Read Committed isolation level is enabled, the next window is displayed and you can continue with the installation.


163




•

No. The If you want to continue without reentering the database connection information, click next window is displayed and you can continue with the installation.

IMPORTANT: If you continue with an invalid database connection, your installation will be invalid and you will have to uninstall and reinstall the instance. If a message states that the database does not have theRead Committed Snapshot option for the Read Committed isolation level enabled, click Yes, and then exit the installation program. 4) for more See the pre-installation or pre-upgrade tasks in Before you install or upgrade (on page information on theRead Committed Snapshot option. When the database setting has been updated, restart the installation process.

Select whether to change the database The Database Component: Skip Database Step window enables you to selec t whether to change the database during the initial installation or upgrade process. Typically, you want to change the database. However, if you are performing an initialinstallation or upgrade in a clustered environment where several instances use the same database, then only the first instance's initial installation or upgrade process should run the database-related scripts. For thesubsequent instances' initial installations or upgrades, skip the change database step since the database was already changed with the rst fi instance.



164


Select whether to start the portal server service The start service after installation window enables you to select whether you want the installation program to automatically start the portal server service after the installation completes.

1. To start the portal server service after the installation completes, select the Start service after install check box. 2. Click Next.


165


Start the installation process The Ready to Install the Program window enables you to review the information that you have provided, continue with the installation, or exit the Installation Wizard.

Click Install.


166



Click Finish.

Start the service If you did not choose to start the service automatically, perform the following tasks to start the service now: 1. From the Start menu, display the list of programs, selectAdministrative Tools, and then select Services. Note: If you do not see Administrative Tools in the list of programs, from theStart menu, select Control Panel, and then select Administrative Tools. 2. In the right pane, scroll down to the portal server service to start. Example: REFS (). 3. Right-click the service, and then select Start. Note: If the service is already started, the Start option is not e nabled.

What to do next 1. SCE If you have upgraded of the necessary server software, continue with Upgrade or add the JDA 177 client software (onall page ). 2. To access a portal server instance from a web browser, Start the web client (on page 190).


167


Upgrade an instance on UNIX Time requirement Allow approximately two hours to complete the upgrade procedure.

Shut down the instance 1. Back up your database to ensure that information is not lost. 2. Log in as the UNIX user to the instance that you want to upgrade. rp stop 3. Shut down the instance with the following command from the $ prompt:

Select the products to install 1. Log in as the UNIX user to the instance. Note: For new installations, use the UNIX user's login name and password that you created earlier in the installation process. If you used an existing user's login name, execute .profile in the $LESDIR directory to set your MOCA environment. For upgrades, use the UNIX user's login name and password that you created when you initially installed or upgraded the instance using the UserInstall script. 2. Insert the JDA UNIX DVD into the CD/DVD drive. 3. Access the directory in which the installer program resides with the following command from the $ prompt: cd /mnt/dvdrom/unixserver/install java -jar 4. Run the installer program with the following command from the $ prompt: userinstall.jar 5. On the Installer window, enter information into the following field: Do You Accept the license Agreement: Enter Y. 6. On the Set Distribution Source window, enter information into the following field: Distribution source: Path to the directory in which the installation files are located. Note: The distribution source value defaults to the full path for the directory that you accessed to start the installation program. 7. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 8. On the Select major product(s) window, enterY for the prompts that correspond to the primary N for all others: product or product group from the following list; enter •


9. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 10. On the Select install type(s) window, enter Y for the prompts that correspond to the following option or options; enterN for all others: •

Application Server 11. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation.


168


Y for the prompts that correspond to the 12. On the Select Product Features to Install window, enter N for all others: components from the following list that you want to include in this instance; enter •

Event Management

13. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. \log directory. 15. Press Enter to continue. 16. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 17. On the Validating Configuration for Installation window: a.




ii.


iii. Fix the errors. iv. Restart the userinstall.jar program. 18. When the installation is complete, press Enter. 19. On the Installing Products window: a.




ii.


iii. Fix the errors. iv. Restart the userinstall.jar program. 20. When the installation is complete, press Enter. 21. On the Installing Database Utils window: a.


b.



ii.


iii. Fix the errors. iv. Restart the userinstall.jar program.


169


Install.cfg: 22. After a message states that the installation program is persisting a.


b.



ii.


iii. Fix the errors. iv. Restart the userinstall.jar program. 23. After a message states that the installation is complete: a.

If no errors are reported, press Enter. The installation completes. Note: An exit status of 0 indicates a successful installation.



ii.


iii. Fix the errors. iv. Restart the userinstall.jar program. 24. Log out of the instance. IMPORTANT: If you do not log out of the instance, your installation will not perform as expected.

Configure the registry 1. If you did not log out at the end of the last procedure, then log out of the instance. 2. Log in as the UNIX user to the instance. The UNIX user prompt is displayed. Note: Use the same UNIX user's login name and password that you created earlier in the installation. 3. Change to the database directory with the following command from the $ prompt: cd dtbs/database 4. Run the registry program with the following command from the $ prompt: java -jar ./mocareg.jar Note: The registry program automatically loads the registry tasks. It can also be run again to make updates instead of manually editing theMOCA_REGISTRY file. 5. On the Modify Service Configuration window, enter information into the following fields: •

Host name: Name of the server that is hosting the instance.

•

Service URL: The value is defaulted tohttp://:/service.



170


7. On the Modify Java Configuration window, enter information into the following fields: •

•

64-bit Java path (vm): Location of the 64-bit JVM. 64-bit Java arguments (vmargs): Arguments to use when starting the 64-bit JVM. The minimum value must be-server -Xmx4096m -XX:MaxPermSize=192m .

8. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 9. On the Modify Database Connection Configuration window, enter information into the following fields: •

Choose database to use: Database software that is used to store data for this instance. Enter one of the following numbers:

•

•

•

1: Oracle 12

•

2: SQL Server 2014

•

3: None; a database is not needed for this instance. Continue with the next step.

JDBC connection string: Java Database Connectivity connection string for accessing the database. The installation program window displays examples of the URL that you should enter. For more information on the URL format, see the Oracle or SQL Server database documentation. Database User: Database user's login: Note: If you do not have the database login information, contact the database administrator.

•

•

If you are using database user authentication, enter the database user's login.

•




•


Note: The password is redisplayed as encrypted text instead of cleartext. 10. If you are using an Oracle database, on the Customize Database window, indicate whether you want to customize the user's tablespace definition file. Enter one of the following options: •

To leave the default tablespaces unchanged, enter1 (Use standard settings).

•

2 (Manually customize To view and customize the user's tablespace definition file, enter usrtbldef.h). Note: Option 2 lets you edit the usrtbldef.h file. During the installation process, the file opens in text format so that you can make changes. After you make the changes and save the file, the installation process proceeds.

•

To use the default database user's tablespace for all tables, enter 3 (Use dbuser's default tablespace for all tables). IMPORTANT: Option 3 is the default, recommended option. Note: Option 3 is for environments where database performance is not an issue, such as development and demonstration environments. No tablespaces need to be manually created, since tables are automatically created in the default tablespace for the database user.


171


11. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 12. On the Modify Reporting Configuration window, enter information into the following field: Reporting url (if any): Leave blank. 13. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 14. On the Modify Event Management Configuration window, enter information into the following fields: •

Event Management url (if any): Leave blank (since you are installing Event Management in

•

this instance). Event Management SMTP: IP address or network name for the Event Management e-mail server. IMPORTANT: This server is the Simple Mail Transfer Protocol (SMTP) server that Event Management will use. The information is required to receive alerts from Event Management.

15. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 16. On the Modify Portal Server Configuration window, enter information into the following fields: IMPORTANT: The Portal Server url field is required if you are installing Warehouse Management, Reporting, or Event Management in the instance. Otherwise, leave the field blank. •

•

Portal Server url (if any): URL for the separate portal server instance. The required format for the URL is http://:/service. Portal Server dir (if any): If your configuration includes customized web pages (forms), then enter the path information for the portal server directory. The directory information is needed to allow customizations to compile and deploy to the portal server.

17. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 18. Several windows are displayed displaying the results of the registry configuration process. Press Enter to continue on each window.

Upgrade the distributed data 1. Change to the database directory with the following command from the $ prompt: cd dtbs/database 2. Verify the user name, password, and database tablespaces are accurate with the following command from the $ prompt:java -jar ./dbcheck.jar Note: If errors are reported, contact your database administrator before continuing with this installation. 3. Execute the database upgrade script with the following command from the $ prompt: java -jar ./dbupgrade.jar Note: If any errors or warnings occur, information about them will be displayed. 4. When a message states that the upgrade was completed successfully, perform the initial java -jar ./postdbupgrade.jar configuration with the following command from the $ prompt: 5. Exit the session.


172


Upgrade the Integrator data Upgrading the Integrator data is a manual process instead of an automated process to give you more control over what gets upgraded and when. IMPORTANT: The Integrator upgrade is required if you want to use the new functionality in this release; however, upgrading the data with the following procedure may affect customizations. If you are not certain that your customizations were created in the recommended format, then be sure to make a backup of your Integrator data before you proceed with this upgrade. If you choose not to upgrade the Integrator data, you may need to disable new triggers to avoid errors when using the application. 1. Change to the instance's Integrator directory with the following command from the $ prompt: cd //DCS/db/data/integrator 2. Upgrade each transaction, with the following command from the $ prompt: slUpgrade -f .slexp -v 3. When you are asked if you want to proceed, enterYes, and then press Enter. 4. When you are asked if you absolutely want to proceed, enterYes, and then press Enter.

Unmount the DVD 1. Log in as a root user to the server. umount /mnt/dvdrom 2. Unmount the DVD with the following command from the # prompt:

Start the service Before you can access the instance of the product from a client workstation, the service must be started. 1. Log in as the UNIX user to the instance. rp start 2. Start the service with the following command from the $ prompt:

What to do next 1. To upgrade another instance on a UNIX platform, return to Upgrade an instance on UNIX (on page 168). 2. To upgrade a portal server instance on a UNIX platform, continue with Upgrade the portal server software on a UNIX server (on page174). 3. If you have upgraded all of the necessary server software, continue with Upgrade or add the JDA SCE client software (on page 177).


173


Upgrade the portal server software on a UNIX server Complete the following procedures to upgrade an instance of the portal server software.

Shut down the instance 1. Log in as the portal server UNIX user to the instance to upgrade. cd bin 2. Access the bin directory with the following command from the $ prompt: refs-server stop 3. Shut down the instance with the following command from the $ prompt:

Select the products to upgrade 1. Log in as the portal server UNIX user to the instance. Note: For upgrades, use the portal server UNIX user's login name and password that you created when you initially installed the instance or upgraded it using the UserInstall script. 2. Insert the JDA UNIX DVD into the CD/DVD drive. 3. Access the directory in which the installer program resides with the following command: $ cd /mnt/dvdrom/rpweb java -jar install_rpweb.jar 4. Run the installer program with the following command: $ 5. On the Portal Server Installation Information window, enter the portal server installation directory. 6. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 7. On the Portal Server Application window, enterY for the prompts that correspond to the product or products from the following list; enter N for all others: •

Portal Server

•

Event Management

8. When a message asks if the information is okay, enterY; otherwise, enterN, and then make corrections before continuing with the installation. 9. On the Server Information window, enter information into the following fields: •

Server Port: Port number on which the portal server will run. The portal server is a serverside web server that provides common web server functionality, such as session management, security, single sign on authentication, internationalization and localization, and language management. The default port number is 8060.

•

Stash URL: Full URL to the Stash server. The Stash server stores the client-side library that provides common components, such as calendars and other controls. The required format for the URL is http://:/stash.

•


•

Base Locale: Identifier for the primary locale. The locale ID, which defaults to United States English, controls the cultural features, such as language, calendar, and date and time formats. The client and server use locale ID to configure your user-interface to meet your language requirements.


174


Enter. 10. If the information is okay and you are finished, press 11. On the Connection Information window, for EMS, enter information into the following fields: •


•


•

Application Name: Enter ems.

•


Enter. 12. If the information is okay and you are finished, press 13. For MCS, enter information into the following fields: •


•


•

Application Name: Enter mcs.

•


Enter. 14. If the information is okay and you are finished, press 15. On the Authentication Information window, perform one of the following tasks: •

If you want a JDA SCE server to supply the infrastructure for authentication and authorization, enter information into the following fields: •

•

•

Authentication Type: Enter Native. Authentication Site Name: Name of the instance of record for all authentication requests.

If you want an external entity to provide authentication, enter information into the following fields: •

Authentication Type: Enter Reverse Proxy.

•

Proxy Header: Header that will be used to find the user ID. Note: The contents of the header must contain the user ID of the user that is to be logged in.

•

•

•

SSO Close URL: Destination URL to be opened when portal server is closed.

To use Enterprise Federated Authentication, enter information into the following fields: •

Authentication Type: Enter Federated SSO.

•

Proxy Header: Header that will be used to find the federated token.

•

Federated SSO Validation Service: Token which is understood by the federated service.

•

SSO Close URL: Destination URL to open when portal server is closed.

To authenticate with an LDAP server, in theAuthentication Type field, enter LDAP.



175


17. On the Database Connection Information window, enter information into the following fields: •

Database Type: Database software that is used to store data for this instance. Enter one of the following types: •

oracle

•

sqlserver

•

JDBC Url: Java Database Connectivity connection string for accessing the database. The installation program window displays examples of the URL that you should enter. For more information on the URL format, see the Oracle or SQL Server database documentation.

•

User: Database user's login: •

•

•

•

•

If you are using database user authentication, enter the database user's login. If you are using OS user authentication, leave the field blank.



•


DBO User: Database administrator's login: •

If you are using database user authentication, enter the database administrator's login.

•


DBO Password: Database administrator's password: •

If you are using database user authentication, enter the database administrator's password.

•


Enter. 18. If the information is okay and you are finished, press 19. Press Enter. 20. Log out of the instance. IMPORTANT: If you do not log out of the instance, your installation will not perform as expected.

Run the database batch scripts 1. If you did not log out at the end of the last procedure, then log out of the instance. 2. Log in as the UNIX user to the instance. The UNIX user prompt is displayed. 3. Access the bin directory within the rpweb directory with the following command from the $ prompt: cd bin 4. Run the following batch scripts from the $ prompt: •

db

•

db all

5. Verify the portal sever installation by reviewing the db and db all logs within the rpweb/logs directory.


176


Start the service Before you can access the portal server instance from a web browser, the service must be started. 1. Log in as the portal server UNIX user to the instance. cd bin 2. Access the bin directory with the following command from the $ prompt: refs-server start 3. Start the service with the following command from the $ prompt:

What to do next 1. If you have upgraded all of the necessary server software, continue with Upgrade or add the JDA SCE client software (on page 177). 2. To access a portal server instance from a web browser, Start the web client (on page 190).

Upgrade or add the JDA SCE client software You can upgrade or add software to a client workstation using the JDA SCE Client Installation DVD and the following procedures.

When to perform You can upgrade or add products to an existing client software installation in the following scenarios: •

You want to switch from a typical to a full installation or vice versa.

•

You want to keep the existing version on the workstation.

Note: If you do not want to keep the existing version, then you must first uninstall the existing client 199) and Install software. For more information, see Uninstall the JDA SCE client software (on page the JDA SCE client software (on page93).

Start the JDA SCE client installation wizard 1. Log in as an administrator to the workstation on which you want to install the client software. 2. Insert the JDA Windows DVD into the CD/DVD drive. 3. On the desktop, double-click theMy Computer icon, and then double-click the icon for the drive that contains the JDA Windows DVD. 4. Double-click the Client folder, double-click the windows folder, and then double-clicksetup.exe. Yes. The Existing Installed Instances If a security warning asks to run the setup.exe software, click Detected window is displayed.


177


Select the installation mode The Existing Installed Instances Detected window is displayed if client instances are already installed on the PC. This window enables you to indicate whether you are installing a new version of client software, or upgrading or adding client software to an installation that already exists.


178


1. To install a new client instance: a.

Select Install a new instance of this application , and then click Next. The Enter Text window is displayed.

IMPORTANT: The client instance name can contain up to 10 characters with the exception of the following characters: / : * ? " < > | \ - . or spaces. b. In the text field, enter a unique name for the new client instance. This is the name that you see when you display the list of JDA SCE applications on your client workstation. c.

Click Next. The Welcome to the InstallShield Wizard for JDA SCE Client window is displayed.

2. To upgrade or add client software to an existing client instance: a.


b. In the list, select the instance. c.

Click Next. If a message states that another version of the client software is found and asks OK. you to accept the automatic restart of the installation program in an upgrade mode, click The Welcome to the InstallShield Wizard for JDA SCE Client window is displayed.


179


Initiate the installation The welcome window enables you to initiate the client software installation.

Click Next. The License Agreement window is displayed.


180


Accept the license agreement You must accept the license agreement to continue with the installation process. If you do not accept the license agreement, the installation stops.

1. Read the license agreement. 2. To accept the agreement, clickYes. The Choose Configuration File Path window is displayed.


181


Specify the configuration file path If you are performing an advanced installation, you must specify the configuration file path to tell the InstallShield Wizard where to find the .ini files containing the pre-defined license or client configuration installation information.



b.

Select the drive and folder in which the files are located, and then click OK.

2. Click Next. The Setup Type window is displayed.


182


Select the setup type The Setup Type window enables you to select one of the following installation options that defines what files to install, upgrade, or add: •

Typical installation: Only the minimum software components that are required to start the client software are installed. When you use the client software to connect to a server instance for the first time, the server downloads only the files required to access the functionality for which you are authorized. That means, only the files that you use are stored on your workstation. Note: If you select theTypical installation option, users with restricted access cannot access the files.

•


Note: It is not necessary for the setup type to be the same type as the previously installed client instance; however, if you are switching from aFull to a Typical installation, the application files Full to Typical, if already installed on your workstation remain. To change the installation type from you do not want all of the application files on your workstation, you must uninstall the client software and then perform a typical installation. For more information, see Uninstall the JDA SCE client software (on page 199) and Install the JDA SCE client software (on page93).


To install the minimum software components that are required to start the client software, select Typical.

•

To install all of the software components, select Full.

2. Click Next. The Product and Destination Selection window is displayed.


183


Select the product and destination for client software The Product and Destination Selection window enables you to select the client software that you want to install, upgrade, or add, as well as specify the destination location for that software. You can install the following client software: Note: If you are completing a full installation as opposed to a typical installation, additional client software is available. •

•

JDA SCE Client w/WinMSQL: Install the JDA SCE client software with WinMSQL on administrative workstations at which users perform setup, configuration, system maintenance, and security setup (configuration of roles and users and assignment of menu options). When you install the JDA SCE client software with WinMSQL, users can run MOCA commands to directly access the database regardless of any authorization rights. TheJDA Client w/WinMSQLoption is recommended for workstations that are used only by system administrators. JDA SCE Client w/o WinMSQL: Install the JDA SCE client software without WinMSQL on enduser workstations where users perform their daily tasks. When you install the JDA SCE client JDA software without WinMSQL, users are prevented from accessing the database directly. The Client w/o WinMSQL option is recommended for end-user workstations. IMPORTANT: If you are upgrading or adding client software, theJDA Client w/o WinMSQL option does not remove WinMSQL. If you no longer want WinMSQL on the workstation, then you must first uninstall the existing client software. For more information, see Uninstall the JDA SCE client software (on page199) and Install the JDA SCE client software (on page93).

•

Activity Agent: Install the Activity Agent software if any of the following conditions apply: •

You are installing the JDA SCE client software to work with Warehouse Labor Management.

•

You are the only user using the workstation.

•

You want to see your performance information throughout the day.


184


1. Select the client software that you want to install, upgrade, or add. Note: As you select, the required and available disk space is calculated and displayed. 2. For an initial installation, if the available disk space is not sufficient, look for available disk space: a.


b.


c.


3. For an initial installation, to change the default destination folder, browse for another location: a.


b. In the Directories list, select the folder into which you want to install the client software. c. When the full path to the folder is displayed in the Path field, click OK. Note: To ease the upgrade process, use the default destination location. 4. Click Next. The Product Component List window is displayed.

Verify the product component list The Product Component List window enables you to verify that you have selected all of the components that you want to install, upgrade, or add. Before you continue with the installation process, you must verify the information on this window. The client software listed on this window should match the selections that you made earlier.

1. Review the information. 2. If the information is accurate, click Next; otherwise, click Back to make corrections before continuing with the installation. The Choose Configuration file to use window is displayed.


185


Specify the configuration file The Choose Configuration file to use window enables you to provide the configuration .xml file to use when you are performing an advanced installation.


Click Browse. The Choose file to use window is displayed.

b.

Navigate to the drive and folder in which the .xml file is located, select it, and then click Open.

2. Click Next. The Client Connections window is displayed.


186


Provide the client connections to server instances The Client Connections window enables you to provide new or modify existing server connection information. You can define client connections for all of the JDA SCE applications and instances with which you will work from this client installation. Client connections include a name and the server instance connection URL.

1. Enter the connection information: Note: To enter connection information later, leave the fields blank. IMPORTANT: The client instance name can contain up to 10 characters with the exception of the following characters: / : * ? " < > | \ - . or spaces. a. In the Name column, enter a name for the connection. The name can be the same as the name of the server instance to which you want to connect (for example, Production, Training, DevServer, or ModelSvr); however, the name does not need to match (for example, Live1, Live2, or Train0673). Create a name that helps you understand the server instance to which your client instance is connecting. b.

In the Connection Url column, enter the URL that was created for the server instance during the server installation. Note: The URL consists of the server name and port number for the server instance and a constant value (service). Example:http://:/service

c.

If you will be using the client software to work with multiple JDA SCE applications or multiple instances of one JDA SCE application, continue to enter Name and Connection Url values until all of the client connections are defined. IMPORTANT: If users at this workstation work with multiple instances of a JDA SCE application or with multiple applications, do not create a default connection.

d.

To create a default connection that defines the server instance to which you connect each time you start the JDA SCE client software, in theDefault Server column select the check box.

2. Click OK. The Start Copying Files window is displayed.


187


3. If a message states that the required version of .NET is not installed, install it: a.

Click Cancel. The installation program is closed.

b.

Manually install the required version of .NET. Note: You can find thedotnetfx35.exe installation executable file in the 3rdParty folder on the JDA installation DVD.

c.


Start the file copy process The Start Copying Files window enables you to verify the installation information that you provided and start the installation process. The information listed (for example, client software and connection specifics) should match the selections that you made earlier.

1. Review the information. 2. If the information is not accurate, clickBack and make the necessary changes. 3. To start copying the files, click Next. The Setup Status window displays the progress of the installation. Note: To cancel the installation after file copying begins, click Cancel. 4. When a message asks to add shortcuts to the desktop, to install the desktop icons for accessing the applications, click Yes. If you click No, you must use theStart menu on your workstation to access the applications. The InstallShield Wizard Complete window is displayed.


188


Finish The InstallShield Wizard Complete window indicates that the client software installation successfully completed.

1. If a message states that the workstation must be restarted because a shared application core component was installed, perform one of the following tasks: •

To restart the workstation now, selectYes, I want to restart my computer now.

•

To restart the workstation later, selectNo, I will restart my computer later .

IMPORTANT: If restarting the workstation is required, the installation will not work correctly until it is performed. 2. Click Finish. 190). 3. Start the JDA SCE client and connect to a JDA SCE application (on page


189

After you install or upgrade

Chapter 6. After you install or upgrade This chapter explains how to install the client software on a workstation and verify your server installation, and it identifies additional post-installation procedures that ensure your installation performs as expected. IMPORTANT: After installing a new or upgrading an existing instance, you must install required hotfixes, if any. See Required hotfixes (on page17).

Start the web client Several JDA SCE modules, such as configuration, packing, administration, and event management, are accessed using the web client. 1. Log in to the workstation from which you want to access the web client. 2. Start the web browser. 3. In the address box, enterhttp://:, where and are the server and port on which you installed the portal server instance. The login page is displayed. 4. Enter your user name and password, and then clickLog In. Notes: •

SUPER as the default For a new installation in which users have not yet been configured, enter user name and password. When the working environment is displayed, immediately access the authorization functionality and create a new user with administrative privileges. For more information, click

•

to access the online help, and then search for authorization.

For security reasons, after creating your own administrative users, you should delete the SUPER user configuration because it provides users with full privileges to configure the application.

Start the JDA SCE client and connect to a JDA SCE application You use this procedure to verify that your installation was successful. You can also use this procedure to upgrade the client software. IMPORTANT: To connect to a 9.1.0.0 server instance from a client version 2009.2 or earlier, you must have updated the 9.1.0.0 registry file to enable communication. For instructions, see Pre29). installation or upgrade tasks for the client software (on page 1. Log in to the workstation on which the JDA SCE client software is installed. 2. Perform one of the following tasks:

•

If the shortcut icon was installed, from the desktop, double-click

•

If the shortcut icon was not installed, from theStart menu, display the list of programs, and then select JDA Supply Chain Execution > Client - > JDA SCE Client.


.

190


3. If the JDA SCE login window is displayed, perform one of the following tasks: •

If a server connection was previously defined, from theService drop-down list, select the connection name or service URL for the application server instance to which you want to connect, and click Go.

•

If a server connection was not previously defined, in the Service field, enter the service URL for the application server instance to which you want to connect, and click Go.

4. If a message states that the connection to the server failed, verify that the service URL is correct. If it is, contact a system administrator to verify that the service is started. If it is not correct, enter the correct service URL, and click Go. Notes: •

Depending on the JDA SCE application to which you are connecting, your facility, and your user configuration, not all of the following fields may be available: •

Username

•

Password

•

Warehouse

•

SUPER as the For a new installation in which users have not yet been configured, enter default user name and password. When the JDA SCE application is displayed, immediately access Authorization Maintenance and create a new user with administrative privileges.

•

For security reasons, after creating your own administrative users, you should remove the SUPER user configuration because this login provides users with full privileges to configure the application.

5. In the Username field, enter your user name, and then pressTab.


191


6. In the Password field, enter your password. 7. If you are connected to a Warehouse Management or Warehouse Labor Management server Warehouse drop-down list, select the instance configured to have multiple warehouses, from the warehouse for which you will be performing work. Note: If you are assigned to only one warehouse, then the identifier for that warehouse is displayed and you cannot select a different warehouse. 8. Click Sign in. 9. If a message states that updated client core components, which enable the applications to function, are available on the server, perform one of the following tasks: IMPORTANT:

•

•

If you have administrator or standard access, you must select the option to download the updated files. If you do not select this option, your applications may not function properly. This option is functional only for users with administrator or standard access to the client workstation.

•

Select the option to use the existing files if you are a user with restricted access to the client workstation. If you have restricted access and you want to access the updated files, contact your system administrator (or other authorized user).

To download the updated files, click Download, and then perform the following tasks: a. When the Welcome to the InstallShield Wizard for JDA Core window is displayed, click Next, and follow the prompts. b. If a window asks you for the connection information again, select the connection name or enter the service URL, and then click OK.

•

To use the existing files, click Use Current.

10. If a message states updated client framework components (for example, toolbars) are available on the server, perform one of the following tasks: IMPORTANT: •

If you have administrator or standard access, you must select the option to download the updated files. If you do not select this option, your applications may not function properly. This option is functional only for users with administrator or standard access to the client workstation.

•

Select the option to use the existing files if you are a user with restricted access to the client workstation. If you have restricted access and you want to access the updated files, contact your system administrator (or other authorized user).

•

To download the updated files, click Download.

•

To use the existing files, or you selected Use Current when prompted to download core components, click Use Current.


192


11. If a message states that the device (the workstation from which you are starting the JDA SCE client and application) does not have a device code defined, perform one of the following tasks: Note: Only the undefined device code message is displayed if you are connecting to an instance in which Warehouse Management is installed.

•

To define a device now, click Yes. The Device Code Selection window is displayed. Perform the following tasks: IMPORTANT: Typically the device code is the workstation name. However, if the workstation name is longer than 10 characters, you must truncate the device code to 10 or fewer characters. If you use a device code that is longer than 10 characters, your application will not perform as expected. a. In the Device Code field, enter or look up a device code for this workstation. b. Click Ok. c. If a message states that the device code for the workstation is not defined in Device Maintenance, click OK, and then add or modify the device information for the workstation. For information on maintaining devices, see the Warehouse Management online help.

•

To define a device later, click No. The JDA SCE client starts. You must define the device later in Device Maintenance. For information on maintaining devices, see the Warehouse Management online help.


193


Add a client connection You can add a client connection in the following scenarios: •

You already have the JDA SCE client installed on a workstation.

•

You want to connect to another JDA SCE server instance.

•

You want to configure a named connection to the server instance to make it easier for users to connect.

1. Log in to the workstation on which the JDA SCE client is installed. JDA Supply Chain Execution 2. From the Start menu, display the list of programs, and then select > Client - > Configuration. The Client Configuration window is displayed.

3. On the Machine tab, click New.


194


4. In the Server field, enter the new connection name. Note: The name can be the same name as the server instance to which you want to connect. However, you can use any name that will help you (or other client users) understand to which server instance you are connecting with this connection. 5. In the Service field, enter the service URL for the server instance to which you want to connect. Note: If you are configuring a connection to a server instance that is version 2009.2 or earlier, then instead of entering the service URL, enter :. For example, HOST:5500.

IMPORTANT: If you frequently connect to more than one instance, do not make this server the default server. When you access client software, and you have a default server connection specified, then the client connects to that server automatically. 6. To automatically connect to this server instance whenever you launch the client software, select the Default Server check box. 7. Click Save, and then click Exit. 190). 8. Start the JDA SCE client and connect to a JDA SCE application (on page


195


Enable remote calls from an earlier version You must complete the following procedure if you installed or upgraded an instance to 9.1.0.0, and a JDA SCE application that is version 2009.2 or earlier is to communicate with it. For example, if you install or upgrade to Event Management 9.1.0.0, and that Event Management instance communicates with Warehouse Management 2009.2, then you must complete the following procedure to open a port that enables communication (remote calls) from Warehouse Management to Event Management. 1. Log in as an administrator to the server on which the 9.1.0.0 instance is installed. 2. Navigate to the LES\data folder for the instance. Example: :\RedPrairie\\LES\data 3. Open the MOCA registry file in Notepad. 4. Under [SERVER], add the following settings and values where the format is=: •

CLASSIC-PORT: Port number of the classic MOCA server to which the earlier version connects. If not present, the classic MOCA listener is not started.

•

CLASSIC-POOL-SIZE: Number of threads (defaults to 20) to be used for executing incoming socket requests on the MOCA classic protocol listener. This value is similar to the classic MOCA max-servers registry key.

•

CLASSIC-ENCODING: Encoding to use to communicate with classic servers (defaults to UTF-8). This value must be a valid Java encoding, and must be the same as US-ASCII in the lower 7 bits. UTF-8 and the typical 8-bit ISO-8859-x encodings and charsets all qualify. This value should be set to the value of the charset column published from the "get encryption information command" when executed against the classic server through MSQL.

Example:

[ SERVER] RMI - PORT=1099 PORT=4500 PROD= DI RS=%LESDI R%; %LESWEBDIR%; %SLOTDIR%; %SMDI R%; %CTDIR%; %LMDI R%; %DCSDIR%; %MTFDI R%; %MOCA RPTDI R%; %SALDI R%; %MCSDI R%; %SLDI R%; %MOCADI R% URL=ht t p: / / PRODSVR: 4500/ ser vi ce MEMORY-FI LE=%LESDI R%\ dat a\ commands. mem CLASSI C- PORT=4800 CLASSI C- POOL- SI ZE=20 CLASSI C- ENCODI NG=I SO8859_5 Note: When the instance is started, if the MOCA registry settings are correct, the log file will include a message similar to the following text: (MocaProtoc) Classic server started on port 4800 (ISO-8859-5). 5. From the File menu, select Save. 6. Close the registry window. 201). 7. Document the connection information in the Record of installation information (on page


196


Validate the integrity of your upgrade You can validate the integrity of your upgrade by comparing an application library version to its corresponding database version. You can do this using Server Command Operations in the JDA SCE client. 1. Start the JDA SCE client and log in to your JDA application. For more information, see Start the 190). JDA SCE client and connect to a JDA SCE application (on page 2. Start Server Command Operations. 3. Generate a list of libraries: a.

In the command field, enter list library version.

b.

Click Execute. A list of libraries, along with the version that is currently installed on your server, is displayed. Locate and then document the version of the MOCA base library; for example, 2009.1.

Note: If you also want to compare DCS, MCS, or SAL, then locate and document the versions for DCSint, MCSbase, or SALbase. 4. Generate the MOCA database version: a.

In the command field, enter [select * from MOCA_DBVERSION].

b.

Click Execute. The version is displayed. Verify that the library version and the database version are the same.

5. If desired, make the same comparison for DCS, MCS, and SAL. Note: In the select command, replace MOCA with DCS, MCS, or SAL.

Post-installation or upgrade Perl location change If you changed the path to Perl after you completed the server software installation on a UNIX server, you must update the instance's.profile file so that it is referencing the appropriate location. IMPORTANT: Perl is referenced by all of the instances on the server. Each instance has its own .profile file. If you change the Perl location, you must change the .profile file of every instance on the server. 1. Log in as the UNIX user to the application server instance. 2. Verify that the .profile file exists in the LESDIR with the following command from the $ prompt: ls -la 3. Open the file to edit with the following command from the $ prompt: vi .profile 4. In the .profile file, update the PATH parameter to specify the path to the current Perl location. 5. Press Shift+ZZ to save, and then close the file.


197


Post-upgrade folder maintenance When you are confident that the upgraded instance is functioning properly, you can remove the old folders. The old folder names contain the packaging version number, and they are displayed in the following format:_. For example, in the following image the JDA SCE application was upgraded from version 2008.1.3 to version 2009.1.0. You can delete the folders that are displayed in the image with a line through them.


198


Uninstall the JDA SCE client software Before installing the client software, you can remove the existing client software from the workstation if the following conditions apply: •

You do not want to keep multiple versions of the client software on the workstation.

•

You want to switch from a Full to a Typical installation, and you do not want to keep all of the installed application files on the workstation.

•

You want to remove WinMSQL from the client installation.

IMPORTANT: When you uninstall a client instance that contains multiple versions, all versions are uninstalled. When you uninstall the client software, one or more messages may ask if you want to delete files and folders that have been downloaded from the server. You should enable the installer to delete the files and the folders unless you have added files to theProgram Files\RedPrairiefolder that you want to preserve. 1. Access the Windows Control Panel, and then select Uninstall a program. The Uninstall or change a program window is displayed. 2. Perform one of the following tasks: •

If you are uninstalling a client version 2005.1 or earlier, perform the following tasks: a. In the list of installed programs, select RedPrairie, and then click Uninstall. The Maintenance Mode window is displayed. Note: You may see RedPrairie Installation Maintenance Engineinstead of RedPrairie. b. Select RedPrairie Client: TYPICAL, and then click Next. The Maintain Installed Product window is displayed. Note: If you performed a Full installation, the Maintenance Mode window will display RedPrairie Client: FULL. c. Click Next.

•

If you are uninstalling a client version 2005.2 or later, in the list of installed programs, select JDA SCE Client - or RedPrairie Client - (some versions may show RedPrairie Client or RedPrairie DigitaLogistix Client), and then clickUninstall.

A message is displayed to remove the selected application and all of its features. 3. Click OK. C:\Program 4. If a message is displayed to remove files that are not managed by the install in Files\, and if you have added files to the Program Files\RedPrairiefolder that you want to preserve, click No; otherwise, click Yes. 5. If one or more messages are displayed to delete C:\Program Files\RedPrairie\\ and all of its contents, and if you have added files to the Program Files\RedPrairie folder that you want to preserve, clickNo; otherwise, clickYes.


199


6. When the InstallShield Wizard Complete window is displayed, click Finish.


200

Record of installation information

Chapter 7. Record of installation information This record of installation information provides you with a list of items for which you need to record information that is specific to your JDA SCE application installation. Record this information as you proceed through the pre-installation and installation procedures. This information is required for a successful installation, and it will serve as a permanent record for each installed instance.

Installation-specific information Each installed instance of a JDA SCE application requires its own record of installation-specific information. If you are installing multiple instances of a JDA SCE application, copy this list and complete it for each installed instance.

Event Management server software •

Environment (for a UNIX installation) •

Environment name

•

UNIX login

•

UNIX group

•

Working directory

•

Physical directory

•

JDA product instance name

•

Instance URL (http://:/service)

•

User authentication method (database or operating system)

•

Windows User Login (if using OS user authentication in this instance)

•

•

User

•

Domain (if not local)

•

Password


SQL Server version

•


•


•


•

Database name

•


•


•


•

JDBC URL


201


•


Oracle server name

•


•


•

Oracle SID

•

Oracle port number

•

Oracle user (if using database OS user authentication for a UNIX installation)

•

•

Version number JDBC URL

•

Portal server instance URL and, for web page (form) customizations, directory location

•

IP address or network name for the Event Management SMTP email server

•

Classic port information (must be added to the registry file if a JDA SCE application that is version 2009.2 or earlier connects to this instance) •

Classic port number

•

Classic pool size

Portal server software •

Portal server instance name

•

Setup type

•

•

Installation destination folder, if different from the default Installed features

•

Portal server port number

•

Server connection URLs •

Stash server URL

•

Static server URL

•

Locale ID

•

Authentication type (Native, Reverse Proxy, Federated SSO, or LDAP)

•

Authentication connection name

•

Connection information (for each connection) •

Connection name

•

•

Connection type Application type

•

Connection URL


202


•


SQL Server version

•


•


•


•

Database name

•


•

•

•

Database user password (if using database user authentication) SQL Server port number


Oracle server name

•


•


•

Oracle SID

•

Oracle port number


203

Event Management 9.1.2.0 Installation Guide

Recommend Documents