C Troubleshooting the Deployment Server Installation

This appendix discusses these Deployment Server installation troubleshooting topics:

C.1 Verify Local Planner Tablespaces are Not Attached

If you are re-installing your Deployment Server, you must ensure that the local Planner tablespaces (Oracle) are not attached. To detach the tablespaces, run these batch files:

jdedwards\e920\planner\data\detach_planner.bat

jdedwards\e920\planner\data\detach_metadata.bat

C.2 Oracle Database Installer Logs

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:\ReconfigureDB.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:

    ConfigureDV920FAspec.log

  • X:\JDEdwards\E920\Detachxxx.log

    Where xxx denotes that there are several of these logs, which contain logging for predefined package specs. For example:

    DetachDV920FAspec.log

See Also

For OEE-specific logs, refer to Section C.5.1.2, "OEE Logs" in this chapter.

C.3 Configuration Files

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 Oracle 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 ojdbc7.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
    

    Caution:

    The shipped jdbj.ini file in the following folder contains specifications for each database type:

    C:\JDEdwards\E920\system\JAS\webclient.ear\webclient.war\WEB-INF\classes

    You must manually comment out (with a semicolon) every database driver that you are not using. For example, if you are connecting to only Oracle databases, your file would look like this:

    [JDBj-JDBC DRIVERS]
    ORACLE=oracle.jdbc.driver.OracleDriver
    ;AS400=com.ibm.as400.access.AS400JDBCDriver
    ;SQLSERVER=com.microsoft.sqlserver.jdbc.SQLServerDriver
    ;UDB=COM.ibm.db2.jdbc.app.DB2Driver
    

C.4 Path Code Master (F00942)

The Path Code Master (F00942) 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

C.5 Oracle Enterprise Edition

This section discusses these topics:

C.5.1 File Locations

This section discusses the location for these critical files:

C.5.1.1 Oracle Installation Directory

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 is:

C:\Oracle\E1Local

Note:

This location can be changed at installation time.

C.5.1.2 OEE Logs

The following table lists the locations of the various log files.

Log File Location
Import for Planner databases <E1_install_dir>\planner\Data\Imp*.log
Import for Planner specs <E1_install_dir>\planner\spec\Imp*.log
Oracle import log for package specifications (created during Install and also during Package Workbench) <E1_install_dir>\<pathcode>\package\<pkg_name>\Spec\imp*.log and Imp*.log
Oracle export log for specifications (created during Install and also during Package Workbench) <E1_install_dir>\<pathcode>\package\<pkg_name>\Spec\exp*.log and Exp*.log
Local Oracle database runtime C:\Oracle\diag\rdbms\e1local\e1local\alert\
Local Oracle database listener C:\Oracle\diag\tnslsnr\<this_machine>\listener\alert\
Log for ReconfigureDB.exe C:\ReconfigureDB.log
Local Oracle database install logs c:\Program Files\Oracle\Inventory\logs
Log for OEE12Setup.exe c:\OEEInstall.log

C.5.1.3 tnsnames.ora

The tnsnames.ora file is located in these directories:

..\Oracle\E1Local\NETWORK\ADMIN
..\JDEdwards\E920\system\classes\webclient.ear\webclient\WEB-INF\classes

C.5.2 Rebooting the Deployment Server

You must reboot the Deployment Server after installing or deinstalling the local Oracle database.

C.5.3 EnterpriseOne Access to 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:

  • JDESY920

  • JDEOL920

<tablespace_name>

For example:

  • JDESY920

  • JDEOL920

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.


C.5.4 Process Explorer

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:

Surrounding text describes process_explorer.gif.
  1. Navigate to Find > Find Handle or DLL....

    Surrounding text describes proc_expl_full_name_dir.gif.
  2. In the Handle or type field, enter the full name of the directory that cannot be deleted. For example:

    c:\oracle\e1local

  3. Click the Search button.

  4. On the search results screen, note the PID(s) (Process IDs) that are associated with the specified directory.

  5. Cancel the Process Explorer Search window to return to Process Explorer.

  6. 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.

  7. 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.

C.5.5 Verifying the Local Oracle Database Installation

To verify that the installation of the local Oracle database was successful:

  1. Inspect the latest logs in these directories:

    <E1_install_dir>\InstallLogs

    C:\Program Files\Oracle\Inventory\logs

  2. Resolve any issues that are identified in the logs.

C.5.6 Deployment Server Installation Problems

You cannot reinstall the local Oracle database using the Deployment Server installer if there are indications that the local Oracle database already exists. 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

C.5.7 Runtime Problems

This section discusses:

C.5.7.1 Jde.log shows ORA-12541: TNS:no listener

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.

C.5.7.2 User gets a pop-up window prompting for E1Local DB user and password and Jde.log shows OCI0000141 - Error - ORA-01017: invalid username/password; logon denied

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 ReconfigureDB.exe.

If the password was decrypted with ReconfigureDB, you should re-encrypt it using ReconfigureDB.exe. Refer to the sections of this guide entitled: Section C.5.9, "Understanding the ReconfigureDB.exe Program" and Section C.5.10, "Encrypting and Decrypting the Password of the Local Database".

C.5.7.3 tnsnames.ora

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. In order to maintain functionality of the Oracle client, you should add the remote database server tnsnames entries into the tnsnames.ora used by E1Local, which is located in this directory:

<OEE_installation_path>\network\admin

By default, the <OEE_installation_path> is C:\Oracle\E1Local, but the actual value is specified during OEE installation.

C.5.8 Administering the Local Oracle Database Using SQL Plus

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 JDESY920 exists in the E1Local database, use the following to sign in:

SQLPlus.exe JDESY920/JDESY920@E1Local

C.5.9 Understanding the ReconfigureDB.exe Program

The installation of the Deployment Server delivers a utility called ReconfigureDB.exe. This program can be used by a database superuser who for Oracle is the user for the SYSTEM and SYS accounts, while for SQL Server Express (SSE) it is the user of the SA account. Only users of these accounts can encrypt and decrypt the password for the local database on the Deployment Server. Throughout this text, the term local database refers to the database that is installed directly on the Deployment Server. Depending on the release of EnterpriseOne, the supported database could be Oracle or SQL Server Express as specified in the Certifications for JD Edwards EnterpriseOne (refer to Section 1.4.1, "Accessing Certifications" of this guide).

The local database password must be encrypted for JD Edwards EnterpriseOne to run on the Deployment Server. In order to provide security and uniqueness, JD Edwards EnterpriseOne generates this password using a combination of the serial number of the local C drive and a proprietary encryption algorithm. Therefore it is assured that this password will not be the same on different computers.

Tip:

With EnterpriseOne Tools Release 9.2.0.0 and later and an Oracle local database, the method of creating the password changed to produce a more complex and secure password. In these notes and the ReconfigureDB.exe program, the old method is referred to as using Legacy encryption; whereas, the new method uses Enhanced encryption.

Important: Enhanced encryption is applicable only to an Oracle local database when using Tools Release 9.2.0.0 and greater. Legacy encryption is used with an Oracle local database when using Tools Releases prior to 9.2.0.0 or with SQL Server Express (using any supported Tools Release).

Important: Prior to running JD Edwards EnterpriseOne on the Deployment Server, you must ensure that the password of the superuser of the local database is set to the relevant encryption using ReconfigureDB.exe. This is done by selecting a program option appropriate for your database and Tools Release:

  • Enhanced Encryption

    You should use this option with the local Oracle database and Tools Release 9.2.0.0 and greater.

  • Legacy Encryption

    You should use this option with any local database and Tools Releases prior to 9.2.0.0.

    You can also use this option with the SQL Server local database with any supported Tools Release.

Note:

With Tools Release 9.2.0.0 and greater, the program for changing the password of the superuser of the local database is ReconfigureDB.exe. The program allows these password options:
  • Plain Text

  • Enhanced Encryption

  • Legacy Encryption

Prior to Tools Release 9.2.0.0, the comparable program was called ReconfigureMSDE.exe and provided only the options for plain text and (Legacy) Encryption.

The ReconfigureDB.exe program runs in either interactive or silent mode. If no command-line options are given, the program launches a Graphical User Interface (GUI). If any command-line options are specified, the ReconfigureDB.exe program runs silently. In both cases, output from the program is written to this log:

C:\ReconfigureDB.log

You can determine the functionality and command syntax of the ReconfigureDB.exe program by executing the program with either the /? or -H options. For example:

ReconfigureDB.exe /?

or

ReconfigureDB.exe -H

When you execute the command with these options the output is not directed to the console; instead the output is written to this file:

c:\ReconfigureDB.log

