JD Edwards EnterpriseOne Tools Release 8.96 …...prise Servers running JD Edwards EnterpriseOne...

JD Edwards EnterpriseOne

Tools Release 8.96

Installation Guide for MicrosoftWindows

April 28, 2006

Installation Guide for Microsoft Windows

Copyright © 2006, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they areprovided under a license agreement containing restrictions on use and disclosure and are also protected by copy-right, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompila-tion of the Programs, except to the extent required to obtain interoperability with other independently createdsoftware 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 thedocumentation, please report them to us in writing. This document is not warranted to be error-free. Except asmay be expressly permitted in your license agreement for these Programs, no part of these Programs may be re-produced 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 be-half of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data de-livered to U.S. Government customers are "commercial computer software" or "commercial technical data" pur-suant 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 technicaldata, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to theextent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--RestrictedRights (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 danger-ous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy andother measures to ensure the safe use of such applications if the Programs are used for such purposes, and we dis-claim 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. Or-acle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risksassociated with the use of such content. If you choose to purchase any products or services from a third party, therelationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-partyproducts or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery ofproducts or services and warranty obligations related to purchased products or services. Oracle is not responsiblefor 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 documenta-tion and disclaims any and all liability or damages resulting from use of said software or documentation. The fol-lowing open source software may be used in Oracle's PeopleSoft products and the following disclaimers areprovided.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copy-right (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 PURPOSEARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CON-TRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTI-TUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LI-ABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OFTHE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

http://www.apache.org/

Table of Contents

1. Understanding the Tools Release Installation ........................................................................ 1Accessing Minimum Technical Requirements ...................................................................... 1

2. Installing Tools Release 8.96 ................................................................................................ 3Installing the Deployment Server ....................................................................................... 3

Backing Up Your Existing System ............................................................................. 3Downloading Tools Release 8.96 for the Client Platform ................................................ 4Running the Install Manager ..................................................................................... 4

Installing the Windows-based Enterprise Server Host Code ..................................................... 5Understanding the Enterprise Server Installation ........................................................... 5Downloading Tools Release 8.96 ............................................................................... 6Stopping Services .................................................................................................... 7Running the Installation Wizard ................................................................................. 7Recovering from a Failed Install .............................................................................. 13Working with Uninstallation ................................................................................... 16Working with the Install Log File ............................................................................. 16Working with the jdelog.properties File ..................................................................... 17

3. Verifying ODBC Connectivity ........................................................................................... 19

4. Working With the Client Update Package ........................................................................... 21Understanding the Client Update Package .......................................................................... 21Creating the Client Update Package .................................................................................. 22

5. Working With Long Running Process Issues ....................................................................... 23Understanding Long Running Process Issues ...................................................................... 23Enabling Long Running Processes .................................................................................... 24

6. Rebuilding Business Functions for Vertex Header Files (for Vertex users only) ....................... 25

7. Understanding Web Services Gateway ................................................................................ 27Understanding WSG Server ............................................................................................ 27Understanding WSG Developer ....................................................................................... 28Downloading JD Edwards EnterpriseOne 8.96 Web Services Gateway Developer ..................... 28

A. Working With Multiple Foundations ................................................................................. 29Understanding Encryption .............................................................................................. 31

Completing the Roll-back Procedures ....................................................................... 31Fulfilling the Pre-Installation Process ........................................................................ 31

Understanding Multiple Foundation Code on the Enterprise Server ......................................... 33Working With Service Packs on the Enterprise Server .................................................. 33

Creating a New Host Code Directory ................................................................ 33Editing the jde.ini File .................................................................................... 35

Understanding the PORTTEST ................................................................................ 36Running the PORTTEST ................................................................................ 36Starting the Services ...................................................................................... 36

Understanding Multiple Foundation Code on the Deployment Server ...................................... 38Installing Multiple Service Packs on the Deployment Server ......................................... 38Adding a New Machine Record for the New Service Pack ............................................ 39

Copyright © 2006, Oracle. All rights reserved. GA 4/28/2006 v

Modifying the Existing Machine Record to Remove Environments ................................. 41Working with Packages for Multiple Foundations ............................................................... 42Working with the Web Development Client ....................................................................... 48Editing the Microsoft Windows Development Client jde.ini File ............................................ 51Promoting Foundation Code ............................................................................................ 51

Installation Guide for Microsoft Windows

vi GA 4/28/2006 Copyright © 2006, Oracle. All rights reserved.

Chapter 1. Understanding the Tools Release InstallationThis document includes instructions for installing the JD Edwards EnterpriseOne Tools Release 8.96 on Enter-prise Servers running JD Edwards EnterpriseOne Tools Release 8.9 or later. In addition, this document includesother tasks that address specific functional areas, which may be optional, separately licensed, or both.

JD Edwards EnterpriseOne Tools Release 8.96 is downloadable by individually supported platforms. The band-width of your internet connection determines the length of time required for the download. Use Change Assistant,the Java "jar" command, or WinZip to extract the deliverable files.

Note

Tools Release 8.96 may be installed on base application release levels 8.9, 8.10, 8.11, and 8.12 as wellas applicable service packs on those releases.

You should always check the JD Edwards EnterpriseOne support web site called Customer Connectionin the section Updates and Critical Fixes for revisions to this guide subsequent to the initial release,which coincides with the General Availability of JD Edwards EnterpriseOne Tools Release 8.96. Thisdocument will only be republished in its entirety for the next major tools release of JD Edwards Enter-priseOne.

Accessing Minimum Technical RequirementsAccess the current Minimum Technical Requirement (MTR) listing from Customer Connection. You can accessthe MTRs through multiple entry points. This path and link are one example:

Navigation: Customer Connection > Implement, Optimize + Upgrade > Optimization Guide > Supported Plat-forms > EnterpriseOne

http://www.peoplesoft.com/corp/en/iou/platforms/enterpriseone.jsp

Copyright © 2006, Oracle. All rights reserved. GA 4/28/2006 1

http://www.peoplesoft.com/corp/en/iou/platforms/enterpriseone.jsp

2 This page intentionally left blank

Chapter 2. Installing Tools Release 8.96This chapter discusses:

• Installing the Deployment Server

• Installing the Windows-based Enterprise Server Host Code

Installing the Deployment ServerThis section discusses:

• Backing Up Your Existing System

• Downloading Tools Release 8.96 for the Client Platform

• Running the Install Manager

Backing Up Your Existing SystemThe Tools Release download replaces the System directory and its subdirectories on the deployment server.Therefore, before you begin you should make a backup of the existing directory structure.

On the deployment server, make a copy of these directories:

/System

/Systemcomp

/OneWorld Client Install


Downloading Tools Release 8.96 for the Client PlatformThis section contains the instructions for downloading and relocating the Installation Wizard for Tools Release8.96 for the Client Platform. You must download this code to a Windows-based Deployment Server.

As a potentially more streamlined installation alternative to the instructions presented in this guide, you may wantto use Change Assistant. Refer to the online instructions at this link:

http://maintenance.peoplesoft.com/softwaredownloads/SP/content/documents/ToolsRelease_8.96_readme.html

1. On Customer Connection, locate and download the Tools Release 8.96 for the Client Platform to your Win-dows-based Deployment Server.

It is recommended that you download the <filename>.par file to a Microsoft Windows temp directory.Do not save the executable anywhere within the JD Edwards installation directory structure.

2. Once the <filename>.par is downloaded onto your Deployment Server, extract the contents.

Note

WinZip can be used to extract the contents, although Change Assistant is the preferred method.

Running the Install ManagerTo run the Install Manager:

1. Run the Install Manager.exe program and click OK.

The JD Edwards EnterpriseOne Installation Manager screen is displayed.

2. On the Installation Manager screen, select Install: Tools Release Install.

The Deployment Server Setup is displayed.

3. Click Next to begin the package size calculation, which can run for several minutes.

The system calculates the required disk space by subtracting the disk space used by the current foundationcode from the space required for the new code. As a result, the calculated number may be small and maydisplay as a negative value in some cases.

The Install Manager detects and sets the default directory path to the existing JD Edwards EnterpriseOnehost code directory.

Chapter 2. Installing Tools Release 8.96

4 GA 4/28/2006 Copyright © 2006, Oracle. All rights reserved.


Installing the Windows-based Enterprise ServerHost Code

This section contains the instructions to use an installation wizard to install Tools Release 8.96 on your MicrosoftWindows-based Enterprise Server. This installation assumes that you are upgrading an existing installation of JDEdwards EnterpriseOne Tools Release.

This section discusses:

• Understanding the Enterprise Server Installation

• Downloading Tools Release 8.96

• Stopping Services

• Running the Installation Wizard

• Recovering from a Failed Install

• Working with Uninstallation

• Working with the Install Log File

• Working with the jdelog.properties File

Understanding the Enterprise Server InstallationThe Installation Wizard replaces the System directory and its subdirectories on the Enterprise Server and auto-mates backup and configuration tasks. Relative to previous releases, the Installation Wizard automates thesetasks:

Task Installation Wizard Automated Function

Back up existing System directory The Installation Wizard copies the existing contents of the Systemdirectory to a user-specified backup location with a user-specifiedname.

After the files are successfully copied, the Installation Wizard de-letes them from their original location. If any of the files in this dir-ectory are locked by Microsoft Windows Services for JD EdwardsEnterpriseOne or by any other Microsoft Windows application,they cannot be deleted by the Installation Wizard, which then indic-ates that the installation failed. After the files are unlocked and de-leted, the user can resume the Installation Wizard, which automat-ically resumes in a recovery mode with the previous user-specifiedlocations and names.

Install the System directory The Installation Wizard installs the new System directory in thesame directory in which it was previously installed.

Set file attributes The Installation Wizard sets the file attributes appropriately to readand execute.

Restore Resource directory The Installation Wizard restores the Resource directory from thebackup it made of the pre-existing installation.

Back up and restore existing jde.ini The Installation Wizard restores the jde.ini file from the backup



Task Installation Wizard Automated Function

file it made of the pre-existing installation.

Validate third-party DLLs If third-party DLLs are not detected, the Installation Wizard deliv-ers bundled DLLs.

If third-party DLLs are detected, the Installation Wizard verifiesand delivers the highest version.

Downloading Tools Release 8.96This section contains the instructions for downloading and relocating the Installation Wizard for Tools Release8.96.

As a potentially more streamlined installation alternative to the instructions presented in this guide, you may wantto use Change Assistant. Refer to the online instructions at this link:


1. On Customer Connection, locate and download the Tools Release 8.96 for the Microsoft Windows Intelplatform.

It is recommended that you download the <filename>.par file to a Microsoft Windows temp directory.Do not save the executable anywhere within the JD Edwards installation directory structure.

Note

WinZip can be used to extract the contents, although Change Assistant is the preferred method.

2. Once the <filename>.par is downloaded onto your Deployment Server, copy or FTP it to your JD Ed-wards EnterpriseOne Enterprise Server.

The target destination can be in the root or temp directory on any drive on the Enterprise Server.

3. On your Enterprise Server, unzip the contents of the <filename>.par file.

Warning

Do not execute the setup program that you unzipped until you first stop Services, as described inStopping Services.




Stopping ServicesYou must stop all currently-running Services on your JD Edwards EnterpriseOne Enterprise Server before begin-ning the installation of Tools Release 8.96.

On your JD Edwards EnterpriseOne enterprise server, you must first stop any currently-running JD Edwards En-terpriseOne Network Services by selecting:

Control Panel > Services > JDE Network Services > Stop

or

Control Panel > Services > PSFT Network Services > Stop

Warning

It is imperative that you stop the running JD Edwards EnterpriseOne Network Services before beginningthe installation of Tools Release 8.96. Failure to do so causes an installation failure and the InstallationWizard aborts. To recover, you must follow the procedures in Recovering from a Failed Install

Running the Installation WizardTo run the Installation Wizard, which you previously downloaded and placed on your JD Edwards EnterpriseOneEnterprise Server:

1. On your JD Edwards EnterpriseOne Enterprise Server, locate and launch the Installation Wizard executablewhich you obtained and located as described in Downloading Tools Release 8.96. The executable is named:

ETNT_setup.exe



2. On the Welcome screen, click Next to continue.

3. On the system to backup screen, the Installation Wizard detects your currently-existing JD Edwards Enter-priseOne Tools installation and displays that directory.

For example, if you were installing Tools Release 8.96 on a system that previously contained Tools Release8.95, a valid directory might be:

d:\JDEdwards\E812\DDP\system

Note

If the Installation Wizard cannot detect an existing installation of JD Edwards EnterpriseOne Tools,it means that it could not detect an existing version according to your registry settings. If you aresure that an installation exists on this machine, you can use the Browse button to locate and specifythe system to backup. You cannot proceed with the Tools Release 8.96 installation until a valid ex-isting directory is specified.

4. Click Next to continue.



5. On the backup options screen, complete these fields:

Select System Backup Location Specify the directory in which you want to create a backup dir-ectory of your existing installation. It is recommended that thisdirectory be a subdirectory of the existing installation.

For example, if your existing installation is named Tools Re-lease 8.95, a valid value might be:

d:\JDEdwards\E812\DDP

Enter a name for the backup system Specify a unique name for the directory to contain the backupcopy of the existing Tools installation. For example:

system_backup

Warning

If this directory already exists, the Installation Wizardpresents an error panel. You cannot proceed with theinstallation until you go back and enter a uniquename.




7. The Installation Wizard presents a panel to remind you that you must stop the any running JDE NetworkServices or PeopleSoft Network Services before proceeding. You should also ensure that no files in thespecified backup directory are locked by other applications. If you do not stop these Services or if any filesare locked, the backup fails. In such cases, you must follow specific recovery procedures as described in Re-covering from a Failed Install.


Note

Due to the potentially large amount of data contained in these directories, it may take a few minutesfor the backup operation to complete.



9. On the Summary Information panel, review your selections and, if correct, click Next to begin the installa-tion of Tools Release 8.96.



10. On the Summary Information panel that indicates the installation completed successfully, click Finish.



Recovering from a Failed InstallIf you did not stop the JDE or PSFT services before installing Tools Release 8.96, or if some other applicationhad locks on the files located in the directory which the Tools Release 8.96 Installation Wizard was trying toback up, this message is displayed:

To recover from such an installation failure, you must re-run the Tools Release 8.96 Installation Wizard.

1. When recovering, the Installation Wizard no longer prompts you for the system folder and the backup folderlocation. This is because the Installation Wizard reads a file to determine the values that you specified dur-ing the initial installation. During recovery the Installation Wizard re-uses the values specified in this file,which is written in the same directory in which the Installation Wizard was originally run:

etnt_config_install.txt

As illustrated below, when you re-run the Installation Wizard to recover from an installation failure, theWelcome screen contains text that indicates a recovery is required.



2. On the recovery welcome panel, click Next to continue.

Note

Unlike a normal installation, when the Installation Wizard detects a recovery situation it does notprompt you for the system location or the backup name. This is because it is reading the values inthe etnt_config_install.txt that the Installation Wizard created during the initial failedinstallation.



3. On the Summary Information panel, review your installation choices and click Next to begin the installationrecovery.

4. Click Next to begin the installation of Tools Release 8.96.



5. On the Summary Information panel that indicates the installation complete successfully, click Finish.

Working with UninstallationThere is no automated uninstallation of Tools Release 8.96.

Once the Installation Wizard has completed, the tool which created the Installation Wizard automatically createsan uninstallation file in the directory in which the Installation Wizard was originally run. However, in these cir-cumstances you cannot use that generated file to perform an automated uninstallation of Tools Release 8.96. Toconserve disk space, you can safely delete this unusable uninstallation executable:

_uninst

Working with the Install Log FileThe Installation Wizard creates a log file in the directory from which it was executed. The log file name is:

etnt_ismp_install.log

Additionally, the Installation Wizard creates another file, called etnt_config_install.txt, which is usedto maintain system information between successive installations. This file exists only if the previous run of theInstallation Wizard failed. If the installation was successful, it is automatically deleted by the Installation Wizard.



Working with the jdelog.properties FileWarning

Universal Naming Convention (UNC) notation (for example, \\file.log) is not supported for spe-cifying the log file location for any of the loggers in the jdelog.properties file.

The jdelog.properties is typically found at this location:

x:\<install path>\ddp\system\classes

You must verify that the jdelog.properties includes proper (non-UNC) path locations for these two logfiles:

JDEROOT.LOG

JAS.LOG

The syntax for specifying the path to your logs in your jdelog.properties file is:

x:\<install path>\ddp\log\jderoot.log

For example, a valid path might be:

D:\jdedwards\e812\ddp\log\jderoot.log

An exception message is logged to the System.err if the Microsoft Windows UNC notation is used for log-ging. That is, JD Edwards EnterpriseOne will not generate logs if Microsoft Windows UNC notation is used.

Additionally, if you use UNC notation to specify the location of the log files, your PORTTEST will fail and re-turn the following exception:

Calling DataDictionary Validation function,...java.lang.NullPointerException

at com.jdedwards.base.logging.JdeLog.configProperties(Unknown Source)at com.jdedwards.base.logging.JdeLog.configure(Unknown Source)at com.jdedwards.base.logging.JdeLog.<clinit>(Unknown Source)at com.peoplesoft.pt.e1.metadata.serializer.MDSerializerProxy.

<clinit>(Unknown Source)Data Dictionary Validation Succeed for "CO 00001"



Chapter 3. Verifying ODBC ConnectivityTools Release 8.96 uses ODBC connectivity exclusively. To verify connectivity, ensure that the following para-meters in the [DB SYSTEM SETTINGS] section of the JDE.INI file on your Enterprise Server are set as fol-lows:

[DB SYSTEM SETTINGS]Database=MACHINE_NAMEType=S

where the MACHINE_NAME is the machine name of the SQL Server machine, and which must be specified as up-per case, and

where Type=S specifies the ODBC connection, whereas previous versions of JD Edwards EnterpriseOne spe-cified Type=L for OLEDB connectivity.


Chapter 4. Working With the Client Update PackageThis section discusses:

• Understanding the Client Update Package

• Creating the Client Update Package

Understanding the Client Update PackageThe package build and assembly process includes many critical tasks that must be successfully completed to cor-rectly install packages. See JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for details onbuilding, assembling, and deploying packages. This guide lists most of these tasks and gives step-by-step instruc-tions for completing them.

This process deploys changes from Tools Release 8.96 to your client workstations. If this Tools Release has anenterprise server download, you must first upgrade the enterprise servers before you upgrade the workstations. Ifthe enterprise servers are not upgraded first, they may not be able to properly receive and process requests fromworkstations that are upgraded.

The package build and assembly process includes many critical tasks that must be successfully completed to cor-rectly install packages. See the JD Edwards EnterpriseOne Tools 8.96 Package Management Guide for details onbuilding, assembling, and deploying packages. This guide lists most of these tasks and gives step-by-step instruc-tions for completing them. Before you build a package, review these tasks to ensure you complete all the re-quired steps.

Note

You cannot use the Express option for either Package Assembly or Package Build.

For more details on the package build process, refer to Assembling Packages in the JD Edwards EnterpriseOneTools 8.96 Package Management Guide.


Creating the Client Update PackageTo create the client update package:

1. On the Foundation Component screen, click Default for the foundation path.

2. Click Next repeatedly to navigate through the remaining Package Assembly screens.

Note

Include only Foundation in the package. Do not include Helps, Objects, or Database.

3. After completing the Package Assembly, click Activate, and then click Define Build.

4. Select Compress Foundation.

5. After completing the Package Build Definition, click Activate and then Submit Build.

6. Deploy this package to all workstations.

Chapter 4. Working With the Client Update Package


Chapter 5. Working With Long Running Process IssuesThis section discusses:

• Understanding Long Running Process Issues

• Enabling Long Running Processes

Understanding Long Running Process IssuesIf you are upgrading to JD Edwards EnterpriseOne Tools Release 8.96 or installing Release 8.12 with the JD Ed-wards EnterpriseOne Tools Release 8.96, you must make modifications to settings in the jde.ini file on yourJD Edwards EnterpriseOne Enterprise Server. These settings are required by the single signon enhancement in JDEdwards EnterpriseOne to run long running processes like upgrades without timing out. You should implementthese settings after installing the Tools Release 8.96 and remove them after you have finished the upgrade pro-cess.

Warning

If you do not include these settings in your jde.ini, and your upgrade or install process is not com-pleted within 12 hours, you may see problems in upgrade or install process.

Note

The concepts for addressing long running processes does not include a discussion of multithreaded ker-nels within the JD Edwards EnterpriseOne code. Refer to the Red Paper entitled: Multithreaded Kernelson Customer Connection for additional details on this application-facing enhancement, which requires aminimum application release level of JD Edwards EnterpriseOne Applications Release 8.11 SP1.

http://www.peoplesoft.com/corp/en/doc_archive/red_paper/rp_e1tools_multithreaded_kernels.jsp

Customer Connection Navigation: Implement, Optimize, and Upgrade | Implementation Guide | Imple-mentation Documentation and Software | Red Paper Library | Multi-threaded Kernels


Enabling Long Running ProcessesTo enable long running processes:

1. Verify these settings in your jde.ini file on your the Deployment Server and the Enterprise Server:

[TRUSTED NODE]numTrustedNodes=1RegularLifeTime=5760ExtendedLifeTime=43200NodeName=_LOCALNODEMachineName=_LOCALNODE

Tip

You should comment out or remove these settings from jde.ini after the upgrade or install processcompletes successfully.

See Also

You can get more information on configuring single signon in the JD Edwards EnterpriseOne Tools 8.96 Serverand Workstation Administration Guide.

Note

If you sign in to JD Edwards EnterpriseOne without a security server, you can only run the businessfunctions and UBEs that are mapped to either the local machine or the enterprise server without the se-curity server.

Chapter 5. Working With Long Running Process Issues


Chapter 6. Rebuilding Business Functions for Vertex HeaderFiles (for Vertex users only)

This applies to customers who use the Vertex Quantum Payroll Tax and Vertex Sales Tax Q Series (formerlyQuantum for Sales and Use Tax) applications with JD Edwards EnterpriseOne.

Because Tools Release 8.96 includes the latest versions of the Vertex header files, you may need to rebuild spe-cific business functions for Vertex to function properly after you apply the Tools Release. Depending on how youhave these BSFNs mapped, you may need to do a server or client update package, or both. Then the librariesmust be recopied for the update to be successful.

These are the business functions that you may need to rebuild after applying Tools Release 8.96.

Business Function Description

B0700058 Establish connection to Vertex

B0000182 Initialize environment for vendor business functions

B0000183 Free environment for vendor business function

B7300004 Retrieve Quantum GeoCodes

B7300002 Validate Quantum GeoCodes

B7300012 Retrieve Quantum software information

X00TAX Calculate and edit tax amounts

For more information about using Vertex Quantum applications with ERP, see Configuring JD Edwards Enter-priseOne for Use with Vertex Quantum Tax Applications in the JD Edwards EnterpriseOne Applications Release8.12 Installation Guide or JD Edwards EnterpriseOne Applications Release 8.12 Upgrade Guide.

Note

Refer to the MTRs on Customer Connection to verify the supported versions of Vertex which vary ac-cording to platform.


Chapter 7. Understanding Web Services GatewayJD Edwards EnterpriseOne Web Services Gateway and Integration Points simplify integration coding and testingby providing higher level interfaces and business process level interfaces. They enable the execution of businessprocesses that span multiple applications, remove latency from key business processes through real-time applica-tion collaboration, and facilitate the extension of existing legacy applications as components of new solutions.

In order for the WSG OneWorld adapter to connect to the JD Edwards EnterpriseOne Enterprise Server and runproperly, the Java connector and kernel files must match or be compatible with the JD Edwards EnterpriseOneEnterprise Server version and WSG system. You also need a different jdeinterop.ini file and additionalfiles to connect to the JD Edwards EnterpriseOne Enterprise Server. See the Configuring the EnterpriseOne Ad-apter section of the Web Services Gateway Installation and Configuration Guide.

This section discusses the two components of WSG and includes these topics:

• Understanding WSG Server

• Understanding WSG Developer

• Downloading JD Edwards EnterpriseOne 8.96 Web Services Gateway Developer

Understanding WSG ServerWSG Server is the primary runtime engine for executing logic, enabling hosting, and executing the Integrationprocesses. It provides the infrastructure and the tools that model and automate business processes, integrate re-sources, monitor business processes, and manage the environment.

WSG Server 8.96 includes these features:

• WSG Server install has only the WSG Server components, including Integration Server and Foundation pack-ages.

• No development components are included with the server component.

• Components are installed in the root folder as /JDEdwards/WSG.

• Is a standalone installer.


Understanding WSG DeveloperWSG Developer is a graphical development tool for building, editing, and testing integration logic. It provides anIntegrated Development Environment in which to develop the logic and Integration objects that perform the workof an integration solution.

WSG Developer 8.96 includes these features:

• WSG Development components as well as WSG Server components.

• Is a part of the JD Edwards EnterpriseOne fat client, not a standalone installer.

• Only available on Microsoft Windows platforms.

• Components are installed in the JD Edwards EnterpriseOne Microsoft Windows client folder.

• Is added as part of the JD Edwards EnterpriseOne package build (Full/Update). JD Edwards EnterpriseOnedevelopment tools include WSG components as a feature for all JD Edwards EnterpriseOne Microsoft Win-dows client packages.

Downloading JD Edwards EnterpriseOne 8.96 WebServices Gateway Developer

This section contains the instructions for downloading and relocating the Installation Wizard for WSG Developer8.96.

1. On Customer Connection, locate and download WSG Developer 8.96 to your Deployment Server.

You should download the <filename>.par file to a Microsoft Windows temp directory. Do not save theexecutable anywhere within the JD Edwards EnterpriseOne directory structure.

Note

Winzip can be used to extract the contents, although you should use Change Assistant.

2. Extract the downloaded file to the OneWorld Client Install\Third Party\Web ServicesGateway directory on the Deployment Server.

3. See the JD Edwards EnterpriseOne 8.96 Web Services Gateway Installation and Setup Guide to set up theinstalled application.

Chapter 7. Understanding Web Services Gateway


Appendix A: Working With Multiple FoundationsAs a best practice, you should always set up multiple Tools Release foundations, including a test environment forapplying service pack fixes. This helps ensure that a stable environment exists before you promote fixes to yourproduction environment. You can also use this same principle and procedure to set up multiple foundations ofmajor Tools Release, such as Tools Release 8.96 and Tools Release 8.95.

The procedures described in this document enable customers to target specific environments when they install aservice pack. For example, customers can keep the production environment running on the existing foundationand apply the new service pack to all other environments. This configuration enables them to perform tests on thenew foundation code without impacting the production environment. When they complete the testing, they canthen apply the new service pack to production.

By completing the tasks below, you can configure your JD Edwards EnterpriseOne systems to handle manyfoundations on a single enterprise server. These tasks require you re-configure path codes and jde.ini files toset up multiple foundations, but once the initial tasks are completed, the new configuration requires very littlemaintenance.

Before you begin the installation, consider these factors:

• Once the Tools Release is installed on the Enterprise Servers, the security kernel stores passwords in the se-curity tables using the new encryption as user log on occurs. There is no configuration to disable usage ofnew encryption. Additionally, there is no conversion program to rollback user records to the old encryption,nor is there one for converting all user records to the new encryption. See Understanding Encryption for addi-tional details.

Note

You can restore a backup copy of the F98OWSEC and F98OWPU tables to reset the user data.

• The multiple foundation setup uses one security server process per port.

• If you have multiple Enterprise Servers at different Tools Release levels, make sure each of them is pointingto the correct security data sources.

• If an Enterprise Server running an older Tools Release accesses data encrypted using the new encryption, au-thentication will fail and the user will not be able to log on.

• If an Enterprise Server running the new Tools Release accesses data encrypted using the old encryption, itwill update the user records in Security tables to the new encryption.

• If the customer has multiple foundations or multiple Enterprise Servers at different Tools Release levels, adual maintenance of users and passwords is required.

• Change the jde.ini setting for SECURITY Data Source back to the SYSTEM Data Source value.

• Remove the F98OWSEC, F98OWPU and F9312 tables from Server Map Data Source.

• Before beginning installation of the Tools Release 8.96, check the associated readme.txt file for late-breaking information and requirements.

This appendix consists of the following tasks:


• Understanding Encryption

• Understanding Multiple Foundation Code on the Enterprise Server

• Understanding Multiple Foundation Code on the Deployment Server

• Understanding Multiple Foundation Code on the Deployment Server

• Working with the Web Development Client

• Editing the Microsoft Windows Development Client jde.ini File

• Promoting Foundation Code

Appendix A: Working With Multiple Foundations


Understanding EncryptionFor previous tools releases, the algorithm used to encrypt and decrypt JD Edwards EnterpriseOne passwords hasbeen compromised and has been posted to web. This enhancement addresses the vulnerability that exists whenstoring passwords in the database and the associated installation or migration issues. The solution updates thepasswords stored in the database to a higher encryption standard.

More details can be found in the Security Vulnerability Report under JD Edwards EnterpriseOne Password En-cryption Vulnerability (Security Vulnerability ID: 2004011901).

Warning

Release 8.9 Consideration. When applying the ESU available in SAR #6929072 to , you must performthe instructions in the Database Password Encryption section of this chapter concurrently to the steps ofapplying this Tools Release. Please read the Database Password Encryption section before performingthe update. Failure to perform the Database Password Encryption steps when applying the ESU andTools Release may prevent you from being able to log on to your database. This ESU is not requiredwhen applying to Release 8.11 or Release 8.12.

This section contains these topics:

• Completing the Roll-back Procedures

• Fulfilling the Pre-Installation Process

Completing the Roll-back ProceduresThe improved encryption is integral to all future Tools Releases and it cannot be disabled. If the customer decidesto rollback to previous Tools Release, please follow these steps:

1. Follow the installation instructions to rollback the Enterprise Server and client workstations.

2. Reset the user records in the F98OWSEC and F98OWPU tables in the System data source from the backupcopy.

3. Change the jde.ini setting for SECURITY Data Source back to the SYSTEM Data Source value.

4. Run PORTTEST on the Enterprise Server to make sure user can log on.

Fulfilling the Pre-Installation ProcessNote

Before starting the pre-installation process, make sure you have created a backup copy of theF98OWSEC and F98OWPU tables as identified in the ESU download.

To handle multiple foundations running different Tools Releases, you should create two data sources for securitytables. These steps detail that recommended procedure.

1. Configure the existing data source (such as current system data source) to point Enterprise Servers runningTools Releases older than Tools Release 8.96.



2. Configure your Tools Release 8.96 to point to a second copy of the F98OWSEC and F98OWPU tables thatreside in your Sever Map Data Source, such as SERVERNAME – B9 Server Map.

Note

If you are not using multiple foundations, your existing data source is sufficient. Setting these datasources will help avoid any data conflict due to overlap between new and old Enterprise Servers.

Perform these steps before you install the Tools Release, service pack, or ESU:

1. Log on to the Deployment Server into the DEP9 environment.

2. Go to OMW and perform a copy table of the F98OWSEC and F98OWPU tables to the existing Server MapData Source where your security kernel is running. For example, your Server Map data source might be:

SERVERNAME – B9 Server Map

3. Go to OMW and perform a copy table of the F9312 table to the existing Server Map Data Source. For ex-ample, your Server Map data source might be SERVERNAME – B9 SERVER MAP.

Note

The purpose of this copy table process to your server map is to create a secondary location that cansupport the new encryption

• See Also

Development Tools Guide for more information about using the Object Management Workbench and TableDesign Aid to copy tables.



Understanding Multiple Foundation Code on theEnterprise Server

To install multiple foundations, you must first install and configure new system code on the Enterprise Server.This chapter includes these topics:

• Working With Service Packs on the Enterprise Server

• Understanding the PORTTEST

Note

If your JD Edwards EnterpriseOne configuration includes multiple servers running JD Edwards Enter-priseOne host code (for example, additional application servers or data servers), then you will need toapply the procedures for installing multiple foundations to each server. For this type of configuration towork successfully:

• Make sure that the port settings for the [JDENET] section in the jde.ini match between all serv-ers running the same foundation.

• Ensure the new services are running on all servers.

• Run PORTTEST successfully on all servers for all foundation releases that you have installed.

Working With Service Packs on the Enterprise ServerThe installation procedure for a Service Pack is the same as that for installing a Tools Release. Refer to InstallingTools Release 8.96 in this guide.

This section discusses these topics:

• Creating a New Host Code Directory

• Editing the jde.ini File

Creating a New Host Code Directory

This section discusses how to create a new host code directory for an Enterprise Server running the MicrosoftWindows operating system.

1. On the Enterprise Server, navigate to drive and directory that contains the JD Edwards EnterpriseOne hostcode. For example:

cd z:\JDEdwards\ddp

where z is the drive on which the JD Edwards EnterpriseOne host code is installed.

2. Create a new directory for the service pack you want to test. For example, E812SPTEST or



E812_DVPSPY.

The new directory will be used to store both the new service pack and the path codes that will access the ser-vice pack.

3. From the \JDEdwards\ddp\E812 directory, select the path codes that you want to access the new ser-vice pack. Move the selected path codes into the newly created directory.

For example, if you wanted to test the new service pack with all environments except Production (PROD,PD), move the Development (DEV,DV), Pristine (PRIST, PS) and Prototype (CRP, PY) path codes.

Warning

Do not copy the path codes. Instead you should always move them. You should not associate morethan one service pack with an environment at the same time.

4. In the new directory, create the following subdirectories:

• log

• packages

• PrintQueue



Editing the jde.ini File

This section discusses how to make the appropriate changes to the jde.ini file on a Microsoft Windows sys-tem.

1. Navigate to the \system\bin32 directory under the new host code directory, and edit the jde.ini file.

2. Locate the [DEBUG] and [INSTALL] sections in the jde.ini file, and change the paths in each of theseentries to point to the new host code directory:

Note

Replace host_code_dir in the entries below with the name of the new host code directory.

[DEBUG]DebugFile=d:\JDEdwards\ddp\host_code_dir\log\jdedebug.logJobFile=d:\JDEdwards\ddp\host_code_dir\log\jde.logJDETSFile=d:\JDEdwards\ddp\host_code_dir\log\JDETS.log

[INSTALL]E812=d:\JDEdwards\ddp\host_code_dirStartServicePrefix=JDEdwards Update x.xx

where x.xx is the service pack number. For example, 8.96.

[BSFN BUILD]BuildArea=d:\JDEdwards\ddp\host_code_dir\packages

3. Locate the [JDENET] section, and find the port settings for serviceNameList and serviceName-Connect. For each entry, add 100 to the number. For example, if the settings are both 6013, change themto 6113.

[JDENET]serviceNameList=6113serviceNameConnect=6113



4. In the [JDEIPC] section, add 1000 to the startIPCKeyValue entry as shown below:

[JDEIPC]startIPCKeyValue=7000

Note

If the startIPCKeyValue value is commented out, delete the comment mark.

5. In the [SECURITY] section, either clear security, or edit DefaultEnvironment to reference a validenvironment that accesses the new service pack.

6. Replace all references to the production environment (for example, PD812) with a valid environment thatwill access the new service pack (for example, PY812).

Understanding the PORTTESTTo ensure that the new service pack is properly installed on the Enterprise Server, complete the following task torun PORTTEST on all environments accessing the new service pack.

Note

If Security Server is on, then JD Edwards EnterpriseOne services must be running before PORTTESTcan be run.

This section discusses how to

• Running the PORTTEST

• Starting the Services

Running the PORTTEST

This section discusses how to run PORTTEST on a Microsoft Windows Enterprise Server.

1. On the Enterprise Server, open a DOS command window and change to the drive that contains the JD Ed-wards EnterpriseOne host code.

2. Enter these commands:

cd \JDEdwards\ddp\host_code_dir\System\bin32

PORTTEST userid password environment

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

3. Repeat the PORTTEST command for each environment accessing the new service pack.

Starting the Services



This section discusses how to manage Services on a Microsoft Windows Enterprise Server.

1. On the Enterprise Server, open a DOS command window and change to the drive that contains the JD Ed-wards EnterpriseOne host code.

2. Enter the following commands:

cd \JDEdwards\ddp\host_code_dir\system\bin32

jdesnet -i

exit

3. From the Microsoft Windows Control Panel, open Services.

4. Select Tools Release Update x.xx E812 Network services.

5. Click Startup.

6. Select Manual.

7. Click This Account.

8. If your default printer is a local printer, enter a local user name and password. If your default printer is a net-work printer, enter a network user name and password.

9. Click OK.

10. Select Tools Release Update x.xx E812 Network Services, and click Start.



Understanding Multiple Foundation Code on theDeployment Server

This chapter discusses:

• Installing Multiple Service Packs on the Deployment Server

• Adding a New Machine Record for the New Service Pack

• Modifying the Existing Machine Record to Remove Environments

Installing Multiple Service Packs on the Deployment Server

1. Sign on to the Deployment server using the PSFT or JDE (as applicable) user ID.

2. Make sure that all JD Edwards EnterpriseOne processes (Solution Explorer) are not running.

3. On the Deployment server, navigate to this directory:

z:\JDEdwards\E812

where z: is the drive on which the JD Edwards EnterpriseOne host code is installed.

4. In the E812 directory, create a directory called

System_SP_Original

where SP_Original is the release number of the service pack currently installed. For example, Sys-tem_894_M1.

5. From the \JDEdwards\E812 directory, copy these directories to the new System directory (Sys-tem_release_number) that was just created. This will serve as backup/rollback location for the previ-ous release.

System

SystemComp

OneWorld Client Install

Note

If you get a warning message, it indicates files are locked. You need to ensure JD Edwards Enter-priseOne or any other application is not running and causing a lock on any file.

6. If the deployment server is directly connected to the Internet, run the installation using one of these twomethods to acquire the tools release :

a. Change Assistant

b. Directly from the Update Center

In either case it is recommended to save the downloaded executable to a temporary directory and run it later



from there.

7. When you run the downloaded executable, you will receive a dialog indicating that the files are extracting.

8. When the extraction is complete, the JD Edwards EnterpriseOne installation program automatically startsand the JD Edwards EnterpriseOne Installation Setup Screen is displayed. Click Next.

9. On Setup Type, click Finish.

The program installs the new System, SystemComp, and OneWorld Client Install files and dir-ectories onto the deployment server.

10. On Installation Complete, click OK.

11. In the E812 directory, create another new directory called System_SP_New where release_number is therelease number of the service pack being installed. For example, System_896_A1.

12. Move the newly installed System, SystemComp, and OneWorld Client Install files and direct-ories into the new directory:

\JDEdwards\E812\System SP_New

For example, \JDEdwards\E812\System_896_A1 .

13. Restore the original directories by copying the System, SystemComp, and OneWorld Client In-stall directories from System_SP_original to the base installation directoryx:\JDEdwards\E812.

14. Locate the jde.ini in this location:

\JDEdwards\E812\System_SP_New\OneWorld Client Install\Misc

15. Modify the above-located jde.ini to change the port to that on which you wish to run the multiple found-ation. For example, valid ports might be 6014, 6015, etc.

16. Modify the client_sp.inf and install.inf files in the \JDEdwards\E812\System_SP_Newdirectory to point to the multiple foundation system.

Adding a New Machine Record for the New Service Pack

1. On the Deployment Server, log on to the deployment environment.

2. From the Fast Path menu, run P9654A.

3. On Work with Locations and Machines, click Find and expand the location tree.

4. Click Enterprise Servers and then click Add.

5. On Enterprise Server Revisions, complete the following fields:

Machine Name Enter the name of your existing primary Enterprise Server.

Description Enter a description for the machine.

Release Enter E812.

Host Type Click the visual assist button and select the type of Enterprise Server.



Port Number This should match the port number previously set in the new service packjde.ini.

Database Type Click the visual assist button and select the type of database being used onthe Enterprise Server.

Installation Path Enter the installation directory path in which Release 8.12 is installed onthe Enterprise Server.

6. Click OK.

Note

For Oracle databases, the program prompts for a connect string. Enter or verify the connect stringand click OK.

7. On Work with Locations and Machines, click Find and expand the tree.

8. Expand the Enterprise Server, click the newly added machine and click Select.

9. On Enterprise Server Revisions, click the Environments form exit.

10. On Machine Environments Revision, add the environments from which you want to access with the new ser-vice pack. You can add the environments either by typing their names into the grid or by selecting them us-ing the visual assist.

11. Click OK twice to return to Work with Locations and Machines.



Modifying the Existing Machine Record to Remove Environ-ments

1. On the Deployment Server, log on to the deployment environment.

2. From the fast path menu, run P9654A.

3. On Work with Locations and Machines, click Find and expand the location tree.

4. Expand Enterprise Servers, click the initial Enterprise Server machine record and click Select.

5. On Enterprise Server Revisions form, click the Environments form exit.

6. Delete all the environments that you added in the previous section.

This should leave you with only those environments that you have defined to access the production servicepack. For example, PD812.

7. Click OK twice.



Working with Packages for Multiple FoundationsDeploying the new tools release is easily done using the Package Build application by using a non-default Found-ation. Use these steps to create and include a new foundation for the multi-foundation tools release.

1. Sign on to the Deployment Server using the PSFT or JDE (as applicable) user ID.

2. Sign on to EnterpriseOne using the PSFT or JDE (as applicable) user ID into the Deployment (DEPXXX)environment.

3. Launch the Package Assembly application from menu GH9083.

4. On Package Component Revisions, select the Multi-foundation Update Package and enter a valid value forthe Parent Package.



5. On Foundation Component Selection, search for and select the new update package you specified in the pre-vious screen.



6. On Foundation Item Revisions, complete these fields:

Item Value Description

Foundation Name SP_NewVersion Enter a unique name of the foundation.

For example, 896_A1.

Description SP New Version Enter a description corresponding to the new founda-tion name.

Service Pack Num-ber

SP New Number Enter an arbitrary SP number where the maximumstring value is four characters.

For example: 896A.

Release E1 Release Use visual assist to appropriately select the Enter-priseOne release level.

Platform Type 99 – Client Enter Client because the foundation is to be deployedto the web development client workstation.

Build Type 20 – Optimize You must select optimize as the build type.

Foundation BuildStatus

30 – Build is Avail-able

You must identify the package build as available.

Date Built Installed Date Enter the date the SP was installed.

Time of Build Time of Installation You can enter any time.

Typically you should enter the approximate time the



Item Value Description

installation was performed.

Foundation Ma-chine Key

Deployment ServerName

Enter the UNC name of the deployment server.

Foundation Path path Enter the relative path to the new system folder.

Be sure to include the front ‘\’ and the System direct-ory at the end. For example:

\E812\System_SP_New\System

7. Click OK to save the Foundation Item Revision information.

8. On Foundation Item Revisions, select the browse button.

9. On Foundation Component Selection, select the Multi-foundation Update Package by clicking the firstcolumn of the selected row.

Ensure that the checkmark displays in the first column of the selected row record.

10. Click Add to create a new foundation to be used.



11. On Package Components Revisions, verify that the Multi-foundation Update Package you added is dis-played in the Foundation field and click OK.



12. On Package Build Revisions, select the Compression Options tab and select your compression options.

13. Click End to complete the Package Assembly process.

14. Proceed to build and deploy the package.



Working with the Web Development ClientUse the procedure in this section to set up your Web Development Client.

1. On the GH9083 menu, launch the Package Build application.

2. Create an update package by selecting Package Assembly and then Add.

3. On the Feature Selection screen, select Add.

4. On Feature Based Deployment Director, click Next.



5. On Package Assembly, Feature Information, complete these fields:

Feature Type Enter a valid value for this featrure type.

Description Enter a description for the machine.

Feature Installation Op-tions

Select your feature installation options by checking the appropriate check-boxes.

Components Verify this checkbox is selected:

Additional Install Processes

6. Click Next.



7. On Package Assembly, Additional Install Processes, complete these fields:

Third Party Enter the name of your Web Development feature.

Description Enter a description for your Web Development feature.

Sequence Enter a valid sequence value for your Web Development feature.

ExecutableName

Enter a valid value for the executable name for your Web Development feature.

The default value is SETUP.EXE.

Source Path Enter a valid path value for your Web Development feature. For example:

\\DEP_SERVER_NAME\SHARE_NAME\System_SP_New\OneWorld One-World Client Install\ThirdParty\WebDevFeature

where DEP_SERVER_NAME is the name of your Deployment Server, and

where SHARE_NAME is the name of your share drive.

8. Click Save.

9. Click Next.

10. Continue with the rest of the package assembly; there is no need to select any objects.

11. Define the package and, when prompted, make sure to select:



Build Feature Inf

12. Submit the package, which creates the new feature .inf for Web Development.

The newly created feature .inf file is located in the package.inf directory.

Note

For any subsequent package builds for the non-default foundation for which you want to includewebdev feature, you can use the package that you created with this procedure.

Editing the Microsoft Windows Development Clientjde.ini File

Note

If you are using Snapshot, you do not need to manually edit the jde.ini file to manage multiple cli-ents for multiple foundations, as described in this procedure.

This section describes editing the jde.ini file for a Microsoft Windows Development Client machine runningthe Microsoft Windows operating system.

In order for the Release 8.12 clients to access the new service pack, you must edit the jde.ini file on each cli-ent to point to the new directory.

Complete the following task on all Release 8.12 clients that have path codes that will access the new servicepack.

Note

You will be unable to access multiple service packs with a single client. To access multiple servicepacks, you will need to install a different client for each service pack. This will require using the Snap-shot application to save each client before installing the next one.

1. On the Release 8.12 workstation, open Microsoft Windows Explorer, and navigate to your Microsoft Win-dows directory. For example:

cd c:\WINNT

2. Open the jde.ini file.

3. Locate the [JDENET] section, and edit the port settings for serviceNameListen and service-NameConnect. Change these entries to match those of the server jde.ini file for the new service pack.

[JDENET]serviceNameList=portNumberserviceNameConnect=portNumber

where portNumber is the same port number you entered in the jde.ini file on the Enterprise Server.



Promoting Foundation CodeThis section discusses how to promote foundation code into the production environment when using a MicrosoftWindows-based Enterprise Server.

1. On the Enterprise Server, stop the Release 8.12 services for the following environments:

• The environment that you want to promote to production

• The production environment

2. Navigate to this directory:

z:\JDEdwards\ddp\E812

3. Create a directory called System Backup, and move the System directory into the System Backupdirectory.

4. Navigate to this directory:

z:\JDEdwards\ddp\foundation_code_dir

5. Copy the System directory to this directory:

z:\JDEdwards\ddp\E812

6. Navigate to this directory and copy the jde.ini file.

z:\JDEdwards\ddp\E812\System Backup\System\bin32

7. Paste the jde.ini file into this directory:

z:\JDEdwards\ddp\E812\System\bin32

The program asks if you want to replace the existing jde.ini file. Click OK to indicate you want to replacethe existing jde.ini file.

8. Start the JD Edwards EnterpriseOne services.

9. On the Deployment Server, create a System Backup subdirectory under the JD Edwards EnterpriseOnehost code directory. For example

z:\JDEdwards\E812\System Backup

10. Copy the System and SystemComp directories into the System Backup directory.

11. Navigate to the directory containing the system code being promoted. For example:

z:\JDEdwards\System x.xx

where x.xx is the release number of the service pack

12. Move the System and SystemComp directories to this directory:

z:\JDEdwards\E812

13. Using P9654A, edit the machine records to include the environments that you want to access the promotedservice pack.



JD Edwards EnterpriseOne Tools Release 8.96 …...prise Servers running JD Edwards EnterpriseOne...

Documents

Transcript of JD Edwards EnterpriseOne Tools Release 8.96 …...prise Servers running JD Edwards EnterpriseOne...