This chapter discusses these topics:
This article explains how to use the Heroku Local CLI plugin. Run your app locally using the Heroku Local command line tool. Heroku Local is a command-line tool to run Procfile-backed apps.It is installed automatically as part of the Heroku CLI.Heroku Local reads configuration variables from a.env file.Heroku Local makes use of node-foreman to accomplish its tasks.
Development workflow for Docker apps.; 25 minutes to read +2; In this article. The application development life cycle starts at your computer, as a developer, where you code the application using your preferred language and test it locally. Mar 19, 2019 Code anywhere: Code on your Chromebook, tablet, and laptop with a consistent dev environment. Develop on a Linux machine and pick up from any device with a web browser. Server-powered: Take advantage of large cloud servers to speed up tests, compilations, downloads, and more. Preserve battery life when you're on the go since all intensive computation runs on your server.
3.1 Understanding the JD Edwards Clients (Development and Web)
The JD Edwards EnterpriseOne Development Client (also known as a Web Development Client, 'Fat' Client, Administrative Client, Windows client, or Workstation) contains components that run as standard Microsoft Windows applications (for example, Active Console, Forms Design Aid (FDA), and Report Design Aid (RDA)) and components that run in a web browser.
Note:
This document uses the following terminology when discussing JD Edwards EnterpriseOne clients:
The Web Client part of the Development Client runs inside an Application Server. The supported Application Servers are:
The Oracle Application Server is included as part of the JD Edwards EnterpriseOne system code and is automatically configured to work with the Web Client when you install the Web Client for OAS. This version of the Web Client is known by any of the following names:
Although OAS is included with JD Edwards EnterpriseOne system code, you can choose to use WAS Express or WAS for Developers as the Application Server for the EnterpriseOne Web Client. Both products are similar; either one may be manually installed before installing the Web Client for WAS. Whereas WAS Express requires a licensing fee to IBM, WAS for Developers is free. The version of the Web Client that is installed on either WAS product is referred to by either of these names:
This chapter describes the first time setup of the JD Edwards EnterpriseOne Development Client installer and installation package on an EnterpriseOne Deployment Server. This setup on the Deployment Server must be done before a user can install a JD Edwards EnterpriseOne Development Client on a workstation. The installation package specifies the components to install and may or may not include the Web Client.
For instructions on how to install Web Clients for both Application Servers: OH4A and H4A7/H4A85, as well as the installation of WAS 7/8.5 Express or WAS 7/8.5 for Developers, refer to the JD Edwards EnterpriseOne Development Client Installation Guide.
3.2 Understanding the Oracle Universal Installer
As of Tools Release 9.1, the Development Client is installed using the Oracle Universal Installer (OUI). In addition, the Web Client is installed as a package feature using OUI. When you run the 9.1 Tools Release installer on the Deployment Server, it copies the OUI installers for the Development Client and Web Client to the correct location on the Deployment Server. The location of the Development Client installer is:
<deployment server name><release>OneWorld Client Install
Underneath this directory are the following. Only noteworthy files and directories are listed. Those under ThirdParty may or may not exist depending on which features are defined.
Note:
Any combination (or all) of the Web Client installers may exist on the Deployment Server; however, an installation package may contain only one Web Client installer (as a feature). Likewise, only one Web Client may be installed on a Development Client.
The installers do not prevent you from installing more than one type of Web Client on a Development Client, but unexpected results may occur if you attempt this.
3.3 Creating the Web Development Feature
Complete this task to create a Web Client Installation Feature for your version of the application server. This feature must be included in the installation package before it is deployed to the Web Client machine.
3.4 Creating an Installation Package
This task describes how to add a Web Client Installation Feature to an installation package.
3.5 Copying JDBC Drivers and the tnsnames.ora file to the Deployment Server
Required JDBC drivers and the
tnsnames.ora file are automatically downloaded from the Deployment Server to the Development Client during the installation of the Development Client. To set up this process, the administrator must first obtain the required JDBC drivers for the supported platforms and databases as well as the tnsnames.ora file, if connecting to an Oracle database, and copy them to the Deployment Server as described in this procedure.
This section describes these tasks:
3.5.1 Copy the JDBC Drivers
To copy the JDBC drivers:
3.5.2 Copy the tnsnames.ora file
The
tnsnames.ora file is required only if the Development Client will connect to an Oracle database. However, if the tnsnames.ora file is not copied to the correct directory on the Deployment Server, the user will receive an error message during the Web Client installation process.
To copy the
tnsnames.ora file:
3.6 Updating the Database Drivers in the JDBJ.ini File
The Web Client installer updates the
JDBJ.ini file with settings for the databases to which the Web Client will connect based on the JDBC database drivers found in this directory:
<Client Install Path>misc
As noted in the preceding section of this chapter entitled: Section 3.5.1, 'Copy the JDBC Drivers', these JDBC database drivers are copied from this directory:
<deployment server name><release>OneWorld Client InstallThirdPartyWebDevFeature<OH4A_or_H4A7_or_H4A85>JDBC
Note:
If you copy additional database drivers into the <Client Install Path>misc directory after installing OH4A, H4A7, or H4A85, you will need to update the list of drivers in the JDBJ.ini file.
To update the database drivers in the
JDBJ.ini file:
3.7 Copying the JDK to the Deployment Server (OH4A Only)
As with the JDBC drivers, you must store the correct version of JDK in a defined directory on the Deployment Server. The JDK is then automatically downloaded to the Web Client during the installation of the OH4A Web Client. (For H4A7 and H4A85, the JDK is installed when you install WebSphere Express or WebSphere for Developers.) To set up this process, the administrator must first obtain the required JDK from Oracle and copy this application to the Deployment Server as described in the following procedure.
Note:
These instructions refer to a JDK (Java Developers Kit) -- not a JRE (Java Runtime Environment). These terms refer to distinctly different products that should not be confused. A JDK contains a JRE plus other components. A specific JDK is an MTR that is required by the Web Client.
Note:
If you have to copy the JDK files to a different directory for some reason, you have to add an entry to the oraparam.ini file for the OH4A installer to indicate the location of that JDK directory. Edit the oraparam.ini file located in this directory:
<deployment server name><release>OneWorld Client InstallThirdPartyWebDevFeatureOH4AInstall
Deployment Server For C Code From Local To Device
Add this entry to the
[FileLocations] section of the oraparam.ini file:
The path should be the parent directory of the
bin directory that holds the javac.exe program. Be sure this path can be reached by the installer as it runs on the target Web Client machine. For example, if the javac.exe resides in depsvr2E910My_JDKbin , enter the following in the [FileLocations] section of the oraparam.ini file:
Note:
If you do not add the entry described in the preceding note, the OH4A installer looks for the JDK directory up one level from the setup.exe program for OH4A.
3.8 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 InstallInstallManager.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 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 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 (this should be on a single line):
<a link='installsetup.exe' href='InstallManager.htm'>EnterpriseOne Client</a>
Note the addition of this relative path:
install . With Tools Release 9.1, 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.
3.9 Updating the oraparam.ini File
The OUI installer reads installation parameters from the
oraparam.ini file. This file resides with the OUI executable called setup.exe in this directory:
<deployment server name><release>OneWorld Client Installinstall
When initially updating a Deployment Server to Tools Release 9.1, the
oraparam.ini file is not updated from the existing install.inf file. Therefore, you must manually update some settings in the oraparam.ini file as described in this section.
The
oraparam.ini file follows the standard format of ini files for Microsoft Windows: it contains sections with names inside square brackets ( [ ] ) and key/value pairs. The keys and their values are separated by equals signs ( = ).
If the following section or keys do not exist in your
oraparam.ini , you must add them along with the values indicated. Be sure that any paths can be reached by the OUI program that is running on the machine where the Development Client is being installed; that is, do not use local paths -- use paths of this form:
<deployment server name><release>xxx
3.10 Setting Up Local Database Installers
The Development Client requires a database to be installed onto the same machine on which the Development Client is to be installed. You can choose the database based on the Applications Release of E1 and 'bitness' of the Windows operating system that your users are using. Do not take the following information for granted - you should always check the MTRs for the most current official information.
Deployment Server For C Code From Local To Devil
To install a database onto a Development Client machine, the user runs this program:
<deployment server name><release>OneWorld Client InstallInstallManager.exe
This program allows the user to install a local database or the E1 Development Client. By default, the
InstallManager.htm file is shipped from Oracle configured to install OEE.
This section describes these topics:
3.10.1 Additional OEE Setup
The main installation program for OEE is
OEESetup.exe . Upon initial installation of Tools Release 9.1, this directory is created:
<deployment server name><release>OneWorld Client InstallThirdPartyORACLE
The installation delivers these files in the above directory:
The above files can be used for both 32- and 64-bit versions of the database and for 11gR2 and 10g versions.
You must manually copy the E1Local cloned database to this directory:
Deployment Server For C Code From Local To Devices<deployment server name><release>OneWorld Client InstallThirdPartyORACLE
This cloned database can be downloaded from the Oracle Software Delivery Cloud site or the JD Edwards Update Center. Available versions of the database include 32- and 64-bit. You should choose the bitness of database that is applicable to your end-user versions of Microsoft Windows.
Inside the zip files that you download are files containing the cloned database. These internal files are called
E1Local.cab , E1Local2.cab , through E1Local15.cab . The names are the same for both 32- and 64-bit versions of the database, so be sure to keep them separated.
If some users require 32-bit and others require 64-bit versions of the database, follow these steps:
3.10.2 SSE Setup
If you want users to install SSE as the local database for the Development Client, you must change the installer option in the
InstallManager.htm file to point to the SSE database installer. You should also refer to the complete instructions on editing the InstallManager.htm file in the section of this guide entitled: Section 3.8, 'Updating the InstallManager.htm File'.
To setup the
InstallManager.htm file to install the SSE local database for the Development Client:
Follow these steps to download the installer for the database and the installer for the .NET Framework from Microsoft.
Note:
If the JD Edwards EnterpriseOne MTRs specify a higher version of the database, use the MTRs in the following instructions.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |