Você está na página 1de 428

JD Edwards EnterpriseOne

Applications Release 8.12

Installation Guide for Oracle on Microsoft Windows

January 2008

Installation Guide for Oracle on Microsoft Windows Copyright 2008, Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Open Source Disclosure Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation. The following open source software may be used in Oracle's PeopleSoft products and the following disclaimers are provided. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED "AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Table of Contents
1. Understanding JD Edwards EnterpriseOne ........................................................................... 1 Understanding This Guide ................................................................................................ 2 Understanding the Installation Process ................................................................................ 3 Understanding the Deployment Server Installation ........................................................ 4 Understanding the Platform Pack Installation ............................................................... 4 Understanding the Installation Planner ........................................................................ 4 Understanding Installation Workbench ........................................................................ 5 Understanding Data Configuration Workbench ............................................................. 5 Understanding the Workstation Installation .................................................................. 6 Considering Additional Factors .......................................................................................... 7 Accessing Minimum Technical Requirements .............................................................. 7 Using JD Edwards EnterpriseOne Support ................................................................... 7 Understanding Documentation Conventions ................................................................. 7 Documentation Updates ................................................................................... 7 Tips .............................................................................................................. 8 Fonts and Type Styles ...................................................................................... 8 Hyperlinks ..................................................................................................... 8 Working With the Customer Checklist ................................................................................ 9 Environments Overview ................................................................................................. 10 Understanding Environments ................................................................................... 10 Planner Environment (JDEPLAN) ............................................................................ 11 Planner Pathcode .......................................................................................... 11 Planner Database .......................................................................................... 11 Pristine Environment (PS812) ................................................................................. 12 Deployment Environment (DEP812) ......................................................................... 12 Development Environment (DV812) ......................................................................... 12 Prototype Environment (PY812) .............................................................................. 12 Production Environment (PD812) ............................................................................ 12 Additional Considerations ....................................................................................... 13 Push Installation ........................................................................................... 13 Cluster Software Options ................................................................................ 13 Web-Based Options ....................................................................................... 13 Release History .................................................................................................... 13 Language Process Overview ............................................................................................ 14 Language Architecture ........................................................................................... 14 Base Language ............................................................................................. 14 Alternate Language Components ...................................................................... 14 Language Preference Codes ............................................................................ 15 Database Character Set and Code Page Considerations ................................................. 15 Unicode ...................................................................................................... 15 Code Page Settings ........................................................................................ 16 Oracle Code Page Settings ...................................................................... 16 Workstations and Deployment Server ....................................................... 16 National Language Support ..................................................................................... 17 Single-Byte and Double-Byte Considerations ..................................................... 17 Font Considerations ....................................................................................... 18 User Display Preferences ................................................................................ 18 2. Before You Begin the Installation ....................................................................................... 19 Verifying Software and Hardware Requirements ................................................................. 19 Verifying the Disk Space Requirements ............................................................................. 20

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

Installation Guide for Oracle on Microsoft Windows

3. Working with the Deployment Server ................................................................................. 21 Installing the Deployment Server ..................................................................................... 22 Downloading and Installing the Latest Software .................................................................. 31 Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server ........................................................................................................................... 31 Installing JDBC Drivers for SQL Server 2000 ............................................................ 32 Installing the Latest Planner Update .......................................................................... 33 Troubleshooting Deployment Server Installation ................................................................. 36 4. Working with the Platform Pack ........................................................................................ 37 Understanding the Platform Pack ..................................................................................... 38 Configuring the Enterprise Server Prior to Installing the Platform Pack ................................... 39 Setting Up NLS_LANG Parameter for Oracle ............................................................ 39 Enabling Remote Connections for Oracle .................................................................. 40 Setting Up and Verifying the Hosts File ..................................................................... 42 Special Consideration for Oracle 11g on Windows .............................................................. 43 Verifying Code Page Settings for Oracle ............................................................................ 43 Understanding the Platform Pack Installation ..................................................................... 45 Installing the Platform Pack ............................................................................................ 46 Running the JD Edwards EnterpriseOne Platform Pack Installer ..................................... 47 Custom Mode Feature Selection ............................................................................... 50 Database Options .................................................................................................. 52 Oracle - Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) or Database only ................................................................................................... 53 Oracle - Enterprise Server Only (Different Machine from Database Server) ...................... 55 Review the Legacy Database Warning Panel .............................................................. 56 Concurrent Users .................................................................................................. 57 Review the Summary Information Panel and Complete the Installation ............................ 59 Verifying the Platform Pack Log File ........................................................................ 59 Troubleshooting Platform Pack Installation ........................................................................ 60 Installer Will Not Start or Complete (Invalid vpd.properties) ......................................... 61 Business Data and Control Tables Already Exist ......................................................... 62 Business Data and Control Tables Do Not Exist .......................................................... 63 Business Data or Control Tables Tablespaces Reported As Existing When They Do Not Exist ........................................................................................................................... 64 System Database Not Detected ................................................................................ 64 Foundation Files Do Not Exist ................................................................................. 66 Rerunning the JD Edwards EnterpriseOne Platform Pack Installer .......................................... 67 Enterprise Server .................................................................................................. 67 Database Server .................................................................................................... 67 Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server ......... 68 Working with Database Security ...................................................................................... 69 5. Working with Installation Planner ..................................................................................... 71 Understanding Installation Planner ................................................................................... 72 Language Information ............................................................................................ 73 Location Information ............................................................................................. 73 Deployment Server Information ............................................................................... 73 Enterprise Server Information .................................................................................. 73 JD Edwards EnterpriseOne HTML Web Server Information .......................................... 74 Data Source Information ......................................................................................... 74 Environment Information ........................................................................................ 75 Working with JD Edwards EnterpriseOne Software Requirements .......................................... 75 Reviewing Installation Planner Processing Options .............................................................. 76 Assumptions About Reviewing Installation Planner Processing Options .......................... 76 Accessing Processing Options ................................................................................. 76 Choosing Processing Option Values ......................................................................... 77 vi GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Installation Guide for Oracle on Microsoft Windows

Specifying the Prompt Mode ........................................................................... 78 Specifying the Process Mode ........................................................................... 79 Specifying the Default Mode ........................................................................... 80 Verifying Status Change Values Have Not Changed ............................................ 82 Specifying Plan Completion Processes .............................................................. 83 Specifying Replication Options ........................................................................ 85 Specifying Remote Location Package Push Options ............................................. 87 Working with a Typical Installation Plan ........................................................................... 89 Assumptions About Defining a Typical Installation Plan .............................................. 89 Starting Installation Planner .................................................................................... 90 Entering a Plan Description ..................................................................................... 91 Entering Location Information ................................................................................. 92 Entering Deployment Server Information ................................................................... 93 Entering Enterprise Server Information ..................................................................... 95 Entering HTML Web Server Information .................................................................. 98 Selecting Default Environments ............................................................................. 102 Finalizing the Installation Plan ............................................................................... 103 Concluding the Planner Validation Report ............................................................... 104 Creating a Custom Installation Plan ................................................................................ 105 Understanding a Custom Installation Plan ................................................................ 106 Starting Installation Planner .................................................................................. 107 Entering a Plan Description ................................................................................... 108 Entering Location Information ............................................................................... 110 Entering Deployment Server Information ................................................................. 111 Entering Enterprise Server Information ................................................................... 113 Enter Data Source Information for Server Map ......................................................... 115 Entering HTML Web Server Information ................................................................ 116 Entering Data Server Information ........................................................................... 121 Entering Shared Data Source Information ................................................................ 123 Specifying (Custom or Default) Shared Data Source Setup Information ................. 123 Verifying the Data Source for Data Dictionary .......................................... 124 Verifying the Object Librarian Data Source .............................................. 125 Verifying the System Data Source .......................................................... 126 Working with Environment Setup .......................................................................... 127 Understanding Environment Setup ................................................................. 127 Setting Up Environments .............................................................................. 128 Adding a Custom Environment .............................................................. 129 Selecting an Environment ..................................................................... 130 Specifying Environment Data Load Parameters ......................................... 131 Selecting Languages ............................................................................ 132 Working with Environment Data Sources ........................................................ 133 Understanding Environment Data Sources ............................................... 133 Selecting an Environment Data Source Setup Option ................................. 133 Setting Up the Data Source for Business Data ........................................... 134 Setting Up the Data Source for Central Objects ......................................... 135 Setting Up the Data Source for Control Tables .......................................... 137 Verifying the Data Dictionary Data Source .............................................. 138 Verifying the Data Source for Versions ................................................... 139 Adding a Remote Location ................................................................................... 140 Finalizing the Installation Plan ............................................................................... 141 Concluding the Validation Planner Report ............................................................... 142 Deleting Machines from an Installation Plan ..................................................................... 143 6. Working With Installation Workbench ............................................................................. Understanding Workbench Components .......................................................................... Verifying the Network Share on the Deployment Server ............................................. Loading Data (Demo Data and Production Data) ....................................................... Creating the Job Queue ........................................................................................ 145 146 147 148 152

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

vii

Installation Guide for Oracle on Microsoft Windows

Working with Unattended Workbench Mode .................................................................... Selecting Attended or Unattended Workbench Mode ................................................. Setting a Task Break in Unattended Workbench Mode ............................................... Starting Installation Workbench ..................................................................................... Working With Initial Tasks Workbench ........................................................................... Changing the Status of Initial Tasks Workbench ....................................................... Configuring Your Locations .......................................................................................... Configuring Your Data Sources ..................................................................................... Configuring Your Environments .................................................................................... Using Machine Workbench ........................................................................................... Using the Package Workbench ...................................................................................... Using Remote Location Workbench ............................................................................... Configuring Remote Locations .............................................................................. Finishing Installation Workbench ................................................................................... Updating Oracle Database Statistics ................................................................................ 7. Working With Data Configuration Workbench ................................................................. Understanding Data Configuration Workbench ................................................................. Data Configuration Process ................................................................................... Components and Tables that are Updated by Data Configuration Workbench ................. Adding a Data Configuration Plan .................................................................................. Running a Data Configuration Plan ................................................................................ Troubleshooting Data Configuration Workbench Installation ............................................... 8. Working With the Enterprise Server ................................................................................ Verifying the Release 8.12 Enterprise Server Installation Using PORTTEST .......................... Starting Network Services on the Enterprise Server ........................................................... Stopping Network Services on the Enterprise Server .......................................................... Working with OCM Generation ..................................................................................... Understanding OCM Mappings ............................................................................. Understanding Data Source Setup .......................................................................... Understanding OCM Creation ............................................................................... Understanding Database Data Sources ............................................................ Understanding Logic Data Sources ................................................................. Understanding OCM Customization ....................................................................... Understanding Data Classes .......................................................................... Creating a New Data Class ............................................................................ Modifying the Data Source Template .............................................................. Associating Table Data Classes ...................................................................... Setting Up a Printer on the Enterprise Server .................................................................... Adding a New Printer .......................................................................................... Defining a Default Printer ..................................................................................... 9. Installing the Workstations for Developers and System Administrators ................................ Understanding Workstation Installation ........................................................................... Preparing for Workstation Installation ............................................................................. Understanding Workstation Installation ........................................................................... Understanding Workstation Installation Methods ...................................................... Working with Interactive Mode ..................................................................... Creating a Desktop Shortcut .................................................................. Using a Shared Drive ........................................................................... Working with Silent Mode ............................................................................ Working with Push Mode ............................................................................. Understanding Third-Party Products ....................................................................... Understanding User Profiles and Languages ..................................................................... Working with the Workstation JDE.INI on the Deployment Server ....................................... Understanding the Workstation JDE.INI on the Deployment Server .............................. Modifying the Workstation JDE.INI on the Deployment Server ................................... viii GA.Rev8 1/7/2008

154 154 154 156 157 157 159 160 161 162 163 164 165 166 166 167 168 168 169 171 172 174 177 177 178 178 179 179 179 180 180 180 180 181 181 181 181 182 182 188 191 191 192 193 193 193 193 194 195 196 196 196 197 197 197

Copyright 2008, Oracle. All rights reserved.

Installation Guide for Oracle on Microsoft Windows

10. Understanding Media Object Queues .............................................................................. 199 Modifying Media Object Queues .................................................................................... 199 Specifying the Help Location ........................................................................................ 200 11. Performing Post Installation Tasks ................................................................................. 203 Understanding Post Installation Tasks ............................................................................. 203 Setting Up Microsoft Windows Security on Release 8.12 Directories .................................... 204 Setting Security on the Files within the Client Directory ............................................. 204 Setting Security on the Pathcode Directory ............................................................... 205 Setting Security on the Database Directory ............................................................... 205 Setting Security on the Data Dictionary Directory ..................................................... 205 Setting Security on the Helps Directory ................................................................... 206 Setting Security on the Media Object Directory ......................................................... 206 Setting Security on the Planner Directory ................................................................. 206 Setting Security on the Print Queue Directory ........................................................... 206 Setting Security on the System Directory ................................................................. 207 Using the Adobe SVG Viewer on Web Clients ................................................................. 208 Understanding Task Word Search Tables ......................................................................... 209 Building Task Word Search Tables ......................................................................... 209 Setting Up Solution Explorer ......................................................................................... 210 Setting Up Solution Explorer HTML Documentation Path .......................................... 210 Setting Up the Home Page for Solution Explorer ....................................................... 210 Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications .......... 212 Adding Vertex Quantum Directory Information to the Microsoft Windows Server Path .... 213 Configuring the Release 8.12 Database Connections for Vertex Quantum Tax Applications 214 Mapping Objects to the Enterprise Server ................................................................ 215 Understanding the Autopilot Scripting Tool ............................................................. 216 Configuring Autopilot for the Oracle Database ................................................. 216 Testing the Vertex Quantum Connection from Release 8.12 ........................................ 221 Enabling CRM Functionality ......................................................................................... 223 Enabling CRM on the CRM Mobile Client ............................................................... 223 Enabling CRM on the Enterprise Server .................................................................. 224 12. Working With Signon Security ...................................................................................... Setting Up Signon Security ........................................................................................... Setting up Security Overrides for Package Build ............................................................... Enabling Server-Side Signon Security ............................................................................. Enabling Client-Side Signon Security ............................................................................. Setting Up JD Edwards EnterpriseOne Single Sign-on ....................................................... 13. Building and Testing Packages ....................................................................................... Understanding Packages ............................................................................................... Installing Application Fixes .......................................................................................... Updating the System Path ............................................................................................. Reviewing Pre-Package Build Issues ............................................................................... Verifying Available Space in DBMS ...................................................................... Verifying Specific UBEs are Mapped Locally .......................................................... Verifying the OCM Mapping ................................................................................. Deleting the BUSOBJ Directories .......................................................................... Verifying the F9631 Table .................................................................................... Verifying the Server-Side Settings .......................................................................... Configuring the Enterprise Server for Simultaneous Builds ......................................... Adding a Security Override for Running Package Build .............................................. Adding a System User for the Central Objects Data Source Owner ....................... Adding an Override for an EnterpriseOne User Running Package Build ................. Reviewing Troubleshooting Tips .................................................................................... 227 228 231 232 232 233 235 235 236 236 238 239 239 240 240 240 241 241 242 242 242 243

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

ix

Installation Guide for Oracle on Microsoft Windows

User Tips ........................................................................................................... Deployment Tips ................................................................................................ Building an Alternate Language Package ......................................................................... Package Build Considerations ............................................................................... Package Deployment Considerations ...................................................................... 14. Installation Utilities ...................................................................................................... Revalidating Software Protection Codes .......................................................................... Revalidating the Deployment Server ....................................................................... Revalidating Workstations .................................................................................... Granting Disk and Registry Access for Microsoft Windows Workstations .............................. Granting Non-Privileged Access to Disk for Microsoft Windows ................................. Granting Access to the Software Installation Directory ............................................... Granting Nonprivileged Access to the Microsoft Windows Registry ............................. 15. Troubleshooting ........................................................................................................... Using the PORTTEST Checklist .................................................................................... Resolving Data Errors .................................................................................................. Planner Update Special Instructions ................................................................................ Special Instructions for All ................................................................................... Special Instructions for OCX Registration ................................................................ Orphan Users ............................................................................................................. 16. Creating a Remote Installation Plan ............................................................................... Understanding Remote Installation Plans ......................................................................... Starting Installation Planner .......................................................................................... Entering Information in Installation Planner ..................................................................... Entering Plan Location Information ................................................................................ Specifying a Deployment Server .................................................................................... Entering Deployment Server Information ................................................................. Concluding Deployment Server Setup ..................................................................... Specifying an Enterprise Server ..................................................................................... Entering Enterprise Server Information ................................................................... Entering Enterprise Server Data Source Information .................................................. Specifying Custom or Default Data Source Information ...................................... Entering the Oracle Connect String ................................................................. Verifying Custom Server Map Source Information ............................................ Adding Another Enterprise Server .................................................................. Entering HTML Web Server Information ........................................................................ Entering Data Server Information ................................................................................... Entering Shared Data Source Information ........................................................................ Specifying (Custom or Default) Shared Data Source Setup Information ......................... Verifying the Data Dictionary Data Source .............................................................. Verifying the Object Librarian Data Source .............................................................. Verifying the System Data Source .......................................................................... Setting Up Environments .............................................................................................. Environments ..................................................................................................... Adding a Custom Environment .............................................................................. Selecting an Environment ..................................................................................... Replicating Information to Remote Locations ................................................................... Setting Up Data Sources for Environment ........................................................................ Beginning the Data Source Setup for Environment .................................................... Setting up the Data Source for Business Data ........................................................... Verifying the Data Source for Control Tables ........................................................... Select Another Environment .................................................................................. Concluding the Remote Installation Plan Setup ................................................................. Finalizing the Installation Plan ....................................................................................... Concluding the Validation Planner Report ....................................................................... x GA.Rev8 1/7/2008

243 244 246 246 246 249 249 249 250 250 251 251 252 253 253 256 256 256 256 257 259 260 261 262 263 264 264 266 266 266 268 268 268 269 270 271 276 278 278 278 279 280 281 281 282 283 283 286 286 286 287 288 290 291 291

Copyright 2008, Oracle. All rights reserved.

Installation Guide for Oracle on Microsoft Windows

17. Adding a Server to an Existing Configuration .................................................................. Assumptions about Adding a Server to an Existing Installation Plan ..................................... Starting Installation Planner .......................................................................................... Entering a Plan Description ........................................................................................... Entering a Plan Location .............................................................................................. Selecting Additional Server Types .................................................................................. Entering Deployment Server Information ......................................................................... Specifying an Enterprise Server ..................................................................................... Entering Enterprise Server Information ................................................................... Entering Enterprise Server Data Source Information .................................................. Specifying Custom or Default Data Source Information ...................................... Entering the Oracle Connect String ................................................................. Verifying Custom Server Map Data Source Information ..................................... Adding another Enterprise Server ................................................................... Entering HTML Web Server Information ........................................................................ Entering Data Server Information ................................................................................... Entering Shared Data Source Information ........................................................................ Specifying (Custom or Default) Shared Data Source Setup information ......................... Verifying the Data Dictionary Data Source .............................................................. Verifying the Object Librarian Data Source .............................................................. Verifying the System Data Source .......................................................................... Setting Up Environments .............................................................................................. Adding a Custom Environment .............................................................................. Selecting an Environment ..................................................................................... Specifying Environment Data Load Parameters ......................................................... Selecting Languages ............................................................................................ Setting Up Environment Data Sources ............................................................................. Selecting an Environment Data Source Setup Option ................................................. Setting Up the Data Source for Business Data ........................................................... Setting Up the Data Source for Central Objects ......................................................... Setting Up the Data Source for Control Tables .......................................................... Verifying the Data Source for Versions ................................................................... Finalizing the Installation Plan ....................................................................................... Concluding the Validation Planner Report ....................................................................... Configuring Additional Servers ..................................................................................... 18. Creating a Language-Only Installation Plan .................................................................... Understanding Language-Only Installation Plans .............................................................. Reviewing Requirements for a Language Installation ......................................................... Installing Languages on the Deployment Server ................................................................ Running Installation Planner ......................................................................................... Accessing Installation Planner ............................................................................... Entering Information into Installation Planner ........................................................... Selecting Custom or Default Parameters .................................................................. Selecting an Environment ..................................................................................... Selecting a Language ................................................................................................... Running Installation Workbench .................................................................................... Verifying Enterprise Server Requirements ....................................................................... Verifying Workstation Requirements .............................................................................. Completing the Language Installation ............................................................................. Building and Deploying Alternate Language Packages ....................................................... 19. Understanding JD Edwards EnterpriseOne Directory Structures ....................................... Deployment Server Directory Structure ........................................................................... Language Directory Structure ........................................................................................ Enterprise Server Directory Structure .............................................................................. Workstation General Directory Structure ......................................................................... Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008

295 295 297 298 299 301 302 304 304 306 306 306 308 308 309 314 317 317 318 319 320 321 322 323 324 325 326 326 326 328 330 331 332 333 334 337 338 338 339 343 343 344 345 346 347 348 348 348 348 349 351 351 355 355 371 xi

Installation Guide for Oracle on Microsoft Windows

20. Understanding Data Source Charts ................................................................................ Business Data ............................................................................................................. Central Objects ........................................................................................................... Control Tables ............................................................................................................ Data Dictionary .......................................................................................................... Logic ........................................................................................................................ Object Librarian .......................................................................................................... Language ................................................................................................................... Local ........................................................................................................................ Server Map ................................................................................................................ System ...................................................................................................................... Versions ....................................................................................................................

373 374 375 376 377 378 379 380 381 382 383 384

21. Major Technical Tables ................................................................................................. 385 22. Working with Reports ................................................................................................... Installation Planner Validation Report (R9840B) ............................................................... Setting Processing Options .................................................................................... How to Read the Report ....................................................................................... Environment Database Creation Report (R98403) ............................................................. Setting Processing Options .................................................................................... Version XJDE0001 for Installations and Upgrades ............................................ Version XJDE0004 for Updates ..................................................................... Version XJDE0024 for Running Pristine Data .................................................. How to Read the Report ............................................................................... Errors and How to Resolve Them ................................................................... Index Recreation (R9698713) ........................................................................................ Pathcode Copy (R9800942) .......................................................................................... 23. Uninstalling the Software .............................................................................................. Understanding the Uninstallation Process ........................................................................ Uninstalling the Software from the Workstations ............................................................... Uninstalling the Deployment Server ............................................................................... Dropping Oracle Tablespaces and Indexes ....................................................................... Removing Database Users for Oracle .............................................................................. Uninstalling the Platform Pack ...................................................................................... 399 399 399 400 400 400 401 402 403 404 404 406 406 407 407 408 409 410 412 414

A. Using Instcat.sql to Support MSDE ODBC ....................................................................... 415 Running the instcat.sql SQL Script ................................................................................. 415

xii

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne


This chapter discusses: Understanding This Guide Understanding the Installation Process Considering Additional Factors Working With the Customer Checklist Environments Overview Language Process Overview

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

Chapter 1. Understanding JD Edwards EnterpriseOne

Understanding This Guide


This guide is designed to direct you through a basic JD Edwards EnterpriseOne installation. It is not a substitute for the database administration manuals provided by your Relational Database Management System (RDBMS) vendor, the network administration manuals provided by your network vendor, or the installation and configuration manuals for third-party products used with JD Edwards EnterpriseOne.

Note
You should always check Customer Connection in the section Updates and Critical Fixes for revisions to this guide subsequent to the initial release, which coincides with the General Availability of Release 8.12. Generally, this document is republished in its entirety only for the next major applications release of JD Edwards EnterpriseOne. The book contains only the procedures required for a typical base installation with predefined typical environments and databases. However, the installation is flexible enough to enable you to: Select specific components to install from multiple predefined environments and databases. Install the Platform Pack to either of these machine combinations: Enterprise Server and Database Server on one machine and one drive the Installer runs once. Enterprise Server and Database Server on separate machines (or different drives in the same machine) the Installer runs twice, once for each server.

This guide is designed for management information system (MIS) managers and installers. It outlines the procedures for installing Release 8.12. To successfully install Release 8.12, you must understand: Hardware and software requirements Database setup and management Enterprise platforms and operating systems

At a minimum, review these guides before beginning: JD Edwards EnterpriseOne Tools 8.96 Foundation Guide JD Edwards EnterpriseOne Tools 8.96 Configurable Network Computing Implementation Guide JD Edwards EnterpriseOne Tools 8.96 System Administration Guide JD Edwards EnterpriseOne Tools 8.96 Package Management Guide JD Edwards EnterpriseOne Tools 8.96 Server and Workstation Administration Guide JD Edwards EnterpriseOne Tools 8.96 Security Administration Guide

In addition, it is recommended to complete the database product courses that your database vendors provide.

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne

Understanding the Installation Process


This documentation explains the process used to install Release 8.12 software using the installation process, which consists of these steps: Install the Deployment Server (see Note below for concurrent operations) Install the Platform Pack (see Note below for concurrent operations) Set up the installation plan by running Installation Planner Run the Installation Workbench Install the HTML Web Server

Note
For Release 8.12, a JD Edwards EnterpriseOne HTML Web Server is mandatory to run web-enabled JD Edwards EnterpriseOne applications, which includes all end-user applications and selected tools applications. This guide only describes the definition of the HTML Web Server in regards to the Installation Planner and the Installation Workbench. The installation of the HTML Web Server itself is not covered by this guide. Separate guides describe the separate installation process for the HTML Web Server on the supported platforms. These HTML Web Server installation guides are available on Customer Connection. For Release 8.12, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web Server. Functionally, these terms are all synonymous. However, this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software. Install the workstations for developers and system administrators

Note
You can concurrently install the Deployment Server, the Platform Pack, and the HTML Web Server assuming the installation programs are run on different machines. This can decrease the overall time it takes to complete the installation. Installations of the Deployment Server and Enterprise Server on the same machine, which are commonly referred to as combo boxes, are not supported in production environments. You can set up your Release 8.12 configuration in many ways. You should follow the typical setup and naming conventions whenever possible, unless there is a strong business case that supports the need to change. See Also Typical Customer Configuration in the JD Edwards EnterpriseOne Tools 8.96 Configurable Network Computing Implementation Guide for more information about the typical customer configuration provided with Release 8.12.

Note
JD Edwards EnterpriseOne Release 8.12 does not support coexistence. This section discusses:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

Chapter 1. Understanding JD Edwards EnterpriseOne

Understanding the Deployment Server Installation Understanding the Platform Pack Installation Understanding the Installation Planner Understanding Installation Workbench Understanding Data Configuration Workbench Understanding the Workstation Installation

Understanding the Deployment Server Installation


The Deployment Server is the focus of the Release 8.12 installation process. The installation program for the Deployment Server copies the Release 8.12 software and a language, if applicable, from the CD to the Deployment Server. From the Deployment Server, the Release 8.12 software is distributed to one or more workstations. Since the Deployment Server and Platform Pack have separate Installers, they can be running concurrently which decreases the overall installation time (assuming the Installers are run on different machines). The Deployment Server installation program guides you through these processes: Authorization, which requires an authorization code and the number of licensed users. Release 8.12 is installed based on the information provided by the user.

The program updates the Microsoft Windows registry with information about the Release 8.12 installation and languages, if applicable.

Understanding the Platform Pack Installation


Rather than transferring all the software from the Deployment Server, the Platform Pack installs the code and database directly to the Enterprise Server. This more direct installation method increases performance during this part of the process. It is especially beneficial in situations in which the Enterprise Server is connected to the Deployment Server using a wide area network (WAN). Since the Deployment Server and Platform Pack have separate Installers, they can be running concurrently which decreases the overall installation time (assuming the Installers are run on different machines).

Understanding the Installation Planner


Installation Planner is an application that runs as a stand-alone program on the Deployment Server. Installation Planner configures the environments for all machines within the enterprise. It also is a system administration tool that stores all information about the installation plan in a set of preloaded tables in the Planner data source. Installation Planner guides you through setting up the installation plan step-by-step based on options you choose.

Note
Languages are installed using the Installation Planner from the Language CD. To install additional languages, you perform the language-specific procedures after you have executed the initial installation described in this guide. For additional details, refer to Creating a Language-Only Installation Plan. Installation Planner manages these processes:

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne

Language setup Location setup Deployment Server setup Enterprise Server setup HTML Web Server Additional server setup This includes setup to servers such as a Database Server.

Data source setup This includes setup for both Enterprise Server-specific and shared environment data sources.

Some data sources remain the same between releases: Business data Control tables

Other data sources are release specific: System and data dictionary Server map The server map is machine-specific and release-specific if separate environments are maintained. Environment setup This includes all environments for a typical customer configuration, and creation of a new environment, such as PD812. This process ensures that the Object Configuration Manager (OCM) mappings are correct and the new environments point to the correct path codes. This could include creating custom environments and path codes.

Understanding Installation Workbench


Installation Workbench runs the plan created during Installation Planner. It functions as a central point for all the processes required to install environments. Some of the processes that install environments might require procedures to be performed manually. However, Installation Workbench assures that procedures are performed in the proper order, and insulates you as much as possible from platform-specific environment setup.

Understanding Data Configuration Workbench


Data Configuration Workbench is a standalone Microsoft Windows application that you must run after the Installation Workbench as a post-install process. When you run Data Configuration Workbench, the system: Configures system and control tables based on the parameters that you enter in the application.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

Chapter 1. Understanding JD Edwards EnterpriseOne

Installs preconfigured data for specific regions and industries if you are a Rapid Start customer.

Important
You must run Data Configuration Workbench regardless of whether you are a Rapid Start customer. This ensures that if you are not a Rapid Start customer, the system is configured properly for a nonRapid Start installation. For information regarding Rapid Start, see JD Edwards EnterpriseOne Rapid Start.

Understanding the Workstation Installation


The Workstation Installation program is a stand-alone Microsoft Windows application that reads the deployment preferences information from the system tables to drive the workstation installation process. The software is installed on the workstations from the Deployment Server.

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne

Considering Additional Factors


This section discusses: Accessing Minimum Technical Requirements Using JD Edwards EnterpriseOne Support Understanding Documentation Conventions

Accessing Minimum Technical Requirements


Access the current Minimum Technical Requirement (MTR) listing from Customer Connection. You can access the MTRs through multiple entry points. This path and link are one example: Navigation: Customer Connection > Implement, Optimize + Upgrade > Optimization Guide > Supported Platforms > EnterpriseOne http://www.peoplesoft.com/corp/en/iou/platforms/enterpriseone.jsp

Using JD Edwards EnterpriseOne Support


Use Customer Connection to access customer support functions and information including issues, Software Action Requests (SARs), and to access the Oracle Update Center. Through the Update Center, you can research and download Service Packs, Electronic Software Updates (ESUs), view SARs and objects, and documentation. If you need further assistance with Release 8.12 installation or upgrade, contact Oracle customer support by phone, fax, or e-mail. Refer to Customer Connection. Limit questions to those regarding JD Edwards EnterpriseOne software. For questions about operating systems, databases, and other software products, contact the appropriate vendor. During normal business hours, a confirmation is sent within one hour of submitting issues through the web, email, or fax. An issue number is assigned immediately when reporting by telephone, and this number references all activity related to the issue.

Understanding Documentation Conventions


This section explains these typographic and design conventions used throughout this documentation. Documentation Updates Tips Fonts and Type Styles Hyperlinks

Documentation Updates
Customer Connection contains document updates and other information about installing and upgrade JD Edwards EnterpriseOne.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

Chapter 1. Understanding JD Edwards EnterpriseOne

Tips
This documentation contains tips containing information that can make the JD Edwards EnterpriseOne setup process easier. Tips information is helpful but optional.

Fonts and Type Styles


Special fonts and type styles are used in this guide. Nearly all of the commands in this guide are case sensitive. Enter them exactly as written. In addition, all of the commands described illustrate the recommended directory structure. If your machine's directory structure is different, modify the commands to match your directory structure. Italic type style designates variables used in the guide. For example, for the variable deployment_server in a command, substitute the actual name of your Deployment Server. Also, the names of other JD Edwards EnterpriseOne guides are in italic type style. For example, JD Edwards EnterpriseOne Tools 8.96 Package Management Guide. Courier font indicates explicit file names, commands, or other information that must be typed into the system. For example, a common file name used by JD Edwards EnterpriseOne is an initialization file called the JDE.INI.

Hyperlinks
The output processor used to generate the PDF versions of this document automatically produce hyperlinks. However, an anomaly in the generation process causes page numbers within brackets (for example, Hyperlinks) for the links to be included only for links within a chapter. Links external to a chapter will not contain page numbers. Likewise, hyperlinks to Appendices are not active, either within the Table of Contents or within the text body.

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne

Working With the Customer Checklist


The Release 8.12 support structure consists of components such as databases, operating systems, and hardware. To install Release 8.12 successfully, set up the support structure before starting the installation process. The tasks in this section are designed to prepare the customer's system for the installation process. Some of the tasks, such as checking that the appropriate hardware and software are available, can take some time to complete. Other tasks are quick and easy. This checklist helps to organize the required upgrade preparation: Review Environments Overview . If the installation involves a secondary language, review Language Process Overview in this chapter. Assess the network. Verify that the Deployment Server hardware and software meet minimum technical requirements. Verify that the Enterprise Server hardware and software meet minimum technical requirements. Verify that the workstation hardware and software meet minimum technical requirements. Verify that HTML Web Server hardware and software meet minimum technical requirements. Verify that the Deployment Server disk space meets minimum technical requirements. Verify that the Enterprise Server disk space meets minimum technical requirements.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

Chapter 1. Understanding JD Edwards EnterpriseOne

Environments Overview
The HTML Web Server (J) environments have the same mappings as the regular environments with the exception of logic, all of which is mapped to run on the Enterprise Server. Each environment shipped with Release 8.12 has a specific use. The following sections explain each environment in more detail. Understanding Environments Planner Environment (JDEPLAN) Pristine Environment (PS812) Deployment Environment (DEP812) Development Environment (DV812) Prototype Environment (PY812) Production Environment (PD812) Additional Considerations

Understanding Environments
The Release 8.12 software includes several environments that represent the typical customer configuration as defined in the JD Edwards EnterpriseOne Tools 8.96 Configurable Network Computing Implementation Guide. These environments are preset to make the installation process as easy as possible. This section contains additional information about these environments and their role in the installation and upgrade process. Follow the setup recommendations and naming standards described in this guide to minimize confusion when communicating with those outside of your implementation team. In addition, future upgrades are simpler if you use JD Edwards EnterpriseOne naming conventions. If you customize your configurations during the process, you should change only the descriptions provided with the typical setup. JD Edwards EnterpriseOne provides the following preset environments: Deployment (DEP812) Planner (JDEPLAN) Prototype (PY812) Pristine (PS812) Development (DV812) Production (PD812) HTML Web Server (J)

10

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne

Planner Environment (JDEPLAN)


The software installation and upgrade process includes a planning stage called the planner environment. Using this approach you can define the main components of your software configuration without affecting the production environment. Every environment must have an associated pathcode and a set of OCM mappings. The planner environment uses a planner pathcode, which is shipped with the software, and a set of OCM mappings, which point to a planner database. All pathcodes share a complete set of runtime central objects on the Deployment Server.

Planner Pathcode
Release 8.12 provides a full set of runtime objects, which are used during the installation process. The software stores these objects on the Deployment Server in the planner directory. The planner pathcode contains the only complete set of runtime central objects on the Deployment Server, which are shared by all pathcodes. The planner pathcode includes preloaded packages used during the update specification merge process. A package indicates the necessary objects for a workstation, a point-in-time snapshot of the central objects on the Deployment Server, and where the installation program finds them.

Planner Database
All information created and updated during the planning stage is saved in these Microsoft Database Engine (MSDE) databases: JDEPlan812 JDECTL812 JDEDD812 JDSYS812 JDEVL812 JDEOL812 JDEData812

When using the planner environment to change your configuration: Planner database tables are updated with the change. A plan is defined and run to move the change to the production environment.

When using the deployment or production environment to change your configuration after finishing the process: Production environment tables in the System pathcode are updated in real-time. Planner database tables are not updated.

For the deployment and production environments, OCM and data source information comes from the planner

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

11

Chapter 1. Understanding JD Edwards EnterpriseOne

database. You should use the production environment system (technical) tables to make changes to environments, pathcodes, packages, and OCM.

Pristine Environment (PS812)


Use the pristine environment (PS812) to test pristine (un-customized) objects with JD Edwards EnterpriseOne demonstration data or for training classes. The pristine environment is also used to run Table Conversion processes during an upgrade. This environment is required to compare modified objects to pristine objects. When encountering a software problem that JD Edwards EnterpriseOne Global Support cannot duplicate, they will ask you to sign on to the pristine environment to duplicate the problem. Routinely, either monthly or quarterly, refresh the data for this environment from the JDEPLAN environment on the Deployment Server. You should apply all software updates, ESUs, and Service Packs to the Pristine environment.

Deployment Environment (DEP812)


Use the deployment environment to run packages builds on the Deployment Server. The deployment environment uses the planner pathcode and has OCM mappings to the production environment system tables and local data. Only one deployment environment is required because all environments created by the installation process share common data sources. The deployment environment uses system information, such as environments, packages, and user profiles. The OCM mappings and data source information are supplied by the planner database.

Development Environment (DV812)


The development environment is for development objects (DV812 pathcode). Log on to this environment to modify and test objects before transferring them to the prototype environment (PY812) pathcode. After transferring the objects into PY812, build and install a full or partial prototype package (for example, PY812FA or PY812PA), and then log on to the prototype environment for additional testing. The Development environment is delivered with JD Edwards EnterpriseOne Demonstration data.

Prototype Environment (PY812)


The prototype environment is the staging environment for production. Constants tables and master tables, such as company constants, fiscal date patterns, and item master are populated with production data during the prototype process. Copy the tables to the production environment before going live. After running Installation Workbench, no business data exists until it is entered. When appropriate, refresh the data this environment uses from your production environment (PD812)

Production Environment (PD812)


Production users have a tested and released package on their system. Batch applications can run on the Enterprise Server.

12

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne

Additional Considerations
Additional considerations include: Push Installation Cluster Software Options Web-Based Options

Push Installation
Push installation enables the system administrator to schedule an automatic installation of a JD Edwards EnterpriseOne package to workstations. Package information is pushed from the Deployment Server to the workstation, rather than the workstation requesting (pulling) an installation from the Deployment Server. The advantage of push installation is no interaction with the user is required. For a push installation, the administrator can schedule a package to deploy to workstations at times when network traffic is low. See Also JD Edwards EnterpriseOne Tools 8.96 Package Management Guide and Installing the Workstations for Developers and System Administrators in this guide for more information about the push installation process

Cluster Software Options


When using cluster software, additional issues exist that must be taken into consideration before installing Release 8.12.

Web-Based Options
HTML Web Server installation enables the use of Web-enabled functions in Release 8.12. For more information, refer to Working with Installation Planner. See Also HTML Web Server, Java Server, or JAS in the JD Edwards EnterpriseOne Tools 8.96 HTML Web Server Installation Guide for more information about Web-based options.

Release History
This version of JD Edwards EnterpriseOne is Release 8.12. The following list shows the currently supported previous releases of JD Edwards EnterpriseOne: Release 8.11 Release 8.10 ERP 8.9 ERP 8.0 OneWorld Xe

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

13

Chapter 1. Understanding JD Edwards EnterpriseOne

Language Process Overview


Note
Languages are installed using the Installation Planner. The Language CD is required to implement this functionality. If you install additional languages, you will perform the procedures after you have executed the initial installation described in this guide. For additional details, refer to the chapter Creating a Language-Only Installation Plan in this guide. This section is provided in this guide for references purposes. The language installation process automatically copies the text from a language database to the production Release 8.12 database and merges the alternate language text with the original English base. These automated processes are described throughout this guide. When installing language for the first time, a language-only plan may be chosen after completing the initial plan. See Also Working with a Typical Installation Plan Creating a Language-Only Installation Plan for the tasks that must be completed when choosing to install an alternate language after completing the base installation.

Language Architecture
The software language architecture incorporates multinational language functionality for international customers. The software specifies the language preference for forms and reports. For example, users who share the same environment may want to view the same text in multiple languages, such as French, Spanish, and English. All language text is stored in a central location and deployed to the individual workstation. JD Edwards EnterpriseOne provides all software with a base language of English. The package build process enables the building of packages for multiple languages. Multiple languages can be installed using the processes outlined in this guide. Language text is accessed by the language preference code settings in the user profile associated with the alternate language installed.

Base Language
Release 8.12 language support works in conjunction with the English base language. The base release contains English and must be installed before creating custom modifications to include changes or additions to the translated text. All control files must also have an English record prior to adding an alternate language text record.

Alternate Language Components


An alternative language component is not included in this release; you must build the language package. An alternate language includes major components whereby language text is stored in the Central Objects, System, Control Table, and Data Dictionary data sources. The data is loaded to the Deployment Server during the installation and copied to the Central Objects and the other data sources through the language installation process. For Release 8.12, JD Edwards EnterpriseOne is shipped with 21 languages. Single-byte languages run on singlebyte or double-byte operating systems, but double-byte languages must run on double-byte operating systems. Instructions in this guide explain how to set up these features. See Also Package Build in the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for more details on how to build a language package.

14

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne

Language Preference Codes


The language preference codes are the standard language codes used throughout the software. The Language Preference Code field, located in the Release 8.12 user profile, determines which language is displayed on forms or reports. All users are assigned a language preference code within the user profile. A blank language preference code specifies the base language of English. Alternate language records always have a value in the language preference code. The alternate language text tables contain language preference codes. The tables contain several records for each item, such as a user defined code value as well as possible multiple records for a code value, with each code representing a different language. If the language preference code does not have a corresponding translated language record, the base English record is the default record. Certain database tables, such as the Business Unit Master, AAIs, Account Master, and Item Master, also contain the language preference code in an additional description table. This information is not translated in the JD Edwards EnterpriseOne demonstration data. Release 8.12 applications support the use of languages. Refer to the individual applications to set up and use multiple languages.

Database Character Set and Code Page Considerations


Data within a database is defined by a set of parameters. Each character within the database is identified by a specific language preference code value. A collection of characters within a defined database is called a character set or code page. A character set or code page setting is a scheme for encoding character data. Every character is defined by a unique hexadecimal value. These values can change between databases and languages. Every language is represented by at least one character set. Some character sets may contain multiple languages. For example, the Western European character set contains all characters common to the Western European languages (Aa - Zz) and all special characters unique to specific languages, such as , , , and . Asian character sets are specific to one language. The software uses code page conversions to control the consistent or desired display of data. A code page conversion adjusts the hexadecimal values of different characters so that the appearance of text on the desktop is the same with different code pages. When installing or upgrading the database, set up the code page for the language before loading your language specifics for Release 8.12. See Also Single-Byte and Double-Byte Considerations to determine the LocalCodeSet and code page settings for your database machine environment.

Unicode
Unicode specifies that the data stored in the data source is in Unicode format. For installs, all data sources default to Unicode. Note that the code page still must be set to the correct value even though the data sources may all be Unicode. The Unicode flag only indicates what column type is used to store character data in a Unicode database. See Also

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

15

Chapter 1. Understanding JD Edwards EnterpriseOne

JD Edwards EnterpriseOne Unicode Data Conversion Guide for information on how to convert data to Unicode. JD Edwards EnterpriseOne Tools 8.96 Development Standards for Business Function Programming Guide for information on how to convert Business Functions to support Unicode text strings. JD Edwards EnterpriseOne Flat File Conversion Guide for information on how to convert Flat Files to Unicode.

Code Page Settings


You should use the code page settings in this guide. The correct code page should be set when the database is created.

Oracle Code Page Settings


Both the NLS_characterset and NLS_LANG environment variables need to be set correctly. Additionally, the Oracle character set for the database needs to be set correctly depending on the language used as listed in this table: Tier 1 Language English French German Italian Spanish Portuguese Japanese 2 Danish Dutch Finnish Norwegian Swedish Korean Traditional Chinese Simplified Chinese 3 Arabic Czech Hungarian Polish Greek Russian Turkish Code Page Setting WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252 JA16SJIS WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252 KO16MSWIN949 ZHT16MSWIN950 ZHS16GBK AR8MSWIN1256 EE8MSWIN1250 EE8MSWIN1250 EE8MSWIN1250 EL8MSWIN1253 CL8MSWIN1251 TR8MSWIN1254

Workstations and Deployment Server


Code page settings for individual languages are specified in Microsoft Windows System locale. Verify that the Deployment Server code page is set correctly prior to upgrade.

16

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 1. Understanding JD Edwards EnterpriseOne

National Language Support


National Language Support (NLS) is a set of common standards that enable data to be entered, displayed, stored, retrieved, and printed in multiple languages, in different databases, and on different platforms. NLS is information that requires the set up of code pages and the JDE.INI for the Enterprise Server and JDE.INI for the web development workstations. By using NLS standards, JD Edwards EnterpriseOne maintains consistent data within all databases and hardware platforms. The same database can store alternate language text, relying on NLS standards to manage the text storage and retrieval. JD Edwards EnterpriseOne uses NLS, on all supported platforms, to interact with any computer system (hardware and software) within your own environment. For the workstation to reflect the language installed on the Deployment Server, perform the tasks for both the Enterprise Server and workstations to verify and modify the JDE.INI settings. These procedures are described throughout this guide.

Single-Byte and Double-Byte Considerations


Many single-byte languages support either national code pages or multinational code pages. The double-byte languages support specific individual national code pages by language. Single-byte character sets use a collection of phonetic characters that require one byte to create a single character. Conversely, the double-byte character sets use ideographic characters and require two bytes to create a single character. Single-byte languages can generally be run on single-byte or double-byte systems. Double-byte languages, such as Japanese, Chinese, and Korean, must run on machines configured to support a double-byte system. For example, a double-byte SQL Server or Oracle database is required for Chinese and Japanese languages. The software can perform a Query By Example (QBE) on any character. However, when using a double-byte language, this process may not necessarily use an understandable collating sequence, although it can still use QBE for any double-byte column. The following table shows the languages that the software supports and the LocalCodeSet values set in the JDE.INI for each platform: Tier 1 1 1 1 1 1 1 2 2 2 2 2 2 2 Language English French German Italian Spanish Portuguese Japanese Danish Dutch Finnish Norwegian Swedish Korean Traditional Chinese Language Code E F G I S P J DN DU FN NO W KO CT LocalCodeSet Value WE_ISO88591 WE_ISO88591 WE_ISO88591 WE_ISO88591 WE_ISO88591 WE_ISO88591 JA_SJIS WE_ISO88591 WE_ISO88591 WE_ISO88591 WE_ISO88591 WE_ISO88591 KO_KSC TC_BIG5

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

17

Chapter 1. Understanding JD Edwards EnterpriseOne

Tier 2 3 3 3 3 3 3 3

Language Simplified Chinese Arabic Czech Hungarian Polish Greek Russian Turkish

Language Code CS AR C HU PO GR RU TR

LocalCodeSet Value SC_GB AR_CP1256 EECP1250 EECP1250 EECP1250 GR_CP1253 RS_CP1251 TK_CP1254

Font Considerations
JD Edwards EnterpriseOne includes standard language fonts in a separate file. Some languages (such as doublebyte) require special fonts to display and print correctly. The software stores the font settings in files according to language. Individual users can choose fonts by language for forms, grids, and reports.

User Display Preferences


User display preferences are individually defined sets of Release 8.12 characteristics that are stored in the user profile. The software uses these preferences to determine how menus and forms are presented to individual users and where language is to be used in Release 8.12 for that user. After user display preferences are set up for a given user, the values remain the same on any workstation that the user accesses. Refer to the JD Edwards EnterpriseOne Tools 8.96 System Administration Guide for information about modifying user profiles.

18

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 2. Before You Begin the Installation


You should complete the tasks in this chapter before you begin the actual installation process. This chapter discusses: Verifying Software and Hardware Requirements Verifying the Disk Space Requirements

Verifying Software and Hardware Requirements


Certain minimum hardware and software requirements must be met to run Release 8.12 on various operating systems and servers. Verify that the Deployment Server, Enterprise Servers, and workstations meet the hardware and software requirements. Because the software and hardware requirements change rapidly as manufacturers constantly update their products, requirements are not provided in this documentation. Refer to Accessing Minimum Technical Requirements.

Note
Make sure that you have taken and installed the latest Planner ESU from the Update Center on Customer Connection. Failing to do so may prevent proper installation of the software. Additionally, a new compiler requirement is added for Release 8.12. Before you run the Deployment Server or Platform Pack installer, you should install a Microsoft Visual C++ compiler on any machine on which the installer will be run. The MTRs list supported C++ compilers on Microsoft Windowsbased machines. Refer to Accessing Minimum Technical Requirements

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

19

Chapter 2. Before You Begin the Installation

Verifying the Disk Space Requirements


The amount of disk space you need for Release 8.12 software on the Deployment Server and Enterprise Server depends on many variables according to platform and database. The space requirements must be available on a single drive. Having the correct amount of space available, but not on a single drive, is not adequate. Up-to-date disk space requirements are listed in the Release 8.12 Minimum Technical Requirements. Refer to Accessing Minimum Technical Requirements

Note
While the disk space tables accurately represent the disk space requirements, the actual requirements for an installation will be greater due to the requirement for temporary space.

20

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 3. Working with the Deployment Server


This chapter discusses: Installing the Deployment Server Downloading and Installing the Latest Software Troubleshooting Deployment Server Installation

Warning
If you are using the default configuration of the Deployment Server that loads to a MSDE database, you must always run the set of stored procedures in the instcat.sql SQL script that is supplied by your installation of the latest version of SQL Server or Microsoft Data Access Component (MDAC). This is required because the version of instcat.sql SQL script within the MSDE SP3 install, which is supplied by the Deployment Server installation, is older than the version supplied with Windows 2003. Otherwise, you may experience intermittent problems with accessing MSDE. You should run the proper version of the instcat.sql SQL script after you install your Deployment Server, and before you begin deploying to workstations. Refer to Using Instcat.sql to Support MSDE ODBC for requirements and operational details. If you are not using the default MSDE database on your Deployment Server, refer to the Note on the following page, under the topic Installing the Deployment Server, for a discussion of requirements for SQL Server on the Deployment Server.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

21

Chapter 3. Working with the Deployment Server

Installing the Deployment Server


Release 8.12 resides on an Intel Pentium-based Deployment Server running Microsoft Windows. The software install and upgrade programs enable you to create and maintain installation plans and deploy Release 8.12 to the Enterprise Servers and workstations. The installation program loads the software on the Deployment Server, installs the MSDE database, and then loads Planner and Workbench tables into the MSDE database on the Deployment Server.

Note
Alternatively, you can choose to replace MSDE with SQL Server as your repository on the Deployment Server. In that case, refer to Accessing Minimum Technical Requirements for specific versions of SQL Server and other requisite software, especially the SQL Native Client which is a unique requirement for SQL Server 2005. If you choose to use SQL Server, you must meet the MTRs prior to running the Deployment Server installer.

Tip
The InstallShield process creates temporary files during the install. By default these are placed on the c: drive of your Windows-based Deployment Server. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully. Alternately, you can redirect these temporary files to a different drive with more space by using this procedure to change the Environment Variables for the logged in user: 1. Create a new empty folder on the drive that has more room. For example, the drive and folder might be d:\ISMPTemp. 2. 3. 4. Right click on My Computer then choose Properties | Advanced | Environment Variables. Scroll through the variables in the top pane (User) and find TEMP and TMP. Change both of these to point to the folder you created on your larger drive in Step 1.

22

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 3. Working with the Deployment Server

Warning
Mandatory PATH Environment Variable Change If you do not have MSDE, or SQL Server, or SQL Server 2005 currently installed on the Deployment Server, the Deployment Server install will install MSDE. During the Deployment Server install, it installs MSDE then immediately attempts to use it to attach the shipped MSDE databases. This will only work if the path to the MSDE code is defined before the Deployment Server install is run. Note that the MSDE install has the location hard coded: C:\Program Files\Microsoft SQL Server To modify the PATH environment variable: 1. 2. 3. On the Deployment Server, right click on My Computer. Click on Properties | Advanced | Environment Variables. Click on PATH in the bottom pane and add to the end of the existing value: ;C:\Program Files\Microsoft SQL Server\80\Tools\BINN

This table lists the mandatory and optional components of the Deployment Server installation. Server Deployment Server Mandatory Component JD Edwards EnterpriseOne files Optional Components Production environment Prototype environment Development environment Pristine environment The installation process for the Deployment Server performs these functions: Installs the objects from the CDs. Creates the path code directory structures (such as PS812 and PD812) based on your selections. Updates the Microsoft Windows Registry.

Note
You can run the Deployment Server and the Platform Pack installation concurrently (assuming the installation programs are run on different machines). After verifying the support structure, you can install the Deployment Server. This process installs the Deployment Server from CDs.

Note
Install the Deployment Server locally; you cannot install the Deployment Server from a remote machine.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

23

Chapter 3. Working with the Deployment Server

Prerequisites Before you run the installation program, shut down all programs running on the Deployment Server that could cause DLL conflicts (such as Microsoft SQL Services, Internet Explorer, Microsoft Word, or Adobe Acrobat). You can restart these programs after you finish installing the Deployment Server.

24

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 3. Working with the Deployment Server

The diagram below illustrates the process flow and the various installation paths.

To install the Deployment Server: 1. Log on to the Deployment Server as a user with Administrator rights.

Warning
Ensure that the Administrator account name that you use does not contain any special characters. 2. Insert the first Deployment Server CD into the CD drive. The setup starts automatically. If the setup does not begin automatically or if you wish to start the installation manually, you can execute the RunInstall.exe file which is located at the root of the installation disk. The RunInstall.exe (which is called by the autorun.inf) enables the JD Edwards EnterpriseOne Deployment Server Installer to detect the drive with the most available space and to use it as the default drive for the installation. If you directly execute the Deployment Server installation program (setupwin32.exe) then the JD Edwards EnterpriseOne Deployment Server Installer will not scan available drives for disk space and you must have adequate space on your c: drive which will be the assumed default drive.

Note
The InstallShield Wizard begins to initialize and prepare the requisite JVM for the JD Edwards EnterpriseOne Deployment Server Installer. Although this may take a few minutes to completely initialize, you can view the progress on the InstallShield Wizard dialog that appears on your screen or Task Bar. When the initialization is complete, a new and separate JD Edwards EnterpriseOne Deployment Server Installer window is displayed.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

25

Chapter 3. Working with the Deployment Server

3.

On JD Edwards | EnterpriseOne Deployment Server Installer, Welcome, click Next.

4.

On JD Edwards | EnterpriseOne Deployment Server Installer, License Validation Panel, complete these fields: GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

26

Chapter 3. Working with the Deployment Server

Expiration Date

Enter the date on which Release 8.12 software expires. This date should default into the SPC generator program as 1/1/2899. For a discussion on obtaining and using the license key generator program, refer to Revalidating the Deployment Server in the chapter of this guide entitled: Installation Utilities. Enter the number of licenses.

Number of Licenses

Note
This number should be less than 5000 in order to avoid potential performance impact. For additional details, refer to Revalidating the Deployment Server in the chapter of this guide entitled: Installation Utilities. Enter the codes that were generated by the SPC generator program. For a discussion on obtaining and using the license key generator program, rRefer to Revalidating the Deployment Server in the chapter of this guide entitled: Installation Utilities.

Authorization Code

Caution
Each time the setup program is run, the serial number changes, which requires a new JD Edwards EnterpriseOne authorization code. Avoid stopping and rerunning the installation program after obtaining an authorization code. 5. Click Next.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

27

Chapter 3. Working with the Deployment Server

6.

On JD Edwards | EnterpriseOne Deployment Server Installer, directory selection panel, complete this field: Directory Name Enter the drive and directory where you want the files installed on your Deployment Server. The JD Edwards EnterpriseOne Deployment Server Installer automatically scans all drives for available space and by default chooses the drive that contains the most available space. For example: z:\JDEdwards\E812

7. 8.

Click Next. On JD Edwards | EnterpriseOne Deployment Server Installer, setup type panel, choose your installation type: Typical Recommended for most users, choose this setup type if you wish to complete the Deployment Server installation with no further specifications. This installation option includes the required JD Edwards EnterpriseOne files for the Prototype and Pristine environments.

Tip
If you choose Typical installation, you can skip directly to step 11 located later in this task to complete the Deployment Server installation. Recommended for experienced users, choose this setup type if you wish to complete the Deployment Server installation by specifying the installation of a subset of pre-defined environments.

Custom

9.

If you chose Custom Mode on the previous panel, on JD Edwards |EnterpriseOne Deployment Server Installer, feature selection panel, select the features you want to install:

28

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 3. Working with the Deployment Server

JD Edwards EnterpriseOne Files

Note
This selection includes mandatory system files. If you do not select this box and the JD Edwards EnterpriseOne Deployment Server Installer can not detect the required system files, it selects them automatically and displays a warning message. On the warning message, you must either select OK to acknowledge that the selection of the mandatory system files, or click Back and change your selections manually. Likewise, if you re-run the JD Edwards EnterpriseOne Deployment Server Installer to add an environment it will check to ensure that these files are already installed and you will not be given an option to install the environment on a machine, drive, or directory that is different from that which contains the JD Edwards EnterpriseOne files. Production Environment Prototype Environment Development Environment Pristine Environment

10. Click Next. 11. On JD Edwards | EnterpriseOne Deployment Server Installer, summary information panel, verify that the appropriate components are selected. If there is insufficient disk space to complete the installation is available on the Deployment Server target machine, an error message is displayed. 12. Click Next to begin the Installation. The JD Edwards EnterpriseOne Deployment Server Installer displays a panel showing the ongoing status of the installation. On JD Edwards | EnterpriseOne Deployment Server Installer, after the installation is complete, a message appears stating that the installation was successful. 13. Click Finish to complete the installation and exit the JD Edwards | EnterpriseOne Deployment Server Installer.

Note
After the JD Edwards EnterpriseOne Deployment Server Installer is complete, a panel may appear directing you to reboot the machine to complete the installation. This occurs if certain Microsoft Windows systems files are in use at the time of installation and therefore cannot be modified in real time. Therefore, in such cases the installation cannot be completed until the machine is rebooted.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

29

Chapter 3. Working with the Deployment Server

Tip
You should review the log file created by the Deployment Server Installer. The file is named log.txt and is located in the Deployment Server installation directory. For example:

30

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 3. Working with the Deployment Server

x:\JDEdwards\E812\log.txt

Downloading and Installing the Latest Software


Before continuing with the installation, download and install the latest Tools Release, Tools Release Patch, requisite JDBC drivers, and Planner Update from the Update Center.

Note
The order in which the following Tools Release and updates are applied is very important. Do not deviate from the order below. This section discusses: Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server Installing JDBC Drivers for SQL Server 2000 Installing the Latest Planner Update

Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server
To install the latest tools release and latest tools release patch: 1. 2. From the Update Center homepage, download the latest Tools Release Patch (for example, 8.96.A1) and Tools Release documentation. Using the Tools Release documentation, install the Tools Release Patch to the Deployment Server.

Note
If you have ever used the Drag and Drop method of moving between Tools Releases for service packs, it is necessary to run the Reconfigure MSDE Utility. To do so, navigate to this directory on your Deployment Server: JDEdwards\E812\system\bin32 From that directory, run this batch file: ReconfigureMSDE.exe When you run this program, a dialog prompts whether you want to convert the password to be compatible with JD Edwards EnterpriseOne SP1 or with SP2 and greater. Select SP2 and greater and click on OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

31

Chapter 3. Working with the Deployment Server

Installing JDBC Drivers for SQL Server 2000


The SQL Server 2000 drivers are required for all installations to access databases on the Deployment Server, regardless of the database you are using on the Enterprise Server.

Note
These instructions are for the Deployment Server only, for installations of JD Edwards EnterpriseOne Applications Release 8.9 or newer that have not set up the Web Development features for Package Build. To install JDBC drivers for SQL Server 2000: 1. On your Deployment Server, create this directory: EnterpriseOne_Install_Location\OneWorld Client Install\ThirdParty \WebDevFeature\JDBC

Note
If this directory already exists and contains the SQL Server 2000 drivers listed in Step 4 no further action is necessary. 2. Obtain the SQL Server 2000 JDBC drivers from Microsoft. Microsoft provides a Type 4 JDBC driver for SQL Server 2000 with full support at no additional charge to licensed customers. a. Download the appropriate driver directly from the Microsoft web site using this link to search the Microsoft Downloads site: http://www.microsoft.com/downloads/search.aspx?displaylang=en b. c. 3. Enter JDBC Driver as your search criteria and choose SQL Server 2000 Driver for JDBC Service Pack 3 with a release date of 7/6/2004. Download only the setup.exe component to a temporary directory on the Deployment Server. For example, x:\temp.

On your Deployment Server, run the setup.exe and choose Custom Installation, which will enable you to choose the SQL Server 2000 Driver for JDBC component to install. Change the default directory in which to install the JDBC drivers from C:\Program Files\Microsoft SQL Server 2000 Driver to point to your temporary directory that you created in the previous Step, in the Substep c. For example, x:\temp.

4.

Navigate to the temporary directory, in the x:\temp\lib subdirectory, and copy these files to the JDBC directory you created in Step 1: msbase.jar msutil.jar mssqlserver.jar

32

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 3. Working with the Deployment Server

Installing the Latest Planner Update


Warning
Due to unpredictable timing issues, there is a possibility that at the end of the Deployment Server install, the MSDE databases that are needed for the planner environment may not automatically get attached as designed by the Installer. Not only will an unattached MSDE database cause the installation of the planner update to fail, it will also prevent you from signing on to the JDEPLAN environment. Navigate to the directory JDEdwards\E812\planner\data and run this script: attach_planner.bat This will attach any databases that were not successfully attached by the install.

Tip
To attach the Metadata MSDE database, navigate to the Planner\spec directory and run this batch file: attach_metadata812.bat

Caution
As part of the MSDE install, which is bundled with the Deployment Server Installer, the password for the sa user on the JDELocal instance is scrambled. If you re-set this password, several JD Edwards EnterpriseOne functions will fail. If you should inadvertently reset the password, you can scramble it again to the expected default password. To do so, navigate to this directory on your Deployment Server: JDEdwards\E812\system\bin32 From that directory, run this batch file: ReconfigureMSDE.exe When you run this program, a dialog prompts whether you want to convert the password to be compatible with JD Edwards EnterpriseOne SP1 or with SP2 and greater. Select SP2 and greater and click on OK. To install the latest planner update: 1. From Customer Connection, download the latest planner update to the Deployment Server. For example, if you are upgrading from JD Edwards EnterpriseOne Release 8.11 to JD Edwards EnterpriseOne Release 8.12, you should install the most recent Tools Release 8.96 planner update. 2. Run the self-extracting executable and follow the on-screen instructions to install the planner update on the Deployment Server.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

33

Chapter 3. Working with the Deployment Server

3.

You must enter a valid JD Edwards EnterpriseOne user and password in order to initialize the Planner environment. The default values are JDE for the user and JDE for the password.

Note
The above login screen is displayed so that the Planner Update can update the metadata specifications on the Deployment Server. 4. When the installation finishes, view the JD Edwards EnterpriseOne Deployment Server Setup form to confirm that the installation was successful.

Tip
If the folder into which you expanded the Planner Update is empty, you should run the selfextracting executable (jxxxx.exe) again. When the Welcome screen comes up, click on Cancel to quit. 5. Follow the steps in the Special Instructions, which are contained within an HTML file that is shipped with the Planner Update. The special instructions file located in this directory with this file name: x:\download_directory\planner_update_id\E812SpecialInstructions.htm where download_directory is the directory where you downloaded the Planner Update.

Caution
You must run the SpecialInstrs.bat every time you apply a new Planner Update.

34

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 3. Working with the Deployment Server

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

35

Chapter 3. Working with the Deployment Server

Troubleshooting Deployment Server Installation


If you have previously run the Deployment Server installer on your Deployment Server, you should ensure that an invalid vpd.properties file does not exist on that machine; otherwise, the installer may fail to start or complete properly. Refer to Installer Will Not Start or Complete (Invalid vpd.properties) for additional details.

36

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack


This chapter discusses: Understanding the Platform Pack Configuring the Enterprise Server Prior to Installing the Platform Pack Verifying Code Page Settings for Oracle Understanding the Platform Pack Installation Installing the Platform Pack Rerunning the JD Edwards EnterpriseOne Platform Pack Installer Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server Working with Database Security

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

37

Chapter 4. Working with the Platform Pack

Understanding the Platform Pack


The Platform Pack installs these major components: JD Edwards EnterpriseOne Server code JD Edwards EnterpriseOne database files

Note
You can concurrently install the Deployment Server, the Platform Pack, and the HTML Web Server (also previously known as JAS) assuming the installation programs are run on different machines. This can decrease the overall time it takes to complete the installation.

Note
To reinstall any Enterprise Server components, refer to Rerunning the JD Edwards EnterpriseOne Platform Pack Installer. This table lists the mandatory and optional components of the Platform Pack installation: Server Enterprise Server Mandatory Component Optional Components

JD Edwards EnterpriseOne Founda- ES Production tion ES Prototype ES Development ES Pristine

Database Server

System Database

Production Databases Prototype Databases Development Databases Pristine Databases

Note
Micosoft Windows Considerations. Microsoft clustering is supported for system failover protection. As detailed in the Minimum Technical Requirements, install any Microsoft Windows server upgrades that are required to support Release 8.12. Before you install Release 8.12 software on the Microsoft Windows Enterprise Server, you must create the Release 8.12 administrator user, verify disk space, and set up and verify the hosts file.

38

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Configuring the Enterprise Server Prior to Installing the Platform Pack


This section discusses: Setting Up NLS_LANG Parameter for Oracle Enabling Remote Connections for Oracle Setting Up and Verifying the Hosts File

See Also Verifying Software and Hardware Requirements for more information about software requirements. Microsoft Cluster Administrator Guide or Microsoft Windows Server 4 Second Edition for more information on using cluster software. Release 8.12 on a Cluster section in JD Edwards EnterpriseOne Tools 8.96 Server and Workstation Administration Guide for more information about clustering.

Setting Up NLS_LANG Parameter for Oracle


You can add or edit the NLS_LANG parameter by accessing the System dialog from the Control Panel. You may need to add the NLS_LANG variable, if it does not exist. The system variable name is NLS_LANG and the variable value (prefixed by a period) should be equal to the code page value set for the NLS_CHARACTERSET in the Oracle database.

For example, if your database is using the code page JA16SJIS (Japanese), the NLS_LANG variable parameter setting would look like this:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

39

Chapter 4. Working with the Platform Pack

Caution
Remember to add a period in front of the NLS_LANG variable value for the given code page. See Also Refer to Language Process Overview for these values and additional information regarding the National Language Support tables.

Enabling Remote Connections for Oracle


If you are having trouble running the JD Edwards EnterpriseOne Platform Pack Installer against your Oracle database, you may need to enable your Oracle database to enable the system to remote connect as sysdba. Oracle treats the connection established by the JD Edwards EnterpriseOne Platform Pack Installer as a remote connection because the SID is specified within the SQLPLUS command. For example, the JD Edwards EnterpriseOne Platform Pack Installer issues this sqlplus command: system/managers@ora920u3 as sysdba To enable remote connections for your Oracle database: 1. Edit the init.ora file, and set the remote condition by adding this line: REMOTE_LOGIN_PASSWORDFILE=SHARED

Note
If your Oracle database installation is not using the JD Edwards EnterpriseOne system administrator password setup by scripts run during the installation of JD Edwards EnterpriseOne, you will need to consult with your Oracle DBA. 2. 3. After the utility runs, you must shut down and restart Oracle. You must then grant the an Oracle system user with sysdba permissions. For example, you could issue this sqlplus command: SQL> grant sysdba to user_name; 4. Verify the password parameter. For example, you can issue this sqlplus command:

40

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

SQL> show parameter password The sqlplus command produces these results: NAME TYPE VALUE remote_login_passwordfile string EXCLUSIVE 5. Verify the user is listed in the password file. For example, you could issue this sqlplus command: SQL> select * from v$pwfile_users; The sqlplus command produces these results: USERNAME SYSDBA SYSOPER SYS TRUE TRUE SYSTEM TRUE FALSE

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

41

Chapter 4. Working with the Platform Pack

Setting Up and Verifying the Hosts File


If you use the Domain Naming Service (DNS) or the Microsoft Windows Internet Naming Service (WINS), you do not need to set up and verify the hosts file. To set up and verify the Hosts file: 1. Using Microsoft Windows Explorer, access this directory: \Winnt\System32\Drivers\Etc\Hosts 2. 3. For each Enterprise Server on your network, you will need a machine IP address, and a machine name. Verify that the address and name are each on a separate line, and that there is a return character at the end of each line. A pound sign (#) marks the start of a comment, and the end-of-line (return) character marks the end of a comment. 4. If clustering is being used, verify that the cluster name is used as the machine name, not one of the server names.

42

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Special Consideration for Oracle 11g on Windows


Warning
The JD Edwards EnterpriseOne Release 8.12 Platform Pack database scripts do not work correctly with the default installation of Oracle 11g. By default, Oracle 11g uses case-sensitive database passwords (whereas this was not the case for versions of Oracle databases previous to 11g). This behavior causes this version of Platform Pack database installation to fail. In order to resolve this issue, before running the Platform Pack database installation scripts, run this command from the SQL Plus command line: SQL> alter system set sec_case_sensitive_logon = FALSE;

Verifying Code Page Settings for Oracle


Release 8.12 requires that the national character set of an Oracle database be set to AL16UTF16. Make sure AL16UTF16 is chosen for a new Oracle database install. If installing a non-English language, the correct code page parameters must be set in the Oracle database and on the Microsoft Windows or UNIX operating systems. In this section you will verify and set the NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET parameters in Oracle and set the NLS_LANG parameter in your operating system to be used in conjunction by the Oracle database. Determine the appropriate NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET values for the language being installed on the Oracle database and set the NLS_LANG value accordingly for both the Oracle client and database server.

Caution
Set the NLS_ CHARACTERSET and NLS_NCHAR_CHARACTERSET parameters for the appropriate language before loading your central objects specification objects for Release 8.12. To verify the code page settings for Oracle: 1. Verify the code page setting of the Oracle database by executing this single-line SQL command from SQL Plus: SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET'; 2. Verify the Unicode code page setting of the Oracle database by executing this single-line SQL command from SQL Plus: SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET'; If the setting is incorrect, set the NLS_NCHAR_CHARACTERSET value to AL16UTF16, using the Oracle documentation to change the setting. 3. Set up NLS_LANG parameter for Oracle. For JD Edwards EnterpriseOne environments with languages to function properly, the NLS_LANG parameter must be set correctly for Oracle. These settings must be set for your Oracle client workstations and Oracle database server.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

43

Chapter 4. Working with the Platform Pack

Caution
Remember to add a period before the NLS_LANG variable value for the given code page. See Also Refer to the Language Process Overview in the for the National Language Support tables and other information related to multilingual installations.

44

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Understanding the Platform Pack Installation


The Platform Pack installation process installs Release 8.12 system and path code files. The diagram below illustrates the process flow and the various installation paths.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

45

Chapter 4. Working with the Platform Pack

Installing the Platform Pack


This section discusses: Running the JD Edwards EnterpriseOne Platform Pack Installer Custom Mode Feature Selection Database Options Oracle - Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) - or Database only Oracle - Enterprise Server Only (Different Machine from Database Server) Review the Legacy Database Warning Panel Concurrent Users Review the Summary Information Panel and Complete the Installation Verifying the Platform Pack Log File

46

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Running the JD Edwards EnterpriseOne Platform Pack Installer


Note
If you are copying or downloading the CD images onto your machine before running the JD Edwards EnterpriseOne Platform Pack Installer, you must name the CD images disk1, disk2, disk3, and so on. Otherwise, the JD Edwards EnterpriseOne Platform Pack Installer will not find them.

Warning
If you have previously run the Platform Pack installer on your Enterprise Server, you should ensure that an invalid vpd.properties file does not exist on that machine; otherwise, the installer may fail to start or complete properly. Refer to Installer Will Not Start or Complete (Invalid vpd.properties) for additional details.

Tip
The InstallShield process creates temporary files during the install. By default these will be placed on the c: drive of a Windows machine. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully. Refer to the Tip in the chapter entitled:Working with the Deployment Server at the beginning of the section entitled: Installing the Deployment Server for a procedure you can use to increase your disk space. To run the JD Edwards EnterpriseOne Platform Pack Installer: 1. Log on to the Enterprise Server as a user with Administrative rights.

Warning
Ensure that the Administrator account name that you use does not contain any special characters. 2. Insert the JD Edwards EnterpriseOne Platform Pack Installer CD into the CD drive. The setup starts automatically. If the setup does not begin automatically or if you wish to start the installation manually, you can execute the RunInstall.exe file which is located at the root of the installation disk. The RunInstall.exe (which is called by the autorun.inf) enables the JD Edwards EnterpriseOne Platform Pack Installer to detect the drive with the most available space and to use it as the default drive for the installation. If you directly execute the JD Edwards EnterpriseOne Platform Pack Installer (RapidSetup.exe) then it does not scan available drives for disk space and you must have adequate space on your c: drive which is the default drive.

Note
The InstallShield Wizard begins to initialize and prepare the requisite JVM for the JD Edwards EnterpriseOne Platform Pack Installer. Although this may take a few minutes to completely initialize, you can view the progress on the InstallShield Wizard dialog that appears on your screen or Task Bar. When the initialization is complete, a new and separate JD Edwards EnterpriseOne Platform Pack Installer window is displayed. 3. On JD Edwards | EnterpriseOne Platform Pack Installer, Welcome, click Next.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

47

Chapter 4. Working with the Platform Pack

4.

On JD Edwards | EnterpriseOne Platform Pack Installer, directory selection panel, complete this field: Directory Name Enter the drive and directory where you want the files installed on your Enterprise Server. The JD Edwards EnterpriseOne Platform Pack Installer automatically scans all drives for available space and by default chooses the drive that contains the most available space. The default value is: c:\JDEdwards\E812 If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer, refer to Rerunning the JD Edwards EnterpriseOne Platform Pack Installer.

5. 6.

Click Next. On the Run Mode selection panel, choose whether you want to install or upgrade JD Edwards EnterpriseOne. Refer to the following table for a full description of each run mode. Install This document only describes the Install Mode. In this mode, the JD Edwards EnterpriseOne Platform Pack Installer checks for the existence of JD Edwards EnterpriseOne business data and control tables; if either exists, the JD Edwards EnterpriseOne Platform Pack Installer aborts. This prevents the inadvertent overwriting of existing critical business data and control tables. If the JD Edwards EnterpriseOne Platform Pack Installer does not detect pre-existing JD Edwards EnterpriseOne data or control tables, the installation process continues normally.

48

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Caution
Upgrade You should always back up all databases that you want to preserve. The Upgrade Mode is described in a separate document entitled: JD Edwards EnterpriseOne Release 8.12 Upgrade Guide. In this mode, the JD Edwards EnterpriseOne Platform Pack Installer checks for the existence of JD Edwards EnterpriseOne business data and control tables which are prerequisites to an upgrade of JD Edwards EnterpriseOne.

Note
If you chose Upgrade mode, the JD Edwards EnterpriseOne Platform Pack Installer displays a panel that confirms the data and tables required for an upgrade and also offers you the option to change from Upgrade to Install. 7. On JD Edwards | EnterpriseOne Platform Pack Installer, setup type panel, choose your installation type: Typical Choose this setup type if you wish to complete the Platform Pack installation with no further specifications. This installation option is recommended for most users and includes the required JD Edwards EnterpriseOne files for the Prototype and Pristine environments.

Tip
If you choose Typical installation, you can skip directly to Database Options located later in this task to complete the Platform Pack installation. Recommended for experienced users, choose this setup type if you wish to complete the Platform Pack installation by specifying the installation of a subset of pre-defined environments.

Custom

Tip
If you choose Custom installation, continue with the steps below in this task which immediately follow. 8. Click Next.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

49

Chapter 4. Working with the Platform Pack

Custom Mode Feature Selection


Note
This section is only applicable if you chose Custom installation mode. If you chose Typical Mode, you can skip to Database Options.

1.

If you are installing in Custom Mode, on JD Edwards | EnterpriseOne Platform Pack Installer, features panel, select from these choices: JD Edwards EnterpriseOne Enterprise Server JD Edwards EnterpriseOne Foundation

Note
This selection includes system files. You must choose this feature for all initial installations of the Enterprise Server. If you do not select this feature, the JD Edwards EnterpriseOne Platform Pack Installer checks your system to verify that the JD Edwards EnterpriseOne Foundation is already installed. If not, the JD Edwards EnterpriseOne Platform Pack Installer automatically selects it for installation. 50 ES Production ES Prototype ES Development GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

ES Pristine

JD Edwards EnterpriseOne Database Server System Database

Note
This selection includes mandatory system files. If you do not select this box and the JD Edwards EnterpriseOne Platform Pack Installer can not detect the required system files, it selects them automatically and displays a warning message. On the warning message, you must either select OK to acknowledge that the selection of the mandatory system files, or click Back and change your selections manually. Likewise, if you rerun the JD Edwards EnterpriseOne Platform Pack Installer to add an environment it will check to ensure that these files are already installed and you will not be given an option to install the environment on a machine, drive, or directory that is different from that which contains the JD Edwards EnterpriseOne Files. 2. Production Databases Prototype Databases Development Databases Pristine Databases

Click Next to continue.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

51

Chapter 4. Working with the Platform Pack

Database Options
Regardless of which installation type you chose, Typical or Custom, you must enter database options as described in this procedure.

1.

On JD Edwards | EnterpriseOne Platform Pack Installer, Database Options, complete these fields: Database Type Database Server Name Use the pulldown menu to choose Oracle Server. By default, the JD Edwards EnterpriseOne Platform Pack Installer automatically detects and populates this field with the machine name on which it is running. The JD Edwards EnterpriseOne Platform Pack Installer validates the Database Server name and compares it against the name of the local computer. If these values are different (for example, if you manually change the value of this field), the JD Edwards EnterpriseOne Platform Pack Installer assumes the Database Server is . If you have selected to install databases, and the database server name that you entered cannot be validated, an error dialog is displayed with resolution instructions. For additional details on error conditions, refer to Troubleshooting Platform Pack Installation.

2.

Click Next.

52

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

When choosing the database, consider these scenarios depending on which machine the database resides: Oracle - Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) - or Database only Oracle - Enterprise Server Only (Different Machine from Database Server)

Oracle - Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) - or Database only
This configuration assumes you have selected to install your JD Edwards EnterpriseOne database server locally on the same machine as your Enterprise Server, or that you are installing a database only.

On the Oracle Database Instance configuration panel, complete these fields: CONNECT STRING Enter a valid value for your Oracle connect string. You may need to obtain this value from your Oracle DBA. You cannot proceed with the installation until this value can be validated by the JD Edwards EnterpriseOne Platform Pack Installer; that is, the Installer will not allow you to proceed if it cannot connect to the database. The installer provides a default value of sys.

SYSADMIN USER

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

53

Chapter 4. Working with the Platform Pack

Warning
You can not use a value of system for the SYSADMIN USER field. You must use the value sys or a user similar to sys. All of the Oracle scripts used by theJD Edwards EnterpriseOne Platform Pack Installer use this syntax to connect to the database: sys as sysdba where sys is the value you enter in the SYSADMIN USER field. Therefore, the Installer's syntax will not work with the system user. The value sys (or equivalent) identifes the system administration user for your Oracle installation. This user must have full DBA privileges which are standard for Oracle installations. The JD Edwards EnterpriseOne Platform Pack Installer validates the user login and ensures the user has the appropriate DBA privileges in order to create and populate the Oracle tables. Enter a valid password for the system administration user under which you will be installed the JD Edwards EnterpriseOne Oracle databases. Enter the path where you want the JD Edwards EnterpriseOne Platform Pack Installer to create your Oracle database tables. For example: z:\database_location

SYSADMIN PASSWORD Directory for database tables

Note
The Installer automatically appends the path you enter here with \ORCL. Enter the path where you want the JD Edwards EnterpriseOne Platform Pack Installer to create your Oracle database indexes. For example: z:\database_location

Directory for database indexes

Note
The Installer automatically appends the path you enter here with \ORCL.

Warning
You should always consult with a DBA for the proper location of the RDBMS system on your machine. Do not install your RDBMS system in location with a child relationship to the JD Edwards EnterpriseOne installation directory, x:\JDEdwards. This practice avoids any potential where actions against the parent directory might adversely impact the child directory. An information panel displays confirming the information you specified for the locations for the Oracle database tables, indexes, and run-time scripts (which are called by the JD Edwards EnterpriseOne Platform Pack Installer). After you have read and confirmed the Oracle installation information, click Next and proceed to Database Options in this task.

54

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Oracle - Enterprise Server Only (Different Machine from Database Server)


This configuration assumes you have selected to install your JD Edwards EnterpriseOne Enterprise Server on a different machine than your JD Edwards EnterpriseOne Database Server.

On the Oracle Connect String panel, complete this field: Connect String Enter a valid value for your Oracle connect string. You may need to obtain this value from your Oracle DBA. You cannot proceed with the installation until this value can be validated by the JD Edwards EnterpriseOne Platform Pack Installer; that is, the Installer will not allow you to proceed if it cannot connect to the database.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

55

Chapter 4. Working with the Platform Pack

Review the Legacy Database Warning Panel


A warning panel displays with this text:

After reviewing the contents of the warning panel, click Next.

56

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Concurrent Users
If you chose to install an Enterprise Server you are presented with the screen that prompts you to enter the number of concurrent users that will be used on that server. The values you enter on this screen, along with the selection or deselection of the specified JD Edwards EnterpriseOne applications, is used by the JD Edwards EnterpriseOne Platform Pack Installer to calculate and set certain JDE.INI settings that will result in optimal server performance for the JD Edwards EnterpriseOne installation.

1.

On JD Edwards | EnterpriseOne Platform Pack Installer, complete these fields: Please enter the number of concurrent users that will be using this system Will any of the following be used by the JD Edwards EnterpriseOne system? Enter a valid value greater than zero.

Click the Yes radio button if you are using any of the following JD Edwards EnterpriseOne applications: Sales Order Processing Configurator Journal Entry Job Cost

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

57

Chapter 4. Working with the Platform Pack

Advance Pricing Purchase Order Inventory

The selection or deselection of this radio button influences the calculations that the JD Edwards EnterpriseOne Platform Pack Installer computes in order to set the JDE.INI on the Enterprise Server for optimal performance. 2. Click Next to continue.

58

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Review the Summary Information Panel and Complete the Installation


To review the Summary Information Panel and to complete the installation: 1. On the Summary Information Panel, review the list of installation components and click Next to begin the installation. On JD Edwards | EnterpriseOne Platform Pack Installer, after the installation is complete, a message appears stating that the installation was successful. 2. Click Finish to complete the installation and exit the JD Edwards | EnterpriseOne Platform Pack InstallShield Wizard. You have successfully completed the Typical installation of the Platform Pack for the JD Edwards EnterpriseOne Enterprise Server. You can proceed to the next major section in this guide entitled: Planning the Installation.

Note
After the Enterprise Server portion of the JD Edwards EnterpriseOne Platform Pack Installer is complete, a panel may appear directing you to reboot the machine to complete the installation. This occurs if certain Microsoft Windows systems files are in use at the time of installation and therefore cannot be modified in real time. Therefore, in such cases the installation cannot be completed until the machine is rebooted.

Verifying the Platform Pack Log File


You can verify that the Platform Pack Installer ran properly by viewing the log file. The Platform Pack Installer creates a log.txt file in the directory where you installed the Platform Pack. For example: drive:\JDEdwards\E812

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

59

Chapter 4. Working with the Platform Pack

Troubleshooting Platform Pack Installation


This section discusses these potential error or warning conditions and their probable causes and resolutions when running the JD Edwards EnterpriseOne Platform Pack Installer: Installer Will Not Start or Complete (Invalid vpd.properties) Business Data and Control Tables Already Exist Business Data and Control Tables Do Not Exist Business Data or Control Tables Tablespaces Reported As Existing When They Do Not Exist System Database Not Detected Foundation Files Do Not Exist

60

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Installer Will Not Start or Complete (Invalid vpd.properties)


If either the Deployment Server or Platform Pack installer indicates that the product is installed when it is not, or if the installation is interrupted before it completes, invalid entries may exist in the vpd.properties file. This file is used by Installer to record installed components. However, if the Installer is interrupted this file may contain references to components that may not yet have been successfully installed. To resolve this situation, run the InstallShield Uninstaller before attempting a reinstallation. The Uninstaller removes any problematic entries from vpd.properties and also removes any components that have already been installed. If you have an existing vpd.properties file that you cannot repair or remove by running the InstallShield Uninstaller, you should rename it. You should rename instead of delete because in JD Edwards EnterpriseOne releases prior to Release 8.12 which were installed using InstallShield the vpd.properties file is shared by other programs that were installed using InstallShield. Therefore, by renaming the file instead of deleting it, once you complete the current installation of JD Edwards EnterpriseOne you will have the prior file available in case you need to restore it when you uninstall other programs. Refer to the following table for locations of the vpd.properties file on the Deployment Server and the Enterprise Server. Location of vpd.properties File Installer Directory Containing the vpd.properties File Deployment C:\Program Files\Common Server Files\InstallShield\Universal\JDEdwardsDepSvr\E812 Platform Pack For JD Edwards EnterpriseOne Releases Prior to Release 8.12: In the Windows system directory. For example, your Windows system directory might be c:\Windows, or c:\winnt. For JD Edwards EnterpriseOne Release 8.12: C:\Program Files\Common Files\InstallShield\Universal\JDEdwardsPPack\E812

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

61

Chapter 4. Working with the Platform Pack

Business Data and Control Tables Already Exist


This screen indicates that the JD Edwards EnterpriseOne Platform Pack Installer has detected that business data and control tables already exist.

If you receive this error, it means you have selected Install as the installation type (as opposed to Upgrade) and the JD Edwards EnterpriseOne Platform Pack Installer has detected that the DTA and CTL tablespaces already exist for the selected environment. To resolve the error condition, you must uninstall the referenced database as specified by the text in the error.

62

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Business Data and Control Tables Do Not Exist


This screen indicates that the JD Edwards EnterpriseOne Platform Pack Installer has detected that business data and control tables do not exist.

If you receive this error, it means you have selected Upgrade as the installation type (as opposed to Install) and the JD Edwards EnterpriseOne Platform Pack Installer has detected that the DTA and CTL tablespaces do not exist for the selected environment. That is, a separate error panel is displayed for each environment (such as Production, Development, Test, or CRP) that you selected, already exists, but does not already contain the mandatory DTA and CTL tablespaces. To resolve the error condition, you must go back and select Install instead of Upgrade.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

63

Chapter 4. Working with the Platform Pack

Business Data or Control Tables Tablespaces Reported As Existing When They Do Not Exist
If the Platform Pack Installer reports that Business Data and Control Tables exist, but in fact the Oracle tablespaces do not exist, ensure the Oracle account has rights to write to its home directory. 1. 2. 3. Navigate to /home and list the directories Check that the Oracle account has write privilege on its home directory. Verify that the Oracle connect string and database home are specified in the correct case.

System Database Not Detected


This screen indicates that the JD Edwards EnterpriseOne Platform Pack Installer has not detected the mandatory System database.

If you receive this error, it means you have selected to install one or more databases but do not have the mandatory JD Edwards EnterpriseOne Database Foundation Components already installed or selected for installation. After the JD Edwards EnterpriseOne Platform Pack Installer displays this error, as a user convenience, it automatically selects the mandatory Database Foundation Components for installation. Therefore, at this point you can continue with the installation which will include the mandatory components. Alternately you can manually navigate backwards and make additional changes to your existing selections.

64

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

65

Chapter 4. Working with the Platform Pack

Foundation Files Do Not Exist


This screen indicates that the JD Edwards EnterpriseOne Platform Pack Installer has not detected the mandatory Foundation files.

If you receive this error, it means you have selected to install one or more environments but do not have the mandatory JD Edwards EnterpriseOne Server Foundation Components already installed or selected for installation. After the JD Edwards EnterpriseOne Platform Pack Installer displays this error, as a user convenience, it automatically selects the mandatory Enterprise Server Foundation Components for installation. Therefore, at this point you can press to continue with the installation which will include the mandatory components. Alternately you can manually navigate backwards and make additional changes to your existing selections.

66

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Rerunning the JD Edwards EnterpriseOne Platform Pack Installer


You must rerun the JD Edwards EnterpriseOne Platform Pack Installer to support these scenarios: You want to install the Enterprise Server and the Database Server on physically different machines. You want to add an Enterprise Server environment to the Enterprise Server. You want to add a Database Server database to the Database Server. You want to reinstall the JD Edwards EnterpriseOne Foundation on the Enterprise Server. You want to reinstall the System Database on the Database Server.

You should never reinstall any optional components without first uninstalling the components. If you select to uninstall the mandatory components you must also select to uninstall or have already uninstalled all related optional components. This table lists the mandatory and related optional components: Server Enterprise Server Mandatory Component JD Edwards EnterpriseOne Foundation Optional Components ES Production ES Prototype ES Development ES Pristine Database Server System Database Production Databases Prototype Databases Development Databases Pristine Databases

Enterprise Server
If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer in order to add environments, you must specify the same machine, drive, and directory as that which you selected for JD Edwards EnterpriseOne Foundation during the initial installation of the Platform Pack.

Database Server
If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer in order to add databases, you must specify the same machine, drive, and directory as that which you selected for System Database during the initial installation of the Platform Pack.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

67

Chapter 4. Working with the Platform Pack

Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server
Caution
The Tools Release level must match what was installed on the Deployment Server. For instructions on installing the tools release, refer to JD Edwards EnterpriseOne Tools Release 8.96 Installation Guide, which is available by platform on Customer Connection. To install the latest tools release and latest tools release patch: 1. 2. From the Update Center homepage, download the latest Tools Release Patch (for example, 8.96.A1) and Tools Release documentation. Using the Tools Release documentation, install the Tools Release Patch to the Enterprise Server.

68

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 4. Working with the Platform Pack

Working with Database Security


In order to maximize your database security, you should change the passwords on all table owners created during the Platform Pack installation; these are created with the user and password equalling the same value. Such a user and password relationship could expose you to worms and viruses aimed at gaining access to your database. Consult with your DBA for advice on changing passwords to meet the security requirements of your database installation. The Installation Workbench assumes that the table owners password is the same as the table owner, unless it finds this override in the jde.ini file on the Deployment Server. Once the database passwords have been changed, you will need to add this section to the jde.ini file: [DSPWD] Datasource_owner=new_password For example, if you changed the passwords for PRODDTA and PRODCTL to alaska5 and nevada6 your section would look like this: [DSPWD] PRODDTA=alaska5 PRODCTL=nevada6 The Installation Workbench assumes that the database user is JDE and that the password is the same, unless it finds this override in the jde.ini file on the Deployment Server. As a security precaution, you should also change the password on the JDE user and add an override in the [DSPWD] section of the jde.ini file. Once the database passwords have been changed, you will need to add this section to the jde.ini file: [DSPWD] JDE=new_password For example, if you are changing the JDE user's password to apples, your section would look like this: [DSPWD] JDE=apples

Note
You must also logon to JDEPLAN using the changed password, otherwise database connections will fail. Using the above example of a changed password, you would logon using these credentials: User = JDE Password = apples Environment = JDEPLAN

Caution
The Installation Workbench can only process passwords equal to or less than 10 characters in length. Therefore, you cannot use passwords greater than 10 characters even if your RDMS allows it.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

69

Chapter 4. Working with the Platform Pack

After you change the [DSPWD] section of the jde.ini file, logon to OneWorld in the JDEPLAN environment on the Deployment Server with the new password in the correct case.

Warning
Whenever you change the password on your database, as recommended for security purposes, you must also ensure that your security settings in the Enterprise Server jde.ini file match that of your database. Refer to Working With Signon Security in this guide for applicable instructions. You should secure the jde.ini file on the Deployment Server to prevent unauthorized access. You should delete the [DSPWD] section once the install or upgrade is complete.

70

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner


This chapter discusses: Understanding Installation Planner Working with JD Edwards EnterpriseOne Software Requirements Reviewing Installation Planner Processing Options Working with a Typical Installation Plan Creating a Custom Installation Plan Deleting Machines from an Installation Plan

See Also A separate chapter in this guide entitled: Creating a Remote Installation Plan A separate chapter in this guide entitled: Adding a Server to an Existing Configuration A separate chapter in this guide entitled: Creating a Language-Only Installation Plan

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

71

Chapter 5. Working with Installation Planner

Understanding Installation Planner


Installation Planner is a Release 8.12 application that runs on the Deployment Server. It is a system administration tool to guide through the process of configuring the machines on which you will run Release 8.12. Installation Planner guides you through setting up: Language Information Location Information Deployment Server Information Enterprise Server Information JD Edwards EnterpriseOne HTML Web Server Information Data Source Information Environment Information

72

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Language Information
Installation Planner enables you to create a plan for installing an alternate language or multiple languages as you create your master plan. You should follow the system prompts to choose which languages will be installed for each environment. For initial installations, you can complete your master plan and install languages later by creating a languageonly plan. Refer to Creating a Language-Only Installation Plan for more information about setting up an alternate language after the master plan.

Location Information
Locations are user-defined groups of machines, databases, and environments. The use of multiple locations is recommended for configurations across a wide area network (WAN). Two types of locations exist: base locations and remote locations. Each installation plan can have only one base location. It is the central point for planning and executing the deployment process. The base location does not have a parent location and does not use a location code. You can have any number of tiered locations; each has a parent location and a location code. To set up locations for installation plans, you must provide the installation program with the location, location description, location code (if there is a secondary location), and parent location (if there is a secondary location). The location code is a three-character alphanumeric code that you specify. This location code is used as part of the name of the data sources for secondary locations in the plan. Locations are stored in the Deployment Locations Definition table (F9654). See Also Refer to Creating a Remote Installation Plan for information about setting up remote locations.

Deployment Server Information


To set up the plan information for the Deployment Server, you must provide the installation program with the machine name and the directory share name. This information populates the Release Master (F00945) and Path Code (F00942) tables, and stores additional Deployment Server information in the Machine Master (F9650) and Machine Detail (F9651) tables.

Enterprise Server Information


To set up the plan for the Enterprise Server, you must provide Installation Planner with the name of the Enterprise Server, its platform type, and the database it uses. Installation Planner populates the F9650 and F9651 Enterprise Server tables and defines the data sources for the Enterprise Server. The Data Source information is stored in the Data Source Master table (F98611). If you want to use cluster software, additional issues must be considered before installing Release 8.12. Refer to the section Release 8.12 on a Cluster in Server and Workstation Administration for more information before attempting the installation. The process also involves setting up multiple Server Map data sources for the Enterprise Server. This is required because Server Map data sources are specific to each Enterprise Server, so you must create one for each server.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

73

Chapter 5. Working with Installation Planner

JD Edwards EnterpriseOne HTML Web Server Information


To set up the plan for the JD Edwards EnterpriseOne HTML Web Server, you must provide Installation Planner with the name of the HTML Web Server machine, its platform type, and other information. Installation Planner populates the F9650 and F9651 Enterprise Server tables.

Warning
For Release 8.12, a JD Edwards EnterpriseOne HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because, unlike prior JD Edwards EnterpriseOne releases, the enduser applications are only accessible through a web interface.

Data Source Information


When you run Installation Planner, these data sources are set up once and shared across all environments: Server Map Server Map data sources are specific to each Enterprise Server, so you must create one for each server. Data Dictionary This is the data source for the Release 8.12 Data Dictionary tables. It is identified by the Release 8.12 release (for example, Data Dictionary - 812). Object Librarian This is the data source for the Object Librarian tables. It is identified by the Release 8.12 release (for example, Object Librarian - 812). System The data source for the System tables. It is identified by the Release 8.12 release (for example, System - 812). You must also set up these data sources for each environment: Control Tables This is the data source for the Control Tables. You can have multiples (for example, Control Tables - Prod, Control Tables - Test, and Control Tables - CRP). Central Objects The data source for the Central Objects specification tables is identified by the type and version number of the software. You can have multiple sets of Central Objects specifications (for example, Central Objects PD812, Central Objects - PS812, Central Objects - DV812, and Central Objects - PY812). However, you can have only one Central Objects data source for each path code. Business Data This is the data source for the Business Data tables. You can have multiple sets of Business Data data sources (for example, Business Data - CRP, Business Data - PROD, Business Data - TEST, and Business Data PS812). Versions

74

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

The data source for the Versions List table (F983051). You can have multiple sets of versions tables (for example, Versions - PD812, Versions - PS812, Versions - DV812, and Versions - PY812). However, you can have only one Versions data source for each path code. See Also Major Technical Tables for more information about individual tables and their uses

Environment Information
Installation Planner enables you to select default environments for your installation that are predefined, or you can choose to define them manually. Likewise, Installation Planner enables data load using default data load options, or you can choose to define them manually and override the default data load options.

Working with JD Edwards EnterpriseOne Software Requirements


The goal of the JD Edwards EnterpriseOne Release 8.12 Installation is to include the most current tools releases and updates at the time the CD is mastered. However, subsequent to that time it is possible that critical fixes may become necessary and available. You should check Customer Connection to verify if any such JD Edwards EnterpriseOne Release 8.12 Installation fixes are required.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

75

Chapter 5. Working with Installation Planner

Reviewing Installation Planner Processing Options


Processing options control how Installation Planner responds as you set up plans and options you see as you work through the custom planner. If processing options are not set up correctly, you will not see the appropriate options as you work through the planner. You set up these processing options to control replication functions and business functions mapping. You should review the default processing options for the Installation Planner application prerequisite to create the plan. First-time users can set up the processing options to step through the planner with informational messages. If you do not want to see these messages, you can turn them off.

Assumptions About Reviewing Installation Planner Processing Options


This table lists the assumptions about reviewing the processing options for the installation planner. Personnel Logon Status Prerequisites Concurrent Tasks Installer. On the Deployment Server, logged on as user JDE with the database password for user JDE, in the Planner environment. The Deployment Server must be installed. The Platform Pack installer can be running.

Accessing Processing Options


To access processing options, you must first log on to Release 8.12 and specify your installation plan type. 1. 2. 3. 4. Log on to Release 8.12 as user JDE with the database password for user JDE. Access the planner environment (JDEPLAN). From the System Installation Tools menu (GH961), right-click either Typical Installation Plan or Custom Installation Plan. Choose Prompt for Values. The Processing Options form appears.

76

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Choosing Processing Option Values


Once you have accessed processing options, perform the following tasks to choose the processing option values: Specifying the Prompt Mode Specifying the Process Mode Specifying the Default Mode Verifying Status Change Values Have Not Changed Specifying Plan Completion Processes Specifying Replication Options Specifying Remote Location Package Push Options

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

77

Chapter 5. Working with Installation Planner

Specifying the Prompt Mode


To specify the prompt mode: 1. Select the Prompt Mode tab.

2.

On the Prompt Mode tab, select a prompt mode: Value 0 1 2 Model Silent Additions Prompt Verbose Description Installation Planner displays only the data entry forms. Installation Planner prompts you to add servers. Installation Planner directs you through creating a plan with a series of prompting forms.

78

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Specifying the Process Mode


To specify the process mode: 1. Select the Process Mode tab.

2.

On the Process Mode tab, select the options for the processes that you want to run when you create your plan: Additional Servers Enter 1 to add servers to your existing setup (Deployment Server, Enterprise Server, Database Server, HTML Web Server). Enter 0 or leave blank for regular plans. Enter 1 to run the JD Edwards EnterpriseOne installation automatically.

Installation

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

79

Chapter 5. Working with Installation Planner

Specifying the Default Mode


To specify the default mode: 1. Select the Default Mode tab.

2.

On the Default Mode tab, enter these values into the processing option fields: Value 0 1 2 Description Do not use default values and do not prompt. Prompt for default options at run-time. Default mode. Always use defaults without prompting.

Default Data Source Information 80

Select whether you want the ability to modify data source information or just take the default values. GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Default Environments Default Data Load Default Advanced Parameters Default Languages Upgrade/Update Plan Generation

Select whether you want the ability to select environments or take the default values. Select whether you want the ability to modify data load parameters or take the default values. Select whether you want the ability to modify advanced parameters or take the default values. Select whether you want the ability to select an alternate language or take the default values. Select whether you want the ability to generate a plan automatically from locations and machines defined in a previous version of the software.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

81

Chapter 5. Working with Installation Planner

Verifying Status Change Values Have Not Changed


On the Status Change tab, this tab form appears.

Note
Do not make any changes on this tab. These values are hard coded in the application

82

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Specifying Plan Completion Processes


To specify plan completion processes: 1. Select the Completion tab.

2.

On the Completion tab, complete the fields using these values: After defining the plan, the options on this tab specify which processes are run. one of the following values: Value 0 1 2 Description Do not run automatically. Prompt to be run. Run automatically.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

83

Chapter 5. Working with Installation Planner

Finalize Plan Validate Plan

Enter the default option 2 to run automatically. Enter the default option 2 to run automatically.

84

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Specifying Replication Options


To specify replication options: 1. Select the Replication tab.

2.

On the Replication tab, complete the fields using these values: Value 0 1 2 Description Do not use and do not prompt. Prompt for option at run-time. Always use without prompting .

Replicate System Tables

Select whether you have the option to replicate system tables automatically for remote locations. GA.Rev8 1/7/2008 85

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Replicate Data Dictionary Tables Replicate Control Tables Replicate Constant Tables

Replicate Master Tables

Select whether you have the option to replicate data dictionary tables automatically for remote locations. Select whether you have the option to replicate control tables, menus, and user defined codes automatically for remote locations. Select whether you have the option to replicate constant tables automatically for remote locations. Business data tables are Object Librarian type 280. Select whether you have the option to replicate master tables automatically for remote locations. Business data tables are Object Librarian type 210 and 211.

86

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Specifying Remote Location Package Push Options


1. Select the Packages tab.

2.

On the Packages tab, enter one of the following values for the remote location package push option: Value 0 1 2 3 Description Do not push packages. Prompt for pushing at runtime. Do not prompt for pushing but display valid packages. Always push default packages without prompting.

3.

When you have chosen the options that you want, click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

87

Chapter 5. Working with Installation Planner

88

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Working with a Typical Installation Plan


This section discusses: Assumptions About Defining a Typical Installation Plan Starting Installation Planner Entering a Plan Description Entering Location Information Entering Deployment Server Information Entering Enterprise Server Information Entering HTML Web Server Information Selecting Default Environments Finalizing the Installation Plan

Assumptions About Defining a Typical Installation Plan


This table outlines assumptions for the Installation Planner phase. Personnel Logon Status Prerequisites Installer. On the Deployment Server, log on to Release 8.12 as user JDE in the JDEPLAN environment. Verify that the Deployment Server is installed and the correct Tools Release, Tools Release Patch, and Planner Update have been installed, in that order. The Platform Pack installation must be completed and you should verify that it completely installed the Pristine database and loaded the Pristine Central Objects. None.

Concurrent Tasks

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

89

Chapter 5. Working with Installation Planner

Starting Installation Planner


To start Installation Planner from within JD Edwards EnterpriseOne: 1. 2. 3. Access the System Installation Tools Menu (GH961). On the System Installation Tools menu, double-click Typical Installation Plan. On Work with Installation Plans, click Add. The Installation Planner form appears. 4. Enter a Plan description.

90

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Entering a Plan Description


To enter a plan description:

1.

On Installation Planner, complete these fields: Name Description Status Install Type To Release Enter the name of the installation plan. Enter the description of the installation plan. Choose 10 (the default value) as the status of the installation plan. Click the Install (the default value) radio button. Verify that the release number is E812 (default value).

2.

Click OK to continue.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

91

Chapter 5. Working with Installation Planner

Entering Location Information


A location groups related Deployment Servers for use in a multi-tier environment. To enter location information:

1.

On Location Revisions, complete these fields: Location Description Location Code Enter the location to which this plan applies; the location can be a city, company headquarters, or a division of the company. Enter a description for this location. If this is the base location, this field is only available when you are adding the base location. If you are editing an existing base location, the field is unavailable. If this is the base location, this field is only available when you are adding the base location. If you are editing an existing base location, the field is unavailable.

Parent Location

2.

Click OK.

92

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Entering Deployment Server Information


While Release 8.12 enables more than one Deployment Server to be defined, only the primary Deployment Server is defined at this time. You can choose a primary Deployment Server from the list of existing servers or you can enter information for a new server. To enter Deployment Server information:

1.

On Deployment Server Revisions, complete or verify these fields: Machine Usage Machine Name Description The value 15 appears by default, indicating that this is a Deployment Server. The name of the Deployment Server appears by default. Enter a long description for the machine. This description should include the location with which this Deployment Server is associated and whether or not it is the primary server. Enter the Release 8.12 release number you are installing or use the visual assist button to choose one from the list. The default value is E812. The value 50 appears by default, indicating that the server type is Intel NT. Your current location is the default value. The user to whom an email is sent when a package is deployed. The default value for primary user is listed in the JDE.INI.

Release Host Type Location Primary User

2.

On the Deployment tab, complete these fields: Primary Deployment Server The hierarchy of the servers. Valid values are: 1- Primary Deployment Server (default value)

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

93

Chapter 5. Working with Installation Planner

0 - Secondary Deployment Server The server share name of the directory to which you installed Release 8.12 on your Deployment Server. Verify that the server share name for Release 8.12 is \E812. 3. Click OK.

Tip
If you enter invalid information into a field on a tab, a stop sign symbol appears next to the tab name, such as Workstation. Click the stop sign icon in the bottom right of the form to see more info about the error. 4. 5. To add another Deployment Server, click Yes and repeat steps 1 through 3. To continue with Installation Planner setup, click No.

94

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Entering Enterprise Server Information


Note
During the definition of the Enterprise Server, a port number must be defined. While Enterprise Servers running the same release can use the same port number, an Enterprise Server running two different versions of software must use two different port numbers. To enter Enterprise Server information:

1.

On Enterprise Server Revisions, verify or complete these fields: Machine Name Description Release Host Type Location Primary User The name of the primary Enterprise Server. Enter a description for the machine. Enter the release number to which this plan applies, or use the visual assist button to choose one from the list. The default value is E812. Click the visual assist button and select the type of Enterprise Server you are adding to the plan. In this case, Intel NT. The location chosen for this plan appears by default. The user to whom an email is sent when a package is deployed. The default value for primary user is listed in the JDE.INI.

Note
The case of machine name must also match the network ID for that machine. 2. On Enterprise Server Revisions, select the Enterprise tab, and complete or verify these fields: GA.Rev8 1/7/2008 95

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Port Number Logical Machine Name Database Type Server Map Data Source

The port number value (6014) for this Enterprise Server as supplied from the JDE.INI. The Installation Planner detects and provides a default value based on the current machine name on which the program is running. Enter the value for your database: O - Oracle Whenever you enter a host type, the Installation Planner populates this field with a default value: machinename - 812 Server Map where machinename is the name of your machine. Verify that the default value is the installation directory path to which you want to install Release 8.12 on the Enterprise Server. Make sure the value is specific to your version of the release. For example, for Release 8.12 the path ends with \E812\ddp.

Installation Path

Caution
You must change the value that defaults into the Installation Path field as shown in the screen capture above. Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. A Deployment Server name appears in this field by default, but it can be changed if necessary.

Deployment Server Name

Note
If you change the port number to a value other than 6014, you must also change this setting in both the Enterprise Server and client JDE.INI. 3. Click OK.

96

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

4.

On Oracle Connect String, enter a valid value for your Oracle database installation.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

97

Chapter 5. Working with Installation Planner

Entering HTML Web Server Information


Note
For Release 8.12, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web Server. Functionally, these terms are all synonymous. However, this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software. To enter HTML Web Server information:

Warning
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface. 1. On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server.

98

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

2.

On HTML Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Location Primary User The default value of 30 indicates that this is a HTML Web Server. Enter the name of your HTML Web Server. The name is case sensitive and must not exceed 10 characters. Enter a description of the HTML Web Server machine. Enter E812 to indicate the release number that you are installing. The default value of 50 specifies the server type as Intel NT. Select the correct server type. The location chosen for this plan appears in this field by default. The user to whom an email is sent when a package is deployed. The default for primary user is listed in the JDE.INI.

3.

On the HTML tab, complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). This is the protocol used by the HTML Web Server. Valid values are http or https. This is the Domain Name System (DNS) host name of the HTML Web Server. For example: www.oracle.com This is the port number the HTML Web Server is listening to. For HTTP, the typical port number is 80.

Protocol Server URL

HTTP Port

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

99

Chapter 5. Working with Installation Planner

For HTTPS, the typical port number is 443.

Note
You can choose to implement a HTML Web Server using a different port number. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne. For JD Edwards EnterpriseOne Release 8.12, the value is 6014. Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. Redirector The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system. The user can specify an explicit servlet name in this field. In this case, the redirector functionality cannot be used. The URL generated will point to the specified servlet in the Primary HTML Web Server. Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need. The Portal servlet is: /jdedwards/servlet/com.jdedwards.portal.PortalBuilderServlet The HTML servlet is: /jdedwards/servlet/com.jdedwards.runtime.virtual.VCServlet Installation Path Enter the installation directory path to which you are installing Release 8.12 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running. For Release 8.12 on Oracle Applications Servers, the path ends with E1HTMLServer. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator. 4. 5. Click OK. To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web

JDENET Listen Port

Default Login

Explicit Servlet Name

100

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Server.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

101

Chapter 5. Working with Installation Planner

Selecting Default Environments


To select default environments: 1. On Environment Selection, ensure that these radio buttons are selected: 2. Default Environments Default Data Load

Select OK.

102

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Finalizing the Installation Plan


When the plan is finalized: The status is set to 20, signaling that several adjustments to OCM mappings and tables are made according to your plan. The system creates the OCM mappings and the JDE.INI. These tables are updated: Release Master table (F00945). Path Code Master table (F00942). Package Plan table (F98404). Machine Detail table (F9651). Language table (F984031), if you are installing a language.

To finalize the Installation Plan: 1. On the message box that indicates Installation Planner has concluded, click OK to exit the message box and initiate the Planner Validation Report. If the processing option default was selected, Planner Validation Report automatically prompts you to run this report. If the processing option default was not selected, click Validate on the tree view of your plan to initiate the Planner Validation Report.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

103

Chapter 5. Working with Installation Planner

Concluding the Planner Validation Report


To conclude the planner validation report: 1. 2. 3. On Report Output Destination, select On Screen or To Printer. Click OK. Review the report to confirm that all records were validated. For more information about Installation Planner Validation Report (R9840B), refer to Working with Reports. 4. On Work With Installation Plans, click Expand to review the plan you created.

See Also A separate chapter in this guide entitled: Creating a Remote Installation Plan A separate chapter in this guide entitled: Adding a Server to an Existing Configuration A separate chapter in this guide entitled: Creating a Language-Only Installation Plan

104

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Creating a Custom Installation Plan


This chapter includes the following processes for creating a custom installation plan: Understanding a Custom Installation Plan Starting Installation Planner Entering a Plan Description Entering Location Information Entering Deployment Server Information Entering Enterprise Server Information Enter Data Source Information for Server Map Entering HTML Web Server Information Entering Data Server Information Entering Shared Data Source Information Working with Environment Setup Adding a Remote Location Finalizing the Installation Plan

See Also A separate chapter in this guide entitled: Creating a Remote Installation Plan A separate chapter in this guide entitled: Adding a Server to an Existing Configuration A separate chapter in this guide entitled: Creating a Language-Only Installation Plan

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

105

Chapter 5. Working with Installation Planner

Understanding a Custom Installation Plan


Note
After installing the Deployment Server, you must define and run the installation plan. You must either define and run a Typical or a Custom Installation Plan -- do not do both. Within a custom installation plan, the information you provide on the Installation Planner forms, such as database type and Enterprise Server type, determines the information displayed on the remaining forms. The Installation Planner processing options also determine which choices are available while setting up your plan. For a complete description of the processing options, refer to Reviewing Installation Planner Processing Options . Data Source Considerations. JD Edwards EnterpriseOne configures your Release 8.12 data sources as completely as possible. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration.

106

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Starting Installation Planner


To start Installation Planner from within JD Edwards EnterpriseOne: 1. 2. 3. Access the System Installation Tools Menu (GH961). On the System Installation Tools menu, double-click Custom Installation Plan. On Work with Installation Plans, click Add. The Installation Planner form appears. 4. Enter a Plan description.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

107

Chapter 5. Working with Installation Planner

Entering a Plan Description


To enter a plan description:

1.

On Installation Planner, complete the following fields: Name Description Status Install Type To Release Include Languages Enter the name of the plan. Enter the description of the plan. Choose 10 (the default value). Click the Install (the default value) radio button. Verify that the release number is E812 (the default value). This is an optional selection that is only available if you have previously specified this Custom plan to install languages. Select yes if you are installing an alternate language.

Note
If you prefer, you can install an alternate language after you complete your master plan. To do so, select the Language Only option on this form. For more information, refer to Creating a Language-Only Installation Plan. 2. 3. Click OK. On Plan Generation, choose one of the following options:

108

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Note
The above screen may not always appear if you are rerunning the Planner, which is preferable because the recommended method is to step through the planner rather than taking defaults. See Caution below. 4. On this form, you have the option to automatically enter the locations and machines into the plan that you defined in the previous version of the software.

Choose a method for generating your plan: To manually create your plan, click OK and continue with Entering Location Information. To enable the system to automatically enter the locations and machines from the previous version, click Take Defaults. The machines that were imported from the previous system data source are entered into the current plan. Skip the sections on entering locations, Deployment Servers, Enterprise Servers, and machines/servers, and continue with Entering Shared Data Source Information.

Caution
In order to ensure the validity of all subsequent plan information, it is strongly recommended that even advanced users should not choose this Take Defaults option. Instead, you should step through plan and verify that the Planner is populating information exactly as you expect to match your requirements. To exit the plan, click Cancel.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

109

Chapter 5. Working with Installation Planner

Entering Location Information


A location groups related Deployment Servers for use in a multi-tier environment. To enter location information:

1.

On Location Revisions, complete these fields: Location Description Location Code Parent Location Enter the location to which this plan applies; the location can be a city, company headquarters, or a division of the company. Enter a description for this location. If this is the base location, this field will be grayed out. For the base location, this field will be grayed out.

2.

Click OK.

110

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Entering Deployment Server Information


While Release 8.12 enables more than one Deployment Server to be defined, only the primary Deployment Server is defined at this time. You can choose a primary Deployment Server from the list of existing servers or you can enter information for a new server. To enter Deployment Server information: 1. Click OK to add a Deployment Server.

2.

On Deployment Server Revisions, complete or verify these fields: Machine Usage Machine Name Description Displays the value 15 by default to indicate that this is a Deployment Server. The name of the Deployment Server appears by default. Enter a long description for the machine. This description should include the location with which this Deployment Server is associated and whether or not it is the primary server. Enter the release number you are installing or use the visual assist button to choose one from the list. The default value is E812. Displays the value 50 appears by default, indicating that the server type is Intel NT. Displays the current location. Displays the user to whom an email is sent when a package is deployed. The default value for primary user is JDE.

Release Host Type Location Primary User

3.

On the Deployment tab, complete these fields: Primary DeployEnter the hierarchy of the servers. Values are: GA.Rev8 1/7/2008 111

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

ment Server 1- Primary Deployment Server (default value) 0 - Secondary Deployment Server The server share name of the directory to which you installed Release 8.12 on your Deployment Server. Verify that the server share name for Release 8.12 is \E812. 4. Click OK.

Tip
If you enter invalid information into a tab field, a stop sign symbol appears next to the tab name, such as Deployment Server. For more information about the error, click the stop sign icon in the bottom right-hand corner of the form. 5. 6. To add another Deployment Server, click Yes and repeat steps 1 through 3. To continue with Installation Planner setup, click No.

112

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Entering Enterprise Server Information


Note
During the definition of the Enterprise Server, a port number must be defined. While Enterprise Servers running the same release can use the same port number, an Enterprise Server running two different versions of software must use two different port numbers. To enter Enterprise Server information:

1.

On Enterprise Server Revisions, verify or complete these fields: Machine Name Description Release Host Type Location Primary User The name of your primary Enterprise Server. Enter a description for the machine. Enter the release number to which this plan applies, or use the visual assist button to choose one from the list. The default value is E812. Click the visual assist button and choose the type of Enterprise Server you are adding to the plan. In this case, Intel NT. The location chosen for this plan appears by default. The user to whom an email is sent when a package is deployed. The default value GA.Rev8 1/7/2008 113

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

for primary user is JDE.

Note
The case of machine name must also match the network ID for that machine. 2. Continuing on Enterprise Server Revisions, select the Enterprise tab, and complete or verify these fields: Port Number Logical Machine Name Database Type Server Map Data Source The port number value (6014) for this Enterprise Server appears by default from the JDE.INI. The Installation Planner detects and provides a default value based on the current machine name on which the program is running. Enter the value for your database: O - Oracle Whenever you enter a host type, the Installation Planner populates this field with a default value: machinename - 812 Server Map where machinename is the name of your machine. Verify that the default value is the installation directory path to which you want to install Release 8.12 on your Enterprise Server. Make sure the value is specific to your version of the release. For example, for Release 8.12 the path ends with \E812\ddp.

Installation Path

Caution
You must change the value that defaults into the Installation Path field as shown in the screen capture above. Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. A Deployment Server name appears in this field by default, but it can be changed if necessary. Indicates the status of the server.

Deployment Server Name Server Status

Note
If you change the port number to a value other than 6014, you must also change this setting in both the Enterprise Server and workstation JDE.INI. 3. Click OK.

114

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Enter Data Source Information for Server Map


To enter information for the Server Map data source:

1.

On Data Source, click OK to continue entering unique data source information, or click Take Defaults to select the default data. If you select the default data, you can skip to Entering HTML Web Server Information.

2. 3.

On Data Source Revisions, verify the accuracy of the Server Map data source. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

115

Chapter 5. Working with Installation Planner

Entering HTML Web Server Information


Note
For Release 8.12, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web Server. Functionally, these terms are all synonymous. However, this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software.

Warning
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface. To enter HTML Web Server information:

1.

On HTML Application Server, click OK to define a new HTML Server, or click Select to choose from a list of existing HTML Servers.

116

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

If you choose Select, you are presented with the Machine Search table, from which you can make your selection.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

117

Chapter 5. Working with Installation Planner

2. 3.

On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server. On HTML Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Location Primary User The default value of 30 indicates that this is a HTML Web Server. Enter the name of your HTML Web Server. The name is case sensitive and must not exceed 10 characters. Enter a description of the HTML Web Server machine. Enter E812 to indicate the release number that you are installing. The default value of 50 specifies the server type as Intel NT. Select the correct server type. The location chosen for this plan appears in this field by default. The user to whom an email is sent when a package is deployed. The default for primary user is listed in the JDE.INI.

4.

On the HTML tab, complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). This is the protocol used by the HTML Web Server. Valid values are http or https. This is the Domain Name System (DNS) host name of the HTML Web Server. For example: www.oracle.com. This is the port number the HTML Web Server is listening to.

Protocol Server URL

HTTP Port

118

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

For HTTP, the typical port number is 80. For HTTPS, the typical port number is 443. However, you can choose to implement a HTML Web Server using a different port number. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne. For JD Edwards EnterpriseOne Release 8.12, the value is 6014. Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. Redirector The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system. Explicit The user can specify an explicit servlet name in this field. In this Servlet case, the redirector functionality cannot be used. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need. The Portal servlet is: /jdedwards/servlet/com.jdedwards.portal.PortalBuilderServlet

JDENET Listen Port

Default Login

The HTML servlet is: /jdedwards/servlet/com.jdedwards.runtime.virtual.VCServlet Installation Path Enter the installation directory path to which you are installing Release 8.12 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running. For Release 8.12 on Oracle Applications Servers, the path ends with E1HTMLServer. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator. 5. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

119

Chapter 5. Working with Installation Planner

6.

To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.

120

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Entering Data Server Information

1.

On Data Server, choose one of these options: OK If your database resides on a separate server, choose click OK to continue entering unique Data Server information. Select Click this option to select an existing Data Server. Skip Click this option if you do not want to define a Data Server. Continue with the Planner using the environment selection in step 6 of this task.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

121

Chapter 5. Working with Installation Planner

2.

On Data Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type The default value of 25 indicates that this is a Database Server. Enter the name of your Database Server. The name must not exceed 10 characters. Enter a description of the Database Server machine. Enter the release number you are installing, for example, E812. Select the type of Database Server that you are adding to the plan. Values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client - Microsoft Windows 90 Client - Microsoft Windows The Installation Planner populates this field by default, based on previous selections. The user to whom an email is sent once a package is deployed. The default for primary user is JDE.

Location Primary User 3.

On the Data tab, complete the following field: Data Source Type Choose the type of data source. For example: O - Oracle

122

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

4. 5. 6. 7.

Click OK. To add another Data Server, click Yes and repeat steps 1 through 4 to define another Data Server. On Data Source, click OK to continue entering unique shared data source information, or click Take Defaults to select the default data for the shared data sources. On Location, select Yes to add another location, or click No to continue with Installation Planner.

Entering Shared Data Source Information


This section discusses: Specifying (Custom or Default) Shared Data Source Setup Information Verifying the Data Source for Data Dictionary Verifying the Object Librarian Data Source Verifying the System Data Source

Specifying (Custom or Default) Shared Data Source Setup Information


When you are prompted to enter the data source information for the shared data sources, to use the Release 8.12 data sources, click Take Defaults, or click OK to specifically enter the data source information. See Also For more information about System data source fields or fields for other data sources mentioned in this process, refer to Understanding Data Source Charts. This sections discusses: Verifying the Data Source for Data Dictionary Verifying the Object Librarian Data Source Verifying the System Data Source

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

123

Chapter 5. Working with Installation Planner

Verifying the Data Source for Data Dictionary


To verify the data source for Data Dictionary:

1. 2.

On Data Source Revisions, verify the accuracy of the settings for the Data Dictionary data source. Click OK.

124

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Verifying the Object Librarian Data Source


To verify the Object Librarian data source:

1. 2.

On Data Source Revisions, verify the accuracy of the settings for the Object Librarian data source. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

125

Chapter 5. Working with Installation Planner

Verifying the System Data Source


To verify the System data source:

1. 2.

On Data Source Revisions, verify the accuracy of the settings for the System data source. Click OK. The Environment Selection screen appears.

126

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Working with Environment Setup


This section discusses: Understanding Environment Setup Setting Up Environments Working with Environment Data Sources

Understanding Environment Setup


By default, Installation Planner configures your system using values for typical environments. Depending on the options chosen when you set up your plan, Release 8.12 displays one or more of the following parameters, which you can customize in the following tasks: Environments Data load options Languages

You can customize any of these parameters by turning off the default option on the Environment Selection form. As you move through the plan, Installation Planner displays a customization form for each parameter that you clear.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

127

Chapter 5. Working with Installation Planner

Setting Up Environments
To set up environments:

1.

On Environment Selection, clear the options for the parameters that you want to customize.

Note
Different parameters appear depending on the options that you chose at the beginning of the planning process. 2. Click OK.

Note
If you selected the default option, which is to include all parameters, skip to Working with Environment Data Sources . Skip the tasks for those parameters that you did not clear.

128

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Adding a Custom Environment


To add a custom environment: 1. 2. 3. 4. 5. 6. 7. Click Add to add a new environment, or click Copy to copy the settings of an existing environment. Enter the environment information on the screen. Click Next. Choose share, or create a pathcode. Click Next. Enter pathcode information on the screen. Click Next.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

129

Chapter 5. Working with Installation Planner

Selecting an Environment
To select an environment:

1.

On Select Environments, double-click the environment that you want to define.

Note
J xxxxxx environments are required for the HTML Web Server. To set up multiple environments, select and define them one at a time.

130

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Specifying Environment Data Load Parameters


If you turned off Default Data Load on the Environment Selection form, the Data Load Parameters form appears.

Note
The data load radio buttons on this form are no longer applicable as of JD Edwards EnterpriseOne Release 8.12 because data is automatically loaded by the Platform Pack Installer. For additional details, refer to Loading Data (Demo Data and Production Data).

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

131

Chapter 5. Working with Installation Planner

Selecting Languages
To select languages:

1. 2. 3. 4.

On Language Selection, select the language you want to set up for the environment. From the Row menu, click Select. Repeat the above steps until all your languages have been selected. Click OK.

132

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Working with Environment Data Sources


This section discusses: Understanding Environment Data Sources Selecting an Environment Data Source Setup Option Setting Up the Data Source for Business Data Setting Up the Data Source for Central Objects Setting Up the Data Source for Control Tables Verifying the Data Dictionary Data Source Verifying the Data Source for Versions

Understanding Environment Data Sources


Once you have set up the environments, you must set up the data sources for those environments. If you created a custom environment, data source information is generated from the data source template provided by JD Edwards EnterpriseOne. See Also To modify this template, refer to the JD Edwards EnterpriseOne Tools 8.96 Configurable Network Computing Implementation Guide.

Selecting an Environment Data Source Setup Option


Installer Planner prompts you to set up data sources for the environment you just configured. To select an environment data source setup option: 1. Click OK to manually enter the data sources and continue with the following task, or click Take Defaults to accept the Release 8.12 default data sources.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

133

Chapter 5. Working with Installation Planner

Setting Up the Data Source for Business Data


To set up the data source for business data:

1. 2. 3.

On Data Source Revisions, verify the data source for your Business Data. From the Form menu, click Advanced. Click OK.

134

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Setting Up the Data Source for Central Objects


To set up the data source for central objects:

1. 2. 3.

On Data Source Revisions, verify the information for your central objects data source. Click OK. On Data Source Revisions, click the Advanced form option.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

135

Chapter 5. Working with Installation Planner

4.

On Advanced Set-Up, because the central objects data source must be Unicode, verify Unicode is checked. Also ensure that LOB is selected.

136

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Setting Up the Data Source for Control Tables


To setup the data source for control tables:

1.

On Data Source Revisions, verify the accuracy of the Control Tables data source. Data Source Name Server Name Object Owner ID Verify the name of the data source. Verify the name of the Enterprise Server. Enter the name of the owner of this object

Note
Control tables data sources are specific to the environment and pathcode. 2. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

137

Chapter 5. Working with Installation Planner

Verifying the Data Dictionary Data Source


To verify the data dictionary data source:

1. 2.

On Data Source Revisions, verify the accuracy of the data dictionary data source. Click OK.

138

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Verifying the Data Source for Versions


To verify the data source for versions:

1.

On Data Source Revisions, verify the accuracy of the versions data source.

Note
Versions data sources are specific to the pathcode, and the Unicode flag on the Advanced form must be selected. 2. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

139

Chapter 5. Working with Installation Planner

Adding a Remote Location


To add a remote location:

1.

Choose one of the following options: Click Yes to add a remote location.

Repeat all processes for adding a location starting with Entering Location Information. Refer to the Creating a Remote Installation Plan task in the Installation Planner Utilities section for information about adding remote locations to your plan. 2. Click No to conclude the Installation Plan setup.

Continue with Finalizing the Installation Plan task.

140

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Finalizing the Installation Plan


Installation Planner displays a message to let you know that the installation plan has been finalized. When the plan is finalized: The status is set to 20, which signals that several adjustments to tables were made according to your plan. The OCM is created. The JDE.INI is modified. The following tables are upgraded: Release Master table (F00945). Path Code Master table (F00942). Package Plan table (F98404). Machine Detail table (F9651). Language table (F984031), if you are installing an alternate language.

To finish the Installation Plan: 1. Click OK to exit the concluding message box and initiate the Planner Validation Report. If you selected the processing option default, the Planner Validation Report automatically prompts you to run this report. If you did not select the processing option default, click Validate on the tree view of your plan to initiate the Planner Validation Report.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

141

Chapter 5. Working with Installation Planner

Concluding the Validation Planner Report


To conclude the validation planner report: 1. 2. 3. On Report Output Destination, select On Screen or To Printer, and click OK. Review the report to confirm that all records were validated. After reviewing the report on the Batch Versions form, click Close. For more information about Installation Planner Validation Report (R9840B), refer to Working with Reports. 4. On Work with Installation Plans, click Expand to review the plan you created.

See Also A separate chapter in this guide entitled: Creating a Remote Installation Plan A separate chapter in this guide entitled: Adding a Server to an Existing Configuration A separate chapter in this guide entitled: Creating a Language-Only Installation Plan

142

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 5. Working with Installation Planner

Deleting Machines from an Installation Plan


As you work through the Installation Planner application, you might find that you need to delete a server or machine that you have created. You can use Installation Planner to delete machines as needed; however, doing so can affect related databases, shared Enterprise Servers and Deployment Servers, and associated records. To delete machines from an installation plan: 1. 2. 3. In the Release 8.12 planner environment, enter P9654A in the Fast Path field and press Enter. On Work With Locations and Machines, click Find. Expand the location. A list of your locations, machines, or servers appears for the base location in the tree view. 4. 5. 6. Select the location, machine, or server that you want to delete. Click Delete. To close the application, click Close.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

143

144

This page intentionally left blank

Chapter 6. Working With Installation Workbench


This section discusses: Understanding Workbench Components Working with Unattended Workbench Mode Starting Installation Workbench Working With Initial Tasks Workbench Configuring Your Locations Configuring Your Data Sources Configuring Your Environments Using Machine Workbench Using the Package Workbench Using the Package Workbench Using Remote Location Workbench Finishing Installation Workbench Updating Oracle Database Statistics

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

145

Chapter 6. Working With Installation Workbench

Understanding Workbench Components


After planning the Release 8.12 installation using Installation Planner, you should run the plan using Installation Workbench. The logic of this program runs specific workbench programs according to the plan you created. Installation Workbench can be run in attended mode or unattended mode. In attended mode, you start each workbench after the previous workbench completes. In unattended mode (the default value), each workbench runs without user intervention. You can set task breaks before or after any specific workbench to stop the process at any point. If using unattended mode, you must check that each task ran successfully. This section describes: Verifying the Network Share on the Deployment Server Loading Data (Demo Data and Production Data) Creating the Job Queue

As listed in this table, Installation Workbench includes the components, some or all of which might be used for yourinstallation, depending on your installation plan: Installation Workbench Compon- Functional Description ent Initial Tasks Workbench When using unattended workbench mode, this workbench runs Release Master after Installation Workbench is started and before Location Workbench begins. This workbench copies all locations that are defined in the plan from the F9654 and F984021 tables in the Planner data source to the System - 812 data source. Copies all data sources that are defined in the plan from the F98611 and F986115 tables in the Planner data source to your System - 812 data source. It also updates the F98401 table to indicate completion. Copies the F0094, F00941, and F00942 tables, as well as the F986101 table for each environment, from your Planner data source to your System 812 data source. It then updates the F98403 table to indicate completion. Depending on the plan settings, it also runs a batch application to copy new generic text and to create and populate Object Management Workbench and version tables. Copies the F9650 and F9651 tables from the Planner data source to the System - 812 data source. It then updates the F98402 table to indicate completion and uses the environment information to populate the F986101 and F98611 tables in the Server Map data source. Only valid environments, data sources, and server map tables are created. Copies the language text from the MSDE database that contains the language text into the control table database and central object database. This workbench runs only for users who are adding an alternate language to their installations. Transfers the F9603 and F9631 tables from the Planner data source to the System - 812 data source. It then updates the F98404 table to indicate completion.

Location Workbench

Data Source Workbench

Environment Workbench

Machine Workbench

Control Table Workbench

Package Workbench

146

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

See Also Major Technical Tables in this guide for more information about individual tables and their uses.

Verifying the Network Share on the Deployment Server


When you created the plan, this network share was created: \\depsvrname\E812 where depsvrname is the name of your Deployment Server. Because several of the Workbenches update files through the network share, these workbenches will fail if the share is not writeable. Sometimes the security settings on your deployment server will prevent the Planner from creating the share as a writeable share. Use this procedure to ensure that the share is writeable before proceeding: 1. 2. 3. 4. 5. 6. On the Deployment Server, navigate to Start | My Computer | Manage Open Shared Folders. Open Shares. Right click on E812 and select Properties and then Share Permissions. Select properties then select Share Permissions Make sure that Everyone is set to Full Control, Change, Read permissions.

Note
Even after the Workbenches are complete, you will still need these settings on the Deployment Server's share in order to successfully perform client installs.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

147

Chapter 6. Working With Installation Workbench

Loading Data (Demo Data and Production Data)


While previous versions of JD Edwards EnterpriseOne used Workbench components to load data, for Release 8.12 the Platform Pack Installer loads appropriate data into specific environments as follows: Demo data to Development and Pristine environments. Production data to Production and Prototype environments.

To load demo data in Production or Prototype environments, you must run a UBE (R98403E) to copy the data to those environments.

Note
The "from" (source) environment can be the Planner environment or your Pristine environment.

Caution
You should not change the record selection on this UBE. 1. Run R98403E using the XJDE0009 version and set the processing options as follows:

148

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

2.

On Processing Options 1-4, complete these fields: Option 1 Option 2 Option 3 Enter the name of the source environment, which is the environment of the table to be copied. For example, JDEPLAN. This field must be blank because this UBE is used to copy a mixture of business data and control tables which are specified to environments, not data sources. Enter the name of the target environment, which is the environment to which you wish to copy the table. In this case, you would specify either the Production or Prototype environments. For example, PD812. This field must be blank because this UBE is used to copy a mixture of business data and control tables which are specified to environments, not data sources.

Option 4

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

149

Chapter 6. Working With Installation Workbench

3.

Click OK to continue specifying processing options.

4.

On Processing Options 5-9, complete these fields: Option 5 The recommended value is 1, which copies the table. The default value is 0, Proof Mode. The recommended value is N, which copies tables only if they exist in the source. Enter Y to copy tables whether or not they exist in the source data source.

Option 6

150

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

Option 7

The default value is N. The recommended value is Y, which recreates tables that already exist in the target data source.

Note
If you do not recreate the tables, you will end up with a mixture of production and demo data in the tables. The default value is N. The recommended value is N, which forces a copy of the data, ignoring the CPYD flag.

Option 8

Note
A value of Y will leave almost all tables empty. That is, a production data load. The default value is N. The recommended value is N, which creates the indexes on the tables before copying the data. This prevents duplicate rows.

Option 9

Note
A value of Y copies the data and then create the indexes. The default value is N. 5. Click OK to accept the values and start the UBE.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

151

Chapter 6. Working With Installation Workbench

Creating the Job Queue


You may set up the job queues before running the Installation Workbench. If you do not, Initial Tasks Workbench will create a default entry for QBATCH with a setting of maximum=4.

Note
If running an Install, you can set up the queues at any stage before running a Package Build. If you set up queues after the Installation Workbench, sign onto DEP812. To create the job queue: 1. 2. Enter GH9013 in the Fast Path field and start the Job Queues program (P986130). Click Add.

3.

On Job Queue Revisions, add a queue by completing these fields: Host Job Queue Default Queue Job Queue Status Queue Type Maximum Batch Jobs Port Number Enter the Enterprise Server name. Enter the job queue name. Turn on this option by clicking the check box. Enter 01. Enter 01. Enter a value that equals the number of processors on the Enterprise Server machine. Enter 6014. If you receive a Network Failed error, you can safely ignore it in this

152

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

case. 4. Add another queue called I-ACTIVE.

5.

On Job Queue Revisions, add a queue by completing these fields: Host Job Queue Default Queue Job Queue Status Queue Type Maximum Batch Jobs Port Number Enter the Enterprise Server name. Enter the Job Queue name: I-ACTIVE. Turn off this option by clicking the radio button. Enter 01. Enter 01. Enter a value that equals the number of processors on the Enterprise Server machine. Enter 6014.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

153

Chapter 6. Working With Installation Workbench

Working with Unattended Workbench Mode


This section discusses: Selecting Attended or Unattended Workbench Mode Setting a Task Break in Unattended Workbench Mode

Selecting Attended or Unattended Workbench Mode


The workbenches can be run manually (attended workbench mode) or automatically (unattended workbench mode). When running Workbench in unattended mode, start Installation Workbench as described below, and then the status of each workbench is displayed as the workbench begins. Unattended workbench is the default value. In unattended workbench, if an error is encountered in any of the individual workbenches, the process stops. After fixing the error, unattended workbench resumes where it left off. To choose attended workbench mode: 1. 2. 3. Open the System Installation Tools menu (GH961). Right-click on Installation Workbench. Select Prompt For and then Values. The Processing Options form appears. 4. In the appropriate field, enter 1 for unattended workbench mode or 0 (zero) for attended workbench mode. The default value is 1 (unattended). 5. Click OK. Work with Installation Plan appears.

Setting a Task Break in Unattended Workbench Mode


In unattended workbench, you can set task breaks before or after any of the individual workbenches. You can use the task break to verify successful completion of a workbench or for other tasks. For example, set a task break after Table Conversion Workbench to verify that all table conversions completed successfully. An automatic task break occurs after Control Table Workbench, preceding Table Conversion Workbench. To set a task break in unattended workbench mode: 1. 2. 3. Open the System Installation Tools menu (GH961). Select Advanced Operations. Double-click Work with Task Breaks. The Work with Task Breaks form appears.

154

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

4.

Click Find. A list of the workbenches appears.

5.

To set a break before or after a workbench, choose the workbench name, and, on the Row menu, select Break Before or Break After. You can clear task breaks on the Row menu.

6.

On Task Break Revisions, specify the following fields: email Address (optional) Task Break Task Break Short Text (required) Optional Detail (optional) Specify (or choose from a list) the address book number of the person who is to be notified when the task break occurs. Specify (blank) for no task break or 2 for a customer task break. If the field is left blank, then no task break is configured. Enter a short text description of the task break. Enter detailed information about the task break.

7.

Click OK. Task Break Revisions closes, and Work with Task Breaks reappears. Specify any further task breaks.

8.

Click Close.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

155

Chapter 6. Working With Installation Workbench

Starting Installation Workbench


Caution
Do not lock the Deployment Server during Installation Workbench processes (for example, with a screen saver password); doing so pauses some processes. Do not run Installation Workbench from a remote access program that simulates a local connection. To start the Installation Workbench: 1. 2. On your Deployment Server, log in to the Planner environment, which is JDEPLAN. From the System Installation Tools menu (GH961), choose Installation Workbench. When this application is run the first time, the system downloads all required objects using Just In Time Installation (JITI).

If you specified attended workbench mode, use the following procedures, including the Initial Tasks Workbench, to complete the workbenches. If you specified unattended workbench mode, the process begins and all workbenches are completed automatically, unless task breaks are set. If you did not set any task breaks, continue with Working With the Enterprise Server.

3.

On Work with Installation Plan, double-click your plan.

156

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

Working With Initial Tasks Workbench


Before the workbench is run, the F00945 table in the System data source is blank because it is no longer populated when a plan is validated. However, after you run the Initial Task Workbench several tables in the System data source are populated including the F00945 table. The Initial Tasks Workbench form lets you complete the Release Master task before the individual workbenches begin. You use this procedure if you are running Workbench in attended mode or if you set a task break before Initial Tasks Workbench.

Changing the Status of Initial Tasks Workbench


You use this procedure if you are running Workbench in attended mode or if you set a task break before Initial Tasks Workbench. To change the status of Initial Tasks Workbench:

You might want to change the status of one or more of the initial workbench tasks. To change the status of a task, use the following procedure. 1. 2. Enter GH961 in the Fast Path field to open the System Installation Tools menu. Double-click Custom Installation Plan.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

157

Chapter 6. Working With Installation Workbench

3. 4.

On Work with Installation Plans, select your installation plan. Select Expand on the Row menu. The plan components, including the initial tasks, appear.

5. 6.

Select the task whose status you want to change. On the Row menu, click Disable, Enable, or Complete (see the table below). The task status changes. Row Menu Option Disable Enable Complete Meaning Displays status of 70 to indicate the task is incomplete, and will not be rerun. Displays status of 10 to incidcate the task will be rerun. Displays status of 60 to indicate the task is complete, and will not be rerun.

158

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

Configuring Your Locations


Location Workbench copies all locations that are defined in the plan from the F9654 table in the Planner data source to the System - 812 data source. It also updates the F984021 table. Use this procedure when running Workbench in attended mode or if you set a task break before Location Workbench.

1. 2.

On Location Workbench, verify that all of your locations are listed. Select Configure from the Form menu. Locations are configured, and the Data Source Workbench form appears. The system updates the Detail Status to 60 and changes the Status Description from Validated to Installed.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

159

Chapter 6. Working With Installation Workbench

Configuring Your Data Sources


Data Source Workbench copies all data sources that are defined in the plan from the F98611 table and the F986115 table in your Planner data source to your System - 812 data source. It also updates the F98401 table to indicate completion. Use this procedure when running Workbench in attended mode or if you set a task break before Data Source Workbench. 1. On Data Source Workbench, verify that all of your data sources are listed as illustrated in this example.

2.

Select Configure from the Form menu. Your data sources are configured, and the Environment Workbench form appears. When the system has configured your data sources, it updates Detail Status to 60 and changes the Status Description from Validated to Installed.

160

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

Configuring Your Environments


Environment Workbench copies the F0094, F00941, and F00942 tables, as well as the F986101 table for each environment, from your Planner data source to your System - 812 data source. It then updates the F98403 table to indicate completion. Depending on the plan settings, it also runs a batch application to copy new generic text and to create and populate Object Management Workbench and version tables. Environment Workbench can run multiple batch applications simultaneously, which enables Release 8.12 to load multiple environments at the same time. This reduces the amount of time it takes to load environments. Use this procedure when running Workbench in attended mode or if a task break is set before Environment Workbench.

1. 2. 3. 4.

On Environment Workbench, review each environment and its associated parameters to make sure the values are correct. After you review the environments, select Configure. When Environment Workbench has completed, verify that the status of each environment has been updated to 60 and that the status description has changed from Validated to Installed. Using Adobe Acrobat, review all XJDE reports, and confirm that all configuration statuses indicate Success.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

161

Chapter 6. Working With Installation Workbench

Using Machine Workbench


Machine Workbench copies the F9650 and F9651 table from the Planner data source to the System - 812 data source. It then updates the F98402 table to indicate completion and uses the environment information to populate the F986101 and F98611 tables in the Server Map data source.

Note
Only valid environments, data sources, and server map tables are created. You use this procedure when running Workbench in attended mode, or if a task break is set before Machine Workbench.

1. 2.

On Machine Workbench, review each server and its associated parameters for the correct values. Select Configure from the Form menu. When the system has configured your servers, it changes the detail status to 60, and Status Description changes from Validated to Installed.

162

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

Using the Package Workbench


Package Workbench transfers the F9603 and F9631 tables from the Planner data source to the System - 812 data source. It then updates the 98404 table to indicate completion. Use this procedure when running Workbench in attended mode or if a task break is set before Package Workbench. Refer to the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for complete information about building and configuring packages.

1. 2.

On Package Workbench, review your packages. Select Configure from the Form menu.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

163

Chapter 6. Working With Installation Workbench

Using Remote Location Workbench


Note
This workbench only appears when Remote Locations have been set up. Remote Location Workbench loads business (master and constant), control, data dictionary, and system tables from base location to remote location servers, by launching different versions of R98403 (XJDE0043, XJDE0044, XJDE0045, XJDE0046 and XJDE0047). It also pushes delivered packages to primary Deployment Servers at remote locations by launching the multi-tier UBE (R98825C). This workbench is processed only if you opted to install remote locations and chose to load replicated data and push packages. Use this procedure when running Workbench in attended mode or if a task break is set before Remote Location Workbench.

164

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 6. Working With Installation Workbench

Configuring Remote Locations


To configure remote locations:

To configure your remote locations: 1. 2. 3. On Remote Location Workbench, Release 8.12 displays all remote location activities in the detail area. On the Form menu, select Configure to launch the workbench. After all remote location activities are complete, click Next.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

165

Chapter 6. Working With Installation Workbench

Finishing Installation Workbench


To finish the Installation Workbench: 1. 2. From Congratulations, on the Form menu, click Finish. From Work with Installation Plans, click Close.

Note
Post Install Procedures still need to be completed from a client. See Performing Post Installation Tasks.

Updating Oracle Database Statistics


You should update database statistics after loading a significant amount of data to your database. Without this step, the database will not use any of the indexes when accessing the data. Depending on the size of your tables, updating statistics may take a while. To update Oracle database statistics: 1. 2. Start SQL Plus and connect to the instance as SYS or SYSTEM. For each data owner enter this command: execute dbms_utility.analyze_schema (' owner','compute'); where owner is the data owner name in the command. For example, PRODDTA, or DD812.

166

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 7. Working With Data Configuration Workbench


Data Configuration Workbench (P01RS001) is an application that runs on the Deployment Server that you must run after the Installation Workbench as a post-install process. When you run Data Configuration Workbench, the system configures system and control tables based on the parameters that you enter in the application.

Note
Terminology. The contents of this chapter are based on the JD Edwards EnterpriseOne recommendations and guidelines for developing a configuration solution for a rapid software implementation. These configuration solutions, originally called Rapid Start, are called Oracle Business Accelerators for JD Edwards EnterpriseOne. Business Accelerators provide the same features and functionality as Rapid Start and now align with other Oracle software offerings of the same name. Some older content will still refer to the Rapid Start name.

Important
Starting with JD Edwards EnterpriseOne Release 8.12, Business Accelerator configurations are delivered as par (portable archive) files. As a result, you must run Data Configuration Workbench in nonRapid Start mode regardless of whether you are a Business Accelerator customer. For details on the installation of Business Accelerator configurations refer to this web site on the Update Center: http://www.peoplesoft.com/corp/en/update_fix/kgwrapper.jsp?app=uc For an overview of Business Accelerator Configurations and Configuration Packages, on the above page refer to the link entitled Loading Business Accelerator Configurations. The URL for that link is: http://maintenance.peoplesoft.com/softwaredownloads/RSData/content/documents/overview%20of%20bu siness%20accelerator%20configurations%20and%20configuration%20packages.doc Understanding Data Configuration Workbench Adding a Data Configuration Plan Running a Data Configuration Plan Troubleshooting Data Configuration Workbench Installation

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

167

Chapter 7. Working With Data Configuration Workbench

Understanding Data Configuration Workbench


If you have not purchased a Business Accelerator solution, the system configures data for a standard implementation when you run Data Configuration Workbench. If you have purchased Business Accelerator, for implementation details you should refer to the web sites list in Important at the beginning of this chapter. This section discusses: Data Configuration Process Components and Tables that are Updated by Data Configuration Workbench

Data Configuration Process


The first step of the data configuration process is to add a data configuration plan that defines how the system configures data. The system stores the information in the Rapid Start - Install Parameters (F01RS001) and Rapid Start - Path Code/Environment Detail (F01RS002) tables. After you add the data configuration plan, then you run the data configuration plan. You can run the data configuration plan in proof mode and final mode. When you run the data configuration plan in proof mode, the system: 1. 2. Submits the Data Configuration Loader program (R01RS001). Generates a PDF that lists the number of business data records that will be updated in each of the affected tables as well as what system, version/central objects, and control tables will be updated when you run the application in final mode.

When you run the data configuration plan in final mode, the system: 1. 2. 3. 4. 5. Submits the Data Configuration Loader program. Replaces business data. Updates system, version/central objects, and control tables. Generates a PDF that lists the number of records updated in the affected tables. Locks the grid area of the Data Configuration Pathcode/Environment Details form, preventing you from making revisions to the environments that are selected for that data configuration plan.

The system stores the information listed on the PDF in the Rapid Start Reporting Workfile table (F01RS010).

Note
To modify the F01RS001, F01RS002, and F01RS010 tables, use only Data Configuration Workbench. The system also enables you to revise data configuration plans and to rerun data configuration plans if errors and mistakes are encountered during the data configuration process.

168

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 7. Working With Data Configuration Workbench

Components and Tables that are Updated by Data Configuration Workbench


This table lists the components and associated tables that Data Configuration Workbench updates when you run the data configuration plan in final mode: Components Business Data Tables Updated Examples of business data tables that the system updates include: Control Tables System Tables Library Lists - User (F0092) Security Workbench (F00950) User Display Preferences (F00921) User Access Definition (F00925) Anonymous User Access Table (F00926) Library List Control (F0093) Role Relationships Table (F95921) User Display Preferences Tag File (F00922) User Install Packages (F00924) E1 Users PIM Information (F00927) One World Security (F98OWSEC) Task Master (F9000) Task Relationships (F9001) Variant (F9005) Variant Description Alternate Description (F9005D) Variant Detail (F9006) Variant Detail Alternate Description (F9006D) Business Unit Master (F0006) Date Fiscal Patterns (F0008) Company Constants (F0010) Account Master (F0901)

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

169

Chapter 7. Working With Data Configuration Workbench

Components Versions

Tables Updated

Versions List (F983051) Versions Tag Table (F983052) Event Rules - Link Table (F98740) Event Rules - Specification Table (F98741) Report Design Aid Text Information (F98760) Report Design Aid Specification Info (F98761)

If you have previously or inadvertently loaded the Data Configuration Workbench in Rapid Start mode (that is, the Install Rapid Start Data? field was set to Yes as shown in the section entitled: Adding a Data Configuration Plan), you can get a complete listing of the business data tables that the system updates as well as the specific values with which the system updates each of the tables. Refer to Appendix E: Business Data Reports for your region in the JD Edwards EnterpriseOne Configuration Methodology 8.12 Guide.

170

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 7. Working With Data Configuration Workbench

Adding a Data Configuration Plan


You must add a data configuration plan after you have completed the installation workbench. To add a data configuration plan:

1. 2. 3.

On the deployment server, log into the JDEPLAN environment as user JDE. From the System Installation Tools menu (GH961), select Data Configuration - Installs Only. On Data Configuration Workbench, click Add.

4.

On Data Configuration Pathcode/Environment Details, complete these fields: Enter the Data Configuration Plan Name Install Rapid Start Data? Enter an alphanumeric user-defined plan name identifiying the plan. Enter N regardless of whether you have purchased a Rapid Start solution.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

171

Chapter 7. Working With Data Configuration Workbench

Note
Starting with JD Edwards EnterpriseOne Release 8.12, Business Accelerator configurations are delivered as .par (portable archive) files. As a result, you must run Data Configuration Workbench in non-Rapid Start mode regardless of whether you are an Oracle Business Accelerator for JD Edwards EnterpriseOne customer. If you have purchased a Business Accelerator configuration, for implementation details you should refer to to the web sites list in Important at the beginning of this chapter. 5. Click OK.

Running a Data Configuration Plan


To run a data configuration plan: 1. 2. 3. On the deployment server, log into the JDEPLAN environment as user JDE. From the System Installation Tools menu (GH961), select Data Configuration - Installs Only. Highlight your data configuration plan and then select Submit PROOF or Submit FINAL from the Row menu.

172

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 7. Working With Data Configuration Workbench

4.

If you select Submit FINAL, click OK on Submit Data Configuration.

The system submits the Data Configuration Loader program and generates a PDF that displays the updates that will occur if you submitted in proof or the updates that did occur if you submitted in final.

Note
The Submit Data Configuration form only displays if you set the Data Configuration Workbench in Rapid Start mode (that is, you set the Install Rapid Start Data? field to Yes).

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

173

Chapter 7. Working With Data Configuration Workbench

Troubleshooting Data Configuration Workbench Installation


This table lists potential error conditions for Data Configuration Workbench and their probable resolutions: Error Message Unable to attach Database Check network connections. If the database in error is an MSDE database, verify that its location is correct. Verify that the database is not already attached. If it is, manually detach it before running Data Configuration Workbench. If the database in question was created by the installation process, verify the environment, path code, and so on. Resolution

Datasource cannot be created Check network connections. If the database in error is an MSDE database, verify that its location is correct. Verify that the Business Data Local data source exists in the Datasource Master table (F98611) before rerunning Data Configuration Workbench. If the database in question was created by the installation process, verify the environment, path code, and so on.

Table does not exist Error opening table 174 Check network connections. If the database in error is an MSDE database, verify that its location is correct. If the database in question was created by the installation process, verify the environment, path code, and so on. Use UTB to verify that the table exists or not. GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved. Check network connections. If the database in error is an MSDE database, verify that its location is correct. If the database in question was created by the installation process, verify the environment, path code, and so on. Use UTB to verify that the table exists.

Chapter 7. Working With Data Configuration Workbench

Error Message Error reading table

Resolution

Check network connections. If the database in error is an MSDE database, verify that its location is correct. If the database in question was created by the installation process, verify the environment, path code, and so on. Use UTB to verify that the table exists. In UTB, click Find and check for any errors.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

175

176

This page intentionally left blank

Chapter 8. Working With the Enterprise Server


This chapter contains these sections: Verifying the Release 8.12 Enterprise Server Installation Using PORTTEST Starting Network Services on the Enterprise Server Stopping Network Services on the Enterprise Server Working with OCM Generation Setting Up a Printer on the Enterprise Server

Verifying the Release 8.12 Enterprise Server Installation Using PORTTEST


Note
When running PORTTEST after installing the Enterprise Server, the test returns a failure message. This is because it is not able to access the F0902 table at this time, (the format of the F0902 table changes during the Table Conversion Workbench). Ignore any errors relating to accessing the F0902 table, (for example, Select all on table F0902 failed - rcode=0). Once the Workbench tasks are all complete, and the Enterprise Server is configured, rerun PORTTEST. The basic PORTTEST procedure ensures connectivity. Refer to Using the PORTTEST Checklist for additional details including the PORTTEST checklist.

Tip
Cluster Software Considerations. If using cluster software, skip this step. Before you attempt to start Release 8.12, complete the steps in the Microsoft Windows Cluster chapter of Release 8.12 on a Cluster in JD Edwards EnterpriseOne Tools 8.96 Server and Workstation Administration Guide. The PORTTEST program initializes a user and an environment (assuming that Release 8.12 is installed and configured correctly). To verify that Release 8.12 is installed correctly, you must run the PORTTEST program for each environment. To verify the Enterprise Server installation using PORTTEST: 1. 2. 3. Log on to the Enterprise Server as JDE. Open a DOS command window. To verify that Release 8.12 is installed correctly on the Enterprise Server, enter these commands: d: [or the appropriate drive letter] cd \JDEdwards\E812\ddp\System\bin32

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

177

Chapter 8. Working With the Enterprise Server

PORTTEST userid password environment where userid is a valid Release 8.12 user, password is the password for that user, and environment is the environment you are verifying. These parameters are case-sensitive. Enter the PORTTEST command for each environment.

Tip
Troubleshooting. The program should display messages indicating the selection of records from an Release 8.12 table. If it does not, review the jde_###.log that was specified in the JDE.INI on the Enterprise Server. If PORTTEST fails to run, see Using the PORTTEST Checklist for diagnostic assistance.

Starting Network Services on the Enterprise Server


After you install the JD Edwards EnterpriseOne Platform Pack on the Microsoft Windows Enterprise Server, you must start the Network Services. To start the network services on the Enterprise Server: 1. 2. From Control Panel, access Services. Locate and highlight this service: JDE E812 3. Click Start.

Stopping Network Services on the Enterprise Server


To stop the network services on the Enterprise Server: 1. 2. 3. From Control Panel, access Services. Locate and highlight every service that is prefixed with the word JDE (JD Edwards EnterpriseOne releases prior to 8.9 and after 8.11) or PeopleSoft (releases 8.9, 8.10, and 8.11). Click Stop.

Note
When you stop JD Edwards EnterpriseOne network services on a Microsoft Windows server, some processes might not stop. To stop the services completely, you should either shutdown and restart your Enterprise Server or complete the remaining steps in this procedure. 4. 5. On the Enterprise Server, go to Task Manager and right-click any JD Edwards EnterpriseOne process that is still running. Select Debug.

178

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 8. Working With the Enterprise Server

This command takes you to debug mode in Microsoft Visual C++. 6. Stop the debug process and exit Visual C++. The JD Edwards EnterpriseOne process that you selected shuts down. Repeat this process for each JD Edwards EnterpriseOne process that is running.

Working with OCM Generation


This section discusses: Understanding OCM Mappings Understanding Data Source Setup Understanding OCM Creation Understanding OCM Customization

Understanding OCM Mappings


JD Edwards EnterpriseOne does not ship Object Configuration Manager (OCM) records for standard environments in Release 8.12. They are generated when you finalize an installation plan. OCM is created based on the Data Class for data sources and for a table or GT object. The Data Class is stored on the Data Sources By Environment (F98511), Data Source Master (F98611) and Object Librarian Master (F9860) tables.

Understanding Data Source Setup


Before OCM can be created, you must configure your data sources. Data source configuration and prompting is driven by the data in the F98511 table. The first set of data sources to be configured is the Enterprise Server data sources. This includes the Server Map data source. Also, logic data sources are automatically configured without prompting. OCM records are not created for the server map data source. UBE, BSFN, RTE, and XAPI mappings are created for the logic data sources. The next set of data sources to be configured is the shared data sources. This includes System, Data Dictionary, and Object Librarian data sources. The first time these data sources are configured, the shared data source template (F98511.SPLL = *SHARED) is copied and tokens are replaced in the data source name and properties to create the shared data source records (F98511.SPLL = DEFAULT). These defaults are then used to create the data source definition in the F98611 table. If record in the F98611 tables already exists, the defaults from the F98511 table are overridden by the current definition. The user is then optionally prompted to customize the data source. The last set of data sources is the environment data sources. A set of data sources is configured for each environment. This includes Business Data, Control Tables, Central Objects and Versions. The environment data source template (F98511.SPLL = *ENV) stores defaults for environment data sources. As data sources are configured for an environment, these records are copied and tokens are replaced in the data source name and properties to create records for the environment (F98511.SPLL = Environment Name). These defaults are then used to create the data source definition in the F98611 table. If records in the F98611 table already exists, the defaults from the F98511 table are overridden by the current definition. The user is then Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 179

Chapter 8. Working With the Enterprise Server

optionally prompted to customize the data source. Given that the standard environments do not always follow the defaults that are specified in the *ENV template, JD Edwards EnterpriseOne provides preconfigured records for the standard environments. Thus, the *ENV template is only used for custom environments.

Understanding OCM Creation


After your data sources have been defined and the plan is complete, the plan is finalized. OCM is created during finalization. This section describes: Understanding Database Data Sources Understanding Logic Data Sources

Understanding Database Data Sources


The process finds the data class for each table or GT object in Object Librarian (F9860.SICLDF). Based on the environment that is being configured and the data class for the object, the data source name is fetched from F98511. If a record is not found, it looks for a record for the data class where environment name is DEFAULT (to determine whether it should be mapped to a shared data source). If a record is not found, no mapping is created and the table is effectively mapped to the default data source. If a record is found and that record is set as the default mapping data source (F98511.SPDFLTMAP), a mapping with object name DEFAULT is created; otherwise the actual object name is used. Mappings are not created for tables in the Planner and Internal data classes.

Understanding Logic Data Sources


The OCM generation algorithm for UBEs and BSFNs are identical to each other, but the output depends on whether the default mapping is LOCAL or an Enterprise Server. The following table shows the default mappings for UBE and BSFN objects. Base Environment DV812, PS812, PD812, PY812 UBE BSFN The algorithm is: If the default is LOCAL, a default mapping to LOCAL is created. Server mappings are created for any object whose Location (labeled Business Function Location for BSFNs and Process Location for UBEs) in Object Management Workbench (OMW) is Server Only (F9860.SIBFLOCN = 3). If the default is Enterprise Server, a default mapping to the Enterprise Server is created. LOCAL mappings are created for any object whose Location (labeled Business Function Location for BSFNs and Process Location for UBEs) in OMW is Client Only (F9860.SIBFLOCN = 1). Enterprise Server LOCAL HTML Web Server Environment JDV812, JPS812, JPD812, JPY812 Enterprise Server Enterprise Server

Understanding OCM Customization


180 GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Chapter 8. Working With the Enterprise Server

This section discusses: Understanding Data Classes Creating a New Data Class Modifying the Data Source Template Associating Table Data Classes

Understanding Data Classes


The data class is at the center of automatic OCM generation. It categorizes the type of data stored in data sources and tables, for example, in the Business Data data source the data class is B while in the System data source the data class is S. If you want to split business data into multiple data sources, you need to create a new data class, add a data source to the data source template for that data class (so Installation Planner prompts for the data source) and assign tables and GT objects to that data class. OCM will be created based on this information. You should do these steps before creating your plan.

Creating a New Data Class


You must create a new data class by adding a value to the H96/DU User Defined Code (UDC) for data sources and H96/CL UDC for table and GT objects.

Modifying the Data Source Template


A data source template defines the set of data sources that will be used by an environment, and the default values for the properties of the data source. They are stored in the F98511 table. The information in this table can be edited using Data Source Templates By Environment (GH9611) program. By understanding this application, you can implement custom environment naming standards and ease the creation of environments. Typically, you will add records to the template for new environments. The template can be found by filtering on *ENV in the environment field. Installation Planner prompts for this set of data sources whenever a new environment is created. The first time data sources are configured for a new environment, these records are copied and tokens replaced to create records specific to the new environment. If you want to add a new data source to a standard JD Edwards EnterpriseOne environment, enter the environment name into the filter field and add a record specifically for that environment. Records with an environment *LOGIC are for logic and server map data sources. They are set up when selecting an Enterprise Server.

Associating Table Data Classes


A table is associated with a data class using a field on the Object Librarian table (F9860.sicldf). Table data classes can be modified two ways. Object Management Workbench (GH902) Select the table in the left tree view in OMW and click Design. Select the Install/Merge Codes tab and modify the data class value. Click OK. Modifying the data class does not affect existing OCM mappings, it is only used when creating mappings for a new environment. Table Data Classes This application can be used to modify the data class for several tables at once. GA.Rev8 1/7/2008 181

Copyright 2008, Oracle. All rights reserved.

Chapter 8. Working With the Enterprise Server

This should only be used by a JD Edwards EnterpriseOne administrator. Go to GH9611 and open Table Data Classes. Use the QBE to filter the list of tables in the grid. Select one or more tables whose data class will be changed. Click Select. Type in the new data class value and click OK. Once these three steps have been taken, planner will prompt for the new data source and create OCM mappings for the new data source whenever an environment is added to a plan and the plan is finalized. Environment ENV1 ENV1 ENV1 ENV1 ENV1 ENV1 ENV1 ENV1 ENV2 ENV2 ENV2 ENV2 ENV2 ENV2 ENV2 ENV2 Object Name DEFAULT F0094 F9860 F9200 F0004 F983051 GT92002 GT9860A DEFAULT F0094 F9860 F9200 F0004 F983051 GT92002 GT9860A User/Group *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC Data Source Business Data ENV1 System - 812 Object Librarian - 812 Data Dictionary - 812 Control Tables ENV1 Versions - PY812 Data Dictionary - 812 Object Librarian - 812 Business Data ENV2 System - 812 Object Librarian - 812 Data Dictionary - 812 Control Tables ENV2 Versions - DV812 Data Dictionary - 812 Object Librarian - 812

Setting Up a Printer on the Enterprise Server


This section describes these tasks, which must be performed in the deployment environment: Adding a New Printer Defining a Default Printer

You also can print Release 8.12 reports, modify existing printers, and delete printers. These tasks are described in detail in the JD Edwards EnterpriseOne Tools 8.96 System Administration Guide. Refer to that document to learn more about setting up a printer to run from the Release 8.12 Enterprise Server.

Adding a New Printer


Release 8.12 provides a Printer Setup director to help you add printers. Instructions appear on each form of the director to guide you through the printer addition process. This procedure is used in conjunction with the steps that appear on the forms of the Printer Setup director. To install your first printer:

182

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 8. Working With the Enterprise Server

1.

On the Printers menu (GH9013), select Printers (P98616). The Printers form appears.

2.

On the Printers form, click Add Printer. The welcome page for the Printer Setup director appears. This page describes the tasks that the director helps you perform.

3.

Review the welcome page and click Next. The Platform Information form appears. The platform type may appear by default, depending on the operating system on which Release 8.12 is running.

4.

On Platform Information, complete these fields: Platform Type Print Server Name Enter the platform type on which you are installing or use the visual assist button to select a platform type. Enter the name of the print server for the printer you are setting up. Valid characters are all alpha (A-z), numeric (0-9), period ( . ), and dash ( - ). Release 8.12 uses this name, along with the print shared name, to create the printer name, which is unavailable for modification on the subsequent form. For printing reports to a non-network printer, leave this field blank. Enter the share name of the printer you are setting up. All characters are valid except the forward slash ( / ) and the backslash ( \ ). Release

Print Shared Name

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

183

Chapter 8. Working With the Enterprise Server

8.12 uses this name, along with the print server name, to create the printer name, which is unavailable for modification on the subsequent form. 5. After you complete the requisite fields, click Next to access the Printer Setup form. Use this form to set information for the printer such as the printer model, physical location of the printer, printer definition language (PDL), and paper types. 6. On the General tab, complete these fields: 7. Printer Model Printer Location

On the Details tab, in the box labeled Printer Definition Language, select one of these options: PostScript PCL Line Printer Custom

8.

In the Default box, specify one of the Printer Definition Language options as the default value. You can select multiple PDLs, but only one default PDL. A user can override this default PDL at the time a batch process is submitted. Choosing PostScript or Printer Command Language (PCL), Release 8.12 disables the Line Printer option. Choosing Line Printer, Release 8.12 disables the PostScript and PCL options. When choosing the Line Printer option, this logic occurs: Release 8.12 disables the grid at the bottom of the form and any paper types you have chosen are cleared. JD Edwards EnterpriseOne automatically provides a printer type of *JDE LINE PAPER for the printer. The Fields in the box labeled Line Printers are used to set the paper dimensions and line parameters. This procedure is explained in later steps in this section. The custom option uses advanced features of the printers application, which are explained in the later steps in this procedure.

9.

On the Details tab, when choosing the PostScript option, the Paper Source box appears and you can change these options: Max Number of Paper Sources Default Paper Source Enter a numeric value in this field to indicate the number of paper trays this printer has available. Enter a numeric value in this field to indicate which tray number you want Release 8.12 to draw paper from as the default tray.

10. On the Details tab, when choosing the Line Printer option, fields appear in a box labeled Line Printers, 184 GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Chapter 8. Working With the Enterprise Server

which you use to set the paper dimensions and line parameters. Complete these fields: Characters Per Inch Columns Per Page Lines Per Inch Lines Per Page Printer Paper Width Printer Paper Height Enter a value to specify the number of characters in one horizontal inch. Enter a value to specify the number of characters in one line of text in the specified report. Enter a value to specify the number of lines of text in one vertical inch. Enter a value to specify the number of lines of text on one printed page. Displays a value that is calculated automatically based on the values entered in the Line Printers box. Displays a value that is calculated automatically based on the values entered in the Line Printers box.

11. On the Details tab, the Custom option lets you specify a conversion filter to use. When choosing the Custom option, a field appears beneath the Custom checkbox. Enter the name of the conversion filter you want to use or use the visual assist to select a filter from the Conversion Program Search and Select form. 12. If you do not want to change or add a conversion filter, skip to step 16 in this task. To change or add a conversion filter, from the Form menu, select Advanced, and continue with the steps in this procedure. The Advanced option is enabled only when Custom has been chosen. The Work With Conversion Programs form appears. 13. Either click Add, or highlight one of the filters and click Copy or Select. The Advanced Conversion Program form appears. 14. Change one or both of these fields: Conversion Program If you clicked Add or Copy on the previous form, the Conversion Program field is enabled. Enter the name of the conversion program that you want to add or copy. When making a copy, the Parameter String field is populated with the string that you highlighted on the previous form. The JD Edwards EnterpriseOne system automatically enters the parameter string in native commands based on the host type from which you are printing and the type of printer (PostScript, PCL, or line).

Parameter String

15. Click OK. The Work with Conversion Programs form appears. Click Close. The Printer Setup form appears. 16. In the grid at the bottom of the Printer Setup form, double-click the row header for each paper type that your

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

185

Chapter 8. Working With the Enterprise Server

printer supports. A checkmark appears in the row header for each paper type that you select.

Note
You can add new paper types as necessary. Instructions are included later in this task. 17. In the Default Type column, enter the numeral 1 in the row for the paper type you want to use as the default. select only one paper type as the default. A user can override the default paper type when a batch process is submitted.

18. To add a new paper type, continue with these steps: 19. From the Form menu, select New Paper Type. The Work With Paper Types form appears. 20. Click Add. The Paper Type Revisions form appears. 21. Complete these fields: Paper Type

186

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 8. Working With the Enterprise Server

Paper Height Paper Width Unit of Measure

The software saves the new paper type. 22. Click OK to return to the Work With Paper Types form, and then click Close to return to Printer Setup. The new paper type is available in the grid on the Printer Setup form. All previous paper type selections are cleared and must be reselected if you want to use them again. 23. When finished entering information for the printer on the Printer Setup form, click End. Release 8.12 saves the new printer setting and returns you to the first form in the Printers application. Platform Type Server Name Printer Name Define the type of physical hardware on which the database resides. Define the computer that receives documents from clients. Enter a name that refers to a shared resource on a server. Each shared directory on a server has a share name, which is used by clients to refer to the directory. Define these attributes for your printer: Printer Model Printer Location

Printer Model

Paper Type Paper Width Paper Height Unit of Measure

Columns Per Page Characters Per Inch (CPI)

Designates the physical location of the printer Enter a user defined code (H98/PT) to define the type of printer paper, such as letter or legal. For example, LETTER, LEGAL, and A4. Define the width of the paper for this paper type. This value is in the unit of measure specified by Unit of Measure. Define the height of the paper for this paper type. This value is in the unit of measure specified by Unit of Measure. Enter a user defined code (00/UM) to define the quantity in which to express an inventory item. For example, CS (case) or BX (box). Form-specific information indicates the unit of measure in which the paper height and width are entered. For example, IN = Inches and MM = Millimeters. Define the number of columns per page. For example, 80 or 132. Define the horizontal printing density in characters per inch. You should only define values that are supported by your printer. Define the number of lines per page. For example, 60 or 66. Define the line spacing in lines per inch. You should only define values that are supported by your printer. Values are: 4 - IBM 5219, 5224, 5225, and 3287 printers only 6 - IBM 5224 printer only

Line Per Page Line Per Inch (LPI)

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

187

Chapter 8. Working With the Enterprise Server

8 - IBM 5224 printer only 9 - IBM 5225 printer only

Note
The standard computer print is 6 LPI and 10 CPI. If you are printing on 8 1/2-inch x 11-inch paper, typically you would specify 8 LPI and 15 CPI. Define the maximum number of paper trays available on the printer you are setting up. Define the output tray for a given batch print job.

Maximum Number of Output Tray Output Tray Name

Defining a Default Printer


To define a default printer: 1. 2. On the Printers menu (GH9013), select the Printers (P98616) program. On the Printers form, click Define Default Printer. The Work With Default Printers form appears. 3. Click Add.

188

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 8. Working With the Enterprise Server

4.

On Default Printer Revisions, complete these fields and then click OK. User/Group Report Name Version Name Click the visual assist to select either a particular user for this printer or to select an entire group. Click the visual assist to select a specific report to print. Enter *ALL for all reports. Click the visual assist to select a specific report to print. If the value in the Report Name field is *ALL, the system populates the Version Name field with the default value of *ALL and makes the field unavailable for subsequent modification. JD Edwards EnterpriseOne provides a default value for this field based on the environment that you are currently logged onto. Enter *ALL for all environments. You can change this information. Enter the name of your printer. Enter the name of the host server where reports will be processed. The visual assist displays the appropriate host names based on the printer name you select. To use this printer for all hosts in your environment, enter *ALL. Define the new printer as the default printer by changing its status to active. If an error occurs, it means that another printer is currently the active default. Change the original default printer to inactive before making the new printer active. Change multiple statuses from the Work With Default Printers form, as explained at the end of this task.

Environment

Printer Name Host Name

Object Status

5.

Click OK, and then click Cancel to access the Work With Default Printers form.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

189

Chapter 8. Working With the Enterprise Server

6.

To change the status of a default printer, select a default record and, from the Row menu, select Change Status. If another printer is already set as the active default, an error occurs. To change the original default printer to inactive, select it, select Change Status on the Row menu, and then select the new printer as the default.

190

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 9. Installing the Workstations for Developers and System Administrators


This chapter includes these topics and tasks: Understanding Workstation Installation Preparing for Workstation Installation Understanding Workstation Installation Understanding User Profiles and Languages Working with the Workstation JDE.INI on the Deployment Server

Understanding Workstation Installation


Release 8.12 software is first installed on the Deployment Server, and then deployed from the Deployment Server to developer and system administrator workstations. The workstation installation can occur using either interactive mode, silent mode, or push mode. Push mode is described in the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide. The workstations for developers and system administrators are Microsoft Windows-based machines. Refer to the Minimum Technical Requirements for specifically-supported versions of Microsoft Windows.

Note
The JD Edwards EnterpriseOne 8.12 Installation delivers pre-built packages that are ready for use as delivered. For the workstation to reflect the language installed on the Deployment Server, you must perform tasks for both the Enterprise Server and workstations, in addition to the procedures to verify and modify the JDE.INI on the workstations and the JDE.INI on the Enterprise Server. See Also Refer to Language Process Overview for more information about how you enable multilingual installations on workstations. JD Edwards EnterpriseOne Web Development Client Installation and Configuration Guide JD Edwards EnterpriseOne Tools 8.96 Package Management Guide

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

191

Chapter 9. Installing the Workstations for Developers and System Administrators

Preparing for Workstation Installation


To prepare for the installation of Release 8.12 on individual workstations, complete brief configurations and modifications: modify the workstation JDE.INI on the Deployment Server and the system administrator creates a user profile for every user before that user can log on to Release 8.12.

Note
Refer to the JD Edwards EnterpriseOne Web Development Client Installation Guide for additional details on installing the Web Development Client. Prerequisites Before installing Release 8.12 on a workstation used for development, you must install the Microsoft Visual C++ Compiler. The specific version of the compiler is detailed in the Minimum Technical Requirements (MTRs) located on Customer Connection. Refer to Accessing Minimum Technical Requirements. Also refer to the appropriate Microsoft documents for installation information. The names of the Deployment Server, Enterprise Server, and client workstation cannot exceed 15 characters in length.

Note
You do not need full administrator privileges to install Release 8.12 on the workstation. However, you do need proper privileges for writing to the disk and the registry. If you do not have these privileges, you will receive a warning during the installation. If you receive a warning, contact your administrator, who can perform the installation or can grant proper disk and registry access. For more information about granting disk and registry access, see Granting Access to the Software Installation Directory. Connectivity is required for: Read/write access to this client install directory on the primary Deployment Server in the base location: \oneworld Read access to the subdirectories located under this directory: \pathcode\package For example: \\deployment_server_name\E812\PD812\package Read/write access to this directory on the primary Deployment Server: \client For example: \\deployment_server_name\E812\client

192

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 9. Installing the Workstations for Developers and System Administrators

Understanding Workstation Installation


The workstation installation program copies all necessary components of Release 8.12 to a workstation. During installation, the installation program verifies that enough disk space exists and, if not, you are prompted to create more space before continuing. This section contains the following topics: Understanding Workstation Installation Methods Understanding Third-Party Products

Understanding Workstation Installation Methods


You can select from three methods to deploy Release 8.12 and to launch the workstation installation program: Working with Interactive Mode Working with Silent Mode Working with Push Mode

Working with Interactive Mode


This section discusses: Creating a Desktop Shortcut Using a Shared Drive

See Also JD Edwards EnterpriseOne Tools 8.96 System Administration Guide for more information on the Install Manager tool and for editing and configuration options.

Caution
Before starting a JD Edwards EnterpriseOne workstation installation, you must close all other applications running on that machine. The installation process may not run correctly if other applications are open.

Creating a Desktop Shortcut


A system administrator can create a shortcut to InstallManager.exe from the JD Edwards EnterpriseOne client install directory on the Deployment Server and can deploy the shortcut to the workstation. For example, the client install directory is typically: \JDEdwards\E812\OneWorld Client Install To ensure that the shortcut works correctly, ensure the Start in: field contains the location of the installmanager.ini file.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

193

Chapter 9. Installing the Workstations for Developers and System Administrators

To create a desktop shortcut: 1. 2. 3. 4. To edit the Start in: field, in Microsoft Windows Explorer or on the desktop, right-click the shortcut. Click Properties, and then click the Shortcut menu. Double-click the Release 8.12 InstallManager shortcut to start the Release 8.12 installation manager. Skip to the next task entitled: Using a Shared Drive. Begin with step 2.

Using a Shared Drive


An installer can connect to the \JDEdwards\E812 shared drive on your Deployment Server from Microsoft Windows Explorer. To use a shared drive: 1. Double-click InstallManager.exe to start the Release 8.12 installation manager. The InstallManager.exe file is located in this folder: OneWorld Client Install 2. 3. On JD Edwards EnterpriseOne Release 8.12 Installation Manager, click Workstation Install. On Client Workstation Setup, click Next. If you do not have the latest versions of Microsoft Internet Explorer or MSDE the Release 8.12 Client Workstation Setup Third Party Application form appears. The option to install Internet Explorer is selected. To install this application, click Next. If you do not want to install these applications at this time, clear the option for one or both of them, and click Next. If the latest versions of Internet Explorer or MSDE are already installed, the Third Party Application form is not displayed. 4. On Client Workstation Setup Package Selection, select the package you want to install and click Next.

Tip
Click the Filters ON button to narrow the displayed list of available packages. This can help you find the package you want. Notice that a short description of each package appears below the list. 5. On Client Workstation Setup Type, complete these fields: Select Setup Type Select Development or Production objects. You should only select the Development option if you intend to develop Release 8.12 applications.

Note
Select the Development option only if you intend to develop JD Edwards EnterpriseOne applications. Select the drive and directory in which to install the package. For example, this is the typical path for Release 8.12:

Install Path

194

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 9. Installing the Workstations for Developers and System Administrators

c:\E812 6. To install the package, click Finish. InstallManager shows the status of the installation process through a series of forms. The Congratulations form indicates that the installation finished successfully. InstallManager creates a Release 8.12 shortcut in the Programs folder of your Start menu and on your desktop. 7. Reboot if necessary.

Caution
The JD Edwards EnterpriseOne client workstation installation process verifies that several of the system DLL files are current. If they are not current, you receive a message to reboot your system. When you reboot, the system updates the DLL files in your Microsoft Windows directories.

Note
When you open Release 8.12 after installing the client workstation, or upgrading to Release 8.12, a security violation screen may appear. Click Get Authorization to obtain a local license, and then click OK.

Working with Silent Mode


JD Edwards EnterpriseOne can also be installed to the workstation by the silent mode, which is optional. The silent installation mode lets you specify the installation path by command-line arguments instead of entering them on the Workstation Installation forms. As a result, submit the silent installation from the command line or through any scheduling service (such as Microsoft Windows schedulers) that you have installed. Verify that you are connected to this shared drive on the Deployment Server: \JDEdwards\E812 To work with silent mode: 1. 2. 3. 4. From the Start menu, select Run. Click Browse. Locate the\JDEdwards\E812\OneWorld Client Install directory on the Deployment Server, select SETUP.EXE, and then click Open. In the Run box, append the required parameters to setup.exe so that the command line conforms to this structure: setup.exe -S -P packagename -D installpath where packagename is a valid package name and installpath is the installation path on the workstation where Release 8.12 should be installed (for example, c:\E812). You also can include the following optional parameters: -t Typical

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

195

Chapter 9. Installing the Workstations for Developers and System Administrators

Using the typical parameter installs the development objects. -t Compact Using the compact parameter does not install the development objects. -r Using the -r parameter indicates you want to uninstall the previous installation before continuing. The results of the uninstallation appear in c:\jdeinst.log.

Caution
If the specified installation path already exists, the directory structure contents are overwritten. 5. To run the command line, click OK. During a silent installation, Release 8.12 Client Installation appears in the Microsoft Windows taskbar. 6. Verify a successful installation by viewing the c:\jdeinst.log file.

Note
When you open Release 8.12 after installing the client workstation, or upgrading to Release 8.12, a security violation screen may appear. Click Get Authorization to obtain a local license, and then click OK.

Working with Push Mode


Push mode is described in the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide.

Understanding Third-Party Products


MSDE is required for Release 8.12 Workstations. If not already installed, it is installed during the installation process. The workstation installation program detects the latest version of MSDE and, depending on the version, prompts to update this application during the Release 8.12 installation process. The use of Microsoft Internet Explorer is optional. Adobe Acrobat Reader 6.0 or greater is strongly recommended to view reports online. Neither the browser or reader applications are delivered with the JD Edwards EnterpriseOne 8.12 Installation. Microsoft Internet Explorer provides: An option for a Web-like menu view within JD Edwards EnterpriseOne Explorer. An option for an Internet connection capability directly from the JD Edwards EnterpriseOne Explorer interface.

Understanding User Profiles and Languages


Note
Release 8.12 supports group preferences for user profile workstation configuration and environment assignment.

196

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 9. Installing the Workstations for Developers and System Administrators

For user and group profiles, you should use the preloaded users to perform the installation process. The system administrator needs to create a user profile before the user can log on to Release 8.12. All users are assigned a language preference code within the user profile. The language preference code field specifies which language is presented on the applicable form or report. You can set up your users and groups when determining how groups are to be organized and what preferences each group shared to have. For languages, the JDE.INI on the Windows-based Deployment Server are updated automatically. For multiple language usage, both the Enterprise Server and workstation JDE.INI need to be modified for the preferred language being installed. See Also JD Edwards EnterpriseOne Tools 8.96 System Administration Guide for more detailed information about setting up group profiles and how to use them, as well as for information about defining user display preferences.

Working with the Workstation JDE.INI on the Deployment Server


This section discusses: Understanding the Workstation JDE.INI on the Deployment Server Modifying the Workstation JDE.INI on the Deployment Server

Understanding the Workstation JDE.INI on the Deployment Server


To facilitate the administration and maintenance of the JDE.INI for multiple client workstations, all instances of the JDE.INI are stored on the Deployment Server. To make a change to a JDE.INI for a workstation, change the original file on the Deployment Server. The file is then copied from the Deployment Server to its respective workstation during the web development client installation process. This task describes modifications required to make to the workstation JDE.INI before installing Release 8.12 on the workstation. When using a double-byte language, modify the ODBCDataSource.inf on the Deployment Server by adding this value to all ODBC Data Sources: DBCSNoTruncErr=1

Warning
If the ODBC Data Sources do not have this registry value on the workstations, some records will not be inserted into tables and Insert Record Failed errors will appear. Use this procedure to modify settings in the JDE.INI in this directory on the Deployment Server: \JDEdwards\E812\OneWorld Client Install\Misc

Modifying the Workstation JDE.INI on the Deployment Server


To modify the workstation JDE.INI on the Deployment Server: Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 197

Chapter 9. Installing the Workstations for Developers and System Administrators

1.

Open the workstation JDE.INI and modify these settings:

Note
For language installations, ensure that the workstation is set up correctly for language preferences to display and print forms. If multiple languages are installed, verify that the appropriate JDE.INI values are set to your preferred language. See Language Process Overview for appropriate values. [INTERACTIVE RUNTIME] For the language you are installing, enter: Initial_Language_Code = x where x is the value for the language installed or, if multiple languages are installed, for the preferred language. Verify that the LocalCodeSet value and code page setting are set to the appropriate values. The system reads the JDE.INI setting for the installed language. Verify that the port number specified for ServiceNameListen and ServiceNameConnect matches the port number in the Enterprise Server JDE.INI.

[INSTALL]

[JDENET]

2.

Save and close the file.

198

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 10. Understanding Media Object Queues


Media objects enable the attachment of information to Release 8.12 applications. Media Object Queues enable you to specify the storage location of media objects to be tracked by reference as opposed to physical network location. This enables easier administration of media locations. Media object queues provide the system administrator the ability to easily manage the storage of media objects and helps in a Release 8.12 configuration. Within Release 8.12, set up media object queues in order to use images that are outside the domain of the imaging product (for example, scanned images). Define a media object queue to identify the pointer to the location where the actual image files or Object Linking and Embedding (OLE) objects reside. For OLE objects, the name of the queue must be OLEQUE. The media object queues must reside on a Microsoft Windows-based machine. A valid network-qualified path must exist for this machine. Use the Deployment Server or any other Microsoft Windows-based machine. If you modify the OLEQUE path, make sure to copy the image files and OLE objects to the new location. When using the Deployment Server to store media object queues, remember to make the machine available for use daily by Release 8.12 applications. Media object queue paths are shipped with generic server names. To enable media object queues at the customer site, enter the Deployment Server name in the media object queue path. See Also Media Objects and Imaging in the JD Edwards EnterpriseOne Tools 8.96 System Administration Guide for more information about the use of media objects.

Modifying Media Object Queues


To modify your media object queues: 1. 2. 3. 4. Log into Release 8.12 as JDE in the DEP812 environment. From System Administration Tools (GH9011), select Media Object Queues (P98MOQUE). To define the location for a new OLE queue, click Add. Complete these fields: Name Path Enter a valid value for your queue. Generally the queue paths include server_name and queue_name. Replace server_name with the name of the Deployment Server or the location of the media object queue. A valid queue path for a network location might be: \\server_name\E812\queue_name where server_name is your Deployment Server and queue_name is the name of the media object queue. When using ComposerCBT, the media object queue path does not require \\ or server_name. ComposerCBT is shipped with an x for the drive name. To enable the Composer CBT queue, replace the x with the drive letter that the workstation uses Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 199

Chapter 10. Understanding Media Object Queues

to access the server where the media object queues reside. For example: N:\Mediaobj\ComposerCBT. 5. 6. To change an existing media object queue, click Find to display a list of queue names and their paths. On Work With Media Object Queues, select the queue name you want to modify.

7. 8. 9.

On Media Object Queues, change the information in the Queue Path On-Line field to reflect the new location. Copy the image files and OLE objects to the new location. Exit Release 8.12 and log back on to enable the changes.

Specifying the Help Location


To specify the help location: 1. 2. From System Administration Tools (GH9011), select Media Object Queues (P98MOQUE). To define the location for the Help file, on Media Object Queues, enter Help in the Name field and click Find.

200

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 10. Understanding Media Object Queues

3.

On Media Object Queue Revisions, complete these fields: Path Replace the existing default value with: http:\\Server_Name\E812\f1search.htm where server_name is the server on which you copied the Help files. Enter the value 09.

Type 4. 5.

Copy the Help to the new location. Exit Release 8.12 and log back on to enable the changes.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

201

202

This page intentionally left blank

Chapter 11. Performing Post Installation Tasks


This section contains these tasks: Understanding Post Installation Tasks Setting Up Microsoft Windows Security on Release 8.12 Directories Using the Adobe SVG Viewer on Web Clients Understanding Task Word Search Tables Setting Up Solution Explorer Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications Enabling CRM Functionality

Understanding Post Installation Tasks


You must modify specific applications after finishing the installation process. You should perform special instructions as described in the Application Special Instructions Guide located on Customer Connection.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

203

Chapter 11. Performing Post Installation Tasks

Setting Up Microsoft Windows Security on Release 8.12 Directories


To set up Microsoft Windows security on the Release 8.12 directories and files on your Deployment Server. Use these charts to determine what permissions are required for the various types of Release 8.12 users and perform these tasks to set permissions on the Security tab: Setting Security on the Files within the Client Directory Setting Security on the Pathcode Directory Setting Security on the Database Directory Setting Security on the Data Dictionary Directory Setting Security on the Helps Directory Setting Security on the Media Object Directory Setting Security on the Planner Directory Setting Security on the Print Queue Directory Setting Security on the System Directory

Note
Not all directories are available. The directory names listed in the table below are subdirectories of the \JDEdwards\E812 directory structure. You can apply the indicated permissions to all subdirectories and files except where noted.

Setting Security on the Files within the Client Directory


Note
The Microsoft Windows Deployment Server logon requires full control for security setup. This table lists the recommended security permission settings on files within the client directory, which varies according to files and user type: Files jdeclntuni.ddc jdeclntuni.xdc All files except jdeclntuni.ddc and jdeclntuni.xdc JDE All other user types Change Read-only User Type All user types Permissions Change

204

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

Setting Security on the Pathcode Directory


This table lists the settings to set security on the pathcode directory: User Type JDE (all subdirectories except \pathcode and \package) Production users (all subdirectories except \pathcode and \package) Development users (all subdirectories except \pathcode and \package) CNC administrators and application leads (all subdirectories except \pathcode and \package) Permissions Change Change Read Only Change Change Change Change Change

Setting Security on the Database Directory


This table lists the settings to set security on the database directory: User Type JDE Production users Development users CNC administrators and application leads Permissions Change No Access No Access No Access

Setting Security on the Data Dictionary Directory


This table lists the settings to set security on the data dictionary directory: User Type JDE Production users Development users CNC administrators and application leads Permissions Change No Access No Access Change

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

205

Chapter 11. Performing Post Installation Tasks

Setting Security on the Helps Directory


This table lists the settings to set security on the Helps directory: User Type JDE Production users Development users CNC administrators and application leads Permissions Change Read Only Read Only Read Only

Setting Security on the Media Object Directory


This table lists the settings to set security on the media object (literal name is mediaobj) directory: User Type JDE Production users Development users CNC administrators and application leads Permissions Change Read Only Read Only Change

Setting Security on the Planner Directory


This table lists the settings to set security on the planner directory: User Type JDE Production users Development users CNC administrators and application leads Permissions Change No Access No Access No Access

Setting Security on the Print Queue Directory


This table lists the settings to set security on the print queue (literal name is printqueue) directory: User Type JDE Production users Development users CNC administrators and application leads Permissions Change No Access No Access No Access

206

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

Setting Security on the System Directory


This table lists the settings to set security on the system directory: User Type JDE Production users Development users CNC administrators and application leads Permissions Change Read Only Read Only Change

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

207

Chapter 11. Performing Post Installation Tasks

Using the Adobe SVG Viewer on Web Clients


Per the Minimum Technical Requirements (MTRs) for JD Edwards EnterpriseOne web clients (refer to Accessing Minimum Technical Requirements), you must have the Adobe Scalable Vector Graphics (SVG) viewer installed on your web clients in order to use specific JD Edwards EnterpriseOne applications, such as Demand Flow Manufacturing. Within such JD Edwards EnterpriseOne applications, the Graphical Product Synchronization uses the Adobe SVG viewer for displaying the graphics associated with the product synchronization. The JD Edwards EnterpriseOne application automatically detects the Adobe viewer if it is already installed for the browser. If the viewer is not installed for the browser, the system displays a link that you can use to install the viewer from the Adobe web site. The URL for this link is: http://www.adobe.com/svg/viewer/install/main.html

Note
SVG is a graphics file format and web development language based on XML that enables dynamic creation of high-quality graphics with precise structural and visual control. It is based on standards defined by the World Wide Web Consortium (http://www.w3.org/TR/SVG/) .

Tip
The installation of the SVG viewer may require administrator authority on your client machine.

208

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

Understanding Task Word Search Tables


The Task Word Search Build program populates the F91014 table from information in the F9000 and F91012 tables. Word Search locates a JD Edwards EnterpriseOne menu or task if the name is not known. The installation of these tables is optional. When running the Word Search Build programs, the system locates the menu or task and word search tables for the environment you are logged on to. The Find It! program is part of the Solution Explorer and uses the same underlying functionality as the Task Word Search. You can search for a Solution Explorer task by entering a complete or partial task name. For the Find It! Program to work, you must following the task below to build Task Word Search tables. If you follow the recommended environment builds during installation, build the Word Search tables using one or a combination of the PD812, PY812, DV812, and PS812 environments. The complete Word Search Build is approximately 7.5 MB. The batch process can take several hours to complete.

Building Task Word Search Tables


To build task word search tables: 1. Log on to the Release 8.12 environment for your pristine or publisher copy of your tasks. This environment typically maps your tasks to the data source Control Tables - Prod, the data source where the Task Word Search master table resides. Use an environment that points to your local workstation only if you very recently installed Release 8.12; otherwise, you could be building from out-of-date tasks. 2. On System Administration Tools (GH9011), select Batch Versions (P98305). The Work with Batch Versions form appears. 3. Enter R91014 in the Batch Application field. This is the name of the batch process that updates the Task Word Search table. 4. 5. Click Find to locate the versions available on your workstation. Select version XJDE0001, Build Task Word Search Table. The Version Prompting form appears. You can submit your job without selecting any options on Version Prompting. However, from Version Prompting you can specify Data Selection and Data Sequencing and access the Advanced Version Prompting form. 6. Click Submit to send your job to the report processing location. The system takes the task information from the Object Configuration Management mappings on the environment you are logged onto and populates the F91014 table.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

209

Chapter 11. Performing Post Installation Tasks

Setting Up Solution Explorer


Solution Explorer is the Microsoft Windows-based interface that provides access to Release 8.12 applications, role-based menus, implementation and configuration options, documentation, and training materials. Solution Explorer is a convenient window into Release 8.12. Users can access Solution Explorer to search and navigate quickly through Release 8.12 applications. Users also can customize Solution Explorer to create their own tasks and link tasks to other Web-based information. The Find It! program is part of Solution Explorer whose search feature uses the same underlying functionality as the Task Word Search. You can search for a Solution Explorer task by entering a complete or partial task name. For the Find It! Program to work, you must perform the previous task Building Task Word Search Tables. For more information about Solution Explorer, see the Solution Accelerator Suite Implementation Guide.

Setting Up Solution Explorer HTML Documentation Path


When Release 8.12 is installed, the system automatically stores HTML documentation hierarchically in folders located in a common documentation directory. Using Media Object Queues, Solution Explorer locates these files and displays the associated documentation in its own window whenever a user selects a task. The file path from Solution Explorer to the HTML documentation files is defined in the F98MOQUE table; it must be configured by accessing the corresponding program, called the Work with Media Object Queues (P98MOQUE) program. When JD Edwards EnterpriseOne installs the documentation files, it creates an entry in the Media Object Queue table that associates the Queue Name, called ActivEraData, with a generic path to the documentation. For Solution Explorer to link each HTML file with the correct task, you must open this program and change the server name for the directory path associated with the Queue Name ActivEraData. The directory path has this structure: \\Server_Name\E812\SolutionExplorder\Data where Server_Name is the name of your Deployment Server. When the queue name ActivEraData is correctly mapped to the main HTML documentation directory, Solution Explorer locates and displays the associated documentation when a user accesses a Task Location or Task View Location. For example, if a task named JDE001234 exists, the path to the HTML file of the summary document for the task is: \\Server_Name\PY812\SolutionExplorer\Data\JDE001234\summary.html where Server_Name is the name of the Deployment Server For more information on setting up the documentation path, refer to Modifying Media Object Queues .

Setting Up the Home Page for Solution Explorer


The home page is generally the first screen a user sees when logging on to Solution Explorer. This screen can be used to display information that is relevant to end users in the enterprise. It can be an external Web site, an intranet site, or even HTML files stored on any server on the network. During the installation process, a directory called PortalLite is created when the Deployment Server is installed. This directory resides in this path: x:\base_installation_directory\SolutionExplorer\PortalLite where x:\base_installation_directory is the drive and directory where you installed Release 8.12 on your Deployment Server. 210 GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

The PortalLite directory includes a set of HTML files that make up the default Home Page. Even though this directory is on the Deployment Server by default, the direcotry could reside anywhere on the network, such as on a HTML Web Server or on a local workstation. When the Release 8.12 client is installed, the system updates the client JDE.INI to point to the location of the PortaLite directory. For example, if the name of the Deployment Server is DepServer1 and the share name is E812, the [Explorer] section of the JDE.INI is updated as follows: [Explorer] ExplorerHomeURL="\\DepServer1\E812\SolutionExplorer\portallite\index.html" ExplorerStart=INTERNET You can change the above parameters in the JDE.INI to display any HTML file or URL as the default Home Page. This table describes these parameters: [Explorer] Parameter ExplorerHomeURL= Description Defines the URL or filename of the Home Page that is displayed when the user logs on. The default value is: \\Depserver1\E812\SolutionExplorer\portalite\index.html ExplorerStart= Defines the Explorer start mode. Values are: INTERNET TASK This is the default value. When you start Solution Explorer, the system displays the Internet view first. When you start Solution Explorer, the system displays the last task view the user viewed. To display a specific task view, use this syntax: ExplorerStart=TASK:xx where xx is the task ID of the task view.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

211

Chapter 11. Performing Post Installation Tasks

Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications
This topic describes how to configure JD Edwards EnterpriseOne to use the Vertex Quantum tax applications. If you do not use these applications with JD Edwards EnterpriseOne, skip this section. Release 8.12 can be used with the following Vertex Quantum tax applications: Vertex Quantum for Payroll Tax Vertex Quantum for Sales and Use Tax

The Vertex Quantum applications should be installed on your system before starting the configuration tasks.

Note
The Vertex Quantum applications can be used with the Indexed Sequential Access Method (ISAM) database or Oracle database (for either of the Vertex Quantum applications) or the SQL Server database (for Vertex Quantum for Sales and Use Tax). The ISAM database is installed as part of the Vertex Quantum application installation. See Also Vertex Quantum for Payroll Tax - Administrator's Guide Vertex Quantum for Sales and Use Tax - Administrator's Guide Before configuring Release 8.12 for use with Vertex Quantum applications, install Vertex Quantum for Payroll Tax, Vertex Quantum for Sales and Use Tax, or both on the Enterprise Server. For information about installing the Vertex Quantum applications, refer to the Vertex Quantum administration guides listed above. When installing the Vertex Quantum applications, note the following: When using DB2/Universal Database (UDB), you must install the Vertex ISAM database. Vertex does not support DB2/UDB. Note the directory path on the Enterprise Server for the directory in which the Vertex Quantum applications are stored. This information is needed when copying the Vertex libraries into the Release 8.12 directory structure. For Vertex Quantum for Sales and Use Tax, you can install the ISAM database version of the Vertex Quantum application, or you can use the SQL Server or Oracle database. For Vertex Quantum for Payroll Tax, you can install the ISAM database version of the Vertex Quantum application, or you can use the Oracle database. You cannot use SQL Server with Vertex Quantum for Payroll Tax. When using the Vertex ISAM database, note the directory path on the Enterprise Server for the directory or directories in which the Vertex Quantum application databases are created. This information is needed for establishing Release 8.12 database connectivity.

212

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

Adding Vertex Quantum Directory Information to the Microsoft Windows Server Path
To add the Vertex Quantum application directory information to the Microsoft Windows server path: 1. 2. 3. 4. 5. 6. 7. From the Microsoft Windows Enterprise Server, access the Control Panel. On Control Panel, click the System icon. In System, select the Advanced tab. On the Advanced tab, click the Environment Variables button. In the System Variables window, scroll down until the keyword Path appears in the Variable column. Click Edit to display the current path in the Variable Value field. Search the current path (as shown in the Value field) for the Vertex Quantum application directory. If the directory does not appear, you must add it to the path, as described in the following step. If the directory appears in the path, skip to step 9 in this task.

8.

Place the cursor in the Value field, and use the right arrow to scroll to the end of the field and enter this path: x:\vertexDirectoryPath\vertex\utils where x:\vertexDirectoryPath is the drive and path for the directory in which the Vertex Quantum applications are stored.

Note
You might need to include a semicolon to separate this entry from previous entries. 9. Click Set. The new value is saved. 10. After you finish setting the Environment Variables, repeat this task for User Variables, starting from step 5 in this task. 11. Click OK and reboot the server. The new path takes effect. Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 213

Chapter 11. Performing Post Installation Tasks

Configuring the Release 8.12 Database Connections for Vertex Quantum Tax Applications
To configure Release 8.12 database connections to use the Vertex Quantum applications: 1. In the Fast Path field, enter G731 to access Vertex Quantum Tax Processing. The Vertex Quantum Tax Processing panel appears. 2. Highlight and right-click the Database Connections (P7308) program. A context menu appears. 3. On the context menu, select Prompt for Values. The Processing Options dialog appears. 4. On Processing Options, click the Quantum tab and enter the following information: Option #1: Enter which Vertex Quantum applications are installed: Value [blank] 1 2 Action Install both Vertex Quantum tax applications. Install the Vertex Quantum for Sales and Use Tax application. Install the Vertex Quantum for Payroll Tax application.

Option #2: Enter location information for the databases: Value [blank] 1 2 Action Define databases for both Vertex Quantum tax applications in the same location. Define databases for the Vertex Quantum for Payroll Tax and Vertex Quantum for Sales and Use Tax applications in separate locations. Define databases for the Vertex Quantum for Payroll Tax and Vertex Quantum for Sales and Use Tax applications in separate locations, and the four databases for the Vertex Quantum for Sales and Use Tax application in separate locations.

Option #3: If processing option #2 is set to 1 or 2 (that is, if the Vertex databases are in separate locations), specify the GeoCode database location information: Value [blank] 1 Action Define the Vertex Quantum Payroll Tax and Sales and Use Tax applications to use the same GeoCode database. Define each of the Vertex applications to use a separate copy of the GeoCode database, and and that the two copies are expected in separate locations.

5.

Click OK. The Vertex Quantum Database Connection panel is displayed. The Database Connection panel contains one or more tabs that correspond to the database connections that must be defined. The displayed tabs are determined by the values you entered in the processing options, in step 4 of this task.

214

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

Note
The GeoCode database is the only Vertex Quantum database that can be shared between the Vertex Quantum Payroll Tax and Sales and Use Tax applications. However, all of the Vertex Quantum databases can be installed in the same location or in different locations. One or more of the following tabs appears on the Database Connection panel: Tab All GeoCode GeoCode-Sales and Use GeoCode-Payroll Description All Vertex Quantum application databases for both applications are located on the same server and in the same location. The same GeoCode database is used by both applications. The GeoCode database used by the Sales and Use Tax application is located on this server and location. A separate copy of the GeoCode database, at another location, is used by the Payroll Tax application. The GeoCode database used by the Payroll Tax application is located on this server and location. A separate copy of the GeoCode database, at another location, is used by the Sales and Use Tax application. The four databases used by the Sales and Use Tax application are located together, on this server and location. The Test Data Management (TDM) database, used by the Sales and Use Tax application, is located on this server and location. The Register database, used by the Sales and Use Tax application, is located on this server and location. The Rate database, used by the Sales and Use Tax application, is located on this server and location. The databases used by the Payroll Tax application are located on this server and location.

Sales and Use TDM Register Rate Payroll

6.

On the Database Connection panel, select each tab and enter the following information: Data Source For ISAM, enter the directory path to the specified database. The location you enter should be the location on the server used for the database when the Vertex applications were installed, as previously described in this step. For ISAM, leave this field blank. For ISAM, leave this field blank. For ISAM, leave this field blank.

Server User ID Password 7. Click OK.

The changes do not take effect until you have logged off of your system and logged back on.

Mapping Objects to the Enterprise Server


Objects that call the Vertex Quantum APIs must execute on the server on which the Vertex Quantum APIs reside. Check that the following Release 8.12 objects are configured in the system OCM to execute on the server. Do not change the mappings. For Vertex Quantum for Payroll Tax:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

215

Chapter 11. Performing Post Installation Tasks

R07200 (Pre-payroll Driver) B0700058

For Vertex Quantum for Sales and Use Tax: X00TAX.c (Tax Calculator) B7300002 (Validate Quantum GeoCodes) B7300004 (Retrieve Quantum GeoCodes) B7300012 (Validate Quantum Software Information) B000182 B000183

Understanding the Autopilot Scripting Tool


The JD Edwards EnterpriseOne Release 8.12 Scripting Tool, also called Autopilot, is an automated testing tool used to create scripts to test the execution of Release 8.12 applications. Autopilot is included on the Release 8.12 installation media; it is activated through purchase of JD Edwards EnterpriseOne. For more information about purchasing Autopilot, contact your JD Edwards EnterpriseOne representative. If you have not purchased Autopilot, skip this procedure. For information about configuring Autopilot, refer to the JD Edwards EnterpriseOne Release 8.12 Scripting Tool Installation Guide. To run Autopilot after it is installed, an ODBC data source must exist in the ODBCDatasource.inf file that is installed on client workstations. Create the data source in Release 8.12, and then create the corresponding ODBC data source.

Configuring Autopilot for the Oracle Database


To create the ODBC data source in preparation for configuring Release 8.12 to run Autopilot: 1. 2. 3. Log on to JDEPLAN on the Deployment Server as user JDE with the database password for user JDE. Enter GH9611 in the Fast Path field. Select Database Data Sources.

216

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

4. 5.

On Machine Search & Select, select data source OneWorld Planner - 812. On Work with Data Sources, click Add.

6.

On Data Source Revisions, add a data source with the following information:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

217

Chapter 11. Performing Post Installation Tasks

Data Source Use Data Source Name Data Source Type Object Owner ID Library Name Library List Name DLL Name Database Name

Displays the value DB. Displays the name of the machine on which this data source resides. Enter the value O (for Oracle). Enter the value SYS812. Leave this field blank. Leave this field blank. Enter the value JDBOCI80.DLL. Enter a value for the Oracle database connect string. The connect string should be to the same database as Data Source Name, which you previously specified on this tab.

Server Name Platform 7. 8. Click OK.

Enter a name for your Enterprise Server. Select the value for your platform type.

On Work with Data Sources, highlight the new Data Source and, from the menu bar, select ODBC Data Source, Row, ODBC Data Source.

9.

On Create New Data Source, select System Data Source and click Next.

218

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

10. On Create New Data Source, select a driver and click Next. Microsoft ODBC for Oracle is recommended. If you do not have this driver, consult your database administrator.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

219

Chapter 11. Performing Post Installation Tasks

11. Click Finish.

220

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

On Microsoft ODBC for Oracle Setup, by default the Data Source Name fields contains the previously selected data source name. 12. Enter the name of your Enterprise Server in the Server field. 13. Click OK. The data source is added to the ODBCDatasource.inf file, which is located in this directory: \JDEdwards\E812\client

Testing the Vertex Quantum Connection from Release 8.12


Use the following procedures to test the Vertex Quantum connection from Release 8.12. To test the Vertex Quantum for Payroll Tax interface: 1. Access the Payroll Workbench menu (G07BUSP11), and select Pay Cycle Workbench.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

221

Chapter 11. Performing Post Installation Tasks

The Work with Payroll Cycle Workbench panel appears. 2. Specify pre-payroll information and submit the pre-payroll. For information about the Payroll Workbench and submitting pre-payroll, see Processing Pre-Payroll in the Release 8.12 Payroll Implementation Guide. 3. If no taxes are being calculated, there may be a setup or configuration problem. Verify the following to make sure setup is correct: UBE R07200 is being executed on the server where the Vertex Quantum for Payroll Tax APIs reside. Correct values are assigned to the Data Source, Server, User ID, and Password fields on the Database Connection panel, as specified in Configuring the Release 8.12 Database Connections for Vertex Quantum Tax Applications.

4.

For the Vertex Quantum for Sales and Use Tax interface: In the Fast Path field, enter P73GEO. The Retrieve GeoCode panel appears.

5.

On the Retrieve GeoCode panel, enter CO in the State field and DENVER in the City field, and click Find. The code 060310140 should appear in the grid.

6.

If nothing appears in the grid, a setup or configuration problem might exist. Verify the following to make sure setup is correct: These values are set in the Work with Quantum Constants Revision table, accessed by the Constants application (P7306) on menu G731:

Quantum Active: Y Canada Country Code: CA

Note
Changes to the Work with Quantum Constants Revision table do not take effect until you have logged off of your system and logged back on. Required Release 8.12 objects are mapped to the server where the Vertex Quantum for Sales and Use Tax APIs reside. Also ensure that correct values are assigned to the Data Source, Server, User ID, and Password fields on the Database Connection panel. Instructions for both procedures are specified in this guide in the section entitled Mapping Objects to the Enterprise Server.

222

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

Enabling CRM Functionality


To enable CRM functionality after the installation is complete, you must perform these procedures on the CRM Enterprise Server and the CRM client: Enabling CRM on the CRM Mobile Client Enabling CRM on the Enterprise Server

Enabling CRM on the CRM Mobile Client


To enable CRM functionality in JD Edwards EnterpriseOne and the JD Edwards EnterpriseOne mobile client, make sure that the F99410 table has records that contain the following system codes: SY90CA CRMMSL SY49

On your Enterprise Server, access the P99410 application and complete this procedure to enable CRM functionality: 1. 2. On Work with EnterpriseOne System Control, click Add. On EnterpriseOne System Control Revisions, enter each of these system codes, one at a time, in the Data Item field: 90CA This code enables CRM functionality in JD Edwards EnterpriseOne. MMSL With SY49, this system code enables CRM functionality in the mobile client. SY49 With CRMMSL, this system code enables CRM functionality in the mobile client. 3. 4. 5. Click Yes. Click OK. Repeat these steps to add each system code.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

223

Chapter 11. Performing Post Installation Tasks

Enabling CRM on the Enterprise Server


Using an ASCII editor, you must modify the JDE.INI on your Enterprise Server to add this section and setting: [MAILMERGE] FileLocation=location where location is a temporary location that you specify for the CRM-related mail merge files that are generated on your Enterprise Server, for example: c:\Microsoft Windows\TEMP

224

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 11. Performing Post Installation Tasks

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

225

226

This page intentionally left blank

Chapter 12. Working With Signon Security


For initial installations of JD Edwards EnterpriseOne, you must setup system user(s) using the Work With System Users (P980001) program to populate the F98OWPU table. You must set up system users before you can add and associate a JD Edwards EnterpriseOne user to a system user using EnterpriseOne Security (P98OWSEC).

Note
The system is shipped with users JDE and RAPID in the F98OWSEC table, as well as a *PUBLIC record for roles. The Rapid user is associated with all of the Rapid Start roles, which allow users to add, change, and delete records for those programs on the task view for the role. If a program is not set up for a particular role, the system uses the default role *PUBLIC, which is set up to secure all objects (add, change, and delete functions are not allowed). By default, an application security setting allows a user with the *PUBLIC role to navigate to different applications forms and view application data; however, they are not allowed any add, change, or delete any data. By contrast, the JDE user is set up with the SYSADMIN role that allows all actions.

Warning
If you attempt to add a user with the P98OWSEC program before you add the system user through the P980001 program, the system may add an invalid record to the F98OWPU table. You might have to delete the invalid record from F98OWPU using the SQL Query tool. You must perform security setup signed on to JD Edwards EnterpriseOne from a deployed client. If you perform the steps signed on to the deployment server, you will not be updating the correct security tables for your JD Edwards EnterpriseOne system. This chapter contains the following tasks: Setting Up Signon Security Setting up Security Overrides for Package Build Enabling Server-Side Signon Security Enabling Client-Side Signon Security Setting Up JD Edwards EnterpriseOne Single Sign-on

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

227

Chapter 12. Working With Signon Security

Setting Up Signon Security


To set up signon security: 1. On P980001 [Work With System Users], click Add.

2.

On System User Revisions, complete the following fields: System User Data Source Password Password Verify JDE DEFAULT Enter a valid password for your installation. Enter the same password that you entered in the password field.

3. 4.

Click OK. Click Find to verify the new record was added.

228

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 12. Working With Signon Security

5.

On P98OWSEC [Work With User Security], complete the following field: User ID / Role JDE

6. 7.

Click Find. Click Add.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

229

Chapter 12. Working With Signon Security

8.

On Security Revisions, complete the following fields: User ID Data Source System User Password User Status Allowed password attempts Password change frequency JDE DEFAULT JDE Enter a valid password for your installation. Ensure the Enabled radio button is selected. Enter a value applicable to your installation. Enter a value applicable to your installation.

9.

Click OK.

10. Click Find to verify that the record was added.

230

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 12. Working With Signon Security

Setting up Security Overrides for Package Build


Since Package Build now creates tables due to the requirement for metadata introduced with JD Edwards EnterpriseOne Tools Release 8.96, you must setup up security overrides for whoever is doing the package build. 1. 2. 3. 4. Create a system user for the owner of the Central Objects data source. For example, DV812. Create a role for package build. For example, PKGBLD. Add a security override for PKGBLD for Central Objects - DV812 using system user DV812. Add the PKGBLD role to the user who will be doing package builds. For example, JDE.

See Also JD Edwards EnterpriseOne Package Management Guide

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

231

Chapter 12. Working With Signon Security

Enabling Server-Side Signon Security


Ensure the JDE.INI on the Enterprise Server has these settings to support signon security: [SECURITY] SecurityServer=server_name User=JDE Password=JDE Default Role=*ALL DefaultEnvironment=PD812 DataSource=System - 812 History=0 After you modify the JDE.INI on the Enterprise Server, you must restart the JD Edwards EnterpriseOne Services so the settings can take effect.

Caution
If you have changed the database password for the JDE user, the password you specify on Enterprise Server in jde.ini must be the new password.

Enabling Client-Side Signon Security


Locate the JD Edwards EnterpriseOne client JDE.INI that is deployed from the Deployment Server. Typically the file can be found at the following location: x:\JDEdwards\E812\OneWorld Client Install\Misc\JDE.INI where x: is the drive on which JD Edwards EnterpriseOne is installed. Ensure that JD Edwards EnterpriseOne client JDE.INI has these settings: [SECURITY] SecurityServer=server_name DataSource=System - 812 DefaultEnvironment=DV812 Default Role=*ALL Row Security=NO_DEFAULT

232

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 12. Working With Signon Security

Setting Up JD Edwards EnterpriseOne Single Signon


You must set up JD Edwards EnterpriseOne Single Signon Security using the procedures described in Chapter 13, Setting Up EnterpriseOne Single Sign-On of the JD Edwards EnterpriseOne Tools 8.96 Security Administration Guide.

Warning
Using default settings may expose a potential security risk. Thus, it is highly recommended to overwrite the single sign-on settings using the single sign-on configuration applications discussed in Chapter 13, Setting Up EnterpriseOne Single Sign-On of the JD Edwards EnterpriseOne Tools 8.96 Security Administration Guide.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

233

234

This page intentionally left blank

Chapter 13. Building and Testing Packages


This section discusses: Understanding Packages Installing Application Fixes Updating the System Path Reviewing Pre-Package Build Issues Reviewing Troubleshooting Tips Building an Alternate Language Package

Understanding Packages
Building and testing packages provides a method to create a package, to define and build a package, to deploy packages to both servers and workstations, and to troubleshoot the packages. These features use a step-by-step director process and include package assembly, package build, and package deployment. Package build is used to set up a workstation or server with Release 8.12 software. Examples scenarios include: Setting up a new workstation. Deploying custom solutions to all or to selected users. Creating a new pathcode for development. Deploying a fix. Changing the package from a full to a partial package on some workstations.

There are options to define three different package types, to build and define packages with custom solutions, and to distribute them through two different deployment options. These options are available to a single server, to a workstation or user, or to selected machines, groups, or individual users. These options can be delivered using just-in-time or scheduled installation methods. You must define, build, and deploy a custom package in order to include any modifications (changed or added business functions or applications) into a package for deployment to workstations (for example, DV812FA or DV812PA). The system administrator is required to build and test packages at the server level. An installer may complete the process for the workstations. These processes can take several hours, depending on the scope of your business. The procedures take place on the Deployment Server in the deployment environment as user JDE. Release 8.12 installation must be completed on the Enterprise Server before building and testing packages. The time required to build packages to the workstation varies depending on the database being used. The package build and assembly process includes many critical tasks that must be successfully completed to in-

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

235

Chapter 13. Building and Testing Packages

stall the packages correctly. This section includes a list of known issues associated with the package build, assembly, and deployment process and gives instructions for avoiding them. Before building a package, review these instructions to successfully complete this process. See Also Package Build in the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for information about how to build and deploy packages. JD Edwards EnterpriseOne Tools 8.96 Development Standards for Business Function Programming Guide for information on how to convert business functions to support Unicode text strings.

Installing Application Fixes


Before you build packages, you should install all application fixes relevant to your business. Application fixes include maintenance packs, ESU bundles, and individual fixes. You should use Change Assistant to find relevant application fixes for system codes associated with the functionality you are using. Change Assistant is a java-based tool that centralizes and economizes the process of searching, identifying, downloading, and deploying many types of software fixes such as ESUs and Tools Releases. It is available free of charge for maintenance paying customers, and can be downloaded from the Update Center. Tests conducted in the Oracle labs on EnterpriseOne have shown that the use of this tool results in a significant reduction in elapsed time as well as a considerable reduction in manual steps - when compared to current search, download, and deploy processes. For instructions on using Change Assistant, refer to Using the Change Assistant in the JD Edwards EnterpriseOne Software Update Guide.

Updating the System Path


Before you build a server package on a Microsoft Windows machine, you must update the SYSTEM path with Microsoft Visual C++ on the Enterprise Server. This path is dependent on the compiler version that you are using. Supported compiler versions vary according to release of JD Edwards EnterpriseOne. Refer to Accessing Minimum Technical Requirements. To update the SYSTEM path: 1. 2. 3. Access the Control Panel. Open System and click the Environment tab. Append the path from your user variables into the path for your system variables. Do not replace the existing system path information. Instead, add a semi-colon to the end of the existing system path and then append the user path information. 4. 5. 6. 7. In your system settings, create the LIB and INCLUDE settings. Copy the LIB and INCLUDE settings from your user to your system. Change the drive letter to point to Visual C++ on your Enterprise Server. Verify these compiler version-dependent path settings (if the paths on your system are different, change them to match these values):

236

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 13. Building and Testing Packages

For the .NET C++ Compiler INCLUDE:

C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\include; C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include; LIB:

C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\lib; C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib; PATH:

C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools; C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\Bin; C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin;

Note
Refer to Accessing Minimum Technical Requirements for details on which compiler version you should use with various applications and tools releases of JD Edwards EnterpriseOne. 8. You must reboot the computer in order for path changes to take effect.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

237

Chapter 13. Building and Testing Packages

Reviewing Pre-Package Build Issues


Check the following items before building packages in order to minimize errors during package builds. Perform each of the relevant tasks on the machine where the package will be built. This section discusses: Verifying Available Space in DBMS Verifying Specific UBEs are Mapped Locally Verifying the OCM Mapping Deleting the BUSOBJ Directories Verifying the F9631 Table Verifying the Server-Side Settings Configuring the Enterprise Server for Simultaneous Builds Adding a Security Override for Running Package Build

238

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 13. Building and Testing Packages

Verifying Available Space in DBMS


Package Deployment will copy the Central Objects tables in your server database to a new set of Metadata Specifications tables in the same database. You must verify that there is enough space available in your Oracle tablespaces for this extra copy. Note the space used by your Central Objects tables and their indexes. The new set of Metadata Specifications tables will use additional space approximately the same size (for a full package) as your current Central Objects tables plus indexes. Those tables are: F98306 F98710 F98711 F98712 F98713 F98720 F98740 F98741 F98743 F98745 F98750 F98751 F98752 F98753 F98760 F98761 F98762

If you do not have enough free space to accommodate these tables, you must increase the size of your tablespaces or drop the metadata specifications tables for old packages no longer in use.

Verifying Specific UBEs are Mapped Locally


To verify that specific UBEs are mapped locally: 1. 2. Open the Object Configuration Manager (OCM). Find each of the following UBEs and make sure each is mapped locally and is active: R9621, R9622, R98825C, and R98825D. GA.Rev8 1/7/2008 239

Copyright 2008, Oracle. All rights reserved.

Chapter 13. Building and Testing Packages

Verifying the OCM Mapping


To verify the OCM mapping: 1. 2. Verify that the F98826 table was generated using Universal Table Browser. Verify that all OCM mappings for all environments are created.

Deleting the BUSOBJ Directories


You should delete all business object (BUSOBJ) directories from the Client and Deployment Server that are running the packages. This directory is located under the pathcode directory. On the Deployment Server, BUSOBJ and object directories are deleted from the Planner pathcode. On the client, these directories are deleted from the pathcode that the user is logged into to build packages.

Verifying the F9631 Table


To verify the F9631 table: 1. 2. 3. Open the F9631 table using UTB. Verify that there are at least 12 records with PDPKGNAME="LITE". If the table is missing any of these records, refresh the table by copying it from the Microsoft MSDE database in the planner pathcode directory. To complete this task, perform the following substeps: a. b. c. Log on to the Deployment Server in the Planner environment. Enter OMW in the Fast Path field to access the Object Management Workbench. In Object Management Workbench, enter your user ID in the User field, and click the Find icon. See JD Edwards EnterpriseOne Tools 8.96 Object Management Workbench Guide. The system displays your default project in the Project window. d. e. f. g. Click the + icon to the left of your default project to display the project components. Select the Objects icon. Click the Search tab in the right-hand pane of Object Management Workbench. Complete the following fields: Category Search Type Search h. Select Object Librarian. Select Object Name. Enter F9631.

Click the Search icon next to the Search field. The F9631 table appears in the Search results window.

240

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 13. Building and Testing Packages

i.

Select the F9631 table and click the left arrow next to the Search pane. Object Management Workbench copies the table icon to the Object folder.

j.

Select the F9631 table in the Object folder and click the Design button next to the Project pane.

Note
You must add yourself to the project as a Developer to access the Design function. The system displays the Object Librarian Table Design screen. k. Select the Table Operations tab, and then click the Copy Table icon. The Copy Table form appears. l. Enter Planner - 812 in the Source data source field.

m. Enter System - 812 in the Destination data source field. n. Click OK to copy the table.

Verifying the Server-Side Settings


To verify the JDE.INI settings on the Enterprise Server: 1. 2. Open the JDE.INI on the Enterprise Server. Verify that the BuildArea setting in the [BSFN BUILD] section points to the PACKAGES directory on the Enterprise Server. For example: \JDEdwards\E812\ddp\packages Verify that the following LinkFlags settings are correct: Ensure that the path to the system/bin32 directory on the Enterprise Server is valid. Ensure that LinkFlags references the path where Release 8.12 is installed.

Configuring the Enterprise Server for Simultaneous Builds


To ensure that simultaneous builds run properly on your Enterprise Server. 1. 2. Open the JDE.INI on the Enterprise Server. In the [BSFN BUILD] sectione, change the SimultaneousBuilds setting to 5 or less (the default is zero, which enables unlimited builds)

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

241

Chapter 13. Building and Testing Packages

Adding a Security Override for Running Package Build


If you are running with security server turned on, you must add a security override so that the package build process can create the metadata repository tables in Central Objects. Adding a security override must be done by a security administrator. To add a security override, you must first add a system user for the Central Objects data source owner, and then add an override for the EnterpriseOne user who will run the package build. This section discusses these tasks: Adding a System User for the Central Objects Data Source Owner Adding an Override for an EnterpriseOne User Running Package Build

Adding a System User for the Central Objects Data Source Owner
To add a system user for the Central Objects data source owner: 1. 2. 3. In P98OWSEC, select the form exit Add System User. On Work with System Users, enter the appropriate data source owner (for example, DV812, PY812 or PD812) in the System User field and select Find. If no values are returned, add the data source owner as a system user by selecting Add and completing the fields on the System User Revisions form: 4. System User Data Source Password Password Verify

Click OK and then Cancel and Close to return to the Work with User Security form.

Adding an Override for an EnterpriseOne User Running Package Build


To add an override for a JD Edwards EnterpriseOne user who is going to run package build: 1. 2. 3. On Work with User Security, enter the user who is going to run package build, and select Find. Select the Form exit, Add Data Source. On Add Data Source, complete the User ID, Data Source, and System User fields.

242

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 13. Building and Testing Packages

Reviewing Troubleshooting Tips


The following troubleshooting tips are designed to help avoid known issues with the package build, assembly, and deployment process. Review these tips when working through the process. The tips are grouped into the following categories: User Tips Deployment Tips

User Tips
Check these items as you build and assemble your packages: When naming your packages, do not use these names: CLIENT SERVER

Verify the assemble and build processes completed. After entering the package information on both the Assembly and Build forms, click the End icon to save the information.

Verify setting on the package definition screen. When selecting servers on the Build Definition form, ensure that a check mark appears next to each server selected. If no check mark appears, highlight the server in the grid and click Select.

Recompress the parent packages. After building an update package that updates the parent package, you must recompress the parent package. This step does not occur automatically.

Verify the location of server packages. When building an update server package, the specified parent package must be stored under the package directory on the server. If the parent package is not under the package directory, the update package does not build.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

243

Chapter 13. Building and Testing Packages

Deployment Tips
Check these items as you deploy your packages: Deploy a package to a CD burner. When deploying the package to a CD burner, the target machine must be created and the CD burner must be attached to this new location. Approve the package. After building a package, change the Deployment Status in the [ATTRIBUTES] section of the package.inf file from No Status Defined to Approved. Without this setting, the package is not visible in the package list when trying to install Release 8.12 from a client workstation. To approve the package: 1. 2. 3. 4. 5. Open the Package Deployment application. Select the Package option. Enter the package name and click Find. Select the package. Click Activate/Deactivate under Row. The package is set to active. Copy the package.inf files. If there are two or more package.inf files that have the same package name listed in the Attributes section, that package will not show up on the install screen. It is possible that a duplicate package might have been created if you copied a package.inf file to back it up. To set the attributes of the package.inf file to that is visible on the install screen: 1. 2. 3. Open the package.inf file for the package that is not showing up on the install screen. Check the Attributes section in the package.inf files of the other package and verify that the package name listed in PackageName= is not duplicated in another package.inf file. If the package name is the same as listed in another package.inf file, change it.

Configure the client package.inf file If you schedule a package to be deployed to a client machine and the client is not prompted for the package installation at login, conflict with a registry setting might exist. Complete the following steps to eliminate this problem: To configure the client package.inf file: 1. 2. Open the client package.inf file. Verify that the value for AppBuildDate is a few minutes or hours earlier than the AppBuildDate in the following registry key: HKEY_LOCAL_MACHINE/Software/jdedwards/OneWorld/install.ini/E812/

244

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 13. Building and Testing Packages

AppBuildDate 3. If the registry also contains a key named FoundationBuildDate, you should verify that the value is a few minutes or hours earlier than the FoundationBuildDate in the following registry key: HKEY_LOCAL_MACHINE/Software/jdedwards/OneWorld/install.ini/E812/ FoundationBuildDate 4. 5. 6. Verify that the DeploymentStatus setting in the package.inf is set to Approved. If the status is not set to Approved, set it to Approved and save the file. Install the package again.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

245

Chapter 13. Building and Testing Packages

Building an Alternate Language Package


A package represents a copy of the central objects at a point in time. It contains replicated objects that Release 8.12 reads at run-time. If custom modifications or text overrides have been made at the time that a software upgrade is performed or to deploy development changes, including a specific language, to a local workstation, build a package and specify which language or languages to include in that package. This action involves the following considerations: Package Build Considerations Package Deployment Considerations

Package Build Considerations


Before beginning to build a language package, verify that the language installation is complete. To build the language package, first define the package. Building the package can take several hours, depending on the size of the package and the number of languages used. This task is completed on the Deployment Server, logged on as user JDE in DEP812. To include language specifications in your package, specify the language in the package definition. The package build process then uses the language preference code. This code is specified as a parameter when building the package. It uses the relational database tables to build the form design aid text and report design aid text specifications. A language package can be a full, update, or partial package.

Caution
When building the client package with translated processing option text, run the build using Microsoft Windows with the system locale set to the appropriate language. If the system locale on the operating system does not match the installed language, the translated text in processing options (POTEXT) will be corrupted. Building server packages that include languages other than English requires that the LocalCodeSet value of the Release 8.12 client matches the LocalCodeSet value of the JDE.INI on the Enterprise Server. If the LocalCodeSet value on the local client differs from the one specified on the Enterprise Server, the server package build fails and errors are logged in the JDE.LOG on the Enterprise Server.

Package Deployment Considerations


A translated package cannot be deployed to a workstation if the appropriate character set is not installed on that workstation. For example, if creating a package containing Japanese text, the workstation must be loaded with Japanese Microsoft Windows to view the Japanese data correctly.

Caution
To transfer translated objects to a server, complete the server package installation procedures. Define each object you have modified for languages. Therefore, track the objects you changed to include them in a package.

Note
To move all objects, call Global Customer Support for assistance. See Also

246

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 13. Building and Testing Packages

JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for more information about transferring objects to the server.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

247

248

This page intentionally left blank

Chapter 14. Installation Utilities


This chapter discusses: Revalidating Software Protection Codes Granting Disk and Registry Access for Microsoft Windows Workstations

Revalidating Software Protection Codes


When you revalidate the software protection codes, you must revalidate both the Deployment Server and workstations. For example, you need to do this if your deployment period or expiration date has expired or if you add modules to the software. The software notifies you seven days before your expiration date.

Revalidating the Deployment Server


You should revalidate the Deployment Server if: The deployment period is about to expire or has expired Modules have been added to the software Additional seats (licenses) to install have been purchased

To revalidate the Deployment Server: 1. 2. 3. 4. 5. 6. 7. 8. To reset the licenses on the Deployment Server, on either a Windows client or the Deployment Server (either one can run the SPC generator program), sign on to JD Edwards EnterpriseOne. Run the Reset EnterpriseOne Security program (R98SRV). On Reset Oracle Security, click Reset Server Security. From Customer Connection, download the update called "SPC", which is associated with SAR # 7549901. On either your Deployment Server or Workstation, run the SPC generator program called SPCSelfService.exe. Select the Release Level and enter your JD Edwards EnterpriseOne Serial Number. If the Release Level is 3 or 4, select the checkbox next to "ALL" in the Licensed Suites section. Enter any number between 1 and 99999 for the number of licenses. Because a number above 5000 will cause JD Edwards EnterpriseOne to run slowly in some instances, it is best to limit the number of licenses to 5000. 9. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

249

Chapter 14. Installation Utilities

10. Note the SPC codes. 11. In JD Edwards EnterpriseOne, on Reset Security, enter the Number of Licenses, Expiration Date (1/1/2899), and SPC codes that were displayed by the SPC generator program. 12. Click OK. The JD Edwards EnterpriseOne are reset. 13. Exit the R98SRV application. 14. Close the SPCSelfService.exe program.

Revalidating Workstations
You might need to revalidate workstations for either of the following reasons: The expiration date has passed. You added modules to JD Edwards EnterpriseOne.

To revalidate a workstation: 1. 2. 3. 4. 5. Log on to the workstation with the appropriate user ID and password. Select any of the environments available to the workstation user. From the Advanced Operations menu (GH9611), select Oracle Licensing Security. On Reset Oracle Security, click Reset Client Security. On Oracle Security Setup, from the Form menu, select Get Authorization. The authorization code appears in the Authorization Code field. 6. Click OK to reset the workstation.

Granting Disk and Registry Access for Microsoft Windows Workstations


Users do not need full administrator access to install the software on the Microsoft Windows workstation; however, they do need disk and registry access. An administrator can grant non-privileged users disk and registry access. This section discusses: Granting Non-Privileged Access to Disk for Microsoft Windows Granting Access to the Software Installation Directory Granting Nonprivileged Access to the Microsoft Windows Registry

250

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 14. Installation Utilities

Granting Non-Privileged Access to Disk for Microsoft Windows


This procedure can be used only by the administrator of the domain. This procedure grants access to the jdeinst.log file and the software installation directory. To grant access to the jdeinst.log file: 1. 2. 3. 4. 5. 6. 7. 8. Create an empty file in the c:\ root directory named jdeinst.log. In Microsoft Windows Explorer, right-click the file and select Properties. Click the Security tab. Click Permissions. Click Add. On Add Users and Groups, double-click the user to be added. Click the pull-down menu in the Type of Access field, and select Full Control. Click OK. Permission to access the jdeinst.log file is granted to the user.

Granting Access to the Software Installation Directory


To grant access to the software installation directory: 1. Create an empty directory named 812 on a drive. This directory will become the installation directory for the software. 2. 3. 4. 5. 6. 7. 8. 9. In Microsoft Windows Explorer, right-click the directory and select Properties. Click the Security tab. Click Permissions. Click Add. On Add Users and Groups, double-click the user to be added. Click the pull-down menu in the Type of Access field, and select Full Control. Enable the setting to Replace Permissions on Subdirectories. Click OK. Permission to access the software installation directory is granted to the user, who now can install the software to this directory.

Granting Nonprivileged Access to the Microsoft Windows


Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 251

Chapter 14. Installation Utilities

Registry
This procedure can be used only by the administrator of the domain. This procedure grants access to HKEY_LOCAL_MACHINE\Software\JDEdwards. To grant nonprivileged access to the Microsoft Windows registry: 1. Run regedt32.exe as follows: a. b. c. 2. 3. 4. 5. Click the Microsoft Windows Start button, and click Run. In the Open field, enter regedt32. Click OK.

Expand the node HKEY_LOCAL_MACHINE on the Local Machine node. Expand the Software node. On the Menu bar, click Edit and then Add Key. In the Key Name field, enter JDEdwards (case-sensitive as shown). Leave the Class field blank.

6. 7. 8. 9.

Click OK. On the Menu bar, click Security, and then select Permissions. On the Registry Key Permissions box, click Add. On the Add Users and Groups box, double-click the user to be added.

10. Click the pull-down menu in the Type of Access field and select Full Control. 11. On Existing Subkeys, select Replace Permissions. 12. Click OK. Permission to access the registry is now granted to the user.

252

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 15. Troubleshooting


This chapter discusses: Using the PORTTEST Checklist Resolving Data Errors Planner Update Special Instructions Orphan Users

Using the PORTTEST Checklist


If the PORTTEST program fails to run, use this checklist to diagnose the problem before calling Global Customer Support. Please have the answers to these questions as well as copies of error messages, your Enterprise Server xxxx, and any error logs, such as JDE.log or JDE_xxxxxx.log. PORTTEST may fail if replication, security server, or transaction processing have been installed incorrectly. If problems occur after the installation of one or more of these services, check the setup of those services for incorrect parameters. Additionally, if PORTTEST reports warnings that indicate data dictionary or company constants are invalid, it may be because the F0010 table is empty. As is true with the full JD Edwards EnterpriseOne installation, this is a normal condition in Pristine and Production environments. General Issues Is the user logged on with administrator privileges? Is the printqueue directory concatenated by the installation? Are the share permissions over the JD Edwards EnterpriseOne directory structure set to FULL? Are all the environment variables set? Is the C compiler installed with the Unicode module? Is the correct version of the C compiler installed? Is ODBC set up for each data source? Can you query the database on the Enterprise Server? Is a PostScript or PCL printer connected to this machine? Yes/No

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

253

Chapter 15. Troubleshooting

Are the printer drivers for this printer installed? Is this printer configured as the default printer? Have the read-only attributes been turned off for all directories and files?

JDE.INI Issues Is your JDE.INI located in the correct directory? Is your JDE.INI located in the correct IIS Directory? Does your JDE.INI have the correct permissions? Are these JDE.INI parameters set properly? [Network Queue Settings] Default Printer OUTQ=your_printer [UBE]

Yes/No

Note
If you use PostScript, is the correct filter set up in the [UBE] section? [DB System Settings]

Note
You should verify all parameters in the [DB System Settings] section, but especially these: Default Env=your_default_environment Default Pathcode=your_default_path_code Server=database_server_name [JDENET] serviceNameListen=port_number serviceNameConnect=port number [INSTALL] E812=valid_path_for_your_install

Communications Issues Are you using DHCP?

Yes/No

254

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 15. Troubleshooting

If not, does an entry exist in the host file for your host? Can you ping your host by name? Can you ping from your host to the workstation by name? If you run Netmon, can you see the host and the workstations? Do the workstations and server agree on the IP address of the server?

Other Issues Were your server map tables F98611 and F986101 edited properly? Run the Verify OCM application and verify: Do only host databases exist? No entries for batch applications exist. Are JD Edwards EnterpriseOne tables accessible to the host? Can you query the F0902 table? Does the PORTTEST program run without error for each valid path code? Does the user name match that of a valid Release 8.12 account? Remember that the user name is case sensitive. Is the password valid for the given Release 8.12 account? Does the environment name match a valid Release 8.12 environment? Remember that the environment name is case sensitive. Does JDENET start and stop properly? After rebooting, do the services start and stop properly? Can you kill the runaway services with Visual C++ debug? If your printer is on a network, are your services running under a network (not a system) account? Are your services running in the administrator group?

Yes/No

If you answered no to any of these questions, your batch application might not run. If you answered yes to all the Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 255

Chapter 15. Troubleshooting

questions, submit a batch application now. If your batch application does not run correctly, turn on error logging and resubmit the batch. This log helps Global Customer Support diagnose the exact problem.

Resolving Data Errors


If you are receiving data warnings against the F0010 table in the Pristine or Production environments, the table might be empty. This is how it is delivered. You can ignore these warnings, load demo data, or load your own data.

Planner Update Special Instructions


The Electronic Software Update (ESU) for the Planner Update Special Instructions was created with special features that updates the Planner pathcode on the Deployment Server. It includes all fixes for Release 8.12 installation and upgrade process. This section describes: Special Instructions for All Special Instructions for OCX Registration

Special Instructions for All


You must run the specialInstrs.bat file to copy certain table records from the ESU database to the Planner databases on the Deployment server. 1. On the Deployment server, browse to this directory: \JDEdwards\812\Planner\Package\PHxxx\Scripts 2. Run the batch file specialInstrs.bat. Note any success or failure messages that appear in the command window. Review the SpecialInstrs.log file that is created in the same directory for details.

Special Instructions for OCX Registration


In some circumstances, Release 8.12 OCX files are not registered. This is known to cause two issues: Object Management Workbench (OMW) fails to start and processing options dialogs do not have labels or text boxes. Run the registration batch file at any time if you encounter either of these issues. SAR 6552762, 6367858. To register the OCX files, you must edit and run the regjdeocx.bat file: 1. 2. 3. On the Deployment Server, drill down into the directory that was created when you expanded this Planner Update (PHxxx). Click on the RegisterOCX directory. Right-click on regjdeocx.bat and select Edit.

256

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 15. Troubleshooting

4. 5. 6.

Change the OCXPATH variable to the correct path for your Deployment Server. Save the file and exit Notepad. Run the regjdeocx.bat to register the OCX files.

Orphan Users
When you run the orphan user script, you must execute the script first from the master database, and then from each delivered database which could include: JDE_CRP JDE_DEVELOPMENT DV812 PS812 PD812 JDE_PRIST812 JDE_PRODUCTION PY812

To troubleshoot database connection errors that are reported by JD Edwards EnterpriseOne: 1. Access Microsoft SQL Query Analyzer and login to the JD Edwards EnterpriseOne database as the JDE user. If there are database connections problems, an error message appears. The error is caused by the introduction of a database whose logins do not match those defined within the SQL Server instance as they are defined by a SQL Server internal number or identifier. You must run the following provided script to correct the condition. 2. From the Microsoft SQL Query Analyzer, click File, Open and navigate to the folder contain the orphan user script. Typically the file is found in this location: c:\JDEdwards\812\mssql 3. Select this script: orphan user with cursor.sql 4. Click the Open button.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

257

Chapter 15. Troubleshooting

5. 6.

Set the database to master. Click the Execute Query button.

258

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan


This section discusses: Understanding Remote Installation Plans Starting Installation Planner Entering Information in Installation Planner Entering Plan Location Information Specifying a Deployment Server Specifying an Enterprise Server Entering HTML Web Server Information Entering Data Server Information Entering Shared Data Source Information Setting Up Environments Replicating Information to Remote Locations Setting Up Data Sources for Environment Concluding the Remote Installation Plan Setup Finalizing the Installation Plan Concluding the Validation Planner Report

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

259

Chapter 16. Creating a Remote Installation Plan

Understanding Remote Installation Plans


Installation Planner is a Release 8.12 application that runs on the Deployment Server. It is a system administration tool that guides through the process of configuring the machines on which your company will run Release 8.12. To set up Release 8.12 for a remote location, create a plan that includes remote locations. Complete the tasks in this section after you create and complete a basic installation plan, and are ready to add the remote locations to the configuration. This section includes information for installing an alternate language. Before you begin, decide what your replication strategy is for Release 8.12. You can use Installation Workbench to copy the system, data dictionary, control, constant and master tables to your remote location. Ongoing replication of the data in these sources must be implemented using third-party software; as of release 8.9, JD Edwards EnterpriseOne no longer has a built-in replication engine. To use replication for Release 8.12, review the processing options for the Installation Planner to make sure that they are set correctly for replication. The information that you provide on the Installation Planner forms, such as database type and Enterprise Server type, determines the information that the system displays on the remaining forms. See Also Reviewing Installation Planner Processing Options for more information about how the processing options for Installation Planner also affect the choices that you are given while setting up your plan

Note
Installation Planner Considerations. Depending on which tables you want to replicate, you are prompted for different data source information. For example, if you choose to replicate the control tables, you are asked to define the control tables data source.

Note
Data Source Considerations. JD Edwards EnterpriseOne provides configured data sources. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration. Only data sources that are referenced in the replication forms appear when you create a remote plan.

260

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

Starting Installation Planner


To start Installation Planner: 1. 2. 3. Log on to Release 8.12 as user JDE with the database password for user JDE. Access the planner environment (JDEPLAN). From the System Installation Tools menu (GH961), click Custom Installation Plan.

4.

On Work with Installation Plans, click Add. The Installation Planner form appears.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

261

Chapter 16. Creating a Remote Installation Plan

Entering Information in Installation Planner


To enter information in Installation Planner:

1.

On Installation Planner, complete these fields: Name Description Status Install Type To Release Enter the name of your remote plan. Enter the description of your remote plan. Select 10 as the status of your remote plan. Select Install. Verify that the release number is E812.

2.

Click OK.

262

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

Entering Plan Location Information


To enter plan location information:

1.

On Location Revisions, complete these fields: Location Description Location Code Enter the location to which this plan applies. The location could be a city, company headquarters, or a division of a company. Enter a description of the location name. For a remote location, enter a 3-character alphanumeric identification code. This 3-character code is used as a prefix for the environments of the remote location, and a suffix is attached for replicated data sources. For example, you might use DAL if the location were Dallas, Texas. In that case, the prototype environment would be named DALPY812, and the business data data source would be named Business Data - CRPDAL. Enter the parent location to which this remote location is attached.

Parent Location 2. Click OK.

The Deployment Server Revisions form appears.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

263

Chapter 16. Creating a Remote Installation Plan

Specifying a Deployment Server


Once a plan location is specified, complete the information for the Deployment Server. You are given the option to enter a new Deployment Server or choose an existing one. For most situations, have a tiered Deployment Server for the remote location. This section discusses: Entering Deployment Server Information Concluding Deployment Server Setup

Entering Deployment Server Information


To enter Deployment Server information: 1. At the Installation Plannerprompt asking if you want to enter new Deployment Server information, click OK to add a Deployment Server.

2.

On Deployment Server Revisions, complete these fields: Machine Usage Machine Name Description Displays the default value of 15 to indicate that this is a Deployment Server. Enter the name of your Deployment Server. Enter a description of the machine name. This name includes the location with which this Deployment Server is associated, and whether or not it is the primary server. Enter the Release 8.12 release number that you are installing, or use the visual assist button to choose one from the list. For example, E812 is the current re-

Release

264

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

Host Type Location Primary User

lease. Displays the default value of 50 to indicate that the server type is an Intel NT. Displays the default location chosen for this plan. Enter the user to whom email is sent when a package is deployed. The default for primary user is JDE.

3.

On the Deployment tab, complete these fields: Primary Deployment Server Server Share Path Enter the hierarchy of the servers. Type 0 (zero) if a primary Deployment Server for the location exists and this is a secondary server. Type 1 if this is the primary Deployment Server for the location. Enter the server share path where you installed Release 8.12 on your Deployment Server. Make sure that this path is specific to your version of the release. For example, for Release 8.12, the path ends with \E812.

4.

Click OK.

Tip
If you enter invalid information into a tab field, a stop sign symbol appears next to the tab name, such as Deployment Server. For more information about the error, click the stop sign icon in the bottom right-hand corner of the form.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

265

Chapter 16. Creating a Remote Installation Plan

Concluding Deployment Server Setup


To conclude the Deployment Server setup: 1. Installation Planner prompts you to decide if you want to add another Deployment Server. To add another Deployment Server, click Yes. Repeat Specifying a Deployment Server . To continue with Installation Planner setup, click No. Continue with the next step. 2. Installation Planner prompts you to decide if want to add an Enterprise Server. To add an Enterprise Server, click OK. Continue with Specifying a Deployment Server .

Note
Add an Enterprise Server if you are using replication in Release 8.12. To skip the Enterprise Server setup and continue with remote Installation Planner, click Skip. Continue with Entering HTML Web Server Information.

Specifying an Enterprise Server


Once the Deployment Server has been specified, add an Enterprise Server by completing the following processes: Entering Enterprise Server Information Entering Enterprise Server Data Source Information

Entering Enterprise Server Information


Enter the base information for the Enterprise Server that you use in this plan.

266

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

1.

On Enterprise Server Revisions, complete or verify these fields: Machine Usage Machine Name Displays the default value 20 to indicate that this is an Enterprise Server. Enter the name of your primary Enterprise Server. The name is case sensitive.

Caution
When using cluster software, use the cluster name, not the machine name. Use the cluster name as the server name when installing Release 8.12. One copy of Release 8.12 will run and be shared by both nodes. Enter a description of the machine. Enter the release number to which this plan applies, or use the visual assist button to choose one from the list, such as E812. Click the visual assist button and choose the type of Enterprise Server that you are adding to the plan, such as Intel NT . Enter the default location chosen for this plan. Enter the user to whom email is sent when a package is deployed. The default for primary user is JDE.

Description Release Host Type Location Primary User

2.

On the Enterprise tab, complete these fields: Port Number Displays the default value for this field, which is supplied the JDE.INI. Change the port number for this Enterprise Server to a unique value, for example, 6014. Displays the system-supplied default value when you enter the host type. Enter the type of database that you want to use for data sources on the Enterprise Server. Value is O for Oracle .

Logical Machine Name Database Type

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

267

Chapter 16. Creating a Remote Installation Plan

Server Map Data Source Installation Path

Displays the system-supplied default value when you enter the host type. Enter the installation directory path where you want to install Release 8.12 on your Enterprise Server. Make sure that this path is specific to your version of the release. For example, for release 8.12, this path ends with \E812. You may need to add the drive x: to the path. Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. The system provides a default value for this field, but you can change it.

Deployment Server Name

3.

Click OK. A message box appears to enable you to specify whether you want to enter custom data sources or take the default data sources. Proceed to Entering Shared Data Source Information.

Entering Enterprise Server Data Source Information


After specifying Enterprise Server information, enter the data source information for the Enterprise Server you will use in this plan. This section discusses: Specifying Custom or Default Data Source Information Entering the Oracle Connect String Verifying Custom Server Map Source Information Adding Another Enterprise Server

Specifying Custom or Default Data Source Information


Release 8.12 asks whether to enter custom data sources or take the default data sources for the Enterprise Server you just added. Choose one of the following options: To enter custom data sources, click OK. Skip to Verifying Custom Server Map Source Information . To accept Release 8.12 default data sources, click Take Defaults. This option limits your customization choices.

Note
The following screen that prompts you to enter the Oracle connect string is only displayed if you choose Take Defaults. That is, if you choose to define your own data source, you will be prompted to enter the oracle connect string on a different screen.

Entering the Oracle Connect String


268 GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

To enter the Oracle connect string:

1. 2.

On Oracle Connect String, enter the connect string for the Enterprise Server, and then click OK. Skip to Adding Another Enterprise Server .

Verifying Custom Server Map Source Information


To verify custom information for the Server Map data source:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

269

Chapter 16. Creating a Remote Installation Plan

1.

On Data Source Revisions, verify your Server Map data source information.

Tip
Data Source Considerations. JD Edwards EnterpriseOne supplies configured data sources. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration. 2. Click OK.

Adding Another Enterprise Server


To add another Enterprise Server, select one of these options: To add another Enterprise Server, click Yes. Repeat processes, starting with Entering Enterprise Server Information . To continue with Installation Planner setup, click No. The Machine/Server Types form appears.

270

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

Entering HTML Web Server Information


Note
For Release 8.12, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web Server. Functionally, these terms are all synonymous. However, this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software.

Warning
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface. To enter HTML Web Server information:

1.

On HTML Application Server, click OK to define a new HTML Server, or click Select to choose from a list of existing HTML Servers.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

271

Chapter 16. Creating a Remote Installation Plan

If you choose Select, you are presented with the Machine Search table, from which you can make your selection.

272

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

2. 3.

On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server. On HTML Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Location Primary User The default value of 30 indicates that this is a HTML Web Server. Enter the name of your HTML Web Server. The name is case sensitive and must not exceed 10 characters. Enter a description of the HTML Web Server machine. Enter E812 to indicate the release number that you are installing. The default value of 50 specifies the server type as Intel NT. Select the correct server type. The location chosen for this plan appears in this field by default. The user to whom an email is sent when a package is deployed. The default for primary user is listed in the JDE.INI.

4.

On the HTML tab, complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). This is the protocol used by the HTML Web Server. Valid values are http or https. This is the Domain Name System (DNS) host name of the HTML Web Server. For example: www.oracle.com. This is the port number the HTML Web Server is listening to.

Protocol Server URL

HTTP Port

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

273

Chapter 16. Creating a Remote Installation Plan

For HTTP, the typical port number is 80. For HTTPS, the typical port number is 443. However, you can choose to implement a HTML Web Server using a different port number. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne. For JD Edwards EnterpriseOne Release 8.12, the value is 6014. Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. Redirector The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system. Explicit The user can specify an explicit servlet name in this field. In this Servlet case, the redirector functionality cannot be used. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need. The Portal servlet is: /jdedwards/servlet/com.jdedwards.portal.PortalBuilderServlet

JDENET Listen Port

Default Login

The HTML servlet is: /jdedwards/servlet/com.jdedwards.runtime.virtual.VCServlet Installation Path Enter the installation directory path to which you are installing Release 8.12 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running. For Release 8.12 on Oracle Applications Servers, the path ends with E1HTMLServer. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator. 5. Click OK.

274

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

6.

To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

275

Chapter 16. Creating a Remote Installation Plan

Entering Data Server Information


To enter Data Server information:

1.

On Data Server, select one of these options: OK If your database resides on a separate server, click OK to continue entering unique Data Server information. Select Click this button to select an existing Data Server. Skip Click this button if you do not want to define a Data Server . Continue the Installation Planner with the environment selection in step 6.

276

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

2.

On Data Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Displays the default value of 25 to indicate that this is a Data Server. Enter the name of your Data Server. The name must not exceed 10 characters. Enter a description of the machine. Enter the Release 8.12 release number you are installing, for example, E812. Select the type of Data Server that you are adding to the plan. Valid values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client - NT 90 Client - Win NT Displays the location chosen for this plan appears in this field by default. Enter the user to whom an email is sent once a package is deployed. The default for primary user is JDE.

Location Primary User

3.

On the Data tab, complete these field: Data Source Type Select the type of data source. Value is O for Oracle .

4.

Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

277

Chapter 16. Creating a Remote Installation Plan

5.

A message box appears to enable you to add another Data Server. Click Yes to add another Data Server. Repeat the procedure in step 2 of this task. Click No to continue with Installation Planner setup.

6.

On Data Source, you are prompted to enter shared data source information for the specific environment that you previously selected to install. Click OK to continue entering unique shared data source information, or click Take Defaults to select the default data for the shared data sources.

7.

On Location, select Yes to add another location or No to continue with Installation Planner.

Entering Shared Data Source Information


To enter or confirm information for data sources that are shared across all of your environments, complete these tasks: Specifying (Custom or Default) Shared Data Source Setup Information Verifying the Data Dictionary Data Source Verifying the Object Librarian Data Source Verifying the System Data Source

Specifying (Custom or Default) Shared Data Source Setup Information


You are prompted for the data source information for the shared data sources. Choose one of the following options: To use the Release 8.12 data sources, click Take Defaults and continue with the task entitled: Setting Up Environments . This option limits your customization choices. Click OK to enter the data sources. Verify the data source information.

Verifying the Data Dictionary Data Source


To verify the data source for Data Dictionary:

278

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

1. 2.

On Data Source Revisions, verify the accuracy of the Data Dictionary data source. Click OK.

Verifying the Object Librarian Data Source


To verify the data source for Object Librarian:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

279

Chapter 16. Creating a Remote Installation Plan

1. 2.

On Data Source Revisions, verify the accuracy of the Object Librarian data source. Click OK.

Verifying the System Data Source


To verify the data source for System:

280

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

1. 2.

On Data Source Revisions, verify the accuracy of the settings for the System data source. Click OK. The Environment Selection screen appears.

See Also For more information about System data source fields or fields for other data sources mentioned in this process, see Understanding Data Source Charts.

Setting Up Environments
By default, Release 8.12 configures your system using values for typical environments. Depending on the options chosen when you set up your plan, Release 8.12 displays one or more of the following parameters, which you can customize in the following tasks: Environments Data load options Languages

Environments
You can customize any of these parameters by clearing the default option on the Environment Selection form. As you move through the plan, the Installation Planner displays a customization form for each parameter that you turn off. Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 281

Chapter 16. Creating a Remote Installation Plan

1.

On Environment Selection, clear the options for those parameters that you want to customize.

Note
The parameters that display might vary depending on which options you selected at the beginning of the planning process. 2. Click OK.

Note
If you checked the default option for all parameters, skip to the next task. Use the following tasks to customize each of the parameters listed above. Installation Planner displays customization forms only for those parameters for which were turned off the default options. Skip the tasks for those parameters that were left turned on. 3. Continue with the following relevant tasks: Selecting an Environment

Adding a Custom Environment


to add a custom environment: 1. 2. Click Add to add a new environment, or click Copy to copy the settings of an existing environment. Enter the environment information on the screen and click Next.

282

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

3. 4.

Select share, or create a pathcode and click Next. Enter pathcode information on the screen and click Next.

Selecting an Environment
The Select Environment form appears. Environments prefixed with J are required for the HTML Web Server. To select an environment:

On Select Environments, double-click the environment that you want to define. To set up multiple environments, choose and define them one at a time. This screen appears after the following tasks are completed.

Replicating Information to Remote Locations


The options on this form determine whether the software will configure data sources and mappings for the remote location. Ongoing replication must be implemented using third-party software. To replicate information to remote locations:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

283

Chapter 16. Creating a Remote Installation Plan

1.

On Control/System Replication, select the Replication Setup tab and select the following options to replicate information to remote locations: Replicate Control Tables Select this option to configure the control tables data source for replication. Clear the option if you do not want to replicate the control tables. Select this option to configure the constant tables for replication. Clear the option if you do not want to replicate the constant tables. Select this option to configure the master tables for replication. Clear the option if you do not want to replicate the master tables.

Replicate Constant Tables

Replicate Master Tables

2.

Select the Data Load tab.

284

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

3.

On the Data Load tab, choose from the following options to copy selected tables to the remote locations: Load Control Tables Select this option to copy the control tables automatically from the base to the remote locations. Clear the option if you do not want to copy the control tables automatically. Select this option to copy the constant tables automatically from the base to the remote locations. Clear the option if you do not want to copy the constant tables automatically. Select this option to copy the master tables automatically from the base to the remote locations. Clear the option if you do not want to copy the master tables automatically.

Load Constant Tables

Load Master Tables

Note
To edit or change the versions of the R98403 program that copy the control tables, constant tables, and master tables, click the Edit or Search buttons next to their respective versions.

Note
If you have defined multiple locations, the system will prompt you to complete sets of the Replication Setup and Data Load screens for each location. 4. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

285

Chapter 16. Creating a Remote Installation Plan

Setting Up Data Sources for Environment


After specifying which tables to replicate, use the following processes to set up environment data sources: Beginning the Data Source Setup for Environment Verifying the Data Source for Control Tables Setting up the Data Source for Business Data Select Another Environment

Beginning the Data Source Setup for Environment


You are prompted to set up data sources for each environment that you chose. Choose one of the following options: To manually enter the data sources, click OK, and continue with Verifying the Data Source for Control Tables. To accept the Release 8.12 default data sources, click Take Defaults, and continue with Select Another Environment . This option limits your customization choices.

Setting up the Data Source for Business Data


To set up the Business Data data source:

286

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

1.

On Data Source Revisions, set up or verify the data source information for your business data.

Note
Be sure that this data source points to either the existing production data source you want to upgrade or a copy of it. 2. Click OK The Select Environments form appears so that you can define another environment, if necessary.

Verifying the Data Source for Control Tables


To verify the Control Tables data source:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

287

Chapter 16. Creating a Remote Installation Plan

1. 2.

On Data Source Revisions, verify your Control Tables data source. Click OK.

Select Another Environment


To select another environment:

288

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

1. 2. 3.

On Select Environments, choose the next environment that you want to define. Repeat all tasks in Replicating Information to Remote Locations and Setting Up Data Sources for Environment. After defining all of your environments, click Close. The Remote Location Packages window appears.

You can push delivered full packages to remote locations when you run the Location Workbench. 4. Select one of the following options:

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

289

Chapter 16. Creating a Remote Installation Plan

Click Yes to view a list of packages to push to the remote location. Click Take Defaults to push all available packages to the remote location. Continue with Concluding the Remote Installation Plan Setup.

Click No if you do not want to push packages to the remote location. Continue with Concluding the Remote Installation Plan Setup.

If you click Yes, the Select Remote Location Packages form appears.

5.

On Select Remote Location Packages, choose a package from the list and click the Deselect icon in the Row menu.

Note
Click the corresponding icon in the Row menu to select or cancel the selection of a package. 6. Click Select to push the chosen packages.

Concluding the Remote Installation Plan Setup


After concluding the environment setup, you can choose to enter another plan location or finalize your remote installation plan. You are prompted to add another location. To add another location, click Yes.

290

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

Repeat all tasks for adding a location, starting with Entering Plan Location Information. To conclude remote Installation Planner setup, click No. Continue with Finalizing the Installation Plan below.

Finalizing the Installation Plan


Installation Planner finalizes your installation plan automatically. A message appears to let you know that the installation plan is finalized. When the plan is finalized: The status is set to 20. This value means that several adjustments to OCM mappings and tables were made according to your plan. The following tables are now updated: Release Master table (F00945). Path Code Master table (F00942). Create OCM (F986101). Package Plan table (F98404). Machine Detail table (F9651). Table Conversion Scheduler (F98405). Language table (F984031) - if you are installing an alternate language. To finalize the installation plan: 1. Click OK to exit the concluding message box and initiate the Planner Validation Report.

If the processing option default was chosen, Planner Validation Report automatically prompts you to run this report. If the processing option default was not chosen, on the tree view of your plan, click Validate to initiate the Planner Validation Report.

Concluding the Validation Planner Report


1. 2. 3. On Report Output Destination, choose On Screen or To Printer, and then click OK. Review the report to confirm that all records were validated. After reviewing the report, on the Batch Versions form, click Close.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

291

Chapter 16. Creating a Remote Installation Plan

For more information about Installation Planner Validation Report (R9840B), refer to Working with Reports. 4. 5. On Work With Installation Plans, click Expand to review the plan that you created. Run Installation Workbench for this installation plan. For more information about Installation Workbench, refer to Working With Installation Workbench.

292

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 16. Creating a Remote Installation Plan

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

293

294

This page intentionally left blank

Chapter 17. Adding a Server to an Existing Configuration


This section contains the procedures for adding additional servers to your configuration. Use these procedures only if you have already defined and run your initial installation plan and set up your environments. This section discusses: Assumptions about Adding a Server to an Existing Installation Plan Starting Installation Planner Entering a Plan Description Entering a Plan Location Selecting Additional Server Types Entering Deployment Server Information Specifying an Enterprise Server Entering HTML Web Server Information Entering Data Server Information Entering Shared Data Source Information Setting Up Environments Setting Up Environment Data Sources Finalizing the Installation Plan Finalizing the Installation Plan Concluding the Validation Planner Report Configuring Additional Servers

Assumptions about Adding a Server to an Existing Installation Plan


This table outlines assumptions for adding a server to an existing Installation Plan phase as a whole. Personnel Logon Status Prerequisites Concurrent Tasks Copyright 2008, Oracle. All rights reserved. Installer. On the Deployment Server, logged on as user JDE with the database password for user JDE, in the planner environment. Verify that the Deployment Server is installed and the Release 8.12 directory is shared. None. GA.Rev8 1/7/2008 295

Chapter 17. Adding a Server to an Existing Configuration

296

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Starting Installation Planner


Begin your installation plan by logging on to Release 8.12 and starting Installation Planner. To start the Installation Planner: 1. 2. 3. 4. Log on to Release 8.12 as user JDE with the database password for user JDE. Access the planner environment (JDEPLAN). From the System Installation Tools menu (GH961), double-click Add-on Servers Plan. On Work with Installation Plans, click Add. Release 8.12 displays the following warning:

5.

Click OK. The Installation Planner form appears.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

297

Chapter 17. Adding a Server to an Existing Configuration

Entering a Plan Description


After starting Installation Planner, enter basic plan information, such as plan name and description. To enter a plan description:

1.

On Installation Planner, complete the following fields: Name Description Status To Release Enter the name of your installation plan. Enter the description of your installation plan. Select 10 as the status of your installation plan. Verify that the release number is E812.

2.

Click OK. The Location Search form appears.

298

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Entering a Plan Location


Once basic plan installation information is entered, you must choose an existing plan location. For most instances, choose the location defined during your base installation. To enter a plan location:

1.

On Location Search, choose a location and click Select.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

299

Chapter 17. Adding a Server to an Existing Configuration

2.

On Location Revisions, click OK.

300

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Selecting Additional Server Types


Once a plan location is specified, specify the types of servers you want to add to your installation plan. To select additional server types:

1. 2.

On Server Add, check the types of servers that you want to add to your configuration. Click OK. A Server Revisions form appears in the order listed on the Server Add form for each type of server that you chose.

3.

Continue with the relevant sections that follow.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

301

Chapter 17. Adding a Server to an Existing Configuration

Entering Deployment Server Information


When choosing to add an additional Deployment Server to your plan, the Deployment Server Revisions form appears. To enter Deployment Server information:

1.

On Deployment Server Revisions, complete the following fields: Machine Name Description Release Location Primary User Enter the name of your additional Deployment Server. Enter a description of the machine. Enter E812. Displays the system-provided default value chosen for this plan. This identifies the user to whom email is sent when a package is deployed. The default for primary user is JDE.

2.

On the Deployment tab, verify or complete the following fields: Primary Deployment Server Server Share Path This field indicates the hierarchy of the servers. The default value for a secondary Deployment Server is 0. Enter the server share path where you installed Release 8.12 on your Deployment Server. Verify that this path matches your version of the release; for example, for Release 8.12, the server share path is \E812.

3.

Click OK.

302

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Tip
If you enter invalid information into a tab field, a stop sign icon appears next to the tab name, such as Deployment Server. For more information about the error, click on the stop sign icon in the bottom right-hand corner of the form. 4. You are prompted to add another Deployment Server. To add another Deployment Server, click Yes. Repeat Entering Deployment Server Information . To continue with the additional server plan, click No. Continue with the relevant sections that follow.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

303

Chapter 17. Adding a Server to an Existing Configuration

Specifying an Enterprise Server


This section discusses: Entering Enterprise Server Information Entering Enterprise Server Data Source Information

Entering Enterprise Server Information


To enter the base information for the Enterprise Server that you use in this plan:

1.

On Enterprise Server Revisions, complete or verify the following fields: Machine Usage Machine Name Displays the default value of 20 to indicate that this is an Enterprise Server. Enter the name of your primary Enterprise Server. The name is casesensitive.

Caution
When using cluster software, use the cluster name, not the machine name. Use the cluster name as the server name when installing Release 8.12. One copy of Release 8.12 will run and be shared by both nodes. Enter a description of the machine. Enter the release number to which this plan applies, or use the visual assist

Description Release

304

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Host Type Location Primary User

button to choose one from the list, such as E812. Click the visual assist button and choose the type of Enterprise Server that you are adding to the plan, such as Intel NT . Enter the default location chosen for this plan. Enter the user to whom email is sent when a package is deployed. The default for primary user is JDE.

2.

On the Enterprise tab, complete these fields: Port Number Displays the default value for this field, which is supplied the JDE.INI. Change the port number for this Enterprise Server to a unique value, for example, 6014. Displays the system-supplied default value when you enter the host type. Enter the type of database that you want to use for data sources on the Enterprise Server. Value is O for Oracle. Displays the system-supplied default value when you enter the host type. Enter the installation directory path where you want to install Release 8.12 on your Enterprise Server. Make sure that this path is specific to your version of the release. For example, for release 8.12, this path ends with \E812. You may need to add the drive x: to the path. Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. The system provides a default value for this field, but you can change it.

Logical Machine Name Database Type Server Map Data Source Installation Path

Deployment Server Name

3.

Click OK. A message box appears prompting you to enter custom data sources or take the default data sources. Proceed to Entering Shared Data Source Information.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

305

Chapter 17. Adding a Server to an Existing Configuration

Entering Enterprise Server Data Source Information


After specifying Enterprise Server information, enter the data source information for the Enterprise Server you will use in this plan. This section discusses: Specifying Custom or Default Data Source Information Entering the Oracle Connect String Verifying Custom Server Map Data Source Information Adding another Enterprise Server

Specifying Custom or Default Data Source Information


You are prompted to enter custom data sources or take the default data sources for the Enterprise Server you just added. Choose one of the following options: To enter custom data sources, click OK. Skip to Verifying Custom Server Map Data Source Information . To accept default data sources, click Take Defaults. This option limits your customization choices.

Note
The following screen that prompts you to enter the Oracle connect string is only displayed if you choose Take Defaults. That is, if you choose to define your own data source, you will be prompted to enter the oracle connect string on a different screen.

Entering the Oracle Connect String


To enter the Oracle connect string:

306

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

1. 2.

On Oracle Connect String, enter the connect string for the Enterprise Server, and then click OK. Skip to Adding another Enterprise Server .

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

307

Chapter 17. Adding a Server to an Existing Configuration

Verifying Custom Server Map Data Source Information


To verify custom Server Map data source information:

1.

On Data Source Revisions, verify your Server Map data source information.

Tip
Default data sources are configured as completely as possible. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration. 2. Click OK.

Adding another Enterprise Server


On the prompt to add another Enterprise Server, choose one of the following options: To add another Enterprise Server, click Yes. Repeat processes, starting with Entering Enterprise Server Information . To continue with Installation Planner setup, click No. The Machine/Server Types form appears.

308

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Entering HTML Web Server Information


Note
For Release 8.12, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web Server. Functionally, these terms are all synonymous. However, this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software.

Warning
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface. To enter HTML Web Server information:

1.

On HTML Application Server, click OK to define a new HTML Server, or click Select to choose from a list of existing HTML Servers.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

309

Chapter 17. Adding a Server to an Existing Configuration

If you choose Select, you are presented with the Machine Search table, from which you can make your selection.

310

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

2. 3.

On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server. On HTML Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Location Primary User The default value of 30 indicates that this is a HTML Web Server. Enter the name of your HTML Web Server. The name is case sensitive and must not exceed 10 characters. Enter a description of the HTML Web Server machine. Enter E812 to indicate the release number that you are installing. The default value of 50 specifies the server type as Intel NT. Select the correct server type. The location chosen for this plan appears in this field by default. The user to whom an email is sent when a package is deployed. The default for primary user is listed in the JDE.INI.

4.

On the HTML tab, complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). This is the protocol used by the HTML Web Server. Valid values are http or https. This is the Domain Name System (DNS) host name of the HTML Web Server. For example: www.oracle.com. This is the port number the HTML Web Server is listening to.

Protocol Server URL

HTTP Port

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

311

Chapter 17. Adding a Server to an Existing Configuration

For HTTP, the typical port number is 80. For HTTPS, the typical port number is 443. However, you can choose to implement a HTML Web Server using a different port number. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne. For JD Edwards EnterpriseOne Release 8.12, the value is 6014. Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. Redirector The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system. Explicit The user can specify an explicit servlet name in this field. In this Servlet case, the redirector functionality cannot be used. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need. The Portal servlet is: /jdedwards/servlet/com.jdedwards.portal.PortalBuilderServlet

JDENET Listen Port

Default Login

The HTML servlet is: /jdedwards/servlet/com.jdedwards.runtime.virtual.VCServlet Installation Path Enter the installation directory path to which you are installing Release 8.12 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running. For Release 8.12 on Oracle Applications Servers, the path ends with E1HTMLServer. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator. 5. Click OK.

312

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

6.

To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

313

Chapter 17. Adding a Server to an Existing Configuration

Entering Data Server Information


To enter Data Server information:

1.

On Data Server, choose one of these options: OK If your database resides on a separate server, choose click OK to continue entering unique Data Server information. Select Click this option to select an existing Data Server. Skip Click this option if you do not want to define a Data Server. Continue with the Planner with the environment selection in step 6 of this task.

314

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

2.

On Data Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Displays the default value of 25 to indicate that this is a Data Server. Enter the name of your Data Server. The name must not exceed 10 characters. Enter a description of the machine. Enter the Release 8.12 release number you are installing, for example, E812. Select the type of Data Server that you are adding to the plan. Valid values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client - NT 90 Client - Win NT Displays the location chosen for this plan appears in this field by default. Enter the user to whom an email is sent once a package is deployed. The default for primary user is JDE.

Location Primary User

3.

On the Data tab, complete the following field: Data Source Type Select the type of data source. Value is O for Oracle .

4.

Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

315

Chapter 17. Adding a Server to an Existing Configuration

5.

A message box appears to enable you to add another Data Server. Click Yes to add another Data Server. Repeat the procedure in step 2 of this task. Click No to continue with Installation Planner setup.

6.

On Data Source, you are prompted to enter shared data source information for the specific environment that you previously selected to install. Click OK to continue entering unique shared data source information, or click Take Defaults to select the default data for the shared data sources.

7.

On Location, select Yes to add another location or No to continue with Installation Planner.

316

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Entering Shared Data Source Information


To enter or confirm information for data sources that are shared across all of your environments, complete these tasks: Specifying (Custom or Default) Shared Data Source Setup information Verifying the Data Dictionary Data Source Verifying the Object Librarian Data Source Verifying the System Data Source

Specifying (Custom or Default) Shared Data Source Setup information


When you are prompted for the data source information for the shared data sources, choose one of these options: To use the Release 8.12 data sources, click Take Defaults and continue with the task entitled: Setting Up Environments . This option limits your customization choices. Click OK to enter, verify, or modify the data source information.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

317

Chapter 17. Adding a Server to an Existing Configuration

Verifying the Data Dictionary Data Source


To verify the Data Dictionary data source:

1. 2.

On Data Source Revisions, verify the accuracy of the Data Dictionary data source. Click OK.

318

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Verifying the Object Librarian Data Source


To verify the Object Librarian data source:

1. 2.

On Data Source Revisions, verify the accuracy of the Object Librarian data source. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

319

Chapter 17. Adding a Server to an Existing Configuration

Verifying the System Data Source


To verify the System data source:

1. 2.

On Data Source Revisions, verify the accuracy of the settings for the System data source. Click OK. The Environment Selection screen appears.

See Also For more information about System data source fields or fields for other data sources mentioned in this process, refer to Understanding Data Source Charts.

320

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Setting Up Environments
By default, Release 8.12 configures your system using values for typical environments. Depending on the options chosen when you set up your plan, Release 8.12 displays one or more of the following parameters, which you can customize in these tasks: Environments Data load options Languages

You can customize any of these parameters by turning off the default option on the Environment Selection form. As you move through the plan, Release 8.12 displays a customization form for each parameter that you turn off.

1.

On Environment Selection, clear the options for those parameters that you want to customize.

Note
The parameters that are available vary depending on the options that you selected at the beginning of the planning process. 2. Click OK.

Note
If you selected the default option for all parameters, skip to Setting Up Environment Data Sources . Use the following tasks to customize each of the parameters listed above. Release 8.12 displays customiza-

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

321

Chapter 17. Adding a Server to an Existing Configuration

tion forms only for those parameters for which were cleared of the default options. Skip the tasks for those parameters that were selected. 3. Continue with the following relevant tasks: Selecting an Environment Specifying Environment Data Load Parameters Selecting Languages

Adding a Custom Environment


To add a custom environment: 1. 2. 3. 4. Click Add to add a new environment, or click Copy to copy the settings of an existing environment. Enter the environment information on the screen and click Next. Select share, or create a pathcode and click Next. Enter pathcode information on the screen and click Next.

322

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Selecting an Environment
The Select Environment form appears. Environments prefixed with J are required for the HTML Web Server. To select an environment:

On Select Environments, double-click the environment that you want to define. To set up multiple environments, choose and define them one at a time. This screen appears after the following tasks are completed.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

323

Chapter 17. Adding a Server to an Existing Configuration

Specifying Environment Data Load Parameters


If you cleared Default Data Load on the Environment Selection form, the Data Load Parameters form appears. To specify environment data load parameters:

Note
The data load radio buttons on this form are no longer applicable as of JD Edwards EnterpriseOne Release 8.12 because data is automatically loaded by the Platform Pack Installer. For additional details, refer to Loading Data (Demo Data and Production Data).

324

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Selecting Languages
To select languages:

1. 2. 3. 4.

On Language Selection, to set up a language for the selected environment, choose the appropriate language. From the Row menu, click Select. Repeat the above steps until all your languages have been selected. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

325

Chapter 17. Adding a Server to an Existing Configuration

Setting Up Environment Data Sources


Once the Environments have been set up, it is necessary to set up the data sources for those environments. If you created a custom environment, data source information is generated from the data source template provided with JD Edwards EnterpriseOne. See Also To modify this template, see the JD Edwards EnterpriseOne Tools 8.96 Configurable Network Computing Implementation Guide.

Selecting an Environment Data Source Setup Option


When you are prompted to set up data sources for the environment you just configured, click OK to manually enter the data sources, continue with the following task, or click Take Defaults to accept the Release 8.12 default data sources.

Setting Up the Data Source for Business Data


To set up the data source for business data:

1. 2.

On Data Source Revisions, verify the data source for your Business Data. From the Form menu, click Advanced.

326

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

3.

Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

327

Chapter 17. Adding a Server to an Existing Configuration

Setting Up the Data Source for Central Objects


To set up the data source for central objects:

1. 2.

On Data Source Revisions, verify the information for your Central Objects data source. Click OK.

Caution
The Central Objects data source must be Unicode. Select Advanced from the Form menu to verify Unicode is checked. Also ensure that LOB is selected.

328

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Note
The Central Objects data sources are specific to the pathcode.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

329

Chapter 17. Adding a Server to an Existing Configuration

Setting Up the Data Source for Control Tables


To set up the data source for control tables:

1.

On Data Source Revisions, verify the accuracy of the Control Tables data source. Data Source Name Server Name Object Owner ID Verify the name of the data source. Verify the name of the Enterprise Server. Enter the name of the owner of this object

Note
The Control Tables data sources are specific to the environment and pathcode. 2. Click OK.

330

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Verifying the Data Source for Versions


To verify the data source for versions:

1. 2.

On Data Source Revisions, verify the accuracy of the Versions data source. Click OK.

Note
Versions data sources are specific to the pathcode, and the Unicode flag on the Advanced Form must be checked.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

331

Chapter 17. Adding a Server to an Existing Configuration

Finalizing the Installation Plan


Installation Planner finalizes your installation plan automatically. A message appears to let you know that the installation plan is finalized. When the plan is finalized: The status is set to 20, which signals that several adjustments to tables were made according to your plan. Create the OCM. Modify the JDE.INI . The following tables are upgraded: Release Master table (F00945) Path Code Master table (F00942) Package Plan table (F98404) Machine Detail table (F9651) Language table (F984031), if you are installing an alternate language

To finalize the installation plan: 1. Click OK to exit the concluding message box and initiate the Planner Validation Report. If you chose the default processing option, Planner Validation Report automatically prompts you to run this report. If you did not choose the default processing option, on the tree view of your plan, click Validate to initiate the Planner Validation Report.

332

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Concluding the Validation Planner Report


To conclude the validation planner report: 1. 2. 3. On Report Output Destination, choose On Screen or To Printer, and then click OK. Review the report to confirm that all records were validated. After reviewing the report, on the Batch Versions form, click Close. For more information about Installation Planner Validation Report (R9840B), refer to Working with Reports. 4. 5. On Work With Installation Plans, click Expand to review the plan that you created. Run Installation Workbench for this installation plan. For more information about Installation Workbench, refer to Working With Installation Workbench.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

333

Chapter 17. Adding a Server to an Existing Configuration

Configuring Additional Servers


To configure any additional servers that you have added: 1. 2. 3. Create the tablespace (SVM812) for the Server Map data source. Set up owner (JDE812) on additional Enterprise Servers. After configuring your database and server, use Installation Workbench to allocate and configure software and resources. When using the Installation Workbench for adding servers, the Table Conversion and the Specification Merge workbenches do not appear because they are not needed. 4. When adding a server plan for a HTML Web Server, using the P9654A program, you must add all environments prefixed with J to the Enterprise Server and generate a Server Map data source.

334

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 17. Adding a Server to an Existing Configuration

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

335

336

This page intentionally left blank

Chapter 18. Creating a Language-Only Installation Plan


This section discusses: Understanding Language-Only Installation Plans Reviewing Requirements for a Language Installation Installing Languages on the Deployment Server Running Installation Planner Running Installation Workbench Verifying Enterprise Server Requirements Verifying Workstation Requirements Completing the Language Installation Building and Deploying Alternate Language Packages

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

337

Chapter 18. Creating a Language-Only Installation Plan

Understanding Language-Only Installation Plans


To make the language-only installation as easy and quick as possible, you should use the procedures in this chapter when installing an alternate language or multiple languages for the first time. These tasks will help you organize the pre-installation preparation required for a language-only installation: Install alternate languages at the same time that you install Release 8.12, or after completing a working installation or upgrade. Implement a language-only plan only for installations in which a language has not been previously installed.

It is important that you complete all tasks in this chapter to achieve a successful language installation.

Reviewing Requirements for a Language Installation


To review the basic requirements for performing a language installation: 1. Review the language installation process. The detailed information regarding the language installation process is found in Language Process Overview . 2. Review the disk space requirements. Verify that the disk space requirements are available for each language and each environment that you are installing on the deployment and Enterprise Servers. 3. Review the directory structure. The detailed information about directory structures is found in the Understanding JD Edwards EnterpriseOne Directory Structures chapter of this guide.

338

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 18. Creating a Language-Only Installation Plan

Installing Languages on the Deployment Server


To install languages on the Deployment Server: 1. Insert the JD Edwards EnterpriseOne language CD into the CD drive. If the autorun does not automatically start the Language Installer program, you can manually run the setup.exe.

2.

On JD Edwards Installation Manager, click the link for the language that you want to install. In this example, the language CD is for French.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

339

Chapter 18. Creating a Language-Only Installation Plan

3.

On the Welcome screen, click Next.

340

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 18. Creating a Language-Only Installation Plan

4.

On Client Workstation Installation Setup Type, complete these fields: Select Setup Type Install Path Ensure the radio button for your language is selected. The Installer provides a default path to the existing client installation on this machine: c:\JDEdwards\812 You must verify that this drive and path is valid for your installation. You can use the browse function to locate the directory.

5.

Click Finish.

The Clinet Workstation Install Progress displays the progress of the language installation.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

341

Chapter 18. Creating a Language-Only Installation Plan

When the installation finishes, the Oracle Deployment Server Setup form indicates whether the installation was successful. 6. On Installation Complete, click OK.

Note
To access more than one language within the same package, you need to build a custom package that includes all available languages.

342

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 18. Creating a Language-Only Installation Plan

Running Installation Planner


Once you have installed languages on the Deployment Server, run Installation Planner. These tasks highlight the critical language-related stages of this operation. Accessing Installation Planner Entering Information into Installation Planner Selecting Custom or Default Parameters Selecting an Environment

Accessing Installation Planner


For details on accessing the Installation Planner, refer to Creating a Custom Installation Plan .

Note
If you choose a custom installation plan, you can choose which language to install for each environment. This section assumes you are defining a custom plan.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

343

Chapter 18. Creating a Language-Only Installation Plan

Entering Information into Installation Planner


To enter information into the Installation Planner:

1. 2.

On Installation Planner, enter the basic plan information. In the Include Language area, select the Language Only option.

344

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 18. Creating a Language-Only Installation Plan

Selecting Custom or Default Parameters


To select custom or default parameters:

1.

From Environment Selection, all environments and languages are the default values. Clear the options for Default Environment and Default Languages if you want to specify which language or languages to install for each environment.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

345

Chapter 18. Creating a Language-Only Installation Plan

Selecting an Environment
To select an environment:

Choose the environment for which you wish to install a language. The Language Selection form appears.

346

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 18. Creating a Language-Only Installation Plan

Selecting a Language
To select a language:

1. 2. 3. 4.

On Language Selection, to set up a language for the selected environment, choose the appropriate language. From the Row menu, click Select. Repeat the above steps until all your languages have been selected. Click OK.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

347

Chapter 18. Creating a Language-Only Installation Plan

Running Installation Workbench


After you create the language-only plan, you must run it through a series of workbenches in order to load the language tables to the appropriate data sources. The language installation process is the same for every database. To run the Installation Workbench: 1. 2. Go to Working With Installation Workbench. Complete the procedures for Control Table Workbench and Specification Table Merge Workbenches. The control tables, data dictionary, and central objects will be loaded by the Control Table Workbench and the Specification Table Merge Workbench.

Verifying Enterprise Server Requirements


To verify Enterprise Server requirements: 1. 2. 3. Verify that the Enterprise Server hardware and software meet all requirements. Verify that the Enterprise Server disk space meets all requirements. Verify that the JDE.INI settings for local code set and code page values are set for your preferred language. These values are found in the National Language Support tables in Language Process Overview .

Verifying Workstation Requirements


To verify workstation requirements: 1. 2. 3. 4. 5. Verify that the workstation hardware and software meet all requirements. Install the appropriate language character set to a workstation. Complete the step to verify the JDE.INI settings on the Deployment Server for Interactive Runtime, Install, and Network Queues. Complete the tasks in Installing the Workstations for Developers and System Administrators. Verify that the group and user profiles are set up properly.

Completing the Language Installation


Once you have verified that the Enterprise Server and workstation hardware and software meet your language install requirements, you can complete the installation. See the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for more information about how to transfer language specifications to the Enterprise Server.

348

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 18. Creating a Language-Only Installation Plan

Building and Deploying Alternate Language Packages


Once you have concluded the installation, it is time to build and deploy the alternate language packages. See Package Build in the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for the details of including a language or creating language-only packages.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

349

350

This page intentionally left blank

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures


The charts in this section illustrate the directory structures for JD Edwards EnterpriseOne on the Deployment Server, the Enterprise Server, and Workstations. You must understand these directory structures to verify that you installed or upgraded Release 8.12 correctly. Assuming you use the recommended shared path names, the process does not delete or overlay your previous release. You will have the Release 8.12 directories in addition to your existing directories. The recommended configuration is for all business functions to be mapped to the server. The only exception to this rule is a client development environment in which case all business functions should be mapped locally. This chapter discusses: Deployment Server Directory Structure Language Directory Structure Enterprise Server Directory Structure Workstation General Directory Structure

Deployment Server Directory Structure


After you install Release 8.12 on the Deployment Server, you should have the following directory structure: Directory Name \JDEdwards \JDEdwards\BPMBroker \JDEdwards\BPMBroker\JRE \JDEdwards\E812 \JDEdwards\E812\bpm \JDEdwards\E812\CD Templates \JDEdwards\E812\CD Templates\Esu & Asu \JDEdwards\E812\CD Templates\Esu & Asu\planner \JDEdwards\E812\CD Templates\Esu & Asu\planner\Package \JDEdwards\E812\CD Templates\Esu & Asu\planner\Package\PKGNAME \JDEdwards\E812\Client \JDEdwards\E812\Database \JDEdwards\E812\path_code where path_code is DV812, PD812, PS812, or PY812 Database setup scripts. Path codes. Product Packaging files. Contents

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

351

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\path_code\bin32 \JDEdwards\E812\path_code\EOne \JDEdwards\E812\path_code\include \JDEdwards\E812\path_code\lib32 \JDEdwards\E812\path_code\make \JDEdwards\E812\path_code\obj \JDEdwards\E812\path_code\package \JDEdwards\E812\path_code\package\DATA \JDEdwards\E812\path_code\package\DATACOMP \JDEdwards\E812\path_code\package\DV812FA \JDEdwards\E812\path_code\package\DV812PA \JDEdwards\E812\path_code\res \JDEdwards\E812\path_code\source \JDEdwards\E812\path_code\spec \JDEdwards\E812\path_code\work \JDEdwards\E812\Hosts \JDEdwards\E812\Hosts\AS400

Contents

Host scripts and programs. Partial host installation objects. The files reside here until you install the platform-specific objects. Partial host installation objects. The files reside here until you install the platformspecific objects. Partial host installation objects. The files reside here until you install the platformspecific objects. Partial host installation objects. The files reside here until you install the platformspecific objects. Partial host installation objects. The files reside

\JDEdwards\E812\Hosts\Hp9000

\JDEdwards\E812\Hosts\IntelNT

\JDEdwards\E812\Hosts\Linux

\JDEdwards\E812\Hosts\RS6000

352

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name

Contents here until you install the platformspecific objects.

\JDEdwards\E812\Hosts\Sun

Partial host installation objects. The files reside here until you install the platformspecific objects. Media objects for runtime.

\JDEdwards\E812\InstallLogs \JDEdwards\E812\MediaObj \JDEdwards\E812\misc \JDEdwards\E812\misc\MSDE \JDEdwards\E812\OneWorld Client Install Package build files for web development client.

\JDEdwards\E812\OneWorld Client Install\Font \JDEdwards\E812\OneWorld Client Install\Misc \JDEdwards\E812\OneWorld Client Install\Push Install Listener \JDEdwards\E812\OneWorld Client Install\ThirdParty \JDEdwards\E812\OneWorld Client Install\ThirdParty\BPMBroker \JDEdwards\E812\OneWorld Client Install\ThirdParty\MOBILESQL \JDEdwards\E812\OneWorld Client Install\ThirdParty\MSDE \JDEdwards\E812\OneWorld Client Install\ThirdParty\Synchrologic \JDEdwards\E812\OneWorld Client Install\ThirdParty\WebDevFeature \JDEdwards\E812\Planner \JDEdwards\E812\PACKAGE_INF \JDEdwards\E812\PACKAGE_INF\Feature_Inf \JDEdwards\E812\planner \JDEdwards\E812\Planner\bin32 Application and business function .DLL files Bitmap objects for applications Planner Environment files

\JDEdwards\E812\Planner\data \JDEdwards\E812\Planner\res \JDEdwards\E812\Planner\spec \JDEdwards\E812\Planner\res\avi files \JDEdwards\E812\Planner\res\formlines \JDEdwards\E812\Planner\res\icons \JDEdwards\E812\Planner\res\images \JDEdwards\E812\Planner\res\treebmps

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

353

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\planner\spec \JDEdwards\E812\PrintQueue \JDEdwards\E812\SolutionExplorer \JDEdwards\E812\SolutionExplorer\Data \JDEdwards\E812\SolutionExplorer\Data\+ Concept To Opportunity \JDEdwards\E812\SolutionExplorer\Data\+ Consumption To Reorder \JDEdwards\E812\SolutionExplorer\Data\+ Demand To Available \JDEdwards\E812\SolutionExplorer\Data\+ Implementation Approach \JDEdwards\E812\SolutionExplorer\Data\+ Manage Materials \JDEdwards\E812\SolutionExplorer\Data\+ Manage The Business \JDEdwards\E812\SolutionExplorer\Data\+ Order To Cash \JDEdwards\E812\SolutionExplorer\Data\+ Procure To Pay \JDEdwards\E812\SolutionExplorer\Data\RNT3 \JDEdwards\E812\SolutionExplorer\Data\SK_FOUNDATION_DOCUMENTS \JDEdwards\E812\SolutionExplorer\Data\style \JDEdwards\E812\SolutionExplorer\Data\styles \JDEdwards\E812\SolutionExplorer\PortalLite \JDEdwards\E812\System \JDEdwards\E812\System\bin32 \JDEdwards\E812\System\classes \JDEdwards\E812\System\classes\samples \JDEdwards\E812\System\Include

Contents

System files.

Production business function header (.H) files.

\JDEdwards\E812\System\Include\metadata \JDEdwards\E812\System\IncludeV \JDEdwards\E812\System\IncludeV\unicode \JDEdwards\E812\System\Lib32 Import libraries for business functions.

\JDEdwards\E812\System\Libv32 \JDEdwards\E812\System\Locale \JDEdwards\E812\System\Locale\Iconv \JDEdwards\E812\System\Locale\Uconvtab \JDEdwards\E812\System\Locale\Xml \JDEdwards\E812\System\Models \JDEdwards\E812\System\OWPatrol \JDEdwards\E812\System\OWPatrol\owkm \JDEdwards\E812\System\OWPatrol\owkm\images \JDEdwards\E812\System\OWPatrol\owkm\km \JDEdwards\E812\System\OWPatrol\owkm\psl \JDEdwards\E812\System\Resource 354 GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\System\Resource\cidfont \JDEdwards\E812\System\Resource\cmap \JDEdwards\E812\System\Resource\encoding \JDEdwards\E812\System\Resource\iccprofile \JDEdwards\E812\System\Resource\truetype \JDEdwards\E812\systemcomp \JDEdwards\E812\_jvm \JDEdwards\E812\_jvm\bin \JDEdwards\E812\_jvm\bin\client \JDEdwards\E812\_jvm\lib \JDEdwards\E812\_jvm\lib\applet \JDEdwards\E812\_jvm\lib\cmm \JDEdwards\E812\_jvm\lib\ext \JDEdwards\E812\_jvm\lib\fonts \JDEdwards\E812\_jvm\lib\i386 \JDEdwards\E812\_jvm\lib\im \JDEdwards\E812\_jvm\lib\images \JDEdwards\E812\_jvm\lib\images\cursors \JDEdwards\E812\_jvm\lib\security \JDEdwards\E812\_jvm\lib\zi \JDEdwards\E812\_uninst

Contents

Language Directory Structure


The following table outlines the Release 8.12 software directory structure for the Release 8.12 language CD. You must understand this directory structure to help you verify that the language was installed correctly. Directory Name \LANGUAGE \Helps \SolutionExplorer \SolutionExplorer\PLANNER \SolutionExplorer\PLANNER\DATA Definition Name of language for JD Edwards EnterpriseOne language installation. Language help files. Solution Explorer language files. Planner path code. Language database.

Enterprise Server Directory Structure


After you run Host Workbench, you should have the following Enterprise Server directory structure: Directory Name \JDEdwards\E812\DDP\DV812 Definition

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

355

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\PrintQueue \JDEdwards\E812\DDP\system \JDEdwards\E812\DDP\DV812\bin32 \JDEdwards\E812\DDP\DV812\data \JDEdwards\E812\DDP\DV812\include

Definition

Production business function include (.h) files. Import libraries for business functions. Object code for business functions. Business function source. Replicated local objects.

\JDEdwards\E812\DDP\DV812\lib32

\JDEdwards\E812\DDP\DV812\make \JDEdwards\E812\DDP\DV812\obj

\JDEdwards\E812\DDP\DV812\res \JDEdwards\E812\DDP\DV812\source \JDEdwards\E812\DDP\DV812\spec \JDEdwards\E812\DDP\DV812\work \JDEdwards\E812\DDP\DV812\res\AVI Files \JDEdwards\E812\DDP\DV812\res\FormLines \JDEdwards\E812\DDP\DV812\res\Icons \JDEdwards\E812\DDP\DV812\res\images \JDEdwards\E812\DDP\DV812\res\treebmps \JDEdwards\E812\DDP\system\Bin32 \JDEdwards\E812\DDP\system\Classes \JDEdwards\E812\DDP\system\Explorer \JDEdwards\E812\DDP\system\Generator \JDEdwards\E812\DDP\system\Include \JDEdwards\E812\DDP\system\IncludeV \JDEdwards\E812\DDP\system\Lib32 \JDEdwards\E812\DDP\system\Libv32 \JDEdwards\E812\DDP\system\Locale \JDEdwards\E812\DDP\system\Models \JDEdwards\E812\DDP\system\OWPatrol \JDEdwards\E812\DDP\system\Resource \JDEdwards\E812\DDP\packages\PD812FA \JDEdwards\E812\DDP\packages\PD812FA\bin32 \JDEdwards\E812\DDP\packages\PD812FA\include \JDEdwards\E812\DDP\packages\PD812FA\obj System include files. System executables.

356

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\packages\PD812FA\source \JDEdwards\E812\DDP\packages\PD812FA\spec \JDEdwards\E812\DDP\packages\PD812FA\obj\CAEC \JDEdwards\E812\DDP\packages\PD812FA\obj\CALLBSFN \JDEdwards\E812\DDP\packages\PD812FA\obj\CCONVERT \JDEdwards\E812\DDP\packages\PD812FA\obj\CCORE \JDEdwards\E812\DDP\packages\PD812FA\obj\CCRIN \JDEdwards\E812\DDP\packages\PD812FA\obj\CDBASE \JDEdwards\E812\DDP\packages\PD812FA\obj\CDDICT \JDEdwards\E812\DDP\packages\PD812FA\obj\CDESIGN \JDEdwards\E812\DDP\packages\PD812FA\obj\CDIST \JDEdwards\E812\DDP\packages\PD812FA\obj\CDMDSCH \JDEdwards\E812\DDP\packages\PD812FA\obj\CEPM \JDEdwards\E812\DDP\packages\PD812FA\obj\CFIN \JDEdwards\E812\DDP\packages\PD812FA\obj\CFND \JDEdwards\E812\DDP\packages\PD812FA\obj\CHRM \JDEdwards\E812\DDP\packages\PD812FA\obj\CINSTALL \JDEdwards\E812\DDP\packages\PD812FA\obj\CINV \JDEdwards\E812\DDP\packages\PD812FA\obj\CLOC \JDEdwards\E812\DDP\packages\PD812FA\obj\CLOG \JDEdwards\E812\DDP\packages\PD812FA\obj\CMFG \JDEdwards\E812\DDP\packages\PD812FA\obj\CMFGBASE \JDEdwards\E812\DDP\packages\PD812FA\obj\COBJLIB \JDEdwards\E812\DDP\packages\PD812FA\obj\COPBASE \JDEdwards\E812\DDP\packages\PD812FA\obj\CPAY \JDEdwards\E812\DDP\packages\PD812FA\obj\CRES \JDEdwards\E812\DDP\packages\PD812FA\obj\CRUNTIME \JDEdwards\E812\DDP\packages\PD812FA\obj\CSALES \JDEdwards\E812\DDP\packages\PD812FA\obj\CTC \JDEdwards\E812\DDP\packages\PD812FA\obj\CTOOL \JDEdwards\E812\DDP\packages\PD812FA\obj\CTRAN \JDEdwards\E812\DDP\packages\PD812FA\obj\CTRANS \JDEdwards\E812\DDP\packages\PD812FA\obj\CWARE \JDEdwards\E812\DDP\packages\PD812FA\obj\CWRKFLOW \JDEdwards\E812\DDP\packages\PD812FA\obj\JDBTRG1 \JDEdwards\E812\DDP\packages\PD812FA\obj\JDBTRG2 \JDEdwards\E812\DDP\packages\PD812FA\obj\JDBTRG3 \JDEdwards\E812\DDP\packages\PD812FA\source\CAEC \JDEdwards\E812\DDP\packages\PD812FA\source\CALLBSFN \JDEdwards\E812\DDP\packages\PD812FA\source\CCONVERT \JDEdwards\E812\DDP\packages\PD812FA\source\CCORE Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008

Definition

357

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\packages\PD812FA\source\CCRIN \JDEdwards\E812\DDP\packages\PD812FA\source\CDBASE \JDEdwards\E812\DDP\packages\PD812FA\source\CDDICT \JDEdwards\E812\DDP\packages\PD812FA\source\CDESIGN \JDEdwards\E812\DDP\packages\PD812FA\source\CDIST \JDEdwards\E812\DDP\packages\PD812FA\source\CDMDSCH \JDEdwards\E812\DDP\packages\PD812FA\source\CEPM \JDEdwards\E812\DDP\packages\PD812FA\source\CFIN \JDEdwards\E812\DDP\packages\PD812FA\source\CFND \JDEdwards\E812\DDP\packages\PD812FA\source\CHRM \JDEdwards\E812\DDP\packages\PD812FA\source\CINSTALL \JDEdwards\E812\DDP\packages\PD812FA\source\CINV \JDEdwards\E812\DDP\packages\PD812FA\source\CLOC \JDEdwards\E812\DDP\packages\PD812FA\source\CLOG \JDEdwards\E812\DDP\packages\PD812FA\source\CMFG \JDEdwards\E812\DDP\packages\PD812FA\source\CMFGBASE \JDEdwards\E812\DDP\packages\PD812FA\source\COBJLIB \JDEdwards\E812\DDP\packages\PD812FA\source\COPBASE \JDEdwards\E812\DDP\packages\PD812FA\source\CPAY \JDEdwards\E812\DDP\packages\PD812FA\source\CRES \JDEdwards\E812\DDP\packages\PD812FA\source\CRUNTIME \JDEdwards\E812\DDP\packages\PD812FA\source\CSALES \JDEdwards\E812\DDP\packages\PD812FA\source\CTC \JDEdwards\E812\DDP\packages\PD812FA\source\CTOOL \JDEdwards\E812\DDP\packages\PD812FA\source\CTRAN \JDEdwards\E812\DDP\packages\PD812FA\source\CTRANS \JDEdwards\E812\DDP\packages\PD812FA\source\CWARE \JDEdwards\E812\DDP\packages\PD812FA\source\CWRKFLOW \JDEdwards\E812\DDP\packages\PD812FA\source\JDBTRG1 \JDEdwards\E812\DDP\packages\PD812FA\source\JDBTRG2 \JDEdwards\E812\DDP\packages\PD812FA\source\JDBTRG3 \JDEdwards\E812\DDP\system\Generator\WEB-INF \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes \JDEdwards\E812\DDP\system\Generator\WEB-INF\lib \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpm \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpmweb \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\database \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas 358 GA.Rev8 1/7/2008

Definition

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \printqueuecenter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\redirector \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\taskexplorer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\workflow \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\beans \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\behaviorcom \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\cache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\datatypes \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\exception \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\gui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\imagegenerator \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\logging \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\owsecurity \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\resource \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\spec \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\timer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\util

Definition

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

359

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\webgui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\gui\explorer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\gui\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\log4j \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\saw \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\test \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\cache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\util\ftp \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\smtp \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\threadpool \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpm\utils \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \bpmweb\broker \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \bpmweb\Handlers \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpmweb\Util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\base \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\explorer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards

Definition

360

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \database\impl \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\database\jdb \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\application \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\as400 \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\businessview \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\condensed \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\config \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\datacache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\formatter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\logical \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\oracle \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\physical \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\resultset \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008

Definition

361

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \database\impl\retry \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\security \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\signon \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\sql \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\sqlserver \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\standalone \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\transaction \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\transform \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\trigger \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\udb \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\usage \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\base \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\bootstrap \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\company 362 GA.Rev8 1/7/2008

Definition

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\ocm \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\role \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\security \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\serviceobj \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\spec \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\udc \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\bsfnplugin \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\exception \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\net \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\res \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\security \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\services \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\transaction \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\anonuser \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\env \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\userpref

Definition

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

363

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\ifc \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\beans \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\components \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\js \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\envcheck \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\hr \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\importer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\linkCenter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\reportcenter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\sarsystem \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal 364 GA.Rev8 1/7/2008

Definition

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \components\webcheck \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\workcenter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\reportcenter\client \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\beans \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\client \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\components \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\datahandler \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\defaults \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\gui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\js \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\unittest \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\client \JdeTreeControl \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \envcheck \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \importer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \linkcenter

Definition

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

365

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \login \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \rss \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \saw \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \search \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \webcheck \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \importer\upload \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\util\cache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\util\gui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\base \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\er \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\event \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\interfac \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards

Definition

366

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \runtime\model \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\swing \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine\form \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine\version \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\er\erobjects \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\engine \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\jniinclude \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\model \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\view \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\model\form \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\model\grid \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\input Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008

Definition

367

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\output \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\xapi \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\form \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\grid \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\version \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawagent \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawchart \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawcomm \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawdb \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawjavalog \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawjdbj \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawlog \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawsuperagent \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\smc \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\smcgui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services\login \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \services\objectlookup \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards 368 GA.Rev8 1/7/2008

Definition

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \services\login\display \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\kernel \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\lib \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\net \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\xml \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\kernel\jdesaw \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\lib\cache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\as400 \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\db \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\proxy \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\xml\test \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\actions \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\db \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\filters \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\gui Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008

Definition

369

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\launchers \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\gui\tagext \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \util\imagegenerator \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \workflow\DesignEngine \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \workflow\monitoring \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\workflow\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\serverproxy \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\test \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtse \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtsm \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtsr \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\xtse\adapters \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\xtsr\adapters \JDEdwards\E812\DDP\system\IncludeV\unicode \JDEdwards\E812\DDP\system\Locale\Iconv \JDEdwards\E812\DDP\system\Locale\Uconvtab \JDEdwards\E812\DDP\system\Locale\Xml \JDEdwards\E812\DDP\system\OWPatrol\owkm \JDEdwards\E812\DDP\system\OWPatrol\owkm\images \JDEdwards\E812\DDP\system\OWPatrol\owkm\km \JDEdwards\E812\DDP\system\OWPatrol\owkm\psl \JDEdwards\E812\DDP\system\Resource\cidfont \JDEdwards\E812\DDP\system\Resource\cmap \JDEdwards\E812\DDP\system\Resource\encoding

Definition

370

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Name \JDEdwards\E812\DDP\system\Resource\font \JDEdwards\E812\DDP\system\Resource\iccprofile \JDEdwards\E812\DDP\system\Resource\truetype \JDEdwards\E812\DDP\system\Resource\font\pfm

Definition

Workstation General Directory Structure


After you install Release 8.12 installation on a Workstation, you should have the following local directory structure: Directory Structure \E812 \E812\Log \E812\output \E812\packages \E812\PD812 \E812\PrintQueue \E812\queues \E812\system \E812\PD812\bin32 \E812\PD812\spec \E812\PD812\spec\JDE \E812\queues\control \E812\queues\outqueue \E812\system\bin32 \E812\system\Classes \E812\system\include \E812\system\includev \E812\system\lib32 \E812\system\libv32 \E812\system\locale \E812\system\owpatrol \E812\system\resource \E812\system\Classes\samples \E812\system\includev\unicode \E812\system\locale\iconv \E812\system\locale\uconvtab \E812\system\locale\xml \E812\system\owpatrol\owkm \E812\system\owpatrol\owkm\images \E812\system\owpatrol\owkm\km

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

371

Chapter 19. Understanding JD Edwards EnterpriseOne Directory Structures

Directory Structure \E812\system\owpatrol\owkm\psl \E812\system\resource\cidfont \E812\system\resource\cmap \E812\system\resource\encoding \E812\system\resource\font \E812\system\resource\iccprofile \E812\system\resource\truetype \E812\system\resource\font\pfm

372

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 20. Understanding Data Source Charts


This chapter discusses these data sources: Business Data Central Objects Control Tables Data Dictionary Local Logic Object Librarian Language Local Server Map System Versions

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

373

Chapter 20. Understanding Data Source Charts

Business Data
This chart lists the characteristics of the Business Data data source. Field Data Source Name (list includes possible sources) Business Data - PROD Business Data - CRP Business Data - TEST Business Data - PS812 Data Source Use Data Source Type Database Server Name Platform Advanced Exit Clustered Unicode Use Decimal Shift Use Julian Dates Support for Locking Updates OCM Data Source Use Table Owner LOB Data Type Support Object Owner ID (list includes possible owner Ids) PRODDTA CRPDTA TESTDTA PS812DTA Database Name (list includes possible databases) Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Connect string for the database Selected Selected Selected Selected Blank Selected DB O Name of the machine where your database resides Platform type Selected Blank Selected Selected Selected Selected Blank Selected Selected Valid Value for Oracle

374

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 20. Understanding Data Source Charts

Central Objects
This chart lists the characteristics of the Central Objects data source. Field Data Source Name (list includes possible sources) Central Objects - PROD Central Objects - CRP Central Objects - TEST Central Objects - PS812 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) PD812 PY812 DV812 PS812 Library Name Library List Name Database Name (list includes possible databases) Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected DB O Oracle

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

375

Chapter 20. Understanding Data Source Charts

Control Tables
This chart lists the characteristics of the Control Tables data source. Field Data Source Name (list includes possible sources) Control Tables - Prod Control Tables - CRP Control Tables - Test Control Tables - PS812 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) Control Tables - Prod Control Tables - CRP Control Tables - PS812 Control Tables - Test Library Name Library List Name Database Name (list includes possible databases) Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected DB O Oracle

376

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 20. Understanding Data Source Charts

Data Dictionary
This chart lists the characteristics of the Data Dictionary data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Oracle Data Dictionary - 812 DB O DD812 Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

377

Chapter 20. Understanding Data Source Charts

Logic
This chart lists the characteristics of the Logic data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source iSeries BLOB Data Source Oracle Name of the machine where your database resides SVR Blank SVM812 Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected Blank

378

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 20. Understanding Data Source Charts

Object Librarian
This chart lists the characteristics of the Object Librarian data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Valid Value for Oracle Object Librarian - 812 DB O OL812 Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

379

Chapter 20. Understanding Data Source Charts

Language
This chart lists the characteristics of the Language data source, which applies to the MSDE database on the Deployment Server. Field Data Source Name (list includes possible sources) Valid Value for MSDE Language Language 812 For example, French 812. Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) Library Name Library List Name Database Name (list includes possible databases) DB N Blank Blank Blank Language JDELanguage_F812 Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source iSeries BLOB Support Local LOCAL Blank Blank Blank Blank Blank Blank

380

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 20. Understanding Data Source Charts

Local
This chart lists the characteristics of the Local data source, which applies to the MSDE database on the Deployment Server. Field Data Source Name (list includes possible sources) Valid Value for MSDE Local JDELocal - DV812 JDELocal - PS812 JDELocal - PD812 JDELocal - PY812 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) Library Name Library List Name Database Name (list includes possible databases) DB N dbo Blank Blank JDELocal JDEPlan812 JDECTL812 JDEDD812 JDESY812 JDEVL812 JDEOL812 JDEData812 Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Local LOCAL Selected Selected Selected Selected Blank Blank

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

381

Chapter 20. Understanding Data Source Charts

Server Map
This chart lists the characteristics of the Server Map data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name DDL Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Valid Value for Oracle machinename - 812 Server Map DB O SVM812 Blank Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Selected Selected

382

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 20. Understanding Data Source Charts

System
This chart lists the characteristics of the System data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Valid Value for Oracle System - 812 DB O SY812 Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

383

Chapter 20. Understanding Data Source Charts

Versions
This chart lists the characteristics of the Versions data source. Field Data Source Name (list includes possible sources) Versions - PD812 Versions - PY812 Versions - DV812 Versions - PS812 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) PD812 PY812 DV812 PS812 Library Name Library List Name Database Name (list includes possible databases) Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected DB O Valid Value for Oracle

384

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 21. Major Technical Tables


This chapter lists the major technical tables in the Release 8.12 data sources. This chapter does not list any Release 8.12 application tables. All technical media storage objects (GTxxx) are listed at the end of this chart. Many tables exist in multiple data sources. Some tables exist in data sources not noted here.

Note
The Local pathcode data source refers only to local databases that are path code specific. In the chart below, Local pathcode could represent more than one data source, depending on the number of path codes you use. Pathcode is one or more of the following path codes: PY812 DV812 PS812 PD812 DEP812

Note
The xxxx Local data source refers only to the local database on the Deployment Server, which is used by the planner environment. * Specific tables in the list below reflect language information, and contain a language preference code that is translated by JD Edwards EnterpriseOne. Table F0004D* Data Source Control Tables Description Purpose

UDC Alternate Language Contains the User Defined Code (UDC) key, language key, and text for headers in the F0004 table. Provides UDC type descriptions for alternate languages. UDC Alternate Language Contains UDC key, language key, and text for detail in the F0005 table. Provides UDC value descriptions for alternate languages. Stores text OLE references and image references. Stores glossary text and media objects for all languages.

F0005D*

Control Tables

F00165*

Business Data xxxx Media Objects storage Data Dictionary - 812 Object Librarian - 812 Business Data Local Data Dictionary Local Object Librarian Local System - 812 Planner - 812 System Local Library List User

F0092

Contains one record per user with initial menu, initial program, and whether to enable fast path.

F00921*

System - 812

User Display Preferences GA.Rev8 1/7/2008

Contains one record per user with date 385

Copyright 2008, Oracle. All rights reserved.

Chapter 21. Major Technical Tables

Table

Data Source Planner - 812 System Local

Description

Purpose format, date separator, DW prefix, and language preference.

F00922

System - 812 Planner - 812 System Local

User Display Preferences Tagfile

Contains one record per user with workstation configuration name. This table is used with the F00050 table.

F00924

System - 812 Planner - 812 System Local

User Install Packages

Contains one record per user for each authorized package.

F0093

System - 812 Planner - 812 System Local

Library List Control

Contains a list, by user, of authorized environments.

F0094

System - 812 Planner - 812 System Local

Library List Master file

Contains master file information for an environment.

F00941

System - 812 Planner - 812 System Local

Environment Detail EO

Contains one record per environment, with release and path code.

F00942

System - 812 Planner - 812 System Local

Object Path Master file

Contains one record per path code with the data source for the specification files and the server path for the other development objects (.DLL, source, headers). Contains one record per release, with the data source for system tables and the environments server path.

F00945

System - 812 Planner - 812 System Local

Release Master

F00946

System - 812 Planner - 812 System Local

Release Compatibility Map Contains information used to map major release levels to determine forward and backward compatibility.

F00948

System - 812 Planner - 812 System Local

Release Data Source Map

Contains information used to map a specific type of data source to a release level, such as Object Librarian, data dictionary, or versions list data sources. Stores security attributes (one record for each user or group).

F00950

System - 812 System Local

Security Workbench table

F00960

System - 812

Machine/ Group Identifica- Stores a list of all workstations that intion stalled Release 8.9 to scheduled packGA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

386

Chapter 21. Major Technical Tables

Table

Data Source System Local

Description

Purpose ages.

F83100*

System - 812 System Local

Data Title

Series of definitions of data titles. Each row is the definition or specification of the date title. Provides soft coded RDA text. Gives each period number an associated description. Provides soft coded RDA text. Lists Release 8.9 tasks (Solution Explorer only). Groups tasks listed in the F9000 table in logical (parent/child) tree order (ActivEra only). Provides descriptions of tasks listed in the F9000 table (ActivEra only). Describes the attributes of variants listed in this table. A variant performs a series of designated tasks (nodes) within a tree order defined in the F9001 table (ActivEra only). Provides translated text for descriptions listed in the F9005 table (ActivEra only). Defines which nodes (tasks) are run within a variant and the names of any tasks dynamically renamed within a variant (ActivEra only). Provides translated text for descriptions listed in the F9006 table (ActivEra only).

F83110*

System - 812 System Local

Column Headings

F9000 F9001

Control Table Control Table

Task Master Task Relationships

F9002 F9005

Control Table Control Table

Task Descriptions Variant Description

F9005D F9006

Control Table Control Table

Alternate Variant Descriptions Variant Detail

F9006D F9010 F9020

Control Table Control Table Control Table

Alternate Variant Detail Descriptions Environment Setup Answers ActivEra Qualifier Rules Header

Defines rule names used by ActivEra. Rules are applied to conditionally execute an individual task or task relationship (tree order). Lists conditional statements within rules listed in the F9020 table (ActivEra only). Stores indexes of HTML documents associated with specific tasks (ActivEra only).

F9022 F9030

Control Table Control Table

ActivEra Qualifier Rules Detail Documentation Crossreference

F9050

Control Table

Rough-cut Answer Depend- Defines the hierarchical means of eliminency ating system codes and subsequent applications which do not apply within a specified system configuration (ActivEra only). Favorites Relationship Properties Categorizes business views on a parent/ child format.

F91100 F91100D* F91300

System - 812 System - 812 System - 812

Favorites All Descriptions Stores alternate descriptions for different languages. Scheduled Job Master GA.Rev8 1/7/2008 387

Copyright 2008, Oracle. All rights reserved.

Chapter 21. Major Technical Tables

Table F91310 F91320 F91330 F91400 F91410 F91420 F91430 F91500 F91510 F9200

Data Source System - 812 System - 812 System - 812 System - 812 System - 812 System - 812 System - 812 System - 812 System - 812 Data Dictionary Data Dictionary Local

Description Scheduled Job Parameters Job Schedule Scheduled Job Override Printer Info Report Director Templates Report Director Templates Sequence Items Report Director Template Smart Field Activation Smart Field Template Criteria

Purpose

Contains the design templates for reports that users can create. Helps users manipulate data sequencing. Creates a list showing all data items belonging to a smart field template. Stores a subset of selection criteria.

Application Header for Tip Contains application names or tools of the Day names where tips reside. Tip Details for Tip of the Day Data Item Master Stores tip texts and a key to modify the sequence. Contains the relational breakdown of data dictionary. Contains display text for each data field for language, data item, and product code reporting. Used when data items descriptions requested. Data dictionary row and column text for all languages* * The language preference code for data dictionary applies to text only. Text includes row and column headings, a compressed description, and glossaries.

F9202*

Data Dictionary Data Dictionary Local

Data Field Display Text

F9203*

Data Dictionary Data Dictionary Local

Data Item Alpha Descriptions

Contains alpha descriptions and compressed descriptions of data items. Used when data items descriptions requested. Similar to the F9202 table. Contains data dictionary alpha descriptions for all languages.

F9207

Data Dictionary Data Dictionary Local

DD Error Message Informa- Contains one record per error message. tion Data Field Specifications Contains detailed information (specifications) for each data item. This table is accessed whenever a data item needs to be identified. Contains information for Smart Fields.

F9210

Data Dictionary Data Dictionary Local

F9211

Data Dictionary Data Dictionary Local

Data Dictionary Smart Fields Smart Field Criteria Setup Rules Software Package Build Header Software Package Build GA.Rev8 1/7/2008

F9212 F96021 F9603 388

Data Dictionary - 812 Data Dictionary Local System - 812 System - 812

Stores the detail information from the definition process of package build. Stores information from the assembly Copyright 2008, Oracle. All rights reserved.

Chapter 21. Major Technical Tables

Table F96210

Data Source System - 812 System Local

Description Header Package Build Validation Tables Package Build Validation Detail Software Package Build Header History

Purpose process of package build.

F96211

System - 812 System Local

F96215

System - 812 Planner - 812 System Local

Contains the history record of the F96021 record. It stores statuses of the package each time it is built.

F9622

System - 812 Planner - 812 System Local

Software Package Build Detail

Stores the option information from the definition process of package build. Each record is either the name of the specification file, the name of a .DLL file, the name of the compression directory, or the name of an object. Contains the history record of the software build program (P9622). Stores the status of the build on the operation of that record when the package is finished. Stores the detail information for the assembly process of package build. Stores the object names, foundation name, data name, or helps name. Holds the default information regarding all machines used by JD Edwards EnterpriseOne.

F96225

System - 812 Planner - 812 System Local

Software Package Build Detail History

F9631

System - 812 Planner - 812 System Local

Software Package Detail

F9650

System - 812 Planner - 812 System Local

Machine Master

F9651

System - 812 Planner - 812 System Local

Machine Detail

Holds specific information about each machine defined in the machine master table by record type.

F9652

System - 812 Planner - 812 System Local

Deployment Group Header Specifies groups that can be used by the Release 8.12 administrator for deploying packages.

F9653

System - 812 Planner - 812 System Local

Deployment Group Detail Definitions

Stores the users that belong to one or more groups that were defined in the deployment header file. In addition, groups of groups can be defined here. Enables definition of one or more locations for deployment. This table is used primarily in multitier deployment.

F9654

System - 812 Planner - 812 System Local

Deployment Location Definitions

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

389

Chapter 21. Major Technical Tables

Table F9660

Data Source System - 812 Planner - 812 System Local

Description Task Breaks

Purpose

F96600

System - 812 Planner - 812 System Local

Deployment Features

F96601

System - 812 Planner - 812 System Local

Deployment Registry

F96602

System - 812 Planner - 812 System Local

Deployment Shortcut

F96603

System - 812 Planner - 812 System Local

Deployment Execute

F96604

System - 812 Planner - 812 System Local

Deployment Third Party

F96605

System - 812 Planner - 812 System Local

Deployment Initialization

F96605T

System - 812 Planner - 812 System Local

Deployment Initialization

F96606

System - 812 Planner - 812 System Local

Deployment File Set

F966071

System - 812 Planner - 812 System Local

Deployment ODBC Data Source

F966072

System - 812 Planner - 812

Deployment ODBC Data Source Attributes

390

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 21. Major Technical Tables

Table

Data Source System Local

Description

Purpose

F9670

System - 812 Planner - 812 System Local

Software Update Master Table

F9671

System - 812 Planner - 812 System Local

Software Update Detail Table

F96710

System - 812 Planner - 812 System Local

Impact Analysis Results

F9672

System - 812 Planner - 812 System Local

Software Update Pathcode Information

F96761

System - 812 Planner - 812 System Local

Software Update Object Detail

F967611

System - 812 Planner - 812 System Local

Software Update Language Table

F9691100 F9691400

System Local System Local

Change Table Favorites

Stores adds, changes, and deletes to favorites tables between releases.

Change Table Report Dir- Stores adds/changes/deletes to the Reector Template Header port Director template header table between releases. Change Table Report Dir- Stores adds/changes/deletes to the Reector Template Sequence port Director Template Sequence table between releases. Change Table Smart Field Stores adds/changes/deletes to the Smart Activity Field Activity table between releases. Change Table Smart Field Stores adds/changes/deletes to the Smart Criteria Field Criteria table between releases. UDC Merge table Contains the UDC records changed or added from release to release. This table is used by the UDC merge program (R98741).

F9691410

System Local

F9691420 F9691430 F9746

System Local System Local System Local

F960004 F960005

Control Tables xxx Control Tables Local Control Tables xxx Control Tables Local

UDC Type UDC Codes

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

391

Chapter 21. Major Technical Tables

Table F9755

Data Source Data Dictionary - 812 Data Dictionary Local

Description Data Item Master Changes by Release

Purpose Contains the data dictionary items changed or added from release to release. This table is used by the Data Dictionary merge program (R989200P). Lists changes made to alpha descriptions of data items (F9203) between releases. This table is used in the data dictionary merge process. Lists changes made to error messages (F9207) between releases. This table is used in the data dictionary merge process. Lists changes made to field specifications (F9210) between releases. This table is used in the data dictionary merges.

F9757

Data Dictionary - 812 Data Dictionary Local

Data Item Alpha Description Changes by Release

F9759

Data Dictionary - 812 Data Dictionary Local

Error Message Pgm Call Changes By Release

F9760

Data Dictionary - 812 Data Dictionary Local Central Objects - xxx Versions Local Central Objects - xxx Versions Local System - 812 System Local

Data Field Specification Changes By Release

F980011 F980021 F98101

Cross Reference Relation- Lists cross-reference relationships for ships business views, event rules, and controls. Cross Reference Field Re- Lists cross-reference relationships for lationships fields in an application. Imaging Constants Determines whether you are doing thirdparty imaging. Contains one record per version (batch or interactive). For interactive, it stores processing option values. For batch, this table holds data selection, sequencing, and other template overrides.

F983051

Versions - xxx Versions Local

Versions List

F982xx

System - 812 System Local Planner - 812

Series (OMW)

F98306* F9840

Central Objects - xxx Versions Local Version - 812 Planner - 812

Processing Option Text

Provides processing option text for all languages.

Installation Plan Master ta- Contains general information for the inble stallation plan with one record per plan name (description and status). Data Source Plan Detail ta- Lists data sources for each plan, and one ble record per plan record per data source associated with that plan. Host Plan Detail table Lists the Enterprise Server and hosts for each plan (one record per plan, per server). Contains the last location for a plan.

F98401

Version - 812 Planner - 812

F98402

Version - 812 Planner - 812

F984021

Version - 812 Planner - 812

Location Plan Detail table

F984022

Version - 812 Planner - 812

Replication Plan Detail table

Stores replicated plan for remote locations, publisher, and subscriber tables.

F98403

Version - 812

Environment Plan Detail ta- Lists environments for each plan. Holds ble flags for production data, demo data, and GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

392

Chapter 21. Major Technical Tables

Table

Data Source Planner - 812

Description

Purpose table conversions for an upgrade.

F984031*

Version - 812 Planner - 812

Language and Environment Lists language and the selected environPlan Detail table ments for each plan. Package Plan Detail table Lists packages and package definitions for each environment. Lists table conversion information merged in Table Conversion Scheduler from Environment Planner and Table Conversion Planner. This table is similar to the F9843 table.

F98404

Version - 812 Planner - 812

F98405

Version - 812 Planner - 812

Table Conversion Scheduler

F984052

Version - 812 Planner - 812

Table Conversion History Stores the logs for table conversions, Log control table merges, and specification merges. Table Conversion JDE Scheduler Contains table conversions, control table merges, and specification merges for upgrades, updates, and coexistent installations. Lists default data sources by environment. This table is used during installation.

F9843

System - 812

F9843T F98511

System - 812 System - 812 Planner - 812 REP Data Sources by Environment

F9860

Object Librarian Object Librarian Local

Object Librarian Master ta- Contains one record per object with deble scription and object type. Object Librarian Status Detail Contains one record per object, per location, per path code. Each object has a server location plus locations for each person who checks it out to his machine.

F9861

Object Librarian Object Librarian Local

F986101

System - 812 Server Map Planner - 812 System Local

Object Configuration Mas- Contains all data sources for tables, ter batch applications, and business functions that run on the server. The only data sources not controlled through this file are the system data source in Release Master and the Development data source in object path master. Data Source Master Holds data source definitions. One record per data source with type, database, machine name, and foundation .DLL.

F98611

System - 812 Server Map Planner - 812 System Local

F986110

System - 812 Server Map Planner - 812 System Local

Contains one record for each job on the server with status information.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

393

Chapter 21. Major Technical Tables

Table F986111

Data Source System - 812 Server Map Planner - 812 System Local

Description Job Number Master

Purpose Contains the next numbers table for server jobs.

F986113

System - 812 Server Map Planner - 812 System Local

Subsystem Job Master

Contains server job records, including status, location, and version.

F986115

System - 812 Server Map Planner - 812 System Local

Table and Data Source Siz- Holds storage, sizing, and location paraing table meters for Oracle, with some general information for all data sources.

F986116

System - 812 Server Map Planner - 812 System Local

MVS table and Data Source Holds storage, sizing, and location paraSizing meters for MVS. Similar to the F986115 table.

F98613

System - 812 Server Map Planner - 812 System Local

Business View Environmental Server

Lists cached tables.

F986150

System - 812 System Local

Server Transfer Package Contents Server Package Transfer

Lists objects belonging to each server package. This table is used by the server package installation process (P986150). Lists the servers and path codes to which a given server package will be transferred. This table is used by the server package install process (P986150). Contains the master list of all service packages. This table is used by the server package install process (P986150). Lists the printer definitions, including logical name, physical name, and conversion program, one record per printer. Lists default printer settings by user and environment. Lists paper sizes defined for each printer, one record per printer.

F986151

System - 812 System Local

F986152

System - 812 System Local

Server Package Master

F98616

System - 812 System Local

Printer

F986161

System - 812 System Local

Default Printer table

F986162

System - 812 System Local

Paper Definition

394

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 21. Major Technical Tables

Table F986163

Data Source System - 812 System Local

Description Printer Capability

Purpose Lists printer capabilities (paper orientation and size, type and location of printer) for each printer, one record per printer. Lists printer output conversions defined for each printer, one record per printer. Stores the default printer information including the user, environment, host name, printer name, and the status. Reserved for future use.

F986164

System - 812 System Local

Output Conversions

F986165

System Shared

New Default Printer Table

F986167

System - 812 System Local

Printer Security

F9862

Object Librarian Object Librarian Local

Object Librarian Function Lists one record for each function conDetail tained in the source file. Object Librarian Object Relationships Form Information Contains one record per business function per related object. This table is used when building business functions. Contains one record per interactive form, including online help information. Holds table-specific information for tables created in TDA (BOBSPEC). Holds all column information for the table in TDA (DDCLMN). TDA Information pertaining to the primary index. TDA All fields that make up the primary index. Holds all business-view specific information from BDA. Stores header file for event rules.

F9863

Object Librarian Object Librarian Local

F9865

Object Librarian Object Librarian Local

F98710 F98711 F98712 F98713 F98720 F98740 F98741 F98743

Central Objects Specific- Table Header ations Central Objects Specific- Table Columns ations Central Objects Specific- Primary Index Header ations Central Objects Specific- Primary Index Detail ations Central Objects Specific- Business View Specificaations tions Central Objects Specific- Event Rules Link ations

Central Objects Specific- Event Rules Specification Contains actual event rules detail for a ations form. Central Objects Specific- Data Structure Templates ations Central Objects Specific- Media Object ations Central Objects Specific- Smart Field Named Mapations pings Central Objects Specific- FDA Text Information ations Contains one record for each template, for example, Data Structure for Business Function. Contains media object text for tools. Contains smart field named mappings. Contains form design text for all languages for any generated application.

F98744 F98745 F98750* F98751 F98752

Central Objects Specific- FDA Specification Informa- Contains specifications for an applicaations tion tion. Central Objects Specific- FDA/SVR Header Informa- Contains summary information about ations tion each application.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

395

Chapter 21. Major Technical Tables

Table F98753 F98760* F98761 F98762 F9882

Data Source

Description

Purpose Contains summary information about each form for each application. Holds records that contain the report design aid text for all languages. Holds records that contain report design aid setup information. Contains business function specifications. Logs all transactions that take place to objects.

Central Objects Specific- FDA/SVR Detail Informaations tion Central Objects Specific- RDA Text Information ations Central Objects Specific- RDA Specification Info ations Central Objects Specific- JDEBLC Behavior Inations formation System - 812 Planner - 812 System Local Checkout Log table

F98825

System - 812

Package Deployment Scheduling

Contains information for deploying client packages, such as group user ID and package assignment.

F9883

System - 812

Release 8.12 Network Loc- Contains information for deploying servations table er packages, such as package assignments. Install Package Header Contains one record per package.

F9885

System - 812 System Local

F9886

System - 812 System Local

Install Package Detail

Contains one record per package per product code or object to be included in the package. Lists each time the package is built.

F9887

System - 812 System Local

Install Package Build History Merge Log

F9888

System - 812 Planner - 812 System Local

Contains temporary message logging for merges.

F98800D* F98800T F98810D* F98810 F98811 F98830 F98840 F98845 F98860

Control Tables Control Tables Control Tables Control Tables Control Tables Control Tables Control Tables Control Tables Control Tables

Process Master Alternative Description Process Master Supplemental Information

Contains multiple language information for the F98800 table. Categorizes Composer processes.

Activity Master Alternat- Contains multiple language information ive Description for the F98810 table. Activity Master Activity Specifications Process Activity Associations Organizational Structure Master Organizational Structure Rule Process Instance Contains workflow activity information. Contains workflow activity specifications stored as event rules. Contains workflow activity relationships. Contains the defining data for organizational models. Contains the data that ties workflows to organizational models. Contains the instances of workflow pro-

396

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 21. Major Technical Tables

Table F98865 F98881

Data Source Control Tables System - 812 System Local

Description Activity Instance Specification Merge Logging

Purpose cesses. Contains the instances of workflow activities within processes. Contains logging information generated from the Specification Merge for upgrade, update, and the Specification Merge and Object Librarian Merge reports.

F9889

System - 812 System Local

Deployment Location Mas- Lists records for each tier with system ter and help information. This table is used only for multitier deployment. Deployment Location Path Code Package Deployment Scheduling Lists records with packages and help information. This table is used only for multitier deployment. Lists scheduling information for a multitier environment. Contains application version information: application, version, and user who entered it.

F98891

System - 812 System Local

F98892

System - 812 System Local

F98950

Central Objects Specific- User Overrides table ations System Local

F98980

System - 812 System Local

Font Override by Language Lists languages with information on corresponding display fonts. DB2 BLOB Support Table of Constants Lists constants for report design aid and form design aid. Determines which path codes to update for data dictionary replication. Contains one record for each replicated change. The table information is stored as a BLOB.

F98BLOB

System - 812

F98CONST System - 812 System Local F98DRENV System - 812 System - Planner F98DRLOG System - 812 Server Map System - Planner F98DRPCN System - 812 Server Map System - Planner F98DRPUB System - 812 System - Planner F98DRSUB System - 812 System - Planner F98EVDTL System - 812 System Local F98EVHDR System - 812 Copyright 2008, Oracle. All rights reserved.

Data Replication Environment Mapping table Data Replication Change Log

Data Replication Pending Change Notifications

Contains one record for each replicated change for each subscriber. Records are deleted as subscribers are notified.

Data Replication Publisher

Lists definitions of published objects.

Data Replication Subscribers Event Detail file

Defines each subscriber.

Filters events displayed in Form Design Aid (FDA) or Universal Batch Engine (UBE) design. Stores event description and event ID. 397

Event Header file GA.Rev8 1/7/2008

Chapter 21. Major Technical Tables

Table

Data Source System Local

Description

Purpose This table is used for all event rules.

F98MOQUE System - 812 System Local F98OWSEC System - 812 System Local F98TMPL System - 812 System Local F98VAR System - 812 System Local GT92002 GT9860A GT9862A GT98DSA GT98DSB Data Dictionary Object Librarian Object Librarian Object Librarian Object Librarian

Media Object Queues

Contains path codes to locations of multimedia objects. Contains the security tables that store the Release 8.12 user name and password for obtaining database user and password for certain data sources.

Release 8.12 Security

Templates

Table of Variables

Contains commonly used event rule variables.

Data Dictionary Glossary Contains column in data dictionary with Information descriptions of data dictionary items. Object Librarian Generic Text Structure Business Function Notes Data Structure Notes Structure and Item Data Structure Notes Structure and Item Media Object Templates Contains notes for objects in the Object Librarian. Contains notes for business functions. Contains notes for data structures. Contains notes for data structures. Contains templates that can be used for any attachment.

GT98TMPL Object Librarian

398

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 22. Working with Reports


During the installation, upgrade, and cumulative update processes, JD Edwards EnterpriseOne creates reports that show detailed information about the plan and summarize the status of the environment builds. During upgrades and cumulative updates, additional reports summarize the status of tables merges. This chapter discusses: Installation Planner Validation Report (R9840B) This report is for installation, upgrade, and cumulative update customers. Environment Database Creation Report (R98403) This report is for installation, upgrade and cumulative update customers. Index Recreation (R9698713) This report is for installation, upgrade and cumulative update customers. Pathcode Copy (R9800942) This report is for installation, upgrade and cumulative update customers.

Installation Planner Validation Report (R9840B)


Note
This report is used by installation, upgrade, and cumulative update customers. All processes use version XJDE0001 of this report. The Installation Planner Validation report summarizes the status of the installation plan and verifies that the plan information is correct before you run the Installation Workbench

Setting Processing Options


The Extra Info tab contains these options: Additional data source information flag OCM Information Flag Enter Y to include additional information. Enter Y to see all Object Configuration Manager (OCM) information for the current data selection. Enter D to select all default records. Enter N to prevent OCM records from being displayed. Enter Y to see OCM differences between the new environment and the previous environment. Enter Y to display all path code information for the plan(s) in the data selection.

OCM Differences Flag Path Code Information Flag

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

399

Chapter 22. Working with Reports

Update the Plan Status (10 60)

Enter 30.

How to Read the Report


Use the Installation Planner Validation report summary section to review basic information about the installation, upgrade, or cumulative update; the number of records validated; and the types of processes run. Review the main body of the report to verify that each data source, machine, and package build in the plan was created successfully. To verify, each detail line should have the value Record Validated in the far right column. The report includes the status of the following record types: Location Data sources (listed by database type) Environments Path codes Object Configuration Manager (OCM) Machines Table conversions Control table merges Specification table merges Packages

A summary should appear at the end of the report verifying that all records were validated and the plan status was updated to 30.

Environment Database Creation Report (R98403)


Release 8.12 creates an Environment Database Creation report for each environment that is part of your plan. For each environment, you can choose to load either production or demonstration data. Users performing installations and upgrades should run version XJDE0001. Users performing cumulative updates should run version XJDE0004. Upgrade users should run XJDE0005 because the update process updates only generic text. When running against pristine data, these users should run version XJDE0024. The environment database creation copies the System data source (previous release) to the System - 812 data source. The System data source is release specific. The report is read and errors are processed in the same way as they are for the regular Environment Database Creation.

Setting Processing Options


These processing options are the typical processing options for each version of the Environment Database Cre400 GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.

Chapter 22. Working with Reports

ation report.

Version XJDE0001 for Installations and Upgrades


The Environment Tab contains these options: Enter the Environment for the database to be created. Enter the Data Source for the database to be created. Enter a 1 to load Production Data or a 2 to load Demonstration Data. Leave this field blank. Leave this field blank. Enter 2. The default is 1. If this report is called from another process, the system passes in this flag. Enter OneWorld Local. If this report is called from another process, the system passes in this flag. Enter the Source Environment for the database to be copied from. Leave this field blank. If this report is called from another process, the system passes in this flag. The Update Tab contains the following options: Enter a 1 for Proof Mode or a 2 to create the Environ- Enter 2. ment Database. The default is Proof Mode. Enter a A to recreate existing tables in data sources Leave this field blank. that allow automatic table creation. The default is not to recreate tables. Enter a 1 to only copy tables that exist in the source Leave this field blank. data source. Enter a Y to add records without clearing the target ta- Leave this field blank. ble. This is used for language tables. The default is to clear the target table. The Print Tab contains these options: Enter a 1 to only print exceptions. Leave this field blank. The default is to print all lines. The Licensing Tab contains these options: Enter a Y to create all tables or a N to create licensed tables only. Enter a Y to print all tables in the report or an N to print licensed tables only. Leave this field blank. The default is to create all tables. Leave this field blank. The default is to print all tables.

Enter the source Data Source for Loading of Data.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

401

Chapter 22. Working with Reports

Version XJDE0004 for Updates


The Environment Tab contains these options: Enter the Environment for the database to be created. Enter the Data Source for the database to be created. Enter a 1 to load Production Data or a 2 to load Demonstration Data Leave this field blank. Leave this field blank. Enter 1. The default is to load production data. If this report is called from another process, the system passes in this flag. Leave this field blank. If this report is called from another process, the system passes in the data source. Leave this field blank. If this report is called from another process, the system passed in the Source Environment. The Update Tab contains these options: Enter a 1 for Proof Mode or a 2 to create the Environ- Enter 2. ment Database. The default is Proof Mode. Enter a A to recreate existing tables in data sources Leave this field blank. that allow automatic table creation The default is not to recreate tables. Enter a 1 to only copy tables that exist in the source Leave this field blank. data source The default is to copy all tables. Enter a Y to add records without clearing the target ta- Enter N to indicate you do not want to add records ble. without clearing the target table. This is used for language tables. The default is to clear the target table. The Print Tab contains this option: Enter a 1 to only print exceptions. Leave this field blank. The default is to print all lines. The Licensing Tab contains these options: Enter a Y to create all tables or an N to create licensed Leave this field blank. tables only. The default is to create all tables. Enter a Y to print all tables in the report or an N to Leave this field blank. print licensed tables only. The default is to print all tables.

Enter the source Data Source for Loading of Data.

Enter the Source Environment for the database to be copied from.

402

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 22. Working with Reports

Version XJDE0024 for Running Pristine Data


The Environment Tab contains these options: Enter the Environment for the database to be created. Enter the Data Source for the database to be created. Enter a 1 to load Production Data or a 2 to load Demonstration Data. Leave this field blank. Leave this field blank. Enter 2. The default is to load production data. If this report is called from another process, the system passes in this flag. Enter OneWorld Local. If this report is called from another process, the system passes in the data source. Leave this field blank. If this report is called from another process, the system passes in the Source Environment . The Update Tab contains theseoptions: Enter a 1 for Proof Mode or a 2 to create the Environ- Enter 2. ment Database. The default is Proof Mode. Enter a A to recreate existing tables in data sources Enter A. that allow automatic table creation. The default is not to recreate tables. Enter a 1 to only copy tables that exist in the source Leave this field blank. data source. The default is to copy all tables. Enter a Y to add records without clearing the target ta- Leave this field blank. ble. This is used for language tables. The default is to clear the target table. The Print Tab contains these options: Enter a 1 to only print exceptions. Leave this field blank. The default is to print all lines. The Licensing Tab contains the following options: Enter a Y to create all tables or a N to create licensed tables only. Leave this field blank.

Enter the source Data Source for Loading of Data.

Enter the Source Environment for the database to be copied from.

The default is to create all tables. Enter a Y to print all tables in the report or a N to print Leave this field blank. licensed tables only. The default is to print all tables.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

403

Chapter 22. Working with Reports

How to Read the Report


Review the reports to make sure the environments were created and configured successfully. The report includes a status for each table: Tables that have been created correctly have a status of Success. Tables that had errors have a status of Failure. Tables can have a status of No Action.

The Environment Database Creation report does not have a cover page. The reports list the following properties of each table (object) created: Object headings Syst Code Object Name Member Description Data Source Crt Tbl Copy Data Rec Insrt Rec Fail Copied from Data Source Status Source DS Warnings Target DS Warnings Description System Code. Shows the JD Edwards EnterpriseOne product code for the database listed in the Member Description column. Displays the alphanumeric name of the database. Displays the full name of the database being created. Displays the data source toward which this member points. Create Table. Shows whether tables are being created for this database. Shows whether the table was copied with data. Record Insert. Displays the number of records inserted. Record Failure. Displays the number of records that failed. Displays whether the table was copied with data and the data source from which it was copied. Displays one of the following statuses for the table creation: Success, Failure, or No Action. Displays any errors or warnings associated with the source data source. Displays any errors or warnings associated with the target data source.

Errors and How to Resolve Them


A report occasionally lists a status of Failure for tables that are created successfully. These failures are generally due to problems creating indices and are not critical for the successful installation of the software. During an upgrade or cumulative update, you could receive failures for some tables. To confirm successful table creation, verify that the following tables were created successfully: F0007Z1 F00092 F0086 F03B11 F03B14

404

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 22. Working with Reports

F03B112 F060116 F06106 F08042 F08330 F0911 F1501B F1721 F1731 F17111 F30006Z1 F3002Z1 F3003Z1 F3460Z1 F39062 F4077 F4106 F4111 F41508 F4600 F4812H F5215 F7302 F986113

Reports frequently list a status of No Action for tables the system created successfully. This status is accompanied by source and target data source warnings for these tables to explain why no action was taken. These warnings are normal and you can ignore them. The most common reasons for the warnings are because the source and target data sources are the same or the table was created by a previously installed environment. When the source and target are the same, the report lists the following warnings: Source data source warning Source Same as Target Target data source warning Existing table

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

405

Chapter 22. Working with Reports

This commonly occurs when the copied from data source is the same as the target data source (where the table is mapped), and often occurs for the following tables: UDC tables F0004 and F0005 Menu tables F0082, F00821, F0083, and F0084

If you load multiple environments that share the same mappings (for example, DV812 and TS812), the first environment loaded (DV812 in this case) lists the tables with a Success status. The second environment (TS812) lists any tables already created during the first environment load with a status of No Action and a target data source warning of Existing Table. The No Action status and Existing Table warning for the second (TS812) environment are normal. You can verify that any table with a target data source warning of Existing Table has been created successfully by verifying it was created while loading a previous environment.

Index Recreation (R9698713)


The R9698713 program is run from Batch Versions after an install or upgrade. It compares database indexes versus Release 8.12 index specifications in F98712 and F98713. If you run the program in Update mode, it recreates incorrect indexes.

Pathcode Copy (R9800942)


Environment Workbench runs the R9800942 program for each custom environment whose path code is to be copied from an existing path code. It copies the directory structure of the existing path code on the Deployment Server. It also copies package.inf and records in the package definition tables F9603, F9631, F96021 and F96215, replacing the path code names in those items.

406

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 23. Uninstalling the Software


This chapter includes these tasks: Understanding the Uninstallation Process Uninstalling the Software from the Workstations Uninstalling the Deployment Server Dropping Oracle Tablespaces and Indexes Removing Database Users for Oracle Uninstalling the Platform Pack

Understanding the Uninstallation Process


Because the Deployment Server is only installed on Microsoft Windows-based machines, you can uninstall it by using Add/Remove programs on the machine on which the installation was initially run. To remove the Platform Pack, you must run a separate platform-specific uninstallation program as described in this guide. In all cases, the installation and upgrade processes do not automatically remove any JD Edwards EnterpriseOne databases. You should have a database administrator (DBA) for your relational database management system (RDMS) manually remove any unused databases according to the list of databases and associated components, which are provided in this document. The Uninstaller program restricts you from uninstalling a mandatory component without also removing all associated optional components that were previously installed. The relationship between the mandatory and optional components is shown in this table: Server Deployment Server Mandatory Component JD Edwards EnterpriseOne Files Optional Components Production Environment Prototype Environment Development Environment Pristine Environment Enterprise Server JD Edwards EnterpriseOne Foundation ES Production ES Prototype ES Development ES Pristine

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

407

Chapter 23. Uninstalling the Software

Uninstalling the Software from the Workstations


You can remove previous JD Edwards EnterpriseOne installations from workstations by running the uninstallation program from Add/Remove Programs in the Microsoft Windows Control Panel. The uninstallation program performs the following tasks: Deletes the JD Edwards program group. Deletes jde*.* from the root directory. Removes the LOCAL data source. Deletes the path. Unregisters services. Removes the uninstall directory. Increments licenses on the Deployment Server. Deletes the installation directory tree. Deletes the registry entry.

Note
You can ignore messages about security that appear during the uninstallation procedure. If error messages say that you cannot remove certain objects, make sure that you have not selected Read Only on the object property sheet, and then rerun the uninstallation program.

408

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 23. Uninstalling the Software

Uninstalling the Deployment Server


When you run the InstallShield Wizard to uninstall the Deployment Server, the program is removed from the machine and also from the list of installed programs. 1. On the Microsoft Windows-based machine which you initially installed the Deployment Server, navigate to Add/Remove Programs and click the Change/Remove button for this program: JD Edwards | EnterpriseOne Deployment Server 2. 3. 4. 5. On JD Edwards | EnterpriseOne Deployment Server Installer, click Next. On JD Edwards | EnterpriseOne Deployment Server Installer, feature selection, choose the components you wish to uninstall and click Next. On JD Edwards | EnterpriseOne Deployment Server Installer, summary information, review the selections and click Next to begin the uninstallation. On JD Edwards | EnterpriseOne Deployment Server Installer, summary information, verify the uninstallation successfully complete and click Finish.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

409

Chapter 23. Uninstalling the Software

Dropping Oracle Tablespaces and Indexes


This section lists the Oracle tablespaces and indexes that must be manually dropped by a DBA. This is the list of databases that were created by the JD Edwards EnterpriseOne 8.12 Installation of the Platform Pack on your Enterprise or Database Server for your JD Edwards EnterpriseOne installation, or from a previous JD Edwards EnterpriseOne installation. By design, these database components are not automatically removed by the JD Edwards EnterpriseOne uninstallation program. You should have a DBA for your RDBMS manually remove any unused items specifically listed in the table below.

Note
When removing Oracle, you must drop the tablespace first and then drop the indexes.

Tip
The JD Edwards EnterpriseOne installer delivers sample scripts which you can use as examples of how to drop the tablespaces. You should examine and edit these to suit your needs with the understanding that they have not been delivered ready to run. You should pay attention to environment variables and arguments the scripts are expecting. Your DBA may prefer to drop the tablespaces themselves instead of using scripts. Sample drop scripts are located in the ORCL directory under the JD Edwards EnterpriseOne installation directory (E812): drop_db.bat You should also be aware that when you run the JD Edwards EnterpriseOne uninstaller, the directory structure containing sample drop scripts is deleted. JD Edwards En- Oracle Index Name (suffixed by the capital Oracle Tablespace Name (suffixed by the terpriseOne letter "I") capital letter "T") Component Foundation SVM812I SY812I OL812I DD812I Production PD812I PRODDTAI PRODCTLI SVM812T SY812T OL812T DD812T PD812T PRODDTAT PRODCTLT

Note
For your installation, the proddta and prodctl tablespaces and indexes may be needed for a previous release. Pristine PS812I PS812DTAI PS812CTLI PS812T PS812DTAT PS812CTLT

410

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 23. Uninstalling the Software

JD Edwards En- Oracle Index Name (suffixed by the capital Oracle Tablespace Name (suffixed by the terpriseOne letter "I") capital letter "T") Component Development DV812I TESTDTAI TESTCTLI DV812T TESTDTAT TESTCTLT

Note
For your installation, the testdta and testctl tablespaces and indexes may be needed for a previous release. Prototype PY812I CRPDTAI CRPCTLI PY812T CRPDTAT CRPCTLT

Note
For your installation, the crpdta and crpdctl tablespaces and indexes may be needed for a previous release.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

411

Chapter 23. Uninstalling the Software

Removing Database Users for Oracle


This section lists the database users that must be manually dropped by a DBA for your RDBMS system. This is the list of users that were created by the JD Edwards EnterpriseOne 8.12 Installation of the Platform Pack on your Enterprise or Database Server for your JD Edwards EnterpriseOne installation, or from a previous JD Edwards EnterpriseOne installation. The database users are not automatically removed by the JD Edwards EnterpriseOne uninstallation program. You should have a DBA for your RDBMS manually remove any unused items listed in the table below. Database Type System Object Librarian Data Dictionary Database User SY812 OL812 DD812 SVM812 You should also remove these users of the JD Edwards EnterpriseOne system: jdedba jde applead sysadmin produser devuser

You should also remove the role: jde_role.

Note
For your Oracle installation, the user jde_role may be needed for a previous release. Production PD812 PRODDTA PRODCTL

Note
For your installation, the proddta and prodctl users may be needed for a previous release. Pristine PS812 PS812DTA PS812CTL

412

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Chapter 23. Uninstalling the Software

Database Type Development

Database User DV812 TESTDTA TESTCTL

Note
For your installation, the testdta and testctl users may be needed for a previous release. Prototype PY812 CRPDTA CRPCTL

Note
For your installation, the crpdta and crpctl users may be needed for a previous release.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

413

Chapter 23. Uninstalling the Software

Uninstalling the Platform Pack


Warning
You should always use the JD Edwards EnterpriseOne Uninstaller program in Add/Remove programs to remove JD Edwards EnterpriseOne. If you manually remove the software, the uninstallation cannot be guaranteed to be complete and, as a result, subsequent reinstallation of JD Edwards EnterpriseOne may be hindered. The JD Edwards EnterpriseOne Uninstaller program performs requisite clean up tasks in the Microsoft Windows registry and also makes changes in common shared files, such as vpd.properties. On the Microsoft Windows-based machine which you initially installed the Platform Pack, navigate to Add/ Remove Programs to uninstall the Platform Pack. 1. On Add/Remove Program, locate and click the Change/Remove button for this program: JD Edwards | EnterpriseOne Platform Pack 2. 3. 4. 5. 6. On JD Edwards | EnterpriseOne Platform Pack Uninstaller, click Next. On JD Edwards | EnterpriseOne Platform Pack Uninstaller, feature selection, choose the components you wish to uninstall. Click Next. On JD Edwards | EnterpriseOne Platform Pack Uninstaller, summary information, review the selections and click Next to begin the uninstallation. On JD Edwards | EnterpriseOne Platform Pack Uninstaller, summary information, verify the uninstallation successfully complete and click Finish.

Note
To avoid the possibility of removing valuable customer data, the uninstall wizard only removes the Enterprise Server runtime code. The uninstall wizard does not drop the databases or their users.

414

GA.Rev8 1/7/2008

Copyright 2008, Oracle. All rights reserved.

Appendix A: Using Instcat.sql to Support MSDE ODBC


You must run the instcat.sql SQL script against the master MicroSoft Database Engine (MSDE) database on your Deployment Server. The instcat.sql SQL script runs stored procedures against your MSDE database instance in order to bring them to the most current level. Refer to the detailed procedures provided by Microsoft on their web site. Reference the following Knowledge Base article: How to Run INSTCAT.SQL Using the following navigation at the Microsoft web site: MSDN Home > MSDN Library > Enterprise Development > Windows Server System > Microsoft SQL Server > Microsoft SQL Server 2000 > ODBC > Configuring the SQL Server ODBC Driver (ODBC) http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_6_odbcht_9ylw.asp

Running the instcat.sql SQL Script


The instcat.sql SQL script is supplied by your installation of the latest version of SQL Server or Microsoft Data Access Component (MDAC). The Microsoft articles referenced above provide the operational theory and requirements for running the instcat.sql SQL script.

Caution
As recommend by Microsoft, you must not have any open connections to the MSDE database when running the instcat.sql SQL script. You should sign off from EnterpriseOne and close SQL Server Enterprise Manager. Use this command line to call the instcat.sql SQL script. ISQL -Usa -Psa_password -Sserver_name -ilocation\Instcat.sql where U specifies the UsereID, and where P specifies the corresponding password, and where -S specifies the Server name of the SQL server, and where -i specifies the full path to the instcat.sql file, and optionally where E specifies the integrated logic to the SQL Server database.

Note
The server name switch (-S) may also include the instance name. For example, Server_name\instance_name.

Copyright 2008, Oracle. All rights reserved.

GA.Rev8 1/7/2008

415

416

This page intentionally left blank

Você também pode gostar