The contents of the ReconfigureDB.log file are shown below:

ReconfigureDB.exe
 
1) Changes the password for the database "superusers" for the LOCAL
   EnterpriseOne database.
2) Can change to or from an encrypted password which is needed for E1 to run.
   This password is generated based on the C drive's serial number and then
   encrypted based on E1 proprietary algorithms; hence, this password will not
   be the same on different computers.
3) Can also change to or from user-specified passwords.
4) The program works on the following local databases--and ONLY these
   databases:
    - E1Local
        Type:  Oracle Enterprise Edition (OEE)
        Users: SYSTEM and SYS
    - JDESSELocal
        Type:  Microsoft SQL Server 2005 Express Edition (SSE)
        User:  SA
 
IMPORTANT NOTE:  With EnterpriseOne Tools Release 9.2.0.0 and later, the
                 method of creating the password changed to produce a more
                 complex and secure password.
                 In this program, the old method is referred to as using
                 "Legacy" encryption; whereas, the new method uses
                 "Enhanced" encryption.
 
 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!  IMPORTANT !!! IMPORTANT !!! IMPORTANT !!! IMPORTANT !!! IMPORTANT !!!
!!!  The superuser password must be set to the E1 encrypted password   !!!
!!!  for E1 to work. Select "Enhanced" for Tools Release 9.2.0.0       !!!
!!!  and later. Select "Legacy" for older Tools Releases.            !!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
SYNTAX
  ReconfigureDB [-options] [Old_Password|-E|-L] [New_Password|-E|-L]
 
LOG FILE
- The log file is  C:\ReconfigureDB.log
 
OPTIONS
- May be preceded by either a slash (/) or hyphen (-).
- May be either upper- or lowercase.
- Include one space before the slash or hyphen.
- The order of the options is important. The old password (or option -E or -L)
  must come before the new password (or option -E or -L).
- If  an old password (or option -E or -L) is given, a new password (or
  option -E or -L) must be given.
- If no options are provided, a GUI will prompt for the type of database and
  the passwords.
 
? or -H             - Writes this help to the log file.
                    - Optional.
 
-T[ORACLE|SSE]      - The database server instance type.
                    - Optional. If not specified, the default value is
                      ORACLE.
 
Old_Password|-E|-L  - May be one of the following:
                        1) Old password
                        2) -E  = Indicates that old password was created using
                                 the ENHANCED (i.e., more complex) generation
                                 algorithm.
                        3) -L  = Indicates that old password was created using
                                 the LEGACY (i.e., less complex) generation
                                 algorithm.
 
New_Password|-E|-L  - May be one of the following:
                        1) New password
                        2) -E  = Indicates that new password should be created
                                 using the ENHANCED (i.e., more complex)
                                 generation algorithm.
                        3) -L  = Indicates that new password should be created
                                 using the LEGACY (i.e., less complex)
                                 generation algorithm.
 
EXAMPLE
  In this example, the password for the JDESSELocal database SA user will be
  changed from "MyOldPassword" to a generated password that is then encrypted
  with the new enhanced method:
 
     ReconfigureDB -TSSE MyOldPassword -E

C.5.10 Encrypting and Decrypting the Password of the Local Database

When the local database is Oracle, JD Edwards EnterpriseOne uses an encrypted password to connect to E1Local through the SYSTEM and SYS accounts.

