This chapter contains the following topics:
Section 8.4, "Copying the JDBC drivers to the Client Install Directory"
Section 8.8, "Working with the Workstation JDE.INI on the Deployment Server"
Release 9.0 software is first installed on the Deployment Server, and then deployed from the Deployment Server to developer and system administrator workstations. The workstation installation can occur using either interactive mode, silent mode, or push mode. Push mode is described in the JD Edwards EnterpriseOne Tools Package Management Guide.
The workstations for developers and system administrators are Microsoft Windows-based machines. Refer to the Section 1.3, "Accessing Minimum Technical Requirements" for specifically-supported versions of Microsoft Windows.
Note:
The JD Edwards EnterpriseOne 9.0 Installation delivers pre-built packages that are ready for use as delivered. For the workstation to reflect the language installed on the Deployment Server, you must perform tasks for both the Enterprise Server and workstations, in addition to the procedures to verify and modify the JDE.INI on the workstations and the JDE.INI on the Enterprise Server.See Also
JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries in the chapter entitled: Language Process Overview for more information about how you enable multilingual installations on workstations.
To prepare for the installation of Release 9.0 on individual workstations, you must modify the workstation JDE.INI on the Deployment Server and the JD Edwards EnterpriseOne system administrator must create a user profile for every user before that user can log on to Release 9.0. You must also copy the configured tnsnames.ora from the oracle\E1local directory to the \client directory on the Deployment Server, as specified in the next section of this guide entitled: Section 8.3, "Copying the Configured tnsnames.ora File".
The workstation installation program copies all necessary components of Release 9.0 to a workstation. During installation, the installation program verifies that enough disk space exists and, if not, you are prompted to create more space before continuing.
Note:
Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for Oracle Application Server (OAS) and WebSphere Application Server (WAS) Express for additional details on installing the Development Client.Prerequisites
Before installing Release 9.0 on a workstation used for development, you must install the Microsoft Visual C++ Compiler. The specific version of the compiler is detailed in Accessing Minimum Technical Requirements. Also refer to the appropriate Microsoft documents for installation information.
The names of the Deployment Server, Enterprise Server, and client workstation cannot exceed 15 characters in length.
Note:
Note: You do not need full administrator privileges to install Release 9.0 on the workstation. However, you do need proper privileges for writing to the disk and the registry. If you do not have these privileges, you will receive a warning during the installation. If you receive a warning, contact your administrator, who can perform the installation or can grant proper disk and registry access.For more information about granting disk and registry access, see the section entitled: Granting Disk and Registry Access for Microsoft Windows Workstations in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide for iSeries.
During workstation installation, connectivity is required for:
Read/write access to this client install directory on the primary Deployment Server in the base location:
\oneworld
Read access to the subdirectories located under this directory:
\pathcode\package
For example:
\\deployment_server_name\E900\PD900\package
Read/write access to this directory on the primary Deployment Server:
\client
For example:
\\deployment_server_name\E900\client
Use this procedure to ensure the Client Installer and the OH4A installer are using the correct the tnsnames.ora file.
To copy the configured tnsnames.ora file:
On the Deployment Server, drill down to this folder:
oracle\E1Local\NETWORK\admin
Locate the tnsnames.ora file in the above folder and copy it to this folder:
\\deployment_server_name\E900\client
When prompted whether to overwrite the existing file, you must choose to overwrite it.
When you ran the Deployment Server installer it copied the Oracle JDBC driver to this directory:
x:\JDEdwards\E900\OneWorld Client Install\ThirdParty\WebDevFeature\JDBC
You must also copy the IBM i JDBC driver (jt400.jar) to this same location.
As with the JDBC drivers, you must store the correct version of JDK in a defined directory on the Deployment Server. This application is then automatically downloaded to the Development Client during the installation process. To set up this process, the administrator must first obtain the required JDK from Sun Microsystems and copy this application to the Deployment Server as described below.
On the Deployment Server, create a directory called \JDK under the folder that contains the Development Client installation program. For example:
OneWorld Client Install\ThirdParty\WebDevFeature\JDK
Refer to Section 1.3, "Accessing Minimum Technical Requirements" to determine the correct JDK required for this installation.
Locate and download the appropriate JDK from the Sun web site. In some cases you must select a Previous Release hyperlink to download older Java versions.
http://www.oracle.com/technetwork/java/javase/downloads/index.html
The JDK may be called Java 2 Platform, Standard Edition (J2SE) for Windows or just J2SE.
Note:
Do not install a JDK with a version higher than what is indicated in the MTRs for the Development Client unless instructed to do so by JD Edwards EnterpriseOne support.Save the JDK to a temporary directory.
From Windows Explorer, navigate to the temporary directory and run the executable program as an administrator.
Click Next.
Select Accept and click Next.
Click Change, and select the \JDK directory you created in Step 1.
Accept all other default values, and click Next.
Deselect both Browse Registration options.
Click Install.
The installation process takes several minutes.
When the process is complete, click Finish.
The workstation installation program copies all necessary components of Release 9.1 to a workstation. During installation, the installation program verifies that enough disk space exists and, if not, you are prompted to create more space before continuing.
Caution:
Before starting a JD Edwards EnterpriseOne workstation installation, you must close all other applications running on that machine. The installation process may not run correctly if other applications are open.This section discusses these topics:
A system administrator can create a shortcut to InstallManager.exe from the JD Edwards EnterpriseOne client install directory on the Deployment Server and can deploy the shortcut to the workstation. For example, the client install directory is typically:
\JDEdwards\E910\OneWorld Client Install
To ensure that the shortcut works correctly, ensure the Start in: field contains the location of the installmanager.htm file.
To create a desktop shortcut:
To edit the Start in: field, in Microsoft Windows Explorer or on the desktop, right-click the shortcut.
Click Properties, and then click the Shortcut menu.
Double-click the Release 9.1 InstallManager shortcut to start the Release 9.1 installation manager.
Skip to the next task entitled: Section 8.6.2, "Using a Shared Drive".
An installer can connect to the\JDEdwards\E910 shared drive on your Deployment Server from Microsoft Windows Explorer.
To use a shared drive:
Double-click InstallManager.exe to start the Release 9.1 installation manager.
The InstallManager.exe file is located in this folder:
OneWorld Client Install
On JD Edwards EnterpriseOne Release 9.1 Installation Manager, click Workstation Install.
On Client Workstation Setup, click Next.
If you do not have the latest version of Microsoft Internet Explorer the Release 9.1 Client Workstation Setup Third Party Application form appears. The option to install Internet Explorer is selected. To install this application, click Next. If you do not want to install these applications at this time, clear the option for one or both of them, and click Next.
If the latest version of Internet Explorer are already installed, the Third Party Application form is not displayed.
On Client Workstation Setup Package Selection, select the package you want to install and click Next.
Tip:
Click the Filters ON button to narrow the displayed list of available packages. This can help you find the package you want. Notice that a short description of each package appears below the list.On Client Workstation Setup Type, complete these fields:
| Field | Description |
|---|---|
| Select Setup Type | Select Development or Production objects. You should only select the Development option if you intend to develop Release 9.1 applications.
Note: Select the Development option only if you intend to develop JD Edwards EnterpriseOne applications. |
| Install Path | Select the drive and directory in which to install the package. For example, this is the typical path for Release 9.1:
|
To install the package, click Finish.
InstallManager shows the status of the installation process through a series of forms.
The Congratulations form indicates that the installation finished successfully. InstallManager creates a Release 9.1 shortcut in the Programs folder of your Start menu and on your desktop.
Reboot if necessary.
Caution:
The JD Edwards EnterpriseOne client workstation installation process verifies that several of the system DLL files are current. If they are not current, you receive a message to reboot your system. When you reboot, the system updates the DLL files in your Microsoft Windows directories.A local Oracle Enterprise Edition (OEE) is required for Release 9.1 Workstations (Development Clients). The OUI installer for the Development Client installs OEE and the Development client separately. Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for Oracle Application Server (OAS) and WebSphere Application Server (WAS) Express.
The use of Microsoft Internet Explorer is optional. Adobe Acrobat Reader 6.0 or greater is strongly recommended to view reports online. Neither the browser or reader applications are delivered with the JD Edwards EnterpriseOne Applications Release 9.1 installation.
Microsoft Internet Explorer provides:
An option for a Web-like menu view within JD Edwards EnterpriseOne Explorer.
An option for an Internet connection capability directly from the JD Edwards EnterpriseOne Explorer interface.
The use of Microsoft Internet Explorer is optional. Adobe Acrobat Reader 6.0 or greater is strongly recommended to view reports online. Neither the browser or reader applications are delivered with the JD Edwards EnterpriseOne 9.0 Installation.
Microsoft Internet Explorer provides:
An option for a Web-like menu view within JD Edwards EnterpriseOne Explorer.
An option for an Internet connection capability directly from the JD Edwards EnterpriseOne Explorer interface.
This section discusses:
Section 8.8.1, "Understanding the Workstation JDE.INI on the Deployment Server"
Section 8.8.2, "Modifying the Workstation JDE.INI on the Deployment Server"
To facilitate the administration and maintenance of the JDE.INI for multiple client workstations, all instances of the JDE.INI are stored on the Deployment Server. To make a change to a JDE.INI for a workstation, change the original file on the Deployment Server. The file is then copied from the Deployment Server to its respective workstation during the Development Client installation process.
This task describes modifications required to make to the workstation JDE.INI before installing Release 9.0 on the workstation.
When using a double-byte language, modify the ODBCDataSource.inf on the Deployment Server by adding this value to all ODBC Data Sources:
DBCSNoTruncErr=1
Important:
If the ODBC Data Sources do not have this registry value on the workstations, some records will not be inserted into tables and Insert Record Failed errors will appear.Use this procedure to modify settings in the JDE.INI in this directory on the Deployment Server:
\JDEdwards\E900\OneWorld Client Install\Misc
To modify the workstation JDE.INI on the Deployment Server:
Open the workstation JDE.INI and modify these settings:
Note:
For language installations, ensure that the workstation is set up correctly for language preferences to display and print forms. If multiple languages are installed, verify that the appropriate JDE.INI values are set to your preferred language. See for appropriate values.| Setting | Description |
|---|---|
[INTERACTIVE RUNTIME] |
For the language you are installing, enter:
Initial_Language_Code = x where x is the value for the language installed or, if multiple languages are installed, for the preferred language. |
[INSTALL] |
Verify that the LocalCodeSet value and code page setting are set to the appropriate values. The system reads the JDE.INI setting for the installed language. |
[JDENET] |
Verify that the port number specified for ServiceNameListen and ServiceNameConnect matches the port number in the Enterprise Server JDE.INI. |
Save and close the file.