JD Edwards EnterpriseOneApplications Release 9.0 Installation Guide for SQL Server on Microsoft Windows September 2008 Installation Guide for SQL Server on Microsoft Windows Copyright Notice Copyright © 2008, Oracle. All rights reserved. Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Subject to patent protection under one or more of the following U.S. patents: 5,781,908; 5,828,376; 5,950,010; 5,960,204; 5,987,497; 5,995,972; 5,987,497; and 6,223,345. Other patents pending. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. 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, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. Hazardous Applications Notice This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Third Party Content, Products, and Services Disclaimer This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services. Contains GNU libgmp library; Copyright 1991 Free Software Foundation, Inc. This library is free software which can be modified and redistributed under the terms of the GNU Library General Public License. Includes Adobe PDF Library, Copyright 1993-2001 Adobe Systems, Inc. and DL Interface, Copyright 1999-2008 Datalogics Inc. All rights reserved. Adobe is a trademark of Adobe Systems Incorporated. Portions of this program contain information proprietary to Microsoft Corporation. Copyright 1985-1999 Microsoft Corporation. Portions of this program contain information proprietary to Tenberry Software, Inc. Copyright 1992-1995 Tenberry Software, Inc. Portions of this program contain information proprietary to Premia Corporation. Copyright 1993 Premia Corporation. This product includes code licensed from RSA Data Security. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes cryptographic software written by Eric Young (
[email protected]). This product includes software written by Tim Hudson (
[email protected]). All rights reserved. This product includes the Sentry Spelling-Checker Engine, Copyright 1993 Wintertree Software Inc. All rights reserved. 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 JD Edwards EnterpriseOne 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 the Workstation Installation .................................................................. 5 Considering Additional Factors .......................................................................................... 6 Accessing Minimum Technical Requirements .............................................................. 6 Using JD Edwards EnterpriseOne Support ................................................................... 6 Understanding Documentation Conventions ................................................................. 6 Documentation Updates ................................................................................... 7 Tips .............................................................................................................. 7 Fonts and Type Styles ...................................................................................... 7 Hyperlinks ..................................................................................................... 7 Working With the Customer Checklist ................................................................................ 8 Environments Overview ................................................................................................... 9 Understanding Environments ..................................................................................... 9 Planner Environment (JDEPLAN) ............................................................................ 10 Planner Pathcode .......................................................................................... 10 Planner Database .......................................................................................... 10 Pristine Environment (PS900) ................................................................................. 11 Deployment Environment (DEP900) ......................................................................... 11 Development Environment (DV900) ......................................................................... 11 Prototype Environment (PY900) .............................................................................. 11 Production Environment (PD900) ............................................................................ 11 Additional Considerations ....................................................................................... 12 Push Installation ........................................................................................... 12 Cluster Software Options ................................................................................ 12 Web-Based Options ....................................................................................... 12 Release History .................................................................................................... 12 Language Process Overview ............................................................................................ 13 Language Architecture ........................................................................................... 13 Base Language ............................................................................................. 13 Alternate Language Components ...................................................................... 13 Language Preference Codes ............................................................................ 14 Database Character Set and Code Page Considerations ................................................. 14 Unicode ...................................................................................................... 14 Code Page Settings ........................................................................................ 15 SQL Server Code Page Settings ............................................................... 15 Workstations and Deployment Server ....................................................... 15 National Language Support ..................................................................................... 16 Single-Byte and Double-Byte Considerations ..................................................... 16 Font Considerations ....................................................................................... 17 User Display Preferences ................................................................................ 17 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.Rev0 v Installation Guide for SQL Server on Microsoft Windows 3. Working with the Deployment Server ................................................................................. 21 Understanding the Deployment Server .............................................................................. 22 SQL Server Express (SSE) Considerations ................................................................. 23 General Considerations .................................................................................. 23 EnterpriseOne Application P96717 ................................................................... 24 Local Oracle Enterprise Edition (OEE) Considerations ................................................. 24 EnterpriseOne Application P96717 ................................................................... 25 Best Practices for OEE Performance ................................................................. 25 Working with JDBC Drivers on the Deployment Server ....................................................... 26 Obtaining the JDBC Drivers .................................................................................... 27 Installing the JDBC Drivers on the Deployment Server ................................................ 28 Installing the Deployment Server ..................................................................................... 29 Downloading and Installing the Latest Software .................................................................. 38 Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server ........................................................................................................................... 38 Installing the Latest Planner Update .......................................................................... 39 Troubleshooting Deployment Server Installation ................................................................. 41 General ............................................................................................................... 41 Log Files ............................................................................................................. 42 Configuration Files ................................................................................................ 43 Path Code Master (F98611) ..................................................................................... 44 Oracle Enterprise Edition ........................................................................................ 45 File Locations ............................................................................................... 46 Oracle Installation Directory ................................................................... 46 OEE Logs ............................................................................................ 46 Tnsnames.ora ....................................................................................... 46 Rebooting the Deployment Server .................................................................... 47 EnterpriseOne Access to the Local Oracle Database ............................................. 47 Uninstalling the Local Oracle Database ............................................................. 48 Process Explorer ........................................................................................... 49 Verifying the Local Oracle Database Installation ................................................. 50 Deployment Server Installation Problems .......................................................... 51 Runtime Problems ......................................................................................... 51 Jde.log shows ORA-12541: TNS:no listener ............................................... 51 User gets a pop-up window prompting for E1Local DB user and password and Jde.log shows OCI0000141 - Error - ORA-01017: invalid username/password; logon denied ........................................................................................... 51 tnsnames.ora ........................................................................................ 51 Administering the Local Oracle Database Using SQL Plus .................................... 52 Encrypting the Password of the Local Oracle Database ......................................... 52 Decrypting the Password of the Local Oracle Database ........................................ 52 Import and Export Tablespaces to the Local Oracle Database ................................ 53 Import Tablespace Script (attach_planner.bat) ............................................ 53 Export Tablespace Script (detach_planner.bat) ............................................ 55 Local Oracle Database Configuration ................................................................ 55 Deployment.inf and <Package_name>.inf .......................................................... 56 4. Working with the Platform Pack ........................................................................................ 57 Understanding the Platform Pack ..................................................................................... 58 Preparing the SQL*Server Database ................................................................................. 59 General Considerations .......................................................................................... 59 Verifying code page settings for SQL Server .............................................................. 59 Configuring the Enterprise Server Prior to Installing the Platform Pack ................................... 61 Setting Up and Verifying the Hosts File ..................................................................... 61 Understanding the Platform Pack Installation ..................................................................... 62 Installing the Platform Pack ............................................................................................ 63 Running the JD Edwards EnterpriseOne Platform Pack Installer ..................................... 64 vi GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Installation Guide for SQL Server on Microsoft Windows Custom Mode Feature Selection ............................................................................... 70 Database and Security Options ................................................................................ 72 SQL*Server - Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) - or Database only ...................................................................................... 74 SQL*Server - Enterprise Server Only (Different Machine from Database Server) .............. 77 Review the Legacy Database Warning Panel .............................................................. 78 Concurrent Users .................................................................................................. 79 Review the Summary Information Panel and Complete the Installation ............................ 81 Verifying the Platform Pack Log File ........................................................................ 82 Troubleshooting Platform Pack Installation ........................................................................ 83 Installer Will Not Start or Complete (Invalid vpd.properties) ......................................... 84 Business Data and Control Tables Already Exist ......................................................... 85 Business Data and Control Tables Do Not Exist .......................................................... 86 System Database Not Detected ................................................................................ 87 Foundation Files Do Not Exist ................................................................................. 88 Rerunning the JD Edwards EnterpriseOne Platform Pack Installer .......................................... 89 Enterprise Server .................................................................................................. 89 Database Server .................................................................................................... 89 Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server ......... 90 Working with Database Security ...................................................................................... 91 5. Working with Installation Planner ..................................................................................... 93 Understanding Installation Planner ................................................................................... 94 Language Information ............................................................................................ 95 Location Information ............................................................................................. 95 Deployment Server Information ............................................................................... 95 Enterprise Server Information .................................................................................. 95 JD Edwards EnterpriseOne HTML Web Server Information .......................................... 96 Data Source Information ......................................................................................... 96 Environment Information ........................................................................................ 97 Working with JD Edwards EnterpriseOne Software Requirements .......................................... 97 Reviewing Installation Planner Processing Options .............................................................. 98 Assumptions About Reviewing Installation Planner Processing Options .......................... 98 Accessing Processing Options ................................................................................. 98 Choosing Processing Option Values ......................................................................... 99 Specifying the Prompt Mode ......................................................................... 100 Specifying the Process Mode ......................................................................... 101 Specifying the Default Mode ......................................................................... 102 Verifying Status Change Values Have Not Changed .......................................... 104 Specifying Plan Completion Processes ............................................................ 105 Specifying Replication Options ...................................................................... 107 Specifying Remote Location Package Push Options ........................................... 109 Working with a Typical Installation Plan ......................................................................... 111 Assumptions About Defining a Typical Installation Plan ............................................ 111 Starting Installation Planner .................................................................................. 112 Entering a Plan Description ................................................................................... 113 Entering Location Information ............................................................................... 114 Entering Deployment Server Information ................................................................. 115 Entering Enterprise Server Information ................................................................... 117 Entering HTML Web Server Information ................................................................ 119 Selecting Default Environments ............................................................................. 122 Finalizing the Installation Plan ............................................................................... 123 Concluding the Planner Validation Report ............................................................... 124 Creating a Custom Installation Plan ................................................................................ 125 Understanding a Custom Installation Plan ................................................................ 126 Starting Installation Planner .................................................................................. 127 Entering a Plan Description ................................................................................... 128 Entering Location Information ............................................................................... 130 Copyright © 2008, Oracle. All rights reserved. GA.Rev0 vii Installation Guide for SQL Server on Microsoft Windows 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 ................................................................ 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 .......................................................... Working with Environment Setup .......................................................................... Understanding Environment Setup ................................................................. Setting Up Environments .............................................................................. Adding a Custom Environment .............................................................. Selecting an Environment ..................................................................... Specifying Environment Data Load Parameters ......................................... Selecting Languages ............................................................................ Working with Environment Data Sources ........................................................ 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 ................................................... Adding a Remote Location ................................................................................... Finalizing the Installation Plan ............................................................................... Concluding the Validation Planner Report ............................................................... Deleting Machines from an Installation Plan ..................................................................... 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 ........................................................................................ 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 ................................................................................... 7. Working With the Enterprise Server ................................................................................ Verifying the Release 9.0 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 ............................................................................... viii GA.Rev0 131 133 135 136 140 142 142 143 144 145 146 146 147 148 149 150 151 152 152 152 153 154 156 157 158 159 160 161 162 163 164 165 166 170 172 172 172 174 175 175 178 179 180 181 182 183 184 185 187 187 188 188 189 189 189 190 Copyright © 2008, Oracle. All rights reserved. Installation Guide for SQL Server on Microsoft Windows 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 ..................................................................................... 8. 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 ................................... 190 190 190 191 191 191 191 192 192 198 201 201 202 203 203 203 203 204 205 206 206 206 207 207 207 9. Understanding Media Object Queues ............................................................................... 209 Modifying Media Object Queues .................................................................................... 209 Specifying the Help Location ........................................................................................ 210 10. Performing Post Installation Tasks ................................................................................. Understanding Post Installation Tasks ............................................................................. Resetting SQL Server Options ....................................................................................... Setting Up Microsoft Windows Security on Release 9.0 Directories ...................................... 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 ................................................................. Using the Adobe SVG Viewer on Web Clients ................................................................. Understanding Task Word Search Tables ......................................................................... Building Task Word Search Tables ......................................................................... Setting Up Solution Explorer ......................................................................................... Setting Up Solution Explorer HTML Documentation Path .......................................... Setting Up the Home Page for Solution Explorer ....................................................... Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications .......... Adding Vertex Quantum Directory Information to the Microsoft Windows Server Path .... Configuring the Release 9.0 Database Connections for Vertex Quantum Tax Applications Mapping Objects to the Enterprise Server ................................................................ Understanding the Autopilot Scripting Tool ............................................................. Testing the Vertex Quantum Connection from Release 9.0 .......................................... Enabling CRM Functionality ......................................................................................... Enabling CRM on the CRM Mobile Client ............................................................... Copyright © 2008, Oracle. All rights reserved. GA.Rev0 213 213 214 215 215 216 216 216 217 217 217 217 218 219 220 220 221 221 221 223 224 225 227 227 227 229 229 ix ......... Enabling Server-Side Signon Security ...................................................................................................................................... Deployment Tips .......................... Verifying Available Space in DBMS .................................... Granting Non-Privileged Access to Disk for Microsoft Windows ................................................................................ Using the PORTTEST Checklist ................. Package Build Considerations ............................................................................................................................................................................................................................................................................... Obtaining the JDK/JRE ... All rights reserved...................................................................................................................................................................................... 14............................................ Granting Access to the Software Installation Directory ........................................................................................................................... Assembling a Package that Contains Published Business Services ................................................................ Verifying Specific UBEs are Mapped Locally ............................................. Understanding Third-Party ODBC Data Source Creation ........... Adding a System User for the Central Objects Data Source Owner ................................ Running the Copy Environment Application (P989400) ... Package Deployment Considerations ................................................................. 16..................................... Installing Application Fixes ............................... Verifying the OCM Mapping . Setting up the Database Components for the Target Environment ..................................................................................................................... x GA..................................... 15.................................................................. Setting Up JD Edwards EnterpriseOne Single Sign-on ............... Deleting the BUSOBJ Directories .......................................... Creating Third-Party Data Sources for SQL Server ........................................... Configuring the Enterprise Server for Simultaneous Builds ................................................................................Installation Guide for SQL Server on Microsoft Windows Enabling CRM on the Enterprise Server .......................................................................................................................................................................... Reviewing Pre-Package Build Issues ....... Revalidating Workstations ....................................................................................................................................................................................................................... Adding an Override for an EnterpriseOne User Running Package Build ...... Working With Signon Security .................................................................... Revalidating Software Protection Codes ......................................... Verifying the Server-Side Settings ...................... Planner Update Special Instructions ..................................................................................... Copying an Environment to Another Environment .............................. 230 Enabling Verity Enhanced Search Capability ......................................................... Setting Up Signon Security ................... Enabling Client-Side Signon Security ..... Working with Third-Party ODBC Data Source Creation ..................................... .................. Oracle............................. Reviewing Troubleshooting Tips .......................... Troubleshooting . Adding a Security Override for Running Package Build ........................................................... Adding Security Overrides ......................................................................................................................... Resolving Data Errors ............................................................... 13.................................................................................................................................................................................Rev0 231 232 235 236 236 237 239 239 240 240 240 242 243 243 244 244 244 245 245 246 246 246 247 247 248 250 250 250 252 255 256 257 258 271 271 271 272 272 273 273 274 275 275 276 276 283 283 286 286 Copyright © 2008..................................................................................................................................................................................................... Building and Testing Packages ................................. ODBC Data Sources for a Microsoft Windows Enterprise Server with SQL Databases ............................................................................ 12....... User Tips ................ Granting Disk and Registry Access for Microsoft Windows Workstations ................................................................................................................................................................................................... Revalidating the Deployment Server ......... Understanding Packages ............................... Building an Alternate Language Package .. Updating the System Path .. Setting up Security Overrides for Package Build ..... Verifying the F9631 Table ..... Installation Utilities ........... 230 11................. Granting Nonprivileged Access to the Microsoft Windows Registry ................................... ............ Setting up the Data Source for Business Data ...................... Beginning the Data Source Setup for Environment ............................................. Entering Enterprise Server Data Source Information ...... Starting Installation Planner ..................................................................... Entering HTML Web Server Information ..................................................... Verifying the Data Dictionary Data Source ................................ Verifying Custom Server Map Data Source Information ................................................................................................... Select Another Environment ................................................................................ Entering a Plan Description ... Verifying the Data Source for Control Tables ........................... Specifying (Custom or Default) Shared Data Source Setup Information ........... Verifying the System Data Source ................................... Entering Enterprise Server Information ........................................................................................................................................................................................................................................... Adding another Enterprise Server ... Adding a Custom Environment .. Specifying an Enterprise Server ..................................... Specifying Custom or Default Data Source Information ........................................................................................................................................................................... Entering a Plan Location ........ 287 17........... Concluding the Remote Installation Plan Setup ..... Entering Plan Location Information ............................................................................................................................................................................... Assumptions about Adding a Server to an Existing Installation Plan .......................................... Entering Enterprise Server Data Source Information .................................................................................................................................. Environments ........................................................... Entering Information in Installation Planner ....................................... Finalizing the Installation Plan ......................................................................................................................................... Verifying the Data Dictionary Data Source ........................................................................................... Entering Shared Data Source Information ............................................................ Creating a Remote Installation Plan ........................................................................ Understanding Remote Installation Plans ............. Verifying the Object Librarian Data Source ............................. Setting Up Environments .. Adding Another Enterprise Server ..Installation Guide for SQL Server on Microsoft Windows Special Instructions for All ............................................................................... Setting Up Data Sources for Environment ................................................................................................................ Oracle............................................ Entering Deployment Server Information ................................................................................................................................Rev0 289 290 291 292 293 294 294 296 296 296 298 298 298 299 300 304 306 306 306 307 308 309 309 310 311 311 314 314 314 315 316 318 319 319 323 323 325 326 327 329 330 332 332 334 334 335 335 336 340 343 343 344 345 xi ........... Verifying Custom Server Map Source Information ............................................................. Entering Enterprise Server Information .............. Specifying a Deployment Server ............................................. Copyright © 2008........................................................ Entering Shared Data Source Information ........................................................................... Entering Data Server Information ........ Selecting an Environment .............................................. Adding a Server to an Existing Configuration ..... GA................................. Starting Installation Planner .................................................... All rights reserved............................................................................................... Specifying (Custom or Default) Shared Data Source Setup information ................................................................ Concluding the Validation Planner Report .......... Specifying an Enterprise Server ........................................................................................................................................................................................................................................ Entering Data Server Information ............................................................................................................................................................................................................................................................... 286 Special Instructions for OCX Registration .................................. Entering Deployment Server Information ........................... Specifying Custom or Default Data Source Information .............................................................................................................. Selecting Additional Server Types ....................................................................................................................... 286 Orphan Users ............................ Concluding Deployment Server Setup ........................................................................ 18........................................ Verifying the Object Librarian Data Source ............. Replicating Information to Remote Locations ....................................... Entering HTML Web Server Information ............................................................................................................................................................................. .................................................................................................................................. Accessing Installation Planner ................... Workstation General Directory Structure .............. Setting Up Environment Data Sources ....................... Completing the Language Installation ............. Setting Up the Data Source for Control Tables ........................................................................................... Control Tables ............................................................ Major Technical Tables ............................................ Setting Up the Data Source for Central Objects .............................................................................................................................................................................. Oracle.................................. Verifying Enterprise Server Requirements ............................................ Versions ....................................................................................................... Setting Processing Options ......... Running Installation Workbench ......................................................................................................... Configuring Additional Servers ........................................................................................................................................ System ..................... Entering Information into Installation Planner ............................................................................................................................................. Selecting an Environment ....... ........................................................................................................................................................................................................................................................ Selecting Custom or Default Parameters ........................................................... Building and Deploying Alternate Language Packages . Object Librarian ...................................................................................................................................................... Setting Up Environments ..................... Language Directory Structure ................... Deployment Server Directory Structure ............. Data Dictionary .... 21.... Installing Languages on the Deployment Server ...... Selecting an Environment Data Source Setup Option ....................................... Adding a Custom Environment ...................... Finalizing the Installation Plan ............................. Reviewing Requirements for a Language Installation ....................................................................................... Selecting Languages ........................................ Creating a Language-Only Installation Plan ................................................. Enterprise Server Directory Structure ................................. 427 427 427 428 xii GA..................... Central Objects ................ Understanding Language-Only Installation Plans ...... Server Map . Business Data ............................................................................................................................... All rights reserved... Understanding Data Source Charts .......................................................................... Selecting a Language ............................................................................................................................................. Running Installation Planner ..................................... Understanding JD Edwards EnterpriseOne Directory Structures ...................................................Installation Guide for SQL Server on Microsoft Windows Verifying the System Data Source .......................................... Specifying Environment Data Load Parameters ....... Verifying Workstation Requirements ............................................................................................... Installation Planner Validation Report (R9840B) ........................................................ 20......................................... 346 347 348 349 350 351 352 352 352 354 356 357 358 359 360 363 364 364 365 369 369 370 371 372 373 374 374 374 374 375 377 377 381 381 397 399 400 402 403 404 405 406 407 408 409 410 411 22............................................................................... Concluding the Validation Planner Report ....................................... How to Read the Report ...................................................... Language ........................................................................................................................................................................................... 19....................................................................... Working with Reports ......... 413 23.............................................................. Selecting an Environment .................................................................................................................... Local ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... Verifying the Data Source for Versions ......................................... Setting Up the Data Source for Business Data .............................................................................................................................Rev0 Copyright © 2008....................................................................................................................................................... Logic .......................................................................................... ...................................................................................................................................................................... Dropping SQL Server Databases ........................................................................................................................................................... Errors and How to Resolve Them ..................................................................................................................................... 443 Running the instcat............................. Version XJDE0001 for Installations and Upgrades ........... All rights reserved......................................................... Uninstalling the Software .............................................................. Uninstalling the Platform Pack ........... 443 B.. Pathcode Copy (R9800942) .. Removing Database Users for SQL*Server .. Understanding the Uninstallation Process .................................................................................... Uninstalling the Deployment Server ..................................... 24......................................... 445 Copyright © 2008.......................... Oracle.......Rev0 xiii ................................................................................... Version XJDE0004 for Updates ...................................................................................................... Uninstalling the Software from the Workstations .........sql to Support SQL Server and SSE ODBC ..................... Using Instcat................... How to Read the Report ............ 428 428 429 430 431 432 432 434 434 435 435 436 437 438 440 442 A...................................................................................... Index Recreation (R9698713) ... Understanding SQL Server Databases ............................................. Version XJDE0024 for Running Pristine Data ................. Setting Processing Options ..........sql SQL Script ..............................................................Installation Guide for SQL Server on Microsoft Windows Environment Database Creation Report (R98403) ...................................................................... GA................................... xiv This page intentionally left blank . Rev0 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.Chapter 1. GA. Oracle. All rights reserved. 2 GA. 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. To successfully install Release 9. review these guides before beginning: • • • • • • JD Edwards EnterpriseOne Tools Foundation Guide JD Edwards EnterpriseOne Tools 8. . All rights reserved. Understanding JD Edwards EnterpriseOne Understanding This Guide This guide is designed to direct you through a basic JD Edwards EnterpriseOne installation. which coincides with the General Availability of Release 9. this document is republished in its entirety only for the next major applications release of JD Edwards EnterpriseOne. it is recommended to complete the database product courses that your database vendors provide. Enterprise Server and Database Server on separate machines (or different drives in the same machine) – the Installer runs twice. once for each server. you must understand: • • • Hardware and software requirements Database setup and management Enterprise platforms and operating systems At a minimum.0. It is not a substitute for the database administration manuals provided by your Relational Database Management System (RDBMS) vendor. Generally. This guide is designed for management information system (MIS) managers and installers. However. It outlines the procedures for installing Release 9. Oracle.0.Rev0 Copyright © 2008.Chapter 1. the installation is flexible enough to enable you to: • • Select specific components to install from multiple predefined environments and databases.9 Configurable Network Computing Implementation Guide JD Edwards EnterpriseOne Tools System Administration Guide JD Edwards EnterpriseOne Tools Package Management Guide JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide JD Edwards EnterpriseOne Tools Security Administration Guide In addition. The book contains only the procedures required for a typical base installation with predefined typical environments and databases. 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.0. This can decrease the overall time it takes to complete the installation. This section discusses: Copyright © 2008. All rights reserved. You can set up your Release 9. these terms are all synonymous.0 does not support coexistence. Functionally.0 configuration in many ways.0. Understanding JD Edwards EnterpriseOne Understanding the Installation Process This documentation explains the process used to install Release 9. 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. Oracle.Chapter 1.0.0. and the HTML Web Server assuming the installation programs are run on different machines. which are commonly referred to as combo boxes. unless there is a strong business case that supports the need to change. the Platform Pack. These HTML Web Server installation guides are available on Customer Connection.Rev0 3 . this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software. Installations of the Deployment Server and Enterprise Server on the same machine. • Install the workstations for developers and system administrators Note You can concurrently install the Deployment Server. This guide only describes the definition of the HTML Web Server in regards to the Installation Planner and the Installation Workbench. You should follow the typical setup and naming conventions whenever possible.9 Configurable Network Computing Implementation Guide for more information about the typical customer configuration provided with Release 9. 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 9. The installation of the HTML Web Server itself is not covered by this guide. GA. See Also Typical Customer Configuration in the JD Edwards EnterpriseOne Tools 8. are not supported in production environments.0 software using the installation process. which includes all end-user applications and selected tools applications. For Release 9. Note JD Edwards EnterpriseOne Release 9. Separate guides describe the separate installation process for the HTML Web Server on the supported platforms. However. a JD Edwards EnterpriseOne HTML Web Server is mandatory to run web-enabled JD Edwards EnterpriseOne applications. From the Deployment Server. The program updates the Microsoft Windows registry with information about the Release 9. It is especially beneficial in situations in which the Enterprise Server is connected to the Deployment Server using a wide area network (WAN). This more direct installation method increases performance during this part of the process. All rights reserved.0 software is distributed to one or more workstations. Note Languages are installed using the Installation Planner from the Language CD. which requires an authorization code and the number of licensed users. To install additional languages. The Deployment Server installation program guides you through these processes: • • Authorization.0 software and a language. you perform the language-specific procedures after you have executed the initial installation described in this guide.Rev0 Copyright © 2008. Since the Deployment Server and Platform Pack have separate Installers. Installation Planner manages these processes: • Language setup 4 GA. Installation Planner guides you through setting up the installation plan step-by-step based on options you choose. refer to Creating a Language-Only Installation Plan. For additional details. if applicable. Installation Planner configures the environments for all machines within the enterprise. Understanding JD Edwards EnterpriseOne • • • • • Understanding the Deployment Server Installation Understanding the Platform Pack Installation Understanding the Installation Planner Understanding Installation Workbench Understanding the Workstation Installation Understanding the Deployment Server Installation The Deployment Server is the focus of the Release 9. they can be running concurrently which decreases the overall installation time (assuming the Installers are run on different machines). Understanding the Platform Pack Installation Rather than transferring all the software from the Deployment Server. if applicable. the Release 9. Since the Deployment Server and Platform Pack have separate Installers. Oracle. 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. the Platform Pack installs the code and database directly to the Enterprise Server.Chapter 1.0 installation and languages.0 installation process. Release 9. .0 is installed based on the information provided by the user. from the CD to the Deployment Server. The installation program for the Deployment Server copies the Release 9. 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. The software is installed on the workstations from the Deployment Server. • Data source setup This includes setup for both Enterprise Server-specific and shared environment data sources. However. and insulates you as much as possible from platform-specific environment setup. It functions as a central point for all the processes required to install environments. 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. such as PD900. Some of the processes that install environments might require procedures to be performed manually. Understanding JD Edwards EnterpriseOne • • • • • Location setup Deployment Server setup Enterprise Server setup HTML Web Server Additional server setup This includes setup to servers such as a Database Server. 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. All rights reserved. Installation Workbench assures that procedures are performed in the proper order. • Environment setup This includes all environments for a typical customer configuration. Copyright © 2008. Understanding Installation Workbench Installation Workbench runs the plan created during Installation Planner. Oracle. GA. and creation of a new environment. This process ensures that the Object Configuration Manager (OCM) mappings are correct and the new environments point to the correct path codes.Chapter 1.Rev0 5 . This could include creating custom environments and path codes. All rights reserved. Oracle.html Access the current Minimum Technical Requirement (MTR) listing from Customer Connection.jsp Using JD Edwards EnterpriseOne Support Use Customer Connection to access customer support functions and information including issues.Rev0 Copyright © 2008. http://www. JD Edwards EnterpriseOne may integrate. 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 Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne Minimum Technical Requirements. view SARs and objects. You can access the MTRs through multiple entry points. An issue number is assigned immediately when reporting by telephone. . email. databases. or fax. • • • Documentation Updates Tips Fonts and Type Styles 6 GA. Understanding Documentation Conventions This section explains these typographic and design conventions used throughout this documentation. Electronic Software Updates (ESUs). interface.0 installation or upgrade. For questions about operating systems. Refer to the following link for cross-reference material in the Program Documentation for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products. fax. This path and link are one example: Navigation: Customer Connection > Implement.oracle. and documentation. or e-mail. and this number references all activity related to the issue. Optimize + Upgrade > Optimization Guide > Supported Platforms > EnterpriseOne http://www. and other software products. and to access the Oracle Update Center.peoplesoft. In addition. a confirmation is sent within one hour of submitting issues through the web. Refer to Customer Connection. Limit questions to those regarding JD Edwards EnterpriseOne software. Software Action Requests (SARs). If you need further assistance with Release 9. or work in conjunction with other Oracle products.com/corp/en/iou/platforms/enterpriseone. you can research and download Service Packs.com/corporate/contracts/index.Chapter 1. During normal business hours. contact the appropriate vendor. Through the Update Center. contact Oracle customer support by phone. or other information that must be typed into the system. Italic type style designates variables used in the guide. Nearly all of the commands in this guide are case sensitive. Hyperlinks The output processor used to generate the PDF versions of this document automatically produce hyperlinks. Likewise. Tips information is helpful but optional. substitute the actual name of your Deployment Server. GA. hyperlinks to Appendices are not active.Rev0 7 . All rights reserved. For example.INI. Understanding JD Edwards EnterpriseOne • Hyperlinks Documentation Updates Customer Connection contains document updates and other information about installing and upgrade JD Edwards EnterpriseOne. Also. For example.Chapter 1. JD Edwards EnterpriseOne Tools Package Management Guide. the names of other JD Edwards EnterpriseOne guides are in italic type style. Hyperlinks) for the links to be included only for links within a chapter. In addition. commands. Fonts and Type Styles Special fonts and type styles are used in this guide. Courier font indicates explicit file names. Copyright © 2008. Links external to a chapter will not contain page numbers. modify the commands to match your directory structure. Oracle. For example. either within the Table of Contents or within the text body. an anomaly in the generation process causes page numbers within brackets (for example. However. Tips This documentation contains tips containing information that can make the JD Edwards EnterpriseOne setup process easier. all of the commands described illustrate the recommended directory structure. If your machine's directory structure is different. for the variable deployment_server in a command. a common file name used by JD Edwards EnterpriseOne is an initialization file called the JDE. Enter them exactly as written. Verify that the Enterprise Server hardware and software meet minimum technical requirements. Other tasks are quick and easy. . Verify that HTML Web Server hardware and software meet minimum technical requirements. can take some time to complete. All rights reserved. set up the support structure before starting the installation process. To install Release 9. Some of the tasks.Rev0 Copyright © 2008. The tasks in this section are designed to prepare the customer's system for the installation process. Oracle. Verify that the Deployment Server hardware and software meet minimum technical requirements. and hardware.Chapter 1. If the installation involves a secondary language. review Language Process Overview in this chapter.0 successfully. Understanding JD Edwards EnterpriseOne Working With the Customer Checklist The Release 9. Verify that the workstation hardware and software meet minimum technical requirements. Verify that the Deployment Server disk space meets minimum technical requirements. operating systems.0 support structure consists of components such as databases. This checklist helps to organize the required upgrade preparation: • • • • • • • • • Review Environments Overview . Assess the network. such as checking that the appropriate hardware and software are available. Verify that the Enterprise Server disk space meets minimum technical requirements. 8 GA. JD Edwards EnterpriseOne provides the following preset environments: • • • • • • • Deployment (DEP900) Planner (JDEPLAN) Prototype (PY900) Pristine (PS900) Development (DV900) Production (PD900) HTML Web Server (J) Copyright © 2008. • • • • • • • • Understanding Environments Planner Environment (JDEPLAN) Pristine Environment (PS900) Deployment Environment (DEP900) Development Environment (DV900) Prototype Environment (PY900) Production Environment (PD900) Additional Considerations Understanding Environments The Release 9. future upgrades are simpler if you use JD Edwards EnterpriseOne naming conventions. The following sections explain each environment in more detail.Chapter 1. In addition. If you customize your configurations during the process. Each environment shipped with Release 9.Rev0 9 . 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. GA. you should change only the descriptions provided with the typical setup. all of which is mapped to run on the Enterprise Server.0 software includes several environments that represent the typical customer configuration as defined in the JD Edwards EnterpriseOne Tools 8.9 Configurable Network Computing Implementation Guide. All rights reserved. Follow the setup recommendations and naming standards described in this guide to minimize confusion when communicating with those outside of your implementation team. Oracle. This section contains additional information about these environments and their role in the installation and upgrade process.0 has a specific use. These environments are preset to make the installation process as easy as possible. The planner environment uses a planner pathcode. 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. which are shared by all pathcodes. Planner Database All information created and updated during the planning stage is saved in these SQL Server Express (SSE) databases: • • • • • • • JDEPlan900 JDECTL900 JDEDD900 JDSYS900 JDEVL900 JDEOL900 JDEData900 When using the planner environment to change your configuration: • • Planner database tables are updated with the change. which is shipped with the software. Every environment must have an associated pathcode and a set of OCM mappings.Chapter 1. which point to a planner database. 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. A package indicates the necessary objects for a workstation. and a set of OCM mappings. All pathcodes share a complete set of runtime central objects on the Deployment Server. Planner database tables are not updated. Understanding JD Edwards EnterpriseOne Planner Environment (JDEPLAN) The software installation and upgrade process includes a planning stage called the planner environment. Planner Pathcode Release 9. and where the installation program finds them.0 provides a full set of runtime objects. For the deployment and production environments. Using this approach you can define the main components of your software configuration without affecting the production environment. The planner pathcode includes preloaded packages used during the update specification merge process. OCM and data source information comes from the planner 10 GA. a point-in-time snapshot of the central objects on the Deployment Server. All rights reserved. Oracle. which are used during the installation process.Rev0 Copyright © 2008. A plan is defined and run to move the change to the production environment. . refresh the data for this environment from the JDEPLAN environment on the Deployment Server. ESUs. You should use the production environment system (technical) tables to make changes to environments. and user profiles. packages. Log on to this environment to modify and test objects before transferring them to the prototype environment (PY900) pathcode. they will ask you to sign on to the pristine environment to duplicate the problem. Oracle. The deployment environment uses system information. The OCM mappings and data source information are supplied by the planner database. After running Installation Workbench. The pristine environment is also used to run Table Conversion processes during an upgrade. and then log on to the prototype environment for additional testing. build and install a full or partial prototype package (for example. no business data exists until it is entered. and item master are populated with production data during the prototype process. packages. When encountering a software problem that JD Edwards EnterpriseOne Global Support cannot duplicate. and OCM. Deployment Environment (DEP900) Use the deployment environment to run packages builds on the Deployment Server. such as company constants. Prototype Environment (PY900) The prototype environment is the staging environment for production. Development Environment (DV900) The development environment is for development objects (DV900 pathcode). Pristine Environment (PS900) Use the pristine environment (PS900) to test pristine (un-customized) objects with JD Edwards EnterpriseOne demonstration data or for training classes. refresh the data this environment uses from your production environment (PD900) Production Environment (PD900) Production users have a tested and released package on their system. Only one deployment environment is required because all environments created by the installation process share common data sources. You should apply all software updates. Batch applications can run on the Enterprise Server. Copy the tables to the production environment before going live. Routinely. All rights reserved. This environment is required to compare modified objects to pristine objects. fiscal date patterns. pathcodes. either monthly or quarterly. Constants tables and master tables. When appropriate. Copyright © 2008. Understanding JD Edwards EnterpriseOne database.Chapter 1. such as environments. The deployment environment uses the planner pathcode and has OCM mappings to the production environment system tables and local data.Rev0 11 . After transferring the objects into PY900. PY900FA or PY900PA). GA. and Service Packs to the Pristine environment. The Development environment is delivered with JD Edwards EnterpriseOne Demonstration data. Oracle. additional issues exist that must be taken into consideration before installing Release 9. the administrator can schedule a package to deploy to workstations at times when network traffic is low. Web-Based Options HTML Web Server installation enables the use of Web-enabled functions in Release 9.Rev0 Copyright © 2008. All rights reserved.0. For more information. See Also JD Edwards EnterpriseOne Tools 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. rather than the workstation requesting (pulling) an installation from the Deployment Server. 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. refer to Working with Installation Planner.11 ERP 8.0. . or JAS in the JD Edwards EnterpriseOne Tools HTML Web Server Installation Guide for more information about Web-based options. Release History This version of JD Edwards EnterpriseOne is Release 9. Java Server.12 Release 8. For a push installation. Package information is pushed from the Deployment Server to the workstation. See Also HTML Web Server. The following list shows the currently supported previous releases of JD Edwards EnterpriseOne: • • • • Release 8.0.10 OneWorld Xe 12 GA. The advantage of push installation is no interaction with the user is required.Chapter 1. Control Table. All language text is stored in a central location and deployed to the individual workstation.0 database and merges the alternate language text with the original English base. you will perform the procedures after you have executed the initial installation described in this guide. The package build process enables the building of packages for multiple languages. The language installation process automatically copies the text from a language database to the production Release 9. All rights reserved. The software specifies the language preference for forms and reports. This section is provided in this guide for references purposes. such as French. For additional details. and Data Dictionary data sources. you must build the language package. Multiple languages can be installed using the processes outlined in this guide. JD Edwards EnterpriseOne is shipped with 21 languages. 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. and English. JD Edwards EnterpriseOne provides all software with a base language of English. Spanish. users who share the same environment may want to view the same text in multiple languages. If you install additional languages. Base Language Release 9. Alternate Language Components An alternative language component is not included in this release. but double-byte languages must run on double-byte operating systems. Language text is accessed by the language preference code settings in the user profile associated with the alternate language installed.0. System. Oracle. Language Architecture The software language architecture incorporates multinational language functionality for international customers. The Language CD is required to implement this functionality. refer to the chapter Creating a Language-Only Installation Plan in this guide. Copyright © 2008. 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. These automated processes are described throughout this guide. An alternate language includes major components whereby language text is stored in the Central Objects.Chapter 1. When installing language for the first time. Single-byte languages run on singlebyte or double-byte operating systems. Instructions in this guide explain how to set up these features. For Release 9. GA. a language-only plan may be chosen after completing the initial plan. For example. The base release contains English and must be installed before creating custom modifications to include changes or additions to the translated text.Rev0 13 .0 language support works in conjunction with the English base language. Understanding JD Edwards EnterpriseOne Language Process Overview Note Languages are installed using the Installation Planner. See Also Package Build in the JD Edwards EnterpriseOne Tools Package Management Guide for more details on how to build a language package. All control files must also have an English record prior to adding an alternate language text record. Each character within the database is identified by a specific language preference code value. Asian character sets are specific to one language. Some character sets may contain multiple languages. also contain the language preference code in an additional description table.0 applications support the use of languages. á.0. all data sources default to Unicode. such as the Business Unit Master. with each code representing a different language. For SQL Server. The alternate language text tables contain language preference codes. Oracle. For installs. the Western European character set contains all characters common to the Western European languages (Aa . These values can change between databases and languages. 14 GA. such as a user defined code value as well as possible multiple records for a code value. The Unicode flag only indicates what column type is used to store character data in a Unicode database. Understanding JD Edwards EnterpriseOne Language Preference Codes The language preference codes are the standard language codes used throughout the software.Chapter 1. Account Master. When installing or upgrading the database. Unicode is required for Central Objects data sources. All users are assigned a language preference code within the user profile. . If the language preference code does not have a corresponding translated language record. Unicode Unicode specifies that the data stored in the data source is in Unicode format. set up the code page for the language before loading your language specifics for Release 9. 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. Refer to the individual applications to set up and use multiple languages. the base English record is the default record. and ü. Every character is defined by a unique hexadecimal value. Release 9. AAIs. located in the Release 9. For example. Every language is represented by at least one character set. This information is not translated in the JD Edwards EnterpriseOne demonstration data. A blank language preference code specifies the base language of English. The software uses code page conversions to control the consistent or desired display of data.Zz) and all special characters unique to specific languages. Database Character Set and Code Page Considerations Data within a database is defined by a set of parameters. Alternate language records always have a value in the language preference code.0 user profile. A character set or code page setting is a scheme for encoding character data. such as Á. A collection of characters within a defined database is called a character set or code page. Certain database tables. Note that the code page still must be set to the correct value even though the data sources may all be Unicode. Ü. The tables contain several records for each item. See Also Single-Byte and Double-Byte Considerations to determine the LocalCodeSet and code page settings for your database machine environment. determines which language is displayed on forms or reports. All rights reserved.Rev0 Copyright © 2008. and Item Master. The Language Preference Code field. All rights reserved. The correct code page should be set when the database is created. Code Page Settings You should use the code page settings in this guide. JD Edwards EnterpriseOne Flat File Conversion Guide for information on how to convert Flat Files to Unicode. Oracle. SQL Server Code Page Settings The Microsoft SQL Server code page setting of 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 1252 1252 1252 1252 1252 1252 932 1252 1252 1252 1252 1252 949 950 936 1256 1250 1250 1250 1253 1251 1254 Workstations and Deployment Server Code page settings for individual languages are specified in Microsoft Windows System locale. JD Edwards EnterpriseOne Tools Development Standards for Business Function Programming Guide for information on how to convert Business Functions to support Unicode text strings. Understanding JD Edwards EnterpriseOne See Also JD Edwards EnterpriseOne Unicode Data Conversion Guide for information on how to convert data to Unicode. Copyright © 2008. GA. Verify that the Deployment Server code page is set correctly prior to upgrade.Chapter 1.Rev0 15 . Single-byte character sets use a collection of phonetic characters that require one byte to create a single character. Single-byte languages can generally be run on single-byte or double-byte systems. perform the tasks for both the Enterprise Server and workstations to verify and modify the JDE. The following table shows the languages that the software supports and the LocalCodeSet values set in the JDE. The same database can store alternate language text. a double-byte SQL Server or Oracle database is required for Chinese and Japanese languages.INI settings. stored. However. when using a double-byte language. retrieved.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 16 GA. The double-byte languages support specific individual national code pages by language. this process may not necessarily use an understandable collating sequence. and printed in multiple languages. although it can still use QBE for any double-byte column. Single-Byte and Double-Byte Considerations Many single-byte languages support either national code pages or multinational code pages. must run on machines configured to support a double-byte system. All rights reserved. For example. .Rev0 Copyright © 2008. and Korean. Conversely. JD Edwards EnterpriseOne maintains consistent data within all databases and hardware platforms. By using NLS standards.Chapter 1. on all supported platforms. such as Japanese. For the workstation to reflect the language installed on the Deployment Server. JD Edwards EnterpriseOne uses NLS. displayed. relying on NLS standards to manage the text storage and retrieval. These procedures are described throughout this guide. Chinese.INI for the web development workstations. Oracle. Understanding JD Edwards EnterpriseOne National Language Support National Language Support (NLS) is a set of common standards that enable data to be entered. the double-byte character sets use ideographic characters and require two bytes to create a single character. to interact with any computer system (hardware and software) within your own environment. Double-byte languages. The software can perform a Query By Example (QBE) on any character.INI for the Enterprise Server and JDE. in different databases. and on different platforms. NLS is information that requires the set up of code pages and the JDE. grids.0 characteristics that are stored in the user profile. the values remain the same on any workstation that the user accesses. After user display preferences are set up for a given user. Some languages (such as doublebyte) require special fonts to display and print correctly. All rights reserved. and reports. GA. 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.Chapter 1. The software stores the font settings in files according to language. Individual users can choose fonts by language for forms. Copyright © 2008.Rev0 17 . 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 9. Refer to the JD Edwards EnterpriseOne Tools System Administration Guide for information about modifying user profiles. Oracle. User Display Preferences User display preferences are individually defined sets of Release 9.0 for that user. 18 This page intentionally left blank . 0 on various operating systems and servers. and workstations meet the hardware and software requirements. Refer to Accessing Minimum Technical Requirements.0. Verify that the Deployment Server. Enterprise Servers. Failing to do so may prevent proper installation of the software. Oracle. Refer to Accessing Minimum Technical Requirements Copyright © 2008. Before You Begin the Installation You should complete the tasks in this chapter before you begin the actual installation process.Rev0 19 . Because the software and hardware requirements change rapidly as manufacturers constantly update their products. Note Make sure that you have taken and installed the latest Planner ESU from the Update Center on Customer Connection. All rights reserved.Chapter 2. requirements are not provided in this documentation. The MTRs list supported C++ compilers on Microsoft Windowsbased machines. GA. Before you run the Deployment Server or Platform Pack installer. a new compiler requirement is added for Release 9. you should install a Microsoft Visual C++ compiler on any machine on which the installer will be run. 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 9. Additionally. the actual requirements for an installation will be greater due to the requirement for temporary space.0 Minimum Technical Requirements. Oracle.Chapter 2. Note While the disk space tables accurately represent the disk space requirements.0 software on the Deployment Server and Enterprise Server depends on many variables according to platform and database. .Rev0 Copyright © 2008. All rights reserved. Having the correct amount of space available. 20 GA. Before You Begin the Installation Verifying the Disk Space Requirements The amount of disk space you need for Release 9. but not on a single drive. Up-to-date disk space requirements are listed in the Release 9. Refer to Accessing Minimum Technical Requirements. The space requirements must be available on a single drive. is not adequate. Oracle. Working with the Deployment Server This chapter discusses: • • • • Installing the Deployment Server Working with JDBC Drivers on the Deployment Server Downloading and Installing the Latest Software Troubleshooting Deployment Server Installation Copyright © 2008.Rev0 21 . All rights reserved. GA.Chapter 3. Working with the Deployment Server Understanding the Deployment Server Release 9. For additional considerations. Important There is no migration path between local databases on the Deployment Server. once you have installed either local database.0 to the Enterprise Servers and workstations. For the local database. . Oracle. or vice versa. That is. no separate end-user licensing is required for installation of the database by the Deployment Server installer. It should be noted. The installation program loads the software on the Deployment Server. refer to the applicable section for your database: • • SQL Server Express (SSE) Considerations Local Oracle Enterprise Edition (OEE) Considerations 22 GA. that neither installed database is fully functional relative to the commercial versions of the products that are installed separately using the database vendor's installers. however.0 resides on an Intel Pentium-based Deployment Server running Microsoft Windows. For either local database (SSE or OEE). you must order either SQL Server Express (SSE) or Oracle Enterprise Edition (OEE). Separate CDs are supplied depending on which database is ordered for the Deployment Server. and then loads Planner and Workbench tables into the local database on the Deployment Server. installs a local database . All rights reserved.Rev0 Copyright © 2008. The software install and upgrade programs enable you to create and maintain installation plans and deploy Release 9. you cannot migrate your local data from SSE to OEE.Chapter 3. the installation includes the SSE database for local use by the Deployment Server. Copyright © 2008. Working with the Deployment Server SQL Server Express (SSE) Considerations This section describes: • • General Considerations EnterpriseOne Application P96717 General Considerations If you have ordered the SQL Server Express (SSE) version of the Deployment Server installer.Chapter 3. especially the SQL Native Client which is a unique requirement for SQL Server 2005. In that case. If you choose to use SQL Server 2005. The installation includes Microsoft GUI tools for database administration. GA. The maximum size of the SSE database is limited to 4 GB. you can choose to replace SQL Server Express (SSE) with SQL Server 2005 as your repository on the Deployment Server. Note Alternatively. you must meet the MTRs prior to running the Deployment Server installer. refer to Accessing Minimum Technical Requirements for specific versions of SQL Server and other requisite software. All rights reserved. Warning Only the optimized mode for SSE is supported. Oracle. Refer to Accessing Minimum Technical Requirements in Understanding JD Edwards EnterpriseOne of this guide.Rev0 23 . All rights reserved.Rev0 Copyright © 2008.mdf and .ldf must be named ABC.3) for local use by the Deployment Server.com/technology/products/database/sql_developer/index. Working with the Deployment Server EnterpriseOne Application P96717 Best practices in JD Edwards EnterpriseOne environments are to never directly modify an EnterpriseOne database outside of EnterpriseOne. For example.oracle. The installation does not include any GUI tools for database administration.mdf and ABC. However. then the .ldf Local Oracle Enterprise Edition (OEE) Considerations If you have ordered the Oracle Enterprise Edition (OEE) version of the Deployment Server installer.Chapter 3.0. the installation includes the OEE database (version 10.html This section discusses these topics: • • EnterpriseOne Application P96717 Best Practices for OEE Performance 24 GA. which is available at this link: http://www.2. you can download a free and fully support GUI tool such as Oracle SQL Developer.ldf have the same name as the databases.mdf and . By default you can only work in the local database using command line entries. P96717. . Therefore a new application. if the database name is ABC. is provided to perform the following SSE database actions: • • • • • Create Database Drop Database Attach Database Detach Database Shrink Database Note The P96717 application assumes that the . Oracle. ini files refere to the local database name in the exact mixed case.Rev0 25 . which is: E1Local Failure to use the exact mixed case will lead to decreased performance of JD Edwards EnterpriseOne on the Deployment Server.7 GB of disk space When fully loaded. P96717. Therefore a new application. Oracle. All rights reserved. Copyright © 2008. the following table lists some guidelines for minimum configurations. Working with the Deployment Server EnterpriseOne Application P96717 Best practices in JD Edwards EnterpriseOne environments are to never directly modify an EnterpriseOne database outside of EnterpriseOne.7 GB of disk space JD Edwards EnterpriseOne specifications require approximately 1. GA. The local Oracle database performs best on hard drives that are not fragmented or full. Local Database Name Ensure that any reference in data sources and . Additionally. Specification RAM Page File Size Disk Space Usage Recommendation 2 GB minimum Minimum setting should be two times the amount of memory Oracle database engine requires approximately 1.Chapter 3. is provided to perform the following Oracle database actions: • • • • Import Tablespace Export Tablespace Create Tablespace Drop Tablespace Best Practices for OEE Performance You should always verify that your Deployment Server machine meets the MTRs (refer to Accessing Minimum Technical Requirements). best performance is obtained if the hard drive on the Deployment Server machine has at least 20% free space. This section describes: • • Obtaining the JDBC Drivers Installing the JDBC Drivers on the Deployment Server 26 GA. .Chapter 3.Rev0 Copyright © 2008. Oracle. All rights reserved. Working with the Deployment Server Working with JDBC Drivers on the Deployment Server The Deployment Server requires database-specific JDBC drivers for several purposes as described below. html Note The ojdbc5. all installations of OEE on the Deployment Server require the ojdbc5.jar driver.jar terpriseOne Enterprise or Database Server SQL Server 2005 and SSE IBM UDB for Windows or Unix IBM UDB for HPUX Itanium with Oracle Application Server IBM DB2 for iSeries sqljdbc.jar db2jcc_license_cu. Database JDBC Driver Files Local Oracle and Oracle on the JD Edwards En.jar is only compatible with JDK 1. you should obtain the required java-based JDBC driver files from your database vendor.0. for JD Edwards EnterpriseOne Release 9.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc_111060. Typically the driver is located in this directory of your Oracle 11g installation: \jdbc\lib • Oracle Technology Network (OTN) http://www.jar If you did not order the OEE edition of the Deployment Server installer. In addition.jar db2java. you can locate the Oracle database driver in these locations: • Oracle Enterprise Edition Database (on your JD Edwards EnterpriseOne Enterprise or Database Server) Your installation of an Oracle 11g database product includes the ojdbc5.5. Working with the Deployment Server Obtaining the JDBC Drivers Based on the database being used on your JD Edwards EnterpriseOne Enterprise Server.zip db2jcc.oracle. Copyright © 2008. Oracle.Chapter 3.ojdbc5.Rev0 27 .jar driver for local database connectivity on the Deployment Server (required to build and deploy ESUs) and to perform installations of the Web Development Client (fat client). GA. All rights reserved.jar jt400. All rights reserved.Rev0 Copyright © 2008. Oracle. you should place the driver file (and if applicable any associated license files) in this directory on the Deployment Server: • x:\JDBC You must supply this directory name when you run the Deployment Server Installer. Working with the Deployment Server Installing the JDBC Drivers on the Deployment Server After you have obtained the JDBC driver from the database vendor. 28 GA. .Chapter 3. Rev0 29 . you can install the Deployment Server. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully. This table lists the mandatory and optional components of the Deployment Server installation. Note You can run the Deployment Server and the Platform Pack installation concurrently (assuming the installation programs are run on different machines). Microsoft Word. 4. 3. All rights reserved. the drive and folder might be d:\ISMPTemp. Updates the Microsoft Windows Registry. you cannot install the Deployment Server from a remote machine. This process installs the Deployment Server from CDs. or Adobe Acrobat). shut down all programs running on the Deployment Server that could cause DLL conflicts (such as Microsoft SQL Services. Creates the path code directory structures (such as PS900 and PD900) based on your selections. GA. Change both of these to point to the folder you created on your larger drive in Step 1. 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. Create a new empty folder on the drive that has more room. Internet Explorer. Alternately. Right click on My Computer then choose Properties | Advanced | Environment Variables.Chapter 3. 2. For example. By default these are placed on the c: drive of your Windows-based Deployment Server. You can restart these programs after you finish installing the Deployment Server. Copyright © 2008. Working with the Deployment Server Installing the Deployment Server The InstallShield process creates temporary files during the install. After verifying the support structure. Scroll through the variables in the top pane (User) and find TEMP and TMP. Oracle. 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. Note Install the Deployment Server locally. Prerequisites Before you run the installation program. . Working with the Deployment Server 30 GA.Chapter 3. All rights reserved. Oracle.Rev0 Copyright © 2008. All rights reserved. To install the Deployment Server: Warning Before you click Next on this screen.exe (which is called by the autorun. you can execute the RunInstall. refer to Working with JDBC Drivers on the Deployment Server in this chapter. refer to Accessing Minimum Technical Requirements in Understanding JD Edwards EnterpriseOne of this guide. Log on to the Deployment Server as a user with Administrator rights. which is either SQL Server Express (SQL/2005) or Oracle. Copyright © 2008. 2. For help with locating MTRs. Working with the Deployment Server The diagram below illustrates the process flow and the various installation paths. you should obtain the JDBC drivers for the Enterprise Server database and also for your local database. Insert the first Deployment Server CD into the CD drive. Although this may take a few minutes to completely initialize. 1. If the location does not exist or is not properly populated and you click Next. a new and separate JD Edwards EnterpriseOne Deployment Server Installer window is displayed. you can view the progress on the InstallShield Wizard dialog that appears on your screen or Task Bar. Both the JDBC drivers and the JDK should be placed in a directory on your Deployment Server before you begin the Deployment Server Installer. If the setup does not begin automatically or if you wish to start the installation manually.Chapter 3.exe file which is located at the root of the installation disk. Note The InstallShield Wizard begins to initialize and prepare the requisite JVM for the JD Edwards EnterpriseOne Deployment Server Installer.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. Warning Ensure that the Administrator account name that you use does not contain any special characters. Oracle. The RunInstall. If you directly execute the Deployment Server installation program (setupwin32. refer to the MTRs for the Release 9.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.Rev0 31 . For specifications of the requisite JDK. an error message is displayed and you must exit the and restart the Deployment Server Installer in order to proceed. When the initialization is complete. For instructions on obtaining and placing the requisite JDBC drivers. The setup starts automatically.0 Deployment Server. GA. You should note this location because during the installation you are prompted for it. On JD Edwards EnterpriseOne Deployment Server Installer. Oracle. Welcome. Working with the Deployment Server 3.Rev0 Copyright © 2008. click Next. All rights reserved. 32 GA.Chapter 3. . setup type panel. directory selection panel. On JD Edwards EnterpriseOne Deployment Server Installer. Oracle. 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.Rev0 33 . Custom Copyright © 2008. complete this field: Directory Name Enter the drive and directory where you want the files installed on your Deployment Server. For example: d:\JDEdwards\E900 5. GA. Recommended for experienced users. On JD Edwards EnterpriseOne Deployment Server Installer. Working with the Deployment Server 4. 6. choose this setup type if you wish to complete the Deployment Server installation by specifying the installation of a subset of pre-defined environments. 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. All rights reserved.Chapter 3. Click Next. choose your installation type: Typical Recommended for most users. you can skip directly to step 10 located later in this task to complete the Deployment Server installation. Tip If you choose Typical installation. or directory that is different from that which contains the JD Edwards EnterpriseOne files. . Working with the Deployment Server 7. Likewise. • • • • 8. 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. On the warning message. All rights reserved. on JD Edwards EnterpriseOne Deployment Server Installer. drive. 34 GA. Oracle. Production Environment Prototype Environment Development Environment Pristine Environment Click Next. If you do not select this box and the JD Edwards EnterpriseOne Deployment Server Installer can not detect the required system files. or click Back and change your selections manually. it selects them automatically and displays a warning message. you must either select OK to acknowledge that the selection of the mandatory system files.Rev0 Copyright © 2008. feature selection panel. If you chose Custom Mode on the previous panel. select the features you want to install: • JD Edwards EnterpriseOne Files Note This selection includes mandatory system files.Chapter 3. 0) Running Change Assistant Running Configuration Assistant For instructions on obtaining and placing the requisite JDBC drivers.Rev0 35 . Working with the Deployment Server Warning Before you click Next on this screen. complete this field: Name of Directory Enter the drive and directory that you previously created as described in Warning above. For example: d:\JDBC Copyright © 2008. you should obtain the JDBC drivers for the Enterprise Server database and also for your local database. refer to Working with JDBC Drivers on the Deployment Server in this chapter. 9. On JD Edwards EnterpriseOne Deployment Server Installer. an error message is displayed and you must exit the and restart the Deployment Server Installer in order to proceed. JDBC folders panel. You should note this location because during the installation you are prompted for it. You should place the JDBC drivers in a directory on your Deployment Server before you begin the Deployment Server Installer. Oracle. and which contains the requisite JDBC Drivers. All rights reserved. For help with locating MTRs. refer to Accessing Minimum Technical Requirements in Understanding JD Edwards EnterpriseOne of this guide.Chapter 3. The JDBC drivers are needed for these purposes: • • • Applying ESUs (process changed for Release 9. If the specified location does not exist and you click Next. which is either SQL Server Express (SQL/2005) or Oracle. GA. The Deployment Server Installer displays the following screen if you have not loaded SQL Server Express Edition on this machine before: 36 GA. On JD Edwards EnterpriseOne Deployment Server Installer. The JD Edwards EnterpriseOne Deployment Server Installer displays a panel showing the ongoing status of the installation. Oracle. . an error message is displayed.Rev0 Copyright © 2008. 11. If there is insufficient disk space to complete the installation is available on the Deployment Server target machine. On JD Edwards EnterpriseOne Deployment Server Installer. Click Next to begin the Installation. a message appears stating that the installation was successful. summary information panel. verify that the appropriate components are selected. after the installation is complete. Working with the Deployment Server 10.Chapter 3. All rights reserved. This occurs if certain Microsoft Windows systems files are in use at the time of installation and therefore cannot be modified in real time. For example: x:\JDEdwards\E900\log. a panel may appear directing you to reboot the machine to complete the installation.txt Copyright © 2008. after the status of each product indicates setup or configuration is complete. GA. Note After the JD Edwards EnterpriseOne Deployment Server Installer is complete. Oracle.txt and is located in the Deployment Server installation directory. The file is named log. click Next to continue. Therefore. On JD Edwards EnterpriseOne Deployment Server Installer. All rights reserved. Working with the Deployment Server On Microsoft SQL Server 2005 Setup. 12. Tip You should review the log file created by the Deployment Server Installer.Chapter 3.Rev0 37 . in such cases the installation cannot be completed until the machine is rebooted. click Finish to complete the installation and exit the JD Edwards EnterpriseOne Deployment Server Installer. 98. download and install the latest Tools Release. Tools Release Patch.A1) and Tools Release documentation. Working with the Deployment Server Downloading and Installing the Latest Software Before continuing with the installation. This section discusses: • • Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server 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. and Planner Update from the Update Center. . Note The order in which the following Tools Release and updates are applied is very important. navigate to this directory on your Deployment Server: JDEdwards\E900\system\bin32 From that directory. it is necessary to run the Reconfigure SSE Utility.exe -TSSE -IJDESSELOCAL -password where -password is the current password for the SSE database. 38 GA. install the Tools Release Patch to the Deployment Server. From the Update Center homepage. download the latest Tools Release Patch (for example. 8. All rights reserved. Using the Tools Release documentation. Note If you have ever used the Drag and Drop method of moving between Tools Releases for service packs. run this batch file: ReconfigureMSDE. To do so. 2.Chapter 3.Rev0 Copyright © 2008. Do not deviate from the order below. Oracle. it will also prevent you from signing on to the JDEPLAN environment. Copyright © 2008. you can encrypt it again to the expected default password.bat Caution As part of the local database install. Run the self-extracting executable and follow the on-screen instructions to install the planner update on the Deployment Server.Rev0 39 .exe -TORACLE -IJDESSELOCAL -password where -password is the current password for the local database or tablespace. To install the latest planner update: 1. Not only will an unattached database or tablespace cause the installation of the planner update to fail. navigate to the Planner\spec directory and run this batch file: attach_metadata.bat This will attach any databases that were not successfully attached by the install. From Customer Connection.Chapter 3. several JD Edwards EnterpriseOne functions will fail. navigate to this directory on your Deployment Server: JDEdwards\E900\system\bin32 From that directory. Tip To attach the metadata local database. Working with the Deployment Server Installing the Latest Planner Update Warning Due to unpredictable timing issues. the databases or tablespaces that are needed for the planner environment may not automatically get attached as designed by the Installer. If you should inadvertently reset the password. run this batch file: For SSE: ReconfigureMSDE. 2.exe -TSSE -IJDESSELOCAL -password For OEE: ReconfigureMSDE. GA. there is a possibility that at the end of the Deployment Server install. Navigate to the directory JDEdwards\E900\planner\data and run this script: attach_planner. download the latest planner update for your Tools Release to the Deployment Server. Oracle. All rights reserved. which is bundled with the Deployment Server Installer. the password for the sa user on the JDELocal instance is encrypted. To do so. If you re-set this password. 40 GA. All rights reserved. Note The above login screen is displayed so that the Planner Update can update the metadata specifications on the Deployment Server. When the Welcome screen comes up. 4. The shipped values are JDE for the user and JDE for the password.Rev0 Copyright © 2008.Chapter 3. You must enter a valid JD Edwards EnterpriseOne user and password in order to initialize the Planner environment. Follow the steps in the Special Instructions. 5. When the installation finishes.exe) again. The special instructions file located in this directory with this file name: x:\download_directory\planner_update_id\E900SpecialInstructions. . click on Cancel to quit.htm where download_directory is the directory where you downloaded the Planner Update. Working with the Deployment Server 3. 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 (JLnnnnn. which are contained within an HTML file that is shipped with the Planner Update. Oracle. If you are re-installing your Deployment Server.properties file does not exist on that machine. the installer may fail to start or complete properly. To detach a database/tablespace. new and changed Batch Version records) from the shipped XML database into the local planner databases.0 onwards you must run R98403XB XJDE0002 because ESUs are shipped with an XML database instead of an MSDE database. run these batch files: detach_planner. Troubleshooting Deployment Server Installation This section discusses: • • • • • General Log Files Configuration Files Path Code Master (F98611) Oracle Enterprise Edition General Invalid vpd. Oracle.Chapter 3.bat R98403XB XJDE0002 For JD Edwards EnterpriseOne Applications Release 9. All rights reserved.properties) for additional details. R98403XB copies control records (for example. Refer to Installer Will Not Start or Complete (Invalid vpd.Rev0 41 . you should ensure that an invalid vpd.bat Copyright © 2008. you must ensure that the local Planner databases (SSE) or tablespace (OEE) are not attached. Working with the Deployment Server Caution Every time you apply a new Planner Update you must run both of these: • • SpecialInstrs. otherwise.properties If you have previously run the Deployment Server installer on your Deployment Server. GA.bat detach_metadata. refer to OEE Logs in this chapter.log n/a \InstallLogs\Configurexxxspec. 42 GA. For example: DetachDV900FAspec.ini setting: [DEBUG] DebugFile=d:\jdedebug.log X:\JDEdwards\E900\log.log x:\jdedebug.log For OEE-specific logs. .log OEE Note The location is defined by this jde.log X:\JDEdwards\E900\SSEInstall.log C:\DotNetSSESetup.Chapter 3.log Note The location is defined by this jde.log X:\JDEdwards\E900\Detachxxx. which contain logging for predefined package specs. Oracle.log X:\JDEdwards\E900\Configurexxxspec. For example: ConfigureDV900FAspec.log x:\jde.log C:\ReconfigureMSDE.log See Also Note where xxx denotes that there are several of these logs. For example: ConfigureDV900FAspec. For example: DetachDV900FAspec.log Note The location is defined by this jde.log \InstallLogs\attach_plannerdata.log Note where xxx denotes that there are several of these logs.log C:\ReconfigureMSDE.log x:\jde.log Note where xxx denotes that there are several of these logs. which contain logging for predefined package specs. Working with the Deployment Server Log Files This table lists the log files for SSE and OEE installations on the Deployment Server: SSE x:\jdedebug.log X:\JDEdwards\E900\Detachxxx.ini setting: [DEBUG] JobFile=D:\jde. All rights reserved.Rev0 Copyright © 2008.ini setting: [DEBUG] JobFile=D:\jde.log n/a n/a \InstallLogs\attach_plannerspec.log Note The location is defined by this jde.log Note where xxx denotes that there are several of these logs. which contain logging for predefined package specs. which contain logging for predefined package specs.log X:\JDEdwards\E900\InstallLogs\attach_plannerdata.ini setting: [DEBUG] DebugFile=d:\jdedebug.txt X:\JDEdwards\E900\Attach_plannerspec. microsoft.ora file.SQLServerDriver ORACLE=oracle. The data source definitions for OEE are defined in these configuration files: • • jde.jdbc.Rev0 43 . jdbj. jde. Working with the Deployment Server Configuration Files Note This section is provided for reference. All rights reserved.jar) used in prior releases of JD Edwards EnterpriseOne.ini SSE Settings [DB SYSTEM SETTINGS] Type=X LOBFlag=N [DB SYSTEM SETTINGS – SECONDARY] Type=X LOBFlag=N OEE Settings [DB SYSTEM SETTINGS] Type=E LOBFlag=Y [DB SYSTEM SETTINGS – SECONDARY] Type=E LOBFlag=Y The jdbj.driver.ini jdbj.ini files appropriately for either the SSE or OEE local database.ini file specifies location of the tnsnames.sqlserver.ini The following tables show a side-by-side comparison of specific settings within the various configuration files that differ depending on where the local database is SSE or OEE in various configuration files.ini SSE Settings [JDBj-BOOTSTRAP DATA SOURCE] databaseType=X lob=false' [JDBj-SPEC DATA SOURCE] databaseType=X lob=false OEE Settings [JDBj-BOOTSTRAP DATA SOURCE] databaseType=E lob=true [JDBj-SPEC DATA SOURCE] databaseType=E lob=true [JDBj-JDBC DRIVERS] [JDBj-JDBC DRIVERS] SQLSERVER=com. GA.jdbc. The jdbj.ini file also specifies the JDBC driver for Oracle as ojdbc5.jar. Oracle.Chapter 3. You are not required to manually configure these files because the Deployment Server installer configures the . which replaces the version (classes12.OracleDriver Copyright © 2008. for SSE your file would look like this: Important The shipped jdbj.jdbc.SQL . In this case.ibm.DB2Driver .ear\webclient\WEB-INF\class es You must manually comment every database driver except the one you are using.ibm. and Package Build. EMDBSY Value 0 1 2 3 5 Spec Type TAM XML TAM XML XML Local DB Type MSDE MSDE SSE SSE Oracle 44 GA.AS400=com.db2.UDB=COM. It contains values for use of EMDBSY column to indicate type of specs and type of local database. These values are used by JDB.jdbc.jdbc.microsoft.microsoft. All rights reserved.ibm.driver.as400.UDB=COM.Chapter 3.app.AS400JDBCDriver SQLSERVER=com.SQLServerDriver . .SQLSERVER=com.jdbc.ini file in the following folder contains specifications for each database type: System\OC4J\j2ee\home\applications \ webclient.ini SSE Settings OEE Settings Important The shipped jdbj.OracleDriver ORACLE=oracle. Working with the Deployment Server jdbj.ear\webclient\WEB-INF\class es You must manually comment every database driver except the one you are using.ibm.as400.jdbc.ini file in the following folder contains specifications for each database type: System\OC4J\j2ee\home\applications \ webclient.jdbc.ORACLE=oracle. JDBj.app.access.AS400=com. for OEE your file would look like this: [JDBj-JDBC DRIVERS] [JDBj-JDBC DRIVERS] .OracleDriver .driver.AS400JDBCDriver .Rev0 Copyright © 2008. Oracle.db2.DB2Driver Path Code Master (F98611) The Path Code Master (F98611) contains change to support SSE and OEE.sqlserver.sqlserver.access. In this case. Working with the Deployment Server Oracle Enterprise Edition This section discuesses these topics: • • • • • • • • • • • • • • File Locations Rebooting the Deployment Server EnterpriseOne Access to the Local Oracle Database Uninstalling the Local Oracle Database Process Explorer Verifying the Local Oracle Database Installation Deployment Server Installation Problems Runtime Problems Administering the Local Oracle Database Using SQL Plus Encrypting the Password of the Local Oracle Database Decrypting the Password of the Local Oracle Database Import and Export Tablespaces to the Local Oracle Database Local Oracle Database Configuration Deployment.Rev0 45 . All rights reserved.Chapter 3. GA.inf Copyright © 2008. Oracle.inf and <Package_name>. ora file is located in these directories: . Log File Oracle import log for data Oracle export log for data Oracle import log for specifications Oracle export log for specifications Location <E1_install_dir>\<pathcode>\Data\imp*. All rights reserved.ora The tnsnames.\admin\E1Local\bdump alert_e1local.log Deployment Server and local Or. Oracle.exe .log acle database install logs Local Oracle database runtime Local Oracle database listener Local Oracle database runtime and listener ReconfigureMSDE. OEE Logs The following table lists the locations of the various log files.log <E1_install_dir>\<pathcode>\Spec\exp*.<E1_dep_svr_install_dir>\InstallLogs\*.. The installation location of the local Oracle database on the Web Development Client (also called the Administration or fat client) is on the same drive as the JD Edwards EnterpriseOne installation.log Tnsnames.\Oracle\E1Local\NETWORK\ADMIN . .ora Oracle Installation Directory Deployment Server.\System\OC4J\j2ee\home\applications\webclient.log .Chapter 3.log C:\ReconfigureMSDE..log <E1_install_dir>\<pathcode>\Spec\imp*.Rev0 Copyright © 2008. Working with the Deployment Server File Locations This sections discusses the location for these critical files: • • • Oracle Installation Directory OEE Logs Tnsnames. The installation location of the local Oracle database on the Deployment Server is: <Drive_with_most_free_space>:\Oracle\E1Local Client.log <E1_install_dir>\<pathcode>\Data\exp*.ear\webclient\WEB-INF\classes 46 GA.\NETWORK\ADMIN\*. GA.Chapter 3. <tablespace_name> For example: • • JDESY900 JDEOL900 <tablespace_name> For example: • • JDESY900 JDEOL900 Note The default password may be changed by DBA. JD Edwards EnterpriseOne accesses the local Oracle database as follows: • Security Server is used JD Edwards EnterpriseOne accesses the system account of the local Oracle database using the generated and encrypted password. Generated and encrypted by the Deployment Server installer. Copyright © 2008. where the install or uninstall should always be done using the JD Edwards EnterpriseOne Deployment Server installer. Local Oracle Database Account System Sys JDE Default Password Generated and encrypted by the Deployment Server installer.Rev0 47 . it must match the password of EnterpriseOne user JDE. All rights reserved. Oracle. EnterpriseOne Access to the Local Oracle Database The Deployment Server installer generates an encrypted password that is used by JD Edwards EnterpriseOne to access the local Oracle database system and sys accounts. JDE Note The default password may be changed by DBA but if Security Server is not used. This table lists the relationship between the local Oracle database accounts and the password. • Security Server is not used JD Edwards EnterpriseOne accesses the local Oracle database using the EnterpriseOne user and password. This value does not affect the runtime operation of JD Edwards EnterpriseOne because it does not access the local Oracle database in this manner. Working with the Deployment Server Rebooting the Deployment Server You must reboot the Deployment Server after installing or uninstalling the local Oracle database. In that case. Refer to Uninstalling the Deployment Server in this guide. Uninstall JD Edwards EnterpriseOne using Add/Remove programs. 48 GA. Uninstall the local Oracle database using the Oracle Universal Installer found in this navigation: Start > All Programs > Oracle – E1Local > Oracle Installation Products > Universal Installer Warning Remove only the E1Local Oracle Home. Working with the Deployment Server Uninstalling the Local Oracle Database To uninstall the local Oracle database: 1. When the E1Local Oracle Home is removed. If you attempt to reinstall the local Oracle database without first deleting this directory it is likely that the reinstall will fail.Chapter 3. Oracle. 2. Delete this directory: <E1_installation_drive>:\Oracle\E1Local Warning You must delete this directory. 4. reboot the Deployment Server machine. . run Process Explorer (described in the next Troubleshooting section) to determine which process(es) has it locked. 3. All rights reserved. Tip You may not be able to delete the directory if a process has it locked.Rev0 Copyright © 2008. GA.sysinternals.Rev0 49 .Chapter 3. and subsequently kill that process.com To use Process Explorer: 1. To obtain the Process Explorer. you can use Process Explorer to determine which process has it locked. All rights reserved. Copyright © 2008. Working with the Deployment Server Process Explorer If you cannot delete the directory for the E1Local Oracle Home because a process has it locked. Oracle. you can download and install a free version at this link: www. Navigate to Find > Find. you will need to reboot the Deployment Server machine.exe). In the Handle or type field. For example: c:\oracle\e1local 3. note the PID(s) that are associated with the specified directory.Rev0 Copyright © 2008. All rights reserved. Use Process Explorer to kill the identified process(es). Working with the Deployment Server 2. killing it may cause the computer to lock up. Then reboot the Deployment Server machine and delete the directory. Cancel the Process Explorer Search window to return to Process Explorer.Chapter 3.exe is the local Oracle database engine. 5. Oracle. Verifying the Local Oracle Database Installation To verify that the installation of the local Oracle database was successful: 1. Click the Search button. Inspect the logs in this directory: <E1_dep_svr_install_dir>\InstallLogs 2. The process Oracle. 7. 6. 50 GA. . If it has a file locked. If one or more of the processes locks a file in the directory you are trying to delete even after rebooting. 4. Note If one or more of the processes is Windows Explorer (explorer. On the search results screen. enter full name of directory that cannot be deleted. If that happens. you can stop the service OracleServiceE1LOCAL. Resolve any issues that are identified in the logs. you may have to determine which service is automatically starting that process and change the service to manual startup. Working with the Deployment Server Deployment Server Installation Problems You cannot reinstall the local Oracle database using the Deployment Server installer if there are indications that the local Oracle database already exists. SQLPlus.log shows OCI0000141 Error . tnsnames. In order to maintain functionality of the Oracle client.ora used by E1Local. If you have both the local Oracle database and the Oracle client (for example. It is possible that the service may not have started due to slow bootup of machine. If so.Error . This registry key exists: \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_E1Local Runtime Problems This section discusses: • • • Jde.ORA-01017: invalid username/password. If the following command executes successfully. you must encrypt the password in order to enable database access. GA.Chapter 3. the \bin directory is added to the start of the Windows PATH. Oracle.ORA-01017: invalid username/password. Refer to Encrypting the Password of the Local Oracle Database in this section.log shows OCI0000141 . you should add the Enterprise Server tnsnames entries into the tnsnames. if you are connecting to an Oracle database on a machine other than the Deployment Server). logon denied tnsnames.ora are used. which is located in this directory: <E1_installation_drive>:\Oracle\E1Local\network\admin Copyright © 2008. The Deployment Server installer will skip the installation of the local Oracle database if either of these conditions are true: • • The local Oracle database service OracleServiceE1LOCAL is running.log shows ORA-12541: TNS:no listener Verify that the Oracle listener service OracleE1LocalTNSListener is running. it means that the password is not encrypted.ora Jde. User gets a pop-up window prompting for E1Local DB user and password and Jde. the local Oracle database version of the executables and tnsnames.Rev0 51 .exe system/admin@E1Local If the password was decrypted with ReconfigureMSDE.exe.log shows ORA-12541: TNS:no listener User gets a pop-up window prompting for E1Local DB user and password and Jde. you should re-encrypt it using ReconfigureMSDE.ora When the Deployment Server installer installs the local Oracle database (E1Local). logon denied Verify the E1Local database system account password is valid. All rights reserved. exe -TORACLE Decrypting the Password of the Local Oracle Database To decrypt the system account password: 1. the syntax of the SQLPlus command is: SQLPlus. If one of these scripts fails to complete (for example. Open a Command Prompt window.exe <user>/<password>@E1Local For example.exe JDESY900/JDESY900@E1Local Encrypting the Password of the Local Oracle Database JD Edwards EnterpriseOne connects to the local Oracle database (E1Local) through the system account using an encrypted password. Upon exit. You can use SQLPlus. 2. use the following to sign in: SQLPlus. Some of the administrative database scripts on the Deployment Server decrypt this password before submitting database commands. You can determine if this is the case by attempting to sign into the local Oracle database using this command: SQLPlus. a command-Prompt version is provided with the installation of the local Oracle database using the Deployment Server installer. Working with the Deployment Server Administering the Local Oracle Database Using SQL Plus By default. Open a Command Prompt window. EnterpriseOne will not be able to connect to the database.Chapter 3. such programs subsequently then re-encrypt the password. it is killed or it otherwise dies) before it can encrypt the password again.Rev0 Copyright © 2008. if the tablespace is JDESY900. Decrypt the E1Local database system account password using this command: ReconfigureMSDE. To sign into a tablespace.exe to access the local Oracle database where both the user and default password are same as tablespace name. Change directory to: <E1_install_dir>\system\bin32 3. Encrypt the E1Local database system account password using this command: ReconfigureMSDE. 2. .exe system/admin@E1Local If you cannot sign on because the password is decrypted. you must re-encrypt the system account password as follows: 1.exe -TORACLE -U 52 GA. Oracle. Change directory to: <E1_install_dir>\system\bin32 3. All rights reserved. bat) To use the import tablespace script: 1. For example: *** need path on Deployment Server *** 2. To import or export the Planner tablespaces.bat file such that any tablespaces that you do not intend to import are commented out. Working with the Deployment Server Warning If you manually decrypt the system account password.bat files to the location of the Oracle . Open a command prompt window.bat) Export Tablespace Script (detach_planner. Import and Export Tablespaces to the Local Oracle Database You can use the JD Edwards EnterpriseOne application P96717 to import and export tablespaces except the Planner.bat c:\Oracle c:\JDEdwards\E900 Copyright © 2008. Copy *. Run the batch file to import the tablespace using this syntax: attach_planner.dbf and . All rights reserved.dmp files. Change directory to the location of the batch files. 6.bat) Import Tablespace Script (attach_planner. 5. ensure that you re-encrypt the password before attempting to run JD Edwards EnterpriseOne.BAT 4. you must use scripts that are delivered with the installation of the Deployment Server. Copy the ReconfigureORCL. These lines start with: call IMPORT_TABLESPACE.bat <Oracle_dir> <E1_install_dir> For example: attach_planner. Edit the attach_planner. specs and serialized objects): <E1_deployment_server_install_dir>\planner\spec This section discusses: • • Import Tablespace Script (attach_planner. JD Edwards EnterpriseOne will fail because it cannot access the local Oracle database.Chapter 3.bat file to this directory: <E1_install_dir>\misc 3. The scripts are located in this directory: For Planner Databases: <E1_deployment_server_install_dir>\planner\data For local metadata repository database (for example. If the password is not encrypted.sql and *. GA.Rev0 53 . Oracle. .bat 54 GA.Rev0 Copyright © 2008. Oracle.Chapter 3. All rights reserved. Working with the Deployment Server Note This import batch file for the local metadata repository is in the spec directory: attach_metadata. Change directory to the location of the batch files.bat) To use the export tablespace script: 1. Edit the detach_planner.bat <Oracle_dir> <E1_install_dir> For example: detach_planner.bat c:\Oracle c:\JDEdwards\E900 Note This export batch file for the local metadata repository is in the spec directory: detach_metadata. Run the batch file to import the tablespace using this syntax: detach_planner.Chapter 3.bat Local Oracle Database Configuration The install. specification. Open a command prompt window. GA.Rev0 55 . Oracle. 3. Working with the Deployment Server Export Tablespace Script (detach_planner. Important Note that the ". These lines start with: call EXPORT_TABLESPACE.bat file such that any tablespaces that you do not intend to import are commented out. [ThirdPartyApps] ORACLE=ThirdParty\ORACLE. All rights reserved." character is required as the suffix for the ORACLE=ThirdParty\ORACLE. The local Oracle database configuration requires Oracle DB installer be located in this directory: <dep_svr_install_dir>\OneWorld Client Installer\ThirdParty\Oracle Copyright © 2008. 4.ini file specifies that the OEE database will be installed by the Web Development (fat) client installer.BAT 2. <Package_name>. All rights reserved. Deployment.inf (example from a DV900FA.inf and <Package_name>.dmp [SPEC_DV900FA] SourceTableSpace=SPEC_DV900FA Server=127.ldf [SPEC_DV900FA] Server=(local)\JDESSELocal UserID=sa Passwd= DataFileDestDir=$DDV900\Spec\ SPEC_DV900FA.inf that differ depending on where the local database is SSE or OEE.inf The following table shows a side-by-side comparison of specific settings within the Deployment.inf file) SSE Settings [MSDE Databases] JDELocal_DV900=SSE SPEC_DV900FA=SSE [JDELocal_DV900] Server=(local)\JDESSELocal UserID=sa Passwd= DataFileDestDir=$DDV900DATA\ JDELocal_DV900.inf SSE Settings OEE Settings [ThirdPartyApps] [ThirdPartyApps] SSE=ThirdParty\SSE\DotNetSSESetup. Oracle. ORACLE=ThirdParty\ORACLE\E1Local.mdf LogFileDestDir=$DDV900\Spec\ SPEC_DV900FA.1 UserID=SYSTEM DataFileDestDir=$DDV900DATA\ JDELocal_DV900.ldf OEE Settings [Oracle Databases] JDELocal_DV900=ORACLE SPEC_DV900FA=ORACLE [JDELocal_DV900] SourceTableSpace=JDELocal Server=127. ORACLE=ThirdParty\ORACLE\E1Local.exe.1 UserID=SYSTEM DataFileDestDir=$DDV900\Spec\ SPEC_DV900FA.SSE=ThirdParty\SSE\DotNetSSESetup.ldf 56 GA.cab.inf and <Package_name>.mdf LogFileDestDir=$DDV900\Spec\ SPEC_DV900FA.Chapter 3.0.0.Rev0 Copyright © 2008.0.cab.dbf DumpFileDestDir=$DDV900DATA\ JDELocal_DV900.mdf LogFileDestDir=$DDV900DATA\ JDELocal_DV900. Working with the Deployment Server Deployment.0.exe. . Chapter 4.Rev0 57 . Oracle. GA. All rights reserved. Working with the Platform Pack This chapter discusses: • • • • • • • • • Understanding the Platform Pack Preparing the SQL*Server Database Configuring the Enterprise Server Prior to Installing the Platform Pack Understanding the Platform Pack Installation Installing the Platform Pack Troubleshooting Platform Pack Installation 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. ES Production tion ES Prototype ES Development ES Pristine Database Server System Database Production Databases Prototype Databases Development Databases Pristine Databases Note Microsoft Windows Considerations. As detailed in the Minimum Technical Requirements. . install any Microsoft Windows server upgrades that are required to support Release 9.Rev0 Copyright © 2008. You must also follow the special instructions that are included in that Planner Update.0 administrator user. 58 GA. All rights reserved. refer to Rerunning the JD Edwards EnterpriseOne Platform Pack Installer. verify disk space. and the HTML Web Server (also previously known as JAS) assuming the installation programs are run on different machines. Microsoft clustering is supported for system failover protection. 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 Warning If you are using the SQL Server 2005 database.0 software on the Microsoft Windows Enterprise Server. Before you install Release 9.Chapter 4. Oracle. Refer to the Minimum Technical Requirements for details on the Planner Update required to support SQL Server 2005. prior to running the Platform Pack you must download the latest Planner Update that supports that database version. and set up and verify the hosts file. Note You can concurrently install the Deployment Server. you must create the Release 9. This table lists the mandatory and optional components of the Platform Pack installation: Server Enterprise Server Mandatory Component Optional Components JD Edwards EnterpriseOne Founda.0. This can decrease the overall time it takes to complete the installation. Note To reinstall any Enterprise Server components. the Platform Pack. you may need to run some stored procedures to ensure your ODBC driver operates properly with the JD Edwards EnterpriseOne databases which the JD Edwards EnterpriseOne Platform Pack Installer delivers. The database administrator must understand how to maintain the Release 9. and system implementation personnel should read this chapter in preparation for installing the enterprise or deployment relational database management systems (RDBMS). From an ISQL window. Review the LocalCodeSet and code page settings for your database machine environment. The database administrator must install the RDBMS before the software implementation team arrives. loaded. and maintained for use with Release 9. Prior to using the JD Edwards EnterpriseOne Platform Pack Installer to load any databases. GA. you must already have a DBMS installed on the target machine. configured. the correct code page settings must be in your database. Verifying code page settings for SQL Server The procedure in this section outlines the minimum requirements of a SQL Server environment to run Release 9. Refer to Using Instcat. the database might still require significant modifications. This guide does not discuss RDBMS installation details.0.Rev0 59 .Chapter 4. Tip Database Integrity Consideration. such as tuning the system. database administrators. enter this command: sp_helpsort Copyright © 2008. Note When installing an alternate language. You should consult cluster installation documentation for the specific DBMS before beginning the Enterprise Server installation. After completing this procedure. When installing the database. All rights reserved. Caution If cluster software is used in conjunction with a DBMS additional considerations exist. After you install your Platform Pack for SQL Server. creating backup or recovery procedures and jobs. A qualified database administrator should be present when the databases are installed.sql to Support SQL Server and SSE ODBC for requirements and operational details.0. set up the code page for the language before loading your language specification objects for Release 9. and maintaining or expanding the database system. Oracle.0 database.0. and before you start your JD Edwards EnterpriseOne server. Working with the Platform Pack Preparing the SQL*Server Database This chapter discusses: • • General Considerations Verifying code page settings for SQL Server General Considerations System administrators. Oracle. . Working with the Platform Pack Caution If the character set is incorrect. 60 GA.Chapter 4. See Also Refer to the Language Process Overview for the National Language Support tables and other information related to multilingual installations. recreate the database with the correct character set. All rights reserved.Rev0 Copyright © 2008. Oracle. 4. not one of the server names. If clustering is being used. Microsoft Cluster Administrator Guide or Microsoft Windows Server 4 Second Edition for more information on using cluster software.0 on a Cluster section in JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide for more information about clustering. Release 9. Working with the Platform Pack Configuring the Enterprise Server Prior to Installing the Platform Pack This section discusses: • Setting Up and Verifying the Hosts File See Also Verifying Software and Hardware Requirements for more information about software requirements. you do not need to set up and verify the hosts file. Using Microsoft Windows Explorer. and a machine name. verify that the cluster name is used as the machine name. and that there is a return character at the end of each line. Copyright © 2008. To set up and verify the Hosts file: 1. GA. A pound sign (#) marks the start of a comment. 3.Chapter 4. Setting Up and Verifying the Hosts File If you use the Domain Naming Service (DNS) or the Microsoft Windows Internet Naming Service (WINS). All rights reserved. Verify that the address and name are each on a separate line. access this directory: \Winnt\System32\Drivers\Etc\Hosts 2. you will need a machine IP address. For each Enterprise Server on your network. and the end-of-line (return) character marks the end of a comment.Rev0 61 . .Chapter 4. All rights reserved. The diagram below illustrates the process flow and the various installation paths. Working with the Platform Pack Understanding the Platform Pack Installation The Platform Pack installation process installs Release 9.Rev0 Copyright © 2008. Oracle. 62 GA.0 system and path code files. Oracle.Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) .Chapter 4.or Database only SQL*Server . All rights reserved.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 Copyright © 2008. GA. 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 and Security Options SQL*Server .Rev0 63 . Refer to Installer Will Not Start or Complete (Invalid vpd. you can view the progress on the InstallShield Wizard dialog that appears on your screen or Task Bar. you must name the CD images disk1.properties file does not exist on that machine. the installer may fail to start or complete properly. Insert the JD Edwards EnterpriseOne Platform Pack Installer CD into the CD drive. If the setup does not begin automatically or if you wish to start the installation manually. 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. . Tip The InstallShield process creates temporary files during the install. Warning Ensure that the Administrator account name that you use does not contain any special characters. Refer to the begining of the section entitled: Installing the Deployment Server for a procedure you can use to increase your disk space. Note The InstallShield Wizard begins to initialize and prepare the requisite JVM for the JD Edwards EnterpriseOne Platform Pack Installer. Warning If you have previously run the Platform Pack installer on your Enterprise Server. All rights reserved. When the initialization is complete.Rev0 Copyright © 2008. disk3. By default these will be placed on the c: drive of a Windows machine. The setup starts automatically. 2. Although this may take a few minutes to completely initialize.exe (which is called by the autorun. 64 GA.exe file which is located at the root of the installation disk. the JD Edwards EnterpriseOne Platform Pack Installer will not find them. To run the JD Edwards EnterpriseOne Platform Pack Installer: 1.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. otherwise. The RunInstall. Log on to the Enterprise Server as a user with Administrative rights. a new and separate JD Edwards EnterpriseOne Platform Pack Installer window is displayed. If you directly execute the JD Edwards EnterpriseOne Platform Pack Installer (setupWin32.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. setupwinIA64. you should ensure that an invalid vpd.exe or setupwinAMD64. Oracle.properties) for additional details. you can execute the RunInstall. and so on. disk2.Chapter 4. Otherwise. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully.exe. All rights reserved.Chapter 4. Welcome. click Next. On JD Edwards EnterpriseOne Platform Pack Installer. Copyright © 2008. Working with the Platform Pack 3. GA.Rev0 65 . Oracle. . The default value is: c:\JDEdwards\E900 66 GA. Oracle. directory selection panel.Chapter 4. complete this field: Directory Name Enter the drive and directory where you want the files installed on your Enterprise Server. Working with the Platform Pack 4. On JD Edwards | EnterpriseOne Platform Pack Installer. 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. All rights reserved.Rev0 Copyright © 2008. In this mode. the JD Edwards EnterpriseOne Platform Pack Installer aborts. Caution Upgrade You should always back up all databases that you want to preserve. Copyright © 2008. 5.Chapter 4. The Upgrade Mode is described in a separate document entitled: JD Edwards EnterpriseOne Release 9. Oracle. Working with the Platform Pack If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer. Refer to the following table for a full description of each run mode.0 Upgrade Guide. if either exists. This prevents the inadvertent overwriting of existing critical business data and control tables.Rev0 67 . choose whether you want to install or upgrade JD Edwards EnterpriseOne. In this mode. refer to Rerunning the JD Edwards EnterpriseOne Platform Pack Installer. Click Next. the JD Edwards EnterpriseOne Platform Pack Installer checks for the existence of JD Edwards EnterpriseOne business data and control tables. 6. GA. the installation process continues normally. If the JD Edwards EnterpriseOne Platform Pack Installer does not detect pre-existing JD Edwards EnterpriseOne data or control tables. All rights reserved. On the Run Mode selection panel. 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. Install This document only describes the Install Mode. 68 Click Next. you can skip directly to Database and Security Options located later in this task to complete the Platform Pack installation. All rights reserved. Tip If you choose Typical installation. setup type panel. . Recommended for experienced users. This installation option is recommended for most users and includes the required JD Edwards EnterpriseOne files for the Prototype and Pristine environments. On JD Edwards | EnterpriseOne Platform Pack Installer.Rev0 Copyright © 2008. choose your installation type: Typical Choose this setup type if you wish to complete the Platform Pack installation with no further specifications. continue with the steps below in this task which immediately follow. GA.Chapter 4. Custom Tip If you choose Custom installation. choose this setup type if you wish to complete the Platform Pack installation by specifying the installation of a subset of pre-defined environments. Working with the Platform Pack Note If you chose Upgrade mode. 7. 8. Oracle. 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. GA. Working with the Platform Pack Copyright © 2008. Oracle.Chapter 4. All rights reserved.Rev0 69 . select from these choices: JD Edwards EnterpriseOne – Enterprise Server • JD Edwards EnterpriseOne Foundation Note This selection includes system files. . If you do not select this feature.Rev0 Copyright © 2008. Oracle. the JD Edwards EnterpriseOne Platform Pack Installer checks your system to verify that the JD Edwards EnterpriseOne Foundation is already installed. If you are installing in Custom Mode. If you chose Typical Mode. If not. All rights reserved. the JD Edwards EnterpriseOne Platform Pack Installer automatically selects it for installation.Chapter 4. 1. • • • 70 ES Production ES Prototype ES Development GA. You must choose this feature for all initial installations of the Enterprise Server. you can skip to Database and Security Options. features panel. Working with the Platform Pack Custom Mode Feature Selection Note This section is only applicable if you chose Custom installation mode. on JD Edwards | EnterpriseOne Platform Pack Installer. Oracle. Working with the Platform Pack • ES Pristine JD Edwards EnterpriseOne – Database Server • System Database Note This selection includes mandatory system files. you must either select OK to acknowledge that the selection of the mandatory system files. it selects them automatically and displays a warning message. Copyright © 2008. Likewise. drive. All rights reserved.Rev0 71 . If you do not select this box and the JD Edwards EnterpriseOne Platform Pack Installer can not detect the required system files.Chapter 4. On the warning message. or directory that is different from that which contains the JD Edwards EnterpriseOne Files. or click Back and change your selections manually. 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. GA. • • • • 2. Production Databases Prototype Databases Development Databases Pristine Databases Click Next to continue. Rev0 Copyright © 2008. The JD Edwards EnterpriseOne Platform Pack Installer validates the Database Server name and compares it against the name of the local computer. If you wish to change the default password that the JD Edwards EnterpriseOne installer uses to connect to your database. Typical or Custom. complete these fields: Database Type Database Server Name Use the pulldown menu to choose SQL*Server. you can enter a secure password. Working with the Platform Pack Database and Security Options Regardless of which installation type you chose. you must enter database options as described in this procedure. Oracle. and the database server name that you entered cannot be validated. For additional details on error conditions. the JD Edwards EnterpriseOne Platform Pack Installer automatically detects and populates this field with the machine name on which it is running. If these values are different (for example. . All rights reserved. an error dialog is displayed with resolution instructions. If you have selected to install databases. if you manually change the value of this field). The maximum length of the password is 10 characters. By default. Secure Password: (for database users) 72 GA. 1. On JD Edwards | EnterpriseOne Platform Pack Installer. Database Options.Chapter 4. the JD Edwards EnterpriseOne Platform Pack Installer assumes the Database Server is a clustered server. refer to Troubleshooting Platform Pack Installation. then by default the system creates a corresponding password of JDE for that user. All rights reserved. If you fail to synchronize these database password settings. Click Next. Working with the Platform Pack Note If you do not change the default vaule (DEFAULT). Copyright © 2008.Rev0 73 . the various Installation Workbenches will not be able to connect to the database. GA. Warning If you change the default password in the Platform Pack installation for your Enterprise Server.ini on the Deployment Server and specify the new secure password that you are using. For example. 2. you must also manually change the [DSPWD] section in the jde.Chapter 4. if a user ID is JDE. the system creates a password for each user where the password is the same as their user ID. Oracle. or that you are installing a database only.or Database only SQL*Server .Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) . All rights reserved. use the pulldown menu to choose the appropriate instance.Enterprise Server Only (Different Machine from Database Server) SQL*Server . Working with the Platform Pack When choosing the database. The JD Edwards EnterpriseOne Platform Pack Installer cannot proceed unless it detects a valid SQL instance. .Rev0 Copyright © 2008. consider these scenarios depending on which machine the database resides: • • SQL*Server .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. Oracle. If multiple instances exist. 1. 74 GA.Chapter 4. On the database instance panel. complete these fields: Database Server Instance The JD Edwards EnterpriseOne Platform Pack Installer automatically detects the name of the server and the instance name of the installed SQL*Server database on the database server on which it is running. Copyright © 2008. complete this field: Database Directory Location Enter the directory location in which you want to create your Microsoft SQL databases. Do not install the RDBMS system in a location with a child relationship to the JD Edwards EnterpriseOne installation directory. All rights reserved. For example: d:\database_location Note The Installer automatically appends the path you enter here with \MSSQL. Instance SA Password 2. Working with the Platform Pack Note The Installer automatically appends the path you enter here with \MSSQL. On the database instance information panel.Rev0 75 . x:\JDEdwards. Oracle. GA.Chapter 4. Warning You should always consult with a DBA for the proper location of the RDBMS system on your machine. enter a valid password for the system administrator of your SQL Server database. This practice avoids any potential where actions against the parent directory might adversely impact the child directory. For the selected instance. Rev0 Copyright © 2008. . 76 GA.Chapter 4. Click Next and proceed to Database and Security Options in this task. Oracle. All rights reserved. Working with the Platform Pack 3. 2. Oracle. Working with the Platform Pack SQL*Server .Chapter 4. On the database instance panel. Copyright © 2008. GA. Since the JD Edwards EnterpriseOne Platform Pack Installer does not verify this value. complete this field: Database Instance Name Enter a valid value for the database instance. you should ensure that it is correct.Rev0 77 .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. Click Next and proceed to Database and Security Options in this task. All rights reserved. 1. 78 GA. 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. All rights reserved.Chapter 4. click Next. Oracle. .Rev0 Copyright © 2008. On JD Edwards | EnterpriseOne Platform Pack Installer.Chapter 4. Oracle.Rev0 79 . The values you enter on this screen. 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. is used by the JD Edwards EnterpriseOne Platform Pack Installer to calculate and set certain JDE. All rights reserved. 1. 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. along with the selection or deselection of the specified JD Edwards EnterpriseOne applications. GA.INI settings that will result in optimal server performance for the JD Edwards EnterpriseOne installation. . 2.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.Rev0 Copyright © 2008.INI on the Enterprise Server for optimal performance. All rights reserved. 80 GA. Click Next to continue. Oracle. review the list of installation components and click Next to begin the installation. On the Summary Information Panel.Chapter 4. Copyright © 2008. Oracle. All rights reserved.Rev0 81 . GA. 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. 2. . Note After the Enterprise Server portion of the JD Edwards EnterpriseOne Platform Pack Installer is complete. You can proceed to the next major section in this guide entitled: Planning the Installation. after the installation is complete. This occurs if certain Microsoft Windows systems files are in use at the time of installation and therefore cannot be modified in real time. Working with the Platform Pack On JD Edwards | EnterpriseOne Platform Pack Installer. You have successfully completed the Typical installation of the Platform Pack for the JD Edwards EnterpriseOne Enterprise Server. The Platform Pack Installer creates a log. a panel may appear directing you to reboot the machine to complete the installation. For example: drive:\JDEdwards\E900 82 GA.Rev0 Copyright © 2008. Click Finish to complete the installation and exit the JD Edwards | EnterpriseOne Platform Pack InstallShield Wizard.txt file in the directory where you installed the Platform Pack. Therefore. Verifying the Platform Pack Log File You can verify that the Platform Pack Installer ran properly by viewing the log file. in such cases the installation cannot be completed until the machine is rebooted. Oracle. a message appears stating that the installation was successful.Chapter 4. All rights reserved. Oracle.properties) Business Data and Control Tables Already Exist Business Data and Control Tables Do Not Exist System Database Not Detected Foundation Files Do Not Exist Copyright © 2008.Chapter 4. GA.Rev0 83 . All rights reserved. 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. 0 which were installed using InstallShield the vpd. For JD Edwards EnterpriseOne Release 9. To resolve this situation. However.properties) If either the Deployment Server or Platform Pack installer indicates that the product is installed when it is not. The Uninstaller removes any problematic entries from vpd. Working with the Platform Pack Installer Will Not Start or Complete (Invalid vpd. by renaming the file instead of deleting it.properties file is shared by other programs that were installed using InstallShield. Location of vpd. run the InstallShield Uninstaller before attempting a reinstallation.Rev0 Copyright © 2008. If you have an existing vpd. invalid entries may exist in the vpd. your Windows system directory might be c:\Windows. .properties File Installer Directory Containing the vpd. Refer to the following table for locations of the vpd. 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.Chapter 4.12 and Release 9. This file is used by Installer to record installed components. or c:\winnt. or if the installation is interrupted before it completes.properties File Deployment For Release 9. You should rename instead of delete because in JD Edwards EnterpriseOne releases prior to Release 8. Oracle.properties file on the Deployment Server and the Enterprise Server. if the Installer is interrupted this file may contain references to components that may not yet have been successfully installed.0: C:\Program Files\Common Files\InstallShield\Universal\JDEdwardsDepSvr\E900 Platform Pack For JD Edwards EnterpriseOne Releases Prior to Release 8.12: In the Windows system directory. All rights reserved.properties file.properties file that you cannot repair or remove by running the InstallShield Uninstaller. For example. you should rename it.0: C:\Program Files\Common Files\InstallShield\Universal\JDEdwardsPPack\E900 84 GA.0: Server C:\Program Files\Common Files\InstallShield\Universal\JDEdwardsDepSvr\E900 For Release 9. Therefore.0: C:\Program Files\Common Files\InstallShield\Universal\JDEdwardsPPack\E900 For JD Edwards EnterpriseOne Release 9.properties and also removes any components that have already been installed. To resolve the error condition. 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. 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 databases already exist for the selected environment. If you receive this error. Copyright © 2008. you must uninstall the referenced database as specified by the text in the error. All rights reserved. GA.Chapter 4. Oracle.Rev0 85 . you must go back and select Install instead of Upgrade. Test. a separate error panel is displayed for each environment (such as Production. already exists. Development. 86 GA. or CRP) that you selected. but does not already contain the mandatory DTA and CTL databases. Oracle. 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 databases do not exist for the selected environment.Chapter 4. That is. All rights reserved. To resolve the error condition.Rev0 Copyright © 2008. . 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. Alternately you can manually navigate backwards and make additional changes to your existing selections. Therefore.Chapter 4. If you receive this error. Working with the Platform Pack System Database Not Detected This screen indicates that the JD Edwards EnterpriseOne Platform Pack Installer has not detected the mandatory System database. as a user convenience.Rev0 87 . Copyright © 2008. GA. All rights reserved. After the JD Edwards EnterpriseOne Platform Pack Installer displays this error. at this point you can continue with the installation which will include the mandatory components. it automatically selects the mandatory Database Foundation Components for installation. Oracle. 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. 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. Alternately you can manually navigate backwards and make additional changes to your existing selections. it automatically selects the mandatory Enterprise Server Foundation Components for installation.Chapter 4. . as a user convenience. 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. All rights reserved. at this point you can press to continue with the installation which will include the mandatory components.Rev0 Copyright © 2008. 88 GA. Therefore. If you receive this error. Oracle. You want to reinstall the JD Edwards EnterpriseOne Foundation on the Enterprise Server. you must specify the same machine. You want to reinstall the System Database on the Database Server. Database Server If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer in order to add databases. All rights reserved. If you select to uninstall the mandatory components you must also select to uninstall or have already uninstalled all related optional components. 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. 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. Oracle.Rev0 89 . You want to add a Database Server database to the Database Server. You want to add an Enterprise Server environment to the Enterprise Server. drive. Copyright © 2008. you must specify the same machine.Chapter 4. and directory as that which you selected for JD Edwards EnterpriseOne Foundation during the initial installation of the Platform Pack. You should never reinstall any optional components without first uninstalling the components. GA. and directory as that which you selected for System Database during the initial installation of the Platform Pack. drive. Oracle. 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. All rights reserved. To install the latest tools release and latest tools release patch: 1. 2.A1) and Tools Release documentation.Chapter 4. 8. . install the Tools Release Patch to the Enterprise Server.98.Rev0 Copyright © 2008. From the Update Center homepage.98 Installation Guide. Using the Tools Release documentation. refer to JD Edwards EnterpriseOne Tools Release 8. download the latest Tools Release Patch (for example. For instructions on installing the tools release. which is available by platform on Customer Connection. 90 GA. you should change the passwords on all table owners created during the Platform Pack installation. 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. if you are changing the JDE user's password to apples.ini file. your section would look like this: [DSPWD] JDE=apples Note You must also logon to JDEPLAN using the changed password. Once the database passwords have been changed. Using the above example of a changed password. GA.ini file: [DSPWD] Datasource_owner=new_password For example. 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. Working with the Platform Pack Working with Database Security In order to maximize your database security. Therefore.ini file: [DSPWD] JDE=new_password For example.Rev0 91 . unless it finds this override in the jde. you will need to add this section to the jde.ini file on the Deployment Server. you cannot use passwords greater than 10 characters even if your RDMS allows it. you will need to add this section to the jde. you should also change the password on the JDE user and add an override in the [DSPWD] section of the jde. Once the database passwords have been changed. Copyright © 2008.Chapter 4. All rights reserved. The Installation Workbench assumes that the table owner’s password is the same as the table owner. Oracle. As a security precaution. these are created with the user and password equal to the same value. Consult with your DBA for advice on changing passwords to meet the security requirements of your database installation.ini file on the Deployment Server. otherwise database connections will fail. Such a user and password relationship could expose you to worms and viruses aimed at gaining access to your database. .ini file.ini file match that of your database. You should delete the [DSPWD] section once the install or upgrade is complete. Working with the Platform Pack After you change the [DSPWD] section of the jde. as recommended for security purposes. Warning Whenever you change the password on your database.Rev0 Copyright © 2008.ini file on the Deployment Server to prevent unauthorized access. Refer to Working With Signon Security in this guide for applicable instructions. Oracle. You should secure the jde. you must also ensure that your security settings in the Enterprise Server jde. logon to OneWorld in the JDEPLAN environment on the Deployment Server with the new password in the correct case.Chapter 4. All rights reserved. 92 GA. Rev0 93 . Oracle. 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. GA.Chapter 5. All rights reserved. Oracle.Chapter 5.Rev0 Copyright © 2008. . 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 94 GA. All rights reserved. Working with Installation Planner Understanding Installation Planner Installation Planner is a Release 9.0. It is a system administration tool to guide through the process of configuring the machines on which you will run Release 9.0 application that runs on the Deployment Server. Chapter 5.Rev0 95 . Refer to the section Release 9. GA. Locations are stored in the Deployment Locations Definition table (F9654). It is the central point for planning and executing the deployment process. Oracle. so you must create one for each server. 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. Installation Planner populates the F9650 and F9651 Enterprise Server tables and defines the data sources for the Enterprise Server. See Also Refer to Creating a Remote Installation Plan for information about setting up remote locations. You can have any number of tiered locations. Location Information Locations are user-defined groups of machines. and the database it uses.0 on a Cluster in Server and Workstation Administration for more information before attempting the installation. To set up locations for installation plans. The Data Source information is stored in the Data Source Master table (F98611). Two types of locations exist: base locations and remote locations. and parent location (if there is a secondary location). and stores additional Deployment Server information in the Machine Master (F9650) and Machine Detail (F9651) tables. All rights reserved. Deployment Server Information To set up the plan information for the Deployment Server. This location code is used as part of the name of the data sources for secondary locations in the plan. and environments. Copyright © 2008. Each installation plan can have only one base location.0. This information populates the Release Master (F00945) and Path Code (F00942) tables. The use of multiple locations is recommended for configurations across a wide area network (WAN). The location code is a three-character alphanumeric code that you specify. Refer to Creating a Language-Only Installation Plan for more information about setting up an alternate language after the master plan. you must provide the installation program with the machine name and the directory share name. databases. each has a parent location and a location code. • • You should follow the system prompts to choose which languages will be installed for each environment. The base location does not have a parent location and does not use a location code. you must provide the installation program with the location. location code (if there is a secondary location). additional issues must be considered before installing Release 9. If you want to use cluster software. location description. For initial installations. you must provide Installation Planner with the name of the Enterprise Server. This is required because Server Map data sources are specific to each Enterprise Server. you can complete your master plan and install languages later by creating a languageonly plan. Enterprise Server Information To set up the plan for the Enterprise Server. The process also involves setting up multiple Server Map data sources for the Enterprise Server. its platform type. Object Librarian .CRP. its platform type. Control Tables . 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.900). System . Central Objects PD900.900). You must also set up these data sources for each environment: • Control Tables This is the data source for the Control Tables. and other information.0 release (for example.0.PS900. and Central Objects .DV900. It is identified by the Release 9. • Versions 96 GA.TEST. You can have multiple sets of Central Objects specifications (for example.Chapter 5. Business Data . Business Data . You can have multiples (for example.Test.0 release (for example.900).PROD. you can have only one Central Objects data source for each path code. It is identified by the Release 9.PY900).Prod. and Control Tables . Business Data . You can have multiple sets of Business Data data sources (for example. unlike prior JD Edwards EnterpriseOne releases.0 Data Dictionary tables. • Data Dictionary This is the data source for the Release 9. Warning For Release 9. and Business Data PS900). . Installation Planner populates the F9650 and F9651 Enterprise Server tables. Data Source Information When you run Installation Planner. Control Tables . Oracle. • Business Data This is the data source for the Business Data tables. Data Dictionary .Rev0 Copyright © 2008. • Object Librarian This is the data source for the Object Librarian tables.CRP). these data sources are set up once and shared across all environments: • Server Map Server Map data sources are specific to each Enterprise Server. However.0 release (for example. the enduser applications are only accessible through a web interface. • System The data source for the System tables. Central Objects . Central Objects . so you must create one for each server. a JD Edwards EnterpriseOne HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because. • Central Objects The data source for the Central Objects specification tables is identified by the type and version number of the software. All rights reserved. It is identified by the Release 9. All rights reserved. Versions .0 Installation fixes are required. Copyright © 2008.0 Installation is to include the most current tools releases and updates at the time the CD is mastered.Rev0 97 . subsequent to that time it is possible that critical fixes may become necessary and available.DV900. and Versions .PD900.PY900). or you can choose to define them manually and override the default data load options. GA. Versions . You can have multiple sets of versions tables (for example. Likewise. However. Installation Planner enables data load using default data load options. You should check Customer Connection to verify if any such JD Edwards EnterpriseOne Release 9.PS900. However. Working with Installation Planner The data source for the Versions List table (F983051). or you can choose to define them manually. you can have only one Versions data source for each path code.Chapter 5. Versions . Oracle. 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. Working with JD Edwards EnterpriseOne Software Requirements The goal of the JD Edwards EnterpriseOne Release 9. you must first log on to Release 9. If processing options are not set up correctly. Assumptions About Reviewing Installation Planner Processing Options This table lists the assumptions about reviewing the processing options for the installation planner. Access the planner environment (JDEPLAN). Accessing Processing Options To access processing options. On the Deployment Server.Rev0 Copyright © 2008. . All rights reserved. 4. Oracle. Personnel Logon Status Prerequisites Concurrent Tasks Installer. in the Planner environment. you will not see the appropriate options as you work through the planner. 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. 98 GA.0 and specify your installation plan type.Chapter 5. If you do not want to see these messages. logged on as user JDE with the database password for user JDE. Choose Prompt for Values. The Processing Options form appears. 3. First-time users can set up the processing options to step through the planner with informational messages. From the System Installation Tools menu (GH961). The Platform Pack installer can be running. you can turn them off. You set up these processing options to control replication functions and business functions mapping. right-click either Typical Installation Plan or Custom Installation Plan.0 as user JDE with the database password for user JDE. The Deployment Server must be installed. You should review the default processing options for the Installation Planner application prerequisite to create the plan. 2. Log on to Release 9. 1. All rights reserved. Working with Installation Planner Choosing Processing Option Values Once you have accessed processing options. Oracle. GA.Rev0 99 .Chapter 5. 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. Select the Prompt Mode tab. Working with Installation Planner Specifying the Prompt Mode To specify the prompt mode: 1. Oracle.Chapter 5. 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.Rev0 Copyright © 2008. Installation Planner directs you through creating a plan with a series of prompting forms. Installation Planner prompts you to add servers. All rights reserved. . 100 GA. 2. Installation Copyright © 2008. Enterprise Server.Rev0 101 . All rights reserved.Chapter 5. Working with Installation Planner Specifying the Process Mode To specify the process mode: 1. Select the Process Mode tab. GA. Enter 0 or leave blank for regular plans. HTML Web Server). 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. Database Server. Enter 1 to run the JD Edwards EnterpriseOne installation automatically. On the Process Mode tab. Oracle. 2. Default mode.Chapter 5. 2. On the Default Mode tab. Default Data Source Information 102 Select whether you want the ability to modify data source information or just take the default values. Select the Default Mode tab. Working with Installation Planner Specifying the Default Mode To specify the default mode: 1. GA. . enter these values into the processing option fields: Value 0 1 2 Description Do not use default values and do not prompt.Rev0 Copyright © 2008. Oracle. Prompt for default options at run-time. All rights reserved. Always use defaults without prompting. Select whether you want the ability to generate a plan automatically from locations and machines defined in a previous version of the software. Select whether you want the ability to modify data load parameters or take the default values.Chapter 5. Copyright © 2008. All rights reserved. GA. Oracle. Select whether you want the ability to modify advanced parameters or take the default values.Rev0 103 . Select whether you want the ability to select an alternate language or take the default values. 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. Working with Installation Planner Verifying Status Change Values Have Not Changed On the Status Change tab. These values are hard coded in the application 104 GA. .Chapter 5. this tab form appears. Oracle.Rev0 Copyright © 2008. All rights reserved. Note Do not make any changes on this tab. GA. Run automatically. Oracle. Prompt to be run. 2. Working with Installation Planner Specifying Plan Completion Processes To specify plan completion processes: 1.Rev0 105 . the options on this tab specify which processes are run. Select the Completion tab.Chapter 5. All rights reserved. Copyright © 2008. one of the following values: Value 0 1 2 Description Do not run automatically. complete the fields using these values: After defining the plan. On the Completion tab. Enter the default option 2 to run automatically. Working with Installation Planner Finalize Plan Validate Plan Enter the default option 2 to run automatically. Oracle. 106 GA.Rev0 Copyright © 2008.Chapter 5. All rights reserved. . Replicate System Tables Select whether you have the option to replicate system tables automatically for remote locations. Prompt for option at run-time. complete the fields using these values: Value 0 1 2 Description Do not use and do not prompt. On the Replication tab. GA. Oracle. All rights reserved. Always use without prompting .Rev0 107 Copyright © 2008. . Working with Installation Planner Specifying Replication Options To specify replication options: 1. 2. Select the Replication tab.Chapter 5. Select whether you have the option to replicate constant tables automatically for remote locations. 108 GA. . Business data tables are Object Librarian type 210 and 211. and user defined codes automatically for remote locations. menus. Select whether you have the option to replicate master tables automatically for remote locations. Business data tables are Object Librarian type 280.Rev0 Copyright © 2008. All rights reserved. Select whether you have the option to replicate control tables. Oracle.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. Chapter 5. GA. On the Packages tab. click OK. Oracle. 2. All rights reserved. Prompt for pushing at runtime. 3.Rev0 109 . Working with Installation Planner Specifying Remote Location Package Push Options 1. Always push default packages without prompting. Copyright © 2008. Select the Packages tab. When you have chosen the options that you want. Do not prompt for pushing but display valid packages. enter one of the following values for the remote location package push option: Value 0 1 2 3 Description Do not push packages. Rev0 Copyright © 2008. Oracle. All rights reserved. Working with Installation Planner 110 GA.Chapter 5. . Verify that the Deployment Server is installed and the correct Tools Release. The Platform Pack installation must be completed and you should verify that it completely installed the Pristine database and loaded the Pristine Central Objects. All rights reserved. Oracle. On the Deployment Server. and Planner Update have been installed. 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. None.Rev0 111 . Concurrent Tasks Copyright © 2008. log on to Release 9.0 as user JDE in the JDEPLAN environment. in that order.Chapter 5. Tools Release Patch. GA. Personnel Logon Status Prerequisites Installer. Enter a Plan description.Rev0 Copyright © 2008. The Installation Planner form appears. Access the System Installation Tools Menu (GH961). click Add. 4. On Work with Installation Plans. Oracle.Chapter 5. All rights reserved. 3. 112 GA. . On the System Installation Tools menu. 2. double-click Typical Installation Plan. Working with Installation Planner Starting Installation Planner To start Installation Planner from within JD Edwards EnterpriseOne: 1. Chapter 5. Oracle. Working with Installation Planner Entering a Plan Description To enter a plan description: 1. Copyright © 2008. 2. complete these fields: Name Description Status Install Type To Release Enter the name of the installation plan. All rights reserved. Enter the description of the installation plan.Rev0 113 . Click OK to continue. Verify that the release number is E900 (default value). GA. On Installation Planner. Choose 10 (the default value) as the status of the installation plan. Click the Install (the default value) radio button. or a division of the company. If you are editing an existing base location. If this is the base location. . Enter a description for this location. If you are editing an existing base location. To enter location information: 1. Oracle. On Location Revisions. If this is the base location. All rights reserved. the location can be a city. Parent Location 2. 114 GA. the field is unavailable.Rev0 Copyright © 2008.Chapter 5. Working with Installation Planner Entering Location Information A location groups related Deployment Servers for use in a multi-tier environment. the field is unavailable. this field is only available when you are adding the base location. complete these fields: Location Description Location Code Enter the location to which this plan applies. company headquarters. Click OK. this field is only available when you are adding the base location. All rights reserved. indicating that the server type is Intel NT. This description should include the location with which this Deployment Server is associated and whether or not it is the primary server. GA. Enter a long description for the machine. Working with Installation Planner Entering Deployment Server Information While Release 9. The value 50 appears by default. only the primary Deployment Server is defined at this time.INI. The user to whom an email is sent when a package is deployed. On Deployment Server Revisions. The default value for primary user is listed in the JDE. Valid values are: 1. The default value is E900. Release Host Type Location Primary User 2.0 release number you are installing or use the visual assist button to choose one from the list. The name of the Deployment Server appears by default. complete or verify these fields: Machine Usage Machine Name Description The value 15 appears by default.0 enables more than one Deployment Server to be defined. To enter Deployment Server information: 1. indicating that this is a Deployment Server. complete these fields: Primary Deployment Server The hierarchy of the servers. You can choose a primary Deployment Server from the list of existing servers or you can enter information for a new server. Enter the Release 9. Your current location is the default value.Rev0 115 . Oracle.Primary Deployment Server (default value) Copyright © 2008.Chapter 5. On the Deployment tab. 3. To continue with Installation Planner setup. 4. To add another Deployment Server. Working with Installation Planner 0 . . such as Workstation. 116 GA.0 is \E900. All rights reserved. click Yes and repeat steps 1 through 3. Tip If you enter invalid information into a field on a tab. 5. Oracle. Click OK.Rev0 Copyright © 2008. click No. Verify that the server share name for Release 9. Click the stop sign icon in the bottom right of the form to see more info about the error.0 on your Deployment Server.Chapter 5. a stop sign symbol appears next to the tab name.Secondary Deployment Server The server share name of the directory to which you installed Release 9. an Enterprise Server running two different versions of software must use two different port numbers. The default value for primary user is listed in the JDE. Copyright © 2008. The default value is E900.INI. In this case. On Enterprise Server Revisions. or use the visual assist button to choose one from the list. Click the visual assist button and select the type of Enterprise Server you are adding to the plan. To enter Enterprise Server information: 1. The location chosen for this plan appears by default.Chapter 5. All rights reserved. Intel NT. verify or complete these fields: Machine Name Description Release Host Type Location Primary User The name of the primary Enterprise Server. Enter the release number to which this plan applies. Oracle.Rev0 117 . Enter a description for the machine. a port number must be defined. GA. Note The case of machine name must also match the network ID for that machine. While Enterprise Servers running the same release can use the same port number. The user to whom an email is sent when a package is deployed. Working with Installation Planner Entering Enterprise Server Information Note During the definition of the Enterprise Server. SQL Server ODBC Whenever you enter a host type.Rev0 Copyright © 2008. see Release 9. For additional considerations.0 on the Enterprise Server. A Deployment Server name appears in this field by default. 3. Oracle.INI. Click OK.900 Server Map where machinename is the name of your machine.INI. Working with Installation Planner Caution If you are using clustering. not one of the servers' machine names. On Enterprise Server Revisions. use the name of the SQL server database network as the machine name when installing Release 9. The Installation Planner detects and provides a default value based on the current machine name on which the program is running. 2. All rights reserved.Chapter 5. Make sure the value is specific to your version of the release. .0 the path ends with \E900\ddp. you must also change this setting in both the Enterprise Server and client JDE. choose the name of the Deployment Server to which this Enterprise Server is attached. For example. for Release 9. Installation Path Caution You must change the value that defaults into the Installation Path field as shown in the screen capture above.0 on a Cluster in JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide and the clustering vendor's software documentation. but it can be changed if necessary. the Installation Planner populates this field with a default value: machinename . Verify that the default value is the installation directory path to which you want to install Release 9. Enter the value for your database: S . 118 GA. Using the visual assist button. and complete or verify these fields: Port Number Logical Machine Name Database Type Server Map Data Source The port number value (6015) for this Enterprise Server as supplied from the JDE.0. select the Enterprise tab. Deployment Server Name Note If you change the port number to a value other than 6015. 1. Working with Installation Planner Entering HTML Web Server Information Note For Release 9. On the HTML Application Server dialog. Oracle. All rights reserved.Rev0 119 . Copyright © 2008. However. 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. click OK to continue entering HTML Web Server information.Chapter 5.0. these terms are all synonymous. 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. this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software. GA. or click Select to select an existing HTML Web Server. The location chosen for this plan appears in this field by default. All rights reserved. Enter a description of the HTML Web Server machine. For example: www.INI. Select the correct server type. . For HTTP. Oracle. The user to whom an email is sent when a package is deployed.oracle. the typical port number is 80. On the HTML tab.Rev0 Copyright © 2008.com This is the port number the HTML Web Server is listening to. On HTML Server Revisions. This is the Domain Name System (DNS) host name of the HTML Web Server. Protocol Server URL HTTP Port 120 GA. Enter E900 to indicate the release number that you are installing.Chapter 5. The default for primary user is listed in the JDE. The default value of 50 specifies the server type as Intel NT. This is the protocol used by the HTML Web Server. Working with Installation Planner 2. Valid values are http or https. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). Enter the name of your HTML Web Server. 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. the web shortcut generated points to the "Primary" HTML Web Server. complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form. The name is case sensitive and must not exceed 10 characters. 3. Oracle.and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. All rights reserved. Defines how shortcuts to a web form are generated by the system code. Enter the installation directory path to which you are installing Release 9. the value is 6015. or its administrator.0 on Oracle Applications Servers. Note You can choose to implement a HTML Web Server using a different port number. the path ends with E1HTMLServer.Chapter 5. You should not use it unless you have a direct need. and redirector will point to a servlet on another HTML Web Server for load balancing. Click OK. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. Values are either a reserved value or an explicit servlet name. the redirector functionality cannot be used. Make sure this is specific to your version of the release. The servlet name to use is generated by the system. JDENET Listen Port Default Login Explicit Servlet Name Installation Path Usage of Explicit servlet name is for backward compatibility only. The URL generated will point to the specified servlet in the Primary HTML Web Server. The value is dependent on the release of JD Edwards EnterpriseOne. For Release 9. you must obtain this value from the HTML Web Server machine itself. Otherwise. For JD Edwards EnterpriseOne Release 9.Rev0 121 . the typical port number is 443. 5. In this case. Redirector The URL generated will point to redirector in the Primary HTML Web Server. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. click Yes and repeat steps 1 through 4 to define another HTML Web Server.0. GA. Working with Installation Planner For HTTPS. and also the platform and application server on which your HTML Web Server is running. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths. To add another HTML Web Server. refer to the applicable platform. 4. The user can specify an explicit servlet name in this field. Copyright © 2008.0 on your HTML Web Server. Default Environments Default Data Load Select OK. All rights reserved.Chapter 5. On Environment Selection. ensure that these radio buttons are selected: • • 2. 122 GA. Oracle. Working with Installation Planner Selecting Default Environments To select default environments: 1. .Rev0 Copyright © 2008. Copyright © 2008. GA. These tables are updated: • • • • • Release Master table (F00945). If the processing option default was not selected. click Validate on the tree view of your plan to initiate the Planner Validation Report. Planner Validation Report automatically prompts you to run this report. To finalize the Installation Plan: 1.Rev0 123 . Working with Installation Planner Finalizing the Installation Plan When the plan is finalized: • • • The status is set to 20.INI. On the message box that indicates Installation Planner has concluded. if you are installing a language. Package Plan table (F98404). The system creates the OCM mappings and the JDE.Chapter 5. Path Code Master table (F00942). Oracle. click OK to exit the message box and initiate the Planner Validation Report. Machine Detail table (F9651). Language table (F984031). • • If the processing option default was selected. All rights reserved. signaling that several adjustments to OCM mappings and tables are made according to your plan. All rights reserved. On Report Output Destination. 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 124 GA. select On Screen or To Printer. . Click OK. 4. Oracle. 3.Chapter 5. Working with Installation Planner Concluding the Planner Validation Report To conclude the planner validation report: 1. Review the report to confirm that all records were validated. click Expand to review the plan you created. 2.Rev0 Copyright © 2008. On Work With Installation Plans. refer to Working with Reports. For more information about Installation Planner Validation Report (R9840B). Chapter 5. GA. 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.Rev0 125 . All rights reserved. 0 data sources as completely as possible. . Working with Installation Planner Understanding a Custom Installation Plan Note After installing the Deployment Server. such as database type and Enterprise Server type. you must define and run the installation plan. JD Edwards EnterpriseOne configures your Release 9.Rev0 Copyright © 2008. All rights reserved. you might need to modify some data source information to reflect your system-specific configuration. Oracle. Data Source Considerations. the information you provide on the Installation Planner forms. The Installation Planner processing options also determine which choices are available while setting up your plan. You must either define and run a Typical or a Custom Installation Plan -. 126 GA.Chapter 5. refer to Reviewing Installation Planner Processing Options . However. Within a custom installation plan. determines the information displayed on the remaining forms. when you run Installation Planner.do not do both. For a complete description of the processing options. The Installation Planner form appears. double-click Custom Installation Plan. Access the System Installation Tools Menu (GH961). 4. GA.Rev0 127 .Chapter 5. On Work with Installation Plans. On the System Installation Tools menu. Copyright © 2008. 3. All rights reserved. Enter a Plan description. Oracle. 2. click Add. Working with Installation Planner Starting Installation Planner To start Installation Planner from within JD Edwards EnterpriseOne: 1. On Installation Planner. Choose 10 (the default value). .Rev0 Copyright © 2008. Verify that the release number is E900 (the default value). 3. Click OK. Select yes if you are installing an alternate language. To do so.Chapter 5. This is an optional selection that is only available if you have previously specified this Custom plan to install languages. Click the Install (the default value) radio button. choose one of the following options: 128 GA. refer to Creating a Language-Only Installation Plan. All rights reserved. you can install an alternate language after you complete your master plan. Enter the description of the plan. Working with Installation Planner Entering a Plan Description To enter a plan description: 1. Oracle. Note If you prefer. select the Language Only option on this form. complete the following fields: Name Description Status Install Type To Release Include Languages Enter the name of the plan. For more information. 2. On Plan Generation. Enterprise Servers. Skip the sections on entering locations. Caution In order to ensure the validity of all subsequent plan information. All rights reserved. which is preferable because the recommended method is to step through the planner rather than taking defaults. it is strongly recommended that even advanced users should not choose this Take Defaults option. • To exit the plan.Chapter 5. Oracle. GA. See Caution below. and continue with Entering Shared Data Source Information. you should step through plan and verify that the Planner is populating information exactly as you expect to match your requirements. click Take Defaults. On this form. Working with Installation Planner Note The above screen may not always appear if you are rerunning the Planner.Rev0 129 . click Cancel. The machines that were imported from the previous system data source are entered into the current plan. you have the option to automatically enter the locations and machines into the plan that you defined in the previous version of the software. Copyright © 2008. click OK and continue with Entering Location Information. and machines/servers. • 4. To enable the system to automatically enter the locations and machines from the previous version. Deployment Servers. Instead. Choose a method for generating your plan: • • To manually create your plan. . All rights reserved. 2. Working with Installation Planner Entering Location Information A location groups related Deployment Servers for use in a multi-tier environment. If this is the base location.Rev0 Copyright © 2008. complete these fields: Location Description Location Code Parent Location Enter the location to which this plan applies. On Location Revisions. this field will be grayed out. 130 GA. company headquarters.Chapter 5. this field will be grayed out. Click OK. Oracle. Enter a description for this location. the location can be a city. To enter location information: 1. or a division of the company. For the base location. On Deployment Server Revisions. Enter the release number you are installing or use the visual assist button to choose one from the list. Displays the current location. only the primary Deployment Server is defined at this time. complete or verify these fields: Machine Usage Machine Name Description Displays the value 15 by default to indicate that this is a Deployment Server. Click OK to add a Deployment Server. The default value for primary user is JDE. To enter Deployment Server information: 1. On the Deployment tab. All rights reserved.0 enables more than one Deployment Server to be defined. complete these fields: Primary DeployEnter the hierarchy of the servers. Displays the value 50 appears by default. Displays the user to whom an email is sent when a package is deployed. You can choose a primary Deployment Server from the list of existing servers or you can enter information for a new server. Oracle. This description should include the location with which this Deployment Server is associated and whether or not it is the primary server. 2. The default value is E900. indicating that the server type is Intel NT. The name of the Deployment Server appears by default.Chapter 5. Enter a long description for the machine. Release Host Type Location Primary User 3. . Values are: GA.Rev0 131 Copyright © 2008. Working with Installation Planner Entering Deployment Server Information While Release 9. 4. Click OK. a stop sign symbol appears next to the tab name. 132 GA. click No. Working with Installation Planner ment Server 1.Primary Deployment Server (default value) 0 .0 on your Deployment Server. For more information about the error. Verify that the server share name for Release 9. .Rev0 Copyright © 2008. 5. click the stop sign icon in the bottom right-hand corner of the form.Secondary Deployment Server The server share name of the directory to which you installed Release 9. 6.0 is \E900.Chapter 5. All rights reserved. Tip If you enter invalid information into a tab field. such as Deployment Server. To continue with Installation Planner setup. Oracle. click Yes and repeat steps 1 through 3. To add another Deployment Server. or use the visual assist button to choose one from the list. Enter a description for the machine. Oracle. Click the visual assist button and choose the type of Enterprise Server you are adding to the plan.Chapter 5. a port number must be defined. Note The case of machine name must also match the network ID for that machine. On Enterprise Server Revisions. All rights reserved. The default value is E900. While Enterprise Servers running the same release can use the same port number. In this case. Working with Installation Planner Entering Enterprise Server Information Note During the definition of the Enterprise Server. Copyright © 2008. Intel NT. Enter the release number to which this plan applies. verify or complete these fields: Machine Name Description Release Host Type Location Primary User The name of your primary Enterprise Server. GA. The location chosen for this plan appears by default. an Enterprise Server running two different versions of software must use two different port numbers. The user to whom an email is sent when a package is deployed. The default value for primary user is JDE. To enter Enterprise Server information: 1.Rev0 133 . All rights reserved. .0 on a Cluster in the JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide and the clustering software documentation. 134 GA.0. Indicates the status of the server. select the Enterprise tab. use the name of the SQL server database network as the machine name when installing Release 9. Installation Path Caution You must change the value that defaults into the Installation Path field as shown in the screen capture above. 3.900 Server Map where machinename is the name of your machine.0 the path ends with \E900\ddp.0 on your Enterprise Server. Verify that the default value is the installation directory path to which you want to install Release 9. For example. you must also change this setting in both the Enterprise Server and workstation JDE. and complete or verify these fields: Port Number Logical Machine Name Database Type Server Map Data Source The port number value (6015) for this Enterprise Server appears by default from the JDE. Oracle. Continuing on Enterprise Server Revisions.Chapter 5. refer to Release 9. Deployment Server Name Server Status Note If you change the port number to a value other than 6015. The Installation Planner detects and provides a default value based on the current machine name on which the program is running. 2. Using the visual assist button. A Deployment Server name appears in this field by default. but it can be changed if necessary.INI.INI. Working with Installation Planner Caution If you are using clustering. the Installation Planner populates this field with a default value: machinename . Click OK.Rev0 Copyright © 2008. For additional considerations. Enter the value for your database: S . for Release 9. Make sure the value is specific to your version of the release.SQL Server ODBC Whenever you enter a host type. not one of the servers' machine names. choose the name of the Deployment Server to which this Enterprise Server is attached. Rev0 135 . or click Take Defaults to select the default data. If you select the default data. 3. Click OK. Copyright © 2008. verify the accuracy of the Server Map data source. Working with Installation Planner Enter Data Source Information for Server Map To enter information for the Server Map data source: 1. Oracle. On Data Source Revisions. 2. you can skip to Entering HTML Web Server Information.Chapter 5. All rights reserved. On Data Source. click OK to continue entering unique data source information. GA. On HTML Application Server. 136 GA. 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. these terms are all synonymous. or click Select to choose from a list of existing HTML Servers.0. click OK to define a new HTML Server. To enter HTML Web Server information: 1. this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software.Rev0 Copyright © 2008. Oracle. . All rights reserved. However. Working with Installation Planner Entering HTML Web Server Information Note For Release 9. 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.Chapter 5. Functionally. you are presented with the Machine Search table.Rev0 137 . All rights reserved. Working with Installation Planner If you choose Select. GA. Oracle. Copyright © 2008.Chapter 5. from which you can make your selection. 4. the web shortcut generated points to the "Primary" HTML Web Server.Chapter 5.oracle. The default value of 50 specifies the server type as Intel NT. Enter E900 to indicate the release number that you are installing. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). Oracle. 3.com. This is the port number the HTML Web Server is listening to. All rights reserved. The location chosen for this plan appears in this field by default. Enter a description of the HTML Web Server machine. This is the protocol used by the HTML Web Server. 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. On HTML Server Revisions. . For example: www. On the HTML Application Server dialog. Valid values are http or https. The user to whom an email is sent when a package is deployed.Rev0 Copyright © 2008.INI. On the HTML tab. Protocol Server URL HTTP Port 138 GA. This is the Domain Name System (DNS) host name of the HTML Web Server. Working with Installation Planner 2. click OK to continue entering HTML Web Server information. The name is case sensitive and must not exceed 10 characters. Enter the name of your HTML Web Server. or click Select to select an existing HTML Web Server. complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form. Select the correct server type. The default for primary user is listed in the JDE. 0 on Oracle Applications Servers. Oracle. Explicit The user can specify an explicit servlet name in this field. 6. However. In this Servlet case. Otherwise. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. the value is 6015.0 on your HTML Web Server.Rev0 139 . Click OK. Defines how shortcuts to a web form are generated by the system code. the path ends with E1HTMLServer. you can choose to implement a HTML Web Server using a different port number. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths. you must obtain this value from the HTML Web Server machine itself. Enter the installation directory path to which you are installing Release 9. 5. Redirector The URL generated will point to redirector in the Primary HTML Web Server. or its administrator. the typical port number is 443.and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. click Yes and repeat steps 1 through 4 to define another HTML Web Server. and also the platform and application server on which your HTML Web Server is running. For JD Edwards EnterpriseOne Release 9. To add another HTML Web Server. Working with Installation Planner For HTTP.0. refer to the applicable platform. Make sure this is specific to your version of the release. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. For Release 9. JDENET Listen Port Default Login Installation Path Copyright © 2008.Chapter 5. the redirector functionality cannot be used. You should not use it unless you have a direct need. The value is dependent on the release of JD Edwards EnterpriseOne. For HTTPS. Usage of Explicit servlet name is for backward compatibility only. GA. and redirector will point to a servlet on another HTML Web Server for load balancing. Values are either a reserved value or an explicit servlet name. All rights reserved. the typical port number is 80. The servlet name to use is generated by the system. choose one of these options: • OK If your database resides on a separate server. . choose click OK to continue entering unique Data Server information. On Data Server. • Skip Click this option if you do not want to define a Data Server. All rights reserved. • Select Click this option to select an existing Data Server. Oracle. Continue with the Planner using the environment selection in step 6 of this task. 140 GA.Rev0 Copyright © 2008. Working with Installation Planner Entering Data Server Information 1.Chapter 5. Rev0 141 . The name must not exceed 10 characters. E900. Values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client . Enter the name of your Database Server. On the Data tab. Enter a description of the Database Server machine. GA. for example. The user to whom an email is sent once a package is deployed. On Data Server Revisions.Microsoft Windows The Installation Planner populates this field by default. The default for primary user is JDE. Enter the release number you are installing.Chapter 5. For example: • S . Location Primary User 3. complete these fields: Machine Usage Machine Name Description Release Host Type The default value of 25 indicates that this is a Database Server. Select the type of Database Server that you are adding to the plan. All rights reserved.SQL Server ODBC Copyright © 2008. Working with Installation Planner 2. based on previous selections. Oracle. complete the following field: Data Source Type Choose the type of data source.Microsoft Windows 90 Client . All rights reserved. or click Take Defaults to select the default data for the shared data sources.0 data sources.Rev0 Copyright © 2008. To add another Data Server. click Yes and repeat steps 1 through 4 to define another Data Server. 5. Oracle. . select Yes to add another location. or click No to continue with Installation Planner. On Data Source. See Also For more information about System data source fields or fields for other data sources mentioned in this process.Chapter 5. Working with Installation Planner 4. refer to Understanding Data Source Charts. On Location. or click OK to specifically enter the data source information. click OK to continue entering unique shared data source information. Note For Release 9. Installation Planner populates this field with the name (and optionally the instance) of the machine on which the SQL Server database is running.0 all ODBC database connections should use the default value for the ODBC Data Source Name field. 7. click Take Defaults. Click OK. 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 9. 6. This sections discusses: • • • Verifying the Data Source for Data Dictionary Verifying the Object Librarian Data Source Verifying the System Data Source 142 GA. On Data Source Revisions. GA. Oracle. Click OK. All rights reserved. 2. verify the accuracy of the settings for the Data Dictionary data source.Chapter 5. Copyright © 2008. Working with Installation Planner Verifying the Data Source for Data Dictionary To verify the data source for Data Dictionary: 1.Rev0 143 . On Data Source Revisions. Click OK. Oracle.Chapter 5. 144 GA. Working with Installation Planner Verifying the Object Librarian Data Source To verify the Object Librarian data source: 1. . 2.Rev0 Copyright © 2008. verify the accuracy of the settings for the Object Librarian data source. All rights reserved. GA. All rights reserved. Copyright © 2008. 2. Working with Installation Planner Verifying the System Data Source To verify the System data source: 1. The Environment Selection screen appears. Click OK.Chapter 5. On Data Source Revisions. Oracle.Rev0 145 . verify the accuracy of the settings for the System data source. Installation Planner displays a customization form for each parameter that you clear. Installation Planner configures your system using values for typical environments.Chapter 5.Rev0 Copyright © 2008. Depending on the options chosen when you set up your plan. Oracle. 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. Release 9. All rights reserved. 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. 146 GA.0 displays one or more of the following parameters. Note If you selected the default option.Chapter 5.Rev0 147 . GA. 2. Oracle. Working with Installation Planner Setting Up Environments To set up environments: 1. Copyright © 2008. Skip the tasks for those parameters that you did not clear. which is to include all parameters. 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. All rights reserved. On Environment Selection. skip to Working with Environment Data Sources . Click OK. 7. 5. or create a pathcode. 4. Choose share.Chapter 5. Click Next. 148 GA. Enter the environment information on the screen. All rights reserved.Rev0 Copyright © 2008. Working with Installation Planner Adding a Custom Environment To add a custom environment: 1. 3. Click Add to add a new environment. 2. . Click Next. Click Next. Oracle. 6. or click Copy to copy the settings of an existing environment. Enter pathcode information on the screen. To set up multiple environments.Chapter 5. All rights reserved. select and define them one at a time. Working with Installation Planner Selecting an Environment To select an environment: 1.Rev0 149 . GA. Oracle. On Select Environments. double-click the environment that you want to define. Note J xxxxxx environments are required for the HTML Web Server. Copyright © 2008. refer to Loading Data (Demo Data and Production Data). . Oracle. the Data Load Parameters form appears.Rev0 Copyright © 2008. Working with Installation Planner Specifying Environment Data Load Parameters If you turned off Default Data Load on the Environment Selection form. Note The data load radio buttons on this form are no longer applicable as of JD Edwards EnterpriseOne Release 9. For additional details.Chapter 5. All rights reserved. 150 GA.0 because data is automatically loaded by the Platform Pack Installer. Rev0 151 . Click OK. click Select. 2. select the language you want to set up for the environment. Oracle. 3. GA. All rights reserved. From the Row menu. Copyright © 2008. On Language Selection. 4.Chapter 5. Repeat the above steps until all your languages have been selected. Working with Installation Planner Selecting Languages To select languages: 1. Rev0 Copyright © 2008. See Also To modify this template. or click Take Defaults to accept the Release 9. Selecting an Environment Data Source Setup Option Installer Planner prompts you to set up data sources for the environment you just configured. All rights reserved. you must set up the data sources for those environments. refer to the JD Edwards EnterpriseOne Tools 8. If you created a custom environment. 152 GA. Oracle. data source information is generated from the data source template provided by JD Edwards EnterpriseOne.9 Configurable Network Computing Implementation Guide. . 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.Chapter 5. Click OK to manually enter the data sources and continue with the following task.0 default data sources. To select an environment data source setup option: 1. Oracle.Rev0 153 . Click OK. verify the data source for your Business Data.Chapter 5. 3. 2. GA. Working with Installation Planner Setting Up the Data Source for Business Data To set up the data source for business data: 1. All rights reserved. Copyright © 2008. click Advanced. From the Form menu. On Data Source Revisions. Chapter 5. On Data Source Revisions. verify the information for your central objects data source. All rights reserved. click the Advanced form option. 3. On Data Source Revisions.Rev0 Copyright © 2008. Working with Installation Planner Setting Up the Data Source for Central Objects To set up the data source for central objects: 1. Oracle. 154 GA. . Click OK. 2. All rights reserved. Copyright © 2008. Working with Installation Planner 4.Chapter 5.Rev0 155 . On Advanced Set-Up. verify Unicode is checked. Oracle. because the central objects data source must be Unicode. GA. verify the accuracy of the Control Tables data source. Verify the name of the Enterprise Server. All rights reserved.Chapter 5. Data Source Name Server Name Object Owner ID Verify the name of the data source. 156 GA. Enter the name of the owner of this object Note Control tables data sources are specific to the environment and pathcode. Click OK. 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. Oracle. 2.Rev0 Copyright © 2008. Rev0 157 . verify the accuracy of the data dictionary data source. On Data Source Revisions. Click OK. 2. All rights reserved. Oracle. GA.Chapter 5. Copyright © 2008. Working with Installation Planner Verifying the Data Dictionary Data Source To verify the data dictionary data source: 1. Working with Installation Planner Verifying the Data Source for Versions To verify the data source for versions: 1.Chapter 5. 158 GA.Rev0 Copyright © 2008. Note Versions data sources are specific to the pathcode. and the Unicode flag on the Advanced form must be selected. Click OK. verify the accuracy of the versions data source. 2. On Data Source Revisions. All rights reserved. Oracle. . Continue with Finalizing the Installation Plan task. Oracle. Copyright © 2008. Repeat all processes for adding a location starting with Entering Location Information. All rights reserved. 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.Chapter 5. • 2. Refer to the Creating a Remote Installation Plan task in the Installation Planner Utilities section for information about adding remote locations to your plan. Click No to conclude the Installation Plan setup. GA.Rev0 159 . Package Plan table (F98404).INI is modified. The OCM is created. if you are installing an alternate language. All rights reserved.Rev0 Copyright © 2008. Machine Detail table (F9651). The following tables are upgraded: • • • • • Release Master table (F00945). the Planner Validation Report automatically prompts you to run this report. 160 GA.Chapter 5. which signals that several adjustments to tables were made according to your plan. . To finish the Installation Plan: 1. Path Code Master table (F00942). Language table (F984031). Working with Installation Planner Finalizing the Installation Plan Installation Planner displays a message to let you know that the installation plan has been finalized. Click OK to exit the concluding message box and initiate the Planner Validation Report. Oracle. click Validate on the tree view of your plan to initiate the Planner Validation Report. The JDE. • • If you selected the processing option default. If you did not select the processing option default. When the plan is finalized: • • • • The status is set to 20. 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. select On Screen or To Printer. 4. click Close. On Report Output Destination. All rights reserved. On Work with Installation Plans. Working with Installation Planner Concluding the Validation Planner Report To conclude the validation planner report: 1. Review the report to confirm that all records were validated. and click OK. For more information about Installation Planner Validation Report (R9840B). 3. After reviewing the report on the Batch Versions form. 2. GA.Chapter 5. refer to Working with Reports.Rev0 161 . Oracle. click Expand to review the plan you created. or servers appears for the base location in the tree view. 5.0 planner environment. 6. click Find. All rights reserved. Click Delete. .Chapter 5. 2. or server that you want to delete. To close the application. In the Release 9. and associated records. machine. machines. Working with Installation Planner Deleting Machines from an Installation Plan As you work through the Installation Planner application. Oracle.Rev0 Copyright © 2008. Expand the location. You can use Installation Planner to delete machines as needed. 4. however. 3. Select the location. shared Enterprise Servers and Deployment Servers. A list of your locations. you might find that you need to delete a server or machine that you have created. click Close. On Work With Locations and Machines. To delete machines from an installation plan: 1. enter P9654A in the Fast Path field and press Enter. doing so can affect related databases. 162 GA. 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 Copyright © 2008. Oracle. GA.Rev0 163 . All rights reserved. Copies the F9650 and F9651 tables from the Planner data source to the System . 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. You can set task breaks before or after any specific workbench to stop the process at any point. It then updates the F98403 table to indicate completion. All rights reserved. some or all of which might be used for your installation. from your Planner data source to your System 900 data source. data sources.Rev0 Copyright © 2008. and server map tables are created. Depending on the plan settings. It also updates the F98401 table to indicate completion. Transfers the F9603 and F9631 tables from the Planner data source to the System . depending on your installation plan: Installation Workbench Compon. In unattended mode (the default value). It then updates the F98404 table to indicate completion.900 data source. Copies the language text from the SSE database that contains the language text into the control table database and central object database.900 data source. Copies the F0094. This workbench runs only for users who are adding an alternate language to their installations.900 data source. Working With Installation Workbench Understanding Workbench Components After planning the Release 9.0 installation using Installation Planner. 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. Oracle. F00941. The logic of this program runs specific workbench programs according to the plan you created. it also runs a batch application to copy new generic text and to create and populate Object Management Workbench and version tables.900 data source. Installation Workbench includes the components.Chapter 6. and F00942 tables. Only valid environments. Location Workbench Data Source Workbench Environment Workbench Machine Workbench Control Table Workbench Package Workbench 164 GA. this workbench runs Release Master after Installation Workbench is started and before Location Workbench begins. Installation Workbench can be run in attended mode or unattended mode. If using unattended mode. 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 . In attended mode. each workbench runs without user intervention. you must check that each task ran successfully. you should run the plan using Installation Workbench. as well as the F986101 table for each environment. you start each workbench after the previous workbench completes.Functional Description ent Initial Tasks Workbench When using unattended workbench mode. Copies all data sources that are defined in the plan from the F98611 and F986115 tables in the Planner data source to your System . . 4. On the Deployment Server. Use this procedure to ensure that the share is writeable before proceeding: 1. All rights reserved.Rev0 165 . navigate to Start | My Computer | Manage Open Shared Folders. you will still need these settings on the Deployment Server's share in order to successfully perform client installs. Copyright © 2008. Open Shares. Sometimes the security settings on your deployment server will prevent the Planner from creating the share as a writeable share. 3. Note Even after the Workbenches are complete. Verifying the Network Share on the Deployment Server When you created the plan. this network share was created: \\depsvrname\E900 where depsvrname is the name of your Deployment Server. GA. 2. Change. Read permissions. Select properties then select Share Permissions Make sure that Everyone is set to Full Control. Right click on E900 and select Properties and then Share Permissions. these workbenches will fail if the share is not writeable. Because several of the Workbenches update files through the network share. 5. Working With Installation Workbench See Also Major Technical Tables in this guide for more information about individual tables and their uses. 6. Oracle.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. To load demo data in Production or Prototype environments. Note The "from" (source) environment can be the Planner environment or your Pristine environment. 1. .Chapter 6. Caution You should not change the record selection on this UBE. Production data to Production and Prototype environments. you must run a UBE (R98403E) to copy the data to those environments. Oracle. for Release 9. Run R98403E using the XJDE0009 version and set the processing options as follows: 166 GA.Rev0 Copyright © 2008.0 the Platform Pack Installer loads appropriate data into specific environments as follows: • • Demo data to Development and Pristine environments. All rights reserved. which is the environment of the table to be copied.Chapter 6. Oracle. JDEPLAN. On Processing Options 1-4. not data sources. complete these fields: Option 1 Option 2 Option 3 Enter the name of the source environment. which is the environment to which you wish to copy the table. PD900. not data sources. Working With Installation Workbench 2. 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. 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. In this case. For example. GA. you would specify either the Production or Prototype environments.Rev0 167 . Enter the name of the target environment. All rights reserved. Option 4 Copyright © 2008. For example. On Processing Options 5-9.Rev0 Copyright © 2008. Option 6 168 GA.Chapter 6. complete these fields: Option 5 The recommended value is 1. Working With Installation Workbench 3. The default value is 0. which copies the table. Click OK to continue specifying processing options. 4. . Proof Mode. Enter Y to copy tables whether or not they exist in the source data source. The recommended value is N. All rights reserved. Oracle. which copies tables only if they exist in the source. you will end up with a mixture of production and demo data in the tables. All rights reserved. Note If you do not recreate the tables. That is. The default value is N. Option 9 Note A value of Y copies the data and then create the indexes. Working With Installation Workbench Option 7 The default value is N. 5. The recommended value is Y. Copyright © 2008. which forces a copy of the data.Chapter 6. The default value is N. The default value is N. a production data load. ignoring the CPYD flag. The recommended value is N. Option 8 Note A value of Y will leave almost all tables empty. which creates the indexes on the tables before copying the data. which recreates tables that already exist in the target data source. Click OK to accept the values and start the UBE. Oracle.Rev0 169 . The recommended value is N. This prevents duplicate rows. GA. If you receive a Network Failed error. All rights reserved. Note If running an Install. To create the job queue: 1. Click Add. Initial Tasks Workbench will create a default entry for QBATCH with a setting of maximum=4.Chapter 6. 2. On Job Queue Revisions.Rev0 Copyright © 2008. Enter 6015. Working With Installation Workbench Creating the Job Queue You may set up the job queues before running the Installation Workbench. . Enter GH9013 in the Fast Path field and start the Job Queues program (P986130). Enter 01. Enter a value that equals the number of processors on the Enterprise Server machine. Enter 01. you can safely ignore it in this 170 GA. If you set up queues after the Installation Workbench. Enter the job queue name. Turn on this option by clicking the check box. If you do not. 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. you can set up the queues at any stage before running a Package Build. 3. sign onto DEP900. Oracle. Enter 01. All rights reserved. Copyright © 2008. Oracle.Chapter 6. Enter a value that equals the number of processors on the Enterprise Server machine. On Job Queue Revisions. Enter 01. 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. Add another queue called I-ACTIVE. 4. GA.Rev0 171 . 5. Turn off this option by clicking the radio button. Working With Installation Workbench case. Enter 6015. Oracle.Chapter 6. Select Prompt For and then Values. Click OK. The default value is 1 (unattended). An automatic task break occurs after Control Table Workbench. Double-click Work with Task Breaks. Open the System Installation Tools menu (GH961). 4. enter 1 for unattended workbench mode or 0 (zero) for attended workbench mode. In unattended workbench. The Processing Options form appears. 172 GA. You can use the task break to verify successful completion of a workbench or for other tasks. The Work with Task Breaks form appears. To choose attended workbench mode: 1. When running Workbench in unattended mode. set a task break after Table Conversion Workbench to verify that all table conversions completed successfully. In the appropriate field. To set a task break in unattended workbench mode: 1. Select Advanced Operations. 5. Unattended workbench is the default value. the process stops. 3. preceding Table Conversion Workbench. start Installation Workbench as described below. For example. if an error is encountered in any of the individual workbenches. Setting a Task Break in Unattended Workbench Mode In unattended workbench. Work with Installation Plan appears. . 3. All rights reserved.Rev0 Copyright © 2008. 2. unattended workbench resumes where it left off. you can set task breaks before or after any of the individual workbenches. Open the System Installation Tools menu (GH961). and then the status of each workbench is displayed as the workbench begins. 2. 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). After fixing the error. Right-click on Installation Workbench. on the Row menu. If the field is left blank. 5. 6. then no task break is configured. Copyright © 2008. Click OK. Oracle. 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. To set a break before or after a workbench. and Work with Task Breaks reappears. Enter detailed information about the task break. Click Find. Click Close.Rev0 173 . Specify any further task breaks. All rights reserved. Task Break Revisions closes. select Break Before or Break After. You can clear task breaks on the Row menu. On Task Break Revisions.Chapter 6. and. Enter a short text description of the task break. Specify (blank) for no task break or 2 for a customer task break. GA. Working With Installation Workbench 4. choose the workbench name. A list of the workbenches appears. 8. 7. Working With Installation Workbench Starting Installation Workbench Caution Do not lock the Deployment Server during Installation Workbench processes (for example.Chapter 6. the system downloads all required objects using Just In Time Installation (JITI). Oracle. 3. Do not run Installation Workbench from a remote access program that simulates a local connection. 174 GA. From the System Installation Tools menu (GH961). When this application is run the first time. log in to the Planner environment. If you did not set any task breaks. On your Deployment Server. On Work with Installation Plan. • • If you specified attended workbench mode.Rev0 Copyright © 2008. unless task breaks are set. If you specified unattended workbench mode. 2. including the Initial Tasks Workbench. continue with Working With the Enterprise Server. with a screen saver password). the process begins and all workbenches are completed automatically. To start the Installation Workbench: 1. which is JDEPLAN. All rights reserved. . choose Installation Workbench. use the following procedures. doing so pauses some processes. double-click your plan. to complete the workbenches. Rev0 175 . You use this procedure if you are running Workbench in attended mode or if you set a task break before Initial Tasks Workbench. use the following procedure. All rights reserved. To change the status of Initial Tasks Workbench: You might want to change the status of one or more of the initial workbench tasks. after you run the Initial Task Workbench several tables in the System data source are populated including the F00945 table. GA. the F00945 table in the System data source is blank because it is no longer populated when a plan is validated. 1. 2. Oracle.Chapter 6. Working With Installation Workbench Working With Initial Tasks Workbench Before the workbench is run. Copyright © 2008. Double-click Custom Installation Plan. To change the status of a task. The Initial Tasks Workbench form lets you complete the Release Master task before the individual workbenches begin. However. Enter GH961 in the Fast Path field to open the System Installation Tools menu. 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. Chapter 6. Select Expand on the Row menu. The plan components. Select the task whose status you want to change. including the initial tasks. select your installation plan. . On Work with Installation Plans. 176 GA. Working With Installation Workbench 3. Oracle. 5. All rights reserved.Rev0 Copyright © 2008. 4. appear. Rev0 177 . click Disable. and will not be rerun. GA.Chapter 6. Displays status of 60 to indicate the task is complete. Copyright © 2008. and will not be rerun. Oracle. or Complete (see the table below). The task status changes. Displays status of 10 to indicate the task will be rerun. On the Row menu. Row Menu Option Disable Enable Complete Meaning Displays status of 70 to indicate the task is incomplete. All rights reserved. Enable. Working With Installation Workbench 6. 178 GA. On Location Workbench. 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 . The system updates the Detail Status to 60 and changes the Status Description from Validated to Installed. and the Data Source Workbench form appears. verify that all of your locations are listed.900 data source. Select Configure from the Form menu.Rev0 Copyright © 2008.Chapter 6. Use this procedure when running Workbench in attended mode or if you set a task break before Location Workbench. Oracle. It also updates the F984021 table. Locations are configured. 1. All rights reserved. . 2. 2. GA. Your data sources are configured. When the system has configured your data sources. it updates Detail Status to 60 and changes the Status Description from Validated to Installed. verify that all of your data sources are listed as illustrated in this example. 1. All rights reserved.900 data source.Chapter 6. Select Configure from the Form menu. On Data Source Workbench. Copyright © 2008. Use this procedure when running Workbench in attended mode or if you set a task break before Data Source Workbench. Oracle.Rev0 179 . It also updates the F98401 table to indicate completion. and the Environment Workbench form appears. 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 . Working With Installation Workbench Configuring Your Environments Environment Workbench copies the F0094. 4. review each environment and its associated parameters to make sure the values are correct.Chapter 6. 180 GA. All rights reserved.0 to load multiple environments at the same time.900 data source. select Configure. Use this procedure when running Workbench in attended mode or if a task break is set before Environment Workbench. and F00942 tables. 3. which enables Release 9. 1. it also runs a batch application to copy new generic text and to create and populate Object Management Workbench and version tables. This reduces the amount of time it takes to load environments. Using Adobe Acrobat. and confirm that all configuration statuses indicate Success. from your Planner data source to your System . When Environment Workbench has completed. as well as the F986101 table for each environment. Depending on the plan settings. After you review the environments. review all XJDE reports. 2. F00941.Rev0 Copyright © 2008. Oracle. verify that the status of each environment has been updated to 60 and that the status description has changed from Validated to Installed. On Environment Workbench. Environment Workbench can run multiple batch applications simultaneously. It then updates the F98403 table to indicate completion. . Chapter 6.Rev0 181 . and Status Description changes from Validated to Installed. On Machine Workbench. Copyright © 2008. You use this procedure when running Workbench in attended mode. 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. review each server and its associated parameters for the correct values.900 data source. When the system has configured your servers. 1. Select Configure from the Form menu. and server map tables are created. Working With Installation Workbench Using Machine Workbench Machine Workbench copies the F9650 and F9651 table from the Planner data source to the System . All rights reserved. 2. it changes the detail status to 60. or if a task break is set before Machine Workbench. Oracle. data sources. GA. Note Only valid environments. Rev0 Copyright © 2008. Refer to the JD Edwards EnterpriseOne Tools Package Management Guide for complete information about building and configuring packages. All rights reserved. Oracle. . It then updates the F98404 table to indicate completion. 2.900 data source. 182 GA. review your packages. Select Configure from the Form menu. Use this procedure when running Workbench in attended mode or if a task break is set before Package Workbench.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 . 1. On Package Workbench. XJDE0045. control. and system tables from base location to remote location servers.Chapter 6. It also pushes delivered packages to primary Deployment Servers at remote locations by launching the multi-tier UBE (R98825C). by launching different versions of R98403 (XJDE0043. All rights reserved. Working With Installation Workbench Using Remote Location Workbench Note This workbench only appears when Remote Locations have been set up. GA.Rev0 183 . Copyright © 2008. Remote Location Workbench loads business (master and constant). XJDE0046 and XJDE0047). This workbench is processed only if you opted to install remote locations and chose to load replicated data and push packages. Oracle. data dictionary. Use this procedure when running Workbench in attended mode or if a task break is set before Remote Location Workbench. XJDE0044. On the Form menu.Rev0 Copyright © 2008. . Release 9. On Remote Location Workbench.0 displays all remote location activities in the detail area. 2. 184 GA. All rights reserved. After all remote location activities are complete. Oracle. Working With Installation Workbench Configuring Remote Locations To configure remote locations: To configure your remote locations: 1. select Configure to launch the workbench.Chapter 6. click Next. 3. All rights reserved. See Performing Post Installation Tasks.Rev0 185 .Chapter 6. GA. From Congratulations. click Finish. Oracle. Note Post Install Procedures still need to be completed from a client. Working With Installation Workbench Finishing Installation Workbench To finish the Installation Workbench: 1. From Work with Installation Plans. 2. click Close. Copyright © 2008. on the Form menu. 186 This page intentionally left blank . the test returns a failure message. Once the Workbench tasks are all complete. you must run the PORTTEST program for each environment. GA. 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). enter these commands: d: [or the appropriate drive letter] cd \JDEdwards\E900\ddp\System\bin32 Copyright © 2008. complete the steps in the Microsoft Windows Cluster chapter of Release 9. rerun PORTTEST. Select all on table F0902 failed . Tip Cluster Software Considerations. 3. The PORTTEST program initializes a user and an environment (assuming that Release 9.Chapter 7. Before you attempt to start Release 9. skip this step.0 on a Cluster in JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide. Oracle. If using cluster software.0. To verify that Release 9. The basic PORTTEST procedure ensures connectivity.Rev0 187 .rcode=0). All rights reserved. Log on to the Enterprise Server as JDE. To verify that Release 9. (for example. Ignore any errors relating to accessing the F0902 table. Refer to Using the PORTTEST Checklist for additional details including the PORTTEST checklist. and the Enterprise Server is configured.0 is installed correctly on the Enterprise Server.0 is installed and configured correctly). 2. To verify the Enterprise Server installation using PORTTEST: 1. Working With the Enterprise Server This chapter contains these sections: • • • • • Verifying the Release 9.0 is installed correctly. Open a DOS command window.0 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 9.0 Enterprise Server Installation Using PORTTEST Note When running PORTTEST after installing the Enterprise Server. see Using the PORTTEST Checklist for diagnostic assistance. Locate and highlight every service that is prefixed with the word JDE (JD Edwards EnterpriseOne releases prior to 8.INI on the Enterprise Server. password is the password for that user. These parameters are case-sensitive. Note When you stop JD Edwards EnterpriseOne network services on a Microsoft Windows server. 4.11) or PeopleSoft (releases 8. access Services. Working With the Enterprise Server PORTTEST userid password environment where userid is a valid Release 9.0 table. you should either shutdown and restart your Enterprise Server or complete the remaining steps in this procedure. Locate and highlight this service: JDE E900 3. 8. Click Start. 5. To stop the services completely. To start the network services on the Enterprise Server: 1. On the Enterprise Server. Select Debug. Stopping Network Services on the Enterprise Server To stop the network services on the Enterprise Server: 1. Click Stop. and environment is the environment you are verifying. 3.11). If PORTTEST fails to run. some processes might not stop. . 2. review the jde_###. Starting Network Services on the Enterprise Server After you install the JD Edwards EnterpriseOne Platform Pack on the Microsoft Windows Enterprise Server. access Services. All rights reserved.10.0 user. and 8. you must start the Network Services. Enter the PORTTEST command for each environment. If it does not. Tip Troubleshooting. 2. 188 GA. go to Task Manager and right-click any JD Edwards EnterpriseOne process that is still running. From Control Panel.9.9 and after 8. Oracle.Chapter 7. From Control Panel.log that was specified in the JDE.Rev0 Copyright © 2008. The program should display messages indicating the selection of records from an Release 9. The JD Edwards EnterpriseOne process that you selected shuts down. the defaults from the F98511 table are overridden by the current definition. UBE. OCM is created based on the Data Class for data sources and for a table or GT object. This includes Business Data.0. The last set of data sources is the environment data sources. the shared data source template (F98511. A set of data sources is configured for each environment. The first time these data sources are configured. and Object Librarian data sources. RTE. These defaults are then used to create the data source definition in the F98611 table. GA.Rev0 189 . If record in the F98611 tables already exists. Data Dictionary. Oracle. 6. BSFN. you must configure your data sources. Understanding Data Source Setup Before OCM can be created. The first set of data sources to be configured is the Enterprise Server data sources. The user is then optionally prompted to customize the data source. Control Tables.SPLL = DEFAULT).SPLL = *ENV) stores defaults for environment data sources.SPLL = Environment Name). 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. They are generated when you finalize an installation plan. If records in the F98611 table already exists. The next set of data sources to be configured is the shared data sources. The Data Class is stored on the Data Sources By Environment (F98511). The user is then Copyright © 2008. OCM records are not created for the server map data source. Stop the debug process and exit Visual C++. Data source configuration and prompting is driven by the data in the F98511 table.SPLL = *SHARED) is copied and tokens are replaced in the data source name and properties to create the shared data source records (F98511. Also. logic data sources are automatically configured without prompting. 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 9. Working With the Enterprise Server This command takes you to debug mode in Microsoft Visual C++. the defaults from the F98511 table are overridden by the current definition. The environment data source template (F98511. These defaults are then used to create the data source definition in the F98611 table. Central Objects and Versions. This includes the Server Map data source. All rights reserved. and XAPI mappings are created for the logic data sources. Repeat this process for each JD Edwards EnterpriseOne process that is running. This includes System. Data Source Master (F98611) and Object Librarian Master (F9860) tables.Chapter 7. 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. If a record is not found. The following table shows the default mappings for UBE and BSFN objects. Thus. If the default is Enterprise Server. JD Edwards EnterpriseOne provides preconfigured records for the standard environments. Mappings are not created for tables in the Planner and Internal data classes. the plan is finalized. a default mapping to the Enterprise Server is created. Based on the environment that is being configured and the data class for the object. JPY900 Enterprise Server Enterprise Server • Understanding OCM Customization 190 GA. OCM is created during finalization. Given that the standard environments do not always follow the defaults that are specified in the *ENV template.Rev0 Copyright © 2008. a default mapping to LOCAL is created. 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. Working With the Enterprise Server optionally prompted to customize the data source. .Chapter 7. Enterprise Server LOCAL HTML Web Server Environment JDV900. PY900 UBE BSFN The algorithm is: • If the default is LOCAL. 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). Oracle. PD900. Understanding OCM Creation After your data sources have been defined and the plan is complete. If a record is found and that record is set as the default mapping data source (F98511. no mapping is created and the table is effectively mapped to the default data source.SPDFLTMAP). All rights reserved. the data source name is fetched from F98511.SICLDF). JPD900. a mapping with object name DEFAULT is created.SIBFLOCN = 1). 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. JPS900. otherwise the actual object name is used. PS900. the *ENV template is only used for custom environments. but the output depends on whether the default mapping is LOCAL or an Enterprise Server. Understanding Logic Data Sources The OCM generation algorithm for UBEs and BSFNs are identical to each other. Base Environment DV900.SIBFLOCN = 3). The template can be found by filtering on *ENV in the environment field. By understanding this application. If you want to split business data into multiple data sources. you can implement custom environment naming standards and ease the creation of environments. If you want to add a new data source to a standard JD Edwards EnterpriseOne environment. It categorizes the type of data stored in data sources and tables. and the default values for the properties of the data source. • Object Management Workbench (GH902) – Select the table in the left tree view in OMW and click Design. these records are copied and tokens replaced to create records specific to the new environment. in the Business Data data source the data class is ‘B’ while in the System data source the data class is ‘S’. The information in this table can be edited using Data Source Templates By Environment (GH9611) program. Modifying the data class does not affect existing OCM mappings. The first time data sources are configured for a new environment. OCM will be created based on this information.Rev0 191 Copyright © 2008. Associating Table Data Classes A table is associated with a data class using a field on the Object Librarian table (F9860. 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. They are set up when selecting an Enterprise Server. All rights reserved. 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. You should do these steps before creating your plan. They are stored in the F98511 table. Records with an environment *LOGIC are for logic and server map data sources. 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. Oracle. you need to create a new data class. Typically.Chapter 7. Table data classes can be modified two ways. Installation Planner prompts for this set of data sources whenever a new environment is created.sicldf). for example. Modifying the Data Source Template A data source template defines the set of data sources that will be used by an environment. Click OK. enter the environment name into the filter field and add a record specifically for that environment. GA. Select the Install/Merge Codes tab and modify the data class value. . you will add records to the template for new environments. 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. To install your first printer: 192 GA.900 Setting Up a Printer on the Enterprise Server This section describes these tasks.900 Business Data – ENV2 System .900 Control Tables – ENV1 Versions . Once these three steps have been taken. Go to GH9611 and open Table Data Classes. Oracle. These tasks are described in detail in the JD Edwards EnterpriseOne Tools System Administration Guide.900 Object Librarian . which must be performed in the deployment environment: • • Adding a New Printer Defining a Default Printer You also can print Release 9.PY900 Data Dictionary . All rights reserved.900 Data Dictionary .0 provides a Printer Setup director to help you add printers. Select one or more tables whose data class will be changed. Use the QBE to filter the list of tables in the grid.900 Object Librarian . 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. Type in the new data class value and click OK. Instructions appear on each form of the director to guide you through the printer addition process. modify existing printers. . Refer to that document to learn more about setting up a printer to run from the Release 9. This procedure is used in conjunction with the steps that appear on the forms of the Printer Setup director. Adding a New Printer Release 9. and delete printers.900 Data Dictionary .Chapter 7.0 Enterprise Server.DV900 Data Dictionary .Rev0 Copyright © 2008.900 Control Tables – ENV2 Versions . Click Select. Working With the Enterprise Server This should only be used by a JD Edwards EnterpriseOne administrator.0 reports. 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 .900 Object Librarian .900 Object Librarian . All rights reserved. For printing reports to a non-network printer. select Printers (P98616). Release Print Shared Name Copyright © 2008. and dash ( . Enter the name of the print server for the printer you are setting up. along with the print shared name. The Printers form appears. Oracle. The welcome page for the Printer Setup director appears. 2.0 is running. 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. Working With the Enterprise Server 1. The Platform Information form appears. leave this field blank. ). GA.Chapter 7.). 4. On Platform Information. All characters are valid except the forward slash ( / ) and the backslash ( \ ). On the Printers menu (GH9013). Release 9.Rev0 193 . Review the welcome page and click Next. which is unavailable for modification on the subsequent form. to create the printer name. On the Printers form. click Add Printer. Enter the share name of the printer you are setting up. period ( . numeric (0-9). This page describes the tasks that the director helps you perform. The platform type may appear by default. Valid characters are all alpha (A-z).0 uses this name. depending on the operating system on which Release 9. 3. Choosing PostScript or Printer Command Language (PCL). which you use to set the paper dimensions and line parameters. The custom option uses advanced features of the printers application. when choosing the PostScript option.0 to draw paper from as the default tray. physical location of the printer. 194 GA.Chapter 7. Printer Model Printer Location On the Details tab.0 disables the grid at the bottom of the form and any paper types you have chosen are cleared. 10. 5. Oracle. specify one of the Printer Definition Language options as the default value. printer definition language (PDL). A user can override this default PDL at the time a batch process is submitted. Working With the Enterprise Server 9. After you complete the requisite fields. fields appear in a box labeled Line Printers. On the Details tab. in the box labeled Printer Definition Language. 6. select one of these options: • • • • PostScript PCL Line Printer Custom 8. • The Fields in the box labeled Line Printers are used to set the paper dimensions and line parameters. Release 9. In the Default box. You can select multiple PDLs.0 disables the Line Printer option. Release 9. On the Details tab. click Next to access the Printer Setup form. When choosing the Line Printer option. Choosing Line Printer. complete these fields: • • 7. when choosing the Line Printer option. and paper types. which are explained in the later steps in this procedure. This procedure is explained in later steps in this section. All rights reserved. but only one default PDL. On the General tab.0 disables the PostScript and PCL options. which is unavailable for modification on the subsequent form. JD Edwards EnterpriseOne automatically provides a printer type of *JDE LINE PAPER for the printer. Use this form to set information for the printer such as the printer model. . along with the print server name. Enter a numeric value in this field to indicate which tray number you want Release 9. 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.Rev0 Copyright © 2008. to create the printer name.0 uses this name. 9. this logic occurs: • Release 9. Chapter 7. from the Form menu. or highlight one of the filters and click Copy or Select. The Advanced option is enabled only when Custom has been chosen. Enter the name of the conversion program that you want to add or copy. Either click Add.Rev0 195 . 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. GA. Enter a value to specify the number of characters in one line of text in the specified report. 13. Enter a value to specify the number of lines of text on one printed page. 11. PCL. If you do not want to change or add a conversion filter. The Work With Conversion Programs form appears. Displays a value that is calculated automatically based on the values entered in the Line Printers box. skip to step 16 in this task. 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. 14. A checkmark appears in the row header for each paper type that you select. Copyright © 2008. On the Details tab. In the grid at the bottom of the Printer Setup form. 16. select Advanced. the Custom option lets you specify a conversion filter to use. Working With the Enterprise Server 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. a field appears beneath the Custom checkbox. The Printer Setup form appears. Oracle. and continue with the steps in this procedure. The Advanced Conversion Program form appears. Enter a value to specify the number of lines of text in one vertical inch. To change or add a conversion filter. or line). double-click the row header for each paper type that your printer supports. The Work with Conversion Programs form appears. When choosing the Custom option. Click OK. 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. Displays a value that is calculated automatically based on the values entered in the Line Printers box. the Parameter String field is populated with the string that you highlighted on the previous form. Click Close. Parameter String 15. 12. When making a copy. All rights reserved. To add a new paper type. . In the Default Type column. 21. The Paper Type Revisions form appears. All rights reserved. continue with these steps: 19. select only one paper type as the default. Instructions are included later in this task. Working With the Enterprise Server Note You can add new paper types as necessary. enter the numeral 1 in the row for the paper type you want to use as the default. The Work With Paper Types form appears. 17. Click Add. 18. A user can override the default paper type when a batch process is submitted. 20. select New Paper Type. From the Form menu.Chapter 7.Rev0 Copyright © 2008. Complete these fields: • • Paper Type Paper Height 196 GA. Oracle. Form-specific information indicates the unit of measure in which the paper height and width are entered. Define the number of columns per page. Each shared directory on a server has a share name.0 saves the new printer setting and returns you to the first form in the Printers application. Oracle. 80 or 132.IBM 5224 printer only 8 . 5224.Chapter 7. and then click Close to return to Printer Setup. For example. 23. Enter a name that refers to a shared resource on a server. 60 or 66. You should only define values that are supported by your printer. All previous paper type selections are cleared and must be reselected if you want to use them again. and 3287 printers only 6 .Rev0 197 . Define the height of the paper for this paper type. Values are: 4 . 22. Working With the Enterprise Server • • Paper Width Unit of Measure The software saves the new paper type. LEGAL. Enter a user defined code (00/UM) to define the quantity in which to express an inventory item. Release 9. For example.IBM 5219. For example. Define the width of the paper for this paper type.IBM 5224 printer only Columns Per Page Characters Per Inch (CPI) Line Per Page Line Per Inch (LPI) Copyright © 2008. click End. and A4. When finished entering information for the printer on the Printer Setup form. 5225. Define the horizontal printing density in characters per inch. The new paper type is available in the grid on the Printer Setup form. For example. CS (case) or BX (box). Define these attributes for your printer: • • Printer Model Printer Location Printer Model Paper Type Paper Width Paper Height Unit of Measure Designates the physical location of the printer Enter a user defined code (H98/PT) to define the type of printer paper. This value is in the unit of measure specified by Unit of Measure. IN = Inches and MM = Millimeters. such as letter or legal. LETTER. GA. This value is in the unit of measure specified by Unit of Measure. Click OK to return to the Work With Paper Types form. For example. which is used by clients to refer to the directory. You should only define values that are supported by your printer. Define the computer that receives documents from clients. Platform Type Server Name Printer Name Define the type of physical hardware on which the database resides. Define the number of lines per page. Define the line spacing in lines per inch. All rights reserved. Chapter 7. Working With the Enterprise Server 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. 198 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 7. 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. 6. Click OK, and then click Cancel to access the Work With Default Printers form. 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. Copyright © 2008, Oracle. All rights reserved. GA.Rev0 199 200 This page intentionally left blank Chapter 8. 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 9.0 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 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 9.0 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 Package Management Guide Copyright © 2008, Oracle. All rights reserved. GA.Rev0 201 Chapter 8. Installing the Workstations for Developers and System Administrators Preparing for Workstation Installation To prepare for the installation of Release 9.0 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 9.0. 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 9.0 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 9.0 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\E900\PD900\package • Read/write access to this directory on the primary Deployment Server: \client For example: \\deployment_server_name\E900\client 202 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 8. Installing the Workstations for Developers and System Administrators Understanding Workstation Installation The workstation installation program copies all necessary components of Release 9.0 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 9.0 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 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\E900\OneWorld Client Install To ensure that the shortcut works correctly, ensure the Start in: field contains the location of the installmanager.htm file. To create a desktop shortcut: 1. To edit the Start in: field, in Microsoft Windows Explorer or on the desktop, right-click the shortcut. Copyright © 2008, Oracle. All rights reserved. GA.Rev0 203 Chapter 8. Installing the Workstations for Developers and System Administrators 2. 3. 4. Click Properties, and then click the Shortcut menu. Double-click the Release 9.0 InstallManager shortcut to start the Release 9.0 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\E900 shared drive on your Deployment Server from Microsoft Windows Explorer. To use a shared drive: 1. Double-click InstallManager.exe to start the Release 9.0 installation manager. The InstallManager.exe file is located in this folder: OneWorld Client Install 2. 3. On JD Edwards EnterpriseOne Release 9.0 Installation Manager, click Workstation Install. On Client Workstation Setup, click Next. If you do not have the latest versions of Microsoft Internet Explorer or SSE the Release 9.0 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 SSE 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 9.0 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 9.0: c:\E900 6. 204 To install the package, click Finish. GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Install Path Chapter 8. Installing the Workstations for Developers and System Administrators 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 9.0 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 9.0 after installing the client workstation, or upgrading to Release 9.0, 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\E900 To work with silent mode: 1. 2. 3. 4. From the Start menu, select Run. Click Browse. Locate the\JDEdwards\E900\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 9.0 should be installed (for example, c:\E900). You also can include the following optional parameters: -t Typical Using the typical parameter installs the development objects. -t Compact Using the compact parameter does not install the development objects. Copyright © 2008, Oracle. All rights reserved. GA.Rev0 205 Chapter 8. Installing the Workstations for Developers and System Administrators -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 9.0 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 9.0 after installing the client workstation, or upgrading to Release 9.0, 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 Package Management Guide. Understanding Third-Party Products SSE is required for Release 9.0 Workstations. If not already installed, it is installed during the installation process. The workstation installation program detects the latest version of SSE and, depending on the version, prompts to update this application during the Release 9.0 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 9.0 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 9.0 supports group preferences for user profile workstation configuration and environment assignment. 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 9.0. 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 206 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. This task describes modifications required to make to the workstation JDE.INI on the Windows-based Deployment Server are updated automatically.INI for a workstation.Rev0 207 .INI on the Deployment Server: 1. change the original file on the Deployment Server.INI before installing Release 9. For languages. as well as for information about defining user display preferences. Open the workstation JDE.Chapter 8. some records will not be inserted into tables and Insert Record Failed errors will appear.INI and modify these settings: Copyright © 2008. The file is then copied from the Deployment Server to its respective workstation during the web development client installation process. Use this procedure to modify settings in the JDE.0 on the workstation. GA.INI on the Deployment Server To modify the workstation JDE. the JDE. modify the ODBCDataSource. both the Enterprise Server and workstation JDE. All rights reserved.INI for multiple client workstations.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. Working with the Workstation JDE. Installing the Workstations for Developers and System Administrators determining how groups are to be organized and what preferences each group shared to have.INI are stored on the Deployment Server.INI in this directory on the Deployment Server: \JDEdwards\E900\OneWorld Client Install\Misc Modifying the Workstation JDE.INI need to be modified for the preferred language being installed. See Also JD Edwards EnterpriseOne Tools System Administration Guide for more detailed information about setting up group profiles and how to use them.INI on the Deployment Server To facilitate the administration and maintenance of the JDE. For multiple language usage. When using a double-byte language. Oracle.INI on the Deployment Server Understanding the Workstation JDE. all instances of the JDE. To make a change to a JDE.INI on the Deployment Server Modifying the Workstation JDE.INI on the Deployment Server This section discusses: • • Understanding the Workstation JDE. Oracle. . The system reads the JDE. Installing the Workstations for Developers and System Administrators Note For language installations. [INSTALL] [JDENET] 2.Rev0 Copyright © 2008. If multiple languages are installed. 208 GA. enter: Initial_Language_Code = x where x is the value for the language installed or. for the preferred language. Verify that the LocalCodeSet value and code page setting are set to the appropriate values.INI. See Language Process Overview for appropriate values.INI values are set to your preferred language. Save and close the file. Verify that the port number specified for ServiceNameListen and ServiceNameConnect matches the port number in the Enterprise Server JDE.Chapter 8. if multiple languages are installed. All rights reserved. [INTERACTIVE RUNTIME] For the language you are installing.INI setting for the installed language. ensure that the workstation is set up correctly for language preferences to display and print forms. verify that the appropriate JDE. Within Release 9. make sure to copy the image files and OLE objects to the new location. Media Object Queues enable you to specify the storage location of media objects to be tracked by reference as opposed to physical network location. A valid network-qualified path must exist for this machine. Media object queues provide the system administrator the ability to easily manage the storage of media objects and helps in a Release 9. 4. Oracle. ComposerCBT is shipped with an x for the drive name. For OLE objects. 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. 3. Log into Release 9. 2. the media object queue path does not require \\ or server_name. To enable the Composer CBT queue. the name of the queue must be OLEQUE. Generally the queue paths include server_name and queue_name.0 applications. replace the x with the drive letter that the workstation uses Copyright © 2008.0 applications. To define the location for a new OLE queue. Understanding Media Object Queues Media objects enable the attachment of information to Release 9. When using ComposerCBT. GA. To enable media object queues at the customer site. The media object queues must reside on a Microsoft Windows-based machine.0 configuration. Media object queue paths are shipped with generic server names.0 as JDE in the DEP900 environment. See Also Media Objects and Imaging in the JD Edwards EnterpriseOne Tools System Administration Guide for more information about the use of media objects. If you modify the OLEQUE path. select Media Object Queues (P98MOQUE). scanned images).Chapter 9. Replace server_name with the name of the Deployment Server or the location of the media object queue. set up media object queues in order to use images that are outside the domain of the imaging product (for example. Modifying Media Object Queues To modify your media object queues: 1. Complete these fields: Name Path Enter a valid value for your queue.0. All rights reserved. enter the Deployment Server name in the media object queue path.Rev0 209 . A valid queue path for a network location might be: \\server_name\E900\queue_name where server_name is your Deployment Server and queue_name is the name of the media object queue. When using the Deployment Server to store media object queues. This enables easier administration of media locations. From System Administration Tools (GH9011). remember to make the machine available for use daily by Release 9. click Add. Use the Deployment Server or any other Microsoft Windows-based machine. Chapter 9. 5. From System Administration Tools (GH9011). Understanding Media Object Queues to access the server where the media object queues reside.Rev0 Copyright © 2008. on Media Object Queues. 2. To define the location for the Help file. 7. Exit Release 9. On Media Object Queues. . enter Help in the Name field and click Find. change the information in the Queue Path On-Line field to reflect the new location. Oracle. Copy the image files and OLE objects to the new location. select Media Object Queues (P98MOQUE). To change an existing media object queue.0 and log back on to enable the changes. 210 GA. For example: N:\Mediaobj\ComposerCBT. Specifying the Help Location To specify the help location: 1. 6. click Find to display a list of queue names and their paths. All rights reserved. select the queue name you want to modify. 9. 8. On Work With Media Object Queues. Chapter 9. Understanding Media Object Queues 3. On Media Object Queue Revisions, complete these fields: Path Replace the existing default value with: http:\\Server_Name\E900\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 9.0 and log back on to enable the changes. Copyright © 2008, Oracle. All rights reserved. GA.Rev0 211 212 This page intentionally left blank Chapter 10. Performing Post Installation Tasks This section contains these tasks: • • • • • • • • • Understanding Post Installation Tasks Resetting SQL Server Options Setting Up Microsoft Windows Security on Release 9.0 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 Enabling Verity Enhanced Search Capability 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.Rev0 213 Chapter 10. Performing Post Installation Tasks Resetting SQL Server Options To reset the database options. 1. 2. 3. In Enterprise Manager, double-click a JD Edwards EnterpriseOne database. Click the Options tab. Turn off these SQL Server options: • • Select Into/Bulk Copy Truncate Log on Checkpoint Repeat this process for each JD Edwards EnterpriseOne-related database. 214 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 10. Performing Post Installation Tasks Setting Up Microsoft Windows Security on Release 9.0 Directories To set up Microsoft Windows security on the Release 9.0 directories and files on your Deployment Server. Use these charts to determine what permissions are required for the various types of Release 9.0 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\E900 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 Copyright © 2008, Oracle. All rights reserved. GA.Rev0 215 Chapter 10. 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 216 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 10. 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 Copyright © 2008, Oracle. All rights reserved. GA.Rev0 217 Chapter 10. 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 218 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 10. 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. Copyright © 2008, Oracle. All rights reserved. GA.Rev0 219 select Batch Versions (P98305). otherwise. Build Task Word Search Table. The installation of these tables is optional. You can search for a Solution Explorer task by entering a complete or partial task name. You can submit your job without selecting any options on Version Prompting. Oracle. the system locates the menu or task and word search tables for the environment you are logged on to. build the Word Search tables using one or a combination of the PD900. The Find It! program is part of the Solution Explorer and uses the same underlying functionality as the Task Word Search. Building Task Word Search Tables To build task word search tables: 1.0 environment for your pristine or publisher copy of your tasks.0. 6. The batch process can take several hours to complete. you must following the task below to build Task Word Search tables. DV900. However.5 MB. Word Search locates a JD Edwards EnterpriseOne menu or task if the name is not known. Select version XJDE0001. When running the Word Search Build programs. from Version Prompting you can specify Data Selection and Data Sequencing and access the Advanced Version Prompting form. 5.Prod. 220 GA. 3. The system takes the task information from the Object Configuration Management mappings on the environment you are logged onto and populates the F91014 table. Use an environment that points to your local workstation only if you very recently installed Release 9. This environment typically maps your tasks to the data source Control Tables . Enter R91014 in the Batch Application field. This is the name of the batch process that updates the Task Word Search table. Log on to the Release 9. 2. Click Submit to send your job to the report processing location. 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. and PS900 environments. The Work with Batch Versions form appears. For the Find It! Program to work.Chapter 10. On System Administration Tools (GH9011). . If you follow the recommended environment builds during installation. All rights reserved. you could be building from out-of-date tasks. 4. PY900. the data source where the Task Word Search master table resides. The complete Word Search Build is approximately 7. Click Find to locate the versions available on your workstation.Rev0 Copyright © 2008. The Version Prompting form appears. the path to the HTML file of the summary document for the task is: \\Server_Name\PY900\SolutionExplorer\Data\JDE001234\summary.0. When JD Edwards EnterpriseOne installs the documentation files. This screen can be used to display information that is relevant to end users in the enterprise. For Solution Explorer to link each HTML file with the correct task.0 applications.0 applications. called ActivEraData. role-based menus.Chapter 10. with a generic path to the documentation. and training materials. You can search for a Solution Explorer task by entering a complete or partial task name. It can be an external Web site. For more information about Solution Explorer. an intranet site. 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 9. refer to Modifying Media Object Queues . All rights reserved. called the Work with Media Object Queues (P98MOQUE) program. For example. Solution Explorer locates and displays the associated documentation when a user accesses a Task Location or Task View Location. The file path from Solution Explorer to the HTML documentation files is defined in the F98MOQUE table.0 is installed. For the Find It! Program to work. During the installation process. Users can access Solution Explorer to search and navigate quickly through Release 9. Oracle. Copyright © 2008.Rev0 221 .0 on your Deployment Server. When the queue name ActivEraData is correctly mapped to the main HTML documentation directory. Using 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. a directory called PortalLite is created when the Deployment Server is installed. implementation and configuration options. The Find It! program is part of Solution Explorer whose search feature uses the same underlying functionality as the Task Word Search. documentation. see the Solution Accelerator Suite Implementation Guide. it must be configured by accessing the corresponding program. or even HTML files stored on any server on the network. The directory path has this structure: \\Server_Name\E900\SolutionExplorder\Data where Server_Name is the name of your Deployment Server. it creates an entry in the Media Object Queue table that associates the Queue Name. you must open this program and change the server name for the directory path associated with the Queue Name ActivEraData. Setting Up Solution Explorer HTML Documentation Path When Release 9. Users also can customize Solution Explorer to create their own tasks and link tasks to other Web-based information.html where Server_Name is the name of the Deployment Server For more information on setting up the documentation path. if a task named JDE001234 exists. Solution Explorer locates these files and displays the associated documentation in its own window whenever a user selects a task. Solution Explorer is a convenient window into Release 9. you must perform the previous task Building Task Word Search Tables. GA. the system automatically stores HTML documentation hierarchically in folders located in a common documentation directory. Performing Post Installation Tasks Setting Up Solution Explorer Solution Explorer is the Microsoft Windows-based interface that provides access to Release 9. Chapter 10. 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 directory could reside anywhere on the network, such as on a HTML Web Server or on a local workstation. When the Release 9.0 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 E900, the [Explorer] section of the JDE.INI is updated as follows: [Explorer] ExplorerHomeURL="\\DepServer1\E900\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\E900\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. 222 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 10. 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 9.0 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 9.0 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 9.0 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 9.0 database connectivity. Copyright © 2008, Oracle. All rights reserved. GA.Rev0 223 Chapter 10. 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. 224 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 10. Performing Post Installation Tasks Configuring the Release 9.0 Database Connections for Vertex Quantum Tax Applications To configure Release 9.0 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 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. Copyright © 2008, Oracle. All rights reserved. GA.Rev0 225 Chapter 10. 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. Enter the ODBC data source name for your server (for example, SQLSERVEROWNTS3). Server For ISAM, leave this field blank. Enter the server name of your Enterprise Server. For ISAM, leave this field blank. Enter the table owner. For ISAM, leave this field blank. Enter the password for the table owner. User ID Password 7. Click OK. The changes do not take effect until you have logged off of your system and logged back on. 226 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 10. Performing Post Installation Tasks 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 9.0 objects are configured in the system OCM to execute on the server. Do not change the mappings. For Vertex Quantum for Payroll Tax: • • 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 9.0 Scripting Tool, also called Autopilot, is an automated testing tool used to create scripts to test the execution of Release 9.0 applications. Autopilot is included on the Release 9.0 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 9.0 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 9.0, and then create the corresponding ODBC data source. The ODBC data source and corresponding entry in the ODBCDatasource.inf file are automatically created by the installation. Testing the Vertex Quantum Connection from Release 9.0 Use the following procedures to test the Vertex Quantum connection from Release 9.0. To test the Vertex Quantum for Payroll Tax interface: 1. Access the Payroll Workbench menu (G07BUSP11), and select Pay Cycle Workbench. The Work with Payroll Cycle Workbench panel appears. Copyright © 2008, Oracle. All rights reserved. GA.Rev0 227 Chapter 10. Performing Post Installation Tasks 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 9.0 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 9.0 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 9.0 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. 228 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. Chapter 10. 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.Rev0 229 Chapter 10. 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 Enabling Verity Enhanced Search Capability If you are using the enhanced search capabilty with JD Edwards EnterpriseOne, you must download and install the Verity Software from the Oracle E-Delivery Web site at this link: http://edelivery.oracle.com/ 230 GA.Rev0 Copyright © 2008, Oracle. All rights reserved. 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). Working With Signon Security For initial installations of JD Edwards EnterpriseOne. GA. you will not be updating the correct security tables for your JD Edwards EnterpriseOne system.Rev0 231 . the system may add an invalid record to the F98OWPU table. Warning If you attempt to add a user with the P98OWSEC program before you add the system user through the P980001 program. Oracle. 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. you must setup system user(s) using the Work With System Users (P980001) program to populate the F98OWPU table. All rights reserved. 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.Chapter 11. You might have to delete the invalid record from F98OWPU using the SQL Query tool. Rev0 Copyright © 2008. Working With Signon Security Setting Up Signon Security To set up signon security: 1. 4. All rights reserved. . Enter the same password that you entered in the password field. 232 GA. On P980001 [Work With System Users]. complete the following fields: System User Data Source Password Password Verify JDE DEFAULT Enter a valid password for your installation.Chapter 11. Click OK. Oracle. 2. click Add. On System User Revisions. 3. Click Find to verify the new record was added. Chapter 11. Click Add. 7. Copyright © 2008. All rights reserved. complete the following field: User ID / Role JDE 6. Working With Signon Security 5.Rev0 233 . On P98OWSEC [Work With User Security]. Click Find. Oracle. GA. On Security Revisions. 234 GA. Enter a value applicable to your installation. Working With Signon Security 8. Oracle. Enter a value applicable to your installation. 9. Ensure the Enabled radio button is selected.Chapter 11. All rights reserved. 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. Click Find to verify that the record was added. 10.Rev0 Copyright © 2008. . Click OK. Chapter 11. 1. you must setup up security overrides for whoever is doing the package build. PKGBLD. Add a security override for PKGBLD for Central Objects . 3. For example. All rights reserved. JDE. DV900.DV900 using system user DV900. See Also • JD Edwards EnterpriseOne Package Management Guide Copyright © 2008. Create a role for package build. Add the PKGBLD role to the user who will be doing package builds. GA. 4. 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. Oracle. For example. 2. Create a system user for the owner of the Central Objects data source. For example.Rev0 235 .98. Enabling Client-Side Signon Security Locate the JD Edwards EnterpriseOne client JDE. Caution If you have changed the database password for the JDE user.900 DefaultEnvironment=DV900 Default Role=*ALL Row Security=NO_DEFAULT 236 GA. you must restart the JD Edwards EnterpriseOne Services so the settings can take effect.ini must be the new password. Typically the file can be found at the following location: x:\JDEdwards\E900\OneWorld Client Install\Misc\JDE. Oracle. Ensure that JD Edwards EnterpriseOne client JDE. Working With Signon Security Enabling Server-Side Signon Security Ensure the JDE.INI has these settings: [SECURITY] SecurityServer=server_name DataSource=System .INI on the Enterprise Server.Rev0 Copyright © 2008. the password you specify on Enterprise Server in jde.Chapter 11. All rights reserved.900 History=0 After you modify the JDE. .INI where x: is the drive on which JD Edwards EnterpriseOne is installed.INI on the Enterprise Server has these settings to support signon security: [SECURITY] SecurityServer=server_name User=JDE Password=JDE Default Role=*ALL DefaultEnvironment=PD900 DataSource=System .INI that is deployed from the Deployment Server. Oracle. Warning Using default settings may expose a potential security risk. Setting Up EnterpriseOne Single Sign-On of the JD Edwards EnterpriseOne Tools Security Administration Guide.Rev0 237 . Copyright © 2008. 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 Security Administration Guide. All rights reserved.Chapter 11. 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. GA. 238 This page intentionally left blank . These options are available to a single server. 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. The system administrator is required to build and test packages at the server level. to deploy packages to both servers and workstations. Building and Testing Packages This section discusses: • • • • • • • • Understanding Packages Obtaining the JDK/JRE Installing Application Fixes Updating the System Path Reviewing Pre-Package Build Issues Reviewing Troubleshooting Tips Building an Alternate Language Package Assembling a Package that Contains Published Business Services Understanding Packages Building and testing packages provides a method to create a package.0 software. or individual users. build.Chapter 12. to build and define packages with custom solutions. package build. Package build is used to set up a workstation or server with Release 9. and to troubleshoot the packages.0 in- Copyright © 2008. These processes can take several hours. DV900FA or DV900PA). and package deployment. An installer may complete the process for the workstations.Rev0 239 . Oracle. Changing the package from a full to a partial package on some workstations. to define and build a package. Examples scenarios include: • • • • • Setting up a new workstation. Deploying custom solutions to all or to selected users. These options can be delivered using just-in-time or scheduled installation methods. Release 9. Creating a new pathcode for development. groups. to a workstation or user. or to selected machines. These features use a step-by-step director process and include package assembly. The procedures take place on the Deployment Server in the deployment environment as user JDE. All rights reserved. depending on the scope of your business. You must define. There are options to define three different package types. Deploying a fix. and to distribute them through two different deployment options. GA. and individual fixes.when compared to current search. Before building a package. ESU bundles. Supported compiler versions vary according to release of JD Edwards EnterpriseOne. You can obtain the requisite JDK/JRE from Sun. and deploying many types of software fixes such as ESUs and Tools Releases. Refer to Accessing Minimum Technical Requirements. Oracle. 2. See Also Package Build in the JD Edwards EnterpriseOne Tools Package Management Guide for information about how to build and deploy packages. See Also For the supported version of the JDK/JRE. Change Assistant is a java-based tool that centralizes and economizes the process of searching. and can be downloaded from the Update Center. Installing Application Fixes Before you build packages. 240 Access the Control Panel. download. . This section includes a list of known issues associated with the package build. Obtaining the JDK/JRE You must have a specific JDK/JRE on the Deployment Server in order to build packages. Updating the System Path Before you build a server package on a Microsoft Windows machine.Rev0 Copyright © 2008. The time required to build packages to the workstation varies depending on the database being used. refer to Using the Change Assistant in the JD Edwards EnterpriseOne Software Update Guide. assembly. and deployment process and gives instructions for avoiding them. The package build and assembly process includes many critical tasks that must be successfully completed to install the packages correctly. refer to Accessing Minimum Technical Requirements in Understanding JD Edwards EnterpriseOne of this guide. 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 . For instructions on using Change Assistant. review these instructions to successfully complete this process. downloading. you must update the SYSTEM path with Microsoft Visual C++ on the Enterprise Server.Chapter 12. GA. Open System and click the Environment tab. This path is dependent on the compiler version that you are using. It is available free of charge for maintenance paying customers. You should use Change Assistant to find relevant application fixes for system codes associated with the functionality you are using. All rights reserved. JD Edwards EnterpriseOne Tools Development Standards for Business Function Programming Guide for information on how to convert business functions to support Unicode text strings. Building and Testing Packages stallation must be completed on the Enterprise Server before building and testing packages. Application fixes include maintenance packs. To update the SYSTEM path: 1. you should install all application fixes relevant to your business. and deploy processes. identifying. Rev0 241 . Building and Testing Packages 3.NET 2003\Common7\Tools\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. change them to match these values): For the . Change the drive letter to point to Visual C++ on your Enterprise Server.NET 2003\Vc7\bin. LIB: C:\Program Files\Microsoft Visual Studio . Verify these compiler version-dependent path settings (if the paths on your system are different. Instead. Copy the LIB and INCLUDE settings from your user to your system. GA. add a semi-colon to the end of the existing system path and then append the user path information.NET C++ Compiler INCLUDE: C:\Program Files\Microsoft Visual Studio .Chapter 12.NET 2003\Vc7\lib.NET 2003\Common7\Tools. C:\Program Files\Microsoft Visual Studio . PATH: C:\Program Files\Microsoft Visual Studio . Append the path from your user variables into the path for your system variables. 5. In your system settings. create the LIB and INCLUDE settings. 7. 4. Copyright © 2008.NET 2003\Vc7\atlmfc\include. All rights reserved. Oracle.NET 2003\Vc7\include. C:\Program Files\Microsoft Visual Studio . C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\lib. 6. C:\Program Files\Microsoft Visual Studio . Do not replace the existing system path information. You must reboot the computer in order for path changes to take effect. 8. Chapter 12. 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 242 GA.Rev0 Copyright © 2008. All rights reserved. Oracle. . Oracle. Note the space used by your Central Objects tables and their indexes. Verifying Specific UBEs are Mapped Locally To verify that specific UBEs are mapped locally: 1. 2. 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. R9622. R98825C. 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. you must increase the size of your tablespaces or drop the metadata specifications tables for old packages no longer in use. You must verify that there is enough space available in your SQL Server tablespaces for this extra copy.Rev0 243 Copyright © 2008. Find each of the following UBEs and make sure each is mapped locally and is active: R9621.Chapter 12. and R98825D. Open the Object Configuration Manager (OCM). GA. 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. . All rights reserved. On the Deployment Server. Click the + icon to the left of your default project to display the project components. and click the Find icon. b. perform the following substeps: a. Click the Search tab in the right-hand pane of Object Management Workbench. Verify that there are at least 12 records with PDPKGNAME="LITE". The system displays your default project in the Project window. BUSOBJ and object directories are deleted from the Planner pathcode. . On the client. If the table is missing any of these records. Enter OMW in the Fast Path field to access the Object Management Workbench. To complete this task. Building and Testing Packages Verifying the OCM Mapping To verify the OCM mapping: 1. The F9631 table appears in the Search results window. Oracle. Log on to the Deployment Server in the Planner environment.Chapter 12. d. c. Click the Search icon next to the Search field.Rev0 Copyright © 2008. Deleting the BUSOBJ Directories You should delete all business object (BUSOBJ) directories from the Client and Deployment Server that are running the packages. these directories are deleted from the pathcode that the user is logged into to build packages. Select the Objects icon. This directory is located under the pathcode directory. f. enter your user ID in the User field. Complete the following fields: Category Search Type Search h. See JD Edwards EnterpriseOne Tools Object Management Workbench Guide. Select Object Librarian. 2. 2. Enter F9631. 244 GA. 3. Verifying the F9631 Table To verify the F9631 table: 1. Verify that the F98826 table was generated using Universal Table Browser. Verify that all OCM mappings for all environments are created. refresh the table by copying it from the Microsoft SSE database in the planner pathcode directory. g. Select Object Name. Open the F9631 table using UTB. e. All rights reserved. In Object Management Workbench. Select the Table Operations tab. Enter Planner . Click OK to copy the table. Building and Testing Packages i. Verifying the Server-Side Settings To verify the JDE. In the [BSFN BUILD] section.INI settings on the Enterprise Server: 1.900 in the Destination data source field. and then click the Copy Table icon.INI on the Enterprise Server. Configuring the Enterprise Server for Simultaneous Builds To ensure that simultaneous builds run properly on your Enterprise Server. which enables unlimited builds) Copyright © 2008. Select the F9631 table in the Object folder and click the Design button next to the Project pane. Open the JDE. All rights reserved. k. Select the F9631 table and click the left arrow next to the Search pane. m. j. Ensure that LinkFlags references the path where Release 9. Verify that the BuildArea setting in the [BSFN BUILD] section points to the PACKAGES directory on the Enterprise Server. 2.INI on the Enterprise Server.0 is installed. n. Object Management Workbench copies the table icon to the Object folder. Enter System . l. The Copy Table form appears. 1. Oracle. For example: \JDEdwards\E900\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.Rev0 245 . 2. Open the JDE.900 in the Source data source field.Chapter 12. GA. The system displays the Object Librarian Table Design screen. Note You must add yourself to the project as a Developer to access the Design function. change the SimultaneousBuilds setting to 5 or less (the default is zero. you must add a security override so that the package build process can create the metadata repository tables in Central Objects. 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. 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. add the data source owner as a system user by selecting Add and completing the fields on the System User Revisions form: • • • • 4. On Add Data Source. complete the User ID. 2. Add Data Source. Building and Testing Packages Adding a Security Override for Running Package Build If you are running with security server turned on. enter the appropriate data source owner (for example. Oracle.Rev0 Copyright © 2008. and System User fields. 3. enter the user who is going to run package build. To add a security override. you must first add a system user for the Central Objects data source owner. On Work with System Users. Data Source. and then add an override for the EnterpriseOne user who will run the package build. In P98OWSEC. DV900. 246 GA. 2. System User Data Source Password Password Verify Click OK and then Cancel and Close to return to the Work with User Security form. If no values are returned. select the form exit Add System User. 3. and select Find. Adding a security override must be done by a security administrator. All rights reserved.Chapter 12. On Work with User Security. . Select the Form exit. PY900 or PD900) in the System User field and select Find. the specified parent package must be stored under the package directory on the server. After building an update package that updates the parent package. If the parent package is not under the package directory. you must recompress the parent package. and deployment process. do not use these names: • • • CLIENT SERVER Verify the assemble and build processes completed. If no check mark appears. All rights reserved. the update package does not build. click the End icon to save the information. Building and Testing Packages Reviewing Troubleshooting Tips The following troubleshooting tips are designed to help avoid known issues with the package build. ensure that a check mark appears next to each server selected. • Verify the location of server packages.Chapter 12. When selecting servers on the Build Definition form. Oracle. • Verify setting on the package definition screen. Copyright © 2008.Rev0 247 . GA. When building an update server package. highlight the server in the grid and click Select. Review these tips when working through the process. After entering the package information on both the Assembly and Build forms. • Recompress the parent packages. assembly. This step does not occur automatically. 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. 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. Enter the package name and click Find. the package is not visible in the package list when trying to install Release 9. It is possible that a duplicate package might have been created if you copied a package. • Approve the package. conflict with a registry setting might exist.inf file to that is visible on the install screen: 1. Configure the client package. The package is set to active. After building a package. When deploying the package to a CD burner.inf file for the package that is not showing up on the install screen. To set the attributes of the package. • Copy the package. To approve the package: 1. 3. Building and Testing Packages Deployment Tips Check these items as you deploy your packages: • Deploy a package to a CD burner. If the package name is the same as listed in another package.inf files of the other package and verify that the package name listed in PackageName= is not duplicated in another package.inf file. Select the Package option.inf file to back it up. 2. • Open the package. the target machine must be created and the CD burner must be attached to this new location. . Oracle. Check the Attributes section in the package. If there are two or more package.0 from a client workstation. Complete the following steps to eliminate this problem: To configure the client package.Rev0 Copyright © 2008. All rights reserved.inf file from No Status Defined to Approved.inf file.inf file: 1. 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. Open the client package. Without this setting.Chapter 12.ini/E900/ 248 GA.inf files. 4.inf file. change it. change the Deployment Status in the [ATTRIBUTES] section of the package. 5. Select the package. Click Activate/Deactivate under Row. 2. 2. 3.inf files that have the same package name listed in the Attributes section. Open the Package Deployment application. that package will not show up on the install screen. Oracle. Copyright © 2008. If the status is not set to Approved. 5. Verify that the DeploymentStatus setting in the package.ini/E900/ FoundationBuildDate 4. Install the package again.inf is set to Approved. 6. 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. All rights reserved.Rev0 249 . GA.Chapter 12. If the registry also contains a key named FoundationBuildDate. set it to Approved and save the file. Building and Testing Packages AppBuildDate 3. update. depending on the size of the package and the number of languages used.INI on the Enterprise Server. Therefore. This task is completed on the Deployment Server. complete the server package installation procedures. if creating a package containing Japanese text.Chapter 12. If the system locale on the operating system does not match the installed language. call Global Customer Support for assistance. For example. Oracle. If the LocalCodeSet value on the local client differs from the one specified on the Enterprise Server. build a package and specify which language or languages to include in that package. the server package build fails and errors are logged in the JDE. Caution To transfer translated objects to a server. This code is specified as a parameter when building the package. To build the language package. or partial package. See Also 250 GA. Caution When building the client package with translated processing option text. It contains replicated objects that Release 9. To include language specifications in your package. It uses the relational database tables to build the form design aid text and report design aid text specifications. to a local workstation. If custom modifications or text overrides have been made at the time that a software upgrade is performed or to deploy development changes. A language package can be a full. first define the package.Rev0 Copyright © 2008. Note To move all objects. specify the language in the package definition. Building server packages that include languages other than English requires that the LocalCodeSet value of the Release 9. The package build process then uses the language preference code. the workstation must be loaded with Japanese Microsoft Windows to view the Japanese data correctly.0 client matches the LocalCodeSet value of the JDE. track the objects you changed to include them in a package.LOG on the Enterprise Server. the translated text in processing options (POTEXT) will be corrupted.0 reads at run-time. . including a specific language. Define each object you have modified for languages. All rights reserved. Building and Testing Packages Building an Alternate Language Package A package represents a copy of the central objects at a point in time. verify that the language installation is complete. This action involves the following considerations: • • Package Build Considerations Package Deployment Considerations Package Build Considerations Before beginning to build a language package. Package Deployment Considerations A translated package cannot be deployed to a workstation if the appropriate character set is not installed on that workstation. Building the package can take several hours. logged on as user JDE in DEP900. run the build using Microsoft Windows with the system locale set to the appropriate language. Chapter 12. Building and Testing Packages JD Edwards EnterpriseOne Tools Package Management Guide for more information about transferring objects to the server. Copyright © 2008. Oracle.Rev0 251 . GA. All rights reserved. and selecting prompt for values. Set the processing option entitled Business Services to a value of 1. All rights reserved.Chapter 12.Rev0 Copyright © 2008. Building and Testing Packages Assembling a Package that Contains Published Business Services To assemble a Business Services package: 1. 252 GA. . Navigate to the processing options for Package Assembly from to the Package and Deployment Tools menu by right-clicking the Package Assembly application (P9601). Oracle. 2. Rev0 253 . Oracle. See Also • • • To begin the assembly process. Building and Testing Packages Note This processing option is blank by default. GA. 3. All rights reserved. Deploying the Package to the Business Services Server in the JD Edwards EnterpriseOne Package Management Guide. Building a Package with Published Business Services in the JD Edwards EnterpriseOne Package Management Guide. Copyright © 2008. Click OK. refer to the chapter entitled Assembling Packages in the JD Edwards EnterpriseOne Package Management Guide.Chapter 12. 254 This page intentionally left blank . It also is dependent on the existence of Data Source Templates for the target environment so that OCM can be generated. All rights reserved. GA.Chapter 13.Rev0 255 . tested full package. Note This process cannot be run for a target environment if the target environment and its path code are not already defined in tables F00941 and F00942. This chapter discusses: • • • Adding Security Overrides Setting up the Database Components for the Target Environment Running the Copy Environment Application (P989400) Copyright © 2008. You can verify such existance using the Data Source Templates by Environment application P98503 on menu GH9611. you should copy the data. Copying an Environment to Another Environment Once you have completed the setup and applied fixes and modifications to your Prototype environment. The Data Source templates for all standard environments are shipped in your planner database. and related records to your Production environment using the process described in this chapter. Oracle. Central Objects. Copying an Environment to Another Environment Adding Security Overrides If you are running Copy Environment with Security Server turned on. In the Security Workbench. create the Central Objects data source for the target path code. add an override for JDE that defines the target data source (Central Objects – XX900. 256 GA. before starting your Copy Environment process in the JDEPLAN environment. In the Security Workbench. which by default sets the password value to be the same as the owner value. Central Objects – XX900. you will need to add an override for JDE for the new Central Objects Data Source for the target Path Code. XX900 with password equal to the password you set up for that owner in the database. Tip You can also do this task while signed into DEP900 on the Deployment Server. 2. . For example. Oracle.Chapter 13.Rev0 Copyright © 2008. add a system user for the owner of the Central Objects data source. On an JD Edwards EnterpriseOne administration client (also called a Web Development or "fat" client). JDE) as the data source owner. XX900. 1. All rights reserved. The easiest way to do this is to copy the source Central Objects data source and change the name and the owner to match your target path code. For example. For example. 3. version 9 is SQL Svr 2005 @SET SQL_VERSION=9 @set NEWENV=YES @set NEWPATHCODE=YES @set UPATHCODE=pd900 (substitute your path code name) @set UENV=prod (substitute your environment prefix) rem JDE_SRV=MYMACHINE or JDE_SRV=MYMACHINE\MYINSTANCE @set JDE_SRV=MACHINENAME\INSTANCE (substitute your machine name and instance) 4. Copyright © 2008. Start the cmd window and navigate to the SQL scripts directory.BAT file as shown below: rem SQL_PATH . 2.Chapter 13.Rev0 257 . Edit the ce_JDESET. For example: ce_InstallSQLDatabase. All rights reserved.directory where you want your database files @set SQL_PATH=z:\JDEdwards\MSSQL rem Version 8 is SQL Server 2000. passing in your sa user and password. 1. Navigate to the SQL scripts directory within the EnterpriseOne install location. Sign on to the enterprise server as an administrative user.bat sa MySAPwd 6. GA. you must set up the database components for the Target environment on your Enterprise Server. Verify the batch file ran correctly by checking the logs in the scripts directory. Run ce_InstallSQLDatabase. For example: z:\JDEdwards\E900\MSSQL\scripts 3.bat. Oracle. 5. Copying an Environment to Another Environment Setting up the Database Components for the Target Environment Before running the Environment Copy application. Chapter 13. Note For information on Processing Options for this application. from a previous attempt to copy to that path code). This is necessary because the copy process breaks if another process has a lock on anything within that directory. 258 GA. Oracle. you must remove it before you start the copy process. refer to Step 11 of this procedure. All rights reserved. . Copying an Environment to Another Environment Running the Copy Environment Application (P989400) Warning If the target path code directory already exists on the Deployment Server or Enterprise Server (for example.Rev0 Copyright © 2008. run the application Environment Copy (P989400). You must run the Copy Environment process on the Deployment Server. 1. You can use the Windows command: rmdir /S /Q d:\JDEdwards\e900\XX900 where you should substitute your target path code directory. From menu GH9611. Copying an Environment to Another Environment Note If you have environment definitions. All rights reserved. complete these fields: • • • • Source Environment Target Environment Source Package Target Package Note Any environment copy is dependent on the OCM for the target environment. Oracle.Chapter 13. On Environment Copy [Copy to existing environment]. you can check the radio button for Copy Environment Definitions to copy the missing records from System – 900 to Planner – 900. click Next. but which are not defined on the Deployment Server which you will be using in this process. you can enable the checkbox for Generate OCM in System / Server Map to create data sources and OCM for your target environment before doing the copies. or path code definitions that exist in your System – 900 data source.Copy Environment / Packages. On P989400 . GA. 2. data source definitions.Rev0 259 . If the OCM does not currently exist. Copyright © 2008. 3. Oracle. • • 4. The Rename Metadata Repository option assumes that you have used system or database utilities to copy all the tables in Central Objects to the new database / owner / library. All rights reserved. You can override the default copy flags by clicking on the Advanced Copy form exit which displays this screen: 260 GA. Copying an Environment to Another Environment Note The Copy Metadata Repository and Rename Metadata Repository options are dependent on certain components having been copied before they are run: • The package definition records for the target package must exist before the Copy Metadata Repository or Rename Metadata Repository runs. The Configure Package Manifest option (which is only selectable by running the following step in this procedure) is dependent on both local and enterprise package repositories having been created. because that UBE (which runs before the Copy Metadata Repository or Rename Metadata Repository) also copies the package records and the package. .inf. It is recommended that you allow the Copy Environment process to copy the path code and package on the Deployment Server.Chapter 13. and also depends on the target package definition records.Rev0 Copyright © 2008. Central Objects and Versions for the target environment. You are returned to the preceding screen where all the default copy options are unprotected. If the data source definitions and OCM for the target environment do not exist. On Advanced Options Environment / Path Codes. It assumes that the data will be on the same server as the corresponding data sources for the source Copyright © 2008. if you used export / import for Oracle in order to make your own copies of Central Objects.Chapter 13. allowing you to pick and choose which components the process will copy.Rev0 261 . 6. This non-default method is only recommended if you have provided for the copies in a non-standard way. GA. the application generates data source definitions for Business Data. Copying an Environment to Another Environment 5. Control Tables. click the Override copy options button. Oracle. click Next. if you want to override the default flags. After you have set the Environment Copy options as described in Step 3. All rights reserved. For example. Copying an Environment to Another Environment environment. the next screen Copy Environments . . Following the series of Data Source Revisions screens. All rights reserved. Below is a sample screen for Business Data: 7.[ Machines].Rev0 Copyright © 2008. but you can change this on the Data Source Revisions screens.Chapter 13. Oracle. 262 GA. 9. highlight the desired machine from the node that lists Available Enterprise Servers and click the large right arrow to add the machine to the node that lists Selected Enterprise Servers. Oracle. 8.[ Machines]. Note The process submits a UBE to each selected server. On Copy Environments .Chapter 13. The source path code and package must exist on the selected servers. Copyright © 2008.Rev0 263 . GA. All rights reserved. Click Next. Copying an Environment to Another Environment This screen shows a list of enterprise servers that allows you to select to which enterprise servers you want to copy the package / path codes. 264 GA. PD900.900. which can be viewed or revised using the Data Source Templates By Environment application on GH9611. a business function runs that generates data sources and OCM in Planner – 900 and copies them up to System . The data source template records for the standard environments (DV900. which is submitted to the Enterprise Server. Oracle. All UBEs run locally except for the Enterprise Server Path Code copy. If you selected Generate OCM.Rev0 Copyright © 2008. Copying an Environment to Another Environment This screen shows lists all the planned function of the processes of running the business functions and UBEs when you click the End button.Chapter 13. PY900) are shipped with the Deployment Server install. PS900. . All rights reserved. This business function uses the template data source records in F98511. Chapter 13. Configure Manifest Runs in UBE R9894005 XJDE0002 to configure the manifest (F98770PD900FA) in Central Objects and in the target package on the Deployment Server. The local repository is renamed by R9894005 XJDE0002. Oracle. This UBE also configures the spec. as the local package directory was copied by R9800942. Runs R9672 XJDE0001. Runs R98403 XJDE0019. Checkout Records ESU History Path Code Directory on Enterprise Server Copy Metadata Repository Runs R989861 XJDE0001. GA. This UBE also copies the Package Header / Detail records. To view the history. The application writes history records into F984052. All rights reserved. Submits R9894003 XJDE0001 to the server. Runs R9894005 XJDE0001 to copy the metadata repository within Central Objects. run the Table Conversion / Merge Log (P984052) on menu GH9611 by filtering on conversion type 95.ini in the target package on the Deployment Server. Runs R9800942. This screen shows a sample conversion log: Copyright © 2008.Rev0 265 . Copying an Environment to Another Environment This table lists details of the UBEs that generate the Path Code Data: Path Code Data Business Data Control Tables Central Objects and Versions Deployment Server Directory UBE Details Runs R98403 XJDE0021. Runs R98403 XJDE0022. Warning OEE Local Database Consideration. This must be done manually because it is not possible for the R9894005 UBE to delete this file as the database keeps a lock on it until the UBE ends.DBF Before deploying the package. When copying a package using local Oracle database. if copying PY900FULL to PD900FULL. After the process completes successfully. For example. you must manually delete the source package DBF file (in this example.Chapter 13. you must deploy the target server package to make it available on the Enterprise Server(s).DBF files in the target package spec directory. 266 GA. PY900FULL. All rights reserved.DBF PD900\package\PD900FULL\spec\PY900FULL. Copying an Environment to Another Environment 10. Oracle. these two DBF files would exist: PD900\package\PD900FULL\spec\PD900FUL. there are additional . .DBF).Rev0 Copyright © 2008. Copying an Environment to Another Environment 11. Oracle. In order to activate the Advanced Copy button.Chapter 13. To access the processing options of the Copy Environment Application (P989400). from menu GH9611 right click on the application and select Prompt for Values. GA. enter a value of Y in this field: Advanced Copy Options Y/N Click OK to return to the Environment Copy application and note that a new section with advanced options is available: Directory copies Copyright © 2008. All rights reserved.Rev0 267 . 12. Chapter 13. Copying an Environment to Another Environment For example. if you choose to do all the database copies using database / system tools.Rev0 Copyright © 2008. . All rights reserved. you would set the copy options like this: 268 GA. Oracle. Rev0 269 . Oracle. Copying an Environment to Another Environment Copyright © 2008. GA.Chapter 13. All rights reserved. 270 This page intentionally left blank . Select the Release Level and enter your JD Edwards EnterpriseOne Serial Number. you need to do this if your deployment period or expiration date has expired or if you add modules to the software. 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. Run the Reset EnterpriseOne Security program (R98SRV). you must revalidate both the Deployment Server and workstations. On either your Deployment Server or Workstation. On Reset Oracle Security. Oracle. sign on to JD Edwards EnterpriseOne.Rev0 271 . Because a number above 5000 will cause JD Edwards EnterpriseOne to run slowly in some instances. For example.exe. run the SPC generator program called SPCSelfService. Click OK. 9. 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. Copyright © 2008. click Reset Server Security. 2. it is best to limit the number of licenses to 5000. 4. To reset the licenses on the Deployment Server. 7. The software notifies you seven days before your expiration date. 3. From Customer Connection. select the checkbox next to "ALL" in the Licensed Suites section. GA. 6. which is associated with SAR # 7549901. Enter any number between 1 and 99999 for the number of licenses. If the Release Level is 3 or 4.Chapter 14. download the update called "SPC". All rights reserved. 8. 5. on either a Windows client or the Deployment Server (either one can run the SPC generator program). Installation Utilities 10. enter the Number of Licenses. You added modules to JD Edwards EnterpriseOne.Chapter 14. 6. 3. 13. from the Form menu. In JD Edwards EnterpriseOne. select Oracle Licensing Security. . however. 5. An administrator can grant non-privileged users disk and registry access. On Reset Oracle Security. 2. 14. Click OK. Close the SPCSelfService. click Reset Client Security. From the Advanced Operations menu (GH9611). On Oracle Security Setup. Oracle. The JD Edwards EnterpriseOne are reset. they do need disk and registry access. 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. on Reset Security. Click OK to reset the workstation. All rights reserved. select Get Authorization. The authorization code appears in the Authorization Code field. 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 272 GA. Note the SPC codes. Revalidating Workstations You might need to revalidate workstations for either of the following reasons: • • The expiration date has passed. 4. Select any of the environments available to the workstation user.Rev0 Copyright © 2008. To revalidate a workstation: 1.exe program. 11. Exit the R98SRV application. Expiration Date (1/1/2899). Log on to the workstation with the appropriate user ID and password. and SPC codes that were displayed by the SPC generator program. 12. log. This procedure grants access to the jdeinst. 8. 4. and select Full Control. 2. Click Add. 7. 9. Click the Security tab. On Add Users and Groups.log file and the software installation directory. 3. 5. Permission to access the software installation directory is granted to the user. right-click the file and select Properties. 3. All rights reserved. In Microsoft Windows Explorer. Click Permissions. 2.log file is granted to the user. 4. Enable the setting to Replace Permissions on Subdirectories. Click OK. 7. Click the Security tab. who now can install the software to this directory. In Microsoft Windows Explorer. 6. Click the pull-down menu in the Type of Access field. This directory will become the installation directory for the software. 6. To grant access to the jdeinst. GA. Click the pull-down menu in the Type of Access field. 8. Create an empty directory named e900 on a drive. Click Permissions.Rev0 273 . Installation Utilities Granting Non-Privileged Access to Disk for Microsoft Windows This procedure can be used only by the administrator of the domain. 5. double-click the user to be added. Permission to access the jdeinst. double-click the user to be added. Click Add.Chapter 14. Create an empty file in the c:\ root directory named jdeinst. Oracle. right-click the directory and select Properties. and select Full Control. Granting Nonprivileged Access to the Microsoft Windows Copyright © 2008.log file: 1. Granting Access to the Software Installation Directory To grant access to the software installation directory: 1. On Add Users and Groups. Click OK. enter regedt32. 9. c. On the Menu bar.Chapter 14. 6. Run regedt32. Click OK. On the Add Users and Groups box. 4. b. Expand the node HKEY_LOCAL_MACHINE on the Local Machine node. 5. 8. 10. 7. click Edit and then Add Key. In the Key Name field. To grant nonprivileged access to the Microsoft Windows registry: 1. select Replace Permissions. All rights reserved. Oracle. and click Run. Installation Utilities Registry This procedure can be used only by the administrator of the domain. Click OK. . 2.exe as follows: a. double-click the user to be added. 12. This procedure grants access to HKEY_LOCAL_MACHINE\Software\JDEdwards. 11. Expand the Software node. 3. click Add. click Security. Click the pull-down menu in the Type of Access field and select Full Control. enter JDEdwards (case-sensitive as shown). Permission to access the registry is now granted to the user. On Existing Subkeys. On the Menu bar. Click OK. Click the Microsoft Windows Start button. 274 GA. Leave the Class field blank.Rev0 Copyright © 2008. and then select Permissions. In the Open field. On the Registry Key Permissions box. Chapter 15.PD900 S (SQL Server) SQL Server Instance Copyright © 2008.PD900 SQL Server Central Objects . You must use SQL Server drivers to create ODBC data sources whose names must exactly match each datasource type entry in the corresponding data source.Rev0 275 . All rights reserved. add a 32-bit ODBC data source that uses the SQL Server driver. GA. depending on the configuration of the Enterprise Server and databases. Working with Third-Party ODBC Data Source Creation This chapter discusses. JD Edwards EnterpriseOne automatically creates all associated 32-bit open database connectivity (ODBC) data source by default. For example: Data Source Data Source Type ODBC Data Source Name Name and Type of Associated 32-bit ODBC Data Source Central Objects . • • • Understanding Third-Party ODBC Data Source Creation ODBC Data Sources for a Microsoft Windows Enterprise Server with SQL Databases Creating Third-Party Data Sources for SQL Server Understanding Third-Party ODBC Data Source Creation For each non-Oracle data source that you set up in the plan. You might need to create associated ODBC Data Sources for the data sources. if the data source type for Central Objects is S (SQL Server). For example. Oracle. Chapter 15.CRP Business Data .DV900 Control Tables . below.TEST Versions . Working with Third-Party ODBC Data Source Creation ODBC Data Sources for a Microsoft Windows Enterprise Server with SQL Databases This table lists the ODBC data sources for a Microsoft Windows Enterprise Server running a SQL Server database. To create third-party data sources for SQL Server: 276 GA.PY900 SQL Database JDE_PS900 JDE_PRIST900 JDE_PRIST900 JDE_PS900 JDE_PD900 JDE_PRODUCTION JDE_PRODUCTION JDE_PD900 JDE_DV900 JDE_DEV JDE_DEV JDE_DV900 JDE_PY900 JDE_CRP JDE_CRP JDE_PY900 Enterprise Server Considerations. if the Enterprise Server is Microsoft Windows. start with 1. All rights reserved.PS900 Control Tables .PD900 Development/Test Central Objects .PY900 Control Tables . JD Edwards EnterpriseOne creates ODBC data sources on the Enterprise Server for SQL. Oracle.PROD Versions .PD900 Control Tables .Prod Business Data .DV900 Prototype Central Objects .PS900 Business Data . you must create data sources for each server that the workstation or Deployment Server will access. .Test Business Data .CRP Versions .PS900 Production Central Objects . Creating Third-Party Data Sources for SQL Server For each workstation or Deployment Server.Rev0 Copyright © 2008. Note If you initiated ODBC data source creation from the Installation Planner's Create New Data Source form.PS900 Versions . Environment Pristine Data Source Central Objects . In addition to adding these ODBC drivers on the Deployment Server. On Create New Data Source.70. All rights reserved. Copyright © 2008.Rev0 277 . Oracle. Working with Third-Party ODBC Data Source Creation 1.23 or higher.Chapter 15. Caution The SQL Server ODBC driver version must be 3. Using a lower driver level can corrupt your database. GA. choose SQL Server and then click Finish.06. Click Next. which is titled Work with Data Sources. Enter the name of the server to which you want to connect.Rev0 Copyright © 2008. 278 GA. 3.Chapter 15. . This is a required field. All rights reserved. The name must match the server name in your Hosts file or in the DHCP table. Oracle. Working with Third-Party ODBC Data Source Creation 2. On Create a New Data Source to SQL Server. complete the following fields: Name Description Server Enter the name of the data source that you assigned to the Database Name field on the Data Source Setup form. Enter a description of the data source. Oracle. 5. 7.PY900 Control Tables . turn on the With SQL Server authentication using a login ID and password entered by the user option. All rights reserved. On Microsoft SQL Server DSN Configuration.PY900 Versions .900 Data Dictionary .900 machinename . GA. See the chart below to determine which databases the data sources use.Rev0 279 . the logon might be JDE with password JDE.CRP JDE_CRP JDE_PY900 Database Name PS900 Copyright © 2008. Working with Third-Party ODBC Data Source Creation 4.Chapter 15. Data Sources System . Turn on Connect to SQL Server to obtain default settings for the additional configuration options.900 Object Librarian . Delete any entry that appears in the Login ID or Password fields and then type logon and password information.900 Server Map Central Objects . Click Next. 6. For example. Caution Specify the database for each datasource. PS900 Versions . Oracle.Chapter 15.DV900 Versions .PS900 Central Objects .CRP Central Objects .PROD Central Objects . type JDE_PRIST900.Rev0 Copyright © 2008.PS900 Business Data . On Create a New Data Source to SQL Server.PD900 Versions . All rights reserved. Working with Third-Party ODBC Data Source Creation Data Sources Business Data . For example.Test Business Data . type the default database name in the Change the default database to field. .PD900 Control Tables . Ensure that the Create temporary stored procedures for prepared SQL statements 280 GA. 9.PS900 Control Tables .DV900 Control Tables .Prod Business Data .TEST Database Name JDE_PS900 JDE_PRIST900 JDE_PD900 JDE_PRODUCTION JDE_DV900 JDE_DEV 8. and then click Finish. All rights reserved. 11. 10. Click Next. Oracle.Rev0 281 . verify that the Perform translation for character data option is not turned on. On Create a New Data Source to SQL Server. Working with Third-Party ODBC Data Source Creation and drop the stored procedures option is not turned on. GA. Copyright © 2008.Chapter 15. click OK. Note If you initiated ODBC data source creation from the Control Panel.Chapter 15. 13. click Test Data Source.Rev0 Copyright © 2008. the system returns to the main screen. . the system returns to the Installation Planner process. and then click OK. Note If you initiated ODBC data source creation from Installation Planner's Create New Data Source form. 282 GA. Oracle. To create the data source. Working with Third-Party ODBC Data Source Creation 12. All rights reserved. On ODBC Microsoft SQL Server Setup. GA. it may be because the F0010 table is empty. Oracle.log. PORTTEST may fail if replication. 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.Chapter 16. this is a normal condition in Pristine and Production environments. check the setup of those services for incorrect parameters. Additionally. or transaction processing have been installed incorrectly.log or JDE_xxxxxx. such as JDE. 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.Rev0 283 . if PORTTEST reports warnings that indicate data dictionary or company constants are invalid. Please have the answers to these questions as well as copies of error messages. All rights reserved. security server. and any error logs. your Enterprise Server xxxx. use this checklist to diagnose the problem before calling Global Customer Support. If problems occur after the installation of one or more of these services. As is true with the full JD Edwards EnterpriseOne installation. Oracle.INI parameters set properly? [Network Queue Settings] Default Printer OUTQ=your_printer [UBE] Yes/No Note If you use PostScript. 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. All rights reserved.Chapter 16. 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] E900=valid_path_for_your_install Communications Issues Are you using DHCP? Yes/No 284 GA.INI located in the correct directory? Is your JDE.Rev0 Copyright © 2008.INI located in the correct IIS Directory? Does your JDE.INI Issues Is your JDE. 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.INI have the correct permissions? Are these JDE. . Chapter 16.Rev0 285 . If you answered yes to all the Copyright © 2008.0 environment? Remember that the environment name is case sensitive.0 account? Remember that the user name is case sensitive. 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. Does JDENET start and stop properly? After rebooting. your batch application might not run. Oracle. All rights reserved. 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. Is the password valid for the given Release 9. Troubleshooting If not. 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 9.0 account? Does the environment name match a valid Release 9. do the services start and stop properly? Can you kill the runaway services with Visual C++ debug? If your printer is on a network. 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. GA. 0 OCX files are not registered. Note any success or failure messages that appear in the command window. Right-click on regjdeocx. On the Deployment Server. or load your own data. It includes all fixes for Release 9. Resolving Data Errors If you are receiving data warnings against the F0010 table in the Pristine or Production environments.bat. load demo data. This is how it is delivered. submit a batch application now. you must edit and run the regjdeocx. Review the SpecialInstrs. This log helps Global Customer Support diagnose the exact problem. the table might be empty. SAR 6552762. If your batch application does not run correctly. Special Instructions for OCX Registration In some circumstances. All rights reserved. Run the registration batch file at any time if you encounter either of these issues.bat file to copy certain table records from the ESU database to the Planner databases on the Deployment server. 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.Chapter 16. turn on error logging and resubmit the batch. Run the batch file specialInstrs. browse to this directory: \JDEdwards\900\Planner\Package\PHxxx\Scripts 2. On the Deployment server. 2. To register the OCX files. Oracle. Troubleshooting questions. Release 9.Rev0 Copyright © 2008. 3.0 installation and upgrade process. 6367858. 286 GA. You can ignore these warnings.bat file: 1. Click on the RegisterOCX directory. This section describes: • • Special Instructions for All Special Instructions for OCX Registration Special Instructions for All You must run the specialInstrs.log file that is created in the same directory for details. . 1.bat and select Edit. 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. drill down into the directory that was created when you expanded this Planner Update (PHxxx). Copyright © 2008.Rev0 287 . From the Microsoft SQL Query Analyzer. and then from each delivered database which could include: • • • • • • • • JDE_CRP JDE_DEVELOPMENT DV900 PS900 PD900 JDE_PRIST900 JDE_PRODUCTION PY900 To troubleshoot database connection errors that are reported by JD Edwards EnterpriseOne: 1.Chapter 16. Open and navigate to the folder contain the orphan user script. If there are database connections problems. click File. 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. 2. Oracle. Access Microsoft SQL Query Analyzer and login to the JD Edwards EnterpriseOne database as the JDE user. Click the Open button. GA. Typically the file is found in this location: c:\JDEdwards\900\mssql 3. 6. Save the file and exit Notepad. Select this script: orphan user with cursor. All rights reserved. 5.sql 4.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. an error message appears. Change the OCXPATH variable to the correct path for your Deployment Server. Run the regjdeocx. Troubleshooting 4. You must run the following provided script to correct the condition. 288 GA. 6.Chapter 16. Oracle. Click the Execute Query button. Set the database to master. . Troubleshooting 5. All rights reserved.Rev0 Copyright © 2008. Chapter 17. All rights reserved. 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.Rev0 289 . GA. Oracle. 0.0 application that runs on the Deployment Server. if you choose to replicate the control tables. you might need to modify some data source information to reflect your system-specific configuration. review the processing options for the Installation Planner to make sure that they are set correctly for replication.Rev0 Copyright © 2008. you are asked to define the control tables data source. To use replication for Release 9.0 for a remote location. Creating a Remote Installation Plan Understanding Remote Installation Plans Installation Planner is a Release 9. .0. Before you begin. The information that you provide on the Installation Planner forms. However. data dictionary. Only data sources that are referenced in the replication forms appear when you create a remote plan. You can use Installation Workbench to copy the system. 290 GA. All rights reserved. This section includes information for installing an alternate language. constant and master tables to your remote location. you are prompted for different data source information. Note Data Source Considerations. determines the information that the system displays on the remaining forms. when you run Installation Planner. 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. control.9. Ongoing replication of the data in these sources must be implemented using third-party software. JD Edwards EnterpriseOne no longer has a built-in replication engine. decide what your replication strategy is for Release 9. For example. To set up Release 9. Complete the tasks in this section after you create and complete a basic installation plan.Chapter 17. and are ready to add the remote locations to the configuration. JD Edwards EnterpriseOne provides configured data sources.0. It is a system administration tool that guides through the process of configuring the machines on which your company will run Release 9. Oracle. such as database type and Enterprise Server type. Depending on which tables you want to replicate. create a plan that includes remote locations. as of release 8. 0 as user JDE with the database password for user JDE. The Installation Planner form appears. From the System Installation Tools menu (GH961).Chapter 17. 2. 4. Oracle. On Work with Installation Plans. All rights reserved. Copyright © 2008. click Add. Access the planner environment (JDEPLAN). Log on to Release 9.Rev0 291 . 3. Creating a Remote Installation Plan Starting Installation Planner To start Installation Planner: 1. GA. click Custom Installation Plan. 292 GA. Enter the description of your remote plan. Select 10 as the status of your remote plan. Oracle. All rights reserved. . Click OK. 2. Select Install.Chapter 17.Rev0 Copyright © 2008. Verify that the release number is E900. complete these fields: Name Description Status Install Type To Release Enter the name of your remote plan. On Installation Planner. Creating a Remote Installation Plan Entering Information in Installation Planner To enter information in Installation Planner: 1. complete these fields: Location Description Location Code Enter the location to which this plan applies. Oracle. The location could be a city. On Location Revisions. For example. In that case. For a remote location. GA. The Deployment Server Revisions form appears. Click OK. All rights reserved. and the business data data source would be named Business Data . Texas. you might use DAL if the location were Dallas. Creating a Remote Installation Plan Entering Plan Location Information To enter plan location information: 1. Enter the parent location to which this remote location is attached. enter a 3-character alphanumeric identification code. and a suffix is attached for replicated data sources.Chapter 17. or a division of a company.Rev0 293 . Copyright © 2008. Parent Location 2. Enter a description of the location name. company headquarters.CRPDAL. the prototype environment would be named DALPY900. This 3-character code is used as a prefix for the environments of the remote location. For most situations. Enter the Release 9. Oracle. This section discusses: • • Entering Deployment Server Information Concluding Deployment Server Setup Entering Deployment Server Information To enter Deployment Server information: 1. All rights reserved. You are given the option to enter a new Deployment Server or choose an existing one. Enter a description of the machine name. 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. or use the visual assist button to choose one from the list. For example. click OK to add a Deployment Server. This name includes the location with which this Deployment Server is associated. At the Installation Plannerprompt asking if you want to enter new Deployment Server information. complete the information for the Deployment Server.Chapter 17. have a tiered Deployment Server for the remote location. On Deployment Server Revisions. Creating a Remote Installation Plan Specifying a Deployment Server Once a plan location is specified.0 release number that you are installing. and whether or not it is the primary server. E900 is the current re- Release 294 GA. . 2.Rev0 Copyright © 2008. complete these fields: Primary Deployment Server Server Share Path Enter the hierarchy of the servers. The default for primary user is JDE. 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. click the stop sign icon in the bottom right-hand corner of the form. For example. For more information about the error. Enter the server share path where you installed Release 9. for Release 9. GA. Click OK. Creating a Remote Installation Plan Host Type Location Primary User lease. a stop sign symbol appears next to the tab name. Displays the default location chosen for this plan. Tip If you enter invalid information into a tab field. 4. On the Deployment tab.0 on your Deployment Server. Copyright © 2008.Chapter 17. All rights reserved. Oracle.Rev0 295 . Make sure that this path is specific to your version of the release. Displays the default value of 50 to indicate that the server type is an Intel NT. such as Deployment Server. 3.0. the path ends with \E900. Enter the user to whom email is sent when a package is deployed. Specifying an Enterprise Server Once the Deployment Server has been specified. • To continue with Installation Planner setup.Chapter 17. Continue with Entering HTML Web Server Information. click No. • To add another Deployment Server. • To skip the Enterprise Server setup and continue with remote Installation Planner. Continue with Specifying a Deployment Server . click Yes. 2. • To add an Enterprise Server. 296 GA. Installation Planner prompts you to decide if you want to add another Deployment Server. click OK. All rights reserved.0. . Oracle. 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. Continue with the next step.Rev0 Copyright © 2008. Installation Planner prompts you to decide if want to add an Enterprise Server. Note Add an Enterprise Server if you are using replication in Release 9. Repeat Specifying a Deployment Server . click Skip. Creating a Remote Installation Plan Concluding Deployment Server Setup To conclude the Deployment Server setup: 1. 6015. Enter the name of your primary Enterprise Server. use the cluster name. Value is S for SQL Server . The name is case sensitive. which is supplied the JDE. not the machine name. such as Intel NT . Creating a Remote Installation Plan 1. Enter the user to whom email is sent when a package is deployed.0 will run and be shared by both nodes. On the Enterprise tab. Enter the default location chosen for this plan. Click the visual assist button and choose the type of Enterprise Server that you are adding to the plan. Enter the release number to which this plan applies. such as E900. Logical Machine Name Database Type Copyright © 2008.Chapter 17. All rights reserved.INI. GA. Description Release Host Type Location Primary User 2. Change the port number for this Enterprise Server to a unique value. Enter the type of database that you want to use for data sources on the Enterprise Server. The default for primary user is JDE. complete these fields: Port Number Displays the default value for this field. One copy of Release 9.0. complete or verify these fields: Machine Usage Machine Name Displays the default value 20 to indicate that this is an Enterprise Server. Enter a description of the machine. Caution When using cluster software. Use the cluster name as the server name when installing Release 9. Displays the system-supplied default value when you enter the host type. Oracle. for example.Rev0 297 . or use the visual assist button to choose one from the list. On Enterprise Server Revisions. Using the visual assist button. enter the data source information for the Enterprise Server you will use in this plan.0. for release 9. choose the name of the Deployment Server to which this Enterprise Server is attached. click OK. this path ends with \E900.Rev0 Copyright © 2008. • To accept Release 9.0 asks whether to enter custom data sources or take the default data sources for the Enterprise Server you just added. Skip to Verifying Custom Server Map Source Information . click Take Defaults. You may need to add the drive x: to the path. This option limits your customization choices. Deployment Server Name 3. The system provides a default value for this field. Proceed to Entering Shared Data Source Information. Creating a Remote Installation Plan Server Map Data Source Installation Path Displays the system-supplied default value when you enter the host type. Entering Enterprise Server Data Source Information After specifying Enterprise Server information. A message box appears to enable you to specify whether you want to enter custom data sources or take the default data sources. . but you can change it. All rights reserved. Oracle. Enter the installation directory path where you want to install Release 9.Chapter 17. This section discusses: • • • Specifying Custom or Default Data Source Information Verifying Custom Server Map Source Information Adding Another Enterprise Server Specifying Custom or Default Data Source Information Release 9. Choose one of the following options: • To enter custom data sources.0 default data sources.0 on your Enterprise Server. For example. Verifying Custom Server Map Source Information To verify custom information for the Server Map data source: 298 GA. Make sure that this path is specific to your version of the release. Click OK. On Data Source Revisions. starting with Entering Enterprise Server Information . click Yes.Chapter 17. GA. 2. However. Repeat processes.Rev0 299 . verify your Server Map data source information. • To continue with Installation Planner setup. Oracle. JD Edwards EnterpriseOne supplies configured data sources. Tip Data Source Considerations. Creating a Remote Installation Plan 1. you might need to modify some data source information to reflect your system-specific configuration. when you run Installation Planner. Adding Another Enterprise Server To add another Enterprise Server. All rights reserved. The Machine/Server Types form appears. Click OK. select one of these options: • To add another Enterprise Server. Copyright © 2008. click No. Functionally. Oracle. 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. Creating a Remote Installation Plan Entering HTML Web Server Information Note For Release 9.0. 300 GA. On HTML Application Server. To enter HTML Web Server information: 1. click OK to define a new HTML Server. 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. these terms are all synonymous. .Rev0 Copyright © 2008. this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software.Chapter 17. or click Select to choose from a list of existing HTML Servers. All rights reserved. However. GA. Copyright © 2008. All rights reserved.Rev0 301 .Chapter 17. from which you can make your selection. you are presented with the Machine Search table. Oracle. Creating a Remote Installation Plan If you choose Select. complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form. On the HTML Application Server dialog. The name is case sensitive and must not exceed 10 characters. 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. This is the port number the HTML Web Server is listening to. . Valid values are http or https. Creating a Remote Installation Plan 2.Chapter 17. For example: www. 4. Enter the name of your HTML Web Server. The user to whom an email is sent when a package is deployed. On HTML Server Revisions. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). The default value of 50 specifies the server type as Intel NT. Oracle. or click Select to select an existing HTML Web Server. Protocol Server URL HTTP Port 302 GA. This is the protocol used by the HTML Web Server.INI. This is the Domain Name System (DNS) host name of the HTML Web Server. Enter a description of the HTML Web Server machine. The location chosen for this plan appears in this field by default. the web shortcut generated points to the "Primary" HTML Web Server. Select the correct server type.com.Rev0 Copyright © 2008. On the HTML tab. Enter E900 to indicate the release number that you are installing. 3. The default for primary user is listed in the JDE. click OK to continue entering HTML Web Server information. All rights reserved.oracle. and also the platform and application server on which your HTML Web Server is running. Enter the installation directory path to which you are installing Release 9. the redirector functionality cannot be used. the value is 6015.0.0 on your HTML Web Server. Values are either a reserved value or an explicit servlet name. Defines how shortcuts to a web form are generated by the system code. In this Servlet case. 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. GA. All rights reserved. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. you can choose to implement a HTML Web Server using a different port number. The value is dependent on the release of JD Edwards EnterpriseOne.Chapter 17. refer to the applicable platform. For HTTPS. Click OK. Oracle. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. JDENET Listen Port Default Login Installation Path Copyright © 2008. You should not use it unless you have a direct need. the path ends with E1HTMLServer. click Yes and repeat steps 1 through 4 to define another HTML Web Server. or its administrator. the typical port number is 443. you must obtain this value from the HTML Web Server machine itself. 6. 5. Otherwise. Make sure this is specific to your version of the release. Explicit The user can specify an explicit servlet name in this field. Usage of Explicit servlet name is for backward compatibility only.and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide.Rev0 303 . This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths. For Release 9. Redirector The URL generated will point to redirector in the Primary HTML Web Server. Creating a Remote Installation Plan For HTTP.0 on Oracle Applications Servers. the typical port number is 80. To add another HTML Web Server. However. For JD Edwards EnterpriseOne Release 9. • Select Click this button to select an existing Data Server. Creating a Remote Installation Plan Entering Data Server Information To enter Data Server information: 1.Rev0 Copyright © 2008. On Data Server. . click OK to continue entering unique Data Server information. All rights reserved. 304 GA. Continue the Installation Planner with the environment selection in step 6. select one of these options: • OK If your database resides on a separate server. Oracle.Chapter 17. • Skip Click this button if you do not want to define a Data Server . for example. Valid values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client . Enter the Release 9. 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. 4. On Data Server Revisions.Chapter 17. The name must not exceed 10 characters. complete these field: Data Source Type Select the type of data source. E900. Value is S for SQL Server . On the Data tab. Select the type of Data Server that you are adding to the plan. Oracle.0 release number you are installing. Click OK.NT 90 Client . Enter the user to whom an email is sent once a package is deployed. The default for primary user is JDE. Enter the name of your Data Server. Enter a description of the machine. Location Primary User 3. Copyright © 2008.Rev0 305 .Win NT Displays the location chosen for this plan appears in this field by default. All rights reserved. GA. Creating a Remote Installation Plan 2. Entering Shared Data Source Information To enter or confirm information for data sources that are shared across all of your environments. Repeat the procedure in step 2 of this task. click Take Defaults and continue with the task entitled: Setting Up Environments . On Data Source. Creating a Remote Installation Plan 5. 7.0 data sources. . Click OK to continue entering unique shared data source information. Verifying the Data Dictionary Data Source To verify the data source for Data Dictionary: 306 GA. • Click Yes to add another Data Server. 6. A message box appears to enable you to add another Data Server. • Click No to continue with Installation Planner setup. All rights reserved. or click Take Defaults to select the default data for the shared data sources. you are prompted to enter shared data source information for the specific environment that you previously selected to install. On Location. Oracle.Rev0 Copyright © 2008.Chapter 17. Choose one of the following options: • To use the Release 9. select Yes to add another location or No to continue with Installation Planner. 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. This option limits your customization choices. Verify the data source information. • Click OK to enter the data sources. On Data Source Revisions. Click OK. 2. All rights reserved.Rev0 307 . GA. verify the accuracy of the Data Dictionary data source.Chapter 17. Verifying the Object Librarian Data Source To verify the data source for Object Librarian: Copyright © 2008. Oracle. Creating a Remote Installation Plan 1. . Verifying the System Data Source To verify the data source for System: 308 GA. Click OK. Creating a Remote Installation Plan 1.Rev0 Copyright © 2008. Oracle. 2. All rights reserved. verify the accuracy of the Object Librarian data source.Chapter 17. On Data Source Revisions. the Installation Planner displays a customization form for each parameter that you turn off. Creating a Remote Installation Plan 1.0 configures your system using values for typical environments. Depending on the options chosen when you set up your plan. 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.0 displays one or more of the following parameters. All rights reserved. The Environment Selection screen appears. Click OK. 2. Release 9. verify the accuracy of the settings for the System data source. 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. As you move through the plan. On Data Source Revisions.Chapter 17. GA. Oracle. Copyright © 2008. Release 9.Rev0 309 . or click Copy to copy the settings of an existing environment. Oracle. On Environment Selection. Note If you checked the default option for all parameters. Use the following tasks to customize each of the parameters listed above. . Click Add to add a new environment.Rev0 Copyright © 2008. Creating a Remote Installation Plan 1. 2. All rights reserved. Note The parameters that display might vary depending on which options you selected at the beginning of the planning process. Enter the environment information on the screen and click Next.Chapter 17. skip to the next task. Continue with the following relevant tasks: • Selecting an Environment Adding a Custom Environment to add a custom environment: 1. clear the options for those parameters that you want to customize. Installation Planner displays customization forms only for those parameters for which were turned off the default options. 3. Skip the tasks for those parameters that were left turned on. Click OK. 2. 310 GA. Rev0 311 . Creating a Remote Installation Plan 3. Replicating Information to Remote Locations The options on this form determine whether the software will configure data sources and mappings for the remote location. Selecting an Environment The Select Environment form appears. To select an environment: On Select Environments. This screen appears after the following tasks are completed. Environments prefixed with J are required for the HTML Web Server. 4. Oracle. All rights reserved. GA. To replicate information to remote locations: Copyright © 2008. or create a pathcode and click Next. To set up multiple environments. Select share.Chapter 17. choose and define them one at a time. Enter pathcode information on the screen and click Next. double-click the environment that you want to define. Ongoing replication must be implemented using third-party software. Rev0 Copyright © 2008. 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 master tables. Select this option to configure the master tables for replication. Clear the option if you do not want to replicate the constant tables. Replicate Constant Tables Replicate Master Tables 2. . All rights reserved. Select the Data Load tab.Chapter 17. Creating a Remote Installation Plan 1. Select this option to configure the constant tables for replication. 312 GA. Oracle. Clear the option if you do not want to replicate the control tables. On Control/System Replication. Oracle. GA. 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. Select this option to copy the master tables automatically from the base to the remote locations. constant tables. Copyright © 2008. and master tables. All rights reserved. Clear the option if you do not want to copy the constant tables automatically. click the Edit or Search buttons next to their respective versions. Load Constant Tables Load Master Tables Note To edit or change the versions of the R98403 program that copy the control tables. Note If you have defined multiple 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 master tables automatically.Rev0 313 . the system will prompt you to complete sets of the Replication Setup and Data Load screens for each location. Click OK.Chapter 17. Creating a Remote Installation Plan 3. 4. On the Data Load tab. 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. All rights reserved. click OK. This option limits your customization choices. and continue with Verifying the Data Source for Control Tables.Rev0 Copyright © 2008. . and continue with Select Another Environment . click Take Defaults. To accept the Release 9.Chapter 17. Creating a Remote Installation Plan Setting Up Data Sources for Environment After specifying which tables to replicate. Oracle.0 default data sources. Setting up the Data Source for Business Data To set up the Business Data data source: 314 GA. Choose one of the following options: • • To manually enter the data sources. On Data Source Revisions. if necessary. Verifying the Data Source for Control Tables To verify the Control Tables data source: Copyright © 2008. All rights reserved. set up or verify the data source information for your business data. GA. 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. Creating a Remote Installation Plan 1. Click OK The Select Environments form appears so that you can define another environment.Rev0 315 .Chapter 17. Oracle. Click OK.Chapter 17. verify your Control Tables data source.Rev0 Copyright © 2008. Creating a Remote Installation Plan 1. Select Another Environment To select another environment: 316 GA. On Data Source Revisions. Oracle. 2. . All rights reserved. The Remote Location Packages window appears. Oracle. click Close. choose the next environment that you want to define. After defining all of your environments. On Select Environments. 4. GA. All rights reserved. 3. 2. Repeat all tasks in Replicating Information to Remote Locations and Setting Up Data Sources for Environment. Select one of the following options: Copyright © 2008. Creating a Remote Installation Plan 1. You can push delivered full packages to remote locations when you run the Location Workbench.Chapter 17.Rev0 317 . You are prompted to add another location.Rev0 Copyright © 2008. On Select Remote Location Packages.Chapter 17. Click Select to push the chosen packages. • To add another location. you can choose to enter another plan location or finalize your remote installation plan. Continue with Concluding the Remote Installation Plan Setup. Continue with Concluding the Remote Installation Plan Setup. Click Take Defaults to push all available packages to the remote location. click Yes. Oracle. Concluding the Remote Installation Plan Setup After concluding the environment setup. 5. choose a package from the list and click the Deselect icon in the Row menu. Creating a Remote Installation Plan • • Click Yes to view a list of packages to push to the remote location. . Note Click the corresponding icon in the Row menu to select or cancel the selection of a package. If you click Yes. 6. • Click No if you do not want to push packages to the remote location. All rights reserved. the Select Remote Location Packages form appears. 318 GA. Review the report to confirm that all records were validated. choose On Screen or To Printer. To finalize the installation plan: 1. Concluding the Validation Planner Report 1. on the Batch Versions form. 3. Language table (F984031) . Click OK to exit the concluding message box and initiate the Planner Validation Report. Creating a Remote Installation Plan Repeat all tasks for adding a location. All rights reserved. Finalizing the Installation Plan Installation Planner finalizes your installation plan automatically. Copyright © 2008.Rev0 319 . After reviewing the report. When the plan is finalized: • • The status is set to 20. Planner Validation Report automatically prompts you to run this report. • To conclude remote Installation Planner setup. on the tree view of your plan.Chapter 17. click No. • • If the processing option default was chosen. and then click OK. GA. A message appears to let you know that the installation plan is finalized.if you are installing an alternate language. This value means that several adjustments to OCM mappings and tables were made according to your plan. starting with Entering Plan Location Information. 2. On Report Output Destination. Oracle. Machine Detail table (F9651). The following tables are now updated: Release Master table (F00945). click Validate to initiate the Planner Validation Report. Create OCM (F986101). Table Conversion Scheduler (F98405). Continue with Finalizing the Installation Plan below. click Close. Package Plan table (F98404). Path Code Master table (F00942). If the processing option default was not chosen. 4. Run Installation Workbench for this installation plan. All rights reserved. For more information about Installation Workbench. refer to Working with Reports. . refer to Working With Installation Workbench. On Work With Installation Plans. Oracle. Creating a Remote Installation Plan For more information about Installation Planner Validation Report (R9840B). click Expand to review the plan that you created. 5.Chapter 17. 320 GA.Rev0 Copyright © 2008. Oracle. GA.Chapter 17. All rights reserved.Rev0 321 . Creating a Remote Installation Plan Copyright © 2008. 322 This page intentionally left blank . Adding a Server to an Existing Configuration This section contains the procedures for adding additional servers to your configuration. All rights reserved. logged on as user JDE with the database password for user JDE. Personnel Logon Status Prerequisites Concurrent Tasks Copyright © 2008. Use these procedures only if you have already defined and run your initial installation plan and set up your environments.Rev0 323 . GA. 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.Chapter 18.0 directory is shared. On the Deployment Server. None. Verify that the Deployment Server is installed and the Release 9. in the planner environment. Oracle. Installer. Adding a Server to an Existing Configuration 324 GA. Oracle.Rev0 Copyright © 2008.Chapter 18. All rights reserved. . 0 displays the following warning: 5. 4. On Work with Installation Plans. Adding a Server to an Existing Configuration Starting Installation Planner Begin your installation plan by logging on to Release 9.0 as user JDE with the database password for user JDE. 2. From the System Installation Tools menu (GH961).Rev0 325 . Log on to Release 9. Access the planner environment (JDEPLAN). Click OK. All rights reserved. The Installation Planner form appears. click Add.Chapter 18. 3. To start the Installation Planner: 1.0 and starting Installation Planner. Copyright © 2008. GA. Release 9. double-click Add-on Servers Plan. Oracle. 326 GA. The Location Search form appears. complete the following fields: Name Description Status To Release Enter the name of your installation plan. Verify that the release number is E900. such as plan name and description. On Installation Planner. Oracle. enter basic plan information. Click OK.Rev0 Copyright © 2008. Adding a Server to an Existing Configuration Entering a Plan Description After starting Installation Planner. Enter the description of your installation plan.Chapter 18. Select 10 as the status of your installation plan. To enter a plan description: 1. . All rights reserved. 2. choose the location defined during your base installation. GA. For most instances. choose a location and click Select. All rights reserved. On Location Search.Rev0 327 .Chapter 18. To enter a plan location: 1. Adding a Server to an Existing Configuration Entering a Plan Location Once basic plan installation information is entered. Copyright © 2008. you must choose an existing plan location. Oracle. click OK. All rights reserved.Rev0 Copyright © 2008.Chapter 18. 328 GA. On Location Revisions. Adding a Server to an Existing Configuration 2. . Oracle. Continue with the relevant sections that follow. Adding a Server to an Existing Configuration Selecting Additional Server Types Once a plan location is specified. GA.Rev0 329 . A Server Revisions form appears in the order listed on the Server Add form for each type of server that you chose. 3.Chapter 18. To select additional server types: 1. 2. All rights reserved. On Server Add. Oracle. Click OK. Copyright © 2008. specify the types of servers you want to add to your installation plan. check the types of servers that you want to add to your configuration. Rev0 Copyright © 2008. for Release 9. 330 GA. Enter the server share path where you installed Release 9. On the Deployment tab. . Oracle. for example. the server share path is \E900. The default for primary user is JDE.Chapter 18. Click OK. Enter E900. On Deployment Server Revisions. 2. Displays the system-provided default value chosen for this plan.0 on your Deployment Server. 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. Enter a description of the machine. Verify that this path matches your version of the release. This identifies the user to whom email is sent when a package is deployed. The default value for a secondary Deployment Server is 0.0. verify or complete the following fields: Primary Deployment Server Server Share Path This field indicates the hierarchy of the servers. 3. All rights reserved. To enter Deployment Server information: 1. complete the following fields: Machine Name Description Release Location Primary User Enter the name of your additional Deployment Server. Adding a Server to an Existing Configuration Tip If you enter invalid information into a tab field. such as Deployment Server.Rev0 331 . All rights reserved. Continue with the relevant sections that follow. Copyright © 2008. You are prompted to add another Deployment Server. 4. a stop sign icon appears next to the tab name.Chapter 18. click on the stop sign icon in the bottom right-hand corner of the form. Oracle. • To add another Deployment Server. Repeat Entering Deployment Server Information . GA. • To continue with the additional server plan. click No. For more information about the error. click Yes. Enter a description of the machine. Enter the release number to which this plan applies.0 will run and be shared by both nodes. not the machine name. All rights reserved. Enter the name of your primary Enterprise Server. On Enterprise Server Revisions. . or use the visual assist Description Release 332 GA. use the cluster name.0.Rev0 Copyright © 2008. Caution When using cluster software. One copy of Release 9. The name is casesensitive. 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. Use the cluster name as the server name when installing Release 9. Oracle. complete or verify the following fields: Machine Usage Machine Name Displays the default value of 20 to indicate that this is an Enterprise Server.Chapter 18. 6015. 2. You may need to add the drive x: to the path. Click the visual assist button and choose the type of Enterprise Server that you are adding to the plan. Displays the system-supplied default value when you enter the host type. On the Enterprise tab. Proceed to Entering Shared Data Source Information. Enter the installation directory path where you want to install Release 9. Enter the user to whom email is sent when a package is deployed. such as E900. All rights reserved. for example. Using the visual assist button. Make sure that this path is specific to your version of the release. Change the port number for this Enterprise Server to a unique value. Copyright © 2008. A message box appears prompting you to enter custom data sources or take the default data sources. Displays the system-supplied default value when you enter the host type. this path ends with \E900.0. choose the name of the Deployment Server to which this Enterprise Server is attached. complete these fields: Port Number Displays the default value for this field.0 on your Enterprise Server.Chapter 18. Click OK. such as Intel NT .INI. The system provides a default value for this field. Enter the type of database that you want to use for data sources on the Enterprise Server. Logical Machine Name Database Type Server Map Data Source Installation Path Deployment Server Name 3. which is supplied the JDE. for release 9.Rev0 333 . Oracle. GA. The default for primary user is JDE. Adding a Server to an Existing Configuration Host Type Location Primary User button to choose one from the list. but you can change it. Value is S for SQL Server. For example. Enter the default location chosen for this plan. • To accept default data sources.Chapter 18. Adding a Server to an Existing Configuration Entering Enterprise Server Data Source Information After specifying Enterprise Server information.Rev0 Copyright © 2008. Skip to Verifying Custom Server Map Data Source Information . Choose one of the following options: • To enter custom data sources. 334 GA. . click OK. This section discusses: • • • Specifying Custom or Default Data Source Information 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. This option limits your customization choices. enter the data source information for the Enterprise Server you will use in this plan. All rights reserved. Oracle. click Take Defaults. 2. verify your Server Map data source information.Chapter 18. Adding a Server to an Existing Configuration Verifying Custom Server Map Data Source Information To verify custom Server Map data source information: 1. Repeat processes. Oracle. Click OK. Copyright © 2008. starting with Entering Enterprise Server Information . when you run Installation Planner. click No. However. GA. choose one of the following options: • To add another Enterprise Server. On Data Source Revisions. The Machine/Server Types form appears. click Yes.Rev0 335 . you might need to modify some data source information to reflect your system-specific configuration. Tip Default data sources are configured as completely as possible. • To continue with Installation Planner setup. Adding another Enterprise Server On the prompt to add another Enterprise Server. All rights reserved. .0. these terms are all synonymous. or click Select to choose from a list of existing HTML Servers. On HTML Application Server. 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.Rev0 Copyright © 2008. 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. Functionally. However.Chapter 18. this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software. 336 GA. click OK to define a new HTML Server. To enter HTML Web Server information: 1. Oracle. All rights reserved. Adding a Server to an Existing Configuration Entering HTML Web Server Information Note For Release 9. Chapter 18. you are presented with the Machine Search table.Rev0 337 . Adding a Server to an Existing Configuration If you choose Select. All rights reserved. GA. Copyright © 2008. Oracle. from which you can make your selection. 4.Chapter 18.oracle. Enter E900 to indicate the release number that you are installing. the web shortcut generated points to the "Primary" HTML Web Server. Enter a description of the HTML Web Server machine. complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form. Enter the name of your HTML Web Server. The default value of 50 specifies the server type as Intel NT.INI. . 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.Rev0 Copyright © 2008.com. On HTML Server Revisions. The user to whom an email is sent when a package is deployed. This is the protocol used by the HTML Web Server. or click Select to select an existing HTML Web Server. For example: www. Oracle. The location chosen for this plan appears in this field by default. All rights reserved. This is the Domain Name System (DNS) host name of the HTML Web Server. The name is case sensitive and must not exceed 10 characters. click OK to continue entering HTML Web Server information. Select the correct server type. Protocol Server URL HTTP Port 338 GA. 3. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). Valid values are http or https. This is the port number the HTML Web Server is listening to. Adding a Server to an Existing Configuration 2. On the HTML tab. On the HTML Application Server dialog. The default for primary user is listed in the JDE. you must obtain this value from the HTML Web Server machine itself. 5. the typical port number is 443. the path ends with E1HTMLServer. the value is 6015. You should not use it unless you have a direct need. For Release 9. and also the platform and application server on which your HTML Web Server is running. Usage of Explicit servlet name is for backward compatibility only.Rev0 339 . To add another HTML Web Server. Click OK. Redirector The URL generated will point to redirector in the Primary HTML Web Server. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths. For JD Edwards EnterpriseOne Release 9.0 on Oracle Applications Servers. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. JDENET Listen Port Default Login Installation Path Copyright © 2008. Explicit The user can specify an explicit servlet name in this field. Defines how shortcuts to a web form are generated by the system code. GA. and redirector will point to a servlet on another HTML Web Server for load balancing. the redirector functionality cannot be used. In this Servlet case. 6.0 on your HTML Web Server. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server.0. you can choose to implement a HTML Web Server using a different port number.Chapter 18. Values are either a reserved value or an explicit servlet name. Adding a Server to an Existing Configuration For HTTP. For HTTPS. However. Make sure this is specific to your version of the release. the typical port number is 80. Enter the installation directory path to which you are installing Release 9. click Yes and repeat steps 1 through 4 to define another HTML Web Server. Oracle. The servlet name to use is generated by the system. Otherwise. or its administrator. All rights reserved. The value is dependent on the release of JD Edwards EnterpriseOne.and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. refer to the applicable platform. • Select Click this option to select an existing Data Server.Rev0 Copyright © 2008. Continue with the Planner with the environment selection in step 6 of this task. . 340 GA. choose click OK to continue entering unique Data Server information. All rights reserved. Adding a Server to an Existing Configuration Entering Data Server Information To enter Data Server information: 1. On Data Server. • Skip Click this option if you do not want to define a Data Server.Chapter 18. choose one of these options: • OK If your database resides on a separate server. Oracle. 4. Valid values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client . E900.Rev0 341 . Adding a Server to an Existing Configuration 2. Oracle. All rights reserved. for example. GA. Enter the name of your Data Server.Chapter 18. The default for primary user is JDE. Enter the user to whom an email is sent once a package is deployed. On Data Server Revisions.Win NT Displays the location chosen for this plan appears in this field by default. complete the following field: Data Source Type Select the type of data source. Click OK. Enter the Release 9.0 release number you are installing.NT 90 Client . Copyright © 2008. The name must not exceed 10 characters. Value is S for SQL Server . Enter a description of the machine. On the Data tab. 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. Select the type of Data Server that you are adding to the plan. Location Primary User 3. Rev0 Copyright © 2008. 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. 6. Click OK to continue entering unique shared data source information. On Location. • Click No to continue with Installation Planner setup. 342 GA. . Oracle. 7. All rights reserved.Chapter 18. or click Take Defaults to select the default data for the shared data sources. Adding a Server to an Existing Configuration 5. you are prompted to enter shared data source information for the specific environment that you previously selected to install. On Data Source. select Yes to add another location or No to continue with Installation Planner. Rev0 343 . Copyright © 2008.0 data sources. Oracle. click Take Defaults and continue with the task entitled: Setting Up Environments . • Click OK to enter.Chapter 18. 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. 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. All rights reserved. This option limits your customization choices. choose one of these options: • To use the Release 9. GA. or modify the data source information. verify. Chapter 18. Click OK. 344 GA. Oracle. On Data Source Revisions. 2. verify the accuracy of the Data Dictionary data source. Adding a Server to an Existing Configuration Verifying the Data Dictionary Data Source To verify the Data Dictionary data source: 1. . All rights reserved.Rev0 Copyright © 2008. All rights reserved.Rev0 345 . On Data Source Revisions. Adding a Server to an Existing Configuration Verifying the Object Librarian Data Source To verify the Object Librarian data source: 1. GA. Oracle. Click OK. Copyright © 2008. verify the accuracy of the Object Librarian data source. 2.Chapter 18. 2. 346 GA. refer to Understanding Data Source Charts. Adding a Server to an Existing Configuration Verifying the System Data Source To verify the System data source: 1. Oracle. All rights reserved.Rev0 Copyright © 2008. The Environment Selection screen appears. Click OK. See Also For more information about System data source fields or fields for other data sources mentioned in this process.Chapter 18. On Data Source Revisions. verify the accuracy of the settings for the System data source. . All rights reserved. clear the options for those parameters that you want to customize. skip to Setting Up Environment Data Sources .0 displays a customization form for each parameter that you turn off. Depending on the options chosen when you set up your plan. Oracle.0 displays one or more of the following parameters. 2.0 displays customization Copyright © 2008. 1. As you move through the plan. GA. Note The parameters that are available vary depending on the options that you selected at the beginning of the planning process. On Environment Selection.Rev0 347 .0 configures your system using values for typical environments. Release 9. 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. Release 9.Chapter 18. Adding a Server to an Existing Configuration Setting Up Environments By default. Use the following tasks to customize each of the parameters listed above. Release 9. Note If you selected the default option for all parameters. Release 9. Click OK. . All rights reserved. Enter the environment information on the screen and click Next. or click Copy to copy the settings of an existing environment. Skip the tasks for those parameters that were selected. or create a pathcode and click Next.Chapter 18.Rev0 Copyright © 2008. Oracle. Adding a Server to an Existing Configuration forms only for those parameters for which were cleared of the default options. Select share. 4. 2. 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. 3. 348 GA. Click Add to add a new environment. Enter pathcode information on the screen and click Next. To set up multiple environments. Oracle. Environments prefixed with J are required for the HTML Web Server. This screen appears after the following tasks are completed. GA. choose and define them one at a time. All rights reserved. Copyright © 2008. To select an environment: On Select Environments. double-click the environment that you want to define. Adding a Server to an Existing Configuration Selecting an Environment The Select Environment form appears.Rev0 349 .Chapter 18. Adding a Server to an Existing Configuration Specifying Environment Data Load Parameters If you cleared Default Data Load on the Environment Selection form. 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 9. For additional details.Chapter 18. 350 GA. . All rights reserved. Oracle. the Data Load Parameters form appears. refer to Loading Data (Demo Data and Production Data).Rev0 Copyright © 2008.0 because data is automatically loaded by the Platform Pack Installer. Rev0 351 . All rights reserved. 4. On Language Selection. Oracle. Copyright © 2008. 3. From the Row menu. Repeat the above steps until all your languages have been selected. GA. choose the appropriate language. Adding a Server to an Existing Configuration Selecting Languages To select languages: 1. click Select. to set up a language for the selected environment. 2. Click OK.Chapter 18. Setting Up the Data Source for Business Data To set up the data source for business data: 1. see the JD Edwards EnterpriseOne Tools 8.Rev0 Copyright © 2008. From the Form menu. 2. Oracle. All rights reserved.0 default data sources. . See Also To modify this template. continue with the following task. If you created a custom environment. or click Take Defaults to accept the Release 9. it is necessary to set up the data sources for those environments. 352 GA. click OK to manually enter the data sources. Adding a Server to an Existing Configuration Setting Up Environment Data Sources Once the Environments have been set up.Chapter 18.9 Configurable Network Computing Implementation Guide. click Advanced. On Data Source Revisions. Selecting an Environment Data Source Setup Option When you are prompted to set up data sources for the environment you just configured. data source information is generated from the data source template provided with JD Edwards EnterpriseOne. verify the data source for your Business Data. Rev0 353 . All rights reserved. Copyright © 2008. Oracle. Click OK. GA. Adding a Server to an Existing Configuration 3.Chapter 18. verify the information for your Central Objects data source. Oracle. 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.Rev0 Copyright © 2008.Chapter 18. Click OK. All rights reserved. Select Advanced from the Form menu to verify Unicode is checked. 2. On Data Source Revisions. . Caution The Central Objects data source must be Unicode. 354 GA. All rights reserved.Rev0 355 .Chapter 18. Adding a Server to an Existing Configuration Note The Central Objects data sources are specific to the pathcode. Oracle. GA. Copyright © 2008. Click OK. Enter the name of the owner of this object Note The Control Tables data sources are specific to the environment and pathcode. 2. . verify the accuracy of the Control Tables data source. Data Source Name Server Name Object Owner ID Verify the name of the data source. Oracle.Chapter 18.Rev0 Copyright © 2008. 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. Verify the name of the Enterprise Server. On Data Source Revisions. All rights reserved. 356 GA. Chapter 18. 2. Adding a Server to an Existing Configuration Verifying the Data Source for Versions To verify the data source for versions: 1. Copyright © 2008. Note Versions data sources are specific to the pathcode. verify the accuracy of the Versions data source. On Data Source Revisions.Rev0 357 . All rights reserved. GA. Click OK. and the Unicode flag on the Advanced Form must be checked. Oracle. Chapter 18. A message appears to let you know that the installation plan is finalized. When the plan is finalized: • • • • The status is set to 20.Rev0 Copyright © 2008. Oracle. on the tree view of your plan. All rights reserved. If you did not choose the default processing option. Click OK to exit the concluding message box and initiate the Planner Validation Report. . Modify the JDE. 358 GA. • • If you chose the default processing option. Adding a Server to an Existing Configuration Finalizing the Installation Plan Installation Planner finalizes your installation plan automatically. Planner Validation Report automatically prompts you to run this report. 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). click Validate to initiate the Planner Validation Report. if you are installing an alternate language To finalize the installation plan: 1.INI . Create the OCM. which signals that several adjustments to tables were made according to your plan. Review the report to confirm that all records were validated. On Report Output Destination. Adding a Server to an Existing Configuration Concluding the Validation Planner Report To conclude the validation planner report: 1.Rev0 359 . refer to Working With Installation Workbench. 3. 4. Oracle. on the Batch Versions form. On Work With Installation Plans. refer to Working with Reports.Chapter 18. click Close. Copyright © 2008. click Expand to review the plan that you created. choose On Screen or To Printer. Run Installation Workbench for this installation plan. For more information about Installation Workbench. 5. 2. and then click OK. GA. All rights reserved. For more information about Installation Planner Validation Report (R9840B). After reviewing the report. When using the Installation Workbench for adding servers. you must add all environments prefixed with J to the Enterprise Server and generate a Server Map data source.Rev0 Copyright © 2008. Adding a Server to an Existing Configuration Configuring Additional Servers To configure any additional servers that you have added: 1. use Installation Workbench to allocate and configure software and resources. When adding a server plan for a HTML Web Server. All rights reserved. . 2. 360 GA. Oracle. After configuring your database and server. using the P9654A program. 3. Create the database PS900. the Table Conversion and the Specification Merge workbenches do not appear because they are not needed.Chapter 18. Chapter 18.Rev0 361 . Oracle. Adding a Server to an Existing Configuration Copyright © 2008. GA. All rights reserved. 362 This page intentionally left blank . GA. All rights reserved. Oracle.Chapter 19.Rev0 363 . 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. Chapter 19. It is important that you complete all tasks in this chapter to achieve a successful language installation. 3. Review the disk space requirements. Implement a language-only plan only for installations in which a language has not been previously installed. Oracle. The detailed information regarding the language installation process is found in Language Process Overview .0. The detailed information about directory structures is found in the Understanding JD Edwards EnterpriseOne Directory Structures chapter of this guide. Reviewing Requirements for a Language Installation To review the basic requirements for performing a language installation: 1.Rev0 Copyright © 2008. you should use the procedures in this chapter when installing an alternate language or multiple languages for the first time. or after completing a working installation or upgrade. All rights reserved. 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 9. Verify that the disk space requirements are available for each language and each environment that you are installing on the deployment and Enterprise Servers. Review the directory structure. 364 GA. 2. Creating a Language-Only Installation Plan Understanding Language-Only Installation Plans To make the language-only installation as easy and quick as possible. Review the language installation process. . the language CD is for French.Rev0 365 . you can manually run the setup.exe. GA. In this example.Chapter 19. If the autorun does not automatically start the Language Installer program. Insert the JD Edwards EnterpriseOne language CD into the CD drive. Copyright © 2008. On JD Edwards Installation Manager. All rights reserved. Creating a Language-Only Installation Plan Installing Languages on the Deployment Server To install languages on the Deployment Server: 1. 2. click the link for the language that you want to install. Oracle. . click Next. All rights reserved. On the Welcome screen.Chapter 19. 366 GA. Creating a Language-Only Installation Plan 3. Oracle.Rev0 Copyright © 2008. Copyright © 2008. On Client Workstation Installation Setup Type. Creating a Language-Only Installation Plan 4. GA. Click Finish. Oracle. The Client Workstation Install Progress displays the progress of the language installation. 5.Rev0 367 . 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\900 You must verify that this drive and path is valid for your installation.Chapter 19. All rights reserved. You can use the browse function to locate the directory. 6. the Oracle Deployment Server Setup form indicates whether the installation was successful. On Installation Complete. All rights reserved. 368 GA. click OK.Rev0 Copyright © 2008. Oracle. Creating a Language-Only Installation Plan When the installation finishes. you need to build a custom package that includes all available languages. Note To access more than one language within the same package. .Chapter 19. • • • • 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. run Installation Planner. refer to Creating a Custom Installation Plan . Copyright © 2008.Chapter 19. you can choose which language to install for each environment. Creating a Language-Only Installation Plan Running Installation Planner Once you have installed languages on the Deployment Server.Rev0 369 . Note If you choose a custom installation plan. These tasks highlight the critical language-related stages of this operation. This section assumes you are defining a custom plan. All rights reserved. Oracle. GA. In the Include Language area. All rights reserved. enter the basic plan information. Creating a Language-Only Installation Plan Entering Information into Installation Planner To enter information into the Installation Planner: 1. Oracle. 2. . On Installation Planner. select the Language Only option.Rev0 Copyright © 2008. 370 GA.Chapter 19. Clear the options for Default Environment and Default Languages if you want to specify which language or languages to install for each environment.Chapter 19. From Environment Selection. Creating a Language-Only Installation Plan Selecting Custom or Default Parameters To select custom or default parameters: 1.Rev0 371 . Oracle. all environments and languages are the default values. All rights reserved. GA. Copyright © 2008. The Language Selection form appears.Chapter 19. .Rev0 Copyright © 2008. Oracle. 372 GA. All rights reserved. Creating a Language-Only Installation Plan Selecting an Environment To select an environment: Choose the environment for which you wish to install a language. Oracle. On Language Selection. choose the appropriate language. Creating a Language-Only Installation Plan Selecting a Language To select a language: 1. All rights reserved. 3. Repeat the above steps until all your languages have been selected. 4. to set up a language for the selected environment.Rev0 373 . Click OK.Chapter 19. 2. From the Row menu. GA. Copyright © 2008. click Select. Install the appropriate language character set to a workstation. Verify that the Enterprise Server hardware and software meet all requirements. data dictionary. Verify that the workstation hardware and software meet all requirements. Complete the tasks in Installing the Workstations for Developers and System Administrators. Oracle. Install. Verifying Enterprise Server Requirements To verify Enterprise Server requirements: 1. The control tables. 4. 3. 2. Verify that the group and user profiles are set up properly. Creating a Language-Only Installation Plan Running Installation Workbench After you create the language-only plan.Rev0 Copyright © 2008. 374 GA. Go to Working With Installation Workbench. To run the Installation Workbench: 1. The language installation process is the same for every database. and central objects will be loaded by the Control Table Workbench and the Specification Table Merge Workbench.INI settings on the Deployment Server for Interactive Runtime. you must run it through a series of workbenches in order to load the language tables to the appropriate data sources. Verifying Workstation Requirements To verify workstation requirements: 1. 3. Completing the Language Installation Once you have verified that the Enterprise Server and workstation hardware and software meet your language install requirements. Complete the procedures for Control Table Workbench and Specification Table Merge Workbenches. and Network Queues.Chapter 19. 5. See the JD Edwards EnterpriseOne Tools Package Management Guide for more information about how to transfer language specifications to the Enterprise Server. All rights reserved. Verify that the Enterprise Server disk space meets all requirements.INI settings for local code set and code page values are set for your preferred language. 2. These values are found in the National Language Support tables in Language Process Overview . Verify that the JDE. Complete the step to verify the JDE. . you can complete the installation. 2. Creating a Language-Only Installation Plan Building and Deploying Alternate Language Packages Once you have concluded the installation.Chapter 19. See Package Build in the JD Edwards EnterpriseOne Tools Package Management Guide for the details of including a language or creating language-only packages. All rights reserved. it is time to build and deploy the alternate language packages.Rev0 375 . Oracle. Copyright © 2008. GA. 376 This page intentionally left blank . The recommended configuration is for all business functions to be mapped to the server. Assuming you use the recommended shared path names. 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 9. and Workstations.Chapter 20. the Enterprise Server. the process does not delete or overlay your previous release. PS900. or PY900 Database setup scripts. you should have the following directory structure: Directory Name \JDEdwards \JDEdwards\BPMBroker \JDEdwards\BPMBroker\JRE \JDEdwards\E900 \JDEdwards\E900\bpm \JDEdwards\E900\CD Templates \JDEdwards\E900\CD Templates\Esu & Asu \JDEdwards\E900\CD Templates\Esu & Asu\planner \JDEdwards\E900\CD Templates\Esu & Asu\planner\Package \JDEdwards\E900\CD Templates\Esu & Asu\planner\Package\PKGNAME \JDEdwards\E900\Client \JDEdwards\E900\Database \JDEdwards\E900\path_code where path_code is DV900. You must understand these directory structures to verify that you installed or upgraded Release 9.0 correctly. The only exception to this rule is a client development environment in which case all business functions should be mapped locally. Path codes. Product Packaging files.Rev0 377 . Oracle. Contents Copyright © 2008.0 directories in addition to your existing directories.0 on the Deployment Server. All rights reserved. PD900. You will have the Release 9. GA. Understanding JD Edwards EnterpriseOne Directory Structures The charts in this section illustrate the directory structures for JD Edwards EnterpriseOne on the Deployment Server. Partial host installation objects.Chapter 20. Partial host installation objects. The files reside here until you install the platform–specific objects. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\path_code\bin32 \JDEdwards\E900\path_code\EOne \JDEdwards\E900\path_code\include \JDEdwards\E900\path_code\lib32 \JDEdwards\E900\path_code\make \JDEdwards\E900\path_code\obj \JDEdwards\E900\path_code\package \JDEdwards\E900\path_code\package\DATA \JDEdwards\E900\path_code\package\DATACOMP \JDEdwards\E900\path_code\package\DV900FA \JDEdwards\E900\path_code\package\DV900PA \JDEdwards\E900\path_code\res \JDEdwards\E900\path_code\source \JDEdwards\E900\path_code\spec \JDEdwards\E900\path_code\work \JDEdwards\E900\Hosts \JDEdwards\E900\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 platform–specific objects. Partial host installation objects. The files reside \JDEdwards\E900\Hosts\Hp9000 \JDEdwards\E900\Hosts\IntelNT \JDEdwards\E900\Hosts\Linux \JDEdwards\E900\Hosts\RS6000 378 GA. Oracle. All rights reserved.Rev0 Copyright © 2008. . The files reside here until you install the platform–specific objects. The files reside here until you install the platform–specific objects. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name Contents here until you install the platform–specific objects. All rights reserved.Chapter 20. \JDEdwards\E900\InstallLogs \JDEdwards\E900\MediaObj \JDEdwards\E900\misc \JDEdwards\E900\misc\SSE \JDEdwards\E900\OneWorld Client Install Package build files for web development client. GA. \JDEdwards\E900\OneWorld Client Install\Font \JDEdwards\E900\OneWorld Client Install\Misc \JDEdwards\E900\OneWorld Client Install\Push Install Listener \JDEdwards\E900\OneWorld Client Install\ThirdParty \JDEdwards\E900\OneWorld Client Install\ThirdParty\BPMBroker \JDEdwards\E900\OneWorld Client Install\ThirdParty\MOBILESQL \JDEdwards\E900\OneWorld Client Install\ThirdParty\SSE \JDEdwards\E900\OneWorld Client Install\ThirdParty\Synchrologic \JDEdwards\E900\OneWorld Client Install\ThirdParty\WebDevFeature \JDEdwards\E900\Planner \JDEdwards\E900\PACKAGE_INF \JDEdwards\E900\PACKAGE_INF\Feature_Inf \JDEdwards\E900\planner \JDEdwards\E900\Planner\bin32 Application and business function . Media objects for runtime. \JDEdwards\E900\Hosts\Sun Partial host installation objects.Rev0 379 . Oracle.DLL files Bitmap objects for applications Planner Environment files \JDEdwards\E900\Planner\data \JDEdwards\E900\Planner\res \JDEdwards\E900\Planner\spec \JDEdwards\E900\Planner\res\avi files \JDEdwards\E900\Planner\res\formlines \JDEdwards\E900\Planner\res\icons \JDEdwards\E900\Planner\res\images \JDEdwards\E900\Planner\res\treebmps Copyright © 2008. Oracle.H) files.Rev0 Copyright © 2008. \JDEdwards\E900\System\Include\metadata \JDEdwards\E900\System\IncludeV \JDEdwards\E900\System\IncludeV\unicode \JDEdwards\E900\System\Lib32 Import libraries for business functions. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\planner\spec \JDEdwards\E900\PrintQueue \JDEdwards\E900\SolutionExplorer \JDEdwards\E900\SolutionExplorer\Data \JDEdwards\E900\SolutionExplorer\Data\+ Concept To Opportunity \JDEdwards\E900\SolutionExplorer\Data\+ Consumption To Reorder \JDEdwards\E900\SolutionExplorer\Data\+ Demand To Available \JDEdwards\E900\SolutionExplorer\Data\+ Implementation Approach \JDEdwards\E900\SolutionExplorer\Data\+ Manage Materials \JDEdwards\E900\SolutionExplorer\Data\+ Manage The Business \JDEdwards\E900\SolutionExplorer\Data\+ Order To Cash \JDEdwards\E900\SolutionExplorer\Data\+ Procure To Pay \JDEdwards\E900\SolutionExplorer\Data\RNT3 \JDEdwards\E900\SolutionExplorer\Data\SK_FOUNDATION_DOCUMENTS \JDEdwards\E900\SolutionExplorer\Data\style \JDEdwards\E900\SolutionExplorer\Data\styles \JDEdwards\E900\SolutionExplorer\PortalLite \JDEdwards\E900\System \JDEdwards\E900\System\bin32 \JDEdwards\E900\System\classes \JDEdwards\E900\System\classes\samples \JDEdwards\E900\System\Include Contents System files. Production business function header (.Chapter 20. . All rights reserved. \JDEdwards\E900\System\Libv32 \JDEdwards\E900\System\Locale \JDEdwards\E900\System\Locale\Iconv \JDEdwards\E900\System\Locale\Uconvtab \JDEdwards\E900\System\Locale\Xml \JDEdwards\E900\System\Models \JDEdwards\E900\System\OWPatrol \JDEdwards\E900\System\OWPatrol\owkm \JDEdwards\E900\System\OWPatrol\owkm\images \JDEdwards\E900\System\OWPatrol\owkm\km \JDEdwards\E900\System\OWPatrol\owkm\psl \JDEdwards\E900\System\Resource 380 GA. Rev0 381 . Solution Explorer language files. Language database. Language help files. Planner path code.Chapter 20. you should have the following Enterprise Server directory structure: Directory Name \JDEdwards\E900\DDP\DV900 Definition Copyright © 2008. Directory Name \LANGUAGE \Helps \SolutionExplorer \SolutionExplorer\PLANNER \SolutionExplorer\PLANNER\DATA Definition Name of language for JD Edwards EnterpriseOne language installation. You must understand this directory structure to help you verify that the language was installed correctly.0 software directory structure for the Release 9. Oracle. All rights reserved.0 language CD. Enterprise Server Directory Structure After you run Host Workbench. GA. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\System\Resource\cidfont \JDEdwards\E900\System\Resource\cmap \JDEdwards\E900\System\Resource\encoding \JDEdwards\E900\System\Resource\iccprofile \JDEdwards\E900\System\Resource\truetype \JDEdwards\E900\systemcomp \JDEdwards\E900\_jvm \JDEdwards\E900\_jvm\bin \JDEdwards\E900\_jvm\bin\client \JDEdwards\E900\_jvm\lib \JDEdwards\E900\_jvm\lib\applet \JDEdwards\E900\_jvm\lib\cmm \JDEdwards\E900\_jvm\lib\ext \JDEdwards\E900\_jvm\lib\fonts \JDEdwards\E900\_jvm\lib\i386 \JDEdwards\E900\_jvm\lib\im \JDEdwards\E900\_jvm\lib\images \JDEdwards\E900\_jvm\lib\images\cursors \JDEdwards\E900\_jvm\lib\security \JDEdwards\E900\_jvm\lib\zi \JDEdwards\E900\_uninst Contents Language Directory Structure The following table outlines the Release 9. System executables.Rev0 Copyright © 2008. Import libraries for business functions. Object code for business functions. Replicated local objects. All rights reserved. Business function source.Chapter 20. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\PrintQueue \JDEdwards\E900\DDP\system \JDEdwards\E900\DDP\DV900\bin32 \JDEdwards\E900\DDP\DV900\data \JDEdwards\E900\DDP\DV900\include Definition Production business function include (. 382 GA.h) files. Oracle. . \JDEdwards\E900\DDP\DV900\lib32 \JDEdwards\E900\DDP\DV900\make \JDEdwards\E900\DDP\DV900\obj \JDEdwards\E900\DDP\DV900\res \JDEdwards\E900\DDP\DV900\source \JDEdwards\E900\DDP\DV900\spec \JDEdwards\E900\DDP\DV900\work \JDEdwards\E900\DDP\DV900\res\AVI Files \JDEdwards\E900\DDP\DV900\res\FormLines \JDEdwards\E900\DDP\DV900\res\Icons \JDEdwards\E900\DDP\DV900\res\images \JDEdwards\E900\DDP\DV900\res\treebmps \JDEdwards\E900\DDP\system\Bin32 \JDEdwards\E900\DDP\system\Classes \JDEdwards\E900\DDP\system\Explorer \JDEdwards\E900\DDP\system\Generator \JDEdwards\E900\DDP\system\Include \JDEdwards\E900\DDP\system\IncludeV \JDEdwards\E900\DDP\system\Lib32 \JDEdwards\E900\DDP\system\Libv32 \JDEdwards\E900\DDP\system\Locale \JDEdwards\E900\DDP\system\Models \JDEdwards\E900\DDP\system\OWPatrol \JDEdwards\E900\DDP\system\Resource \JDEdwards\E900\DDP\packages\PD900FA \JDEdwards\E900\DDP\packages\PD900FA\bin32 \JDEdwards\E900\DDP\packages\PD900FA\include \JDEdwards\E900\DDP\packages\PD900FA\obj System include files. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\packages\PD900FA\source \JDEdwards\E900\DDP\packages\PD900FA\spec \JDEdwards\E900\DDP\packages\PD900FA\obj\CAEC \JDEdwards\E900\DDP\packages\PD900FA\obj\CALLBSFN \JDEdwards\E900\DDP\packages\PD900FA\obj\CCONVERT \JDEdwards\E900\DDP\packages\PD900FA\obj\CCORE \JDEdwards\E900\DDP\packages\PD900FA\obj\CCRIN \JDEdwards\E900\DDP\packages\PD900FA\obj\CDBASE \JDEdwards\E900\DDP\packages\PD900FA\obj\CDDICT \JDEdwards\E900\DDP\packages\PD900FA\obj\CDESIGN \JDEdwards\E900\DDP\packages\PD900FA\obj\CDIST \JDEdwards\E900\DDP\packages\PD900FA\obj\CDMDSCH \JDEdwards\E900\DDP\packages\PD900FA\obj\CEPM \JDEdwards\E900\DDP\packages\PD900FA\obj\CFIN \JDEdwards\E900\DDP\packages\PD900FA\obj\CFND \JDEdwards\E900\DDP\packages\PD900FA\obj\CHRM \JDEdwards\E900\DDP\packages\PD900FA\obj\CINSTALL \JDEdwards\E900\DDP\packages\PD900FA\obj\CINV \JDEdwards\E900\DDP\packages\PD900FA\obj\CLOC \JDEdwards\E900\DDP\packages\PD900FA\obj\CLOG \JDEdwards\E900\DDP\packages\PD900FA\obj\CMFG \JDEdwards\E900\DDP\packages\PD900FA\obj\CMFGBASE \JDEdwards\E900\DDP\packages\PD900FA\obj\COBJLIB \JDEdwards\E900\DDP\packages\PD900FA\obj\COPBASE \JDEdwards\E900\DDP\packages\PD900FA\obj\CPAY \JDEdwards\E900\DDP\packages\PD900FA\obj\CRES \JDEdwards\E900\DDP\packages\PD900FA\obj\CRUNTIME \JDEdwards\E900\DDP\packages\PD900FA\obj\CSALES \JDEdwards\E900\DDP\packages\PD900FA\obj\CTC \JDEdwards\E900\DDP\packages\PD900FA\obj\CTOOL \JDEdwards\E900\DDP\packages\PD900FA\obj\CTRAN \JDEdwards\E900\DDP\packages\PD900FA\obj\CTRANS \JDEdwards\E900\DDP\packages\PD900FA\obj\CWARE \JDEdwards\E900\DDP\packages\PD900FA\obj\CWRKFLOW \JDEdwards\E900\DDP\packages\PD900FA\obj\JDBTRG1 \JDEdwards\E900\DDP\packages\PD900FA\obj\JDBTRG2 \JDEdwards\E900\DDP\packages\PD900FA\obj\JDBTRG3 \JDEdwards\E900\DDP\packages\PD900FA\source\CAEC \JDEdwards\E900\DDP\packages\PD900FA\source\CALLBSFN \JDEdwards\E900\DDP\packages\PD900FA\source\CCONVERT \JDEdwards\E900\DDP\packages\PD900FA\source\CCORE Copyright © 2008. Oracle.Rev0 Definition 383 . GA. All rights reserved.Chapter 20. All rights reserved. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\packages\PD900FA\source\CCRIN \JDEdwards\E900\DDP\packages\PD900FA\source\CDBASE \JDEdwards\E900\DDP\packages\PD900FA\source\CDDICT \JDEdwards\E900\DDP\packages\PD900FA\source\CDESIGN \JDEdwards\E900\DDP\packages\PD900FA\source\CDIST \JDEdwards\E900\DDP\packages\PD900FA\source\CDMDSCH \JDEdwards\E900\DDP\packages\PD900FA\source\CEPM \JDEdwards\E900\DDP\packages\PD900FA\source\CFIN \JDEdwards\E900\DDP\packages\PD900FA\source\CFND \JDEdwards\E900\DDP\packages\PD900FA\source\CHRM \JDEdwards\E900\DDP\packages\PD900FA\source\CINSTALL \JDEdwards\E900\DDP\packages\PD900FA\source\CINV \JDEdwards\E900\DDP\packages\PD900FA\source\CLOC \JDEdwards\E900\DDP\packages\PD900FA\source\CLOG \JDEdwards\E900\DDP\packages\PD900FA\source\CMFG \JDEdwards\E900\DDP\packages\PD900FA\source\CMFGBASE \JDEdwards\E900\DDP\packages\PD900FA\source\COBJLIB \JDEdwards\E900\DDP\packages\PD900FA\source\COPBASE \JDEdwards\E900\DDP\packages\PD900FA\source\CPAY \JDEdwards\E900\DDP\packages\PD900FA\source\CRES \JDEdwards\E900\DDP\packages\PD900FA\source\CRUNTIME \JDEdwards\E900\DDP\packages\PD900FA\source\CSALES \JDEdwards\E900\DDP\packages\PD900FA\source\CTC \JDEdwards\E900\DDP\packages\PD900FA\source\CTOOL \JDEdwards\E900\DDP\packages\PD900FA\source\CTRAN \JDEdwards\E900\DDP\packages\PD900FA\source\CTRANS \JDEdwards\E900\DDP\packages\PD900FA\source\CWARE \JDEdwards\E900\DDP\packages\PD900FA\source\CWRKFLOW \JDEdwards\E900\DDP\packages\PD900FA\source\JDBTRG1 \JDEdwards\E900\DDP\packages\PD900FA\source\JDBTRG2 \JDEdwards\E900\DDP\packages\PD900FA\source\JDBTRG3 \JDEdwards\E900\DDP\system\Generator\WEB-INF \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes \JDEdwards\E900\DDP\system\Generator\WEB-INF\lib \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpm \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpmweb \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\database \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas 384 GA.Chapter 20. . Oracle.Rev0 Definition Copyright © 2008. Rev0 385 . Oracle. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \printqueuecenter \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\redirector \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\taskexplorer \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\util \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\workflow \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\beans \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\behaviorcom \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\cache \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\datatypes \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\exception \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\gui \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\imagegenerator \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\logging \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\owsecurity \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\resource \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\spec \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\timer \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\util Definition Copyright © 2008.Chapter 20. All rights reserved. GA. Rev0 Copyright © 2008. . Oracle. All rights reserved. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\webgui \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\gui\explorer \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\gui\util \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\log4j \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\saw \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\test \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\cache \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\util\ftp \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\smtp \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\threadpool \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpm\utils \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \bpmweb\broker \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \bpmweb\Handlers \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpmweb\Util \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\base \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\explorer \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards Definition 386 GA.Chapter 20. Chapter 20.Rev0 Definition 387 . GA. All rights reserved. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \database\impl \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\database\jdb \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\application \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\as400 \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\businessview \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\condensed \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\config \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\datacache \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\formatter \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\logical \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\oracle \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\physical \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\resultset \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards Copyright © 2008. Oracle. Rev0 Definition Copyright © 2008. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \database\impl\retry \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\security \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\signon \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\sql \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\sqlserver \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\standalone \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\transaction \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\transform \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\trigger \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\udb \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\usage \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\base \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\bootstrap \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\company 388 GA. All rights reserved.Chapter 20. Oracle. . Chapter 20. All rights reserved. Oracle. GA. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\ocm \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\role \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\security \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\serviceobj \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\spec \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\udc \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\bsfnplugin \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\exception \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\net \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\res \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\security \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\services \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\transaction \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\anonuser \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\env \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\userpref Definition Copyright © 2008.Rev0 389 . All rights reserved. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\ifc \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\beans \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\components \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\js \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\util \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\envcheck \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\hr \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\importer \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\linkCenter \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\reportcenter \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\sarsystem \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal 390 GA. Oracle.Rev0 Definition Copyright © 2008.Chapter 20. . Oracle. All rights reserved.Rev0 391 . GA. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \components\webcheck \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\workcenter \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\reportcenter\client \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\beans \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\client \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\components \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\datahandler \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\defaults \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\gui \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\js \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\unittest \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\util \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\client \JdeTreeControl \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \envcheck \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \importer \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \linkcenter Definition Copyright © 2008.Chapter 20. . Oracle.Rev0 Copyright © 2008.Chapter 20. All rights reserved. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \login \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \rss \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \saw \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \search \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \webcheck \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \importer\upload \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\util\cache \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\util\gui \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\base \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\er \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\event \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\interfac \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards Definition 392 GA. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \runtime\model \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\swing \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine\form \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine\version \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\er\erobjects \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\engine \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\jniinclude \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\model \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\view \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\model\form \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\model\grid \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\input Copyright © 2008.Chapter 20. Oracle. All rights reserved. GA.Rev0 Definition 393 . Chapter 20. . All rights reserved. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\output \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\xapi \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\form \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\grid \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\version \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawagent \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawchart \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawcomm \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawdb \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawjavalog \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawjdbj \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawlog \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawsuperagent \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\smc \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\smcgui \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services\login \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \services\objectlookup \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards 394 GA. Oracle.Rev0 Definition Copyright © 2008. All rights reserved. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \services\login\display \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\kernel \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\lib \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\net \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\xml \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\kernel\jdesaw \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\lib\cache \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\as400 \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\db \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\proxy \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\xml\test \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\actions \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\db \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\filters \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\gui Copyright © 2008. Oracle.Rev0 Definition 395 .Chapter 20. GA. Chapter 20. Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\launchers \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\gui\tagext \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \util\imagegenerator \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \workflow\DesignEngine \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \workflow\monitoring \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\workflow\util \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\serverproxy \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\test \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtse \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtsm \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtsr \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\xtse\adapters \JDEdwards\E900\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\xtsr\adapters \JDEdwards\E900\DDP\system\IncludeV\unicode \JDEdwards\E900\DDP\system\Locale\Iconv \JDEdwards\E900\DDP\system\Locale\Uconvtab \JDEdwards\E900\DDP\system\Locale\Xml \JDEdwards\E900\DDP\system\OWPatrol\owkm \JDEdwards\E900\DDP\system\OWPatrol\owkm\images \JDEdwards\E900\DDP\system\OWPatrol\owkm\km \JDEdwards\E900\DDP\system\OWPatrol\owkm\psl \JDEdwards\E900\DDP\system\Resource\cidfont \JDEdwards\E900\DDP\system\Resource\cmap \JDEdwards\E900\DDP\system\Resource\encoding Definition 396 GA. All rights reserved. .Rev0 Copyright © 2008. Oracle. 0 installation on a Workstation.Rev0 397 . Understanding JD Edwards EnterpriseOne Directory Structures Directory Name \JDEdwards\E900\DDP\system\Resource\font \JDEdwards\E900\DDP\system\Resource\iccprofile \JDEdwards\E900\DDP\system\Resource\truetype \JDEdwards\E900\DDP\system\Resource\font\pfm Definition Workstation General Directory Structure After you install Release 9. you should have the following local directory structure: Directory Structure \E900 \E900\Log \E900\output \E900\packages \E900\PD900 \E900\PrintQueue \E900\queues \E900\system \E900\PD900\bin32 \E900\PD900\spec \E900\PD900\spec\JDE \E900\queues\control \E900\queues\outqueue \E900\system\bin32 \E900\system\Classes \E900\system\include \E900\system\includev \E900\system\lib32 \E900\system\libv32 \E900\system\locale \E900\system\owpatrol \E900\system\resource \E900\system\Classes\samples \E900\system\includev\unicode \E900\system\locale\iconv \E900\system\locale\uconvtab \E900\system\locale\xml \E900\system\owpatrol\owkm \E900\system\owpatrol\owkm\images \E900\system\owpatrol\owkm\km Copyright © 2008. All rights reserved. GA.Chapter 20. Oracle. . Understanding JD Edwards EnterpriseOne Directory Structures Directory Structure \E900\system\owpatrol\owkm\psl \E900\system\resource\cidfont \E900\system\resource\cmap \E900\system\resource\encoding \E900\system\resource\font \E900\system\resource\iccprofile \E900\system\resource\truetype \E900\system\resource\font\pfm 398 GA.Chapter 20.Rev0 Copyright © 2008. Oracle. All rights reserved. Chapter 21.Rev0 399 . GA. All rights reserved. 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. Chapter 21. Oracle.Rev0 Copyright © 2008. All rights reserved.PS900 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 PS900DTA Database Name (list includes possible databases) JDE_PRODUCTION JDE_CRP JDE_DEVELOPMENT JDE_PRIST900 Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Selected Selected Selected Selected Blank Blank DB S Name of the machine where your database resides NTSVR Selected Blank Selected Selected Selected Selected Blank Selected Blank 400 GA.PROD Business Data .TEST Business Data . Field Data Source Name (list includes possible sources) Business Data . .CRP Business Data . Understanding Data Source Charts Business Data This chart lists the characteristics of the Business Data data source. All rights reserved.Chapter 21. Oracle.Rev0 401 . GA. Understanding Data Source Charts Copyright © 2008. Chapter 21.DV900 Central Objects .Rev0 Copyright © 2008. .PY900 Central Objects . Field Data Source Name (list includes possible sources) Central Objects . Oracle.PD900 Central Objects . All rights reserved.PS900 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) PD900 PY900 DV900 PS900 Library Name Library List Name Database Name (list includes possible databases) JDE_PD900 JDE_PY900 JDE_PS900 JDE_DV900 Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected Blank Blank DB S SQL Server 402 GA. Understanding Data Source Charts Central Objects This chart lists the characteristics of the Central Objects data source. CRP Control Tables .Rev0 403 .Test Control Tables . Oracle.PS900 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) PRODCTL CRPCTL PS900CTL TESTCTL Library Name Library List Name Database Name (list includes possible databases) JDE_PRODUCTION JDE_CRP JDE_DEVELOPMENT JDE_PRIST900 Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected Blank Blank DB S SQL Server Copyright © 2008.Chapter 21. GA.Prod Control Tables . Understanding Data Source Charts Control Tables This chart lists the characteristics of the Control Tables data source. All rights reserved. Field Data Source Name (list includes possible sources) Control Tables . Chapter 21. Oracle. Understanding Data Source Charts Data Dictionary This chart lists the characteristics of the Data Dictionary data source.900 DB S DD900 Blank Blank JDE900 Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Blank 404 GA. All rights reserved.Rev0 Copyright © 2008. 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 SQL Server Data Dictionary . . All rights reserved.Rev0 405 . Oracle. GA. Understanding Data Source Charts Logic This chart lists the characteristics of the Logic data source.Chapter 21. 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 SQL Server Name of the machine where your database resides SRN Blank SVM900 Blank Blank PS900 Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Blank Blank Copyright © 2008. Rev0 Copyright © 2008. All rights reserved.900 DB S OL900 Blank Blank PS900 Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Blank 406 GA.Chapter 21. . 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 SQL Server Object Librarian . Understanding Data Source Charts Object Librarian This chart lists the characteristics of the Object Librarian data source. Oracle. Chapter 21. Understanding Data Source Charts Language This chart lists the characteristics of the Language data source. Field Data Source Name (list includes possible sources) Valid Value for SSE Language Language – 900 For example. which applies to the SSE database on the Deployment Server. GA.Rev0 407 . French – 900. Oracle. 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_F900 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 Copyright © 2008. All rights reserved. DV900 JDELocal . Oracle. which applies to the SSE database on the Deployment Server. Understanding Data Source Charts Local This chart lists the characteristics of the Local data source.PS900 JDELocal .Rev0 Copyright © 2008. .PD900 JDELocal .Chapter 21. All rights reserved. Field Data Source Name (list includes possible sources) Valid Value for SSE Local JDELocal .PY900 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 JDEPlan900 JDECTL900 JDEDD900 JDESY900 JDEVL900 JDEOL900 JDEData900 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 408 GA. GA.900 Server Map DB S SVM900 Blank Blank Blank machinename . Understanding Data Source Charts Server Map This chart lists the characteristics of the Server Map data source.Chapter 21. All rights reserved. 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 SQL Server machinename .Rev0 409 . Oracle.900 Server Map Name of the machine where your database resides Platform type Selected Selected Selected Selected Selected Blank Copyright © 2008. . 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 SQL Server System . All rights reserved.900 DB S SY900 Blank Blank JDE900 Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Blank 410 GA.Rev0 Copyright © 2008. Understanding Data Source Charts System This chart lists the characteristics of the System data source. Oracle.Chapter 21. PY900 Versions . GA.DV900 Versions . Oracle.PD900 Versions .Chapter 21.PS900 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) PD900 PY900 DV900 PS900 Library Name Library List Name Database Name (list includes possible databases) JDE_PD900 JDE_PY900 JDE_DV900 JDE_PS900 Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Blank Blank Blank DB S Valid Value for SQL Server Copyright © 2008.Rev0 411 . Field Data Source Name (list includes possible sources) Versions . All rights reserved. Understanding Data Source Charts Versions This chart lists the characteristics of the Versions data source. 412 This page intentionally left blank . which is used by the planner environment. Oracle.900 Planner . Pathcode is one or more of the following path codes: • • • • • PY900 DV900 PS900 PD900 DEP900 Note The xxxx Local data source refers only to the local database on the Deployment Server. In the chart below.0 data sources. Local – pathcode could represent more than one data source. Stores text OLE references and image references. F00921* System . Provides UDC value descriptions for alternate languages.900 User Display Preferences GA. Major Technical Tables This chapter lists the major technical tables in the Release 9. and contain a language preference code that is translated by JD Edwards EnterpriseOne. UDC – Alternate Language Contains UDC key. depending on the number of path codes you use. All technical media storage objects (GTxxx) are listed at the end of this chart. Table F0004D* Data Source Control Tables Description Purpose UDC – Alternate Language Contains the User Defined Code (UDC) key.Chapter 22. Many tables exist in multiple data sources. .0 application tables. Some tables exist in data sources not noted here.900 Object Librarian . and whether to enable fast path. This chapter does not list any Release 9. * Specific tables in the list below reflect language information. All rights reserved. language key.Rev0 Contains one record per user with date 413 Copyright © 2008. language key. and text for headers in the F0004 table.900 Business Data Local Data Dictionary Local Object Librarian Local System . Note The Local – pathcode data source refers only to local databases that are path code specific. Stores glossary text and media objects for all languages. and text for detail in the F0005 table. initial program.900 System Local Library List – User F0092 Contains one record per user with initial menu. Provides UDC type descriptions for alternate languages. F0005D* Control Tables F00165* Business Data – xxxx Media Objects storage Data Dictionary . 900 System Local Release Master F00946 System . with the data source for system tables and the environments server path. F00945 System . F00948 System .900 Planner .900 System Local Description Purpose format. such as Object Librarian. DW prefix. F00922 System .900 System Local Environment Detail – EO Contains one record per environment. headers).Chapter 22.900 System Local Library List Master file Contains master file information for an environment. and language preference.900 Machine/ Group Identifica.900 Planner .900 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 (.900 System Local Release Data Source Map Contains information used to map a specific type of data source to a release level. This table is used with the F00050 table. Stores security attributes (one record for each user or group).900 Planner . Contains one record per release.900 System Local Library List Control Contains a list.900 Planner . data dictionary. F00924 System .900 Planner . date separator. All rights reserved.900 System Local Security Workbench table F00960 System . F00950 System .Stores a list of all workstations that intion stalled Release 8.900 Planner . F0094 System . F00942 System .900 Planner . of authorized environments.900 System Local User Install Packages Contains one record per user for each authorized package.900 Planner . 414 .900 Planner .900 System Local Release Compatibility Map Contains information used to map major release levels to determine forward and backward compatibility. or versions list data sources. with release and path code. Major Technical Tables Table Data Source Planner .DLL.9 to scheduled packGA. F00941 System .900 System Local User Display Preferences Tagfile Contains one record per user with workstation configuration name.Rev0 Copyright © 2008. F0093 System . Oracle. by user. source. Rules are applied to conditionally execute an individual task or task relationship (tree order). Provides translated text for descriptions listed in the F9005 table (ActivEra only). Groups tasks listed in the F9000 table in logical (parent/child) tree order (ActivEra only). Major Technical Tables Table Data Source System Local Description Purpose ages. Provides soft coded RDA text. Provides translated text for descriptions listed in the F9006 table (ActivEra only).Rev0 415 Copyright © 2008.900 System . F91100 F91100D* F91300 System .900 System Local Data Title Series of definitions of data titles. Provides soft coded RDA text. Provides descriptions of tasks listed in the F9000 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. F83100* System .Chapter 22.Defines the hierarchical means of eliminency ating system codes and subsequent applications which do not apply within a specified system configuration (ActivEra only).900 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. Scheduled Job Master GA. Favorites – Relationship Properties Categorizes business views on a parent/ child format. Defines which nodes (tasks) are run within a variant and the names of any tasks dynamically renamed within a variant (ActivEra only). F83110* System . All rights reserved.900 Favorites – All Descriptions Stores alternate descriptions for different languages.900 System . Gives each period number an associated description. Each row is the definition or specification of the date title. A variant performs a series of designated tasks (nodes) within a tree order defined in the F9001 table (ActivEra only). Lists Release 8. Describes the attributes of variants listed in this table. Oracle. Lists conditional statements within rules listed in the F9020 table (ActivEra only). .9 tasks (Solution Explorer only). Contains one record per error message.Chapter 22. . Similar to the F9202 table. and glossaries. and product code reporting. Contains the relational breakdown of data dictionary.900 System .900 System . a compressed description. Tip Details for Tip of the Day Data Item Master Stores tip texts and a key to modify the sequence.900 System . data item. Contains display text for each data field for language. tion Data Field Specifications Contains detailed information (specifications) for each data item. 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. All rights reserved.900 System . Helps users manipulate data sequencing. Contains data dictionary alpha descriptions for all languages. F9207 Data Dictionary Data Dictionary Local DD Error Message Informa. Oracle.900 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. Data dictionary row and column text for all languages* * The language preference code for data dictionary applies to text only.900 System . Major Technical Tables Table F91310 F91320 F91330 F91400 F91410 F91420 F91430 F91500 F91510 F9200 Data Source System .900 System .Rev0 F9212 F96021 F9603 416 Data Dictionary . Stores information from the assembly Copyright © 2008. Creates a list showing all data items belonging to a smart field template. This table is accessed whenever a data item needs to be identified. Stores a subset of selection criteria. 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. Application Header for Tip Contains application names or tools of the Day names where tips reside. Contains information for Smart Fields.900 Data Dictionary Local System .900 Stores the detail information from the definition process of package build. Used when data items descriptions requested.900 System . Used when data items descriptions requested.900 System . Text includes row and column headings.900 System . 900 Planner .900 System Local Software Package Build Detail History F9631 System . Each record is either the name of the specification file.0 administrator for deploying packages. the name of the compression directory.900 System Local Deployment Location Definitions Copyright © 2008.900 System Local Description Header Package Build Validation Tables Package Build Validation Detail Software Package Build Header History Purpose process of package build. Stores the status of the build on the operation of that record when the package is finished. F9652 System . Major Technical Tables Table F96210 Data Source System .DLL file.900 Planner . groups of groups can be defined here. F9622 System . Stores the object names. or the name of an object. GA.900 System Local Software Package Detail F9650 System . In addition. F9653 System . This table is used primarily in multitier deployment. or helps name. Holds the default information regarding all machines used by JD Edwards EnterpriseOne. foundation name. All rights reserved.900 Planner . F96225 System .900 System Local Machine Master F9651 System .900 System Local Deployment Group Header Specifies groups that can be used by the Release 9. F9654 System .900 Planner .900 System Local Contains the history record of the F96021 record.Rev0 417 .900 Planner . Stores the detail information for the assembly process of package build. Contains the history record of the software build program (P9622). Enables definition of one or more locations for deployment. F96211 System .900 Planner .Chapter 22. Oracle.900 Planner . data name. the name of a .900 System Local Machine Detail Holds specific information about each machine defined in the machine master table by record type. It stores statuses of the package each time it is built.900 Planner .900 System Local F96215 System .900 System Local Deployment Group Detail Definitions Stores the users that belong to one or more groups that were defined in the deployment header file.900 System Local Software Package Build Detail Stores the option information from the definition process of package build.900 Planner . Chapter 22.900 Planner .900 Planner .900 Planner . Oracle.900 System Local Deployment ODBC Data Source F966072 System . All rights reserved. Major Technical Tables Table F9660 Data Source System .900 System Local Deployment File Set F966071 System .900 System Local Deployment Registry F96602 System . .900 Planner .900 System Local Deployment Initialization F96606 System .900 Planner .900 Planner .900 System Local Description Task Breaks Purpose F96600 System .900 Planner .900 System Local Deployment Initialization F96605T System .900 Planner .900 System Local Deployment Features F96601 System .900 System Local Deployment Execute F96604 System .900 Deployment ODBC Data Source Attributes 418 GA.Rev0 Copyright © 2008.900 System Local Deployment Shortcut F96603 System .900 Planner .900 Planner .900 Planner .900 System Local Deployment Third Party F96605 System . UDC Merge table Contains the UDC records changed or added from release to release. Change Table – Report Dir. Change Table – Report Dir.Stores adds/changes/deletes to the Reector Template Header port Director template header table between releases.900 Planner .Rev0 419 . changes. Change Table – Smart Field Stores adds/changes/deletes to the Smart Criteria Field Criteria table between releases.900 Planner . 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. GA.900 System Local Software Update Object Detail F967611 System .900 Planner . Oracle.900 System Local Software Update Language Table F9691100 F9691400 System Local System Local Change Table – Favorites Stores adds. This table is used by the UDC merge program (R98741).900 Planner .900 System Local Impact Analysis Results F9672 System .Chapter 22. Change Table – Smart Field Stores adds/changes/deletes to the Smart Activity Field Activity table between releases.900 Planner . and deletes to favorites tables between releases.900 System Local Software Update Detail Table F96710 System .Stores adds/changes/deletes to the Reector Template Sequence port Director Template Sequence table between releases. All rights reserved. Major Technical Tables Table Data Source System Local Description Purpose F9670 System .900 System Local Software Update Pathcode Information F96761 System .900 Planner .900 System Local Software Update Master Table F9671 System . Imaging Constants Determines whether you are doing thirdparty imaging. and GA. F983051 Versions . For batch.900 F98402 Version .900 Planner .900 Environment Plan Detail ta.Rev0 Copyright © 2008. event rules. This table is used by the Data Dictionary merge program (R989200P).Lists cross-reference relationships for ships business views.900 Data Dictionary Local Error Message Pgm Call Changes By Release F9760 Data Dictionary .Lists cross-reference relationships for lationships fields in an application.Chapter 22. Contains the last location for a plan. publisher. and subscriber tables.xxx Versions Local System . Lists changes made to field specifications (F9210) between releases.900 F984021 Version .900 Planner . Contains one record per version (batch or interactive). Lists changes made to alpha descriptions of data items (F9203) between releases.900 Location Plan Detail table F984022 Version .900 Replication Plan Detail table Stores replicated plan for remote locations. and controls.xxx Versions Local Central Objects . All rights reserved. Major Technical Tables Table F9755 Data Source Data Dictionary . this table holds data selection. This table is used in the data dictionary merge process. Oracle.xxx Versions Local Version . demo data. Installation Plan Master ta. F98401 Version . Host Plan Detail table Lists the Enterprise Server and hosts for each plan (one record per plan. Cross– Reference Field Re.Lists environments for each plan. it stores processing option values.900 Processing Option Text Provides processing option text for all languages. This table is used in the data dictionary merge process. 420 . per server).900 System Local Data Field Specification Changes By Release F980011 F980021 F98101 Cross– Reference Relation. Holds ble flags for production data. F9757 Data Dictionary .900 Data Dictionary Local Data Item Alpha Description Changes by Release F9759 Data Dictionary .900 Series (OMW) F98306* F9840 Central Objects . sequencing.xxx Versions Local Versions List F982xx System . F98403 Version . For interactive.900 Data Dictionary Local Central Objects .900 System Local Planner .Contains general information for the inble stallation plan with one record per plan name (description and status). Lists changes made to error messages (F9207) between releases. and other template overrides.900 Planner .900 Planner . This table is used in the data dictionary merges. and one ble record per plan record per data source associated with that plan.900 Data Dictionary Local Description Data Item Master Changes by Release Purpose Contains the data dictionary items changed or added from release to release. Data Source Plan Detail ta.900 Planner .Lists data sources for each plan. Data Source Master Holds data source definitions. 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.Rev0 421 .900 Planner .900 Server Map Planner . Major Technical Tables Table Data Source Planner .Contains all data sources for tables.900 REP Data Sources by Environment F9860 Object Librarian Object Librarian Local Object Librarian Master ta.900 System .900 F9843T F98511 System .900 System Local Object Configuration Mas.900 Server Map Planner . and business functions that run on the server. per path code.900 Planner . All rights reserved. and specification merges. F98611 System .900 Table Conversion Scheduler F984052 Version . and foundation . This table is similar to the F9843 table. ter batch applications. Copyright © 2008. Table Conversion – JDE Scheduler Contains table conversions. Package Plan Detail table Lists packages and package definitions for each environment. and coexistent installations.900 Planner . control table merges. per location. Lists table conversion information merged in Table Conversion Scheduler from Environment Planner and Table Conversion Planner.900 Description Purpose table conversions for an upgrade.Chapter 22. Lists default data sources by environment.900 Planner . F9843 System . GA. F9861 Object Librarian Object Librarian Local F986101 System . machine name.DLL.900 System Local Contains one record for each job on the server with status information. and specification merges for upgrades.900 Server Map Planner . F984031* Version .900 Table Conversion – History Stores the logs for table conversions. updates. This table is used during installation. Log control table merges.Contains one record per object with deble scription and object type. Object Librarian – Status Detail Contains one record per object. Oracle. Each object has a server location plus locations for each person who checks it out to his machine.900 F98405 Version .900 System Local F986110 System . database.900 Language and Environment Lists language and the selected environPlan Detail table ments for each plan.900 Planner . F98404 Version . One record per data source with type. Major Technical Tables Table F986111 Data Source System . This table is used by the server package installation process (P986150). This table is used by the server package install process (P986150).Holds storage. including status.900 Server Map Planner .900 Server Map Planner .900 System Local MVS table and Data Source Holds storage. sizing.900 System Local F986152 System . location. Lists paper sizes defined for each printer. This table is used by the server package install process (P986150).Rev0 Copyright © 2008.900 Server Map Planner .900 System Local Server Transfer Package Contents Server Package Transfer Lists objects belonging to each server package. Contains the master list of all service packages. and location paraing table meters for Oracle.900 System Local Description Job Number Master Purpose Contains the next numbers table for server jobs. physical name. . and conversion program.900 System Local Printer F986161 System . F986116 System . All rights reserved. one record per printer. F986113 System .900 System Local Subsystem Job Master Contains server job records. and version. Lists the servers and path codes to which a given server package will be transferred. Lists the printer definitions. Similar to the F986115 table.900 Server Map Planner .900 System Local Business View Environmental Server Lists cached tables.900 System Local Default Printer table F986162 System .900 System Local Paper Definition 422 GA. including logical name. F98613 System .900 System Local Server Package Master F98616 System .900 System Local Table and Data Source Siz. F986151 System . Oracle. with some general information for all data sources. one record per printer.900 Server Map Planner . F986115 System . sizing. Lists default printer settings by user and environment.Chapter 22. F986150 System . and location paraSizing meters for MVS. Data Structure Templates ations Central Objects Specific. environment. F986164 System .900 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.Media Object ations Central Objects Specific. for example.Rev0 423 .FDA Specification Informa.Primary Index Header ations Central Objects Specific. host name. Holds all business-view specific information from BDA. All rights reserved.Contains summary information about ations tion each application. Contains smart field named mappings. one record per printer. Contains form design text for all languages for any generated application. Copyright © 2008. Oracle. Contains one record per interactive form.Chapter 22. Central Objects Specific. Object Librarian – Object Relationships Form Information Contains one record per business function per related object.Table Columns ations Central Objects Specific. Holds table-specific information for tables created in TDA (BOBSPEC). Reserved for future use. printer name. Major Technical Tables Table F986163 Data Source System .FDA Text Information ations Contains one record for each template. TDA – Information pertaining to the primary index. Lists printer output conversions defined for each printer.Table Header ations Central Objects Specific.Primary Index Detail ations Central Objects Specific.Event Rules – Link ations Central Objects Specific. and the status. Stores the default printer information including the user. Holds all column information for the table in TDA (DDCLMN). F9863 Object Librarian Object Librarian Local F9865 Object Librarian Object Librarian Local F98710 F98711 F98712 F98713 F98720 F98740 F98741 F98743 Central Objects Specific. F98744 F98745 F98750* F98751 F98752 Central Objects Specific.Business View Specificaations tions Central Objects Specific.Contains specifications for an applicaations tion tion. Stores header file for event rules. including online help information. type and location of printer) for each printer. Data Structure for Business Function.900 System Local Output Conversions F986165 System Shared New Default Printer Table F986167 System . TDA – All fields that make up the primary index.Event Rules – Specification Contains actual event rules detail for a ations form. Contains media object text for tools. one record per printer.Smart Field Named Mapations pings Central Objects Specific.FDA/SVR Header Informa.900 System Local Description Printer Capability Purpose Lists printer capabilities (paper orientation and size. GA. This table is used when building business functions. Central Objects Specific. F9885 System . Contains the data that ties workflows to organizational models. All rights reserved. Lists each time the package is built. F9883 System . Categorizes Composer processes. Activity Master Activity Specifications Process Activity Associations Organizational Structure Master Organizational Structure Rule Process Instance Contains workflow activity information.JDEBLC – Behavior Inations formation System . Contains the defining data for organizational models. such as group user ID and package assignment.FDA/SVR Detail Informaations tion Central Objects Specific. 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. Install Package Header Contains one record per package. Logs all transactions that take place to objects. Holds records that contain report design aid setup information. Holds records that contain the report design aid text for all languages.RDA Specification Info ations Central Objects Specific. Contains workflow activity specifications stored as event rules.900 System Local F9886 System .Contains information for deploying servtions table er packages.900 System Local Contains temporary message logging for merges.Rev0 Copyright © 2008. .RDA Text Information ations Central Objects Specific.900 System Local Install Package Build History Merge Log F9888 System .900 Planner .900 Planner . Major Technical Tables Table F98753 F98760* F98761 F98762 F9882 Data Source Description Purpose Contains summary information about each form for each application.900 Release 9. Central Objects Specific. F9887 System . such as package assignments. Activity Master – Alternat. Contains business function specifications.900 System Local Install Package Detail Contains one record per package per product code or object to be included in the package.900 System Local Checkout Log table F98825 System .Chapter 22.0 Network Loca.Contains multiple language information ive Description for the F98810 table. Contains workflow activity relationships. Contains the instances of workflow pro- 424 GA. Oracle.900 Package Deployment Scheduling Contains information for deploying client packages. 900 System – Local F98EVHDR System .900 System – Local F98950 Central Objects Specific. Deployment Location Path Code Package Deployment Scheduling Lists records with packages and help information. Oracle.900 System – Local F98892 System . All rights reserved. Contains application version information: application. and user who entered it. and the Specification Merge and Object Librarian Merge reports.Planner F98DRPUB System .Chapter 22. Lists scheduling information for a multitier environment. Data Replication Subscribers Event Detail file Defines each subscriber. Data Replication Publisher Lists definitions of published objects. Contains one record for each replicated change.Planner F98DRSUB System .Lists records for each tier with system ter and help information.900 F98CONST System .User Overrides table ations System – Local F98980 System . This table is used only for multitier deployment. Determines which path codes to update for data dictionary replication.900 System – Local Description Activity Instance Specification Merge Logging Purpose cesses.900 Server Map System .900 Server Map System .900 System – Local F98DRENV System . update. Contains logging information generated from the Specification Merge for upgrade.Planner F98DRLOG System . Stores event description and event ID.900 System .900 System – Local Deployment Location Mas.900 System . Major Technical Tables Table F98865 F98881 Data Source Control Tables System . F98BLOB System .Planner F98DRPCN System .900 Copyright © 2008.900 System . Contains the instances of workflow activities within processes. Records are deleted as subscribers are notified.900 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. 425 Event Header file GA. version. The table information is stored as a BLOB.Rev0 .Planner F98EVDTL System . Data Replication Environment Mapping table Data Replication Change Log Data Replication Pending Change Notifications Contains one record for each replicated change for each subscriber. F98891 System . This table is used only for multitier deployment. Filters events displayed in Form Design Aid (FDA) or Universal Batch Engine (UBE) design. F9889 System . Contains notes for business functions.Chapter 22.900 System – Local F98OWSEC System . Release 9. All rights reserved. Contains templates that can be used for any attachment.900 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.Rev0 Copyright © 2008. F98MOQUE System . Oracle. Data Dictionary – Glossary Contains column in data dictionary with Information descriptions of data dictionary items. Major Technical Tables Table Data Source System – Local Description Purpose This table is used for all event rules. GT98TMPL Object Librarian 426 GA. 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.0 user name and password for obtaining database user and password for certain data sources.900 System – Local F98VAR System . Contains notes for data structures. Contains notes for data structures. Contains the security tables that store the Release 9. .0 Security Templates Table of Variables Contains commonly used event rule variables.900 System – Local F98TMPL System . Chapter 23. During upgrades and cumulative updates. upgrade. upgrade and cumulative update customers. Enter D to select all default records. Enter Y to see OCM differences between the new environment and the previous environment. upgrade and cumulative update customers. • Environment Database Creation Report (R98403) This report is for installation. GA. upgrade.Rev0 427 . upgrade. Oracle. Enter Y to see all Object Configuration Manager (OCM) information for the current data selection. • Pathcode Copy (R9800942) This report is for installation. Enter Y to display all path code information for the plan(s) in the data selection. All rights reserved. JD Edwards EnterpriseOne creates reports that show detailed information about the plan and summarize the status of the environment builds. and cumulative update customers. Enter N to prevent OCM records from being displayed. 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. Installation Planner Validation Report (R9840B) Note This report is used by installation. upgrade and cumulative update customers. OCM Differences Flag Path Code Information Flag Copyright © 2008. This chapter discusses: • Installation Planner Validation Report (R9840B) This report is for installation. and cumulative update processes. Working with Reports During the installation. and cumulative update customers. additional reports summarize the status of tables merges. All processes use version XJDE0001 of this report. • Index Recreation (R9698713) This report is for installation. Review the main body of the report to verify that each data source. Upgrade users should run XJDE0005 because the update process updates only generic text. To verify. Oracle. How to Read the Report Use the Installation Planner Validation report summary section to review basic information about the installation. these users should run version XJDE0024. The environment database creation copies the System data source (previous release) to the System . The report is read and errors are processed in the same way as they are for the regular Environment Database Creation. When running against pristine data. For each environment.900 data source. machine. Setting Processing Options These processing options are the typical processing options for each version of the Environment Database Cre428 GA. The System data source is release specific.0 creates an Environment Database Creation report for each environment that is part of your plan. 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. you can choose to load either production or demonstration data. upgrade. Users performing installations and upgrades should run version XJDE0001. Working with Reports Update the Plan Status (10 – 60) Enter 30. and package build in the plan was created successfully. Users performing cumulative updates should run version XJDE0004. .Chapter 23. or cumulative update. Environment Database Creation Report (R98403) Release 9. and the types of processes run.Rev0 Copyright © 2008. All rights reserved. the number of records validated. each detail line should have the value Record Validated in the far right column. Leave this field blank. Leave this field blank. Leave this field blank.Leave this field blank. The default is Proof Mode. The default is to create all tables. If this report is called from another process. Working with Reports ation report.Enter 2. The Print Tab contains these options: Enter a 1 to only print exceptions. the system passes in this flag. The default is to print all lines. If this report is called from another process. The Update Tab contains the following options: Enter a 1 for Proof Mode or a 2 to create the Environ. Enter a Y to add records without clearing the target ta. All rights reserved. GA. The default is to print all tables. The default is to clear the target table. Enter a Y to print all tables in the report or an N to print licensed tables only. Enter the Source Environment for the database to be copied from. Leave this field blank. Enter a 1 to load Production Data or a 2 to load Demonstration Data. the system passes in this flag. Enter the source Data Source for Loading of Data. Oracle.Rev0 429 . ble. Leave this field blank. Leave this field blank. the system passes in this flag. If this report is called from another process. Enter a 1 to only copy tables that exist in the source Leave this field blank. Enter a A to recreate existing tables in data sources Leave this field blank. The default is 1. Copyright © 2008. data source. that allow automatic table creation. Enter the Data Source for the database to be created. This is used for language tables. Enter OneWorld Local. The default is not to recreate tables. The Licensing Tab contains these options: Enter a Y to create all tables or a N to create licensed tables only. Enter 2. Version XJDE0001 for Installations and Upgrades The Environment Tab contains these options: Enter the Environment for the database to be created. ment Database.Chapter 23. Enter a Y to add records without clearing the target ta. Oracle. Enter a A to recreate existing tables in data sources Leave this field blank. the system passes in this flag. tables only. that allow automatic table creation The default is not to recreate tables. All rights reserved. 430 GA. This is used for language tables. The default is to create all tables.Enter 2. without clearing the target table. If this report is called from another process. ment Database. Leave this field blank.Chapter 23. data source The default is to copy all tables. print licensed tables only. Enter the Data Source for the database to be created. The default is Proof Mode. The Licensing Tab contains these options: Enter a Y to create all tables or an N to create licensed Leave this field blank. Enter the source Data Source for Loading of Data. Leave this field blank. the system passed in the Source Environment. Enter a Y to print all tables in the report or an N to Leave this field blank. Enter the Source Environment for the database to be copied from. Working with Reports Version XJDE0004 for Updates The Environment Tab contains these options: Enter the Environment for the database to be created. If this report is called from another process.Rev0 Copyright © 2008. Leave this field blank. Leave this field blank. If this report is called from another process. The default is to clear the target table. Enter 1. . The Update Tab contains these options: Enter a 1 for Proof Mode or a 2 to create the Environ. Enter a 1 to only copy tables that exist in the source Leave this field blank. Enter a 1 to load Production Data or a 2 to load Demonstration Data Leave this field blank. the system passes in the data source. The Print Tab contains this option: Enter a 1 to only print exceptions. The default is to load production data. The default is to print all lines. The default is to print all tables.Enter N to indicate you do not want to add records ble. The Print Tab contains these options: Enter a 1 to only print exceptions. Leave this field blank. The Update Tab contains these options: Enter a 1 for Proof Mode or a 2 to create the Environ. This is used for language tables. the system passes in this flag. Enter a A to recreate existing tables in data sources Enter A. All rights reserved. the system passes in the data source. Working with Reports Version XJDE0024 for Running Pristine Data The Environment Tab contains these options: Enter the Environment for the database to be created. Leave this field blank. that allow automatic table creation. The default is to print all tables. The default is to copy all tables.Enter 2.Chapter 23. ment Database. data source. The default is not to recreate tables. Enter 2. Oracle. Enter OneWorld Local. ble. licensed tables only. The default is to load production data. Leave this field blank. The default is to create all tables. Enter the source Data Source for Loading of Data. Copyright © 2008. If this report is called from another process. Enter a Y to add records without clearing the target ta. the system passes in the Source Environment . Enter a Y to print all tables in the report or a N to print Leave this field blank. If this report is called from another process. Enter the Source Environment for the database to be copied from. Enter a 1 to load Production Data or a 2 to load Demonstration Data. 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. Leave this field blank. Leave this field blank. Enter the Data Source for the database to be created. GA. If this report is called from another process. The default is to print all lines. Enter a 1 to only copy tables that exist in the source Leave this field blank. The default is Proof Mode.Rev0 431 . The default is to clear the target table. Chapter 23. Displays the data source toward which this member points. Record Insert. Shows the JD Edwards EnterpriseOne product code for the database listed in the Member Description column. All rights reserved. The report includes a status for each table: • • • Tables that have been created correctly have a status of Success. Shows whether tables are being created for this database. Working with Reports How to Read the Report Review the reports to make sure the environments were created and configured successfully. Tables that had errors have a status of 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. Oracle.Rev0 Copyright © 2008. or No Action. . Shows whether the table was copied with data. To confirm successful table creation. Displays any errors or warnings associated with the source data source. Errors and How to Resolve Them A report occasionally lists a status of Failure for tables that are created successfully. Displays the number of records inserted. Displays the full name of the database being created. you could receive failures for some tables. Displays the alphanumeric name of the database. Failure. Displays one of the following statuses for the table creation: Success. verify that the following tables were created successfully: • • • • • F0007Z1 F00092 F0086 F03B11 F03B14 432 GA. 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. Create Table. During an upgrade or cumulative update. Record Failure. The Environment Database Creation report does not have a cover page. Tables can have a status of No Action. These failures are generally due to problems creating indices and are not critical for the successful installation of the software. Displays any errors or warnings associated with the target data source. Chapter 23. GA. 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. These warnings are normal and you can ignore them. Oracle. All rights reserved. This status is accompanied by source and target data source warnings for these tables to explain why no action was taken. 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.Rev0 433 . 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. replacing the path code names in those items. F00821.Chapter 23.Rev0 Copyright © 2008. All rights reserved. and often occurs for the following tables: UDC tables F0004 and F0005 Menu tables F0082. . It compares database indexes versus Release 9. If you run the program in Update mode. It also copies package. 434 GA. Oracle.inf and records in the package definition tables F9603. Index Recreation (R9698713) The R9698713 program is run from Batch Versions after an install or upgrade. DV900 and TS900). it recreates incorrect indexes. F9631. 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 F0084 If you load multiple environments that share the same mappings (for example. F96021 and F96215. It copies the directory structure of the existing path code on the Deployment Server. F0083. The second environment (TS900) 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. 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. the first environment loaded (DV900 in this case) lists the tables with a Success status. The No Action status and Existing Table warning for the second (TS900) environment are normal.0 index specifications in F98712 and F98713. 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.Chapter 24. In all cases. To remove the Platform Pack. GA.Rev0 435 . Oracle. The Uninstaller program restricts you from uninstalling a mandatory component without also removing all associated optional components that were previously installed. which are provided in this document. Uninstalling the Software This chapter includes these tasks: • • • • • • Understanding the Uninstallation Process Uninstalling the Software from the Workstations Uninstalling the Deployment Server Dropping SQL Server Databases Removing Database Users for SQL*Server Uninstalling the Platform Pack Understanding the Uninstallation Process Because the Deployment Server is only installed on Microsoft Windows-based machines. the installation and upgrade processes do not automatically remove any JD Edwards EnterpriseOne databases. you can uninstall it by using Add/Remove programs on the machine on which the installation was initially run. All rights reserved. you must run a separate platform-specific uninstallation program as described in this guide. 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. All rights reserved. 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. Oracle. If error messages say that you cannot remove certain objects. The uninstallation program performs the following tasks: • • • • • • • • • Deletes the JD Edwards program group. Unregisters services. Deletes jde*. and then rerun the uninstallation program. Removes the LOCAL data source. Note You can ignore messages about security that appear during the uninstallation procedure.Chapter 24. make sure that you have not selected Read Only on the object property sheet.* from the root directory. Removes the uninstall directory. Deletes the path. . 436 GA.Rev0 Copyright © 2008. Deletes the installation directory tree. Increments licenses on the Deployment Server. Deletes the registry entry. Chapter 24. choose the components you wish to uninstall and click Next. click Next. summary information. On JD Edwards | EnterpriseOne Deployment Server Installer. summary information. On JD Edwards | EnterpriseOne Deployment Server Installer. 4. Oracle. the program is removed from the machine and also from the list of installed programs. verify the uninstallation successfully complete and click Finish. Uninstalling the Software Uninstalling the Deployment Server When you run the InstallShield Wizard to uninstall the Deployment Server. GA. On the Microsoft Windows-based machine which you initially installed the Deployment Server. All rights reserved. review the selections and click Next to begin the uninstallation. 5. On JD Edwards | EnterpriseOne Deployment Server Installer. 3. feature selection.Rev0 437 . 1. Copyright © 2008. On JD Edwards | EnterpriseOne Deployment Server Installer. navigate to Add/Remove Programs and click the Change/Remove button for this program: JD Edwards | EnterpriseOne Deployment Server 2. JD Edwards EnterpriseOne Component Foundation SQL*Server Database Name JDE900 JD Edwards EnterpriseOne Purpose System Object Librarian Data Dictionary Server Map Production JDE_PD900 Production Object Specifications • • JDE_PRODUCTION Central Objects Versions Production Data Production Control Tables Pristine JDE_PS900 Pristine Object Specifications • • Central Objects Versions JDE_PRIST900 Pristine Data Pristine Control Tables 438 GA. these databases are not automatically removed by the JD Edwards EnterpriseOne uninstallation program. and then you subsequently reinstall JD Edwards EnterpriseOne 9. You should have a DBA for your RDBMS manually remove any unused databases listed in the table below. By design.Rev0 Copyright © 2008. .0.0 Installation of the Platform Pack on your Enterprise or Database Server for your JD Edwards EnterpriseOne installation. If you fail to drop the databases before you run the Platform Pack installer. or from a previous JD Edwards EnterpriseOne installation. This is the list of databases that were created by the JD Edwards EnterpriseOne 9. This section lists the SQL Server databases that must be manually dropped by a DBA. All rights reserved. Uninstalling the Software Dropping SQL Server Databases Warning For uninstalling.Chapter 24. Oracle. the Microsoft Windows operating system will delete the databases the next time the machine is restarted. you must drop the SQL Server databases that were created by the JD Edwards EnterpriseOne installer prior to uninstalling the Platform Pack. Chapter 24.Rev0 439 . GA. Uninstalling the Software JD Edwards EnterpriseOne Component Development SQL*Server Database Name JDE_DV900 JD Edwards EnterpriseOne Purpose Development Object Specifications • • Central Objects Versions JDE_DEVELOPMENT Development Data Development Control Tables Prototype JDE_PY900 CRP Object Specifications • • Central Objects Versions JDE_CRP CRP Data CRP Control Tables Copyright © 2008. All rights reserved. Oracle. Chapter 24. Uninstalling the Software Removing Database Users for SQL*Server This section lists the database users that must be manually dropped by a DBA for your RDBMS system. . Oracle. or from a previous JD Edwards EnterpriseOne installation. This is the list of users that were created by the JD Edwards EnterpriseOne 9. All rights reserved. Database Type System Object Librarian Data Dictionary Database User SY900 OL900 DD900 SVM900 You should also remove these users of the JD Edwards EnterpriseOne system: • • • • • • Production jdedba jde applead sysadmin produser devuser PD900 PRODDTA PRODCTL Note For your installation. You should have a DBA for your RDBMS manually remove any unused items listed in the table below. the proddta and prodctl users may be needed for a previous release. The database users are not automatically removed by the JD Edwards EnterpriseOne uninstallation program.Rev0 Copyright © 2008.0 Installation of the Platform Pack on your Enterprise or Database Server for your JD Edwards EnterpriseOne installation. Pristine PS900 PS900DTA PS900CTL Development DV900 TESTDTA TESTCTL 440 GA. the testdta and testctl users may be needed for a previous release. All rights reserved. the crpdta and crpctl users may be needed for a previous release. Prototype PY900 CRPDTA CRPCTL Note For your installation. GA. Copyright © 2008. Oracle.Rev0 441 . Uninstalling the Software Database Type Database User Note For your installation.Chapter 24. Chapter 24. the uninstallation cannot be guaranteed to be complete and. Click Next. On the Microsoft Windows-based machine which you initially installed the Platform Pack. locate and click the Change/Remove button for this program: JD Edwards | EnterpriseOne Platform Pack 2.Rev0 Copyright © 2008. 442 GA. as a result.properties. On JD Edwards | EnterpriseOne Platform Pack Uninstaller. On JD Edwards | EnterpriseOne Platform Pack Uninstaller. 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. 1. 4. Note To avoid the possibility of removing valuable customer data. such as vpd. navigate to Add/ Remove Programs to uninstall the Platform Pack. subsequent reinstallation of JD Edwards EnterpriseOne may be hindered. choose the components you wish to uninstall. The uninstall wizard does not drop the databases or their users. On JD Edwards | EnterpriseOne Platform Pack Uninstaller. summary information. verify the uninstallation successfully complete and click Finish. On Add/Remove Program. 6. feature selection. click Next. It is also very important you drop your SQL Server databases prior to running the uninstaller. as specified in the warning in the section entitled: Dropping SQL Server Databases . All rights reserved. 5. On JD Edwards | EnterpriseOne Platform Pack Uninstaller. The JD Edwards EnterpriseOne Uninstaller program performs requisite clean up tasks in the Microsoft Windows registry and also makes changes in common shared files. . If you manually remove the software. Oracle. review the selections and click Next to begin the uninstallation. summary information. the uninstall wizard only removes the Enterprise Server runtime code. 3. microsoft.sql to Support SQL Server and SSE ODBC You must run the instcat.sql SQL script. Reference the following Knowledge Base article: • How to Run INSTCAT.Appendix A: Using Instcat.sql SQL script runs stored procedures against your SQL Server or SSE database instance in order to bring them to the most current level.asp Running the instcat.com/library/default. The Microsoft articles referenced above provide the operational theory and requirements for running the instcat. Note The server name switch (-S) may also include the instance name. Oracle.sql SQL script against the master MicroSoft Database Engine (SSE) database on your Deployment Server and also against the master SQL Server database on your JD Edwards EnterpriseOne database server. and where -S specifies the Server name of the SQL server. and optionally where –E specifies the integrated logic to the SQL Server database.sql SQL script is supplied by your installation of the latest version of SQL Server or Microsoft Data Access Component (MDAC).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. and where –P specifies the corresponding password. Use this command line to call the instcat.sql file. Copyright © 2008.Rev0 443 .sql SQL Script The instcat. Server_name\instance_name. You should sign off from EnterpriseOne and close SQL Server Enterprise Manager. The instcat. ISQL -Usa -Psa_password -Sserver_name -ilocation\Instcat. Caution As recommend by Microsoft. All rights reserved.sql SQL script. Refer to the detailed procedures provided by Microsoft on their web site.asp?url=/library/en-us/howtosql/ht_6_odbcht_9ylw. and where -i specifies the full path to the instcat. For example. GA.sql SQL script.sql where –U specifies the UsereID. you must not have any open connections to the SSE database when running the instcat. 444 This page intentionally left blank . All rights reserved. Oracle. Copyright © 2008. GA.Appendix B: Understanding SQL Server Databases This appendix presents a diagram of the JD Edwards EnterpriseOne relationships with the SQL Server databases.Rev0 445 . 446 This page intentionally left blank .