When the local database is SQL Server Express, JD Edwards EnterpriseOne uses an encrypted password to connect to JDESSELocal through the SA account.

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 fails) before it can encrypt the password again, JD Edwards 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, SYS, or SA account password using the following steps for EnterpriseOne to operate correctly.

  1. Launch the ReconfigureDB.exe program located in this directory:

    <E1_install_dir>\system\bin32\ReconfigureDB.exe

    Note:

    You do not have to right click on ReconfigureDB.exe and select Run as administrator. This is because this version of the program is designed to automatically attempt to start with the elevated permissions. If you are not signed into Windows with an administrative account, you will be prompted to enter the credentials for an administrative account.

    If you do not specify any command line options, this program will launch in GUI mode and you can proceed as described in the following steps in this section. Optionally you can use command line options to execute ReconfigureDB.exe .

    Tip:

    For details of syntax and command line options for ReconfigureDB.exe , refer to the preceding section in this document entitled: Section C.5.9, "Understanding the ReconfigureDB.exe Program".
    Surrounding text describes reconfiguredb_main.gif.
  2. On the main ReconfigureDB screen, the Select the local database section lists the types of local databases that are currently installed; options for database types that are not installed will be inactive.

    • E1Local (Oracle Enterprise Edition - OEE)

      This is the only valid option for JD Edwards Applications Release 9.1 (E910) and greater.

    • JDESSELocal (Microsoft SQL Server 2005 Express Edition - SEE)

      You should choose this if the local database is SSE, which is a valid option in JD Edwards Applications Releases prior to 9.1 (E910).

  3. In the Select the action for the E1Local database users section, the first column titled Change from password… indicates the old password; that is, the from password that you want to change. Select one of the available options:

    • A plain text password

      Specify the password in the input field if you know that it was not generated with one of the two types of encryption. For security purposes, your keystrokes are displayed as asterisks.

    • Enhanced Encryption

      Click this radio button if the old password was encrypted with the enhanced encryption that is applicable to a local Oracle database and Tools Release 9.2.0.0 or greater. This option uses an enhanced encryption algorithm (relative to prior releases) providing greater security for the local Oracle database.

    • Legacy Encryption

      Click this radio button if the old password was encrypted with the legacy encryption that is applicable to the local databases which can be either:

      • Oracle on Tools Release prior to 9.2.0.0

      • SQL Server Express on any supported Tools Release

      This option uses an older, less secure encryption algorithm (relative to later releases) providing less security for the local database.

  4. The second column titled To password indicates the new password; that is, to what you want to change the password. Select one of the available options:

    • A plain text password

      Use this option if you do not want to use either of the two types of encryption. For security purposes, your keystrokes are displayed as asterisks.

      Caution:

      If you select the plain text password option, ensure that you re-encrypt the password before attempting to run JD Edwards EnterpriseOne. If the password is not encrypted with the correct type of encryption, JD Edwards EnterpriseOne will fail because it cannot access the local database.

      Note:

      The password cannot contain any spaces. Spaces at the start or end of the password will be removed.
    • Enhanced Encryption

      Click this radio button if the new password will be encrypted with the enhanced encryption that is applicable to a local Oracle database and Tools Release 9.2.0.0. The option uses an enhanced encryption algorithm (relative to prior releases) providing greater security for the local Oracle database.

    • Legacy Encryption

      Click this radio button if the old password will be encrypted with the legacy encryption that is applicable to the local databases which can be either:

      • Oracle on Tools Releases prior to 9.2.0.0

        or

      • SQL Server Express on any supported Tools Release

      This option uses an older, less secure encryption algorithm (relative to later releases) providing less security for the local database.

  5. Click the OK button.

    Surrounding text describes confirm_password.gif.
  6. On Confirm Password, re-enter the password in the New password: field.

    This is to confirm the new password for local database users which are SYSTEM and SYS for an Oracle database and SA for an SSE database.

    The password value cannot contain a space character (blank). Attempting to do so causes this error to be displayed

    Surrounding text describes reconfiguredb_error.gif.
  7. Click the OK button.

    Surrounding text describes success_password.gif.

    A dialog box indicates that the password was successfully changed. Click the OK button to exit the dialog.

  8. Watch the status bar at the bottom of the dialog for informational messages.

Tip:

If changing the password fails, look in this log file for additional information:

C:\ReconfigureDB.log

Also, ensure you are using the correct password as perhaps the password you are trying is not what you thought it was.

If neither of the above helps resolve a password failure, attempt to stop and restart these database services:

Oracle Database

  • OracleServiceE1LOCAL

  • OracleE1LocalTNSListener

SSE Database

  • JDESSELOCAL

After the database services are stopped and restarted, you can retry ReconfigureDB.exe.

C.5.11 Import and Export Tablespaces to the Local Oracle Database

You can use the JD Edwards EnterpriseOne application P96717 to import and export tablespaces except the Planner. 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

For local metadata repository database (for example, specs and serialized objects):

<E1_install_dir>\planner\spec

This section discusses:

C.5.11.1 Import Tablespace Script (attach_planner.bat)

