Professional Documents
Culture Documents
9 0 With 8 98 4 Standalone Installation Using OUI With OEE Rev2
9 0 With 8 98 4 Standalone Installation Using OUI With OEE Rev2
9 0 With 8 98 4 Standalone Installation Using OUI With OEE Rev2
98
Installation Guide
May 2011
Copyright Notice
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and
are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may
not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part,
in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
Subject to patent protection under one or more of the following U.S. patents: 5,781,908; 5,828,376; 5,950,010; 5,960,204;
5,987,497; 5,995,972; 5,987,497; and 6,223,345. Other patents pending.
Warranty Disclaimer
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors,
please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, the following notice is applicable:
Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers
are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition
Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and
adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to
the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19,
Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA
94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended
for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this
software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other
measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software in dangerous applications.
This software and documentation may provide access to or information on content, products and services from third parties.
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third
party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages
incurred due to your access to or use of third party content, products or services.
Contains GNU libgmp library; Copyright 1991 Free Software Foundation, Inc. This library is free software which can be
modified and redistributed under the terms of the GNU Library General Public License.
Includes Adobe® PDF Library, Copyright 1993-2001 Adobe Systems, Inc. and DL Interface, Copyright 1999-2008 Datalogics
Inc. All rights reserved. Adobe® is a trademark of Adobe Systems Incorporated.
Portions of this program contain information proprietary to Microsoft Corporation. Copyright 1985-1999 Microsoft Corporation.
Portions of this program contain information proprietary to Tenberry Software, Inc. Copyright 1992-1995 Tenberry Software,
Inc.
Portions of this program contain information proprietary to Premia Corporation. Copyright 1993 Premia Corporation.
This product includes code licensed from RSA Data Security. All rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes software written by Tim Hudson (tjh@cryptsoft.com). All rights reserved.
This product includes the Sentry Spelling-Checker Engine, Copyright 1993 Wintertree Software Inc. All rights reserved.
Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims
any and all liability or damages resulting from use of said software or documentation. The following open source software may
be used in Oracle's JD Edwards EnterpriseOne products and the following disclaimers are provided.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 1999-
2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED “AS IS’’ AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Ta ble of Contents
This document explains how to install and run the JD Edwards EnterpriseOne 9.0/8.98
Standalone Client using the Oracle Universal Installer (OUI), hereafter referred to as
Standalone Client. This version of the Standalone Client using OUI supports only the
Oracle Enterprise Edition (OEE) as the local database. This version that uses OUI does
not support Microsoft SQL Server 2005 Express Edition (SSE).
Install the local database if it is not already installed and the Standalone
Client.
Analyze and correct any problems that arise during the installation.
Run the web client as part of the Standalone Client and troubleshoot any
startup errors.
Refer to the Glossary in this document for definitions of terms and acronyms.
The MTRs are contained in an attachment within document 705409.1 that is entitled JDE E1
Tools 8.9x Client.
The computer on which you are installing the Standalone Client needs to meet the MTRs of
all types of clients described in this section. Therefore you should review and ascertain that
your machine meets the requirements listed in these topics of the client MTR document:
1. Be sure the MTRs are met before starting the Standalone Client installation.
2. JDK 1.5 is supplied with the installation. Do not replace this with another version
of the JDK because JDK 1.6 and higher have not been validated with
EnterpriseOne Tools Release 8.98. Also, do not replace this JDK with a 64-bit
version because EnterpriseOne is a 32-bit program which requires a 32-bit version
of the JDK even when running on a 64-bit version of Microsoft Windows.
3. Microsoft Visual Studio is not required unless you are building business
functions. The installation of the Standalone Client installs the Microsoft libraries
that are necessary to run EnterpriseOne, but if you plan to build business
functions, you will need the compiler and additional libraries that Visual Studio
provides.
deinstall the Standalone Client, refer to the section of this guide entitled:
Deinstalling the Standalone Client.
5. Standalone Client does not require Software Protection Codes (SPCs) to run so
you will not need to perform the steps for applying SPCs that previous
EnterpriseOne releases required.
6. This version of the Standalone Client using OUI supports only the Oracle
Enterprise Edition (OEE) as the local database.
This version of Standalone Client using OUI does not support Microsoft SQL
Server 2005 Express Edition (SSE).
7. This release of the Standalone Client contains Oracle Enterprise Edition (OEE)
11gR2. If you previously had installed OEE 11gR2 as the local database and you
are reinstalling the Standalone Client, you do not have to deinstall the database
first. However, if you previously had installed OEE 10g or you need to reinstall
the 11gR2 database for some reason, follow the instructions in the section of this
guide entitled: Deinstalling the OEE Database (optional).
8. If you need to install the OEE database and the Microsoft Windows environment
variable ORACLE_HOME exists, the Standalone Client installer will delete it
during the installation.
Depending on several factors, you can install the Standalone Client using one of these
methods:
Perform these steps if you are copying the installation DVD to a hard drive, either locally
or to a network location. You may want to do this so additional users can install from a
single location.
1. On the hard drive onto which you want to copy the installation DVD, create a
temporary installation directory. The recommended name is:
\Standalone_9.00
2. Copy the contents of the installation DVD to the temporary installation directory
you created in Step 1 above.
Complete these instructions if you are downloading the Standalone Client software from
the Oracle E-Delivery web site:
http://edelivery.oracle.com
If you are installing the Standalone Client from DVD or a network share location,
and therefore have performed the steps in the preceding section of this chapter,
you can skip this section and proceed to Chapter 4. Installing the Standalone
Client.
2. Open the E-Delivery web site, continue through the screens, and select these
values on the Media Pack Search screen:
Select a Product Pack: JD Edwards EnterpriseOne
Platform: Microsoft Windows (32 bit)
Note: Even if you are installed on a 64-bit version of the Windows 7
operating system, (that is, Windows 7 x64), for the above selection
you must choose Microsoft Windows (32 bit) as the platform.
3. Click the Go button to display the results.
4. In the results grid, click the radio button next to the proper description.
For English, select this:
5. Click Continue.
Note: Language. If the description of the download item does not contain the
word Language, the language of the Standalone Client is English.
If the description of the download item contains the word Language, the
language of the Standalone Client includes both English and other supported
languages.
7. Click the Download button next to the item that you wish to download.
Note: Multiple Part Downloads. Due to the maximum file size restrictions for
downloads on E-Delivery, you will need to download multiple parts for a
selected part number.
8. Save the .zip file to the temporary installation directory you created in Step 1.
If you followed the recommendation, the directory is named
\Standalone_9.00
9. After you finish downloading the first item, labeled (Part 1 of 2), select the
corresponding row for the second item labeled (Part 2 of 2) and click the
Download button.
10. Again, save the .zip file to the same directory where you saved the previous
.zip file.
11. After you finish downloading all parts of your item, use your favorite unzip
program to extract the contents of the downloaded files to the temporary
installation directory that you created in Step 1. If you followed the
recommendation, the directory is named:
\Standalone_9.00
Note: Extract Option. When extracting, be sure to click in the checkbox to enable
this option:
Note: JDBC Drivers. All files necessary to perform the installation, including
JDBC drivers, now reside in the temporary installation directory. If you
followed the recommendation, the directory is named:
Standalone_9.00
This example screen illustrates the directory structure when the .zip files are
extracted into the recommended temporary installation directory
(Standalone_9.00):
You can install the Standalone Client directly from a DVD or from a copy of the DVD or
a download from E-Delivery. Refer to Chapter 3. Installation Methods for additional
details.
Notes: Assumptions. The instructions in this chapter assume that you are installing
directly from the DVD. In this case, the installation program will be located
in the root directory of the DVD.
If you are installing from a copy of the DVD or a download from E-Delivery,
the installation program will be in the directory into which you copied the
DVD or into which you expanded the downloaded files. If you followed the
recommendation, this directory is:
C:\Standalone_9.00
Installing the Standalone Client involves first installing a local database and then
installing the actual E1 Standalone Client. Follow the instructions in the next two
sections to install the database and client.
When you install the OEE database engine, two Oracle Homes will be created:
When you install the E1 Standalone Client, you specify an Oracle Home and
name for that installation as well. For example, you may enter
C:\JDEdwards\E900 as the Oracle Home path and
JDE_Standalone_Home as the Oracle Home name.
Following the above examples, you would now have three Oracle Homes:
Tip: It is recommended that you use the above names when installing OEE
and the E1 Standalone Client.
This release of the Standalone Client contains Oracle Enterprise Edition (OEE) 11gR2. If
you previously had installed OEE 11gR2 as the local database and you are reinstalling the
Standalone Client, you do not have to deinstall the database first. However, if you
previously had installed OEE 10g or you need to reinstall the 11gR2 database for some
reason, follow the instructions in the section of this guide entitled: Deinstalling the OEE
Database (optional).
Note: Vista and Greater on Microsoft Windows. When running the installation program
on Vista and higher versions of Microsoft Windows, you must right click on the
executable and select Run as Administrator.
4. On Oracle License Agreement, if you accept the license click the appropriate
button. You cannot continue with the installation unless you accept the license
agreement.
7. On Specify Home Details, you must specify an Oracle Home path and a name
for that path.
For more information about Oracle Homes and recommendations for naming
the Oracle Homes for the E1 Standalone Client, see the section in this guide
entitled: Understanding Destination Paths.
On Specify Home Details, enter a path and name for the Parent Oracle Home
path under which the local OEE database will be installed.
In summary, you will have two Oracle Homes for the database:
The Parent Oracle Home is the path that you specify on this screen.
Likewise its name will be the name that you enter on this screen. For
example:
o Path: C:\JDEdwards
o Name: JDE_Local_DB_Home
o Path: C:\JDEdwards\E1Local
o Name: E1Local
11. When the installation of the database finishes, you will see the End of
Installation screen.
Warning: Examine the Installer Logs. Even though the screen says that
the installation was successful, you should perform a quick determination
that all the database installation steps were successful before clicking Exit.
Follow these steps:
a. From Windows’ Control Panel, run Administrative Tools / Services.
c. If either one of these is missing, there was a problem in completing all the
installation and configuration steps. Examine the logs specified in the
table OEE Installer Logs. You will probably need to deinstall the database
engine using the steps in the section Deinstalling the OEE Database,
reboot, and then reinstall the OEE database.
13. You must reboot your machine before continuing with the installation of the
E1 client as described in the next task in this guide.
Note: Vista and Greater on Microsoft Windows. When running the installation program
on Vista and higher versions of Microsoft Windows, you must right click on the
executable and select Run as Administrator.
4. On Oracle License Agreement, if you accept the license click the appropriate
button. You cannot continue with the installation unless you accept the license
agreement.
7. On Select Installation Type, enable the appropriate radio button for these
installation types:
Development
Production
Custom
After several screens, you will be presented a list of components (shown in the
next table) that you will select to install or reinstall.
E1 Local Data E1 non-system data that will be stored in the Yes Yes
local database. This includes
Training data
Control data
Data Dictionary
Object Librarian
Versions
Features Features defined for the E1 package. Yes Yes
8. After you have selected an installation type, click the Next button.
9. On Specify Home Details, you must specify an Oracle Home path and a
name for that path.
The path you enter here is for the Oracle Home path where the E1 Standalone
Client will be installed.
Warning: Do not specify the same Oracle Home name or path into which you installed
the local database; however, you can specify a path that is a subdirectory of the
database’s Parent Oracle Home.
11. On Package Selection, only one package is shown for the Standalone Client.
That package is called DEMO and is highlighted by default.
Notes: The E1 Standalone Client and E1 Web Development (Fat) Clients will both
use this OUI installer. The following checks were added to the installer to
handle the general cases whereby local databases in addition to OEE and
multiple E1 packages will be available for the Development Client installer
to install.
Available disk space. After you click Next, the installer compares the
selected package size with the amount of free disk space of the destination
path. If not enough free disk space exists, the installer displays a warning.
The size of the selected package applies to a new installation of all
components of the package. If you are sure that enough disk space really
exists (for example, you are reinstalling one or more components), you can
ignore the warning and continue with the installation; otherwise, free up the
necessary disk space or use the Back button to back up to the Specify
Home Details screen to select a different drive onto which the Standalone
Client will be installed. You can then continue with the installation.
Available database. In addition, until you select the package to install, the
installer has not had enough information to determine which database engine
is required. If you have not installed the OEE database engine prior to
attempting to install the Standalone Client and you select a package that
requires OEE, you will receive an error message at this time. If that occurs,
use the Back buttons to back up to Select a Product to Install and select
the option to install the Database Engine. When that installation completes,
you will need to reboot your machine and then rerun the Standalone Client
installer.
13. On Summary, verify that what is to be installed is correct and click Install.
15. When the installation of the E1 client finishes, you will see the
End of Installation screen.
Warning: Examine the Installer Logs. Regardless of whether you get the above message
indicating the Standalone Client installer succeeded, you should always check
the logs before you attempt to run the Standalone Client. Examine the logs
specified in the table Standalone Client Installer Logs.
After installing the Standalone Client, you must perform the following post installation
task:
Updating the tnsnames.ora file
The name of the OEE database that is installed with the Standalone Client is E1Local. It
has its own tnsnames.ora file, which is used to define how a connection to the
database is made. For example, this tnsnames.ora defines the port number and SID
for E1Local.
If you have other Oracle databases installed on this machine, or if you access remote
Oracle databases, you will have other tnsnames.ora files to define those connection
parameters.
By design, the tnsnames.ora for the last installed Oracle database is used by any
software running on your local machine to access all the Oracle databases. Because the
E1Local database is normally installed during the installation of the Standalone Client, it
is likely that will be the last database installed. Therefore, in order to regain connectivity
to other Oracle databases, you must update the tnsnames.ora file used by E1Local
with the database connection information that is stored in the other tnsnames.ora
files on your machine.
C:\JDEdwards\E1Local\NETWORK\ADMIN\tnsnames.ora
Note: OEE Install Location. OEE for the Standalone Client is always installed in
a subdirectory called E1Local under the path that you specified when
installing OEE.
2. Edit the tnsnames.ora files on your machine for any other Oracle databases
that you may access (whether remote or local databases). These tnsnames.ora
files will be located in the NETWORK\ADMIN path under the installation paths of
the Oracle database clients. For example:
C:\Apps\db\oracle102\NETWORK\ADMIN\tnsnames.ora
3. Copy the contents of these other tnsnames.ora files and append them to the
version of the file that is being used by the E1Local database (for example,
C:\JDEdwards\E1Local\NETWORK\ADMIN\tnsnames.ora).
Note: Vista and Greater on Microsoft Windows. When running the installation program
on Vista and higher versions of Microsoft Windows, you must right click on the
shortcut or executable and select Run as Administrator.
Optionally, you can double click the program activConsole.exe from this
path:
C:\JDEdwards\E900\system\bin32
3. If you have installed any Oracle Business Accelerators (OBA), click the Options
button to display the environment and role fields. In this case, you should enter
the role: DEMOROLE and take the default environment: DEMO900.
Note: Startup Time. You should allow sufficient startup time for the JD
Edwards EnterpriseOne background process jdenet_n.exe,
which acts as the security server on the Standalone Client. Ensure
this program has completed its initialization steps before you click
OK on the logon screen.
Genera l
If you have any trouble running the Standalone Client, turn on additional logging and
rerun the Standalone Client.
3. If the column titled PID is not displayed, use this procedure to turn it on:
c. Click OK.
6. In the [DEBUG] section, change the value of the Output key to FILE, as shown
below:
[DEBUG]
Output=FILE
7. Note the names of the log files specified for the JobFile and DebugFile keys in the
Debug section so you can locate them when needed.
Problem:
You get an error (either in a pop-up window or in the logs) indicating that the Standalone
Client could not connect to the security server.
Resolution:
1. Try again to sign on. The security server (process jdenet_n.exe) may have
simply been slow in starting causing the activConsole.exe to time out.
2. By default, the Standalone Client attempts to start the web client at the same time
that activConsole.exe starts. This could cause the security server (process
jdenet_n.exe) to take too long to start causing the activConsole.exe to
time out.
You can specify that the web client should start only when you attempt to bring
up the Web menu (described in the next section entitled: Still Cannot Connect to
the Security Server). To do so, follow these steps:
a. Run the Microsoft Windows Task Manager.
[LOCALWEB]
StartAppServer=ONDEMAND
e. Rerun activConsole.exe.
Problem:
After doing the above, you again get an error (either in a pop-up window or in the logs)
indicating that the Standalone Client could not connect to the security server.
Resolution:
Verify that the local database service(s) is running using this procedure:
OracleServiceE1LOCAL
OracleE1LocalTNSListener
If not, for each stopped service click Action > Start in the menu.
c. Rerun activConsole.exe .
The Standalone Client should automatically sign you into the Standalone Web
Client.
Genera l
If you have any trouble running the Web Client, look at the Web Client logs.
1. In Microsoft Windows Explorer, drill down to the location of the Web Client
logs. By default, the logs are located in this directory:
C:\JDEdwards\E900\system\OC4J\j2ee\home\log
2. Examine any logs that were recently created, especially logs that are prefixed with
either:
jas
jde
3. If you do not find any logs with the above prefixes, the logs may be in another
folder. Use this procedure to determine the location of those logs:
a. In Microsoft Windows Explorer, drill down to this directory:
C:\JDEdwards\E900\system\OC4J\j2ee\home\applications\
webclient.ear\webclient\WEB-INF\classes
Search through the file and note the value of the FILE key. In each of the
sections that describe a log file there are section headers that are enclosed in
square brackets ([ and ]). If a section header or the FILE key is commented
out with a pound sign (#), you can ignore that section. For example:
#[E1LOG]
or
# File=log\jderoot.log
The value of the FILE key in each section is the name and path of a log file
associated with that section. For example:
File=log\jderoot.log
The actual file name will be the value of the FILE key with an underscore and
the current date appended. For example:
jderoot_090109.log
If a log file name and path starts with a drive letter followed by a colon and
slash, the path is absolute. This means that the log file will be located on the
specified drive in the specified directory. For example:
File=c:\standalone_logs\jas_090109.log
If a log file name and path starts with a slash, the path is also absolute. This
means that the log file will be located on the drive on which the E1
Standalone Client is installed and in the specified directory. For example:
File=\log\jderoot_090109.log
If a log file name and path start with neither a drive letter nor a backslash, the
path is relative to this folder:
C:\JDEDwards\E900\system\OC4J\j2ee\home
For example, if the value for the FILE key is log\jas.log and the
Standalone Client is installed in C:\JDEdwards\E900, the log file is
written to:
C:\JDEdwards\E900\system\OC4J\j2ee\home\log
Problem:
After starting the Standalone Web Client from the Standalone Client, you get an error on
the screen indicating that the Web Client could not connect to the security server.
Resolution:
Verify that the local database services are running using this procedure:
OracleServiceE1LOCAL
OracleE1LocalTNSListener
If not, for each stopped service click Action > Start in the menu.
Notes: Because you are replacing files that the Standalone Client installer uses, you
will need to either copy the installer from a DVD to a hard drive or
download the installer from E-Delivery. Follow the instructions in the
section Copying the Installation DVD or Downloading from the Oracle E-
Delivery Website.
For the following instructions, it is assumed that the folder where the
Standalone Client installer resides is:
<drive>:\Standalone_9.00
activConsole.exe
jdenet_n.exe
If either or both of these processes are running, either wait for them to finish or
kill them via Task Manager.
3. Because the entire system directory is to be replaced, you should backup your
existing system directory in your installed Standalone Client. To do so, rename
the directory. For example:
4. Download the appropriate Tools Release WINCLIENT from the Update Center.
The download is transferred to your machine as a .par file. This file may be
opened with the standard WinZip program.
Warning: Improper Unzipping. You should not open the .par file by
double clicking on it. It is a self-extracting file that is normally
installed on a deployment server. If you double-click on it, it
will assume that your workstation is a deployment server and
attempt to install it in an incompatible manner.
6. Inside the .par file are multiple .CAB files in the Disk1\System folder. The
files are called SystemX.CAB where X is either nonexistent or a whole number.
Extract these .CAB files into the “system” folder where you placed the temporary
installation directory (for example, \Standalone_9.00).
7. Launch InstallManager.exe from the root folder of the copy of the DVD
(for example, \Standalone_9.00\InstallManager.exe).
Note: Vista and Greater on Microsoft Windows. When running the installation program
on Vista and higher versions of Microsoft Windows, you must right click on the
executable and select Run as Administrator.
10. On Oracle License Agreement, if you accept the license click the appropriate
button. You cannot continue with the installation unless you accept the license
agreement.
11. On Select a Product to Install, ensure that the radio button for
EnterpriseOne Client is turned on.
15. On Specify Home Details, from the drop-down lists next to either the Name
or Path fields, select the Oracle Home directory where you installed the
E1 client.
17. On Available Product Components, turn off all checkboxes except those
next to Foundation.
19. On Package Selection, only one package is shown for the Standalone Client.
That package is called DEMO and is highlighted by default.
23. When the installation of the E1 client finishes, you will see the
End of Installation screen.
25. Clear the cache in your browser using these browser-dependent procedures:
Mozilla Firefox
a. Go to Tools > Options.
b. On the Network tab and in the Cache section, click the Clear Now button.
26. Launch EnterpriseOne by following the instructions in the section of this guide
entitled: Starting the Standalone Client.
activConsole.exe
jdenet_n.exe
If either or both of these processes are running, either wait for them to finish or
kill them via Task Manager.
Deinstall Products…
5. Put a check mark next to the item with the Oracle Home name that you gave to
your E1 client.
8. When the deinstall is complete, exit from the Oracle Universal Installer.
<E1Local_Oracle_Home >\deinstall\deinstall.bat
c:\JDEdwards\E1Local
Note: The OEE installation program should have created some artifact files
for us by the deinstaller. These files provide answers to prompts that
the database deinstaller would normally prompt a user. If for some
reason, those files were not created during OEE installation, or
otherwise cannot be located by the deinstaller, you are prompted for
information when you perform the deinstall. In most cases, you can
take the default values. These are the prompts:
Upon completion of steps a-i, you may get some errors indicating that not all of
the directories could be deleted. This will be addressed as a later step in the
section entitled: To complete the database deinstallation. At this point you can
continue in sequence with the current section.
3. The above steps are used to remove the OEE 11gR2 database engine. To remove
the Parent Oracle Home, continue with the next. For more information regarding
the Parent Oracle Home, refer to Understanding Destination Paths.
8. When the deinstall is complete, exit from the Oracle Universal Installer.
9. Perform the steps in the section below entitled: To complete the database
deinstallation.
1. Go to Start > All Programs > Oracle – E1Local > Oracle Installation Products >
Universal Installer.
Deinstall Products…
3. Put a check mark next to the Oracle Homes for these items:
JDE_Local_DB_Home
This is the Oracle Home Name that you provided when installing OEE. If you
are not sure which name you used, expand the tree for each listed Oracle
Home by clicking on the plus sign next to each Oracle Home Name. The one
that you need to deinstall is titled Database Engine followed by a version
number. Place a check mark next to the parent of the line containing the
Database Engine.
E1Local
This is the Oracle Home Name of the cloned copy of the database.
5. When the deinstall is complete, exit from the Oracle Universal Installer.
6. Use this procedure to verify that the proper keys were removed from the registry:
a. Go to Start > Run….
b. In the Open field, enter this command to start the Registry Editor:
regedit
iii. Choose a location and provide a filename for the registry backup.
HKEY_LOCAL_MACHINE\SOFTWARE\Oracle
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
C:\JDEdwards\E1Local
Note: No Files Can Exist In This Folder. It is very important that no files
exist in this folder when you next attempt to install the OEE database.
If any files do exist, the OEE installation will probably fail.
k. If you cannot delete the folder because a file in that folder is locked, follow
these steps:
i. Determine which file is locked and which process has the lock on the file.
A freeware program called Process Explorer can be helpful in
determining this information. You can obtain a free copy of Process
Explorer from this web site:
www.sysinternals.com
ii. Either kill the locking process with Process Explorer or Microsoft
Windows Task Manager or, if the process was started as a Microsoft
Windows service, change the Startup Type to Manual and reboot the
computer again.
iii. Try again to delete the folder.
7. Perform the steps in the section below entitled: To complete the database
deinstallation.
Use this procedure to verify that the proper keys were removed from the registry:
1. Go to Start > Run….
2. In the Open field, enter this command to start the Registry Editor:
regedit
d. Click Save.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
C:\JDEdwards\E1Local
Note: No Files Can Exist In This Folder. It is very important that no files
exist in this folder when you next attempt to install the OEE database.
If any files do exist, the OEE installation will probably fail.
11. If you cannot delete the folder because a file in that folder is locked, follow
these steps:
a. Determine which file is locked and which process has the lock on the file.
A freeware program called Process Explorer can be helpful in
determining this information. You can obtain a free copy of Process
Explorer from this web site:
www.sysinternals.com
b. Either kill the locking process with Process Explorer or Microsoft
Windows Task Manager or, if the process was started as a Microsoft
Windows service, change the Startup Type to Manual and reboot the
computer again.
c. Try again to delete the folder.
12. Perform the steps in the section below entitled: To complete the database
deinstallation.
This glossary provides descriptions of terms and acronyms used in this document.
Da ta ba se driver
A set of code used to connect to a database.
E-Delivery
An Oracle web site from which applications can be downloaded.
Insta ll Ma na ger
The JD Edwards EnterpriseOne program that starts the Standalone Client installer. The
actual program name is:
InstallManager.exe
JDBC driver
A database driver that is used by Java programs to connect to a database.
Loca l da ta ba se
A database that resides on the client workstation on which the Standalone Client is
installed.
Root folder
The base-level folder of a computer drive whether that drive is a hard drive or a DVD. It
is designated by the drive letter, a colon, and a backslash or, if the drive letter can be
assumed, simply by a single backslash.
Sna pshot
A JD Edwards EnterpriseOne tool used to save and restore installations of JD Edwards
EnterpriseOne products such as standalone clients, development clients, and deployment
servers.
Spec da ta ba se
Tools component
The JD Edwards EnterpriseOne component of the Standalone Client that provides mid-
level functionality to the EnterpriseOne applications. Also known as JD Edwards
EnterpriseOne Tools Release or “system” code.