Beruflich Dokumente
Kultur Dokumente
January 2008
Installation Guide for Oracle on Microsoft Windows Copyright 2008, Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Open Source Disclosure Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation. The following open source software may be used in Oracle's PeopleSoft products and the following disclaimers are provided. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED "AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Table of Contents
1. Understanding JD Edwards EnterpriseOne ........................................................................... 1 Understanding This Guide ................................................................................................ 2 Understanding the Installation Process ................................................................................ 3 Understanding the Deployment Server Installation ........................................................ 4 Understanding the Platform Pack Installation ............................................................... 4 Understanding the Installation Planner ........................................................................ 4 Understanding Installation Workbench ........................................................................ 5 Understanding Data Configuration Workbench ............................................................. 5 Understanding the Workstation Installation .................................................................. 6 Considering Additional Factors .......................................................................................... 7 Accessing Minimum Technical Requirements .............................................................. 7 Using JD Edwards EnterpriseOne Support ................................................................... 7 Understanding Documentation Conventions ................................................................. 7 Documentation Updates ................................................................................... 7 Tips .............................................................................................................. 8 Fonts and Type Styles ...................................................................................... 8 Hyperlinks ..................................................................................................... 8 Working With the Customer Checklist ................................................................................ 9 Environments Overview ................................................................................................. 10 Understanding Environments ................................................................................... 10 Planner Environment (JDEPLAN) ............................................................................ 11 Planner Pathcode .......................................................................................... 11 Planner Database .......................................................................................... 11 Pristine Environment (PS812) ................................................................................. 12 Deployment Environment (DEP812) ......................................................................... 12 Development Environment (DV812) ......................................................................... 12 Prototype Environment (PY812) .............................................................................. 12 Production Environment (PD812) ............................................................................ 12 Additional Considerations ....................................................................................... 13 Push Installation ........................................................................................... 13 Cluster Software Options ................................................................................ 13 Web-Based Options ....................................................................................... 13 Release History .................................................................................................... 13 Language Process Overview ............................................................................................ 14 Language Architecture ........................................................................................... 14 Base Language ............................................................................................. 14 Alternate Language Components ...................................................................... 14 Language Preference Codes ............................................................................ 15 Database Character Set and Code Page Considerations ................................................. 15 Unicode ...................................................................................................... 15 Code Page Settings ........................................................................................ 16 Oracle Code Page Settings ...................................................................... 16 Workstations and Deployment Server ....................................................... 16 National Language Support ..................................................................................... 17 Single-Byte and Double-Byte Considerations ..................................................... 17 Font Considerations ....................................................................................... 18 User Display Preferences ................................................................................ 18 2. Before You Begin the Installation ....................................................................................... 19 Verifying Software and Hardware Requirements ................................................................. 19 Verifying the Disk Space Requirements ............................................................................. 20
GA.Rev8 1/7/2008
3. Working with the Deployment Server ................................................................................. 21 Installing the Deployment Server ..................................................................................... 22 Downloading and Installing the Latest Software .................................................................. 31 Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server ........................................................................................................................... 31 Installing JDBC Drivers for SQL Server 2000 ............................................................ 32 Installing the Latest Planner Update .......................................................................... 33 Troubleshooting Deployment Server Installation ................................................................. 36 4. Working with the Platform Pack ........................................................................................ 37 Understanding the Platform Pack ..................................................................................... 38 Configuring the Enterprise Server Prior to Installing the Platform Pack ................................... 39 Setting Up NLS_LANG Parameter for Oracle ............................................................ 39 Enabling Remote Connections for Oracle .................................................................. 40 Setting Up and Verifying the Hosts File ..................................................................... 42 Special Consideration for Oracle 11g on Windows .............................................................. 43 Verifying Code Page Settings for Oracle ............................................................................ 43 Understanding the Platform Pack Installation ..................................................................... 45 Installing the Platform Pack ............................................................................................ 46 Running the JD Edwards EnterpriseOne Platform Pack Installer ..................................... 47 Custom Mode Feature Selection ............................................................................... 50 Database Options .................................................................................................. 52 Oracle - Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) or Database only ................................................................................................... 53 Oracle - Enterprise Server Only (Different Machine from Database Server) ...................... 55 Review the Legacy Database Warning Panel .............................................................. 56 Concurrent Users .................................................................................................. 57 Review the Summary Information Panel and Complete the Installation ............................ 59 Verifying the Platform Pack Log File ........................................................................ 59 Troubleshooting Platform Pack Installation ........................................................................ 60 Installer Will Not Start or Complete (Invalid vpd.properties) ......................................... 61 Business Data and Control Tables Already Exist ......................................................... 62 Business Data and Control Tables Do Not Exist .......................................................... 63 Business Data or Control Tables Tablespaces Reported As Existing When They Do Not Exist ........................................................................................................................... 64 System Database Not Detected ................................................................................ 64 Foundation Files Do Not Exist ................................................................................. 66 Rerunning the JD Edwards EnterpriseOne Platform Pack Installer .......................................... 67 Enterprise Server .................................................................................................. 67 Database Server .................................................................................................... 67 Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server ......... 68 Working with Database Security ...................................................................................... 69 5. Working with Installation Planner ..................................................................................... 71 Understanding Installation Planner ................................................................................... 72 Language Information ............................................................................................ 73 Location Information ............................................................................................. 73 Deployment Server Information ............................................................................... 73 Enterprise Server Information .................................................................................. 73 JD Edwards EnterpriseOne HTML Web Server Information .......................................... 74 Data Source Information ......................................................................................... 74 Environment Information ........................................................................................ 75 Working with JD Edwards EnterpriseOne Software Requirements .......................................... 75 Reviewing Installation Planner Processing Options .............................................................. 76 Assumptions About Reviewing Installation Planner Processing Options .......................... 76 Accessing Processing Options ................................................................................. 76 Choosing Processing Option Values ......................................................................... 77 vi GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.
Specifying the Prompt Mode ........................................................................... 78 Specifying the Process Mode ........................................................................... 79 Specifying the Default Mode ........................................................................... 80 Verifying Status Change Values Have Not Changed ............................................ 82 Specifying Plan Completion Processes .............................................................. 83 Specifying Replication Options ........................................................................ 85 Specifying Remote Location Package Push Options ............................................. 87 Working with a Typical Installation Plan ........................................................................... 89 Assumptions About Defining a Typical Installation Plan .............................................. 89 Starting Installation Planner .................................................................................... 90 Entering a Plan Description ..................................................................................... 91 Entering Location Information ................................................................................. 92 Entering Deployment Server Information ................................................................... 93 Entering Enterprise Server Information ..................................................................... 95 Entering HTML Web Server Information .................................................................. 98 Selecting Default Environments ............................................................................. 102 Finalizing the Installation Plan ............................................................................... 103 Concluding the Planner Validation Report ............................................................... 104 Creating a Custom Installation Plan ................................................................................ 105 Understanding a Custom Installation Plan ................................................................ 106 Starting Installation Planner .................................................................................. 107 Entering a Plan Description ................................................................................... 108 Entering Location Information ............................................................................... 110 Entering Deployment Server Information ................................................................. 111 Entering Enterprise Server Information ................................................................... 113 Enter Data Source Information for Server Map ......................................................... 115 Entering HTML Web Server Information ................................................................ 116 Entering Data Server Information ........................................................................... 121 Entering Shared Data Source Information ................................................................ 123 Specifying (Custom or Default) Shared Data Source Setup Information ................. 123 Verifying the Data Source for Data Dictionary .......................................... 124 Verifying the Object Librarian Data Source .............................................. 125 Verifying the System Data Source .......................................................... 126 Working with Environment Setup .......................................................................... 127 Understanding Environment Setup ................................................................. 127 Setting Up Environments .............................................................................. 128 Adding a Custom Environment .............................................................. 129 Selecting an Environment ..................................................................... 130 Specifying Environment Data Load Parameters ......................................... 131 Selecting Languages ............................................................................ 132 Working with Environment Data Sources ........................................................ 133 Understanding Environment Data Sources ............................................... 133 Selecting an Environment Data Source Setup Option ................................. 133 Setting Up the Data Source for Business Data ........................................... 134 Setting Up the Data Source for Central Objects ......................................... 135 Setting Up the Data Source for Control Tables .......................................... 137 Verifying the Data Dictionary Data Source .............................................. 138 Verifying the Data Source for Versions ................................................... 139 Adding a Remote Location ................................................................................... 140 Finalizing the Installation Plan ............................................................................... 141 Concluding the Validation Planner Report ............................................................... 142 Deleting Machines from an Installation Plan ..................................................................... 143 6. Working With Installation Workbench ............................................................................. Understanding Workbench Components .......................................................................... Verifying the Network Share on the Deployment Server ............................................. Loading Data (Demo Data and Production Data) ....................................................... Creating the Job Queue ........................................................................................ 145 146 147 148 152
GA.Rev8 1/7/2008
vii
Working with Unattended Workbench Mode .................................................................... Selecting Attended or Unattended Workbench Mode ................................................. Setting a Task Break in Unattended Workbench Mode ............................................... Starting Installation Workbench ..................................................................................... Working With Initial Tasks Workbench ........................................................................... Changing the Status of Initial Tasks Workbench ....................................................... Configuring Your Locations .......................................................................................... Configuring Your Data Sources ..................................................................................... Configuring Your Environments .................................................................................... Using Machine Workbench ........................................................................................... Using the Package Workbench ...................................................................................... Using Remote Location Workbench ............................................................................... Configuring Remote Locations .............................................................................. Finishing Installation Workbench ................................................................................... Updating Oracle Database Statistics ................................................................................ 7. Working With Data Configuration Workbench ................................................................. Understanding Data Configuration Workbench ................................................................. Data Configuration Process ................................................................................... Components and Tables that are Updated by Data Configuration Workbench ................. Adding a Data Configuration Plan .................................................................................. Running a Data Configuration Plan ................................................................................ Troubleshooting Data Configuration Workbench Installation ............................................... 8. Working With the Enterprise Server ................................................................................ Verifying the Release 8.12 Enterprise Server Installation Using PORTTEST .......................... Starting Network Services on the Enterprise Server ........................................................... Stopping Network Services on the Enterprise Server .......................................................... Working with OCM Generation ..................................................................................... Understanding OCM Mappings ............................................................................. Understanding Data Source Setup .......................................................................... Understanding OCM Creation ............................................................................... Understanding Database Data Sources ............................................................ Understanding Logic Data Sources ................................................................. Understanding OCM Customization ....................................................................... Understanding Data Classes .......................................................................... Creating a New Data Class ............................................................................ Modifying the Data Source Template .............................................................. Associating Table Data Classes ...................................................................... Setting Up a Printer on the Enterprise Server .................................................................... Adding a New Printer .......................................................................................... Defining a Default Printer ..................................................................................... 9. Installing the Workstations for Developers and System Administrators ................................ Understanding Workstation Installation ........................................................................... Preparing for Workstation Installation ............................................................................. Understanding Workstation Installation ........................................................................... Understanding Workstation Installation Methods ...................................................... Working with Interactive Mode ..................................................................... Creating a Desktop Shortcut .................................................................. Using a Shared Drive ........................................................................... Working with Silent Mode ............................................................................ Working with Push Mode ............................................................................. Understanding Third-Party Products ....................................................................... Understanding User Profiles and Languages ..................................................................... Working with the Workstation JDE.INI on the Deployment Server ....................................... Understanding the Workstation JDE.INI on the Deployment Server .............................. Modifying the Workstation JDE.INI on the Deployment Server ................................... viii GA.Rev8 1/7/2008
154 154 154 156 157 157 159 160 161 162 163 164 165 166 166 167 168 168 169 171 172 174 177 177 178 178 179 179 179 180 180 180 180 181 181 181 181 182 182 188 191 191 192 193 193 193 193 194 195 196 196 196 197 197 197
10. Understanding Media Object Queues .............................................................................. 199 Modifying Media Object Queues .................................................................................... 199 Specifying the Help Location ........................................................................................ 200 11. Performing Post Installation Tasks ................................................................................. 203 Understanding Post Installation Tasks ............................................................................. 203 Setting Up Microsoft Windows Security on Release 8.12 Directories .................................... 204 Setting Security on the Files within the Client Directory ............................................. 204 Setting Security on the Pathcode Directory ............................................................... 205 Setting Security on the Database Directory ............................................................... 205 Setting Security on the Data Dictionary Directory ..................................................... 205 Setting Security on the Helps Directory ................................................................... 206 Setting Security on the Media Object Directory ......................................................... 206 Setting Security on the Planner Directory ................................................................. 206 Setting Security on the Print Queue Directory ........................................................... 206 Setting Security on the System Directory ................................................................. 207 Using the Adobe SVG Viewer on Web Clients ................................................................. 208 Understanding Task Word Search Tables ......................................................................... 209 Building Task Word Search Tables ......................................................................... 209 Setting Up Solution Explorer ......................................................................................... 210 Setting Up Solution Explorer HTML Documentation Path .......................................... 210 Setting Up the Home Page for Solution Explorer ....................................................... 210 Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications .......... 212 Adding Vertex Quantum Directory Information to the Microsoft Windows Server Path .... 213 Configuring the Release 8.12 Database Connections for Vertex Quantum Tax Applications 214 Mapping Objects to the Enterprise Server ................................................................ 215 Understanding the Autopilot Scripting Tool ............................................................. 216 Configuring Autopilot for the Oracle Database ................................................. 216 Testing the Vertex Quantum Connection from Release 8.12 ........................................ 221 Enabling CRM Functionality ......................................................................................... 223 Enabling CRM on the CRM Mobile Client ............................................................... 223 Enabling CRM on the Enterprise Server .................................................................. 224 12. Working With Signon Security ...................................................................................... Setting Up Signon Security ........................................................................................... Setting up Security Overrides for Package Build ............................................................... Enabling Server-Side Signon Security ............................................................................. Enabling Client-Side Signon Security ............................................................................. Setting Up JD Edwards EnterpriseOne Single Sign-on ....................................................... 13. Building and Testing Packages ....................................................................................... Understanding Packages ............................................................................................... Installing Application Fixes .......................................................................................... Updating the System Path ............................................................................................. Reviewing Pre-Package Build Issues ............................................................................... Verifying Available Space in DBMS ...................................................................... Verifying Specific UBEs are Mapped Locally .......................................................... Verifying the OCM Mapping ................................................................................. Deleting the BUSOBJ Directories .......................................................................... Verifying the F9631 Table .................................................................................... Verifying the Server-Side Settings .......................................................................... Configuring the Enterprise Server for Simultaneous Builds ......................................... Adding a Security Override for Running Package Build .............................................. Adding a System User for the Central Objects Data Source Owner ....................... Adding an Override for an EnterpriseOne User Running Package Build ................. Reviewing Troubleshooting Tips .................................................................................... 227 228 231 232 232 233 235 235 236 236 238 239 239 240 240 240 241 241 242 242 242 243
GA.Rev8 1/7/2008
ix
User Tips ........................................................................................................... Deployment Tips ................................................................................................ Building an Alternate Language Package ......................................................................... Package Build Considerations ............................................................................... Package Deployment Considerations ...................................................................... 14. Installation Utilities ...................................................................................................... Revalidating Software Protection Codes .......................................................................... Revalidating the Deployment Server ....................................................................... Revalidating Workstations .................................................................................... Granting Disk and Registry Access for Microsoft Windows Workstations .............................. Granting Non-Privileged Access to Disk for Microsoft Windows ................................. Granting Access to the Software Installation Directory ............................................... Granting Nonprivileged Access to the Microsoft Windows Registry ............................. 15. Troubleshooting ........................................................................................................... Using the PORTTEST Checklist .................................................................................... Resolving Data Errors .................................................................................................. Planner Update Special Instructions ................................................................................ Special Instructions for All ................................................................................... Special Instructions for OCX Registration ................................................................ Orphan Users ............................................................................................................. 16. Creating a Remote Installation Plan ............................................................................... Understanding Remote Installation Plans ......................................................................... Starting Installation Planner .......................................................................................... Entering Information in Installation Planner ..................................................................... Entering Plan Location Information ................................................................................ Specifying a Deployment Server .................................................................................... Entering Deployment Server Information ................................................................. Concluding Deployment Server Setup ..................................................................... Specifying an Enterprise Server ..................................................................................... Entering Enterprise Server Information ................................................................... Entering Enterprise Server Data Source Information .................................................. Specifying Custom or Default Data Source Information ...................................... Entering the Oracle Connect String ................................................................. Verifying Custom Server Map Source Information ............................................ Adding Another Enterprise Server .................................................................. Entering HTML Web Server Information ........................................................................ Entering Data Server Information ................................................................................... Entering Shared Data Source Information ........................................................................ Specifying (Custom or Default) Shared Data Source Setup Information ......................... Verifying the Data Dictionary Data Source .............................................................. Verifying the Object Librarian Data Source .............................................................. Verifying the System Data Source .......................................................................... Setting Up Environments .............................................................................................. Environments ..................................................................................................... Adding a Custom Environment .............................................................................. Selecting an Environment ..................................................................................... Replicating Information to Remote Locations ................................................................... Setting Up Data Sources for Environment ........................................................................ Beginning the Data Source Setup for Environment .................................................... Setting up the Data Source for Business Data ........................................................... Verifying the Data Source for Control Tables ........................................................... Select Another Environment .................................................................................. Concluding the Remote Installation Plan Setup ................................................................. Finalizing the Installation Plan ....................................................................................... Concluding the Validation Planner Report ....................................................................... x GA.Rev8 1/7/2008
243 244 246 246 246 249 249 249 250 250 251 251 252 253 253 256 256 256 256 257 259 260 261 262 263 264 264 266 266 266 268 268 268 269 270 271 276 278 278 278 279 280 281 281 282 283 283 286 286 286 287 288 290 291 291
17. Adding a Server to an Existing Configuration .................................................................. Assumptions about Adding a Server to an Existing Installation Plan ..................................... Starting Installation Planner .......................................................................................... Entering a Plan Description ........................................................................................... Entering a Plan Location .............................................................................................. Selecting Additional Server Types .................................................................................. Entering Deployment Server Information ......................................................................... Specifying an Enterprise Server ..................................................................................... Entering Enterprise Server Information ................................................................... Entering Enterprise Server Data Source Information .................................................. Specifying Custom or Default Data Source Information ...................................... Entering the Oracle Connect String ................................................................. Verifying Custom Server Map Data Source Information ..................................... Adding another Enterprise Server ................................................................... Entering HTML Web Server Information ........................................................................ Entering Data Server Information ................................................................................... Entering Shared Data Source Information ........................................................................ Specifying (Custom or Default) Shared Data Source Setup information ......................... Verifying the Data Dictionary Data Source .............................................................. Verifying the Object Librarian Data Source .............................................................. Verifying the System Data Source .......................................................................... Setting Up Environments .............................................................................................. Adding a Custom Environment .............................................................................. Selecting an Environment ..................................................................................... Specifying Environment Data Load Parameters ......................................................... Selecting Languages ............................................................................................ Setting Up Environment Data Sources ............................................................................. Selecting an Environment Data Source Setup Option ................................................. Setting Up the Data Source for Business Data ........................................................... Setting Up the Data Source for Central Objects ......................................................... Setting Up the Data Source for Control Tables .......................................................... Verifying the Data Source for Versions ................................................................... Finalizing the Installation Plan ....................................................................................... Concluding the Validation Planner Report ....................................................................... Configuring Additional Servers ..................................................................................... 18. Creating a Language-Only Installation Plan .................................................................... Understanding Language-Only Installation Plans .............................................................. Reviewing Requirements for a Language Installation ......................................................... Installing Languages on the Deployment Server ................................................................ Running Installation Planner ......................................................................................... Accessing Installation Planner ............................................................................... Entering Information into Installation Planner ........................................................... Selecting Custom or Default Parameters .................................................................. Selecting an Environment ..................................................................................... Selecting a Language ................................................................................................... Running Installation Workbench .................................................................................... Verifying Enterprise Server Requirements ....................................................................... Verifying Workstation Requirements .............................................................................. Completing the Language Installation ............................................................................. Building and Deploying Alternate Language Packages ....................................................... 19. Understanding JD Edwards EnterpriseOne Directory Structures ....................................... Deployment Server Directory Structure ........................................................................... Language Directory Structure ........................................................................................ Enterprise Server Directory Structure .............................................................................. Workstation General Directory Structure ......................................................................... Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008
295 295 297 298 299 301 302 304 304 306 306 306 308 308 309 314 317 317 318 319 320 321 322 323 324 325 326 326 326 328 330 331 332 333 334 337 338 338 339 343 343 344 345 346 347 348 348 348 348 349 351 351 355 355 371 xi
20. Understanding Data Source Charts ................................................................................ Business Data ............................................................................................................. Central Objects ........................................................................................................... Control Tables ............................................................................................................ Data Dictionary .......................................................................................................... Logic ........................................................................................................................ Object Librarian .......................................................................................................... Language ................................................................................................................... Local ........................................................................................................................ Server Map ................................................................................................................ System ...................................................................................................................... Versions ....................................................................................................................
373 374 375 376 377 378 379 380 381 382 383 384
21. Major Technical Tables ................................................................................................. 385 22. Working with Reports ................................................................................................... Installation Planner Validation Report (R9840B) ............................................................... Setting Processing Options .................................................................................... How to Read the Report ....................................................................................... Environment Database Creation Report (R98403) ............................................................. Setting Processing Options .................................................................................... Version XJDE0001 for Installations and Upgrades ............................................ Version XJDE0004 for Updates ..................................................................... Version XJDE0024 for Running Pristine Data .................................................. How to Read the Report ............................................................................... Errors and How to Resolve Them ................................................................... Index Recreation (R9698713) ........................................................................................ Pathcode Copy (R9800942) .......................................................................................... 23. Uninstalling the Software .............................................................................................. Understanding the Uninstallation Process ........................................................................ Uninstalling the Software from the Workstations ............................................................... Uninstalling the Deployment Server ............................................................................... Dropping Oracle Tablespaces and Indexes ....................................................................... Removing Database Users for Oracle .............................................................................. Uninstalling the Platform Pack ...................................................................................... 399 399 399 400 400 400 401 402 403 404 404 406 406 407 407 408 409 410 412 414
A. Using Instcat.sql to Support MSDE ODBC ....................................................................... 415 Running the instcat.sql SQL Script ................................................................................. 415
xii
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
Note
You should always check Customer Connection in the section Updates and Critical Fixes for revisions to this guide subsequent to the initial release, which coincides with the General Availability of Release 8.12. Generally, this document is republished in its entirety only for the next major applications release of JD Edwards EnterpriseOne. The book contains only the procedures required for a typical base installation with predefined typical environments and databases. However, the installation is flexible enough to enable you to: Select specific components to install from multiple predefined environments and databases. Install the Platform Pack to either of these machine combinations: Enterprise Server and Database Server on one machine and one drive the Installer runs once. Enterprise Server and Database Server on separate machines (or different drives in the same machine) the Installer runs twice, once for each server.
This guide is designed for management information system (MIS) managers and installers. It outlines the procedures for installing Release 8.12. To successfully install Release 8.12, you must understand: Hardware and software requirements Database setup and management Enterprise platforms and operating systems
At a minimum, review these guides before beginning: JD Edwards EnterpriseOne Tools 8.96 Foundation Guide JD Edwards EnterpriseOne Tools 8.96 Configurable Network Computing Implementation Guide JD Edwards EnterpriseOne Tools 8.96 System Administration Guide JD Edwards EnterpriseOne Tools 8.96 Package Management Guide JD Edwards EnterpriseOne Tools 8.96 Server and Workstation Administration Guide JD Edwards EnterpriseOne Tools 8.96 Security Administration Guide
In addition, it is recommended to complete the database product courses that your database vendors provide.
GA.Rev8 1/7/2008
Note
For Release 8.12, a JD Edwards EnterpriseOne HTML Web Server is mandatory to run web-enabled JD Edwards EnterpriseOne applications, which includes all end-user applications and selected tools applications. This guide only describes the definition of the HTML Web Server in regards to the Installation Planner and the Installation Workbench. The installation of the HTML Web Server itself is not covered by this guide. Separate guides describe the separate installation process for the HTML Web Server on the supported platforms. These HTML Web Server installation guides are available on Customer Connection. For Release 8.12, the current terminology and that used in this guide is to refer to the machine running the JD Edwards EnterpriseOne Java Application Server (JAS) as the HTML Web Server. Functionally, these terms are all synonymous. However, this guide only uses the terms JAS or Java Server when explicitly labeled as such by the software. Install the workstations for developers and system administrators
Note
You can concurrently install the Deployment Server, the Platform Pack, and the HTML Web Server assuming the installation programs are run on different machines. This can decrease the overall time it takes to complete the installation. Installations of the Deployment Server and Enterprise Server on the same machine, which are commonly referred to as combo boxes, are not supported in production environments. You can set up your Release 8.12 configuration in many ways. You should follow the typical setup and naming conventions whenever possible, unless there is a strong business case that supports the need to change. See Also Typical Customer Configuration in the JD Edwards EnterpriseOne Tools 8.96 Configurable Network Computing Implementation Guide for more information about the typical customer configuration provided with Release 8.12.
Note
JD Edwards EnterpriseOne Release 8.12 does not support coexistence. This section discusses:
GA.Rev8 1/7/2008
Understanding the Deployment Server Installation Understanding the Platform Pack Installation Understanding the Installation Planner Understanding Installation Workbench Understanding Data Configuration Workbench Understanding the Workstation Installation
The program updates the Microsoft Windows registry with information about the Release 8.12 installation and languages, if applicable.
Note
Languages are installed using the Installation Planner from the Language CD. To install additional languages, you perform the language-specific procedures after you have executed the initial installation described in this guide. For additional details, refer to Creating a Language-Only Installation Plan. Installation Planner manages these processes:
GA.Rev8 1/7/2008
Language setup Location setup Deployment Server setup Enterprise Server setup HTML Web Server Additional server setup This includes setup to servers such as a Database Server.
Data source setup This includes setup for both Enterprise Server-specific and shared environment data sources.
Some data sources remain the same between releases: Business data Control tables
Other data sources are release specific: System and data dictionary Server map The server map is machine-specific and release-specific if separate environments are maintained. Environment setup This includes all environments for a typical customer configuration, and creation of a new environment, such as PD812. This process ensures that the Object Configuration Manager (OCM) mappings are correct and the new environments point to the correct path codes. This could include creating custom environments and path codes.
GA.Rev8 1/7/2008
Installs preconfigured data for specific regions and industries if you are a Rapid Start customer.
Important
You must run Data Configuration Workbench regardless of whether you are a Rapid Start customer. This ensures that if you are not a Rapid Start customer, the system is configured properly for a nonRapid Start installation. For information regarding Rapid Start, see JD Edwards EnterpriseOne Rapid Start.
GA.Rev8 1/7/2008
Documentation Updates
Customer Connection contains document updates and other information about installing and upgrade JD Edwards EnterpriseOne.
GA.Rev8 1/7/2008
Tips
This documentation contains tips containing information that can make the JD Edwards EnterpriseOne setup process easier. Tips information is helpful but optional.
Hyperlinks
The output processor used to generate the PDF versions of this document automatically produce hyperlinks. However, an anomaly in the generation process causes page numbers within brackets (for example, Hyperlinks) for the links to be included only for links within a chapter. Links external to a chapter will not contain page numbers. Likewise, hyperlinks to Appendices are not active, either within the Table of Contents or within the text body.
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
Environments Overview
The HTML Web Server (J) environments have the same mappings as the regular environments with the exception of logic, all of which is mapped to run on the Enterprise Server. Each environment shipped with Release 8.12 has a specific use. The following sections explain each environment in more detail. Understanding Environments Planner Environment (JDEPLAN) Pristine Environment (PS812) Deployment Environment (DEP812) Development Environment (DV812) Prototype Environment (PY812) Production Environment (PD812) Additional Considerations
Understanding Environments
The Release 8.12 software includes several environments that represent the typical customer configuration as defined in the JD Edwards EnterpriseOne Tools 8.96 Configurable Network Computing Implementation Guide. These environments are preset to make the installation process as easy as possible. This section contains additional information about these environments and their role in the installation and upgrade process. Follow the setup recommendations and naming standards described in this guide to minimize confusion when communicating with those outside of your implementation team. In addition, future upgrades are simpler if you use JD Edwards EnterpriseOne naming conventions. If you customize your configurations during the process, you should change only the descriptions provided with the typical setup. JD Edwards EnterpriseOne provides the following preset environments: Deployment (DEP812) Planner (JDEPLAN) Prototype (PY812) Pristine (PS812) Development (DV812) Production (PD812) HTML Web Server (J)
10
GA.Rev8 1/7/2008
Planner Pathcode
Release 8.12 provides a full set of runtime objects, which are used during the installation process. The software stores these objects on the Deployment Server in the planner directory. The planner pathcode contains the only complete set of runtime central objects on the Deployment Server, which are shared by all pathcodes. The planner pathcode includes preloaded packages used during the update specification merge process. A package indicates the necessary objects for a workstation, a point-in-time snapshot of the central objects on the Deployment Server, and where the installation program finds them.
Planner Database
All information created and updated during the planning stage is saved in these Microsoft Database Engine (MSDE) databases: JDEPlan812 JDECTL812 JDEDD812 JDSYS812 JDEVL812 JDEOL812 JDEData812
When using the planner environment to change your configuration: Planner database tables are updated with the change. A plan is defined and run to move the change to the production environment.
When using the deployment or production environment to change your configuration after finishing the process: Production environment tables in the System pathcode are updated in real-time. Planner database tables are not updated.
For the deployment and production environments, OCM and data source information comes from the planner
GA.Rev8 1/7/2008
11
database. You should use the production environment system (technical) tables to make changes to environments, pathcodes, packages, and OCM.
12
GA.Rev8 1/7/2008
Additional Considerations
Additional considerations include: Push Installation Cluster Software Options Web-Based Options
Push Installation
Push installation enables the system administrator to schedule an automatic installation of a JD Edwards EnterpriseOne package to workstations. Package information is pushed from the Deployment Server to the workstation, rather than the workstation requesting (pulling) an installation from the Deployment Server. The advantage of push installation is no interaction with the user is required. For a push installation, the administrator can schedule a package to deploy to workstations at times when network traffic is low. See Also JD Edwards EnterpriseOne Tools 8.96 Package Management Guide and Installing the Workstations for Developers and System Administrators in this guide for more information about the push installation process
Web-Based Options
HTML Web Server installation enables the use of Web-enabled functions in Release 8.12. For more information, refer to Working with Installation Planner. See Also HTML Web Server, Java Server, or JAS in the JD Edwards EnterpriseOne Tools 8.96 HTML Web Server Installation Guide for more information about Web-based options.
Release History
This version of JD Edwards EnterpriseOne is Release 8.12. The following list shows the currently supported previous releases of JD Edwards EnterpriseOne: Release 8.11 Release 8.10 ERP 8.9 ERP 8.0 OneWorld Xe
GA.Rev8 1/7/2008
13
Language Architecture
The software language architecture incorporates multinational language functionality for international customers. The software specifies the language preference for forms and reports. For example, users who share the same environment may want to view the same text in multiple languages, such as French, Spanish, and English. All language text is stored in a central location and deployed to the individual workstation. JD Edwards EnterpriseOne provides all software with a base language of English. The package build process enables the building of packages for multiple languages. Multiple languages can be installed using the processes outlined in this guide. Language text is accessed by the language preference code settings in the user profile associated with the alternate language installed.
Base Language
Release 8.12 language support works in conjunction with the English base language. The base release contains English and must be installed before creating custom modifications to include changes or additions to the translated text. All control files must also have an English record prior to adding an alternate language text record.
14
GA.Rev8 1/7/2008
Unicode
Unicode specifies that the data stored in the data source is in Unicode format. For installs, all data sources default to Unicode. Note that the code page still must be set to the correct value even though the data sources may all be Unicode. The Unicode flag only indicates what column type is used to store character data in a Unicode database. See Also
GA.Rev8 1/7/2008
15
JD Edwards EnterpriseOne Unicode Data Conversion Guide for information on how to convert data to Unicode. JD Edwards EnterpriseOne Tools 8.96 Development Standards for Business Function Programming Guide for information on how to convert Business Functions to support Unicode text strings. JD Edwards EnterpriseOne Flat File Conversion Guide for information on how to convert Flat Files to Unicode.
16
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
17
Tier 2 3 3 3 3 3 3 3
Language Simplified Chinese Arabic Czech Hungarian Polish Greek Russian Turkish
Language Code CS AR C HU PO GR RU TR
LocalCodeSet Value SC_GB AR_CP1256 EECP1250 EECP1250 EECP1250 GR_CP1253 RS_CP1251 TK_CP1254
Font Considerations
JD Edwards EnterpriseOne includes standard language fonts in a separate file. Some languages (such as doublebyte) require special fonts to display and print correctly. The software stores the font settings in files according to language. Individual users can choose fonts by language for forms, grids, and reports.
18
GA.Rev8 1/7/2008
Note
Make sure that you have taken and installed the latest Planner ESU from the Update Center on Customer Connection. Failing to do so may prevent proper installation of the software. Additionally, a new compiler requirement is added for Release 8.12. Before you run the Deployment Server or Platform Pack installer, you should install a Microsoft Visual C++ compiler on any machine on which the installer will be run. The MTRs list supported C++ compilers on Microsoft Windowsbased machines. Refer to Accessing Minimum Technical Requirements
GA.Rev8 1/7/2008
19
Note
While the disk space tables accurately represent the disk space requirements, the actual requirements for an installation will be greater due to the requirement for temporary space.
20
GA.Rev8 1/7/2008
Warning
If you are using the default configuration of the Deployment Server that loads to a MSDE database, you must always run the set of stored procedures in the instcat.sql SQL script that is supplied by your installation of the latest version of SQL Server or Microsoft Data Access Component (MDAC). This is required because the version of instcat.sql SQL script within the MSDE SP3 install, which is supplied by the Deployment Server installation, is older than the version supplied with Windows 2003. Otherwise, you may experience intermittent problems with accessing MSDE. You should run the proper version of the instcat.sql SQL script after you install your Deployment Server, and before you begin deploying to workstations. Refer to Using Instcat.sql to Support MSDE ODBC for requirements and operational details. If you are not using the default MSDE database on your Deployment Server, refer to the Note on the following page, under the topic Installing the Deployment Server, for a discussion of requirements for SQL Server on the Deployment Server.
GA.Rev8 1/7/2008
21
Note
Alternatively, you can choose to replace MSDE with SQL Server as your repository on the Deployment Server. In that case, refer to Accessing Minimum Technical Requirements for specific versions of SQL Server and other requisite software, especially the SQL Native Client which is a unique requirement for SQL Server 2005. If you choose to use SQL Server, you must meet the MTRs prior to running the Deployment Server installer.
Tip
The InstallShield process creates temporary files during the install. By default these are placed on the c: drive of your Windows-based Deployment Server. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully. Alternately, you can redirect these temporary files to a different drive with more space by using this procedure to change the Environment Variables for the logged in user: 1. Create a new empty folder on the drive that has more room. For example, the drive and folder might be d:\ISMPTemp. 2. 3. 4. Right click on My Computer then choose Properties | Advanced | Environment Variables. Scroll through the variables in the top pane (User) and find TEMP and TMP. Change both of these to point to the folder you created on your larger drive in Step 1.
22
GA.Rev8 1/7/2008
Warning
Mandatory PATH Environment Variable Change If you do not have MSDE, or SQL Server, or SQL Server 2005 currently installed on the Deployment Server, the Deployment Server install will install MSDE. During the Deployment Server install, it installs MSDE then immediately attempts to use it to attach the shipped MSDE databases. This will only work if the path to the MSDE code is defined before the Deployment Server install is run. Note that the MSDE install has the location hard coded: C:\Program Files\Microsoft SQL Server To modify the PATH environment variable: 1. 2. 3. On the Deployment Server, right click on My Computer. Click on Properties | Advanced | Environment Variables. Click on PATH in the bottom pane and add to the end of the existing value: ;C:\Program Files\Microsoft SQL Server\80\Tools\BINN
This table lists the mandatory and optional components of the Deployment Server installation. Server Deployment Server Mandatory Component JD Edwards EnterpriseOne files Optional Components Production environment Prototype environment Development environment Pristine environment The installation process for the Deployment Server performs these functions: Installs the objects from the CDs. Creates the path code directory structures (such as PS812 and PD812) based on your selections. Updates the Microsoft Windows Registry.
Note
You can run the Deployment Server and the Platform Pack installation concurrently (assuming the installation programs are run on different machines). After verifying the support structure, you can install the Deployment Server. This process installs the Deployment Server from CDs.
Note
Install the Deployment Server locally; you cannot install the Deployment Server from a remote machine.
GA.Rev8 1/7/2008
23
Prerequisites Before you run the installation program, shut down all programs running on the Deployment Server that could cause DLL conflicts (such as Microsoft SQL Services, Internet Explorer, Microsoft Word, or Adobe Acrobat). You can restart these programs after you finish installing the Deployment Server.
24
GA.Rev8 1/7/2008
The diagram below illustrates the process flow and the various installation paths.
To install the Deployment Server: 1. Log on to the Deployment Server as a user with Administrator rights.
Warning
Ensure that the Administrator account name that you use does not contain any special characters. 2. Insert the first Deployment Server CD into the CD drive. The setup starts automatically. If the setup does not begin automatically or if you wish to start the installation manually, you can execute the RunInstall.exe file which is located at the root of the installation disk. The RunInstall.exe (which is called by the autorun.inf) enables the JD Edwards EnterpriseOne Deployment Server Installer to detect the drive with the most available space and to use it as the default drive for the installation. If you directly execute the Deployment Server installation program (setupwin32.exe) then the JD Edwards EnterpriseOne Deployment Server Installer will not scan available drives for disk space and you must have adequate space on your c: drive which will be the assumed default drive.
Note
The InstallShield Wizard begins to initialize and prepare the requisite JVM for the JD Edwards EnterpriseOne Deployment Server Installer. Although this may take a few minutes to completely initialize, you can view the progress on the InstallShield Wizard dialog that appears on your screen or Task Bar. When the initialization is complete, a new and separate JD Edwards EnterpriseOne Deployment Server Installer window is displayed.
GA.Rev8 1/7/2008
25
3.
4.
On JD Edwards | EnterpriseOne Deployment Server Installer, License Validation Panel, complete these fields: GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.
26
Expiration Date
Enter the date on which Release 8.12 software expires. This date should default into the SPC generator program as 1/1/2899. For a discussion on obtaining and using the license key generator program, refer to Revalidating the Deployment Server in the chapter of this guide entitled: Installation Utilities. Enter the number of licenses.
Number of Licenses
Note
This number should be less than 5000 in order to avoid potential performance impact. For additional details, refer to Revalidating the Deployment Server in the chapter of this guide entitled: Installation Utilities. Enter the codes that were generated by the SPC generator program. For a discussion on obtaining and using the license key generator program, rRefer to Revalidating the Deployment Server in the chapter of this guide entitled: Installation Utilities.
Authorization Code
Caution
Each time the setup program is run, the serial number changes, which requires a new JD Edwards EnterpriseOne authorization code. Avoid stopping and rerunning the installation program after obtaining an authorization code. 5. Click Next.
GA.Rev8 1/7/2008
27
6.
On JD Edwards | EnterpriseOne Deployment Server Installer, directory selection panel, complete this field: Directory Name Enter the drive and directory where you want the files installed on your Deployment Server. The JD Edwards EnterpriseOne Deployment Server Installer automatically scans all drives for available space and by default chooses the drive that contains the most available space. For example: z:\JDEdwards\E812
7. 8.
Click Next. On JD Edwards | EnterpriseOne Deployment Server Installer, setup type panel, choose your installation type: Typical Recommended for most users, choose this setup type if you wish to complete the Deployment Server installation with no further specifications. This installation option includes the required JD Edwards EnterpriseOne files for the Prototype and Pristine environments.
Tip
If you choose Typical installation, you can skip directly to step 11 located later in this task to complete the Deployment Server installation. Recommended for experienced users, choose this setup type if you wish to complete the Deployment Server installation by specifying the installation of a subset of pre-defined environments.
Custom
9.
If you chose Custom Mode on the previous panel, on JD Edwards |EnterpriseOne Deployment Server Installer, feature selection panel, select the features you want to install:
28
GA.Rev8 1/7/2008
Note
This selection includes mandatory system files. If you do not select this box and the JD Edwards EnterpriseOne Deployment Server Installer can not detect the required system files, it selects them automatically and displays a warning message. On the warning message, you must either select OK to acknowledge that the selection of the mandatory system files, or click Back and change your selections manually. Likewise, if you re-run the JD Edwards EnterpriseOne Deployment Server Installer to add an environment it will check to ensure that these files are already installed and you will not be given an option to install the environment on a machine, drive, or directory that is different from that which contains the JD Edwards EnterpriseOne files. Production Environment Prototype Environment Development Environment Pristine Environment
10. Click Next. 11. On JD Edwards | EnterpriseOne Deployment Server Installer, summary information panel, verify that the appropriate components are selected. If there is insufficient disk space to complete the installation is available on the Deployment Server target machine, an error message is displayed. 12. Click Next to begin the Installation. The JD Edwards EnterpriseOne Deployment Server Installer displays a panel showing the ongoing status of the installation. On JD Edwards | EnterpriseOne Deployment Server Installer, after the installation is complete, a message appears stating that the installation was successful. 13. Click Finish to complete the installation and exit the JD Edwards | EnterpriseOne Deployment Server Installer.
Note
After the JD Edwards EnterpriseOne Deployment Server Installer is complete, a panel may appear directing you to reboot the machine to complete the installation. This occurs if certain Microsoft Windows systems files are in use at the time of installation and therefore cannot be modified in real time. Therefore, in such cases the installation cannot be completed until the machine is rebooted.
GA.Rev8 1/7/2008
29
Tip
You should review the log file created by the Deployment Server Installer. The file is named log.txt and is located in the Deployment Server installation directory. For example:
30
GA.Rev8 1/7/2008
x:\JDEdwards\E812\log.txt
Note
The order in which the following Tools Release and updates are applied is very important. Do not deviate from the order below. This section discusses: Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server Installing JDBC Drivers for SQL Server 2000 Installing the Latest Planner Update
Installing the Latest Tools Release and Latest Tools Release Patch to the Deployment Server
To install the latest tools release and latest tools release patch: 1. 2. From the Update Center homepage, download the latest Tools Release Patch (for example, 8.96.A1) and Tools Release documentation. Using the Tools Release documentation, install the Tools Release Patch to the Deployment Server.
Note
If you have ever used the Drag and Drop method of moving between Tools Releases for service packs, it is necessary to run the Reconfigure MSDE Utility. To do so, navigate to this directory on your Deployment Server: JDEdwards\E812\system\bin32 From that directory, run this batch file: ReconfigureMSDE.exe When you run this program, a dialog prompts whether you want to convert the password to be compatible with JD Edwards EnterpriseOne SP1 or with SP2 and greater. Select SP2 and greater and click on OK.
GA.Rev8 1/7/2008
31
Note
These instructions are for the Deployment Server only, for installations of JD Edwards EnterpriseOne Applications Release 8.9 or newer that have not set up the Web Development features for Package Build. To install JDBC drivers for SQL Server 2000: 1. On your Deployment Server, create this directory: EnterpriseOne_Install_Location\OneWorld Client Install\ThirdParty \WebDevFeature\JDBC
Note
If this directory already exists and contains the SQL Server 2000 drivers listed in Step 4 no further action is necessary. 2. Obtain the SQL Server 2000 JDBC drivers from Microsoft. Microsoft provides a Type 4 JDBC driver for SQL Server 2000 with full support at no additional charge to licensed customers. a. Download the appropriate driver directly from the Microsoft web site using this link to search the Microsoft Downloads site: http://www.microsoft.com/downloads/search.aspx?displaylang=en b. c. 3. Enter JDBC Driver as your search criteria and choose SQL Server 2000 Driver for JDBC Service Pack 3 with a release date of 7/6/2004. Download only the setup.exe component to a temporary directory on the Deployment Server. For example, x:\temp.
On your Deployment Server, run the setup.exe and choose Custom Installation, which will enable you to choose the SQL Server 2000 Driver for JDBC component to install. Change the default directory in which to install the JDBC drivers from C:\Program Files\Microsoft SQL Server 2000 Driver to point to your temporary directory that you created in the previous Step, in the Substep c. For example, x:\temp.
4.
Navigate to the temporary directory, in the x:\temp\lib subdirectory, and copy these files to the JDBC directory you created in Step 1: msbase.jar msutil.jar mssqlserver.jar
32
GA.Rev8 1/7/2008
Tip
To attach the Metadata MSDE database, navigate to the Planner\spec directory and run this batch file: attach_metadata812.bat
Caution
As part of the MSDE install, which is bundled with the Deployment Server Installer, the password for the sa user on the JDELocal instance is scrambled. If you re-set this password, several JD Edwards EnterpriseOne functions will fail. If you should inadvertently reset the password, you can scramble it again to the expected default password. To do so, navigate to this directory on your Deployment Server: JDEdwards\E812\system\bin32 From that directory, run this batch file: ReconfigureMSDE.exe When you run this program, a dialog prompts whether you want to convert the password to be compatible with JD Edwards EnterpriseOne SP1 or with SP2 and greater. Select SP2 and greater and click on OK. To install the latest planner update: 1. From Customer Connection, download the latest planner update to the Deployment Server. For example, if you are upgrading from JD Edwards EnterpriseOne Release 8.11 to JD Edwards EnterpriseOne Release 8.12, you should install the most recent Tools Release 8.96 planner update. 2. Run the self-extracting executable and follow the on-screen instructions to install the planner update on the Deployment Server.
GA.Rev8 1/7/2008
33
3.
You must enter a valid JD Edwards EnterpriseOne user and password in order to initialize the Planner environment. The default values are JDE for the user and JDE for the password.
Note
The above login screen is displayed so that the Planner Update can update the metadata specifications on the Deployment Server. 4. When the installation finishes, view the JD Edwards EnterpriseOne Deployment Server Setup form to confirm that the installation was successful.
Tip
If the folder into which you expanded the Planner Update is empty, you should run the selfextracting executable (jxxxx.exe) again. When the Welcome screen comes up, click on Cancel to quit. 5. Follow the steps in the Special Instructions, which are contained within an HTML file that is shipped with the Planner Update. The special instructions file located in this directory with this file name: x:\download_directory\planner_update_id\E812SpecialInstructions.htm where download_directory is the directory where you downloaded the Planner Update.
Caution
You must run the SpecialInstrs.bat every time you apply a new Planner Update.
34
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
35
36
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
37
Note
You can concurrently install the Deployment Server, the Platform Pack, and the HTML Web Server (also previously known as JAS) assuming the installation programs are run on different machines. This can decrease the overall time it takes to complete the installation.
Note
To reinstall any Enterprise Server components, refer to Rerunning the JD Edwards EnterpriseOne Platform Pack Installer. This table lists the mandatory and optional components of the Platform Pack installation: Server Enterprise Server Mandatory Component Optional Components
Database Server
System Database
Note
Micosoft Windows Considerations. Microsoft clustering is supported for system failover protection. As detailed in the Minimum Technical Requirements, install any Microsoft Windows server upgrades that are required to support Release 8.12. Before you install Release 8.12 software on the Microsoft Windows Enterprise Server, you must create the Release 8.12 administrator user, verify disk space, and set up and verify the hosts file.
38
GA.Rev8 1/7/2008
See Also Verifying Software and Hardware Requirements for more information about software requirements. Microsoft Cluster Administrator Guide or Microsoft Windows Server 4 Second Edition for more information on using cluster software. Release 8.12 on a Cluster section in JD Edwards EnterpriseOne Tools 8.96 Server and Workstation Administration Guide for more information about clustering.
For example, if your database is using the code page JA16SJIS (Japanese), the NLS_LANG variable parameter setting would look like this:
GA.Rev8 1/7/2008
39
Caution
Remember to add a period in front of the NLS_LANG variable value for the given code page. See Also Refer to Language Process Overview for these values and additional information regarding the National Language Support tables.
Note
If your Oracle database installation is not using the JD Edwards EnterpriseOne system administrator password setup by scripts run during the installation of JD Edwards EnterpriseOne, you will need to consult with your Oracle DBA. 2. 3. After the utility runs, you must shut down and restart Oracle. You must then grant the an Oracle system user with sysdba permissions. For example, you could issue this sqlplus command: SQL> grant sysdba to user_name; 4. Verify the password parameter. For example, you can issue this sqlplus command:
40
GA.Rev8 1/7/2008
SQL> show parameter password The sqlplus command produces these results: NAME TYPE VALUE remote_login_passwordfile string EXCLUSIVE 5. Verify the user is listed in the password file. For example, you could issue this sqlplus command: SQL> select * from v$pwfile_users; The sqlplus command produces these results: USERNAME SYSDBA SYSOPER SYS TRUE TRUE SYSTEM TRUE FALSE
GA.Rev8 1/7/2008
41
42
GA.Rev8 1/7/2008
Caution
Set the NLS_ CHARACTERSET and NLS_NCHAR_CHARACTERSET parameters for the appropriate language before loading your central objects specification objects for Release 8.12. To verify the code page settings for Oracle: 1. Verify the code page setting of the Oracle database by executing this single-line SQL command from SQL Plus: SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET'; 2. Verify the Unicode code page setting of the Oracle database by executing this single-line SQL command from SQL Plus: SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET'; If the setting is incorrect, set the NLS_NCHAR_CHARACTERSET value to AL16UTF16, using the Oracle documentation to change the setting. 3. Set up NLS_LANG parameter for Oracle. For JD Edwards EnterpriseOne environments with languages to function properly, the NLS_LANG parameter must be set correctly for Oracle. These settings must be set for your Oracle client workstations and Oracle database server.
GA.Rev8 1/7/2008
43
Caution
Remember to add a period before the NLS_LANG variable value for the given code page. See Also Refer to the Language Process Overview in the for the National Language Support tables and other information related to multilingual installations.
44
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
45
46
GA.Rev8 1/7/2008
Warning
If you have previously run the Platform Pack installer on your Enterprise Server, you should ensure that an invalid vpd.properties file does not exist on that machine; otherwise, the installer may fail to start or complete properly. Refer to Installer Will Not Start or Complete (Invalid vpd.properties) for additional details.
Tip
The InstallShield process creates temporary files during the install. By default these will be placed on the c: drive of a Windows machine. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully. Refer to the Tip in the chapter entitled:Working with the Deployment Server at the beginning of the section entitled: Installing the Deployment Server for a procedure you can use to increase your disk space. To run the JD Edwards EnterpriseOne Platform Pack Installer: 1. Log on to the Enterprise Server as a user with Administrative rights.
Warning
Ensure that the Administrator account name that you use does not contain any special characters. 2. Insert the JD Edwards EnterpriseOne Platform Pack Installer CD into the CD drive. The setup starts automatically. If the setup does not begin automatically or if you wish to start the installation manually, you can execute the RunInstall.exe file which is located at the root of the installation disk. The RunInstall.exe (which is called by the autorun.inf) enables the JD Edwards EnterpriseOne Platform Pack Installer to detect the drive with the most available space and to use it as the default drive for the installation. If you directly execute the JD Edwards EnterpriseOne Platform Pack Installer (RapidSetup.exe) then it does not scan available drives for disk space and you must have adequate space on your c: drive which is the default drive.
Note
The InstallShield Wizard begins to initialize and prepare the requisite JVM for the JD Edwards EnterpriseOne Platform Pack Installer. Although this may take a few minutes to completely initialize, you can view the progress on the InstallShield Wizard dialog that appears on your screen or Task Bar. When the initialization is complete, a new and separate JD Edwards EnterpriseOne Platform Pack Installer window is displayed. 3. On JD Edwards | EnterpriseOne Platform Pack Installer, Welcome, click Next.
GA.Rev8 1/7/2008
47
4.
On JD Edwards | EnterpriseOne Platform Pack Installer, directory selection panel, complete this field: Directory Name Enter the drive and directory where you want the files installed on your Enterprise Server. The JD Edwards EnterpriseOne Platform Pack Installer automatically scans all drives for available space and by default chooses the drive that contains the most available space. The default value is: c:\JDEdwards\E812 If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer, refer to Rerunning the JD Edwards EnterpriseOne Platform Pack Installer.
5. 6.
Click Next. On the Run Mode selection panel, choose whether you want to install or upgrade JD Edwards EnterpriseOne. Refer to the following table for a full description of each run mode. Install This document only describes the Install Mode. In this mode, the JD Edwards EnterpriseOne Platform Pack Installer checks for the existence of JD Edwards EnterpriseOne business data and control tables; if either exists, the JD Edwards EnterpriseOne Platform Pack Installer aborts. This prevents the inadvertent overwriting of existing critical business data and control tables. If the JD Edwards EnterpriseOne Platform Pack Installer does not detect pre-existing JD Edwards EnterpriseOne data or control tables, the installation process continues normally.
48
GA.Rev8 1/7/2008
Caution
Upgrade You should always back up all databases that you want to preserve. The Upgrade Mode is described in a separate document entitled: JD Edwards EnterpriseOne Release 8.12 Upgrade Guide. In this mode, the JD Edwards EnterpriseOne Platform Pack Installer checks for the existence of JD Edwards EnterpriseOne business data and control tables which are prerequisites to an upgrade of JD Edwards EnterpriseOne.
Note
If you chose Upgrade mode, the JD Edwards EnterpriseOne Platform Pack Installer displays a panel that confirms the data and tables required for an upgrade and also offers you the option to change from Upgrade to Install. 7. On JD Edwards | EnterpriseOne Platform Pack Installer, setup type panel, choose your installation type: Typical Choose this setup type if you wish to complete the Platform Pack installation with no further specifications. This installation option is recommended for most users and includes the required JD Edwards EnterpriseOne files for the Prototype and Pristine environments.
Tip
If you choose Typical installation, you can skip directly to Database Options located later in this task to complete the Platform Pack installation. Recommended for experienced users, choose this setup type if you wish to complete the Platform Pack installation by specifying the installation of a subset of pre-defined environments.
Custom
Tip
If you choose Custom installation, continue with the steps below in this task which immediately follow. 8. Click Next.
GA.Rev8 1/7/2008
49
1.
If you are installing in Custom Mode, on JD Edwards | EnterpriseOne Platform Pack Installer, features panel, select from these choices: JD Edwards EnterpriseOne Enterprise Server JD Edwards EnterpriseOne Foundation
Note
This selection includes system files. You must choose this feature for all initial installations of the Enterprise Server. If you do not select this feature, the JD Edwards EnterpriseOne Platform Pack Installer checks your system to verify that the JD Edwards EnterpriseOne Foundation is already installed. If not, the JD Edwards EnterpriseOne Platform Pack Installer automatically selects it for installation. 50 ES Production ES Prototype ES Development GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.
ES Pristine
Note
This selection includes mandatory system files. If you do not select this box and the JD Edwards EnterpriseOne Platform Pack Installer can not detect the required system files, it selects them automatically and displays a warning message. On the warning message, you must either select OK to acknowledge that the selection of the mandatory system files, or click Back and change your selections manually. Likewise, if you rerun the JD Edwards EnterpriseOne Platform Pack Installer to add an environment it will check to ensure that these files are already installed and you will not be given an option to install the environment on a machine, drive, or directory that is different from that which contains the JD Edwards EnterpriseOne Files. 2. Production Databases Prototype Databases Development Databases Pristine Databases
GA.Rev8 1/7/2008
51
Database Options
Regardless of which installation type you chose, Typical or Custom, you must enter database options as described in this procedure.
1.
On JD Edwards | EnterpriseOne Platform Pack Installer, Database Options, complete these fields: Database Type Database Server Name Use the pulldown menu to choose Oracle Server. By default, the JD Edwards EnterpriseOne Platform Pack Installer automatically detects and populates this field with the machine name on which it is running. The JD Edwards EnterpriseOne Platform Pack Installer validates the Database Server name and compares it against the name of the local computer. If these values are different (for example, if you manually change the value of this field), the JD Edwards EnterpriseOne Platform Pack Installer assumes the Database Server is . If you have selected to install databases, and the database server name that you entered cannot be validated, an error dialog is displayed with resolution instructions. For additional details on error conditions, refer to Troubleshooting Platform Pack Installation.
2.
Click Next.
52
GA.Rev8 1/7/2008
When choosing the database, consider these scenarios depending on which machine the database resides: Oracle - Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) - or Database only Oracle - Enterprise Server Only (Different Machine from Database Server)
Oracle - Enterprise Server and Database Server (Loaded onto Same Machine Simultaneously) - or Database only
This configuration assumes you have selected to install your JD Edwards EnterpriseOne database server locally on the same machine as your Enterprise Server, or that you are installing a database only.
On the Oracle Database Instance configuration panel, complete these fields: CONNECT STRING Enter a valid value for your Oracle connect string. You may need to obtain this value from your Oracle DBA. You cannot proceed with the installation until this value can be validated by the JD Edwards EnterpriseOne Platform Pack Installer; that is, the Installer will not allow you to proceed if it cannot connect to the database. The installer provides a default value of sys.
SYSADMIN USER
GA.Rev8 1/7/2008
53
Warning
You can not use a value of system for the SYSADMIN USER field. You must use the value sys or a user similar to sys. All of the Oracle scripts used by theJD Edwards EnterpriseOne Platform Pack Installer use this syntax to connect to the database: sys as sysdba where sys is the value you enter in the SYSADMIN USER field. Therefore, the Installer's syntax will not work with the system user. The value sys (or equivalent) identifes the system administration user for your Oracle installation. This user must have full DBA privileges which are standard for Oracle installations. The JD Edwards EnterpriseOne Platform Pack Installer validates the user login and ensures the user has the appropriate DBA privileges in order to create and populate the Oracle tables. Enter a valid password for the system administration user under which you will be installed the JD Edwards EnterpriseOne Oracle databases. Enter the path where you want the JD Edwards EnterpriseOne Platform Pack Installer to create your Oracle database tables. For example: z:\database_location
Note
The Installer automatically appends the path you enter here with \ORCL. Enter the path where you want the JD Edwards EnterpriseOne Platform Pack Installer to create your Oracle database indexes. For example: z:\database_location
Note
The Installer automatically appends the path you enter here with \ORCL.
Warning
You should always consult with a DBA for the proper location of the RDBMS system on your machine. Do not install your RDBMS system in location with a child relationship to the JD Edwards EnterpriseOne installation directory, x:\JDEdwards. This practice avoids any potential where actions against the parent directory might adversely impact the child directory. An information panel displays confirming the information you specified for the locations for the Oracle database tables, indexes, and run-time scripts (which are called by the JD Edwards EnterpriseOne Platform Pack Installer). After you have read and confirmed the Oracle installation information, click Next and proceed to Database Options in this task.
54
GA.Rev8 1/7/2008
On the Oracle Connect String panel, complete this field: Connect String Enter a valid value for your Oracle connect string. You may need to obtain this value from your Oracle DBA. You cannot proceed with the installation until this value can be validated by the JD Edwards EnterpriseOne Platform Pack Installer; that is, the Installer will not allow you to proceed if it cannot connect to the database.
GA.Rev8 1/7/2008
55
56
GA.Rev8 1/7/2008
Concurrent Users
If you chose to install an Enterprise Server you are presented with the screen that prompts you to enter the number of concurrent users that will be used on that server. The values you enter on this screen, along with the selection or deselection of the specified JD Edwards EnterpriseOne applications, is used by the JD Edwards EnterpriseOne Platform Pack Installer to calculate and set certain JDE.INI settings that will result in optimal server performance for the JD Edwards EnterpriseOne installation.
1.
On JD Edwards | EnterpriseOne Platform Pack Installer, complete these fields: Please enter the number of concurrent users that will be using this system Will any of the following be used by the JD Edwards EnterpriseOne system? Enter a valid value greater than zero.
Click the Yes radio button if you are using any of the following JD Edwards EnterpriseOne applications: Sales Order Processing Configurator Journal Entry Job Cost
GA.Rev8 1/7/2008
57
The selection or deselection of this radio button influences the calculations that the JD Edwards EnterpriseOne Platform Pack Installer computes in order to set the JDE.INI on the Enterprise Server for optimal performance. 2. Click Next to continue.
58
GA.Rev8 1/7/2008
Note
After the Enterprise Server portion of the JD Edwards EnterpriseOne Platform Pack Installer is complete, a panel may appear directing you to reboot the machine to complete the installation. This occurs if certain Microsoft Windows systems files are in use at the time of installation and therefore cannot be modified in real time. Therefore, in such cases the installation cannot be completed until the machine is rebooted.
GA.Rev8 1/7/2008
59
60
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
61
If you receive this error, it means you have selected Install as the installation type (as opposed to Upgrade) and the JD Edwards EnterpriseOne Platform Pack Installer has detected that the DTA and CTL tablespaces already exist for the selected environment. To resolve the error condition, you must uninstall the referenced database as specified by the text in the error.
62
GA.Rev8 1/7/2008
If you receive this error, it means you have selected Upgrade as the installation type (as opposed to Install) and the JD Edwards EnterpriseOne Platform Pack Installer has detected that the DTA and CTL tablespaces do not exist for the selected environment. That is, a separate error panel is displayed for each environment (such as Production, Development, Test, or CRP) that you selected, already exists, but does not already contain the mandatory DTA and CTL tablespaces. To resolve the error condition, you must go back and select Install instead of Upgrade.
GA.Rev8 1/7/2008
63
Business Data or Control Tables Tablespaces Reported As Existing When They Do Not Exist
If the Platform Pack Installer reports that Business Data and Control Tables exist, but in fact the Oracle tablespaces do not exist, ensure the Oracle account has rights to write to its home directory. 1. 2. 3. Navigate to /home and list the directories Check that the Oracle account has write privilege on its home directory. Verify that the Oracle connect string and database home are specified in the correct case.
If you receive this error, it means you have selected to install one or more databases but do not have the mandatory JD Edwards EnterpriseOne Database Foundation Components already installed or selected for installation. After the JD Edwards EnterpriseOne Platform Pack Installer displays this error, as a user convenience, it automatically selects the mandatory Database Foundation Components for installation. Therefore, at this point you can continue with the installation which will include the mandatory components. Alternately you can manually navigate backwards and make additional changes to your existing selections.
64
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
65
If you receive this error, it means you have selected to install one or more environments but do not have the mandatory JD Edwards EnterpriseOne Server Foundation Components already installed or selected for installation. After the JD Edwards EnterpriseOne Platform Pack Installer displays this error, as a user convenience, it automatically selects the mandatory Enterprise Server Foundation Components for installation. Therefore, at this point you can press to continue with the installation which will include the mandatory components. Alternately you can manually navigate backwards and make additional changes to your existing selections.
66
GA.Rev8 1/7/2008
You should never reinstall any optional components without first uninstalling the components. If you select to uninstall the mandatory components you must also select to uninstall or have already uninstalled all related optional components. This table lists the mandatory and related optional components: Server Enterprise Server Mandatory Component JD Edwards EnterpriseOne Foundation Optional Components ES Production ES Prototype ES Development ES Pristine Database Server System Database Production Databases Prototype Databases Development Databases Pristine Databases
Enterprise Server
If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer in order to add environments, you must specify the same machine, drive, and directory as that which you selected for JD Edwards EnterpriseOne Foundation during the initial installation of the Platform Pack.
Database Server
If you are rerunning the JD Edwards EnterpriseOne Platform Pack Installer in order to add databases, you must specify the same machine, drive, and directory as that which you selected for System Database during the initial installation of the Platform Pack.
GA.Rev8 1/7/2008
67
Installing the Latest Tools Release and Latest Tools Release Patch to the Enterprise Server
Caution
The Tools Release level must match what was installed on the Deployment Server. For instructions on installing the tools release, refer to JD Edwards EnterpriseOne Tools Release 8.96 Installation Guide, which is available by platform on Customer Connection. To install the latest tools release and latest tools release patch: 1. 2. From the Update Center homepage, download the latest Tools Release Patch (for example, 8.96.A1) and Tools Release documentation. Using the Tools Release documentation, install the Tools Release Patch to the Enterprise Server.
68
GA.Rev8 1/7/2008
Note
You must also logon to JDEPLAN using the changed password, otherwise database connections will fail. Using the above example of a changed password, you would logon using these credentials: User = JDE Password = apples Environment = JDEPLAN
Caution
The Installation Workbench can only process passwords equal to or less than 10 characters in length. Therefore, you cannot use passwords greater than 10 characters even if your RDMS allows it.
GA.Rev8 1/7/2008
69
After you change the [DSPWD] section of the jde.ini file, logon to OneWorld in the JDEPLAN environment on the Deployment Server with the new password in the correct case.
Warning
Whenever you change the password on your database, as recommended for security purposes, you must also ensure that your security settings in the Enterprise Server jde.ini file match that of your database. Refer to Working With Signon Security in this guide for applicable instructions. You should secure the jde.ini file on the Deployment Server to prevent unauthorized access. You should delete the [DSPWD] section once the install or upgrade is complete.
70
GA.Rev8 1/7/2008
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
GA.Rev8 1/7/2008
71
72
GA.Rev8 1/7/2008
Language Information
Installation Planner enables you to create a plan for installing an alternate language or multiple languages as you create your master plan. You should follow the system prompts to choose which languages will be installed for each environment. For initial installations, you can complete your master plan and install languages later by creating a languageonly plan. Refer to Creating a Language-Only Installation Plan for more information about setting up an alternate language after the master plan.
Location Information
Locations are user-defined groups of machines, databases, and environments. The use of multiple locations is recommended for configurations across a wide area network (WAN). Two types of locations exist: base locations and remote locations. Each installation plan can have only one base location. It is the central point for planning and executing the deployment process. The base location does not have a parent location and does not use a location code. You can have any number of tiered locations; each has a parent location and a location code. To set up locations for installation plans, you must provide the installation program with the location, location description, location code (if there is a secondary location), and parent location (if there is a secondary location). The location code is a three-character alphanumeric code that you specify. This location code is used as part of the name of the data sources for secondary locations in the plan. Locations are stored in the Deployment Locations Definition table (F9654). See Also Refer to Creating a Remote Installation Plan for information about setting up remote locations.
GA.Rev8 1/7/2008
73
Warning
For Release 8.12, a JD Edwards EnterpriseOne HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because, unlike prior JD Edwards EnterpriseOne releases, the enduser applications are only accessible through a web interface.
74
GA.Rev8 1/7/2008
The data source for the Versions List table (F983051). You can have multiple sets of versions tables (for example, Versions - PD812, Versions - PS812, Versions - DV812, and Versions - PY812). However, you can have only one Versions data source for each path code. See Also Major Technical Tables for more information about individual tables and their uses
Environment Information
Installation Planner enables you to select default environments for your installation that are predefined, or you can choose to define them manually. Likewise, Installation Planner enables data load using default data load options, or you can choose to define them manually and override the default data load options.
GA.Rev8 1/7/2008
75
76
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
77
2.
On the Prompt Mode tab, select a prompt mode: Value 0 1 2 Model Silent Additions Prompt Verbose Description Installation Planner displays only the data entry forms. Installation Planner prompts you to add servers. Installation Planner directs you through creating a plan with a series of prompting forms.
78
GA.Rev8 1/7/2008
2.
On the Process Mode tab, select the options for the processes that you want to run when you create your plan: Additional Servers Enter 1 to add servers to your existing setup (Deployment Server, Enterprise Server, Database Server, HTML Web Server). Enter 0 or leave blank for regular plans. Enter 1 to run the JD Edwards EnterpriseOne installation automatically.
Installation
GA.Rev8 1/7/2008
79
2.
On the Default Mode tab, enter these values into the processing option fields: Value 0 1 2 Description Do not use default values and do not prompt. Prompt for default options at run-time. Default mode. Always use defaults without prompting.
Select whether you want the ability to modify data source information or just take the default values. GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.
Default Environments Default Data Load Default Advanced Parameters Default Languages Upgrade/Update Plan Generation
Select whether you want the ability to select environments or take the default values. Select whether you want the ability to modify data load parameters or take the default values. Select whether you want the ability to modify advanced parameters or take the default values. Select whether you want the ability to select an alternate language or take the default values. Select whether you want the ability to generate a plan automatically from locations and machines defined in a previous version of the software.
GA.Rev8 1/7/2008
81
Note
Do not make any changes on this tab. These values are hard coded in the application
82
GA.Rev8 1/7/2008
2.
On the Completion tab, complete the fields using these values: After defining the plan, the options on this tab specify which processes are run. one of the following values: Value 0 1 2 Description Do not run automatically. Prompt to be run. Run automatically.
GA.Rev8 1/7/2008
83
Enter the default option 2 to run automatically. Enter the default option 2 to run automatically.
84
GA.Rev8 1/7/2008
2.
On the Replication tab, complete the fields using these values: Value 0 1 2 Description Do not use and do not prompt. Prompt for option at run-time. Always use without prompting .
Select whether you have the option to replicate system tables automatically for remote locations. GA.Rev8 1/7/2008 85
Replicate Data Dictionary Tables Replicate Control Tables Replicate Constant Tables
Select whether you have the option to replicate data dictionary tables automatically for remote locations. Select whether you have the option to replicate control tables, menus, and user defined codes automatically for remote locations. Select whether you have the option to replicate constant tables automatically for remote locations. Business data tables are Object Librarian type 280. Select whether you have the option to replicate master tables automatically for remote locations. Business data tables are Object Librarian type 210 and 211.
86
GA.Rev8 1/7/2008
2.
On the Packages tab, enter one of the following values for the remote location package push option: Value 0 1 2 3 Description Do not push packages. Prompt for pushing at runtime. Do not prompt for pushing but display valid packages. Always push default packages without prompting.
3.
When you have chosen the options that you want, click OK.
GA.Rev8 1/7/2008
87
88
GA.Rev8 1/7/2008
Concurrent Tasks
GA.Rev8 1/7/2008
89
90
GA.Rev8 1/7/2008
1.
On Installation Planner, complete these fields: Name Description Status Install Type To Release Enter the name of the installation plan. Enter the description of the installation plan. Choose 10 (the default value) as the status of the installation plan. Click the Install (the default value) radio button. Verify that the release number is E812 (default value).
2.
Click OK to continue.
GA.Rev8 1/7/2008
91
1.
On Location Revisions, complete these fields: Location Description Location Code Enter the location to which this plan applies; the location can be a city, company headquarters, or a division of the company. Enter a description for this location. If this is the base location, this field is only available when you are adding the base location. If you are editing an existing base location, the field is unavailable. If this is the base location, this field is only available when you are adding the base location. If you are editing an existing base location, the field is unavailable.
Parent Location
2.
Click OK.
92
GA.Rev8 1/7/2008
1.
On Deployment Server Revisions, complete or verify these fields: Machine Usage Machine Name Description The value 15 appears by default, indicating that this is a Deployment Server. The name of the Deployment Server appears by default. Enter a long description for the machine. This description should include the location with which this Deployment Server is associated and whether or not it is the primary server. Enter the Release 8.12 release number you are installing or use the visual assist button to choose one from the list. The default value is E812. The value 50 appears by default, indicating that the server type is Intel NT. Your current location is the default value. The user to whom an email is sent when a package is deployed. The default value for primary user is listed in the JDE.INI.
2.
On the Deployment tab, complete these fields: Primary Deployment Server The hierarchy of the servers. Valid values are: 1- Primary Deployment Server (default value)
GA.Rev8 1/7/2008
93
0 - Secondary Deployment Server The server share name of the directory to which you installed Release 8.12 on your Deployment Server. Verify that the server share name for Release 8.12 is \E812. 3. Click OK.
Tip
If you enter invalid information into a field on a tab, a stop sign symbol appears next to the tab name, such as Workstation. Click the stop sign icon in the bottom right of the form to see more info about the error. 4. 5. To add another Deployment Server, click Yes and repeat steps 1 through 3. To continue with Installation Planner setup, click No.
94
GA.Rev8 1/7/2008
1.
On Enterprise Server Revisions, verify or complete these fields: Machine Name Description Release Host Type Location Primary User The name of the primary Enterprise Server. Enter a description for the machine. Enter the release number to which this plan applies, or use the visual assist button to choose one from the list. The default value is E812. Click the visual assist button and select the type of Enterprise Server you are adding to the plan. In this case, Intel NT. The location chosen for this plan appears by default. The user to whom an email is sent when a package is deployed. The default value for primary user is listed in the JDE.INI.
Note
The case of machine name must also match the network ID for that machine. 2. On Enterprise Server Revisions, select the Enterprise tab, and complete or verify these fields: GA.Rev8 1/7/2008 95
Port Number Logical Machine Name Database Type Server Map Data Source
The port number value (6014) for this Enterprise Server as supplied from the JDE.INI. The Installation Planner detects and provides a default value based on the current machine name on which the program is running. Enter the value for your database: O - Oracle Whenever you enter a host type, the Installation Planner populates this field with a default value: machinename - 812 Server Map where machinename is the name of your machine. Verify that the default value is the installation directory path to which you want to install Release 8.12 on the Enterprise Server. Make sure the value is specific to your version of the release. For example, for Release 8.12 the path ends with \E812\ddp.
Installation Path
Caution
You must change the value that defaults into the Installation Path field as shown in the screen capture above. Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. A Deployment Server name appears in this field by default, but it can be changed if necessary.
Note
If you change the port number to a value other than 6014, you must also change this setting in both the Enterprise Server and client JDE.INI. 3. Click OK.
96
GA.Rev8 1/7/2008
4.
On Oracle Connect String, enter a valid value for your Oracle database installation.
GA.Rev8 1/7/2008
97
Warning
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface. 1. On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server.
98
GA.Rev8 1/7/2008
2.
On HTML Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Location Primary User The default value of 30 indicates that this is a HTML Web Server. Enter the name of your HTML Web Server. The name is case sensitive and must not exceed 10 characters. Enter a description of the HTML Web Server machine. Enter E812 to indicate the release number that you are installing. The default value of 50 specifies the server type as Intel NT. Select the correct server type. The location chosen for this plan appears in this field by default. The user to whom an email is sent when a package is deployed. The default for primary user is listed in the JDE.INI.
3.
On the HTML tab, complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). This is the protocol used by the HTML Web Server. Valid values are http or https. This is the Domain Name System (DNS) host name of the HTML Web Server. For example: www.oracle.com This is the port number the HTML Web Server is listening to. For HTTP, the typical port number is 80.
HTTP Port
GA.Rev8 1/7/2008
99
Note
You can choose to implement a HTML Web Server using a different port number. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne. For JD Edwards EnterpriseOne Release 8.12, the value is 6014. Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. Redirector The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system. The user can specify an explicit servlet name in this field. In this case, the redirector functionality cannot be used. The URL generated will point to the specified servlet in the Primary HTML Web Server. Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need. The Portal servlet is: /jdedwards/servlet/com.jdedwards.portal.PortalBuilderServlet The HTML servlet is: /jdedwards/servlet/com.jdedwards.runtime.virtual.VCServlet Installation Path Enter the installation directory path to which you are installing Release 8.12 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running. For Release 8.12 on Oracle Applications Servers, the path ends with E1HTMLServer. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator. 4. 5. Click OK. To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web
Default Login
100
GA.Rev8 1/7/2008
Server.
GA.Rev8 1/7/2008
101
Select OK.
102
GA.Rev8 1/7/2008
To finalize the Installation Plan: 1. On the message box that indicates Installation Planner has concluded, click OK to exit the message box and initiate the Planner Validation Report. If the processing option default was selected, Planner Validation Report automatically prompts you to run this report. If the processing option default was not selected, click Validate on the tree view of your plan to initiate the Planner Validation Report.
GA.Rev8 1/7/2008
103
See Also A separate chapter in this guide entitled: Creating a Remote Installation Plan A separate chapter in this guide entitled: Adding a Server to an Existing Configuration A separate chapter in this guide entitled: Creating a Language-Only Installation Plan
104
GA.Rev8 1/7/2008
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
GA.Rev8 1/7/2008
105
106
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
107
1.
On Installation Planner, complete the following fields: Name Description Status Install Type To Release Include Languages Enter the name of the plan. Enter the description of the plan. Choose 10 (the default value). Click the Install (the default value) radio button. Verify that the release number is E812 (the default value). This is an optional selection that is only available if you have previously specified this Custom plan to install languages. Select yes if you are installing an alternate language.
Note
If you prefer, you can install an alternate language after you complete your master plan. To do so, select the Language Only option on this form. For more information, refer to Creating a Language-Only Installation Plan. 2. 3. Click OK. On Plan Generation, choose one of the following options:
108
GA.Rev8 1/7/2008
Note
The above screen may not always appear if you are rerunning the Planner, which is preferable because the recommended method is to step through the planner rather than taking defaults. See Caution below. 4. On this form, you have the option to automatically enter the locations and machines into the plan that you defined in the previous version of the software.
Choose a method for generating your plan: To manually create your plan, click OK and continue with Entering Location Information. To enable the system to automatically enter the locations and machines from the previous version, click Take Defaults. The machines that were imported from the previous system data source are entered into the current plan. Skip the sections on entering locations, Deployment Servers, Enterprise Servers, and machines/servers, and continue with Entering Shared Data Source Information.
Caution
In order to ensure the validity of all subsequent plan information, it is strongly recommended that even advanced users should not choose this Take Defaults option. Instead, you should step through plan and verify that the Planner is populating information exactly as you expect to match your requirements. To exit the plan, click Cancel.
GA.Rev8 1/7/2008
109
1.
On Location Revisions, complete these fields: Location Description Location Code Parent Location Enter the location to which this plan applies; the location can be a city, company headquarters, or a division of the company. Enter a description for this location. If this is the base location, this field will be grayed out. For the base location, this field will be grayed out.
2.
Click OK.
110
GA.Rev8 1/7/2008
2.
On Deployment Server Revisions, complete or verify these fields: Machine Usage Machine Name Description Displays the value 15 by default to indicate that this is a Deployment Server. The name of the Deployment Server appears by default. Enter a long description for the machine. This description should include the location with which this Deployment Server is associated and whether or not it is the primary server. Enter the release number you are installing or use the visual assist button to choose one from the list. The default value is E812. Displays the value 50 appears by default, indicating that the server type is Intel NT. Displays the current location. Displays the user to whom an email is sent when a package is deployed. The default value for primary user is JDE.
3.
On the Deployment tab, complete these fields: Primary DeployEnter the hierarchy of the servers. Values are: GA.Rev8 1/7/2008 111
ment Server 1- Primary Deployment Server (default value) 0 - Secondary Deployment Server The server share name of the directory to which you installed Release 8.12 on your Deployment Server. Verify that the server share name for Release 8.12 is \E812. 4. Click OK.
Tip
If you enter invalid information into a tab field, a stop sign symbol appears next to the tab name, such as Deployment Server. For more information about the error, click the stop sign icon in the bottom right-hand corner of the form. 5. 6. To add another Deployment Server, click Yes and repeat steps 1 through 3. To continue with Installation Planner setup, click No.
112
GA.Rev8 1/7/2008
1.
On Enterprise Server Revisions, verify or complete these fields: Machine Name Description Release Host Type Location Primary User The name of your primary Enterprise Server. Enter a description for the machine. Enter the release number to which this plan applies, or use the visual assist button to choose one from the list. The default value is E812. Click the visual assist button and choose the type of Enterprise Server you are adding to the plan. In this case, Intel NT. The location chosen for this plan appears by default. The user to whom an email is sent when a package is deployed. The default value GA.Rev8 1/7/2008 113
Note
The case of machine name must also match the network ID for that machine. 2. Continuing on Enterprise Server Revisions, select the Enterprise tab, and complete or verify these fields: Port Number Logical Machine Name Database Type Server Map Data Source The port number value (6014) for this Enterprise Server appears by default from the JDE.INI. The Installation Planner detects and provides a default value based on the current machine name on which the program is running. Enter the value for your database: O - Oracle Whenever you enter a host type, the Installation Planner populates this field with a default value: machinename - 812 Server Map where machinename is the name of your machine. Verify that the default value is the installation directory path to which you want to install Release 8.12 on your Enterprise Server. Make sure the value is specific to your version of the release. For example, for Release 8.12 the path ends with \E812\ddp.
Installation Path
Caution
You must change the value that defaults into the Installation Path field as shown in the screen capture above. Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. A Deployment Server name appears in this field by default, but it can be changed if necessary. Indicates the status of the server.
Note
If you change the port number to a value other than 6014, you must also change this setting in both the Enterprise Server and workstation JDE.INI. 3. Click OK.
114
GA.Rev8 1/7/2008
1.
On Data Source, click OK to continue entering unique data source information, or click Take Defaults to select the default data. If you select the default data, you can skip to Entering HTML Web Server Information.
2. 3.
On Data Source Revisions, verify the accuracy of the Server Map data source. Click OK.
GA.Rev8 1/7/2008
115
Warning
The HTML Web Server is mandatory for the majority of JD Edwards EnterpriseOne applications because the end-user applications are only accessible through a web interface. To enter HTML Web Server information:
1.
On HTML Application Server, click OK to define a new HTML Server, or click Select to choose from a list of existing HTML Servers.
116
GA.Rev8 1/7/2008
If you choose Select, you are presented with the Machine Search table, from which you can make your selection.
GA.Rev8 1/7/2008
117
2. 3.
On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server. On HTML Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Location Primary User The default value of 30 indicates that this is a HTML Web Server. Enter the name of your HTML Web Server. The name is case sensitive and must not exceed 10 characters. Enter a description of the HTML Web Server machine. Enter E812 to indicate the release number that you are installing. The default value of 50 specifies the server type as Intel NT. Select the correct server type. The location chosen for this plan appears in this field by default. The user to whom an email is sent when a package is deployed. The default for primary user is listed in the JDE.INI.
4.
On the HTML tab, complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). This is the protocol used by the HTML Web Server. Valid values are http or https. This is the Domain Name System (DNS) host name of the HTML Web Server. For example: www.oracle.com. This is the port number the HTML Web Server is listening to.
HTTP Port
118
GA.Rev8 1/7/2008
For HTTP, the typical port number is 80. For HTTPS, the typical port number is 443. However, you can choose to implement a HTML Web Server using a different port number. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne. For JD Edwards EnterpriseOne Release 8.12, the value is 6014. Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. Redirector The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system. Explicit The user can specify an explicit servlet name in this field. In this Servlet case, the redirector functionality cannot be used. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need. The Portal servlet is: /jdedwards/servlet/com.jdedwards.portal.PortalBuilderServlet
Default Login
The HTML servlet is: /jdedwards/servlet/com.jdedwards.runtime.virtual.VCServlet Installation Path Enter the installation directory path to which you are installing Release 8.12 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running. For Release 8.12 on Oracle Applications Servers, the path ends with E1HTMLServer. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator. 5. Click OK.
GA.Rev8 1/7/2008
119
6.
To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.
120
GA.Rev8 1/7/2008
1.
On Data Server, choose one of these options: OK If your database resides on a separate server, choose click OK to continue entering unique Data Server information. Select Click this option to select an existing Data Server. Skip Click this option if you do not want to define a Data Server. Continue with the Planner using the environment selection in step 6 of this task.
GA.Rev8 1/7/2008
121
2.
On Data Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type The default value of 25 indicates that this is a Database Server. Enter the name of your Database Server. The name must not exceed 10 characters. Enter a description of the Database Server machine. Enter the release number you are installing, for example, E812. Select the type of Database Server that you are adding to the plan. Values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client - Microsoft Windows 90 Client - Microsoft Windows The Installation Planner populates this field by default, based on previous selections. The user to whom an email is sent once a package is deployed. The default for primary user is JDE.
On the Data tab, complete the following field: Data Source Type Choose the type of data source. For example: O - Oracle
122
GA.Rev8 1/7/2008
4. 5. 6. 7.
Click OK. To add another Data Server, click Yes and repeat steps 1 through 4 to define another Data Server. On Data Source, click OK to continue entering unique shared data source information, or click Take Defaults to select the default data for the shared data sources. On Location, select Yes to add another location, or click No to continue with Installation Planner.
GA.Rev8 1/7/2008
123
1. 2.
On Data Source Revisions, verify the accuracy of the settings for the Data Dictionary data source. Click OK.
124
GA.Rev8 1/7/2008
1. 2.
On Data Source Revisions, verify the accuracy of the settings for the Object Librarian data source. Click OK.
GA.Rev8 1/7/2008
125
1. 2.
On Data Source Revisions, verify the accuracy of the settings for the System data source. Click OK. The Environment Selection screen appears.
126
GA.Rev8 1/7/2008
You can customize any of these parameters by turning off the default option on the Environment Selection form. As you move through the plan, Installation Planner displays a customization form for each parameter that you clear.
GA.Rev8 1/7/2008
127
Setting Up Environments
To set up environments:
1.
On Environment Selection, clear the options for the parameters that you want to customize.
Note
Different parameters appear depending on the options that you chose at the beginning of the planning process. 2. Click OK.
Note
If you selected the default option, which is to include all parameters, skip to Working with Environment Data Sources . Skip the tasks for those parameters that you did not clear.
128
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
129
Selecting an Environment
To select an environment:
1.
Note
J xxxxxx environments are required for the HTML Web Server. To set up multiple environments, select and define them one at a time.
130
GA.Rev8 1/7/2008
Note
The data load radio buttons on this form are no longer applicable as of JD Edwards EnterpriseOne Release 8.12 because data is automatically loaded by the Platform Pack Installer. For additional details, refer to Loading Data (Demo Data and Production Data).
GA.Rev8 1/7/2008
131
Selecting Languages
To select languages:
1. 2. 3. 4.
On Language Selection, select the language you want to set up for the environment. From the Row menu, click Select. Repeat the above steps until all your languages have been selected. Click OK.
132
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
133
1. 2. 3.
On Data Source Revisions, verify the data source for your Business Data. From the Form menu, click Advanced. Click OK.
134
GA.Rev8 1/7/2008
1. 2. 3.
On Data Source Revisions, verify the information for your central objects data source. Click OK. On Data Source Revisions, click the Advanced form option.
GA.Rev8 1/7/2008
135
4.
On Advanced Set-Up, because the central objects data source must be Unicode, verify Unicode is checked. Also ensure that LOB is selected.
136
GA.Rev8 1/7/2008
1.
On Data Source Revisions, verify the accuracy of the Control Tables data source. Data Source Name Server Name Object Owner ID Verify the name of the data source. Verify the name of the Enterprise Server. Enter the name of the owner of this object
Note
Control tables data sources are specific to the environment and pathcode. 2. Click OK.
GA.Rev8 1/7/2008
137
1. 2.
On Data Source Revisions, verify the accuracy of the data dictionary data source. Click OK.
138
GA.Rev8 1/7/2008
1.
On Data Source Revisions, verify the accuracy of the versions data source.
Note
Versions data sources are specific to the pathcode, and the Unicode flag on the Advanced form must be selected. 2. Click OK.
GA.Rev8 1/7/2008
139
1.
Choose one of the following options: Click Yes to add a remote location.
Repeat all processes for adding a location starting with Entering Location Information. Refer to the Creating a Remote Installation Plan task in the Installation Planner Utilities section for information about adding remote locations to your plan. 2. Click No to conclude the Installation Plan setup.
140
GA.Rev8 1/7/2008
To finish the Installation Plan: 1. Click OK to exit the concluding message box and initiate the Planner Validation Report. If you selected the processing option default, the Planner Validation Report automatically prompts you to run this report. If you did not select the processing option default, click Validate on the tree view of your plan to initiate the Planner Validation Report.
GA.Rev8 1/7/2008
141
See Also A separate chapter in this guide entitled: Creating a Remote Installation Plan A separate chapter in this guide entitled: Adding a Server to an Existing Configuration A separate chapter in this guide entitled: Creating a Language-Only Installation Plan
142
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
143
144
GA.Rev8 1/7/2008
145
As listed in this table, Installation Workbench includes the components, some or all of which might be used for yourinstallation, depending on your installation plan: Installation Workbench Compon- Functional Description ent Initial Tasks Workbench When using unattended workbench mode, this workbench runs Release Master after Installation Workbench is started and before Location Workbench begins. This workbench copies all locations that are defined in the plan from the F9654 and F984021 tables in the Planner data source to the System - 812 data source. Copies all data sources that are defined in the plan from the F98611 and F986115 tables in the Planner data source to your System - 812 data source. It also updates the F98401 table to indicate completion. Copies the F0094, F00941, and F00942 tables, as well as the F986101 table for each environment, from your Planner data source to your System 812 data source. It then updates the F98403 table to indicate completion. Depending on the plan settings, it also runs a batch application to copy new generic text and to create and populate Object Management Workbench and version tables. Copies the F9650 and F9651 tables from the Planner data source to the System - 812 data source. It then updates the F98402 table to indicate completion and uses the environment information to populate the F986101 and F98611 tables in the Server Map data source. Only valid environments, data sources, and server map tables are created. Copies the language text from the MSDE database that contains the language text into the control table database and central object database. This workbench runs only for users who are adding an alternate language to their installations. Transfers the F9603 and F9631 tables from the Planner data source to the System - 812 data source. It then updates the F98404 table to indicate completion.
Location Workbench
Environment Workbench
Machine Workbench
Package Workbench
146
GA.Rev8 1/7/2008
See Also Major Technical Tables in this guide for more information about individual tables and their uses.
Note
Even after the Workbenches are complete, you will still need these settings on the Deployment Server's share in order to successfully perform client installs.
GA.Rev8 1/7/2008
147
To load demo data in Production or Prototype environments, you must run a UBE (R98403E) to copy the data to those environments.
Note
The "from" (source) environment can be the Planner environment or your Pristine environment.
Caution
You should not change the record selection on this UBE. 1. Run R98403E using the XJDE0009 version and set the processing options as follows:
148
GA.Rev8 1/7/2008
2.
On Processing Options 1-4, complete these fields: Option 1 Option 2 Option 3 Enter the name of the source environment, which is the environment of the table to be copied. For example, JDEPLAN. This field must be blank because this UBE is used to copy a mixture of business data and control tables which are specified to environments, not data sources. Enter the name of the target environment, which is the environment to which you wish to copy the table. In this case, you would specify either the Production or Prototype environments. For example, PD812. This field must be blank because this UBE is used to copy a mixture of business data and control tables which are specified to environments, not data sources.
Option 4
GA.Rev8 1/7/2008
149
3.
4.
On Processing Options 5-9, complete these fields: Option 5 The recommended value is 1, which copies the table. The default value is 0, Proof Mode. The recommended value is N, which copies tables only if they exist in the source. Enter Y to copy tables whether or not they exist in the source data source.
Option 6
150
GA.Rev8 1/7/2008
Option 7
The default value is N. The recommended value is Y, which recreates tables that already exist in the target data source.
Note
If you do not recreate the tables, you will end up with a mixture of production and demo data in the tables. The default value is N. The recommended value is N, which forces a copy of the data, ignoring the CPYD flag.
Option 8
Note
A value of Y will leave almost all tables empty. That is, a production data load. The default value is N. The recommended value is N, which creates the indexes on the tables before copying the data. This prevents duplicate rows.
Option 9
Note
A value of Y copies the data and then create the indexes. The default value is N. 5. Click OK to accept the values and start the UBE.
GA.Rev8 1/7/2008
151
Note
If running an Install, you can set up the queues at any stage before running a Package Build. If you set up queues after the Installation Workbench, sign onto DEP812. To create the job queue: 1. 2. Enter GH9013 in the Fast Path field and start the Job Queues program (P986130). Click Add.
3.
On Job Queue Revisions, add a queue by completing these fields: Host Job Queue Default Queue Job Queue Status Queue Type Maximum Batch Jobs Port Number Enter the Enterprise Server name. Enter the job queue name. Turn on this option by clicking the check box. Enter 01. Enter 01. Enter a value that equals the number of processors on the Enterprise Server machine. Enter 6014. If you receive a Network Failed error, you can safely ignore it in this
152
GA.Rev8 1/7/2008
5.
On Job Queue Revisions, add a queue by completing these fields: Host Job Queue Default Queue Job Queue Status Queue Type Maximum Batch Jobs Port Number Enter the Enterprise Server name. Enter the Job Queue name: I-ACTIVE. Turn off this option by clicking the radio button. Enter 01. Enter 01. Enter a value that equals the number of processors on the Enterprise Server machine. Enter 6014.
GA.Rev8 1/7/2008
153
154
GA.Rev8 1/7/2008
4.
5.
To set a break before or after a workbench, choose the workbench name, and, on the Row menu, select Break Before or Break After. You can clear task breaks on the Row menu.
6.
On Task Break Revisions, specify the following fields: email Address (optional) Task Break Task Break Short Text (required) Optional Detail (optional) Specify (or choose from a list) the address book number of the person who is to be notified when the task break occurs. Specify (blank) for no task break or 2 for a customer task break. If the field is left blank, then no task break is configured. Enter a short text description of the task break. Enter detailed information about the task break.
7.
Click OK. Task Break Revisions closes, and Work with Task Breaks reappears. Specify any further task breaks.
8.
Click Close.
GA.Rev8 1/7/2008
155
If you specified attended workbench mode, use the following procedures, including the Initial Tasks Workbench, to complete the workbenches. If you specified unattended workbench mode, the process begins and all workbenches are completed automatically, unless task breaks are set. If you did not set any task breaks, continue with Working With the Enterprise Server.
3.
156
GA.Rev8 1/7/2008
You might want to change the status of one or more of the initial workbench tasks. To change the status of a task, use the following procedure. 1. 2. Enter GH961 in the Fast Path field to open the System Installation Tools menu. Double-click Custom Installation Plan.
GA.Rev8 1/7/2008
157
3. 4.
On Work with Installation Plans, select your installation plan. Select Expand on the Row menu. The plan components, including the initial tasks, appear.
5. 6.
Select the task whose status you want to change. On the Row menu, click Disable, Enable, or Complete (see the table below). The task status changes. Row Menu Option Disable Enable Complete Meaning Displays status of 70 to indicate the task is incomplete, and will not be rerun. Displays status of 10 to incidcate the task will be rerun. Displays status of 60 to indicate the task is complete, and will not be rerun.
158
GA.Rev8 1/7/2008
1. 2.
On Location Workbench, verify that all of your locations are listed. Select Configure from the Form menu. Locations are configured, and the Data Source Workbench form appears. The system updates the Detail Status to 60 and changes the Status Description from Validated to Installed.
GA.Rev8 1/7/2008
159
2.
Select Configure from the Form menu. Your data sources are configured, and the Environment Workbench form appears. When the system has configured your data sources, it updates Detail Status to 60 and changes the Status Description from Validated to Installed.
160
GA.Rev8 1/7/2008
1. 2. 3. 4.
On Environment Workbench, review each environment and its associated parameters to make sure the values are correct. After you review the environments, select Configure. When Environment Workbench has completed, verify that the status of each environment has been updated to 60 and that the status description has changed from Validated to Installed. Using Adobe Acrobat, review all XJDE reports, and confirm that all configuration statuses indicate Success.
GA.Rev8 1/7/2008
161
Note
Only valid environments, data sources, and server map tables are created. You use this procedure when running Workbench in attended mode, or if a task break is set before Machine Workbench.
1. 2.
On Machine Workbench, review each server and its associated parameters for the correct values. Select Configure from the Form menu. When the system has configured your servers, it changes the detail status to 60, and Status Description changes from Validated to Installed.
162
GA.Rev8 1/7/2008
1. 2.
On Package Workbench, review your packages. Select Configure from the Form menu.
GA.Rev8 1/7/2008
163
164
GA.Rev8 1/7/2008
To configure your remote locations: 1. 2. 3. On Remote Location Workbench, Release 8.12 displays all remote location activities in the detail area. On the Form menu, select Configure to launch the workbench. After all remote location activities are complete, click Next.
GA.Rev8 1/7/2008
165
Note
Post Install Procedures still need to be completed from a client. See Performing Post Installation Tasks.
166
GA.Rev8 1/7/2008
Note
Terminology. The contents of this chapter are based on the JD Edwards EnterpriseOne recommendations and guidelines for developing a configuration solution for a rapid software implementation. These configuration solutions, originally called Rapid Start, are called Oracle Business Accelerators for JD Edwards EnterpriseOne. Business Accelerators provide the same features and functionality as Rapid Start and now align with other Oracle software offerings of the same name. Some older content will still refer to the Rapid Start name.
Important
Starting with JD Edwards EnterpriseOne Release 8.12, Business Accelerator configurations are delivered as par (portable archive) files. As a result, you must run Data Configuration Workbench in nonRapid Start mode regardless of whether you are a Business Accelerator customer. For details on the installation of Business Accelerator configurations refer to this web site on the Update Center: http://www.peoplesoft.com/corp/en/update_fix/kgwrapper.jsp?app=uc For an overview of Business Accelerator Configurations and Configuration Packages, on the above page refer to the link entitled Loading Business Accelerator Configurations. The URL for that link is: http://maintenance.peoplesoft.com/softwaredownloads/RSData/content/documents/overview%20of%20bu siness%20accelerator%20configurations%20and%20configuration%20packages.doc Understanding Data Configuration Workbench Adding a Data Configuration Plan Running a Data Configuration Plan Troubleshooting Data Configuration Workbench Installation
GA.Rev8 1/7/2008
167
When you run the data configuration plan in final mode, the system: 1. 2. 3. 4. 5. Submits the Data Configuration Loader program. Replaces business data. Updates system, version/central objects, and control tables. Generates a PDF that lists the number of records updated in the affected tables. Locks the grid area of the Data Configuration Pathcode/Environment Details form, preventing you from making revisions to the environments that are selected for that data configuration plan.
The system stores the information listed on the PDF in the Rapid Start Reporting Workfile table (F01RS010).
Note
To modify the F01RS001, F01RS002, and F01RS010 tables, use only Data Configuration Workbench. The system also enables you to revise data configuration plans and to rerun data configuration plans if errors and mistakes are encountered during the data configuration process.
168
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
169
Components Versions
Tables Updated
Versions List (F983051) Versions Tag Table (F983052) Event Rules - Link Table (F98740) Event Rules - Specification Table (F98741) Report Design Aid Text Information (F98760) Report Design Aid Specification Info (F98761)
If you have previously or inadvertently loaded the Data Configuration Workbench in Rapid Start mode (that is, the Install Rapid Start Data? field was set to Yes as shown in the section entitled: Adding a Data Configuration Plan), you can get a complete listing of the business data tables that the system updates as well as the specific values with which the system updates each of the tables. Refer to Appendix E: Business Data Reports for your region in the JD Edwards EnterpriseOne Configuration Methodology 8.12 Guide.
170
GA.Rev8 1/7/2008
1. 2. 3.
On the deployment server, log into the JDEPLAN environment as user JDE. From the System Installation Tools menu (GH961), select Data Configuration - Installs Only. On Data Configuration Workbench, click Add.
4.
On Data Configuration Pathcode/Environment Details, complete these fields: Enter the Data Configuration Plan Name Install Rapid Start Data? Enter an alphanumeric user-defined plan name identifiying the plan. Enter N regardless of whether you have purchased a Rapid Start solution.
GA.Rev8 1/7/2008
171
Note
Starting with JD Edwards EnterpriseOne Release 8.12, Business Accelerator configurations are delivered as .par (portable archive) files. As a result, you must run Data Configuration Workbench in non-Rapid Start mode regardless of whether you are an Oracle Business Accelerator for JD Edwards EnterpriseOne customer. If you have purchased a Business Accelerator configuration, for implementation details you should refer to to the web sites list in Important at the beginning of this chapter. 5. Click OK.
172
GA.Rev8 1/7/2008
4.
The system submits the Data Configuration Loader program and generates a PDF that displays the updates that will occur if you submitted in proof or the updates that did occur if you submitted in final.
Note
The Submit Data Configuration form only displays if you set the Data Configuration Workbench in Rapid Start mode (that is, you set the Install Rapid Start Data? field to Yes).
GA.Rev8 1/7/2008
173
Datasource cannot be created Check network connections. If the database in error is an MSDE database, verify that its location is correct. Verify that the Business Data Local data source exists in the Datasource Master table (F98611) before rerunning Data Configuration Workbench. If the database in question was created by the installation process, verify the environment, path code, and so on.
Table does not exist Error opening table 174 Check network connections. If the database in error is an MSDE database, verify that its location is correct. If the database in question was created by the installation process, verify the environment, path code, and so on. Use UTB to verify that the table exists or not. GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved. Check network connections. If the database in error is an MSDE database, verify that its location is correct. If the database in question was created by the installation process, verify the environment, path code, and so on. Use UTB to verify that the table exists.
Resolution
Check network connections. If the database in error is an MSDE database, verify that its location is correct. If the database in question was created by the installation process, verify the environment, path code, and so on. Use UTB to verify that the table exists. In UTB, click Find and check for any errors.
GA.Rev8 1/7/2008
175
176
Tip
Cluster Software Considerations. If using cluster software, skip this step. Before you attempt to start Release 8.12, complete the steps in the Microsoft Windows Cluster chapter of Release 8.12 on a Cluster in JD Edwards EnterpriseOne Tools 8.96 Server and Workstation Administration Guide. The PORTTEST program initializes a user and an environment (assuming that Release 8.12 is installed and configured correctly). To verify that Release 8.12 is installed correctly, you must run the PORTTEST program for each environment. To verify the Enterprise Server installation using PORTTEST: 1. 2. 3. Log on to the Enterprise Server as JDE. Open a DOS command window. To verify that Release 8.12 is installed correctly on the Enterprise Server, enter these commands: d: [or the appropriate drive letter] cd \JDEdwards\E812\ddp\System\bin32
GA.Rev8 1/7/2008
177
PORTTEST userid password environment where userid is a valid Release 8.12 user, password is the password for that user, and environment is the environment you are verifying. These parameters are case-sensitive. Enter the PORTTEST command for each environment.
Tip
Troubleshooting. The program should display messages indicating the selection of records from an Release 8.12 table. If it does not, review the jde_###.log that was specified in the JDE.INI on the Enterprise Server. If PORTTEST fails to run, see Using the PORTTEST Checklist for diagnostic assistance.
Note
When you stop JD Edwards EnterpriseOne network services on a Microsoft Windows server, some processes might not stop. To stop the services completely, you should either shutdown and restart your Enterprise Server or complete the remaining steps in this procedure. 4. 5. On the Enterprise Server, go to Task Manager and right-click any JD Edwards EnterpriseOne process that is still running. Select Debug.
178
GA.Rev8 1/7/2008
This command takes you to debug mode in Microsoft Visual C++. 6. Stop the debug process and exit Visual C++. The JD Edwards EnterpriseOne process that you selected shuts down. Repeat this process for each JD Edwards EnterpriseOne process that is running.
optionally prompted to customize the data source. Given that the standard environments do not always follow the defaults that are specified in the *ENV template, JD Edwards EnterpriseOne provides preconfigured records for the standard environments. Thus, the *ENV template is only used for custom environments.
This section discusses: Understanding Data Classes Creating a New Data Class Modifying the Data Source Template Associating Table Data Classes
This should only be used by a JD Edwards EnterpriseOne administrator. Go to GH9611 and open Table Data Classes. Use the QBE to filter the list of tables in the grid. Select one or more tables whose data class will be changed. Click Select. Type in the new data class value and click OK. Once these three steps have been taken, planner will prompt for the new data source and create OCM mappings for the new data source whenever an environment is added to a plan and the plan is finalized. Environment ENV1 ENV1 ENV1 ENV1 ENV1 ENV1 ENV1 ENV1 ENV2 ENV2 ENV2 ENV2 ENV2 ENV2 ENV2 ENV2 Object Name DEFAULT F0094 F9860 F9200 F0004 F983051 GT92002 GT9860A DEFAULT F0094 F9860 F9200 F0004 F983051 GT92002 GT9860A User/Group *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC *PUBLIC Data Source Business Data ENV1 System - 812 Object Librarian - 812 Data Dictionary - 812 Control Tables ENV1 Versions - PY812 Data Dictionary - 812 Object Librarian - 812 Business Data ENV2 System - 812 Object Librarian - 812 Data Dictionary - 812 Control Tables ENV2 Versions - DV812 Data Dictionary - 812 Object Librarian - 812
You also can print Release 8.12 reports, modify existing printers, and delete printers. These tasks are described in detail in the JD Edwards EnterpriseOne Tools 8.96 System Administration Guide. Refer to that document to learn more about setting up a printer to run from the Release 8.12 Enterprise Server.
182
GA.Rev8 1/7/2008
1.
On the Printers menu (GH9013), select Printers (P98616). The Printers form appears.
2.
On the Printers form, click Add Printer. The welcome page for the Printer Setup director appears. This page describes the tasks that the director helps you perform.
3.
Review the welcome page and click Next. The Platform Information form appears. The platform type may appear by default, depending on the operating system on which Release 8.12 is running.
4.
On Platform Information, complete these fields: Platform Type Print Server Name Enter the platform type on which you are installing or use the visual assist button to select a platform type. Enter the name of the print server for the printer you are setting up. Valid characters are all alpha (A-z), numeric (0-9), period ( . ), and dash ( - ). Release 8.12 uses this name, along with the print shared name, to create the printer name, which is unavailable for modification on the subsequent form. For printing reports to a non-network printer, leave this field blank. Enter the share name of the printer you are setting up. All characters are valid except the forward slash ( / ) and the backslash ( \ ). Release
GA.Rev8 1/7/2008
183
8.12 uses this name, along with the print server name, to create the printer name, which is unavailable for modification on the subsequent form. 5. After you complete the requisite fields, click Next to access the Printer Setup form. Use this form to set information for the printer such as the printer model, physical location of the printer, printer definition language (PDL), and paper types. 6. On the General tab, complete these fields: 7. Printer Model Printer Location
On the Details tab, in the box labeled Printer Definition Language, select one of these options: PostScript PCL Line Printer Custom
8.
In the Default box, specify one of the Printer Definition Language options as the default value. You can select multiple PDLs, but only one default PDL. A user can override this default PDL at the time a batch process is submitted. Choosing PostScript or Printer Command Language (PCL), Release 8.12 disables the Line Printer option. Choosing Line Printer, Release 8.12 disables the PostScript and PCL options. When choosing the Line Printer option, this logic occurs: Release 8.12 disables the grid at the bottom of the form and any paper types you have chosen are cleared. JD Edwards EnterpriseOne automatically provides a printer type of *JDE LINE PAPER for the printer. The Fields in the box labeled Line Printers are used to set the paper dimensions and line parameters. This procedure is explained in later steps in this section. The custom option uses advanced features of the printers application, which are explained in the later steps in this procedure.
9.
On the Details tab, when choosing the PostScript option, the Paper Source box appears and you can change these options: Max Number of Paper Sources Default Paper Source Enter a numeric value in this field to indicate the number of paper trays this printer has available. Enter a numeric value in this field to indicate which tray number you want Release 8.12 to draw paper from as the default tray.
10. On the Details tab, when choosing the Line Printer option, fields appear in a box labeled Line Printers, 184 GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.
which you use to set the paper dimensions and line parameters. Complete these fields: Characters Per Inch Columns Per Page Lines Per Inch Lines Per Page Printer Paper Width Printer Paper Height Enter a value to specify the number of characters in one horizontal inch. Enter a value to specify the number of characters in one line of text in the specified report. Enter a value to specify the number of lines of text in one vertical inch. Enter a value to specify the number of lines of text on one printed page. Displays a value that is calculated automatically based on the values entered in the Line Printers box. Displays a value that is calculated automatically based on the values entered in the Line Printers box.
11. On the Details tab, the Custom option lets you specify a conversion filter to use. When choosing the Custom option, a field appears beneath the Custom checkbox. Enter the name of the conversion filter you want to use or use the visual assist to select a filter from the Conversion Program Search and Select form. 12. If you do not want to change or add a conversion filter, skip to step 16 in this task. To change or add a conversion filter, from the Form menu, select Advanced, and continue with the steps in this procedure. The Advanced option is enabled only when Custom has been chosen. The Work With Conversion Programs form appears. 13. Either click Add, or highlight one of the filters and click Copy or Select. The Advanced Conversion Program form appears. 14. Change one or both of these fields: Conversion Program If you clicked Add or Copy on the previous form, the Conversion Program field is enabled. Enter the name of the conversion program that you want to add or copy. When making a copy, the Parameter String field is populated with the string that you highlighted on the previous form. The JD Edwards EnterpriseOne system automatically enters the parameter string in native commands based on the host type from which you are printing and the type of printer (PostScript, PCL, or line).
Parameter String
15. Click OK. The Work with Conversion Programs form appears. Click Close. The Printer Setup form appears. 16. In the grid at the bottom of the Printer Setup form, double-click the row header for each paper type that your
GA.Rev8 1/7/2008
185
printer supports. A checkmark appears in the row header for each paper type that you select.
Note
You can add new paper types as necessary. Instructions are included later in this task. 17. In the Default Type column, enter the numeral 1 in the row for the paper type you want to use as the default. select only one paper type as the default. A user can override the default paper type when a batch process is submitted.
18. To add a new paper type, continue with these steps: 19. From the Form menu, select New Paper Type. The Work With Paper Types form appears. 20. Click Add. The Paper Type Revisions form appears. 21. Complete these fields: Paper Type
186
GA.Rev8 1/7/2008
The software saves the new paper type. 22. Click OK to return to the Work With Paper Types form, and then click Close to return to Printer Setup. The new paper type is available in the grid on the Printer Setup form. All previous paper type selections are cleared and must be reselected if you want to use them again. 23. When finished entering information for the printer on the Printer Setup form, click End. Release 8.12 saves the new printer setting and returns you to the first form in the Printers application. Platform Type Server Name Printer Name Define the type of physical hardware on which the database resides. Define the computer that receives documents from clients. Enter a name that refers to a shared resource on a server. Each shared directory on a server has a share name, which is used by clients to refer to the directory. Define these attributes for your printer: Printer Model Printer Location
Printer Model
Designates the physical location of the printer Enter a user defined code (H98/PT) to define the type of printer paper, such as letter or legal. For example, LETTER, LEGAL, and A4. Define the width of the paper for this paper type. This value is in the unit of measure specified by Unit of Measure. Define the height of the paper for this paper type. This value is in the unit of measure specified by Unit of Measure. Enter a user defined code (00/UM) to define the quantity in which to express an inventory item. For example, CS (case) or BX (box). Form-specific information indicates the unit of measure in which the paper height and width are entered. For example, IN = Inches and MM = Millimeters. Define the number of columns per page. For example, 80 or 132. Define the horizontal printing density in characters per inch. You should only define values that are supported by your printer. Define the number of lines per page. For example, 60 or 66. Define the line spacing in lines per inch. You should only define values that are supported by your printer. Values are: 4 - IBM 5219, 5224, 5225, and 3287 printers only 6 - IBM 5224 printer only
GA.Rev8 1/7/2008
187
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.
188
GA.Rev8 1/7/2008
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
Object Status
5.
Click OK, and then click Cancel to access the Work With Default Printers form.
GA.Rev8 1/7/2008
189
6.
To change the status of a default printer, select a default record and, from the Row menu, select Change Status. If another printer is already set as the active default, an error occurs. To change the original default printer to inactive, select it, select Change Status on the Row menu, and then select the new printer as the default.
190
GA.Rev8 1/7/2008
Note
The JD Edwards EnterpriseOne 8.12 Installation delivers pre-built packages that are ready for use as delivered. For the workstation to reflect the language installed on the Deployment Server, you must perform tasks for both the Enterprise Server and workstations, in addition to the procedures to verify and modify the JDE.INI on the workstations and the JDE.INI on the Enterprise Server. See Also Refer to Language Process Overview for more information about how you enable multilingual installations on workstations. JD Edwards EnterpriseOne Web Development Client Installation and Configuration Guide JD Edwards EnterpriseOne Tools 8.96 Package Management Guide
GA.Rev8 1/7/2008
191
Note
Refer to the JD Edwards EnterpriseOne Web Development Client Installation Guide for additional details on installing the Web Development Client. Prerequisites Before installing Release 8.12 on a workstation used for development, you must install the Microsoft Visual C++ Compiler. The specific version of the compiler is detailed in the Minimum Technical Requirements (MTRs) located on Customer Connection. Refer to Accessing Minimum Technical Requirements. Also refer to the appropriate Microsoft documents for installation information. The names of the Deployment Server, Enterprise Server, and client workstation cannot exceed 15 characters in length.
Note
You do not need full administrator privileges to install Release 8.12 on the workstation. However, you do need proper privileges for writing to the disk and the registry. If you do not have these privileges, you will receive a warning during the installation. If you receive a warning, contact your administrator, who can perform the installation or can grant proper disk and registry access. For more information about granting disk and registry access, see Granting Access to the Software Installation Directory. Connectivity is required for: Read/write access to this client install directory on the primary Deployment Server in the base location: \oneworld Read access to the subdirectories located under this directory: \pathcode\package For example: \\deployment_server_name\E812\PD812\package Read/write access to this directory on the primary Deployment Server: \client For example: \\deployment_server_name\E812\client
192
GA.Rev8 1/7/2008
See Also JD Edwards EnterpriseOne Tools 8.96 System Administration Guide for more information on the Install Manager tool and for editing and configuration options.
Caution
Before starting a JD Edwards EnterpriseOne workstation installation, you must close all other applications running on that machine. The installation process may not run correctly if other applications are open.
GA.Rev8 1/7/2008
193
To create a desktop shortcut: 1. 2. 3. 4. To edit the Start in: field, in Microsoft Windows Explorer or on the desktop, right-click the shortcut. Click Properties, and then click the Shortcut menu. Double-click the Release 8.12 InstallManager shortcut to start the Release 8.12 installation manager. Skip to the next task entitled: Using a Shared Drive. Begin with step 2.
Tip
Click the Filters ON button to narrow the displayed list of available packages. This can help you find the package you want. Notice that a short description of each package appears below the list. 5. On Client Workstation Setup Type, complete these fields: Select Setup Type Select Development or Production objects. You should only select the Development option if you intend to develop Release 8.12 applications.
Note
Select the Development option only if you intend to develop JD Edwards EnterpriseOne applications. Select the drive and directory in which to install the package. For example, this is the typical path for Release 8.12:
Install Path
194
GA.Rev8 1/7/2008
c:\E812 6. To install the package, click Finish. InstallManager shows the status of the installation process through a series of forms. The Congratulations form indicates that the installation finished successfully. InstallManager creates a Release 8.12 shortcut in the Programs folder of your Start menu and on your desktop. 7. Reboot if necessary.
Caution
The JD Edwards EnterpriseOne client workstation installation process verifies that several of the system DLL files are current. If they are not current, you receive a message to reboot your system. When you reboot, the system updates the DLL files in your Microsoft Windows directories.
Note
When you open Release 8.12 after installing the client workstation, or upgrading to Release 8.12, a security violation screen may appear. Click Get Authorization to obtain a local license, and then click OK.
GA.Rev8 1/7/2008
195
Using the typical parameter installs the development objects. -t Compact Using the compact parameter does not install the development objects. -r Using the -r parameter indicates you want to uninstall the previous installation before continuing. The results of the uninstallation appear in c:\jdeinst.log.
Caution
If the specified installation path already exists, the directory structure contents are overwritten. 5. To run the command line, click OK. During a silent installation, Release 8.12 Client Installation appears in the Microsoft Windows taskbar. 6. Verify a successful installation by viewing the c:\jdeinst.log file.
Note
When you open Release 8.12 after installing the client workstation, or upgrading to Release 8.12, a security violation screen may appear. Click Get Authorization to obtain a local license, and then click OK.
196
GA.Rev8 1/7/2008
For user and group profiles, you should use the preloaded users to perform the installation process. The system administrator needs to create a user profile before the user can log on to Release 8.12. All users are assigned a language preference code within the user profile. The language preference code field specifies which language is presented on the applicable form or report. You can set up your users and groups when determining how groups are to be organized and what preferences each group shared to have. For languages, the JDE.INI on the Windows-based Deployment Server are updated automatically. For multiple language usage, both the Enterprise Server and workstation JDE.INI need to be modified for the preferred language being installed. See Also JD Edwards EnterpriseOne Tools 8.96 System Administration Guide for more detailed information about setting up group profiles and how to use them, as well as for information about defining user display preferences.
Warning
If the ODBC Data Sources do not have this registry value on the workstations, some records will not be inserted into tables and Insert Record Failed errors will appear. Use this procedure to modify settings in the JDE.INI in this directory on the Deployment Server: \JDEdwards\E812\OneWorld Client Install\Misc
1.
Note
For language installations, ensure that the workstation is set up correctly for language preferences to display and print forms. If multiple languages are installed, verify that the appropriate JDE.INI values are set to your preferred language. See Language Process Overview for appropriate values. [INTERACTIVE RUNTIME] For the language you are installing, enter: Initial_Language_Code = x where x is the value for the language installed or, if multiple languages are installed, for the preferred language. Verify that the LocalCodeSet value and code page setting are set to the appropriate values. The system reads the JDE.INI setting for the installed language. Verify that the port number specified for ServiceNameListen and ServiceNameConnect matches the port number in the Enterprise Server JDE.INI.
[INSTALL]
[JDENET]
2.
198
GA.Rev8 1/7/2008
to access the server where the media object queues reside. For example: N:\Mediaobj\ComposerCBT. 5. 6. To change an existing media object queue, click Find to display a list of queue names and their paths. On Work With Media Object Queues, select the queue name you want to modify.
7. 8. 9.
On Media Object Queues, change the information in the Queue Path On-Line field to reflect the new location. Copy the image files and OLE objects to the new location. Exit Release 8.12 and log back on to enable the changes.
200
GA.Rev8 1/7/2008
3.
On Media Object Queue Revisions, complete these fields: Path Replace the existing default value with: http:\\Server_Name\E812\f1search.htm where server_name is the server on which you copied the Help files. Enter the value 09.
Type 4. 5.
Copy the Help to the new location. Exit Release 8.12 and log back on to enable the changes.
GA.Rev8 1/7/2008
201
202
GA.Rev8 1/7/2008
203
Note
Not all directories are available. The directory names listed in the table below are subdirectories of the \JDEdwards\E812 directory structure. You can apply the indicated permissions to all subdirectories and files except where noted.
204
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
205
206
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
207
Note
SVG is a graphics file format and web development language based on XML that enables dynamic creation of high-quality graphics with precise structural and visual control. It is based on standards defined by the World Wide Web Consortium (http://www.w3.org/TR/SVG/) .
Tip
The installation of the SVG viewer may require administrator authority on your client machine.
208
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
209
The PortalLite directory includes a set of HTML files that make up the default Home Page. Even though this directory is on the Deployment Server by default, the direcotry could reside anywhere on the network, such as on a HTML Web Server or on a local workstation. When the Release 8.12 client is installed, the system updates the client JDE.INI to point to the location of the PortaLite directory. For example, if the name of the Deployment Server is DepServer1 and the share name is E812, the [Explorer] section of the JDE.INI is updated as follows: [Explorer] ExplorerHomeURL="\\DepServer1\E812\SolutionExplorer\portallite\index.html" ExplorerStart=INTERNET You can change the above parameters in the JDE.INI to display any HTML file or URL as the default Home Page. This table describes these parameters: [Explorer] Parameter ExplorerHomeURL= Description Defines the URL or filename of the Home Page that is displayed when the user logs on. The default value is: \\Depserver1\E812\SolutionExplorer\portalite\index.html ExplorerStart= Defines the Explorer start mode. Values are: INTERNET TASK This is the default value. When you start Solution Explorer, the system displays the Internet view first. When you start Solution Explorer, the system displays the last task view the user viewed. To display a specific task view, use this syntax: ExplorerStart=TASK:xx where xx is the task ID of the task view.
GA.Rev8 1/7/2008
211
Configuring JD Edwards EnterpriseOne for Use with Vertex Quantum Tax Applications
This topic describes how to configure JD Edwards EnterpriseOne to use the Vertex Quantum tax applications. If you do not use these applications with JD Edwards EnterpriseOne, skip this section. Release 8.12 can be used with the following Vertex Quantum tax applications: Vertex Quantum for Payroll Tax Vertex Quantum for Sales and Use Tax
The Vertex Quantum applications should be installed on your system before starting the configuration tasks.
Note
The Vertex Quantum applications can be used with the Indexed Sequential Access Method (ISAM) database or Oracle database (for either of the Vertex Quantum applications) or the SQL Server database (for Vertex Quantum for Sales and Use Tax). The ISAM database is installed as part of the Vertex Quantum application installation. See Also Vertex Quantum for Payroll Tax - Administrator's Guide Vertex Quantum for Sales and Use Tax - Administrator's Guide Before configuring Release 8.12 for use with Vertex Quantum applications, install Vertex Quantum for Payroll Tax, Vertex Quantum for Sales and Use Tax, or both on the Enterprise Server. For information about installing the Vertex Quantum applications, refer to the Vertex Quantum administration guides listed above. When installing the Vertex Quantum applications, note the following: When using DB2/Universal Database (UDB), you must install the Vertex ISAM database. Vertex does not support DB2/UDB. Note the directory path on the Enterprise Server for the directory in which the Vertex Quantum applications are stored. This information is needed when copying the Vertex libraries into the Release 8.12 directory structure. For Vertex Quantum for Sales and Use Tax, you can install the ISAM database version of the Vertex Quantum application, or you can use the SQL Server or Oracle database. For Vertex Quantum for Payroll Tax, you can install the ISAM database version of the Vertex Quantum application, or you can use the Oracle database. You cannot use SQL Server with Vertex Quantum for Payroll Tax. When using the Vertex ISAM database, note the directory path on the Enterprise Server for the directory or directories in which the Vertex Quantum application databases are created. This information is needed for establishing Release 8.12 database connectivity.
212
GA.Rev8 1/7/2008
Adding Vertex Quantum Directory Information to the Microsoft Windows Server Path
To add the Vertex Quantum application directory information to the Microsoft Windows server path: 1. 2. 3. 4. 5. 6. 7. From the Microsoft Windows Enterprise Server, access the Control Panel. On Control Panel, click the System icon. In System, select the Advanced tab. On the Advanced tab, click the Environment Variables button. In the System Variables window, scroll down until the keyword Path appears in the Variable column. Click Edit to display the current path in the Variable Value field. Search the current path (as shown in the Value field) for the Vertex Quantum application directory. If the directory does not appear, you must add it to the path, as described in the following step. If the directory appears in the path, skip to step 9 in this task.
8.
Place the cursor in the Value field, and use the right arrow to scroll to the end of the field and enter this path: x:\vertexDirectoryPath\vertex\utils where x:\vertexDirectoryPath is the drive and path for the directory in which the Vertex Quantum applications are stored.
Note
You might need to include a semicolon to separate this entry from previous entries. 9. Click Set. The new value is saved. 10. After you finish setting the Environment Variables, repeat this task for User Variables, starting from step 5 in this task. 11. Click OK and reboot the server. The new path takes effect. Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 213
Configuring the Release 8.12 Database Connections for Vertex Quantum Tax Applications
To configure Release 8.12 database connections to use the Vertex Quantum applications: 1. In the Fast Path field, enter G731 to access Vertex Quantum Tax Processing. The Vertex Quantum Tax Processing panel appears. 2. Highlight and right-click the Database Connections (P7308) program. A context menu appears. 3. On the context menu, select Prompt for Values. The Processing Options dialog appears. 4. On Processing Options, click the Quantum tab and enter the following information: Option #1: Enter which Vertex Quantum applications are installed: Value [blank] 1 2 Action Install both Vertex Quantum tax applications. Install the Vertex Quantum for Sales and Use Tax application. Install the Vertex Quantum for Payroll Tax application.
Option #2: Enter location information for the databases: Value [blank] 1 2 Action Define databases for both Vertex Quantum tax applications in the same location. Define databases for the Vertex Quantum for Payroll Tax and Vertex Quantum for Sales and Use Tax applications in separate locations. Define databases for the Vertex Quantum for Payroll Tax and Vertex Quantum for Sales and Use Tax applications in separate locations, and the four databases for the Vertex Quantum for Sales and Use Tax application in separate locations.
Option #3: If processing option #2 is set to 1 or 2 (that is, if the Vertex databases are in separate locations), specify the GeoCode database location information: Value [blank] 1 Action Define the Vertex Quantum Payroll Tax and Sales and Use Tax applications to use the same GeoCode database. Define each of the Vertex applications to use a separate copy of the GeoCode database, and and that the two copies are expected in separate locations.
5.
Click OK. The Vertex Quantum Database Connection panel is displayed. The Database Connection panel contains one or more tabs that correspond to the database connections that must be defined. The displayed tabs are determined by the values you entered in the processing options, in step 4 of this task.
214
GA.Rev8 1/7/2008
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.
6.
On the Database Connection panel, select each tab and enter the following information: Data Source For ISAM, enter the directory path to the specified database. The location you enter should be the location on the server used for the database when the Vertex applications were installed, as previously described in this step. For ISAM, leave this field blank. For ISAM, leave this field blank. For ISAM, leave this field blank.
The changes do not take effect until you have logged off of your system and logged back on.
GA.Rev8 1/7/2008
215
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
216
GA.Rev8 1/7/2008
4. 5.
On Machine Search & Select, select data source OneWorld Planner - 812. On Work with Data Sources, click Add.
6.
On Data Source Revisions, add a data source with the following information:
GA.Rev8 1/7/2008
217
Data Source Use Data Source Name Data Source Type Object Owner ID Library Name Library List Name DLL Name Database Name
Displays the value DB. Displays the name of the machine on which this data source resides. Enter the value O (for Oracle). Enter the value SYS812. Leave this field blank. Leave this field blank. Enter the value JDBOCI80.DLL. Enter a value for the Oracle database connect string. The connect string should be to the same database as Data Source Name, which you previously specified on this tab.
Enter a name for your Enterprise Server. Select the value for your platform type.
On Work with Data Sources, highlight the new Data Source and, from the menu bar, select ODBC Data Source, Row, ODBC Data Source.
9.
On Create New Data Source, select System Data Source and click Next.
218
GA.Rev8 1/7/2008
10. On Create New Data Source, select a driver and click Next. Microsoft ODBC for Oracle is recommended. If you do not have this driver, consult your database administrator.
GA.Rev8 1/7/2008
219
220
GA.Rev8 1/7/2008
On Microsoft ODBC for Oracle Setup, by default the Data Source Name fields contains the previously selected data source name. 12. Enter the name of your Enterprise Server in the Server field. 13. Click OK. The data source is added to the ODBCDatasource.inf file, which is located in this directory: \JDEdwards\E812\client
GA.Rev8 1/7/2008
221
The Work with Payroll Cycle Workbench panel appears. 2. Specify pre-payroll information and submit the pre-payroll. For information about the Payroll Workbench and submitting pre-payroll, see Processing Pre-Payroll in the Release 8.12 Payroll Implementation Guide. 3. If no taxes are being calculated, there may be a setup or configuration problem. Verify the following to make sure setup is correct: UBE R07200 is being executed on the server where the Vertex Quantum for Payroll Tax APIs reside. Correct values are assigned to the Data Source, Server, User ID, and Password fields on the Database Connection panel, as specified in Configuring the Release 8.12 Database Connections for Vertex Quantum Tax Applications.
4.
For the Vertex Quantum for Sales and Use Tax interface: In the Fast Path field, enter P73GEO. The Retrieve GeoCode panel appears.
5.
On the Retrieve GeoCode panel, enter CO in the State field and DENVER in the City field, and click Find. The code 060310140 should appear in the grid.
6.
If nothing appears in the grid, a setup or configuration problem might exist. Verify the following to make sure setup is correct: These values are set in the Work with Quantum Constants Revision table, accessed by the Constants application (P7306) on menu G731:
Note
Changes to the Work with Quantum Constants Revision table do not take effect until you have logged off of your system and logged back on. Required Release 8.12 objects are mapped to the server where the Vertex Quantum for Sales and Use Tax APIs reside. Also ensure that correct values are assigned to the Data Source, Server, User ID, and Password fields on the Database Connection panel. Instructions for both procedures are specified in this guide in the section entitled Mapping Objects to the Enterprise Server.
222
GA.Rev8 1/7/2008
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.
GA.Rev8 1/7/2008
223
224
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
225
226
Note
The system is shipped with users JDE and RAPID in the F98OWSEC table, as well as a *PUBLIC record for roles. The Rapid user is associated with all of the Rapid Start roles, which allow users to add, change, and delete records for those programs on the task view for the role. If a program is not set up for a particular role, the system uses the default role *PUBLIC, which is set up to secure all objects (add, change, and delete functions are not allowed). By default, an application security setting allows a user with the *PUBLIC role to navigate to different applications forms and view application data; however, they are not allowed any add, change, or delete any data. By contrast, the JDE user is set up with the SYSADMIN role that allows all actions.
Warning
If you attempt to add a user with the P98OWSEC program before you add the system user through the P980001 program, the system may add an invalid record to the F98OWPU table. You might have to delete the invalid record from F98OWPU using the SQL Query tool. You must perform security setup signed on to JD Edwards EnterpriseOne from a deployed client. If you perform the steps signed on to the deployment server, you will not be updating the correct security tables for your JD Edwards EnterpriseOne system. This chapter contains the following tasks: Setting Up Signon Security Setting up Security Overrides for Package Build Enabling Server-Side Signon Security Enabling Client-Side Signon Security Setting Up JD Edwards EnterpriseOne Single Sign-on
GA.Rev8 1/7/2008
227
2.
On System User Revisions, complete the following fields: System User Data Source Password Password Verify JDE DEFAULT Enter a valid password for your installation. Enter the same password that you entered in the password field.
3. 4.
Click OK. Click Find to verify the new record was added.
228
GA.Rev8 1/7/2008
5.
On P98OWSEC [Work With User Security], complete the following field: User ID / Role JDE
6. 7.
GA.Rev8 1/7/2008
229
8.
On Security Revisions, complete the following fields: User ID Data Source System User Password User Status Allowed password attempts Password change frequency JDE DEFAULT JDE Enter a valid password for your installation. Ensure the Enabled radio button is selected. Enter a value applicable to your installation. Enter a value applicable to your installation.
9.
Click OK.
230
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
231
Caution
If you have changed the database password for the JDE user, the password you specify on Enterprise Server in jde.ini must be the new password.
232
GA.Rev8 1/7/2008
Warning
Using default settings may expose a potential security risk. Thus, it is highly recommended to overwrite the single sign-on settings using the single sign-on configuration applications discussed in Chapter 13, Setting Up EnterpriseOne Single Sign-On of the JD Edwards EnterpriseOne Tools 8.96 Security Administration Guide.
GA.Rev8 1/7/2008
233
234
Understanding Packages
Building and testing packages provides a method to create a package, to define and build a package, to deploy packages to both servers and workstations, and to troubleshoot the packages. These features use a step-by-step director process and include package assembly, package build, and package deployment. Package build is used to set up a workstation or server with Release 8.12 software. Examples scenarios include: Setting up a new workstation. Deploying custom solutions to all or to selected users. Creating a new pathcode for development. Deploying a fix. Changing the package from a full to a partial package on some workstations.
There are options to define three different package types, to build and define packages with custom solutions, and to distribute them through two different deployment options. These options are available to a single server, to a workstation or user, or to selected machines, groups, or individual users. These options can be delivered using just-in-time or scheduled installation methods. You must define, build, and deploy a custom package in order to include any modifications (changed or added business functions or applications) into a package for deployment to workstations (for example, DV812FA or DV812PA). The system administrator is required to build and test packages at the server level. An installer may complete the process for the workstations. These processes can take several hours, depending on the scope of your business. The procedures take place on the Deployment Server in the deployment environment as user JDE. Release 8.12 installation must be completed on the Enterprise Server before building and testing packages. The time required to build packages to the workstation varies depending on the database being used. The package build and assembly process includes many critical tasks that must be successfully completed to in-
GA.Rev8 1/7/2008
235
stall the packages correctly. This section includes a list of known issues associated with the package build, assembly, and deployment process and gives instructions for avoiding them. Before building a package, review these instructions to successfully complete this process. See Also Package Build in the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for information about how to build and deploy packages. JD Edwards EnterpriseOne Tools 8.96 Development Standards for Business Function Programming Guide for information on how to convert business functions to support Unicode text strings.
236
GA.Rev8 1/7/2008
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\include; C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include; LIB:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\lib; C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib; PATH:
C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools; C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\Bin; C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin;
Note
Refer to Accessing Minimum Technical Requirements for details on which compiler version you should use with various applications and tools releases of JD Edwards EnterpriseOne. 8. You must reboot the computer in order for path changes to take effect.
GA.Rev8 1/7/2008
237
238
GA.Rev8 1/7/2008
If you do not have enough free space to accommodate these tables, you must increase the size of your tablespaces or drop the metadata specifications tables for old packages no longer in use.
Click the Search icon next to the Search field. The F9631 table appears in the Search results window.
240
GA.Rev8 1/7/2008
i.
Select the F9631 table and click the left arrow next to the Search pane. Object Management Workbench copies the table icon to the Object folder.
j.
Select the F9631 table in the Object folder and click the Design button next to the Project pane.
Note
You must add yourself to the project as a Developer to access the Design function. The system displays the Object Librarian Table Design screen. k. Select the Table Operations tab, and then click the Copy Table icon. The Copy Table form appears. l. Enter Planner - 812 in the Source data source field.
m. Enter System - 812 in the Destination data source field. n. Click OK to copy the table.
GA.Rev8 1/7/2008
241
Adding a System User for the Central Objects Data Source Owner
To add a system user for the Central Objects data source owner: 1. 2. 3. In P98OWSEC, select the form exit Add System User. On Work with System Users, enter the appropriate data source owner (for example, DV812, PY812 or PD812) in the System User field and select Find. If no values are returned, add the data source owner as a system user by selecting Add and completing the fields on the System User Revisions form: 4. System User Data Source Password Password Verify
Click OK and then Cancel and Close to return to the Work with User Security form.
242
GA.Rev8 1/7/2008
User Tips
Check these items as you build and assemble your packages: When naming your packages, do not use these names: CLIENT SERVER
Verify the assemble and build processes completed. After entering the package information on both the Assembly and Build forms, click the End icon to save the information.
Verify setting on the package definition screen. When selecting servers on the Build Definition form, ensure that a check mark appears next to each server selected. If no check mark appears, highlight the server in the grid and click Select.
Recompress the parent packages. After building an update package that updates the parent package, you must recompress the parent package. This step does not occur automatically.
Verify the location of server packages. When building an update server package, the specified parent package must be stored under the package directory on the server. If the parent package is not under the package directory, the update package does not build.
GA.Rev8 1/7/2008
243
Deployment Tips
Check these items as you deploy your packages: Deploy a package to a CD burner. When deploying the package to a CD burner, the target machine must be created and the CD burner must be attached to this new location. Approve the package. After building a package, change the Deployment Status in the [ATTRIBUTES] section of the package.inf file from No Status Defined to Approved. Without this setting, the package is not visible in the package list when trying to install Release 8.12 from a client workstation. To approve the package: 1. 2. 3. 4. 5. Open the Package Deployment application. Select the Package option. Enter the package name and click Find. Select the package. Click Activate/Deactivate under Row. The package is set to active. Copy the package.inf files. If there are two or more package.inf files that have the same package name listed in the Attributes section, that package will not show up on the install screen. It is possible that a duplicate package might have been created if you copied a package.inf file to back it up. To set the attributes of the package.inf file to that is visible on the install screen: 1. 2. 3. Open the package.inf file for the package that is not showing up on the install screen. Check the Attributes section in the package.inf files of the other package and verify that the package name listed in PackageName= is not duplicated in another package.inf file. If the package name is the same as listed in another package.inf file, change it.
Configure the client package.inf file If you schedule a package to be deployed to a client machine and the client is not prompted for the package installation at login, conflict with a registry setting might exist. Complete the following steps to eliminate this problem: To configure the client package.inf file: 1. 2. Open the client package.inf file. Verify that the value for AppBuildDate is a few minutes or hours earlier than the AppBuildDate in the following registry key: HKEY_LOCAL_MACHINE/Software/jdedwards/OneWorld/install.ini/E812/
244
GA.Rev8 1/7/2008
AppBuildDate 3. If the registry also contains a key named FoundationBuildDate, you should verify that the value is a few minutes or hours earlier than the FoundationBuildDate in the following registry key: HKEY_LOCAL_MACHINE/Software/jdedwards/OneWorld/install.ini/E812/ FoundationBuildDate 4. 5. 6. Verify that the DeploymentStatus setting in the package.inf is set to Approved. If the status is not set to Approved, set it to Approved and save the file. Install the package again.
GA.Rev8 1/7/2008
245
Caution
When building the client package with translated processing option text, run the build using Microsoft Windows with the system locale set to the appropriate language. If the system locale on the operating system does not match the installed language, the translated text in processing options (POTEXT) will be corrupted. Building server packages that include languages other than English requires that the LocalCodeSet value of the Release 8.12 client matches the LocalCodeSet value of the JDE.INI on the Enterprise Server. If the LocalCodeSet value on the local client differs from the one specified on the Enterprise Server, the server package build fails and errors are logged in the JDE.LOG on the Enterprise Server.
Caution
To transfer translated objects to a server, complete the server package installation procedures. Define each object you have modified for languages. Therefore, track the objects you changed to include them in a package.
Note
To move all objects, call Global Customer Support for assistance. See Also
246
GA.Rev8 1/7/2008
JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for more information about transferring objects to the server.
GA.Rev8 1/7/2008
247
248
To revalidate the Deployment Server: 1. 2. 3. 4. 5. 6. 7. 8. To reset the licenses on the Deployment Server, on either a Windows client or the Deployment Server (either one can run the SPC generator program), sign on to JD Edwards EnterpriseOne. Run the Reset EnterpriseOne Security program (R98SRV). On Reset Oracle Security, click Reset Server Security. From Customer Connection, download the update called "SPC", which is associated with SAR # 7549901. On either your Deployment Server or Workstation, run the SPC generator program called SPCSelfService.exe. Select the Release Level and enter your JD Edwards EnterpriseOne Serial Number. If the Release Level is 3 or 4, select the checkbox next to "ALL" in the Licensed Suites section. Enter any number between 1 and 99999 for the number of licenses. Because a number above 5000 will cause JD Edwards EnterpriseOne to run slowly in some instances, it is best to limit the number of licenses to 5000. 9. Click OK.
GA.Rev8 1/7/2008
249
10. Note the SPC codes. 11. In JD Edwards EnterpriseOne, on Reset Security, enter the Number of Licenses, Expiration Date (1/1/2899), and SPC codes that were displayed by the SPC generator program. 12. Click OK. The JD Edwards EnterpriseOne are reset. 13. Exit the R98SRV application. 14. Close the SPCSelfService.exe program.
Revalidating Workstations
You might need to revalidate workstations for either of the following reasons: The expiration date has passed. You added modules to JD Edwards EnterpriseOne.
To revalidate a workstation: 1. 2. 3. 4. 5. Log on to the workstation with the appropriate user ID and password. Select any of the environments available to the workstation user. From the Advanced Operations menu (GH9611), select Oracle Licensing Security. On Reset Oracle Security, click Reset Client Security. On Oracle Security Setup, from the Form menu, select Get Authorization. The authorization code appears in the Authorization Code field. 6. Click OK to reset the workstation.
250
GA.Rev8 1/7/2008
Registry
This procedure can be used only by the administrator of the domain. This procedure grants access to HKEY_LOCAL_MACHINE\Software\JDEdwards. To grant nonprivileged access to the Microsoft Windows registry: 1. Run regedt32.exe as follows: a. b. c. 2. 3. 4. 5. Click the Microsoft Windows Start button, and click Run. In the Open field, enter regedt32. Click OK.
Expand the node HKEY_LOCAL_MACHINE on the Local Machine node. Expand the Software node. On the Menu bar, click Edit and then Add Key. In the Key Name field, enter JDEdwards (case-sensitive as shown). Leave the Class field blank.
6. 7. 8. 9.
Click OK. On the Menu bar, click Security, and then select Permissions. On the Registry Key Permissions box, click Add. On the Add Users and Groups box, double-click the user to be added.
10. Click the pull-down menu in the Type of Access field and select Full Control. 11. On Existing Subkeys, select Replace Permissions. 12. Click OK. Permission to access the registry is now granted to the user.
252
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
253
Are the printer drivers for this printer installed? Is this printer configured as the default printer? Have the read-only attributes been turned off for all directories and files?
JDE.INI Issues Is your JDE.INI located in the correct directory? Is your JDE.INI located in the correct IIS Directory? Does your JDE.INI have the correct permissions? Are these JDE.INI parameters set properly? [Network Queue Settings] Default Printer OUTQ=your_printer [UBE]
Yes/No
Note
If you use PostScript, is the correct filter set up in the [UBE] section? [DB System Settings]
Note
You should verify all parameters in the [DB System Settings] section, but especially these: Default Env=your_default_environment Default Pathcode=your_default_path_code Server=database_server_name [JDENET] serviceNameListen=port_number serviceNameConnect=port number [INSTALL] E812=valid_path_for_your_install
Yes/No
254
GA.Rev8 1/7/2008
If not, does an entry exist in the host file for your host? Can you ping your host by name? Can you ping from your host to the workstation by name? If you run Netmon, can you see the host and the workstations? Do the workstations and server agree on the IP address of the server?
Other Issues Were your server map tables F98611 and F986101 edited properly? Run the Verify OCM application and verify: Do only host databases exist? No entries for batch applications exist. Are JD Edwards EnterpriseOne tables accessible to the host? Can you query the F0902 table? Does the PORTTEST program run without error for each valid path code? Does the user name match that of a valid Release 8.12 account? Remember that the user name is case sensitive. Is the password valid for the given Release 8.12 account? Does the environment name match a valid Release 8.12 environment? Remember that the environment name is case sensitive. Does JDENET start and stop properly? After rebooting, do the services start and stop properly? Can you kill the runaway services with Visual C++ debug? If your printer is on a network, are your services running under a network (not a system) account? Are your services running in the administrator group?
Yes/No
If you answered no to any of these questions, your batch application might not run. If you answered yes to all the Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 255
questions, submit a batch application now. If your batch application does not run correctly, turn on error logging and resubmit the batch. This log helps Global Customer Support diagnose the exact problem.
256
GA.Rev8 1/7/2008
4. 5. 6.
Change the OCXPATH variable to the correct path for your Deployment Server. Save the file and exit Notepad. Run the regjdeocx.bat to register the OCX files.
Orphan Users
When you run the orphan user script, you must execute the script first from the master database, and then from each delivered database which could include: JDE_CRP JDE_DEVELOPMENT DV812 PS812 PD812 JDE_PRIST812 JDE_PRODUCTION PY812
To troubleshoot database connection errors that are reported by JD Edwards EnterpriseOne: 1. Access Microsoft SQL Query Analyzer and login to the JD Edwards EnterpriseOne database as the JDE user. If there are database connections problems, an error message appears. The error is caused by the introduction of a database whose logins do not match those defined within the SQL Server instance as they are defined by a SQL Server internal number or identifier. You must run the following provided script to correct the condition. 2. From the Microsoft SQL Query Analyzer, click File, Open and navigate to the folder contain the orphan user script. Typically the file is found in this location: c:\JDEdwards\812\mssql 3. Select this script: orphan user with cursor.sql 4. Click the Open button.
GA.Rev8 1/7/2008
257
5. 6.
258
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
259
Note
Installation Planner Considerations. Depending on which tables you want to replicate, you are prompted for different data source information. For example, if you choose to replicate the control tables, you are asked to define the control tables data source.
Note
Data Source Considerations. JD Edwards EnterpriseOne provides configured data sources. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration. Only data sources that are referenced in the replication forms appear when you create a remote plan.
260
GA.Rev8 1/7/2008
4.
On Work with Installation Plans, click Add. The Installation Planner form appears.
GA.Rev8 1/7/2008
261
1.
On Installation Planner, complete these fields: Name Description Status Install Type To Release Enter the name of your remote plan. Enter the description of your remote plan. Select 10 as the status of your remote plan. Select Install. Verify that the release number is E812.
2.
Click OK.
262
GA.Rev8 1/7/2008
1.
On Location Revisions, complete these fields: Location Description Location Code Enter the location to which this plan applies. The location could be a city, company headquarters, or a division of a company. Enter a description of the location name. For a remote location, enter a 3-character alphanumeric identification code. This 3-character code is used as a prefix for the environments of the remote location, and a suffix is attached for replicated data sources. For example, you might use DAL if the location were Dallas, Texas. In that case, the prototype environment would be named DALPY812, and the business data data source would be named Business Data - CRPDAL. Enter the parent location to which this remote location is attached.
GA.Rev8 1/7/2008
263
2.
On Deployment Server Revisions, complete these fields: Machine Usage Machine Name Description Displays the default value of 15 to indicate that this is a Deployment Server. Enter the name of your Deployment Server. Enter a description of the machine name. This name includes the location with which this Deployment Server is associated, and whether or not it is the primary server. Enter the Release 8.12 release number that you are installing, or use the visual assist button to choose one from the list. For example, E812 is the current re-
Release
264
GA.Rev8 1/7/2008
lease. Displays the default value of 50 to indicate that the server type is an Intel NT. Displays the default location chosen for this plan. Enter the user to whom email is sent when a package is deployed. The default for primary user is JDE.
3.
On the Deployment tab, complete these fields: Primary Deployment Server Server Share Path Enter the hierarchy of the servers. Type 0 (zero) if a primary Deployment Server for the location exists and this is a secondary server. Type 1 if this is the primary Deployment Server for the location. Enter the server share path where you installed Release 8.12 on your Deployment Server. Make sure that this path is specific to your version of the release. For example, for Release 8.12, the path ends with \E812.
4.
Click OK.
Tip
If you enter invalid information into a tab field, a stop sign symbol appears next to the tab name, such as Deployment Server. For more information about the error, click the stop sign icon in the bottom right-hand corner of the form.
GA.Rev8 1/7/2008
265
Note
Add an Enterprise Server if you are using replication in Release 8.12. To skip the Enterprise Server setup and continue with remote Installation Planner, click Skip. Continue with Entering HTML Web Server Information.
266
GA.Rev8 1/7/2008
1.
On Enterprise Server Revisions, complete or verify these fields: Machine Usage Machine Name Displays the default value 20 to indicate that this is an Enterprise Server. Enter the name of your primary Enterprise Server. The name is case sensitive.
Caution
When using cluster software, use the cluster name, not the machine name. Use the cluster name as the server name when installing Release 8.12. One copy of Release 8.12 will run and be shared by both nodes. Enter a description of the machine. Enter the release number to which this plan applies, or use the visual assist button to choose one from the list, such as E812. Click the visual assist button and choose the type of Enterprise Server that you are adding to the plan, such as Intel NT . Enter the default location chosen for this plan. Enter the user to whom email is sent when a package is deployed. The default for primary user is JDE.
2.
On the Enterprise tab, complete these fields: Port Number Displays the default value for this field, which is supplied the JDE.INI. Change the port number for this Enterprise Server to a unique value, for example, 6014. Displays the system-supplied default value when you enter the host type. Enter the type of database that you want to use for data sources on the Enterprise Server. Value is O for Oracle .
GA.Rev8 1/7/2008
267
Displays the system-supplied default value when you enter the host type. Enter the installation directory path where you want to install Release 8.12 on your Enterprise Server. Make sure that this path is specific to your version of the release. For example, for release 8.12, this path ends with \E812. You may need to add the drive x: to the path. Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. The system provides a default value for this field, but you can change it.
3.
Click OK. A message box appears to enable you to specify whether you want to enter custom data sources or take the default data sources. Proceed to Entering Shared Data Source Information.
Note
The following screen that prompts you to enter the Oracle connect string is only displayed if you choose Take Defaults. That is, if you choose to define your own data source, you will be prompted to enter the oracle connect string on a different screen.
1. 2.
On Oracle Connect String, enter the connect string for the Enterprise Server, and then click OK. Skip to Adding Another Enterprise Server .
GA.Rev8 1/7/2008
269
1.
On Data Source Revisions, verify your Server Map data source information.
Tip
Data Source Considerations. JD Edwards EnterpriseOne supplies configured data sources. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration. 2. Click OK.
270
GA.Rev8 1/7/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. To enter HTML Web Server information:
1.
On HTML Application Server, click OK to define a new HTML Server, or click Select to choose from a list of existing HTML Servers.
GA.Rev8 1/7/2008
271
If you choose Select, you are presented with the Machine Search table, from which you can make your selection.
272
GA.Rev8 1/7/2008
2. 3.
On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server. On HTML Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Location Primary User The default value of 30 indicates that this is a HTML Web Server. Enter the name of your HTML Web Server. The name is case sensitive and must not exceed 10 characters. Enter a description of the HTML Web Server machine. Enter E812 to indicate the release number that you are installing. The default value of 50 specifies the server type as Intel NT. Select the correct server type. The location chosen for this plan appears in this field by default. The user to whom an email is sent when a package is deployed. The default for primary user is listed in the JDE.INI.
4.
On the HTML tab, complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). This is the protocol used by the HTML Web Server. Valid values are http or https. This is the Domain Name System (DNS) host name of the HTML Web Server. For example: www.oracle.com. This is the port number the HTML Web Server is listening to.
HTTP Port
GA.Rev8 1/7/2008
273
For HTTP, the typical port number is 80. For HTTPS, the typical port number is 443. However, you can choose to implement a HTML Web Server using a different port number. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne. For JD Edwards EnterpriseOne Release 8.12, the value is 6014. Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. Redirector The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system. Explicit The user can specify an explicit servlet name in this field. In this Servlet case, the redirector functionality cannot be used. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need. The Portal servlet is: /jdedwards/servlet/com.jdedwards.portal.PortalBuilderServlet
Default Login
The HTML servlet is: /jdedwards/servlet/com.jdedwards.runtime.virtual.VCServlet Installation Path Enter the installation directory path to which you are installing Release 8.12 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running. For Release 8.12 on Oracle Applications Servers, the path ends with E1HTMLServer. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator. 5. Click OK.
274
GA.Rev8 1/7/2008
6.
To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.
GA.Rev8 1/7/2008
275
1.
On Data Server, select one of these options: OK If your database resides on a separate server, click OK to continue entering unique Data Server information. Select Click this button to select an existing Data Server. Skip Click this button if you do not want to define a Data Server . Continue the Installation Planner with the environment selection in step 6.
276
GA.Rev8 1/7/2008
2.
On Data Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Displays the default value of 25 to indicate that this is a Data Server. Enter the name of your Data Server. The name must not exceed 10 characters. Enter a description of the machine. Enter the Release 8.12 release number you are installing, for example, E812. Select the type of Data Server that you are adding to the plan. Valid values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client - NT 90 Client - Win NT Displays the location chosen for this plan appears in this field by default. Enter the user to whom an email is sent once a package is deployed. The default for primary user is JDE.
3.
On the Data tab, complete these field: Data Source Type Select the type of data source. Value is O for Oracle .
4.
Click OK.
GA.Rev8 1/7/2008
277
5.
A message box appears to enable you to add another Data Server. Click Yes to add another Data Server. Repeat the procedure in step 2 of this task. Click No to continue with Installation Planner setup.
6.
On Data Source, you are prompted to enter shared data source information for the specific environment that you previously selected to install. Click OK to continue entering unique shared data source information, or click Take Defaults to select the default data for the shared data sources.
7.
On Location, select Yes to add another location or No to continue with Installation Planner.
278
GA.Rev8 1/7/2008
1. 2.
On Data Source Revisions, verify the accuracy of the Data Dictionary data source. Click OK.
GA.Rev8 1/7/2008
279
1. 2.
On Data Source Revisions, verify the accuracy of the Object Librarian data source. Click OK.
280
GA.Rev8 1/7/2008
1. 2.
On Data Source Revisions, verify the accuracy of the settings for the System data source. Click OK. The Environment Selection screen appears.
See Also For more information about System data source fields or fields for other data sources mentioned in this process, see Understanding Data Source Charts.
Setting Up Environments
By default, Release 8.12 configures your system using values for typical environments. Depending on the options chosen when you set up your plan, Release 8.12 displays one or more of the following parameters, which you can customize in the following tasks: Environments Data load options Languages
Environments
You can customize any of these parameters by clearing the default option on the Environment Selection form. As you move through the plan, the Installation Planner displays a customization form for each parameter that you turn off. Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008 281
1.
On Environment Selection, clear the options for those parameters that you want to customize.
Note
The parameters that display might vary depending on which options you selected at the beginning of the planning process. 2. Click OK.
Note
If you checked the default option for all parameters, skip to the next task. Use the following tasks to customize each of the parameters listed above. Installation Planner displays customization forms only for those parameters for which were turned off the default options. Skip the tasks for those parameters that were left turned on. 3. Continue with the following relevant tasks: Selecting an Environment
282
GA.Rev8 1/7/2008
3. 4.
Select share, or create a pathcode and click Next. Enter pathcode information on the screen and click Next.
Selecting an Environment
The Select Environment form appears. Environments prefixed with J are required for the HTML Web Server. To select an environment:
On Select Environments, double-click the environment that you want to define. To set up multiple environments, choose and define them one at a time. This screen appears after the following tasks are completed.
GA.Rev8 1/7/2008
283
1.
On Control/System Replication, select the Replication Setup tab and select the following options to replicate information to remote locations: Replicate Control Tables Select this option to configure the control tables data source for replication. Clear the option if you do not want to replicate the control tables. Select this option to configure the constant tables for replication. Clear the option if you do not want to replicate the constant tables. Select this option to configure the master tables for replication. Clear the option if you do not want to replicate the master tables.
2.
284
GA.Rev8 1/7/2008
3.
On the Data Load tab, choose from the following options to copy selected tables to the remote locations: Load Control Tables Select this option to copy the control tables automatically from the base to the remote locations. Clear the option if you do not want to copy the control tables automatically. Select this option to copy the constant tables automatically from the base to the remote locations. Clear the option if you do not want to copy the constant tables automatically. Select this option to copy the master tables automatically from the base to the remote locations. Clear the option if you do not want to copy the master tables automatically.
Note
To edit or change the versions of the R98403 program that copy the control tables, constant tables, and master tables, click the Edit or Search buttons next to their respective versions.
Note
If you have defined multiple locations, the system will prompt you to complete sets of the Replication Setup and Data Load screens for each location. 4. Click OK.
GA.Rev8 1/7/2008
285
286
GA.Rev8 1/7/2008
1.
On Data Source Revisions, set up or verify the data source information for your business data.
Note
Be sure that this data source points to either the existing production data source you want to upgrade or a copy of it. 2. Click OK The Select Environments form appears so that you can define another environment, if necessary.
GA.Rev8 1/7/2008
287
1. 2.
On Data Source Revisions, verify your Control Tables data source. Click OK.
288
GA.Rev8 1/7/2008
1. 2. 3.
On Select Environments, choose the next environment that you want to define. Repeat all tasks in Replicating Information to Remote Locations and Setting Up Data Sources for Environment. After defining all of your environments, click Close. The Remote Location Packages window appears.
You can push delivered full packages to remote locations when you run the Location Workbench. 4. Select one of the following options:
GA.Rev8 1/7/2008
289
Click Yes to view a list of packages to push to the remote location. Click Take Defaults to push all available packages to the remote location. Continue with Concluding the Remote Installation Plan Setup.
Click No if you do not want to push packages to the remote location. Continue with Concluding the Remote Installation Plan Setup.
If you click Yes, the Select Remote Location Packages form appears.
5.
On Select Remote Location Packages, choose a package from the list and click the Deselect icon in the Row menu.
Note
Click the corresponding icon in the Row menu to select or cancel the selection of a package. 6. Click Select to push the chosen packages.
290
GA.Rev8 1/7/2008
Repeat all tasks for adding a location, starting with Entering Plan Location Information. To conclude remote Installation Planner setup, click No. Continue with Finalizing the Installation Plan below.
If the processing option default was chosen, Planner Validation Report automatically prompts you to run this report. If the processing option default was not chosen, on the tree view of your plan, click Validate to initiate the Planner Validation Report.
GA.Rev8 1/7/2008
291
For more information about Installation Planner Validation Report (R9840B), refer to Working with Reports. 4. 5. On Work With Installation Plans, click Expand to review the plan that you created. Run Installation Workbench for this installation plan. For more information about Installation Workbench, refer to Working With Installation Workbench.
292
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
293
294
296
GA.Rev8 1/7/2008
5.
GA.Rev8 1/7/2008
297
1.
On Installation Planner, complete the following fields: Name Description Status To Release Enter the name of your installation plan. Enter the description of your installation plan. Select 10 as the status of your installation plan. Verify that the release number is E812.
2.
298
GA.Rev8 1/7/2008
1.
GA.Rev8 1/7/2008
299
2.
300
GA.Rev8 1/7/2008
1. 2.
On Server Add, check the types of servers that you want to add to your configuration. Click OK. A Server Revisions form appears in the order listed on the Server Add form for each type of server that you chose.
3.
GA.Rev8 1/7/2008
301
1.
On Deployment Server Revisions, complete the following fields: Machine Name Description Release Location Primary User Enter the name of your additional Deployment Server. Enter a description of the machine. Enter E812. Displays the system-provided default value chosen for this plan. This identifies the user to whom email is sent when a package is deployed. The default for primary user is JDE.
2.
On the Deployment tab, verify or complete the following fields: Primary Deployment Server Server Share Path This field indicates the hierarchy of the servers. The default value for a secondary Deployment Server is 0. Enter the server share path where you installed Release 8.12 on your Deployment Server. Verify that this path matches your version of the release; for example, for Release 8.12, the server share path is \E812.
3.
Click OK.
302
GA.Rev8 1/7/2008
Tip
If you enter invalid information into a tab field, a stop sign icon appears next to the tab name, such as Deployment Server. For more information about the error, click on the stop sign icon in the bottom right-hand corner of the form. 4. You are prompted to add another Deployment Server. To add another Deployment Server, click Yes. Repeat Entering Deployment Server Information . To continue with the additional server plan, click No. Continue with the relevant sections that follow.
GA.Rev8 1/7/2008
303
1.
On Enterprise Server Revisions, complete or verify the following fields: Machine Usage Machine Name Displays the default value of 20 to indicate that this is an Enterprise Server. Enter the name of your primary Enterprise Server. The name is casesensitive.
Caution
When using cluster software, use the cluster name, not the machine name. Use the cluster name as the server name when installing Release 8.12. One copy of Release 8.12 will run and be shared by both nodes. Enter a description of the machine. Enter the release number to which this plan applies, or use the visual assist
Description Release
304
GA.Rev8 1/7/2008
button to choose one from the list, such as E812. Click the visual assist button and choose the type of Enterprise Server that you are adding to the plan, such as Intel NT . Enter the default location chosen for this plan. Enter the user to whom email is sent when a package is deployed. The default for primary user is JDE.
2.
On the Enterprise tab, complete these fields: Port Number Displays the default value for this field, which is supplied the JDE.INI. Change the port number for this Enterprise Server to a unique value, for example, 6014. Displays the system-supplied default value when you enter the host type. Enter the type of database that you want to use for data sources on the Enterprise Server. Value is O for Oracle. Displays the system-supplied default value when you enter the host type. Enter the installation directory path where you want to install Release 8.12 on your Enterprise Server. Make sure that this path is specific to your version of the release. For example, for release 8.12, this path ends with \E812. You may need to add the drive x: to the path. Using the visual assist button, choose the name of the Deployment Server to which this Enterprise Server is attached. The system provides a default value for this field, but you can change it.
Logical Machine Name Database Type Server Map Data Source Installation Path
3.
Click OK. A message box appears prompting you to enter custom data sources or take the default data sources. Proceed to Entering Shared Data Source Information.
GA.Rev8 1/7/2008
305
Note
The following screen that prompts you to enter the Oracle connect string is only displayed if you choose Take Defaults. That is, if you choose to define your own data source, you will be prompted to enter the oracle connect string on a different screen.
306
GA.Rev8 1/7/2008
1. 2.
On Oracle Connect String, enter the connect string for the Enterprise Server, and then click OK. Skip to Adding another Enterprise Server .
GA.Rev8 1/7/2008
307
1.
On Data Source Revisions, verify your Server Map data source information.
Tip
Default data sources are configured as completely as possible. However, when you run Installation Planner, you might need to modify some data source information to reflect your system-specific configuration. 2. Click OK.
308
GA.Rev8 1/7/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. To enter HTML Web Server information:
1.
On HTML Application Server, click OK to define a new HTML Server, or click Select to choose from a list of existing HTML Servers.
GA.Rev8 1/7/2008
309
If you choose Select, you are presented with the Machine Search table, from which you can make your selection.
310
GA.Rev8 1/7/2008
2. 3.
On the HTML Application Server dialog, click OK to continue entering HTML Web Server information, or click Select to select an existing HTML Web Server. On HTML Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Location Primary User The default value of 30 indicates that this is a HTML Web Server. Enter the name of your HTML Web Server. The name is case sensitive and must not exceed 10 characters. Enter a description of the HTML Web Server machine. Enter E812 to indicate the release number that you are installing. The default value of 50 specifies the server type as Intel NT. Select the correct server type. The location chosen for this plan appears in this field by default. The user to whom an email is sent when a package is deployed. The default for primary user is listed in the JDE.INI.
4.
On the HTML tab, complete these fields: Primary HTML Server When the system code generates an email message with a web shortcut pointing to a form, the web shortcut generated points to the "Primary" HTML Web Server. Only one of all the HTML Web Servers defined in installation planner can be defined as primary ("1"). This is the protocol used by the HTML Web Server. Valid values are http or https. This is the Domain Name System (DNS) host name of the HTML Web Server. For example: www.oracle.com. This is the port number the HTML Web Server is listening to.
HTTP Port
GA.Rev8 1/7/2008
311
For HTTP, the typical port number is 80. For HTTPS, the typical port number is 443. However, you can choose to implement a HTML Web Server using a different port number. This is the port on which the JDENET communications protocol communicates with the JD Edwards EnterpriseOne Enterprise Server. The value is dependent on the release of JD Edwards EnterpriseOne. For JD Edwards EnterpriseOne Release 8.12, the value is 6014. Defines how shortcuts to a web form are generated by the system code. Values are either a reserved value or an explicit servlet name. Reserved values are: Standard The URL generated will point to a servlet on the Primary HTML Web Server. Redirector The URL generated will point to redirector in the Primary HTML Web Server, and redirector will point to a servlet on another HTML Web Server for load balancing. The servlet name to use is generated by the system. Explicit The user can specify an explicit servlet name in this field. In this Servlet case, the redirector functionality cannot be used. The URL generName ated will point to the specified servlet in the Primary HTML Web Server. Usage of Explicit servlet name is for backward compatibility only. You should not use it unless you have a direct need. The Portal servlet is: /jdedwards/servlet/com.jdedwards.portal.PortalBuilderServlet
Default Login
The HTML servlet is: /jdedwards/servlet/com.jdedwards.runtime.virtual.VCServlet Installation Path Enter the installation directory path to which you are installing Release 8.12 on your HTML Web Server. Make sure this is specific to your version of the release, and also the platform and application server on which your HTML Web Server is running. For Release 8.12 on Oracle Applications Servers, the path ends with E1HTMLServer. For example: c:\Program Files\JDEdwards\E1HTMLServer For default paths, refer to the applicable platform- and application server-dependent version of the JD Edwards EnterpriseOne HTML Web Server Installation Guide. Otherwise, you must obtain this value from the HTML Web Server machine itself, or its administrator. 5. Click OK.
312
GA.Rev8 1/7/2008
6.
To add another HTML Web Server, click Yes and repeat steps 1 through 4 to define another HTML Web Server.
GA.Rev8 1/7/2008
313
1.
On Data Server, choose one of these options: OK If your database resides on a separate server, choose click OK to continue entering unique Data Server information. Select Click this option to select an existing Data Server. Skip Click this option if you do not want to define a Data Server. Continue with the Planner with the environment selection in step 6 of this task.
314
GA.Rev8 1/7/2008
2.
On Data Server Revisions, complete these fields: Machine Usage Machine Name Description Release Host Type Displays the default value of 25 to indicate that this is a Data Server. Enter the name of your Data Server. The name must not exceed 10 characters. Enter a description of the machine. Enter the Release 8.12 release number you are installing, for example, E812. Select the type of Data Server that you are adding to the plan. Valid values are: 10 iSeries 20 HP9000 25 Sun Solaris 30 RS/6000 35 Linux 50 Microsoft Windows (Intel) 80 Client - NT 90 Client - Win NT Displays the location chosen for this plan appears in this field by default. Enter the user to whom an email is sent once a package is deployed. The default for primary user is JDE.
3.
On the Data tab, complete the following field: Data Source Type Select the type of data source. Value is O for Oracle .
4.
Click OK.
GA.Rev8 1/7/2008
315
5.
A message box appears to enable you to add another Data Server. Click Yes to add another Data Server. Repeat the procedure in step 2 of this task. Click No to continue with Installation Planner setup.
6.
On Data Source, you are prompted to enter shared data source information for the specific environment that you previously selected to install. Click OK to continue entering unique shared data source information, or click Take Defaults to select the default data for the shared data sources.
7.
On Location, select Yes to add another location or No to continue with Installation Planner.
316
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
317
1. 2.
On Data Source Revisions, verify the accuracy of the Data Dictionary data source. Click OK.
318
GA.Rev8 1/7/2008
1. 2.
On Data Source Revisions, verify the accuracy of the Object Librarian data source. Click OK.
GA.Rev8 1/7/2008
319
1. 2.
On Data Source Revisions, verify the accuracy of the settings for the System data source. Click OK. The Environment Selection screen appears.
See Also For more information about System data source fields or fields for other data sources mentioned in this process, refer to Understanding Data Source Charts.
320
GA.Rev8 1/7/2008
Setting Up Environments
By default, Release 8.12 configures your system using values for typical environments. Depending on the options chosen when you set up your plan, Release 8.12 displays one or more of the following parameters, which you can customize in these tasks: Environments Data load options Languages
You can customize any of these parameters by turning off the default option on the Environment Selection form. As you move through the plan, Release 8.12 displays a customization form for each parameter that you turn off.
1.
On Environment Selection, clear the options for those parameters that you want to customize.
Note
The parameters that are available vary depending on the options that you selected at the beginning of the planning process. 2. Click OK.
Note
If you selected the default option for all parameters, skip to Setting Up Environment Data Sources . Use the following tasks to customize each of the parameters listed above. Release 8.12 displays customiza-
GA.Rev8 1/7/2008
321
tion forms only for those parameters for which were cleared of the default options. Skip the tasks for those parameters that were selected. 3. Continue with the following relevant tasks: Selecting an Environment Specifying Environment Data Load Parameters Selecting Languages
322
GA.Rev8 1/7/2008
Selecting an Environment
The Select Environment form appears. Environments prefixed with J are required for the HTML Web Server. To select an environment:
On Select Environments, double-click the environment that you want to define. To set up multiple environments, choose and define them one at a time. This screen appears after the following tasks are completed.
GA.Rev8 1/7/2008
323
Note
The data load radio buttons on this form are no longer applicable as of JD Edwards EnterpriseOne Release 8.12 because data is automatically loaded by the Platform Pack Installer. For additional details, refer to Loading Data (Demo Data and Production Data).
324
GA.Rev8 1/7/2008
Selecting Languages
To select languages:
1. 2. 3. 4.
On Language Selection, to set up a language for the selected environment, choose the appropriate language. From the Row menu, click Select. Repeat the above steps until all your languages have been selected. Click OK.
GA.Rev8 1/7/2008
325
1. 2.
On Data Source Revisions, verify the data source for your Business Data. From the Form menu, click Advanced.
326
GA.Rev8 1/7/2008
3.
Click OK.
GA.Rev8 1/7/2008
327
1. 2.
On Data Source Revisions, verify the information for your Central Objects data source. Click OK.
Caution
The Central Objects data source must be Unicode. Select Advanced from the Form menu to verify Unicode is checked. Also ensure that LOB is selected.
328
GA.Rev8 1/7/2008
Note
The Central Objects data sources are specific to the pathcode.
GA.Rev8 1/7/2008
329
1.
On Data Source Revisions, verify the accuracy of the Control Tables data source. Data Source Name Server Name Object Owner ID Verify the name of the data source. Verify the name of the Enterprise Server. Enter the name of the owner of this object
Note
The Control Tables data sources are specific to the environment and pathcode. 2. Click OK.
330
GA.Rev8 1/7/2008
1. 2.
On Data Source Revisions, verify the accuracy of the Versions data source. Click OK.
Note
Versions data sources are specific to the pathcode, and the Unicode flag on the Advanced Form must be checked.
GA.Rev8 1/7/2008
331
To finalize the installation plan: 1. Click OK to exit the concluding message box and initiate the Planner Validation Report. If you chose the default processing option, Planner Validation Report automatically prompts you to run this report. If you did not choose the default processing option, on the tree view of your plan, click Validate to initiate the Planner Validation Report.
332
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
333
334
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
335
336
GA.Rev8 1/7/2008
337
It is important that you complete all tasks in this chapter to achieve a successful language installation.
338
GA.Rev8 1/7/2008
2.
On JD Edwards Installation Manager, click the link for the language that you want to install. In this example, the language CD is for French.
GA.Rev8 1/7/2008
339
3.
340
GA.Rev8 1/7/2008
4.
On Client Workstation Installation Setup Type, complete these fields: Select Setup Type Install Path Ensure the radio button for your language is selected. The Installer provides a default path to the existing client installation on this machine: c:\JDEdwards\812 You must verify that this drive and path is valid for your installation. You can use the browse function to locate the directory.
5.
Click Finish.
The Clinet Workstation Install Progress displays the progress of the language installation.
GA.Rev8 1/7/2008
341
When the installation finishes, the Oracle Deployment Server Setup form indicates whether the installation was successful. 6. On Installation Complete, click OK.
Note
To access more than one language within the same package, you need to build a custom package that includes all available languages.
342
GA.Rev8 1/7/2008
Note
If you choose a custom installation plan, you can choose which language to install for each environment. This section assumes you are defining a custom plan.
GA.Rev8 1/7/2008
343
1. 2.
On Installation Planner, enter the basic plan information. In the Include Language area, select the Language Only option.
344
GA.Rev8 1/7/2008
1.
From Environment Selection, all environments and languages are the default values. Clear the options for Default Environment and Default Languages if you want to specify which language or languages to install for each environment.
GA.Rev8 1/7/2008
345
Selecting an Environment
To select an environment:
Choose the environment for which you wish to install a language. The Language Selection form appears.
346
GA.Rev8 1/7/2008
Selecting a Language
To select a language:
1. 2. 3. 4.
On Language Selection, to set up a language for the selected environment, choose the appropriate language. From the Row menu, click Select. Repeat the above steps until all your languages have been selected. Click OK.
GA.Rev8 1/7/2008
347
348
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
349
350
GA.Rev8 1/7/2008
351
Directory Name \JDEdwards\E812\path_code\bin32 \JDEdwards\E812\path_code\EOne \JDEdwards\E812\path_code\include \JDEdwards\E812\path_code\lib32 \JDEdwards\E812\path_code\make \JDEdwards\E812\path_code\obj \JDEdwards\E812\path_code\package \JDEdwards\E812\path_code\package\DATA \JDEdwards\E812\path_code\package\DATACOMP \JDEdwards\E812\path_code\package\DV812FA \JDEdwards\E812\path_code\package\DV812PA \JDEdwards\E812\path_code\res \JDEdwards\E812\path_code\source \JDEdwards\E812\path_code\spec \JDEdwards\E812\path_code\work \JDEdwards\E812\Hosts \JDEdwards\E812\Hosts\AS400
Contents
Host scripts and programs. Partial host installation objects. The files reside here until you install the platform-specific objects. Partial host installation objects. The files reside here until you install the platformspecific objects. Partial host installation objects. The files reside here until you install the platformspecific objects. Partial host installation objects. The files reside here until you install the platformspecific objects. Partial host installation objects. The files reside
\JDEdwards\E812\Hosts\Hp9000
\JDEdwards\E812\Hosts\IntelNT
\JDEdwards\E812\Hosts\Linux
\JDEdwards\E812\Hosts\RS6000
352
GA.Rev8 1/7/2008
Directory Name
\JDEdwards\E812\Hosts\Sun
Partial host installation objects. The files reside here until you install the platformspecific objects. Media objects for runtime.
\JDEdwards\E812\InstallLogs \JDEdwards\E812\MediaObj \JDEdwards\E812\misc \JDEdwards\E812\misc\MSDE \JDEdwards\E812\OneWorld Client Install Package build files for web development client.
\JDEdwards\E812\OneWorld Client Install\Font \JDEdwards\E812\OneWorld Client Install\Misc \JDEdwards\E812\OneWorld Client Install\Push Install Listener \JDEdwards\E812\OneWorld Client Install\ThirdParty \JDEdwards\E812\OneWorld Client Install\ThirdParty\BPMBroker \JDEdwards\E812\OneWorld Client Install\ThirdParty\MOBILESQL \JDEdwards\E812\OneWorld Client Install\ThirdParty\MSDE \JDEdwards\E812\OneWorld Client Install\ThirdParty\Synchrologic \JDEdwards\E812\OneWorld Client Install\ThirdParty\WebDevFeature \JDEdwards\E812\Planner \JDEdwards\E812\PACKAGE_INF \JDEdwards\E812\PACKAGE_INF\Feature_Inf \JDEdwards\E812\planner \JDEdwards\E812\Planner\bin32 Application and business function .DLL files Bitmap objects for applications Planner Environment files
GA.Rev8 1/7/2008
353
Directory Name \JDEdwards\E812\planner\spec \JDEdwards\E812\PrintQueue \JDEdwards\E812\SolutionExplorer \JDEdwards\E812\SolutionExplorer\Data \JDEdwards\E812\SolutionExplorer\Data\+ Concept To Opportunity \JDEdwards\E812\SolutionExplorer\Data\+ Consumption To Reorder \JDEdwards\E812\SolutionExplorer\Data\+ Demand To Available \JDEdwards\E812\SolutionExplorer\Data\+ Implementation Approach \JDEdwards\E812\SolutionExplorer\Data\+ Manage Materials \JDEdwards\E812\SolutionExplorer\Data\+ Manage The Business \JDEdwards\E812\SolutionExplorer\Data\+ Order To Cash \JDEdwards\E812\SolutionExplorer\Data\+ Procure To Pay \JDEdwards\E812\SolutionExplorer\Data\RNT3 \JDEdwards\E812\SolutionExplorer\Data\SK_FOUNDATION_DOCUMENTS \JDEdwards\E812\SolutionExplorer\Data\style \JDEdwards\E812\SolutionExplorer\Data\styles \JDEdwards\E812\SolutionExplorer\PortalLite \JDEdwards\E812\System \JDEdwards\E812\System\bin32 \JDEdwards\E812\System\classes \JDEdwards\E812\System\classes\samples \JDEdwards\E812\System\Include
Contents
System files.
\JDEdwards\E812\System\Libv32 \JDEdwards\E812\System\Locale \JDEdwards\E812\System\Locale\Iconv \JDEdwards\E812\System\Locale\Uconvtab \JDEdwards\E812\System\Locale\Xml \JDEdwards\E812\System\Models \JDEdwards\E812\System\OWPatrol \JDEdwards\E812\System\OWPatrol\owkm \JDEdwards\E812\System\OWPatrol\owkm\images \JDEdwards\E812\System\OWPatrol\owkm\km \JDEdwards\E812\System\OWPatrol\owkm\psl \JDEdwards\E812\System\Resource 354 GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.
Directory Name \JDEdwards\E812\System\Resource\cidfont \JDEdwards\E812\System\Resource\cmap \JDEdwards\E812\System\Resource\encoding \JDEdwards\E812\System\Resource\iccprofile \JDEdwards\E812\System\Resource\truetype \JDEdwards\E812\systemcomp \JDEdwards\E812\_jvm \JDEdwards\E812\_jvm\bin \JDEdwards\E812\_jvm\bin\client \JDEdwards\E812\_jvm\lib \JDEdwards\E812\_jvm\lib\applet \JDEdwards\E812\_jvm\lib\cmm \JDEdwards\E812\_jvm\lib\ext \JDEdwards\E812\_jvm\lib\fonts \JDEdwards\E812\_jvm\lib\i386 \JDEdwards\E812\_jvm\lib\im \JDEdwards\E812\_jvm\lib\images \JDEdwards\E812\_jvm\lib\images\cursors \JDEdwards\E812\_jvm\lib\security \JDEdwards\E812\_jvm\lib\zi \JDEdwards\E812\_uninst
Contents
GA.Rev8 1/7/2008
355
Definition
Production business function include (.h) files. Import libraries for business functions. Object code for business functions. Business function source. Replicated local objects.
\JDEdwards\E812\DDP\DV812\lib32
\JDEdwards\E812\DDP\DV812\make \JDEdwards\E812\DDP\DV812\obj
\JDEdwards\E812\DDP\DV812\res \JDEdwards\E812\DDP\DV812\source \JDEdwards\E812\DDP\DV812\spec \JDEdwards\E812\DDP\DV812\work \JDEdwards\E812\DDP\DV812\res\AVI Files \JDEdwards\E812\DDP\DV812\res\FormLines \JDEdwards\E812\DDP\DV812\res\Icons \JDEdwards\E812\DDP\DV812\res\images \JDEdwards\E812\DDP\DV812\res\treebmps \JDEdwards\E812\DDP\system\Bin32 \JDEdwards\E812\DDP\system\Classes \JDEdwards\E812\DDP\system\Explorer \JDEdwards\E812\DDP\system\Generator \JDEdwards\E812\DDP\system\Include \JDEdwards\E812\DDP\system\IncludeV \JDEdwards\E812\DDP\system\Lib32 \JDEdwards\E812\DDP\system\Libv32 \JDEdwards\E812\DDP\system\Locale \JDEdwards\E812\DDP\system\Models \JDEdwards\E812\DDP\system\OWPatrol \JDEdwards\E812\DDP\system\Resource \JDEdwards\E812\DDP\packages\PD812FA \JDEdwards\E812\DDP\packages\PD812FA\bin32 \JDEdwards\E812\DDP\packages\PD812FA\include \JDEdwards\E812\DDP\packages\PD812FA\obj System include files. System executables.
356
GA.Rev8 1/7/2008
Directory Name \JDEdwards\E812\DDP\packages\PD812FA\source \JDEdwards\E812\DDP\packages\PD812FA\spec \JDEdwards\E812\DDP\packages\PD812FA\obj\CAEC \JDEdwards\E812\DDP\packages\PD812FA\obj\CALLBSFN \JDEdwards\E812\DDP\packages\PD812FA\obj\CCONVERT \JDEdwards\E812\DDP\packages\PD812FA\obj\CCORE \JDEdwards\E812\DDP\packages\PD812FA\obj\CCRIN \JDEdwards\E812\DDP\packages\PD812FA\obj\CDBASE \JDEdwards\E812\DDP\packages\PD812FA\obj\CDDICT \JDEdwards\E812\DDP\packages\PD812FA\obj\CDESIGN \JDEdwards\E812\DDP\packages\PD812FA\obj\CDIST \JDEdwards\E812\DDP\packages\PD812FA\obj\CDMDSCH \JDEdwards\E812\DDP\packages\PD812FA\obj\CEPM \JDEdwards\E812\DDP\packages\PD812FA\obj\CFIN \JDEdwards\E812\DDP\packages\PD812FA\obj\CFND \JDEdwards\E812\DDP\packages\PD812FA\obj\CHRM \JDEdwards\E812\DDP\packages\PD812FA\obj\CINSTALL \JDEdwards\E812\DDP\packages\PD812FA\obj\CINV \JDEdwards\E812\DDP\packages\PD812FA\obj\CLOC \JDEdwards\E812\DDP\packages\PD812FA\obj\CLOG \JDEdwards\E812\DDP\packages\PD812FA\obj\CMFG \JDEdwards\E812\DDP\packages\PD812FA\obj\CMFGBASE \JDEdwards\E812\DDP\packages\PD812FA\obj\COBJLIB \JDEdwards\E812\DDP\packages\PD812FA\obj\COPBASE \JDEdwards\E812\DDP\packages\PD812FA\obj\CPAY \JDEdwards\E812\DDP\packages\PD812FA\obj\CRES \JDEdwards\E812\DDP\packages\PD812FA\obj\CRUNTIME \JDEdwards\E812\DDP\packages\PD812FA\obj\CSALES \JDEdwards\E812\DDP\packages\PD812FA\obj\CTC \JDEdwards\E812\DDP\packages\PD812FA\obj\CTOOL \JDEdwards\E812\DDP\packages\PD812FA\obj\CTRAN \JDEdwards\E812\DDP\packages\PD812FA\obj\CTRANS \JDEdwards\E812\DDP\packages\PD812FA\obj\CWARE \JDEdwards\E812\DDP\packages\PD812FA\obj\CWRKFLOW \JDEdwards\E812\DDP\packages\PD812FA\obj\JDBTRG1 \JDEdwards\E812\DDP\packages\PD812FA\obj\JDBTRG2 \JDEdwards\E812\DDP\packages\PD812FA\obj\JDBTRG3 \JDEdwards\E812\DDP\packages\PD812FA\source\CAEC \JDEdwards\E812\DDP\packages\PD812FA\source\CALLBSFN \JDEdwards\E812\DDP\packages\PD812FA\source\CCONVERT \JDEdwards\E812\DDP\packages\PD812FA\source\CCORE Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008
Definition
357
Directory Name \JDEdwards\E812\DDP\packages\PD812FA\source\CCRIN \JDEdwards\E812\DDP\packages\PD812FA\source\CDBASE \JDEdwards\E812\DDP\packages\PD812FA\source\CDDICT \JDEdwards\E812\DDP\packages\PD812FA\source\CDESIGN \JDEdwards\E812\DDP\packages\PD812FA\source\CDIST \JDEdwards\E812\DDP\packages\PD812FA\source\CDMDSCH \JDEdwards\E812\DDP\packages\PD812FA\source\CEPM \JDEdwards\E812\DDP\packages\PD812FA\source\CFIN \JDEdwards\E812\DDP\packages\PD812FA\source\CFND \JDEdwards\E812\DDP\packages\PD812FA\source\CHRM \JDEdwards\E812\DDP\packages\PD812FA\source\CINSTALL \JDEdwards\E812\DDP\packages\PD812FA\source\CINV \JDEdwards\E812\DDP\packages\PD812FA\source\CLOC \JDEdwards\E812\DDP\packages\PD812FA\source\CLOG \JDEdwards\E812\DDP\packages\PD812FA\source\CMFG \JDEdwards\E812\DDP\packages\PD812FA\source\CMFGBASE \JDEdwards\E812\DDP\packages\PD812FA\source\COBJLIB \JDEdwards\E812\DDP\packages\PD812FA\source\COPBASE \JDEdwards\E812\DDP\packages\PD812FA\source\CPAY \JDEdwards\E812\DDP\packages\PD812FA\source\CRES \JDEdwards\E812\DDP\packages\PD812FA\source\CRUNTIME \JDEdwards\E812\DDP\packages\PD812FA\source\CSALES \JDEdwards\E812\DDP\packages\PD812FA\source\CTC \JDEdwards\E812\DDP\packages\PD812FA\source\CTOOL \JDEdwards\E812\DDP\packages\PD812FA\source\CTRAN \JDEdwards\E812\DDP\packages\PD812FA\source\CTRANS \JDEdwards\E812\DDP\packages\PD812FA\source\CWARE \JDEdwards\E812\DDP\packages\PD812FA\source\CWRKFLOW \JDEdwards\E812\DDP\packages\PD812FA\source\JDBTRG1 \JDEdwards\E812\DDP\packages\PD812FA\source\JDBTRG2 \JDEdwards\E812\DDP\packages\PD812FA\source\JDBTRG3 \JDEdwards\E812\DDP\system\Generator\WEB-INF \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes \JDEdwards\E812\DDP\system\Generator\WEB-INF\lib \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpm \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpmweb \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\database \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas 358 GA.Rev8 1/7/2008
Definition
Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \printqueuecenter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\redirector \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\taskexplorer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\workflow \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\beans \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\behaviorcom \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\cache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\datatypes \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\exception \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\gui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\imagegenerator \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\logging \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\owsecurity \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\resource \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\spec \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\timer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\util
Definition
GA.Rev8 1/7/2008
359
Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\webgui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\gui\explorer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\gui\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\log4j \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\saw \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\logging\test \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\cache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\base\util\ftp \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\smtp \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \base\util\threadpool \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpm\utils \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \bpmweb\broker \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \bpmweb\Handlers \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\bpmweb\Util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\base \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\explorer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards
Definition
360
GA.Rev8 1/7/2008
Directory Name \database\impl \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\database\jdb \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\application \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\as400 \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\businessview \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\condensed \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\config \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\datacache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\formatter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\logical \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\oracle \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\physical \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\resultset \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008
Definition
361
Directory Name \database\impl\retry \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\security \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\signon \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\sql \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\sqlserver \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\standalone \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\transaction \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\transform \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\trigger \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\udb \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\impl\usage \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\base \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\bootstrap \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\company 362 GA.Rev8 1/7/2008
Definition
Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\ocm \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\role \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\security \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\serviceobj \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\spec \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \database\services\udc \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\bsfnplugin \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\exception \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\net \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\res \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\security \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\jas\services \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\transaction \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\anonuser \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\env \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \jas\services\userpref
Definition
GA.Rev8 1/7/2008
363
Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\ifc \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\beans \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\components \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\js \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \oneworld\owportal\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\envcheck \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\hr \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\importer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\linkCenter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\reportcenter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\sarsystem \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal 364 GA.Rev8 1/7/2008
Definition
Directory Name \components\webcheck \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\workcenter \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\oneworld\owpo rtal \components\reportcenter\client \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\beans \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\client \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\components \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\datahandler \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\defaults \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\gui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\js \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\unittest \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\client \JdeTreeControl \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \envcheck \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \importer \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \linkcenter
Definition
GA.Rev8 1/7/2008
365
Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \login \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \rss \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \saw \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \search \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \webcheck \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\compone nts \importer\upload \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \portal\util\cache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\portal\util\gui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\base \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\er \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\runtime\event \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\interfac \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards
Definition
366
GA.Rev8 1/7/2008
Directory Name \runtime\model \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\swing \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine\form \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\engine\version \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\er\erobjects \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\engine \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\jniinclude \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\model \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\generator\view \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\model\form \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\model\grid \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\input Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008
Definition
367
Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\output \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\virtual\xapi \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\form \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\grid \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \runtime\vtcomponent\version \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawagent \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawchart \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawcomm \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawdb \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawjavalog \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawjdbj \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\sawlog \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \saw\sawsuperagent \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\smc \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\saw\smcgui \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\services\login \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \services\objectlookup \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards 368 GA.Rev8 1/7/2008
Definition
Directory Name \services\login\display \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\kernel \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\lib \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\net \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\system\xml \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\kernel\jdesaw \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\lib\cache \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\as400 \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\db \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\security\proxy \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \system\xml\test \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\actions \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\db \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\filters \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\gui Copyright 2008, Oracle. All rights reserved. GA.Rev8 1/7/2008
Definition
369
Directory Name \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\launchers \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \taskexplorer\gui\tagext \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \util\imagegenerator \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \workflow\DesignEngine \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \workflow\monitoring \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\workflow\util \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\serverproxy \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\test \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtse \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtsm \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards\xts\xtsr \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\xtse\adapters \JDEdwards\E812\DDP\system\Generator\WEB-INF\classes\com\jdedwards \xts\xtsr\adapters \JDEdwards\E812\DDP\system\IncludeV\unicode \JDEdwards\E812\DDP\system\Locale\Iconv \JDEdwards\E812\DDP\system\Locale\Uconvtab \JDEdwards\E812\DDP\system\Locale\Xml \JDEdwards\E812\DDP\system\OWPatrol\owkm \JDEdwards\E812\DDP\system\OWPatrol\owkm\images \JDEdwards\E812\DDP\system\OWPatrol\owkm\km \JDEdwards\E812\DDP\system\OWPatrol\owkm\psl \JDEdwards\E812\DDP\system\Resource\cidfont \JDEdwards\E812\DDP\system\Resource\cmap \JDEdwards\E812\DDP\system\Resource\encoding
Definition
370
GA.Rev8 1/7/2008
Definition
GA.Rev8 1/7/2008
371
Directory Structure \E812\system\owpatrol\owkm\psl \E812\system\resource\cidfont \E812\system\resource\cmap \E812\system\resource\encoding \E812\system\resource\font \E812\system\resource\iccprofile \E812\system\resource\truetype \E812\system\resource\font\pfm
372
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
373
Business Data
This chart lists the characteristics of the Business Data data source. Field Data Source Name (list includes possible sources) Business Data - PROD Business Data - CRP Business Data - TEST Business Data - PS812 Data Source Use Data Source Type Database Server Name Platform Advanced Exit Clustered Unicode Use Decimal Shift Use Julian Dates Support for Locking Updates OCM Data Source Use Table Owner LOB Data Type Support Object Owner ID (list includes possible owner Ids) PRODDTA CRPDTA TESTDTA PS812DTA Database Name (list includes possible databases) Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Connect string for the database Selected Selected Selected Selected Blank Selected DB O Name of the machine where your database resides Platform type Selected Blank Selected Selected Selected Selected Blank Selected Selected Valid Value for Oracle
374
GA.Rev8 1/7/2008
Central Objects
This chart lists the characteristics of the Central Objects data source. Field Data Source Name (list includes possible sources) Central Objects - PROD Central Objects - CRP Central Objects - TEST Central Objects - PS812 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) PD812 PY812 DV812 PS812 Library Name Library List Name Database Name (list includes possible databases) Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected DB O Oracle
GA.Rev8 1/7/2008
375
Control Tables
This chart lists the characteristics of the Control Tables data source. Field Data Source Name (list includes possible sources) Control Tables - Prod Control Tables - CRP Control Tables - Test Control Tables - PS812 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) Control Tables - Prod Control Tables - CRP Control Tables - PS812 Control Tables - Test Library Name Library List Name Database Name (list includes possible databases) Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected DB O Oracle
376
GA.Rev8 1/7/2008
Data Dictionary
This chart lists the characteristics of the Data Dictionary data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Oracle Data Dictionary - 812 DB O DD812 Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected
GA.Rev8 1/7/2008
377
Logic
This chart lists the characteristics of the Logic data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source iSeries BLOB Data Source Oracle Name of the machine where your database resides SVR Blank SVM812 Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected Blank
378
GA.Rev8 1/7/2008
Object Librarian
This chart lists the characteristics of the Object Librarian data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Valid Value for Oracle Object Librarian - 812 DB O OL812 Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected
GA.Rev8 1/7/2008
379
Language
This chart lists the characteristics of the Language data source, which applies to the MSDE database on the Deployment Server. Field Data Source Name (list includes possible sources) Valid Value for MSDE Language Language 812 For example, French 812. Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) Library Name Library List Name Database Name (list includes possible databases) DB N Blank Blank Blank Language JDELanguage_F812 Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source iSeries BLOB Support Local LOCAL Blank Blank Blank Blank Blank Blank
380
GA.Rev8 1/7/2008
Local
This chart lists the characteristics of the Local data source, which applies to the MSDE database on the Deployment Server. Field Data Source Name (list includes possible sources) Valid Value for MSDE Local JDELocal - DV812 JDELocal - PS812 JDELocal - PD812 JDELocal - PY812 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) Library Name Library List Name Database Name (list includes possible databases) DB N dbo Blank Blank JDELocal JDEPlan812 JDECTL812 JDEDD812 JDESY812 JDEVL812 JDEOL812 JDEData812 Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Local LOCAL Selected Selected Selected Selected Blank Blank
GA.Rev8 1/7/2008
381
Server Map
This chart lists the characteristics of the Server Map data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name DDL Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Valid Value for Oracle machinename - 812 Server Map DB O SVM812 Blank Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Selected Selected
382
GA.Rev8 1/7/2008
System
This chart lists the characteristics of the System data source. Field Data Source Name Data Source Use Data Source Type Object Owner ID Library Name Library List Name Database Name Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Valid Value for Oracle System - 812 DB O SY812 Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected
GA.Rev8 1/7/2008
383
Versions
This chart lists the characteristics of the Versions data source. Field Data Source Name (list includes possible sources) Versions - PD812 Versions - PY812 Versions - DV812 Versions - PS812 Data Source Use Data Source Type Object Owner ID (list includes possible owner IDs) PD812 PY812 DV812 PS812 Library Name Library List Name Database Name (list includes possible databases) Server Name Platform Use Table Owner Use Julian Dates Use Decimal Shift Support for Updates OCM Data Source LOB Data Source Blank Blank Connect string for the database Name of the machine where your database resides Platform type Selected Selected Selected Selected Blank Selected DB O Valid Value for Oracle
384
GA.Rev8 1/7/2008
Note
The Local pathcode data source refers only to local databases that are path code specific. In the chart below, Local pathcode could represent more than one data source, depending on the number of path codes you use. Pathcode is one or more of the following path codes: PY812 DV812 PS812 PD812 DEP812
Note
The xxxx Local data source refers only to the local database on the Deployment Server, which is used by the planner environment. * Specific tables in the list below reflect language information, and contain a language preference code that is translated by JD Edwards EnterpriseOne. Table F0004D* Data Source Control Tables Description Purpose
UDC Alternate Language Contains the User Defined Code (UDC) key, language key, and text for headers in the F0004 table. Provides UDC type descriptions for alternate languages. UDC Alternate Language Contains UDC key, language key, and text for detail in the F0005 table. Provides UDC value descriptions for alternate languages. Stores text OLE references and image references. Stores glossary text and media objects for all languages.
F0005D*
Control Tables
F00165*
Business Data xxxx Media Objects storage Data Dictionary - 812 Object Librarian - 812 Business Data Local Data Dictionary Local Object Librarian Local System - 812 Planner - 812 System Local Library List User
F0092
Contains one record per user with initial menu, initial program, and whether to enable fast path.
F00921*
System - 812
Table
Description
F00922
Contains one record per user with workstation configuration name. This table is used with the F00050 table.
F00924
F0093
F0094
F00941
Environment Detail EO
Contains one record per environment, with release and path code.
F00942
Contains one record per path code with the data source for the specification files and the server path for the other development objects (.DLL, source, headers). Contains one record per release, with the data source for system tables and the environments server path.
F00945
Release Master
F00946
Release Compatibility Map Contains information used to map major release levels to determine forward and backward compatibility.
F00948
Contains information used to map a specific type of data source to a release level, such as Object Librarian, data dictionary, or versions list data sources. Stores security attributes (one record for each user or group).
F00950
F00960
System - 812
Machine/ Group Identifica- Stores a list of all workstations that intion stalled Release 8.9 to scheduled packGA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.
386
Table
Description
Purpose ages.
F83100*
Data Title
Series of definitions of data titles. Each row is the definition or specification of the date title. Provides soft coded RDA text. Gives each period number an associated description. Provides soft coded RDA text. Lists Release 8.9 tasks (Solution Explorer only). Groups tasks listed in the F9000 table in logical (parent/child) tree order (ActivEra only). Provides descriptions of tasks listed in the F9000 table (ActivEra only). Describes the attributes of variants listed in this table. A variant performs a series of designated tasks (nodes) within a tree order defined in the F9001 table (ActivEra only). Provides translated text for descriptions listed in the F9005 table (ActivEra only). Defines which nodes (tasks) are run within a variant and the names of any tasks dynamically renamed within a variant (ActivEra only). Provides translated text for descriptions listed in the F9006 table (ActivEra only).
F83110*
Column Headings
F9000 F9001
F9002 F9005
F9005D F9006
Alternate Variant Detail Descriptions Environment Setup Answers ActivEra Qualifier Rules Header
Defines rule names used by ActivEra. Rules are applied to conditionally execute an individual task or task relationship (tree order). Lists conditional statements within rules listed in the F9020 table (ActivEra only). Stores indexes of HTML documents associated with specific tasks (ActivEra only).
F9022 F9030
F9050
Control Table
Rough-cut Answer Depend- Defines the hierarchical means of eliminency ating system codes and subsequent applications which do not apply within a specified system configuration (ActivEra only). Favorites Relationship Properties Categorizes business views on a parent/ child format.
Favorites All Descriptions Stores alternate descriptions for different languages. Scheduled Job Master GA.Rev8 1/7/2008 387
Table F91310 F91320 F91330 F91400 F91410 F91420 F91430 F91500 F91510 F9200
Data Source System - 812 System - 812 System - 812 System - 812 System - 812 System - 812 System - 812 System - 812 System - 812 Data Dictionary Data Dictionary Local
Description Scheduled Job Parameters Job Schedule Scheduled Job Override Printer Info Report Director Templates Report Director Templates Sequence Items Report Director Template Smart Field Activation Smart Field Template Criteria
Purpose
Contains the design templates for reports that users can create. Helps users manipulate data sequencing. Creates a list showing all data items belonging to a smart field template. Stores a subset of selection criteria.
Application Header for Tip Contains application names or tools of the Day names where tips reside. Tip Details for Tip of the Day Data Item Master Stores tip texts and a key to modify the sequence. Contains the relational breakdown of data dictionary. Contains display text for each data field for language, data item, and product code reporting. Used when data items descriptions requested. Data dictionary row and column text for all languages* * The language preference code for data dictionary applies to text only. Text includes row and column headings, a compressed description, and glossaries.
F9202*
F9203*
Contains alpha descriptions and compressed descriptions of data items. Used when data items descriptions requested. Similar to the F9202 table. Contains data dictionary alpha descriptions for all languages.
F9207
DD Error Message Informa- Contains one record per error message. tion Data Field Specifications Contains detailed information (specifications) for each data item. This table is accessed whenever a data item needs to be identified. Contains information for Smart Fields.
F9210
F9211
Data Dictionary Smart Fields Smart Field Criteria Setup Rules Software Package Build Header Software Package Build GA.Rev8 1/7/2008
Data Dictionary - 812 Data Dictionary Local System - 812 System - 812
Stores the detail information from the definition process of package build. Stores information from the assembly Copyright 2008, Oracle. All rights reserved.
Table F96210
Description Header Package Build Validation Tables Package Build Validation Detail Software Package Build Header History
F96211
F96215
Contains the history record of the F96021 record. It stores statuses of the package each time it is built.
F9622
Stores the option information from the definition process of package build. Each record is either the name of the specification file, the name of a .DLL file, the name of the compression directory, or the name of an object. Contains the history record of the software build program (P9622). Stores the status of the build on the operation of that record when the package is finished. Stores the detail information for the assembly process of package build. Stores the object names, foundation name, data name, or helps name. Holds the default information regarding all machines used by JD Edwards EnterpriseOne.
F96225
F9631
F9650
Machine Master
F9651
Machine Detail
Holds specific information about each machine defined in the machine master table by record type.
F9652
Deployment Group Header Specifies groups that can be used by the Release 8.12 administrator for deploying packages.
F9653
Stores the users that belong to one or more groups that were defined in the deployment header file. In addition, groups of groups can be defined here. Enables definition of one or more locations for deployment. This table is used primarily in multitier deployment.
F9654
GA.Rev8 1/7/2008
389
Table F9660
Purpose
F96600
Deployment Features
F96601
Deployment Registry
F96602
Deployment Shortcut
F96603
Deployment Execute
F96604
F96605
Deployment Initialization
F96605T
Deployment Initialization
F96606
F966071
F966072
390
GA.Rev8 1/7/2008
Table
Description
Purpose
F9670
F9671
F96710
F9672
F96761
F967611
F9691100 F9691400
Change Table Report Dir- Stores adds/changes/deletes to the Reector Template Header port Director template header table between releases. Change Table Report Dir- Stores adds/changes/deletes to the Reector Template Sequence port Director Template Sequence table between releases. Change Table Smart Field Stores adds/changes/deletes to the Smart Activity Field Activity table between releases. Change Table Smart Field Stores adds/changes/deletes to the Smart Criteria Field Criteria table between releases. UDC Merge table Contains the UDC records changed or added from release to release. This table is used by the UDC merge program (R98741).
F9691410
System Local
F960004 F960005
Control Tables xxx Control Tables Local Control Tables xxx Control Tables Local
GA.Rev8 1/7/2008
391
Table F9755
Purpose Contains the data dictionary items changed or added from release to release. This table is used by the Data Dictionary merge program (R989200P). Lists changes made to alpha descriptions of data items (F9203) between releases. This table is used in the data dictionary merge process. Lists changes made to error messages (F9207) between releases. This table is used in the data dictionary merge process. Lists changes made to field specifications (F9210) between releases. This table is used in the data dictionary merges.
F9757
F9759
F9760
Data Dictionary - 812 Data Dictionary Local Central Objects - xxx Versions Local Central Objects - xxx Versions Local System - 812 System Local
Cross Reference Relation- Lists cross-reference relationships for ships business views, event rules, and controls. Cross Reference Field Re- Lists cross-reference relationships for lationships fields in an application. Imaging Constants Determines whether you are doing thirdparty imaging. Contains one record per version (batch or interactive). For interactive, it stores processing option values. For batch, this table holds data selection, sequencing, and other template overrides.
F983051
Versions List
F982xx
Series (OMW)
F98306* F9840
Installation Plan Master ta- Contains general information for the inble stallation plan with one record per plan name (description and status). Data Source Plan Detail ta- Lists data sources for each plan, and one ble record per plan record per data source associated with that plan. Host Plan Detail table Lists the Enterprise Server and hosts for each plan (one record per plan, per server). Contains the last location for a plan.
F98401
F98402
F984021
F984022
Stores replicated plan for remote locations, publisher, and subscriber tables.
F98403
Version - 812
Environment Plan Detail ta- Lists environments for each plan. Holds ble flags for production data, demo data, and GA.Rev8 1/7/2008 Copyright 2008, Oracle. All rights reserved.
392
Table
Description
F984031*
Language and Environment Lists language and the selected environPlan Detail table ments for each plan. Package Plan Detail table Lists packages and package definitions for each environment. Lists table conversion information merged in Table Conversion Scheduler from Environment Planner and Table Conversion Planner. This table is similar to the F9843 table.
F98404
F98405
F984052
Table Conversion History Stores the logs for table conversions, Log control table merges, and specification merges. Table Conversion JDE Scheduler Contains table conversions, control table merges, and specification merges for upgrades, updates, and coexistent installations. Lists default data sources by environment. This table is used during installation.
F9843
System - 812
F9843T F98511
System - 812 System - 812 Planner - 812 REP Data Sources by Environment
F9860
Object Librarian Master ta- Contains one record per object with deble scription and object type. Object Librarian Status Detail Contains one record per object, per location, per path code. Each object has a server location plus locations for each person who checks it out to his machine.
F9861
F986101
Object Configuration Mas- Contains all data sources for tables, ter batch applications, and business functions that run on the server. The only data sources not controlled through this file are the system data source in Release Master and the Development data source in object path master. Data Source Master Holds data source definitions. One record per data source with type, database, machine name, and foundation .DLL.
F98611
F986110
Contains one record for each job on the server with status information.
GA.Rev8 1/7/2008
393
Table F986111
Data Source System - 812 Server Map Planner - 812 System Local
F986113
F986115
Table and Data Source Siz- Holds storage, sizing, and location paraing table meters for Oracle, with some general information for all data sources.
F986116
MVS table and Data Source Holds storage, sizing, and location paraSizing meters for MVS. Similar to the F986115 table.
F98613
F986150
Lists objects belonging to each server package. This table is used by the server package installation process (P986150). Lists the servers and path codes to which a given server package will be transferred. This table is used by the server package install process (P986150). Contains the master list of all service packages. This table is used by the server package install process (P986150). Lists the printer definitions, including logical name, physical name, and conversion program, one record per printer. Lists default printer settings by user and environment. Lists paper sizes defined for each printer, one record per printer.
F986151
F986152
F98616
Printer
F986161
F986162
Paper Definition
394
GA.Rev8 1/7/2008
Table F986163
Purpose Lists printer capabilities (paper orientation and size, type and location of printer) for each printer, one record per printer. Lists printer output conversions defined for each printer, one record per printer. Stores the default printer information including the user, environment, host name, printer name, and the status. Reserved for future use.
F986164
Output Conversions
F986165
System Shared
F986167
Printer Security
F9862
Object Librarian Function Lists one record for each function conDetail tained in the source file. Object Librarian Object Relationships Form Information Contains one record per business function per related object. This table is used when building business functions. Contains one record per interactive form, including online help information. Holds table-specific information for tables created in TDA (BOBSPEC). Holds all column information for the table in TDA (DDCLMN). TDA Information pertaining to the primary index. TDA All fields that make up the primary index. Holds all business-view specific information from BDA. Stores header file for event rules.
F9863
F9865
Central Objects Specific- Table Header ations Central Objects Specific- Table Columns ations Central Objects Specific- Primary Index Header ations Central Objects Specific- Primary Index Detail ations Central Objects Specific- Business View Specificaations tions Central Objects Specific- Event Rules Link ations
Central Objects Specific- Event Rules Specification Contains actual event rules detail for a ations form. Central Objects Specific- Data Structure Templates ations Central Objects Specific- Media Object ations Central Objects Specific- Smart Field Named Mapations pings Central Objects Specific- FDA Text Information ations Contains one record for each template, for example, Data Structure for Business Function. Contains media object text for tools. Contains smart field named mappings. Contains form design text for all languages for any generated application.
Central Objects Specific- FDA Specification Informa- Contains specifications for an applicaations tion tion. Central Objects Specific- FDA/SVR Header Informa- Contains summary information about ations tion each application.
GA.Rev8 1/7/2008
395
Data Source
Description
Purpose Contains summary information about each form for each application. Holds records that contain the report design aid text for all languages. Holds records that contain report design aid setup information. Contains business function specifications. Logs all transactions that take place to objects.
Central Objects Specific- FDA/SVR Detail Informaations tion Central Objects Specific- RDA Text Information ations Central Objects Specific- RDA Specification Info ations Central Objects Specific- JDEBLC Behavior Inations formation System - 812 Planner - 812 System Local Checkout Log table
F98825
System - 812
Contains information for deploying client packages, such as group user ID and package assignment.
F9883
System - 812
Release 8.12 Network Loc- Contains information for deploying servations table er packages, such as package assignments. Install Package Header Contains one record per package.
F9885
F9886
Contains one record per package per product code or object to be included in the package. Lists each time the package is built.
F9887
F9888
Control Tables Control Tables Control Tables Control Tables Control Tables Control Tables Control Tables Control Tables Control Tables
Contains multiple language information for the F98800 table. Categorizes Composer processes.
Activity Master Alternat- Contains multiple language information ive Description for the F98810 table. Activity Master Activity Specifications Process Activity Associations Organizational Structure Master Organizational Structure Rule Process Instance Contains workflow activity information. Contains workflow activity specifications stored as event rules. Contains workflow activity relationships. Contains the defining data for organizational models. Contains the data that ties workflows to organizational models. Contains the instances of workflow pro-
396
GA.Rev8 1/7/2008
Purpose cesses. Contains the instances of workflow activities within processes. Contains logging information generated from the Specification Merge for upgrade, update, and the Specification Merge and Object Librarian Merge reports.
F9889
Deployment Location Mas- Lists records for each tier with system ter and help information. This table is used only for multitier deployment. Deployment Location Path Code Package Deployment Scheduling Lists records with packages and help information. This table is used only for multitier deployment. Lists scheduling information for a multitier environment. Contains application version information: application, version, and user who entered it.
F98891
F98892
F98950
F98980
Font Override by Language Lists languages with information on corresponding display fonts. DB2 BLOB Support Table of Constants Lists constants for report design aid and form design aid. Determines which path codes to update for data dictionary replication. Contains one record for each replicated change. The table information is stored as a BLOB.
F98BLOB
System - 812
F98CONST System - 812 System Local F98DRENV System - 812 System - Planner F98DRLOG System - 812 Server Map System - Planner F98DRPCN System - 812 Server Map System - Planner F98DRPUB System - 812 System - Planner F98DRSUB System - 812 System - Planner F98EVDTL System - 812 System Local F98EVHDR System - 812 Copyright 2008, Oracle. All rights reserved.
Contains one record for each replicated change for each subscriber. Records are deleted as subscribers are notified.
Filters events displayed in Form Design Aid (FDA) or Universal Batch Engine (UBE) design. Stores event description and event ID. 397
Table
Description
F98MOQUE System - 812 System Local F98OWSEC System - 812 System Local F98TMPL System - 812 System Local F98VAR System - 812 System Local GT92002 GT9860A GT9862A GT98DSA GT98DSB Data Dictionary Object Librarian Object Librarian Object Librarian Object Librarian
Contains path codes to locations of multimedia objects. Contains the security tables that store the Release 8.12 user name and password for obtaining database user and password for certain data sources.
Templates
Table of Variables
Data Dictionary Glossary Contains column in data dictionary with Information descriptions of data dictionary items. Object Librarian Generic Text Structure Business Function Notes Data Structure Notes Structure and Item Data Structure Notes Structure and Item Media Object Templates Contains notes for objects in the Object Librarian. Contains notes for business functions. Contains notes for data structures. Contains notes for data structures. Contains templates that can be used for any attachment.
398
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
399
Enter 30.
A summary should appear at the end of the report verifying that all records were validated and the plan status was updated to 30.
ation report.
GA.Rev8 1/7/2008
401
402
GA.Rev8 1/7/2008
The default is to create all tables. Enter a Y to print all tables in the report or a N to print Leave this field blank. licensed tables only. The default is to print all tables.
GA.Rev8 1/7/2008
403
The Environment Database Creation report does not have a cover page. The reports list the following properties of each table (object) created: Object headings Syst Code Object Name Member Description Data Source Crt Tbl Copy Data Rec Insrt Rec Fail Copied from Data Source Status Source DS Warnings Target DS Warnings Description System Code. Shows the JD Edwards EnterpriseOne product code for the database listed in the Member Description column. Displays the alphanumeric name of the database. Displays the full name of the database being created. Displays the data source toward which this member points. Create Table. Shows whether tables are being created for this database. Shows whether the table was copied with data. Record Insert. Displays the number of records inserted. Record Failure. Displays the number of records that failed. Displays whether the table was copied with data and the data source from which it was copied. Displays one of the following statuses for the table creation: Success, Failure, or No Action. Displays any errors or warnings associated with the source data source. Displays any errors or warnings associated with the target data source.
404
GA.Rev8 1/7/2008
F03B112 F060116 F06106 F08042 F08330 F0911 F1501B F1721 F1731 F17111 F30006Z1 F3002Z1 F3003Z1 F3460Z1 F39062 F4077 F4106 F4111 F41508 F4600 F4812H F5215 F7302 F986113
Reports frequently list a status of No Action for tables the system created successfully. This status is accompanied by source and target data source warnings for these tables to explain why no action was taken. These warnings are normal and you can ignore them. The most common reasons for the warnings are because the source and target data sources are the same or the table was created by a previously installed environment. When the source and target are the same, the report lists the following warnings: Source data source warning Source Same as Target Target data source warning Existing table
GA.Rev8 1/7/2008
405
This commonly occurs when the copied from data source is the same as the target data source (where the table is mapped), and often occurs for the following tables: UDC tables F0004 and F0005 Menu tables F0082, F00821, F0083, and F0084
If you load multiple environments that share the same mappings (for example, DV812 and TS812), the first environment loaded (DV812 in this case) lists the tables with a Success status. The second environment (TS812) lists any tables already created during the first environment load with a status of No Action and a target data source warning of Existing Table. The No Action status and Existing Table warning for the second (TS812) environment are normal. You can verify that any table with a target data source warning of Existing Table has been created successfully by verifying it was created while loading a previous environment.
406
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
407
Note
You can ignore messages about security that appear during the uninstallation procedure. If error messages say that you cannot remove certain objects, make sure that you have not selected Read Only on the object property sheet, and then rerun the uninstallation program.
408
GA.Rev8 1/7/2008
GA.Rev8 1/7/2008
409
Note
When removing Oracle, you must drop the tablespace first and then drop the indexes.
Tip
The JD Edwards EnterpriseOne installer delivers sample scripts which you can use as examples of how to drop the tablespaces. You should examine and edit these to suit your needs with the understanding that they have not been delivered ready to run. You should pay attention to environment variables and arguments the scripts are expecting. Your DBA may prefer to drop the tablespaces themselves instead of using scripts. Sample drop scripts are located in the ORCL directory under the JD Edwards EnterpriseOne installation directory (E812): drop_db.bat You should also be aware that when you run the JD Edwards EnterpriseOne uninstaller, the directory structure containing sample drop scripts is deleted. JD Edwards En- Oracle Index Name (suffixed by the capital Oracle Tablespace Name (suffixed by the terpriseOne letter "I") capital letter "T") Component Foundation SVM812I SY812I OL812I DD812I Production PD812I PRODDTAI PRODCTLI SVM812T SY812T OL812T DD812T PD812T PRODDTAT PRODCTLT
Note
For your installation, the proddta and prodctl tablespaces and indexes may be needed for a previous release. Pristine PS812I PS812DTAI PS812CTLI PS812T PS812DTAT PS812CTLT
410
GA.Rev8 1/7/2008
JD Edwards En- Oracle Index Name (suffixed by the capital Oracle Tablespace Name (suffixed by the terpriseOne letter "I") capital letter "T") Component Development DV812I TESTDTAI TESTCTLI DV812T TESTDTAT TESTCTLT
Note
For your installation, the testdta and testctl tablespaces and indexes may be needed for a previous release. Prototype PY812I CRPDTAI CRPCTLI PY812T CRPDTAT CRPCTLT
Note
For your installation, the crpdta and crpdctl tablespaces and indexes may be needed for a previous release.
GA.Rev8 1/7/2008
411
Note
For your Oracle installation, the user jde_role may be needed for a previous release. Production PD812 PRODDTA PRODCTL
Note
For your installation, the proddta and prodctl users may be needed for a previous release. Pristine PS812 PS812DTA PS812CTL
412
GA.Rev8 1/7/2008
Note
For your installation, the testdta and testctl users may be needed for a previous release. Prototype PY812 CRPDTA CRPCTL
Note
For your installation, the crpdta and crpctl users may be needed for a previous release.
GA.Rev8 1/7/2008
413
Note
To avoid the possibility of removing valuable customer data, the uninstall wizard only removes the Enterprise Server runtime code. The uninstall wizard does not drop the databases or their users.
414
GA.Rev8 1/7/2008
Caution
As recommend by Microsoft, you must not have any open connections to the MSDE database when running the instcat.sql SQL script. You should sign off from EnterpriseOne and close SQL Server Enterprise Manager. Use this command line to call the instcat.sql SQL script. ISQL -Usa -Psa_password -Sserver_name -ilocation\Instcat.sql where U specifies the UsereID, and where P specifies the corresponding password, and where -S specifies the Server name of the SQL server, and where -i specifies the full path to the instcat.sql file, and optionally where E specifies the integrated logic to the SQL Server database.
Note
The server name switch (-S) may also include the instance name. For example, Server_name\instance_name.
GA.Rev8 1/7/2008
415
416