To use the import tablespace script:

  1. Navigate to the directory JDEdwards\E920\planner\data and run this script:

    TestPlannerDBs.bat

  2. 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 %DATA_PATH%\IMPORT_TABLESPACE.BAT

  3. Open a command prompt window by right-clicking on a Command Prompt shortcut and selecting Run as administrator.

  4. Change directory to the location of the batch files.

  5. Run the batch file to import the tablespace using this syntax:

    attach_planner.bat <database_password> <E1_install_dir>

    For example:

    attach_planner.bat default c:\JDEdwards\E920

    Note:

    This import batch file for the local metadata repository is in the spec directory:

    attach_metadata.bat

C.5.11.2 Export Tablespace Script (detach_planner.bat)

To use the export tablespace script:

  1. Edit the jdedwards\E920\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 %DATA_PATH%\EXPORT_TABLESPACE.BAT

  2. Open a command prompt window by right-clicking on a Command Prompt shortcut and selecting Run as administrator.

  3. Change directory to the location of the batch files.

  4. Run the batch file to import the tablespace using this syntax:

    detach_planner.bat <E1_install_dir>

    For example:

    detach_planner.bat c:\JDEdwards\E920

    Note:

    This export batch file for the local metadata repository is in the spec directory:

    detach_metadata.bat

C.5.12 Updating the InstallManager.htm File

To install a database or the Development Client onto a Development Client machine, the user runs this program:

\\<deployment server name>\<release>\OneWorld Client Install\InstallManager.exe

This program displays a Graphical User Interface that provides several options for the user to perform. The options that InstallManager.exe displays are read from the file InstallManager.htm that resides in the same directory as InstallManager.exe.

The JD Edwards EnterpriseOne administrator can edit this file to rename the options or to add new options. Instructions are inside the file.

Caution:

Although InstallManager.htm is in HTML format, it is a restricted HTML that the InstallManager.exe can read. Some text file editing programs add extraneous HTML tags that InstallManager.exe cannot recognize.

The Microsoft Windows program Notepad.exe is an example of a program that is known to not add these extra tags, making it safe to use. Before you make any changes to the file, it is good practice to save a copy in case any changes that you make are not recognized by InstallManager.exe when it reads it.

Note that the installation path of the Development Client's installer (setup.exe) changed with Tools Release 9.1. This means that you will need to change the path of the Development Client's installer in the InstallManager.htm when you first install Tools Release 9.1 and greater onto a Deployment Server that has a tools release prior to 9.1 installed.

The following is an example of a line in a pre-9.1 InstallManager.htm that creates the link to install the Development Client (this should be on a single line):

<a class="sectionItem" id="LaunchLink" link="setup.exe" href="InstallManager.htm">EnterpriseOne Client</a>

The Development Client's installer prior to Tools Release 9.1 is called setup.exe. It should be in the same directory as InstallManager.exe and InstallManager.htm. The value of the link in the above line should be a path and executable for the installer. If a relative path is used (for example, the path starts with neither a drive letter followed by a colon nor a backslash), the path is relative to the location of InstallManager.exe. If no path is given, Setup.exe and InstallManager.exe are in the same directory.

Here is an example of a similar line for Tools Release 9.1 and greater (this should be on a single line):

<a class="sectionItem" id="LaunchLink" link="install\setup.exe" href="InstallManager.htm">EnterpriseOne Client</a>

Note the addition of this relative path: install. With Tools Release 9.1 and greater, the Development Client's installer (which, is also called setup.exe) is now located in a subdirectory called install under the path where InstallManager.exe resides.

C.5.13 Deployment.inf and <Package_name>.inf

The following lists specific settings within the Deployment.inf and <Package_name>.inf for OEE.

  • Deployment.inf

    [ThirdPartyApps]ORACLE=ThirdParty\ORACLE\OEE12Setup.exe,
    
  • <Package_name>.inf (example from a DV920FA.inf file)

    [Oracle Databases]
    JDELocal_DV920=ORACLE
    SPEC_DV920FA=ORACLE
     
    [JDELocal_DV920]
    SourceTableSpace=JDELocal
    Server=127.0.0.1
    UserID=SYSTEM
    DataFileDestDir=$DDV920DATA\JDELocal_DV920.dbf
    DumpFileDestDir=$DDV920DATA\JDELocal_DV920.dmp
     
    [SPEC_DV920FA]
    SourceTableSpace=SPEC_DV920FA
    Server=127.0.0.1
    UserID=SYSTEM
    DataFileDestDir=$DDV920\Spec\SPEC_DV920FA.dbf
    LogFileDestDir=$DDV920\Spec\SPEC_DV920FA.dmp