Gateway Service Installation - Common Functionality
Double click on the installation executable to begin the installation.
The Installer creates a new user account called JDEDIRECT_SERV on the GATEWAY machine and sets the required rights.
The gateway service installation is the same for any version of JDE OneWorld and is detailed below from the 'Welcome to Gateway Service Configuration Tool' wizard appearing.
Note: For a successful information of the Gateway Service you will need:
| 1. | Details of the location of the .INI files for the Enterprise Server. |
| 2. | DB User ID |
| 3. | DB Password |
| 4. | JDE User ID |
| 5. | JDE User Password |
| 6. | Operating Environment |
| 7. | Access to the JDE Enterprise E1 Server 'Classes (.jar) Files' |
| 8. | ptf.log file details if running versions Xe or ERP8 of JDEdwards OneWorld or E1. |
Select Next to display the jde.ini file input screen.
If you know the location (route) to the required .ini files, then it may be entered here.
If the location is not known, then 'Browse' the file and highlight.
Highlight the required file and then select 'Open'.
This returns the jde.ini file details to the input screen and defines the JDE version to use.
Select 'Next' to show a screen that allows Users to input a 'Service description'. This may be up to 255 characters and will be visible for output in the Gateway Service Manager Control panel.
This may be left blank. If no description is entered the system will enter a default. See an example in the Gateway Service Manager section.
Having entered a service description (or not), on 'Next' the Get Service Pack/Tools release information screen or Database Security login screen appears depending which version of jde OneWorld you are running (as defined by the jde.ini files earlier). If version Xe or ERP8 then the ptf.log screen appears and requires details of the log file to be entered to define the Service Pack in use. Follow the screen instructions to find the route to the required .log file.
If running jde OneWorld 8.9, 8.10, 8.11 or 8.12 then the .log screen will not appear and the Database login screen appears.
In Release 2.0.4.7 of the ODBC driver a new Remember Passwords checkbox was added. This is checked by default and if left, both passwords will be remembered. If you do not want the system to remember your passwords then uncheck this option.
Enter your Database Login Details, and JDE Login details as requested:
Database Login Details
Data Source Name: Pre filled on entry
Database: Pre filled on entry
DB User ID: Blank on initial entry. Enter a valid DB User ID
DB Password Blank on initial entry. Enter a valid DB password
JDE Login Details
JDE User ID: Blank on initial entry. Enter a valid JDE User ID
JDE Password: Blank on initial entry. Enter a valid JDE password
Environment: Blank on initial entry. Enter a valid JDE Environment
As stated above these entries must exist in the F98OWSEC table.
If you do not know the required System Security details, then consult your SYSTEMS ADMINISTRATOR now...
Once all details have been entered select Next to continue to the User login validation method screen. However, if an entry is incorrect you may get the following 'Warning'!
A login problem has been encountered. Select OK and check and re-enter all login details. On successful entry of Login Details, the Copy Class files for Java Connector screen appears.
If a Fat Client was NOT installed on the service machine then the 'Alternative, use the Fat Client on the system for E1 user login validation' check box and option would not appear. In this case the Java Connectors will be used for use authentication. Follow the steps detailed in Java Connector Installation Route.
In this case a Fat Client has been installed on the service machine and so the option now exists as to how you wish to authenticate User login details; by the java connector (The Default) or Fat Client? It is recommended that the Java Connector route is used as this considerably speeds up authentication, but the Fat Client route is available once on the service.
If you have multiple releases of E1 running (i.e. Xe, and E811prod and E811Dev) then it is now possible to have a multiple services set up on one PC but the Fat Client authentication route may be taken once only.
If the first installation of the service uses the Fat Client route then on the next application this check box and option will not appear.
For details of the Java Connector Route see at (Non FC) Java Connector Installation Route.
For details of the Fat Client installation route see at Fat Client Installation Route.