This chapter discusses:
Section 3.2, "Local Oracle Enterprise Edition (OEE) Considerations"
Section 3.3, "Obtaining and Preparing the Deployment Server Install Image"
Section 3.4, "Working with JDBC Drivers on the Deployment Server"
Section 3.6, "Working with the Development Client Installation"
Section 3.7, "Adding Additional Environments (Rerunning the Deployment Server Installer)"
Section 3.9, "Troubleshooting Deployment Server Installation"
The Deployment Server for JD Edwards EnterpriseOne must reside on an Intel Pentium-based computer running Microsoft Windows. Optionally you can choose to install the Deployment Server into a virtual machine for Microsoft Windows. For non-production use with Oracle VM Templates, a Deployment Server is not required. You must have a Deployment Server in production environments or any environment in which you want to apply ESUs or perform Package Builds.
The JD Edwards EnterpriseOne software installation and upgrade programs enable you to create and maintain installation plans and deploy Release 9.1 to the Enterprise Servers and workstations.
Beginning with JD Edwards EnterpriseOne Applications Release 9.1, the Deployment Server installation program is based on the Oracle Universal Installer (OUI). You can use the OUI to:
Install the JD Edwards EnterpriseOne Deployment Client
This installation includes attaching and importing the Planner and Workbench tables into the local database on the Deployment Server.
Also beginning with Release 9.1, only the Oracle Enterprise Edition (OEE) database is supported as the local database on the Deployment Server.
A local OEE database must exist before you can run the OUI-based Deployment Server installer. The JD Edwards program called InstallManager is used to start the installation of the local OEE database.
No separate end-user licensing is required for installation of the local OEE database. It should be noted, however, that the installed OEE database is not fully functional relative to the commercial versions of the Oracle databases that are available.
Install the JD Edwards EnterpriseOne Deployment Share on the same machine as the Deployment Client or on a remote share.
The default is to install the Deployment Share and the Deployment Client on the same machine. If you choose to install on a remote share, the target machine can be Windows or Linux SAMBA based.
For additional considerations, refer to Section 3.2, "Local Oracle Enterprise Edition (OEE) Considerations".
The Deployment Server installer includes the OEE database (version 11gR2) for local use by the Deployment Server. The installation includes GUI tools for database administration.
Caution:
Because the Deployment Server installer must have access to a local OEE database, you must install the 32-bit database client prior to installing the Deployment Server.This section discusses these topics:
You must install a 32-bit version of the Oracle database client and then copy your tnsnames.ora
file to a subdirectory under the database client installation directory.
Caution:
Because the Deployment Server installer must have access to a local OEE database, you must install the 32-bit database client prior to installing the Deployment Server.To install a 32-bit Oracle database client:
Download the 32-bit Oracle 11g database client from the Oracle Software Delivery Cloud (https://edelivery.oracle.com
).
Install the database client.
Caution:
PATH environment variable. When you installed the 64-bit Oracle database, the installer placed the path to the database (for example,c:\Oracle\E1local\bin
) at the start of the Windows PATH environment variable. Then when you installed the 32-bit Oracle database client, the installer placed the path to the database client (for example, c:\Oracle\product\11.2.0\client_1\bin
) at the start of the Windows PATH environment variable.
When EnterpriseOne runs, it looks for database drivers in each directory from start to finish in the PATH. The first occurrence of a driver DLL that EnterpriseOne finds will be loaded. This means that the path to the 32-bit Oracle database client must come BEFORE the path to the 64-bit Oracle database.
If you installed the 64-bit database and 32-bit database client in that order, the order in the PATH should be correct. However, if you installed them in the opposite order, you need to correct the order in the PATH.
To reverse the order of the 64-bit database and 32-bit database client paths in the Windows PATH, follow these steps:
From the Start button, select Control Panel and then System.
On the left side of the window that comes up, click Advanced system settings.
Click the Advanced tab.
Click Environment Variables….
In the ”System variables” box, highlight the variable Path and click Edit….
In the ”Variable value” field, cut the 32-bit database client's path and the following semicolon (for example, c:\Oracle\product\11.2.0\client_1\bin;
).
Paste the client's path and semicolon at the start of the Path value.
Click OK.
Click OK to exit from the Environment Variables window.
Click OK to exit from the System Properties window.
Close the Control Panel's System window.
After you install the Deployment Server, you can copy this tnsnames.ora
file that the installation delivered:
From:
x:\oracle\E1Local\NETWORK\admin\
To:
<32-bit Oracle Client Install Dir>\network\admin
Best practices in JD Edwards EnterpriseOne environments are to never directly modify an EnterpriseOne database outside of EnterpriseOne. You should always use the JD Edwards EnterpriseOne application P96717 to perform the following Oracle database actions:
Import Tablespace
Export Tablespace
Create Tablespace
Drop Tablespace
You should always verify that your Deployment Server machine meets the MTRs (refer to Section 1.3, "Certifications (Formerly Known as Minimum Technical Requirements)"). The local Oracle database performs best on hard drives that are not fragmented or full. Additionally, the following table lists some guidelines for minimum configurations.
Specification | Recommendation |
---|---|
RAM | 2 GB minimum |
Page File Size | Minimum setting should be two times the amount of memory |
Disk Space Usage | Oracle database engine requires approximately 1.7 GB of disk space
JD Edwards EnterpriseOne specifications require approximately 1.7 GB of disk space When fully loaded, best performance is obtained if the hard drive on the Deployment Server machine has at least 20% free space. |
Local Database Name | Ensure that any reference in data sources and .ini files refer to the local database name in the exact mixed case, which is:
E1Local Failure to use the exact mixed case will lead to decreased performance of JD Edwards EnterpriseOne on the Deployment Server. |
You install the Deployment Server Install image from DVD images obtained from the Oracle Software Delivery Cloud (https://edelivery.oracle.com
).
To install from images downloaded from the Oracle Software Delivery Cloud:
Create a parent download directory on a disk with at least 15 GB free space. For example:
c:\DepSvr\Disk1
Download the source DVD images for the JD Edwards EnterpriseOne Deployment Server into the directory you created in Step 1.
You must use either the 7-Zip or WinZip program to unzip each of the DVD images into the directory you created in Step 1 (to verify successful extraction see Caution below).
Note:
During the extraction if you receive a message indicating that..\META-INF\MANIFEST\MF
already exists, at the prompt you can choose either Ignore or Replace.Caution:
You cannot use the built-in Microsoft Windows Explorer functionality to extract the zip files otherwise the result is an incomplete install image. You must use WinZip or 7Zip.To verify a successful extraction, check the file size of SPEC_MASTER.DBF
. This file should be 1.8 GB.
After unzipping all DVDs, you should have a structure that looks like this:
c:\DepSvr\Disk1\ DeploymentServer\ Install\ META-INF\ Misc\ stage\ InstallManager.exe InstallManager.htm InstallManager.ico ONEWORLD.ICO OracleLogo.gif README.TXT
Caution:
The directories contained on the Disk2, Disk3, Disk4, Disk5, and Disk4 images are all at the same hierarchical level as the\Disk1\DeploymentServer
directory.
When your unzip operation is complete, all the files must be in the same structure as the \Disk1\DeploymentServer
directory.
You should not have either a Disk2, Disk3, Disk4, Disk5, or Disk6 directory.
The Deployment Server delivers the ojdbc5.jar
for connecting to both the local and the enterprise Oracle databases
Caution:
Microsoft Windows 2008. If you are running the JD Edwards EnterpriseOne Deployment Server on a Microsoft Windows 2008 (or higher) platform, you must be signed onto the machine as administrator. Additionally you must run all JD Edwards EnterpriseOne installers and processes 'as Administrator '.Due to the security model on Microsoft Windows 2008, failure to run the JD Edwards EnterpriseOne processes 'as Administrator ' will likely result in random and unpredictable failures in the processes at run time.
Caution:
Remote Desktop. If you are using Remote Desktop to connect to the Deployment Server, you must use the/admin
argument to launch Remote Desktop. For example:
C:\WINDOWS\system32\mstsc.exe /F /admin
If you do not run Remote Desktop with the /admin
argument, Microsoft Windows blocks several important installer functions although Microsoft Windows reports success to the installer. For example, some registry entries will be missing and the Share for the Deployment Server will not be correctly created.
The Oracle Universal Installer (OUI) process creates temporary files during the install. By default these are placed on the c: drive of your Windows-based Deployment Server. You may need a sizable amount of free space on your c: drive in order to complete the installation successfully.
For Microsoft Windows 2008, pay special attention to the various Cautions in the steps in this chapter.
This table lists the mandatory and optional components of the Deployment Server installation.
Server | Mandatory Component | Optional Components |
---|---|---|
Deployment Server | Deployment Client
EnterpriseOne Files |
Development environment
Prototype environment Pristine environment |
The installation process for the Deployment Server performs these functions:
Installs the objects from the CDs.
Creates the path code directory structures (such as PS910) used on your selections.
Updates the Microsoft Windows Registry.
Note:
You can concurrently run the Deployment Server installer and perform the creation of the Enterprise, Web and Database virtual machines.After verifying the support structure as shown in the section of this guide entitled: Section 3.3, "Obtaining and Preparing the Deployment Server Install Image", you can install the Deployment Server. This process installs the Deployment Server from CDs.
Note:
You must install the Deployment Server locally; you cannot install the Deployment Server from a remote machine. However, you can choose to install JD Edwards EnterpriseOne files and environments on a remote machine using a mapped drive. Prior to installing to a remote machine, you must have already setup the drive with network mapping.This section describes these topics:
Section 3.5.3, "Before Launching the Deployment Server Installer"
Section 3.5.5, "Using InstallManager to Install a Local Database on the Deployment Server"
Section 3.5.7, "Understanding the JD Edwards EnterpriseOne Deployment Server Installer"
Before you run the installation program, shut down all programs running on the Deployment Server that could cause DLL conflicts (such as Microsoft SQL Services, Internet Explorer, Microsoft Word, or Adobe Acrobat). You can restart these programs after you finish installing the Deployment Server.
The diagram below illustrates the process flow and the various installation paths.
Note:
The Deployment Server OUI installer delivers the requisite JDK/JVM.You can install the Deployment Server using any of these methods:
From a copy of the Deployment Server installation DVDs that exists on a hard disk drive.
From a downloaded and unzipped image of the installation DVDs that was obtained from the Oracle Software Delivery Cloud (https://edelivery.oracle.com
).
Each Oracle product that is installed on a machine has what is termed an Oracle Home directory or path. This is a directory that contains all the files associated with the product. This path has a name as well. You can specify a name that is intuitive so you do not have to remember the path.
When you install the JD Edwards EnterpriseOne Deployment Server, you specify an Oracle Home and name for that installation as well. For example, you may enter C:\JDEdwards\E910
as the Oracle Home path and JDE DEP910_HOME as the Oracle Home name. Following the this example, your Oracle Home on the Deployment Server would be:
Oracle Home Path | Oracle Home Name | Comment |
---|---|---|
C:\JDEdwards\E910 |
JDE_DEP910_HOME | This is the Oracle Home of the Deployment Server |
If you have not already installed the database engine and a database called E1Local does not exist on your Deployment Server, use the procedures in this section to install these requisite components before installing the JD Edwards EnterpriseOne Deployment Server. If the local database engine is already installed and an E1Local database exists, do not reinstall the database engine; go to the section entitled: Section 3.5.7, "Understanding the JD Edwards EnterpriseOne Deployment Server Installer".
To use the InstallManager to install a local database:
Obtain the appropriate disk images from the Oracle Software Delivery Cloud (https://edelivery.oracle.com
) for the local database you wish to install on your Deployment Server.
Log on to the Deployment Server as a user with Administrator rights.
Caution:
Ensure that the Administrator account name that you use does not contain any special characters.Locate the unzipped image for the Deployment Server installation DVDs.
Tip:
Refer to the preceding Tip: Installation Methods for a list of various installation methods.From the unzipped image, execute the InstallManager.exe
file from the root folder.
\Disk1\InstallManager.exe
Caution:
Microsoft Windows 2008 (and Higher). On the Microsoft Windows 2008 (and higher) platform, you must right-click on the executable and select Run as Administrator from the drop-down.On JD Edwards Install Manager, select this link to install the local OEE database:
EnterpriseOne Database Engine
If you receive a Install Manager - Security warning dialog, The publisher could not be verified., click the Run button to begin the installation of the local database. This installation process can take quite some time. Upon completion a local database called E1Local will exist.
Caution:
You must reboot your machine before continuing with the installation of the JD Edwards EnterpriseOne Deployment Server as described in the next section in this guide entitled: Section 3.5.7, "Understanding the JD Edwards EnterpriseOne Deployment Server Installer".Even though the screen indicates that the installation was successful, you should perform the following checks to verify that the database truly installed correctly:
Examine the log file
The log file is in this folder:
C:\Program Files\Oracle\Inventory\logs
The log file name is named:
installActionsyyyy-mm-dd_hh-mm-ssAM|PM.log
where the syntax is:
yyyy
is the year
mm
is the month
dd
is the day of the month
hh
is the hour
mm
is the minutes
ss
is the seconds
AM|PM
is either AM or PM
For additional details on log file names and location, refer to the section of this chapter entitled: Section 3.9.2, "OEE Installer Logs".
Verify that the OEE services exist and are running
From the Microsoft Windows Control Panel, navigate to Administrative Tools > Services.
In the list of Services, look for these services:
OracleE1LocalTNSListener
OracleServiceE1LOCAL
If either of the above services is missing, it indicates that there was a problem in completing all the installation and configuration steps. You should examine the logs specified in the table in the section of this guide entitled: Section 3.9.2, "OEE Installer Logs".
To remedy you will probably need to deinstall the database engine using the steps in the section of this guide entitled: Section 11.3, "Deinstalling the Local OEE from the Deployment Server", reboot the Deployment Server machine, and then reinstall the OEE database.
A local OEE database engine and a database called E1Local must already exist on this machine. If not, use the procedures in the preceding section entitled: Section 3.5.5, "Using InstallManager to Install a Local Database on the Deployment Server".
This section describes:
Section 3.5.7.1, "Understanding EnterpriseOne Files Location"
Section 3.5.7.2, "Running the JD Edwards EnterpriseOne Deployment Server Installer"
Section 3.5.7.3, "Mandatory Post Installation Tools Accelerator"
The software component called EnterpriseOne Files is a pre-defined grouping of files that can be installed on your local machine or a mapped network drive. It includes EnterpriseOne system files and pathcodes for these four (4) environments:
Development
Prototype
Pristine
Production
By default the installer assumes the local machine is the Deployment Server. As such it provides a default value for your Oracle Home path.
You cannot change this local path value after the installation is complete; it must remain whatever value you specified at the time of installation.
Optionally you can choose to install EnterpriseOne (E1) Files to a remote machine as the Deployment Server. If you do so, the installer creates a unique ”planner client” on the local machine that contains only the Planner pathcode. You should only set up one ”planner client” machine to do the Deployment Server jobs such as applying software updates, running installation plan, and so on.
Using a Remote Machine as the Deployment Server
If you intend to use a remote machine as the Deployment Server, prior to running the Deployment Server installer you must first map a network drive using this procedure:
On the remote Deployment Server, create a folder as the target location in which the installer will place the EnterpriseOne (E1) files. For example:
E:\JDEdwards\E910
Using the example above, share the target folder E910
with full permissions.
Caution:
Because the Deployment Server installer must be run as an Administrator, you must also map a network drive as an Administrator.Start a Command Prompt as Administrator and map a network drive on the local machine to the remote Deployment Server machine. For example, map Z:\
to \\Remote_Deployment_Server_Machine_name\E910
Tip:
You can verify that the drive is being mapped as an Administrator by confirming that ”Administrator:” is displayed in the title bar of the Command Prompt window.The below screen shows a sample of a properly mapped network drive for the remote Deployment Server:
Note:
In a later separate process described in Section 3.5.7.2, "Running the JD Edwards EnterpriseOne Deployment Server Installer", when you are prompted by the installer for the location of the remote Deployment Server, in the location field you can browse to or enter the mapped drive including the drive letter designation. Using the above example in Step 3, the value would be theZ:
drive. Using the above screen shot as an example, the value would be the L:
drive.
The same installer validates the location that you enter for the remote location. If the mapping to the remote location is not valid or the directory specified in Step 1 above does not exist on the remote machine, the installer will not continue.
Note:
The installer validates the location. If the mapping to the remote location is not valid the installer cannot continue. Likewise the directory specified in Step 1 must exist on the remote machine or else the installer cannot continue.Use the procedure in this section to install the JD Edwards EnterpriseOne Deployment Server.
Log on to the Deployment Server as a user with Administrator rights.
Caution:
Ensure that the Administrator account name that you use does not contain any special characters such as ampersands, asterisks, or underscores.Locate the unzipped image for the Deployment Server installation.
Tip:
Refer to the preceding Tip: Installation Methods for a list of various installation methods.Caution:
Microsoft Windows 2008 (and Higher). On the Microsoft Windows 2008 (and higher) platform, you must right-click on the executable and select Run as Administrator from the drop-down.From disk1, execute the InstallManager.exe
file from the root folder. For example:
\Disk1\InstallManager.exe
On JD Edwards Install Manager, select this link:
EnterpriseOne E910 Deployment Server
This process opens a Microsoft Windows command window as shown in the below example.
After the OUI installer is launched, the command window is closed and the Welcome screen is displayed.
On Welcome, select the Next button.
On Select Installation Type, you must select the Custom radio button for this installation type. This is required because it is mandatory for all four path codes to be loaded.
Note:
The Typical selection installs environments for Deployment Client (Planner), prototype, pristine and also installs JD Edwards EnterpriseOne files on the local machine. The Typical selection installs environments for Deployment Client (Planner), prototype, pristine and also installs JD Edwards EnterpriseOne files on the local machine. This selection will not work for this process.The Custom selection lets you choose the specific environments you want to install on the deployment server. The deployment client (Planner) is always installed on the local machine. You may choose to install JD Edwards EnterpriseOne Files and environments on a remote machine. In that case, first you need to setup a mapped drive as described in the section of this guide entitled: Section 3.5.7.1, "Understanding EnterpriseOne Files Location". This selection is required for this process.
After you have selected an installation type, select the Next button.
On Specify Home Details, you must specify an Oracle Home path and a name for that path.
Tip:
For more information about Oracle Homes and recommendations for naming the Oracle Homes for the JD Edwards EnterpriseOne Deployment Server, see the section in this guide entitled: Section 3.5.4, "Understanding Destination Paths".Each Oracle product that is installed on a machine has what is termed an Oracle Home path. This path contains all the files for each Oracle product. This path has a user-specified name as well.
On Specify Home Details, complete these fields:
Field | Description |
---|---|
Name | Enter a name for the Oracle Home for the JD Edwards EnterpriseOne Deployment Server. For example:
JDE_DEP910_HOME |
Path | The path you enter here is for the Oracle Home path where the E1 Deployment Server will be installed. For example, the path might be:
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. For local installation, you must use the default value. For remote installation, this value must be the letter designation of the mapped drive. For additional details, refer to the section of this chapter entitled: Section 3.5.4, "Understanding Destination Paths". |
Select the Next button.
Note:
The Available Product Components screen and subsequent screens until the Summary are displayed if you chose Custom installation on Select Installation Type in Step 7.On Available Product Components, EnterpriseOne Deployment Server, enable the checkboxes to select these features components you want to install:
EnterpriseOne Deployment Client
The selection for EnterpriseOne Deployment Client is mandatory in order to select other components. If you do not select this component, you cannot select any other components. This installs the planner pathcode and databases on the local machine. You will be given an option to install other components on a remote share.
EnterpriseOne Files
The selection for EnterpriseOne Files includes mandatory system files. If you do not select this component you cannot select any other environment components. Likewise, if you re-run the JD Edwards EnterpriseOne Deployment Server Installer to add an environment it will check to ensure that these files are already installed and you will not be given an option to install the environment on a machine, drive, or directory that is different from that which contains the JD Edwards EnterpriseOne files.
Development Environment
Prototype Environment
Pristine Environment
Tip:
Use the Select All button to select all components.Caution:
By default all environments are selected. However, since Oracle VM Templates for JD Edwards is not shipped with the Production Environment, you should manually deselect that checkbox, as shown in the preceding screen shot.Click the Next button.
On Specify EnterpriseOne Files Location, you can accept the default local value or enter a mapped network drive.
The installer provides a default value which is your Oracle Home path. For example:
C:\JDEdwards\E910
If you prefer to install JD EnterpriseOne Files to a remote Deployment Server, you can specify a mapped drive. For example:
Z:\
For more on the proper use of mapped drives and network drives, refer to the following Caution.
Caution:
You cannot enter a network path such as:\\machine_name\network_share
If you enter a network path instead of a mapped drive, the installer will give an error.
When you click Browse to select the drive, if the mapped remote drive is not listed, perform these steps:
Start a Command Prompt session by right clicking and selecting Run as Administrator.
This command prompt opens on the Microsoft 2008 Server with Administrator:cmd in the header.
In the command window, type this command:
net use z: \\<MachineName>\<SharedPath>
where z:
is the drive on which your mapped drive exists.
Select the Next button.
On Deployment Server for OVM, change the following values to match what you are using for your Virtual Machines for Enterprise Server, Database Server and Web Server:
Location Name
Specify the same Deployment Location that you are using for the Database Server.
Deployment Server Name
You should only change this value from the supplied value if you are installing to a Remote Share on a different machine. If that is the case, then supply the name of the Remote Share machine.
Caution:
On this screen only, you should not enter a fully qualified machine name. You should only enter server names without the domain. The values you enter for the Deployment Server Name on this screen are used to populate the Planner database, which for these fields has a restriction of 15 alphanumeric characters.Database Server
Specify the name of your Database Server.
HTML Server
Specify the name of your HTML Server.
Enterprise Server
Specify the name of your Enterprise Server.
Select the Next button.
On Oracle connect string, Enterprise database connect string, you can change the connect string value only if you are installing to a non-virtualized database, such as Exadata or ODA.
Caution:
If you are installing a virtual database using the Oracle VM templates for JD Edwards EnterpriseOne, you must accept the default value, which is ovsorcl. If you change this value for use with a virtualized Oracle database, all database server functions will fail.Select the Next button.
On Choose E1Local User Password, you can specify a secure password to be used for the E1Local Database Users on the Deployment Server. This unique password will be used for all database accounts created by the Deployment Server installer.
The default password is the same as the user name of the database account. For example, if the user name of the local database account is JDE, the default password is JDE.
If you do not specify a E1Local user password, by default the installer will use this value: DEFAULT. You cannot leave this field blank.
Select the Next button.
On Summary, verify the list of items to be installed is correct.
If there is insufficient disk space to complete the installation on the Deployment Server target machine, an error message is displayed.
Click the Install button.
The JD Edwards EnterpriseOne Deployment Server Installer displays a panel showing the ongoing status of the installation.
When the installation of the Deployment Server finishes, the End of Installation screen is displayed.
Caution:
Examine the Installer Logs. Even though the screen indicates that the installation was successful, you should you should always check the logs before you attempt to run the Deployment Server. The file is named log.txt and is located in the Deployment Server installation directory. For example:C:\Program Files (x86)\Oracle\Inventory\logs\InstallActions\ installActionsyyyy-mm-dd_hh-mm-ssPM.log
For additional details on log file names and location, refer to the section of this chapter entitled: Section 3.9.2, "OEE Installer Logs".
On End of Installation, select the Exit button.
After the Deployment Server is installed, you must run the TLOVM001 Tools Accelerator. You will not be able to start services until you have run this accelerator. For details on locating this Tools Accelerator and a description of its functions, refer to the procedure in the section of this guide entitled: Section 3.10, "Configuring the Planner Databases".
After the Deployment Server is installed for Oracle VM Templates implementations, before you install the Development Client (also called the fat client), you must complete the procedures in this section entitled:
If you when you are installing the VM Template for the Enterprise Server, you did not give the requisite non-qualified name for the Deployment Server, you will need to modify the oraparma.ini
file to include both the non-qualified name and the fully qualified name, as described in this procedure.
Prior to submitting UBEs on the Development Client, you must to manually update the oraparam.ini
file on the Deployment Server using this procedure.
Navigate to this directory on the Deployment Server:
OneWorldClientInstall\Install
Use an ASCII editor to edit the oraparam.ini
file.
Within the oraparam.ini
file, search for this section:
[FileLocations]
Change the PackageInf setting to remove the segment \\DEPLOYMSTR\E910
as shown below:
from:
PackageInfs=\\<Your Deployment Server Name>\E910\\DEPLOYMSTR\E910\pacakge_inf
to:
PackageInfs=\\<Your Deployment Server Name>\E910 \pacakge_inf
Change the CurrentReleaseMasterPath setting to remove the segment \\DEPLOYMSTR\E910
as shown below:
from:
=\\<Your Deployment Server Name>\E910\\DEPLOYMSTR\E910
to:
=\\<Your Deployment Server Name>\E910
Save and close the oraparam.ini
file.
If you do not have WebSphere Express installed on your Development Client, before you install the Development Client you must follow the procedure in this section or else the Install Features will fail.
Login to the Deployment Server.
Go to this directory:
X:/JDEdwards/E910_1/package_inf
Use an ASCII editor to open the DV910FA.inf
file.
In the [Features]
section, comment out this entry:
WEBDEVELF=\\<MachineName>\E910\package_inf\feature_inf\WEBDEVELF_1.INF
Save and close the DV910FA.inf
file.
After you have installed the Development Client, before you can log onto it, you must follow this procedure to add the Security Serve name to the Development Client jde.ini
file.
On the Development Client machine, use an ASCII editor to open the jde.ini
file.
In the [Security]
section, locate this setting:
SecurityServer
Enter a valid value for the Security Server for your installation. For Oracle VM Template implementations, this value is the same name as your Enterprise Server machine name.
Save and close the jde.ini
file.
Caution:
If you want to add an additional environment that you did not install when you first ran the Deployment Server Installer, you must re-run the installer from the original disk image. You cannot re-run the installer using the OUI-based installer.You can only use the installer located accessed by Start > All Programs > Oracle - JDE_DEP910_HOME > Oracle Installation Products > Universal Installer for deinstalling the Deployment Server.
To rerun the Deployment Server Installer, follow the instructions in the preceding section of this chapter entitled: Section 3.5, "Installing the Deployment Server".
This install image of Deployment Server and matching OVM machines was updated with the latest available ESUs and Tools Release at the Tools 9.1 Update 3 general availability time frame. While you do not need to install additional software changes unless you have a specific need for them, it is recommended and always a best practice to download the latest Planner Update. If you are not adding any Tools or ESU changes, you can skip to the section of this guide entitled: Section 3.9, "Troubleshooting Deployment Server Installation".
If you decide to update to get the latest software, you should use Change Assistant to download and install the latest Tools Release, Tools Release Patch, and Planner Update ESU from the JD Edwards EnterpriseOne Update Center.
Caution:
You must start Change Assistant as Administrator. Right-click on the shortcut and select 'Run as Administrator from the drop-down.Note:
The order in which the following Tools Release and updates are applied is very important. Do not deviate from the order described in these procedures.This section discusses:
To install the latest tools release and latest tools release patch:
From the JD Edwards EnterpriseOne Update Center homepage, download the latest Tools Release Patch (for example, 9.1.1.0) and Tools Release documentation.
Using the Tools Release documentation, install the Tools Release Patch to the Deployment Server.
Caution:
You must right-click on the executable and select Run as Administrator from the drop-down.Note:
If you have ever used the Drag and Drop method of moving between Tools Releases for service packs, it is necessary to run theReconfigureMSDE
utility to encrypt the ”system” database user's password. Refer to the section of this guide entitled: Section 3.9.5.9, "Encrypting the Password of the Local Oracle Database".Caution:
As part of the local database installation, which is bundled with the Deployment Server Installer, the password for the system user on the E1Local database is encrypted. If you re-set this password, several JD Edwards EnterpriseOne functions will fail. If you should inadvertently reset the password, you can encrypt it again to the expected default password. Refer to the section of this guide entitled: Section 3.9.5.9, "Encrypting the Password of the Local Oracle Database".To install the latest planner update:
From My Oracle Support, download the latest planner update for your Tools Release to the Deployment Server.
Run the self-extracting executable and follow the on-screen instructions to install the planner update on the Deployment Server.
You must enter a valid JD Edwards EnterpriseOne user and password to initialize the Planner.
The shipped values are JDE for the user and JDE for the password.
Note:
The above login screen is displayed so the Planner Update can update the metadata specifications on the Deployment Server.When the installation finishes, view the JD Edwards EnterpriseOne Deployment Server Setup form to confirm that the installation was successful.
Tip:
If the folder into which you expanded the Planner Update is empty, you should run the self-extracting executable (JMnnnnn.exe
) again. When the Welcome screen comes up, click on Cancel to quit.Follow the steps in the Special Instructions, which are contained within an HTML file that is shipped with the Planner Update. The special instructions file is in this directory with this file name:
x:\download_directory\planner_update_id\E910SpecialInstructions.htm
where download_directory
is the directory where you downloaded the Planner Update.
Caution:
Every time you apply a new Planner Update you must run both of these:SpecialInstrs.bat
R98403XB XJDE0002
This section discusses:
If you are re-installing your Deployment Server, you must ensure that the local Planner tablespaces (OEE) are not attached. To detach the tablespaces, run these batch files:
jdedwards\e910\planner\data\DropPlannerDB.BAT
jdedwards\e910\planner\data\detach_metadata.bat
This section lists the log files for installations on the Deployment Server:
x:\jdedebug.log
Note:
The location is defined by this jde.ini setting:[DEBUG]
DebugFile=d:\jdedebug.log
x:\jde.log
Note:
The location is defined by this jde.ini setting:[DEBUG]
JobFile=D:\jde.log
C:\ReconfigureMSDE.log
\InstallLogs\attach_plannerdata.log
\InstallLogs\attach_plannerspec.log
\InstallLogs\Configurexxxspec.log
Where xxx
denotes that there are several of these logs, which contain logging for predefined package specs. For example:
ConfigureDV910FAspec.log
X:\JDEdwards\E910\Detach
xxx.log
Where xxx
denotes that there are several of these logs, which contain logging for predefined package specs. For example:
DetachDV910FAspec.log
See Also
For OEE-specific logs, refer to Section 3.9.5.1.2, "OEE Logs" in this chapter.
Note:
This section is provided for reference. You are not required to manually configure these files because the Deployment Server installer configures the .ini files appropriately for the OEE local database.The data source definitions for OEE are defined in these configuration files:
jde.ini
jdbj.ini
The following lists some of the settings within the various configuration files that are related to the local database.
jde.ini
[DB SYSTEM SETTINGS] Type=E LOBFlag=Y [DB SYSTEM SETTINGS ' SECONDARY] Type=E LOBFlag=Y
jdbj.ini
The jdbj.ini
file specifies location of the tnsnames.ora
file.
The jdbj.ini
file also specifies the JDBC driver for Oracle as ojdbc5.jar
, which replaces the version (classes12.jar
) used in prior releases of JD Edwards EnterpriseOne.
[JDBj-BOOTSTRAP DATA SOURCE] databaseType=E lob=true [JDBj-SPEC DATA SOURCE] databaseType=E lob=true [JDBj-JDBC DRIVERS] ORACLE=oracle.jdbc.driver.OracleDriver
The Path Code Master (F98611) contains changes to support OEE. It contains values for use of EMDBSY column to indicate type of specs and type of local database. These values are used by JDB, JDBj, and Package Build.
EMDBSY Value | Spec Type | Local DB Type |
---|---|---|
0 | TAM | MSDE |
1 | XML | MSDE |
2 | TAM | SSE |
3 | XML | SSE |
5 | XML | Oracle |
This section discusses these topics:
Section 3.9.5.3, "EnterpriseOne Access to the Local Oracle Database"
Section 3.9.5.5, "Verifying the Local Oracle Database Installation"
Section 3.9.5.8, "Administering the Local Oracle Database Using SQL Plus"
Section 3.9.5.9, "Encrypting the Password of the Local Oracle Database"
Section 3.9.5.10, "Decrypting the Password of the Local Oracle Database"
Section 3.9.5.11, "Import and Export Tablespaces to the Local Oracle Database"
This section discusses the location for these critical files:
Deployment Server. The default installation location of the local Oracle database on the Deployment Server is:
C:\Oracle\E1Local
Note:
This location can be changed at installation time.Client. The default installation location of the local Oracle database on the Web Development Client (also called the Administration client or fat client or workstation) is:
C:\Oracle\E1Local
Note:
This location can be changed at installation time.The following table lists the locations of the various log files.
Log File | Location |
---|---|
Oracle import log for data | <E1_install_dir>\<pathcode>\Data\imp*.log |
Oracle export log for data | <E1_install_dir>\<pathcode>\Data\exp*.log |
Oracle import log for specifications | <E1_install_dir>\<pathcode>\Spec\imp*.log |
Oracle export log for specifications | <E1_install_dir>\<pathcode>\Spec\exp*.log |
Deployment Server and local Oracle database install logs | <E1_install_dir>\InstallLogs\*.log |
Local Oracle database runtime | .\admin\E1Local\bdump |
Local Oracle database listener | alert_e1local.log |
Local Oracle database runtime and listener | .\NETWORK\ADMIN\*.log |
Log for ReconfigureMSDE.exe |
C:\ReconfigureMSDE.log |
Local Oracle database install logs | c:\Program Files\Oracle\Inventory\logs |
Log for OEESetup.exe |
c:\OEEInstall.log |
The tnsnames.ora
file is located in these directories:
..\Oracle\E1Local\NETWORK\ADMIN ..\E910\client
You must reboot the Deployment Server after installing or deinstalling the local Oracle database.
The Deployment Server Installation Workbench generates and encrypts a password and then changes the local Oracle database ”system” and ”sys” accounts' passwords to that password. During the rest of the Installation Workbench and at runtime of the Deployment Server, the local Oracle database is accessed via the ”system” account and this generated and encrypted password.
This table lists the relationship between the local Oracle database accounts and the password.
Local Oracle Database Account | Default Password |
---|---|
System | Generated and encrypted by the Deployment Server installer. |
Sys | Generated and encrypted by the Deployment Server installer. |
JDE | JDE
Note: The default password may be changed by DBA but if Security Server is not used, it must match the password of EnterpriseOne user JDE. |
<tablespace_name>
For example:
|
<tablespace_name>
For example:
Note: The default password may be changed by DBA. This value does not affect the runtime operation of JD Edwards EnterpriseOne because it does not access the local Oracle database in this manner. |
If you cannot delete the directory for the E1Local Oracle Home because a process has it locked, you can use Process Explorer to determine which process has it locked, and subsequently kill that process.
To obtain Process Explorer, you can download and install a free version at this link:
http://technet.microsoft.com/en-us/sysinternals
To use Process Explorer:
Navigate to Find > Find Handle or DLL....
In the Handle or type field, enter the full name of the directory that cannot be deleted. For example:
c:\oracle\e1local
Click the Search button.
On the search results screen, note the PID(s) (Process IDs) that are associated with the specified directory.
Cancel the Process Explorer Search window to return to Process Explorer.
Use Process Explorer to kill the identified process(es).
Note:
If one or more of the processes is Windows Explorer (explorer.exe
), killing it may cause the computer to lock up. If that happens, you will need to reboot the Deployment Server machine.
The process Oracle.exe
is the local Oracle database engine. If it has a file locked, you can stop the service OracleServiceE1LOCAL.
If one or more of the processes locks a file in the directory you are trying to delete even after rebooting, you may have to determine which service is automatically starting that process and change the service to manual startup. Then reboot the Deployment Server machine and delete the directory.
To verify that the installation of the local Oracle database was successful:
Inspect the latest logs in these directories:
<E1_install_dir>\InstallLogs
C:\Program Files\Oracle\Inventory\logs
Resolve any issues that are identified in the logs.
You cannot reinstall the local Oracle database using the Deployment Server installer if there are indications that the local Oracle database already exists. The Deployment Server installer will skip the installation of the local Oracle database if either of these conditions is true:
The local Oracle database service OracleServiceE1LOCAL is running.
This registry key exists:
\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE\KEY_E1Local
This section discusses:
Verify that the Oracle listener service OracleE1LocalTNSListener is running. It is possible that the service may not have started due to slow bootup of the machine.
Verify that the E1Local database system account password is valid. If the following command executes successfully, it means that the password is not encrypted. If so, you must encrypt the password in order to enable database access.
SQLPlus.exe system/admin@E1Local
where ”admin” is the password. This password may have been set to ”admin” by one of the EnterpriseOne database scripts, or it may be a plain-text word that someone set by running ReconfigureMSDE
.
If the password was decrypted with ReconfigureMSDE
, you should re-encrypt it using ReconfigureMSDE.exe
. Refer to the section of this guide entitled: Section 3.9.5.9, "Encrypting the Password of the Local Oracle Database".
When the Deployment Server installer installs the local Oracle database (E1Local), the \bin
directory is added to the start of the Windows PATH. If you have both the local Oracle database and the Oracle client installed (for example, if you are connecting to an Oracle database on a machine other than the Deployment Server), the local Oracle database version of the executables and tnsnames.ora
are used. The Deployment Server installer will rename any tnsnames.ora
file that it finds in the location below, and put a configured tnsnames.ora
in this location.
<E1Local_installation_path>\network\admin
By default, the <E1Local_installation_path>
is C:\Oracle\E1Local
, but the actual value is specified during OEE installation.
Note:
If the deployment server is in a different domain than the Database Server, the configuredtnsnames.ora
may not have the correct domain name for your Database Server. If not, you should edit the tnsnames.ora
file in this location:
c:\oracle\E1local\network\admin
This tnsnames.ora
must specify the correct domain name for the Database Server for the ovsorcl database. Copy and overlay the corrected tnsnames.ora
file into this directory:
JDEdwards\E910\client
This tnsnames.ora
file is used for JD Edwards EnterpriseOne Development Client install.
This configured tnsnames.ora
must be copied to the network\admin
directory under the 32-bit Client install for Oracle, and also into the ..\E910\client
directory for use by Client Install.
The command-prompt program SQLPlus.exe
and GUI program SQL Developer are provided with the installation of the local Oracle database using the Deployment Server installer. You can use either tool to access the local Oracle database where both the user and default password are the same as the tablespace name. If using SQLPlus, the command to sign into a database is:
SQLPlus.exe <user>/<password>@E1Local
For example, if the tablespace JDESY910 exists in the E1Local database, use the following to sign in:
SQLPlus.exe JDESY910/JDESY910@E1Local
JD Edwards EnterpriseOne connects to the local Oracle database (E1Local) through the system account using an encrypted password. Some of the administrative database scripts on the Deployment Server decrypt this password before submitting database commands. Upon exit, such programs subsequently then re-encrypt the password. If one of these scripts fails to complete (for example, it is killed or it otherwise dies) before it can encrypt the password again, EnterpriseOne will not be able to connect to the database. You can determine if this is the case by attempting to sign into the local Oracle database using this command:
SQLPlus.exe system/admin@E1Local
where ”admin” is the default password that the scripts use.
If you can sign in, the password must still be decrypted. You must re-encrypt the system account password using the following steps for EnterpriseOne to operate correctly:
Locate this program:
<E1_install_dir>\system\bin32\ReconfigureMSDE.exe
Right click on ReconfigureMSDE.exe
and select Run as administrator.
Tip:
Do not let the ”MSDE” part of the program name mislead you. This program was originally created when EnterpriseOne supported Microsoft's MSDE database. It was not renamed when support for OEE was added.Be sure the E1Local database is selected.
Enter the ”system” user's old password (in this case, enter ”admin” without the quotes) in the field ”Change from password….”
Under ”To password”, click on ”Encrypted E1 Password.”
Click OK.
Click OK.
Watch the status bar at the bottom of the dialog for informational messages.
If changing the password fails, attempt to stop and restart the database services OracleServiceE1LOCAL and OracleE1LocalTNSListener and then retry ReconfigureMSDE.exe
.
To decrypt the system account password:
Locate this program:
<E1_install_dir>\system\bin32\ReconfigureMSDE.exe
Right click on ReconfigureMSDE.exe
and select Run as administrator.
Tip:
Do not let the ”MSDE” part of the program name mislead you. This program was originally created when EnterpriseOne supported Microsoft's MSDE database. It was not renamed when support for OEE was added.Be sure the E1Local database is selected.
Under ”Change from password…”, click on ”Encrypted E1 Password.”
Enter the ”system” user's new password in the field ”To password.”
Reenter the new password and click OK.
Click OK.
Watch the status bar at the bottom of the dialog for informational messages.
If changing the password fails, attempt to stop and restart the database services OracleServiceE1LOCAL and OracleE1LocalTNSListener and then retry ReconfigureMSDE.exe
.
Caution:
If you manually decrypt the system account password, ensure that you re-encrypt the password before attempting to run JD Edwards EnterpriseOne. If the password is not encrypted, JD Edwards EnterpriseOne will fail because it cannot access the local Oracle database.You can use the JD Edwards EnterpriseOne application P96717 to import and export tablespaces except the Planner tablespaces. To import or export the Planner tablespaces, you must use scripts that are delivered with the installation of the Deployment Server. The scripts are located in this directory:
For Planner Databases:
<E1_install_dir>\planner\data\attach_planner.bat
<E1_install_dir>\planner\data\detach_planner.bat
For local metadata repository database (for example, specs and serialized objects):
<E1_install_dir>\planner\Data\attach_metadata.bat
<E1_install_dir>\planner\Data\detach_metadata.bat
This section discusses:
Section 3.9.5.11.1, "Import Tablespace Script (attach_planner.bat)"
Section 3.9.5.11.2, "Export Tablespace Script (detach_planner.bat)"
To use the import tablespace script:
Navigate to the directory JDEdwards\E910\planner\data
and run this script:
TestPlannerDBs.bat
Edit the attach_planner.bat
file such that any tablespaces that you do not intend to import are commented out. These lines start with:
call IMPORT_TABLESPACE.BAT
Open a command prompt window by right-clicking on a Command Prompt shortcut and selecting Run as administrator.
Change directory to the location of the batch files.
Run the batch file to import the tablespace using this syntax:
attach_planner.bat <Oracle_dir> <E1_install_dir>
where <Oracle_dir>
is the parent of the E1Local directory.
For example:
attach_planner.bat c:\Oracle c:\JDEdwards\E910
Note:
This import batch file for the local metadata repository is in the spec directory:attach_metadata.bat
To use the export tablespace script:
Edit the jdedwards\E910\planner\data\detach_planner.bat
file such that any tablespaces that you do not intend to import are commented out. These lines start with:
call EXPORT_TABLESPACE.BAT
Open a command prompt window by right-clicking on a Command Prompt shortcut and selecting Run as administrator.
Change directory to the location of the batch files.
Run the batch file to import the tablespace using this syntax:
detach_planner.bat <Oracle_dir> <E1_install_dir>
where <Oracle_dir>
is the parent of the E1Local directory.
For example:
detach_planner.bat c:\Oracle c:\JDEdwards\E910
Note:
This export batch file for the local metadata repository is in the data directory:detach_metadata.bat
The <E1_install_dir>\OneWorld Client Install\install.ini
file specifies that the OEE database will be installed by the Web Development client (workstation) installer.
[ThirdPartyApps] ORACLE=ThirdParty\ORACLE\OEESetup.exe,
Caution:
The ”,” character is required at the end of the line that specifies theOEESetup.exe
.The local Oracle database configuration requires that the Oracle DB installer be located in this directory:
<E1_install_dir>\OneWorld Client Installer\ThirdParty\ORACLE
The following lists specific settings within the Deployment.inf and <Package_name>.inf
for OEE.
Deployment.inf
[ThirdPartyApps]ORACLE=ThirdParty\ORACLE\OEESetup.exe,
<Package_name>.inf
(example from a DV910FA.inf
file)
[Oracle Databases] JDELocal_DV910=ORACLE SPEC_DV910FA=ORACLE [JDELocal_DV910] SourceTableSpace=JDELocal Server=127.0.0.1 UserID=SYSTEM DataFileDestDir=$DDV910DATA\JDELocal_DV910.dbf DumpFileDestDir=$DDV910DATA\JDELocal_DV910.dmp [SPEC_DV910FA] SourceTableSpace=SPEC_DV910FA Server=127.0.0.1 UserID=SYSTEM DataFileDestDir=$DDV910\Spec\SPEC_DV910FA.dbf LogFileDestDir=$DDV910\Spec\SPEC_DV910FA.dmp
If you cannot submit UBEs from the Development Client (also called the ”fat” client), it may be because you specified a fully qualified name instead of a non-qualified name for the Deployment Server.
Use this procedure to specify both a non-qualified and fully qualified name for the Job Queue entries.
Login to the Development Client.
Fastpath to P986130.
If you specified a fully qualified name during the Oracle VM Template installation, you will see entries for QBATCH and I-ACTIVE with the machine name as fully qualified machine name (for example: machine-name.domain.name
)
Select the QBATCH entry and click the Copy icon.
On Job Queue Revisions, complete these fields:
Host
Enter the non-qualified machine name without the domain name. This can be a maximum of 15 alphanumeric characters (no special characters).
Job Queue
Enter QBATCH.
Port
Enter the value 6016.
Click the OK button.
On the Work with Job Queue form, click the Find button and verify the entry is available.
The images for the installation of the Oracle VM Deployment Server include the Installation Plan created for you at Oracle. You do not need to create and run an Installation Plan for the PS910, PY910, and DV910 environments. However, there are some steps that normally run during an Installation plan that must be done on your Deployment Server. An Oracle Tools Accelerator has been provided to do these steps, and must be run at this point.
Note:
This step cannot be run until you have started the OVM Database Server or loaded the Non-Virtualized Database Server. This is required because this step updates tables in the Database Server.Use this procedure to configure the Planner databases:
If you have not done so already, install the latest version of Change Assistant.
Set the Preferences in Change Assistant to store and find ESUs in your install location. For example:
c:\JDEdwards\E910\Change Assistant\Downloads
Start Change Assistant and deploy the Tools Accelerator TLOVM001_20_99.par
, which is obtained from the location specified in the preceding step. This Tools Accelerator does the following:
Shares the install folder on the Deployment Server for Client Install and Package Build
Updates ESU entries in the registry for the shipped ESUs
Configures the shipped install and package .inf
files and .ini
files
Configures the Package Feature records
Configures the manifest records for these shipped packages:
- PS910FA
- PY910FA
- DV910FA
Caution:
If you do not install all four standard environments as recommended, the Tools Accelerator will fail at this point for each environments that is not installed. However, this does not prevent it from running correctly for the standard environments that you did install.Note:
If you re-load the OVM database Server or non Virtualized Database Server, you must re-run this process.