JD Edwards EnterpriseOne

HTML Server on WebLogic Reference Guide

Release 9.1 for Microsoft Windows

E18840-13

August 2017

Provides reference material for the JD Edwards EnterpriseOne HTML Server on WebLogic.

JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide, Release 9.1 for Microsoft Windows

E18840-13

Copyright © 2009, 2017, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Accessing Certifications (formerly Minimum Technical Requirements)

2 Understanding Server Manager and This Guide

3 Installing and Configuring Oracle WebLogic 12.1.3

- 3.1 Overview

- 3.2 Downloading Oracle WebLogic 12.1.3 from the Oracle Software Delivery Cloud

- 3.3 Before You Begin

- 3.3.1 64-Bit Support - General

- 3.3.2 64-Bit - JDK

- 3.3.3 System Requirements

- 3.3.4 Installation Considerations

- 3.4 Installing and Verifying the JDK Version

- 3.5 Installing Oracle WebLogic 12.1.3

- 3.6 Using Fusion Middleware Configuration Wizard to Configure Oracle WebLogic 12.1.3

4 Installing and Configuring
Oracle WebLogic 12.1.2

- 4.1 Overview

- 4.2 Downloading Oracle WebLogic 12.1.2 from the Oracle Software Delivery Cloud

- 4.3 Before You Begin

- 4.3.1 64-Bit Support - General

- 4.3.2 64-Bit - JDK

- 4.3.3 System Requirements

- 4.3.4 Installation Considerations

- 4.4 Installing and Verifying the JDK Version

- 4.5 Installing Oracle WebLogic 12.1.2

- 4.6 Using Fusion Middleware Configuration Wizard to Configure Oracle WebLogic 12.1.2

5 Installing and Configuring Oracle WebLogic 10.3.6.0

- 5.1 Overview

- 5.2 Downloading Oracle WebLogic 10.3.6.0 from the Oracle Software Delivery Cloud

- 5.3 Before You Begin

- 5.3.1 64-Bit Support - General

- 5.3.2 64-Bit - JDK

- 5.3.3 System Requirements

- 5.3.4 Installation Considerations

- 5.4 Installing and Verifying the JDK Version

- 5.5 Installing Oracle WebLogic 10.3.6.0

- 5.6 Using QuickStart to Configure Oracle WebLogic 10.3.6.0

- 5.7 Post Installation and Configuration

6 Installing and Configuring Oracle WebLogic 10.3.5.0

- 6.1 Overview

- 6.2 Downloading Oracle WebLogic 10.3.5.0 from the Oracle Software Delivery Cloud

- 6.3 Before You Begin

- 6.3.1 64-Bit Support - General

- 6.3.2 64-Bit - JDK

- 6.3.3 System Requirements

- 6.3.4 Installation Considerations

- 6.4 Installing and Verifying the JDK Version

- 6.5 Installing Oracle WebLogic 10.3.5.0

- 6.6 Using QuickStart to Configure Oracle WebLogic 10.3.5.0

7 Preparing the WebLogic Server for JD Edwards EnterpriseOne HTML Server Installation

- 7.1 Start the WebLogic Administration Console

- 7.1.1 Creating a boot.properties File for User and Password

- 7.1.2 Adding WebLogic Admin Server or Managed Server Process to Windows Services

- 7.1.3 Creating a Process to Remove the WebLogic Admin Console from the Windows Services

- 7.2 Start the Node Manager Manually

- 7.3 Enable Node Manager as a Windows Service

- 7.4 Create the Machine Definition

8 Upgrading to WebLogic Server 10.3.6.0

- 8.1 Before You Begin

- 8.2 Installing and Verifying the JDK Version

- 8.3 Running OUI to Upgrade an Existing WebLogic Server to 10.3.6

9 Upgrading to WebLogic Version 10.3.5.0

- 9.1 Before You Begin

- 9.2 Installing and Verifying the JDK Version

- 9.3 Running OUI to Upgrade an Existing WebLogic Server to 10.3.5

10 Understanding EnterpriseOne HTML Server Package Discovery

- 10.1 Impacts to End Users

- 10.2 Understanding the Manifest

11 Uninstalling or Deinstalling WebLogic

- 11.1 Uninstalling WebLogic 10.3.5.0 or 10.3.6.0

- 11.2 Deinstalling WebLogic 12c

A Generating JD Edwards EnterpriseOne Serialized Objects

- A.1 Installing eGenerator

- A.1.1 Prerequisites

- A.1.2 Installing the Generator Program (JD Edwards EnterpriseOne 8.9 only)

- A.1.3 Setting the Default Storage Parameter (SQL only)

- A.1.4 Preparing JD Edwards EnterpriseOne for Serialized Objects

- A.2 Logging In

- A.2.1 Running the eGenerator Diagnostic Tool

- A.2.2 Generate to the Web Server

- A.2.3 Bypass the Web Server and Generate Serialized Objects Directly to the Serialized Object Tables

- A.3 Configuring eGenerator

- A.3.1 Setting eGenerator Options

- A.3.1.1 Generation Modes

- A.3.1.1.1 Sequential Generation

- A.3.1.1.2 Parallel Generation

- A.3.2 Choosing Languages

- A.3.3 Configuring the genapp.ini File

- A.4 Generating the Serialized Object Manifest

- A.5 Generating an FDA-Created Portlet

- A.6 Generating All Standard Serialized Objects

- A.7 Generating a List of Objects (Bulk Generation)

- A.8 Verifying the Generation Process

- A.8.1 Checking Log Files

- A.8.2 Checking Database Acknowledgements

- A.9 Generating Other Selected Objects Using JD Edwards EnterpriseOne 8.12

- A.9.1 Generating Core Objects

- A.9.2 Generating Applications

- A.9.3 Generating Forms

- A.9.4 Generating Reports

- A.9.5 Generating NERs

- A.9.6 Generating Data Dictionary Items

- A.9.7 Generating Tables

- A.9.8 Generating Business Views

- A.9.9 Generating Data Structures

B Understanding Media Objects on the Web Server

- B.1 Required jas.ini Settings

- B.2 How Media Objects are Displayed by the HTML Server

Preface

Welcome to the JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide.

Note:
This guide has been updated for JD Edwards EnterpriseOne Tools Release 9.1 Update 5. For details on documentation updates, refer to the JD Edwards EnterpriseOne Tools Net Change for Tools Documentation Library.

Audience

This guide is intended for system administrators and technical consultants who are responsible for installing and configuring JD Edwards EnterpriseOne.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

You can access related documents from the JD Edwards EnterpriseOne Release Documentation Overview pages on My Oracle Support. Access the main documentation overview page by searching for the document ID, which is 876932.1, or by using this link:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=876932.1

This guide contains references to server configuration settings that JD Edwards EnterpriseOne stores in configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, and so on). Beginning with the JD Edwards EnterpriseOne Tools Release 8.97, it is highly recommended that you only access and manage these settings for the supported server types using the Server Manager program. See the JD Edwards EnterpriseOne Server Manager Guide.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Accessing Certifications (formerly Minimum Technical Requirements)

Customers must conform to the supported platforms for the release as detailed in the Certifications for JD Edwards EnterpriseOne. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the following link for cross-reference material in the Program Documentation for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.

http://www.oracle.com/corporate/contracts/index.html

Access the Certifications from My Oracle Support (https://support.oracle.com) by searching for this product from the Certifications tab:

- JD Edwards EnterpriseOne HTML Server

2 Understanding Server Manager and This Guide

Beginning with JD Edwards EnterpriseOne Tools Release 8.97, a new tool called Server Manager is provided. This tool is a complete replacement for the JD Edwards EnterpriseOne legacy management and installation tools including internal components known as Server Administration Workbench (SAW), Server Management Console (SMC), and the InstallShield based installers previously used to install or upgrade JD Edwards EnterpriseOne servers. As a result, you should refer to the JD Edwards EnterpriseOne Server Manager Guide for details on installing and configuring all JD Edwards EnterpriseOne server products, with the exception of the JD Edwards EnterpriseOne Deployment Server, whose installation is described in this guide. This guide only contains reference information for functionality outside the Server Manager tool.

Note:
Management of JD Edwards EnterpriseOne Tools Release 8.96 or earlier must be done using the existing tools. Server Manager cannot be used to manage any JD Edwards EnterpriseOne Tools Release prior to 8.97

The Server Manager tool provides:

- Web Based System Management
You can securely access and manage your JD Edwards EnterpriseOne installation from anywhere using a standard web browser.

- Remote Deployment and Upgrades
You can install, uninstall, and update your JD Edwards EnterpriseOne servers regardless of their physical location or platform.

- Remote Operational Control
You can start and stop any of your JD Edwards EnterpriseOne servers, Oracle J2EE application servers, or supported third party J2EE application servers directly from the Management Console.

- Secure Administrative Tasks
Server Manager permits you to specify which existing JD Edwards EnterpriseOne users have access to the Management Console control which JD Edwards EnterpriseOne servers the user may view, and specify which administrative tasks the user may perform on those servers.

- Configuration Management
Server Manager provides a web-based interface for managing the configuration of all managed servers. The application presents each configuration item along with integrated help describing the configuration setting.

Note:
Beginning with the availability of Server Manager, it is strongly advised that all changes to configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, etc.) for any JD Edwards EnterpriseOne server managed by Server Manager be accomplished using only the Management Console interface of Server Manager. In addition to providing usability improvements, using Server Manager reduces the risk of introducing configuration errors by providing dropdowns that contain only valid values where applicable. Further, the tool provides a useful Audit History for any modifications made to configurations using Server Manager.

- Configuration Comparison
Use Server Manager to compare the configuration of two or more servers to identify configuration differences. You can compare configurations through the Management Console application regardless of the platform or location of the actual JD Edwards EnterpriseOne server. You can also compare individual servers with the default configuration of the corresponding server groups to which the servers belong.

- Audit History

Server Manager maintains a history of changes made to the managed servers. This includes a history of each configuration change, each server start and stop, and each tools release update, including the user that performed the change or operation. The Management Console application provides mechanisms to query and view the audit history that is maintained.

- Integrated EnterpriseOne Software Management
Use Server Manager to centrally maintain all your JD Edwards EnterpriseOne server tools releases, including the ability to copy the software to the remote server machines.

- Logical Server Grouping
Server Manager allows you to group servers with a similar purpose. These groups can include any of the server types such as Enterprise Server, HTML Server, and so on. A default, or template, configuration is maintained for each server group.

- Application Release Independence
Server Manager is delivered with JD Edwards EnterpriseOne Tools Release 8.97 and is compatible with any supported JD Edwards EnterpriseOne application release beginning with Application Release 8.9 through the currently supported release. No electronic software updates (ESUs) are required to support Server Manager.

- Self-Contained Installation
The installation of Server Manager delivers all components that are required by the Management Console application. There are no third party requirements regardless of your existing or intended middleware topology (for example, Oracle WebLogic, Oracle Application Server, WebSphere Application Server, or no application server).

- Tools Release Independence
Newer versions of the Server Manager application will continue to support the management of earlier tools releases back to JD Edwards EnterpriseOne Tools Release 8.97.

3 Installing and Configuring Oracle WebLogic 12.1.3

Note:
This chapter has been added in support of functionality for JD Edwards EnterpriseOne Tools Release 9.1 Update 5.

This chapter includes these tasks:

- Section 3.1, "Overview"

- Section 3.2, "Downloading Oracle WebLogic 12.1.3 from the Oracle Software Delivery Cloud"

- Section 3.3, "Before You Begin"

- Section 3.4, "Installing and Verifying the JDK Version"

- Section 3.5, "Installing Oracle WebLogic 12.1.3"

- Section 3.6, "Using Fusion Middleware Configuration Wizard to Configure Oracle WebLogic 12.1.3"

3.1 Overview

This document provides instructions for installing and running the Oracle installer for Oracle WebLogic 12.1.3.

Additional information regarding Oracle WebLogic 12.1.3 is available at this link:

http://docs.oracle.com/middleware/1213/wls/index.html

3.2 Downloading Oracle WebLogic 12.1.3 from the Oracle Software Delivery Cloud

You can download Oracle WebLogic 12.1.3 from the Oracle Software Delivery Cloud located at this link:

http://edelivery.oracle.com

3.3 Before You Begin

- Section 3.3.1, "64-Bit Support - General"

- Section 3.3.2, "64-Bit - JDK"

- Section 3.3.3, "System Requirements"

- Section 3.3.4, "Installation Considerations"

3.3.1 64-Bit Support - General

Per the Minimum Technical Requirements for JD Edwards, Oracle WebLogic 12.1.3 is supported with 64-bit JDKs on 64-bit platforms. You should always review the Certifications for JD Edwards EnterpriseOne for the supported platforms as described in Chapter 1, "Accessing Certifications (formerly Minimum Technical Requirements)".

3.3.2 64-Bit - JDK

The installation of Oracle WebLogic 12.1.3 for 64-bit platforms does not include the 64-bit JDK. Therefore, prior to installing Oracle WebLogic 12.1.3 for 64-bit platforms, you must manually download and install the requisite JDK. For the latest information about the specifically supported JDK, refer to the Oracle Fusion Middleware 12c Infrastructure product on Oracle Certification.

Additionally, JD Edwards EnterpriseOne requires that a 64-bit JDK be installed so that the \bin directory of the JDK is located at the beginning of the PATH variable definition.

3.3.3 System Requirements

Refer to Chapter 1, "Accessing Certifications (formerly Minimum Technical Requirements)" to locate for specific system requirements including minimum processor and memory required for Oracle WebLogic 12.1.3 on JD Edwards EnterpriseOne HTML Servers.

3.3.4 Installation Considerations

Oracle recommends the following:

- Do not exceed a maximum of 12 characters when naming your home directory. If the name of this directory has more than 12 characters and if there are spaces in the directory name, the CLASSPATH may not be resolved properly.

- You can install only one instance of each version of an Oracle WebLogic product in a single home directory

- If you launch the installation from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log stores messages (informational, warning, error, and fatal) about events that occur during the installation process.

3.4 Installing and Verifying the JDK Version

Oracle WebLogic 12.1.3 supports Oracle JDK 1.7.0_55+ version. version. Oracle JDK can be downloaded from the Oracle Software Delivery Cloud at this link:

http://edelivery.oracle.com

Note:
A plus sign '+' after the fourth digit in the version number indicates that this and its subsequent versions are supported.

Caution:
For Oracle WebLogic 12.1.3, no version of 1.6.x from any vendor is supported.

To verify your version of an installed JDK, use this command from the command prompt:

Note:
Verify the returned result indicates that a 64-bit version of the JDK is installed.
JD Edwards EnterpriseOne requires that a 64-bit JDK be installed so that the \bin directory of the JDK is located at the beginning of the PATH variable definition.

Note:
You must have a valid value for the Java_Home in your system path.

3.5 Installing Oracle WebLogic 12.1.3

To use the Oracle Universal Installer (OUI) to install Oracle WebLogic 12.1.3:

1. Locate the Oracle WebLogic 12.1.3 installer from the image that you downloaded from the Oracle Software Delivery Cloud.
The file name of the installer is:

fmw_12.1.3.0.0_wls.jar

2. Open a Command window with Run as Administrator option and run this command from the prompt:
>java -jar fmw_12.1.3.0.0_wls.jar

Upon execution, the installer starts preparing the OUI install program and displays the Welcome screen.

3. On Welcome, click the Next button.

4. On Installation Location, provide a location for the home for this installation of WebLogic 12.1.3.
For example, your Oracle Home directory might be:

C:\Oracle\Middleware

Tip:
The location you enter here will be your MW_HOME value.

5. Click the Next button.

6. On Installation Type, select the type of installation you wish to perform.
In this guide, it is assumed you select the Complete Installation type, which installs the Oracle WebLogic and the Oracle Coherence Server. However you can choose to select WebLogic Server Installation option.

Note:
The Complete Installation selection automatically includes the Oracle Coherence server. This is a stand-alone cache server that enables dedicated JVM instances responsible for maintaining and managing cached data. As of the initial publication of this guide, the JD Edwards EnterpriseOne HTML Server has not been certified with the Oracle Coherence Server.

7. Click the Next button.

8. The installer runs Prerequisite Checks and shows progress.

9. If the checks are successful, click the Next button.

10. On Specify Security Updates, Oracle strongly recommends you complete the Email address and/or the My Oracle Support Password fields to register your installation of Oracle WebLogic 12.1.3. This registration will enable you to be informed of security issues.

11. Click the Next button.

12. On Installation Summary, review the list of products that will be installed.

13. Click the Install button.

As the installer begins a progress bar is displayed in the lower right-hand portion of the screen and displays the new features of the Oracle WebLogic 12c.

14. On Installation Complete, ensure this checkbox is selected in order to launch to the Quickstart menu so that you can create your Domain:

- Automatically Launch the Quickstart Configuration Wizard

15. Click the Finish button.
The launch of QuickStart Configuration Wizard opens the Fusion Middleware Configuration wizard. Refer to the next section in this guide entitled: Section 3.6, "Using Fusion Middleware Configuration Wizard to Configure Oracle WebLogic 12.1.3".

3.6 Using Fusion Middleware Configuration Wizard to Configure Oracle WebLogic 12.1.3

You can use QuickStart to create a starter domain using the Configuration Wizard. These instructions guide you in the creation of a domain for JD Edwards EnterpriseOne.

If you selected the Run Quickstart check box on the Installation Complete menu of the installer, QuickStart is automatically launched.

To manually launch the QuickStart configuration wizard, run this executable:

<MW_HOME>\oracle_common\common\bin\config.cmd

1. On Configuration Type, enter or browse to your domain location. For example:
C:\Oracle\Middleware\user_projects\domains\base_domain

where in this example base_domain is the domain name.

Tip:
The typical default domain location is:
<MW_HOME>\user_projects\domains

2. Click the Next button.

3. On Templates, select the checkbox for this template:
Basic WebLogic Server Domain - 12.1.3.0 [wlserver]*

4. Click the Next button.

5. On Administrator Account, complete the fields for user name and password for the default user that will start the domain.

Tip:
For this example the default user is:
weblogic

6. Click the Next button.

7. On Domain Mode and JDK, for use with JD Edwards EnterpriseOne you must select this radio button in the Domain Mode section:
Production

8. In the JDK section, ensure the radio button is selected for the available JDK. For example:
Oracle HotSpot 1.7.0_55 C:\PROGRA~\Java\JDK17~1.0_6

9. Click the Next button.

10. On Advanced Configuration, check these boxes to modify their settings:

- Administration Server

- Node Manager

- Manager Servers, Clusters and Coherence

11. Click the Next button.

12. On Administrative Server, complete these fields:

- Server Name
Enter a name for the Administration Server. For example:

AdminServer

- Listen address
You can accept the default selection, which is:

All Local Addresses

- Listen Port

Tip:
The default port value is 7001.
You can override the default value if desired. For example, you could enter this port value: 8000.

You must specify this same port number in the URL that starts the Admin Console.

13. Click the Next button.

14. On Node Manager, in the Node Manager Type section, select this radio button:
Per Domain

Note:
The Per Domain value is the only supported Node Manager Type for use with JD Edwards EnterpriseOne.

15. On Node Manager, in the Node Manager Credentials section, enter valid values for your Node Manager.

Note:
A valid username and password are required to start the node manager.

16. Click the Next button.

17. On Managed Servers, ensure that the specified Listen Port is unique for this server and click the Next button.

18. Set the Listen Address to localhost and click the Next button.

19. On Configure Clusters, click the Next button to skip this step for purposes of this guide. Refer to the Note below.

Caution:
Clustering is not part of the basic Oracle WebLogic 12.1.3 License. In order to use the Clustering feature you must upgrade and obtain a license for an Oracle Enterprise WebLogic Server.

20. On Machines, click the Machine tab and then click the Add button to define a machine name.

Note:
You also can define the Machine from the Oracle WebLogic 12.1.3 Administration Console after the configuration.

21. Click the Next button.

22. On Assign Servers to Machines, in the left pane highlight available servers and use the right arrow button to assign the available server(s) to the newly defined machine.

23. On Configuration Summary, review your selections.

24. Click the Create button.

25. On Configuration Progress, when the Progress bar indicates the process is 100% complete, click the Next button.

26. On Configuration Success, click the Finish button to exit the wizard.

4 Installing and Configuring
Oracle WebLogic 12.1.2

Note:
This chapter has been added in support of functionality for JD Edwards EnterpriseOne Tools Release 9.1 Update 4.

This chapter includes these tasks:

- Section 4.1, "Overview"

- Section 4.2, "Downloading Oracle WebLogic 12.1.2 from the Oracle Software Delivery Cloud"

- Section 4.3, "Before You Begin"

- Section 4.4, "Installing and Verifying the JDK Version"

- Section 4.5, "Installing Oracle WebLogic 12.1.2"

- Section 4.6, "Using Fusion Middleware Configuration Wizard to Configure Oracle WebLogic 12.1.2"

4.1 Overview

This document provides instructions for installing and running the Oracle installer for Oracle WebLogic 12.1.2.

Additional information regarding Oracle WebLogic 12.1.2 is available at this link:

http://docs.oracle.com/middleware/1212/wls/index.html

4.2 Downloading Oracle WebLogic 12.1.2 from the Oracle Software Delivery Cloud

You can download Oracle WebLogic 12.1.2 from the Oracle Software Delivery Cloud located at this link:

http://edelivery.oracle.com

4.3 Before You Begin

This section describes these topics:

- Section 4.3.1, "64-Bit Support - General"

- Section 4.3.2, "64-Bit - JDK"

- Section 4.3.3, "System Requirements"

- Section 4.3.4, "Installation Considerations"

4.3.1 64-Bit Support - General

Per the Minimum Technical Requirements for JD Edwards, Oracle WebLogic 12.1.2 is supported with 64-bit JDKs on 64-bit platforms. You should always review the Certifications for JD Edwards EnterpriseOne for the supported platforms as described in Chapter 1, "Accessing Certifications (formerly Minimum Technical Requirements)".

4.3.2 64-Bit - JDK

The installation of Oracle WebLogic 12.1.2 for 64-bit platforms does not include the 64-bit JDK. Therefore, prior to installing Oracle WebLogic 12.1.2 for 64-bit platforms, you must manually download and install the requisite JDK. For the latest information about the specifically supported JDK, refer to the Oracle Fusion Middleware 12c Infrastructure product on Oracle Certification.

Additionally, JD Edwards EnterpriseOne requires that a 64-bit JDK be installed so that the \bin directory of the JDK is located at the beginning of the PATH variable definition.

Caution:
For Oracle WebLogic 12.1.2, no version of 1.6.x from any vendor is supported. The supported version of the JDK is listed in the section of this guide entitled: Section 4.4, "Installing and Verifying the JDK Version".

4.3.3 System Requirements

Refer to Chapter 1, "Accessing Certifications (formerly Minimum Technical Requirements)" to locate for specific system requirements including minimum processor and memory required for Oracle WebLogic 12.1.2 on JD Edwards EnterpriseOne HTML Servers.

4.3.4 Installation Considerations

Oracle recommends the following:

- Do not exceed a maximum of 12 characters when naming your home directory. If the name of this directory has more than 12 characters and if there are spaces in the directory name, the CLASSPATH may not be resolved properly.

- You can install only one instance of each version of an Oracle WebLogic product in a single home directory

- If you launch the installation from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log stores messages (informational, warning, error, and fatal) about events that occur during the installation process.

4.4 Installing and Verifying the JDK Version

Oracle WebLogic 12.1.2 supports JDK 1.7.0_55+ version. Oracle JDK can be downloaded from the Oracle Software Delivery Cloud at this link:

http://edelivery.oracle.com

Note:
A plus sign '+' after the fourth digit in the version number indicates that this and its subsequent versions are supported.

To verify your version of an installed JDK, use this command from the command prompt:

Note:
Verify the returned result indicates that a 64-bit version of the JDK is installed.
JD Edwards EnterpriseOne requires that a 64-bit JDK be installed so that the \bin directory of the JDK is located at the beginning of the PATH variable definition.

Note:
You must have a valid value for the Java_Home in your system path.

4.5 Installing Oracle WebLogic 12.1.2

To use the Oracle Universal Installer (OUI) to install Oracle WebLogic 12.1.2:

1. Locate the Oracle WebLogic 12.1.2 installer from the image that you downloaded from the Oracle Software Delivery Cloud.
The file name of the installer is:

wls_121200.jar

2. Open a Command window with Run as Administrator option and run this command from the prompt:
>java -jar wls_121200.jar

Upon execution, the installer starts preparing the OUI install program and displays the Welcome screen.

3. On Welcome, click the Next button.

4. On Installation Location, provide a location for the home for this installation of WebLogic 12.1.2.
For example, your Oracle Home directory might be:

C:\Oracle\Middleware

Tip:
The location you enter here will be your MW_HOME value.

5. Click the Next button.

6. On Installation Type, select the type of installation you wish to perform.
In this guide, it is assumed you select the Complete Installation type, which installs the Oracle WebLogic and the Oracle Coherence Server. However you can choose to select WebLogic Server Installation option.

Note:
The Complete Installation selection automatically includes the Oracle Coherence server. This is a stand-alone cache server that enables dedicated JVM instances responsible for maintaining and managing cached data. As of the initial publication of this guide, the JD Edwards EnterpriseOne HTML Server has not been certified with the Oracle Coherence Server.

7. Click the Next button.

8. The installer runs Prerequisite Checks and shows progress.

9. If the checks are successful, click the Next button.

10. On Specify Security Updates, Oracle strongly recommends you complete the Email address and/or the My Oracle Support Password fields to register your installation of Oracle WebLogic 12.1.2. This registration will enable you to be informed of security issues.

11. Click the Next button.

12. On Installation Summary, review the list of products that will be installed.

13. Click the Install button.

As the installer begins a progress bar is displayed in the lower right-hand portion of the screen and displays the new features of the Oracle WebLogic 12c.

14. On Installation Complete, ensure this checkbox is selected in order to launch to the Quickstart menu so that you can create your Domain:

- Automatically Launch the Quickstart Configuration Wizard

15. Click the Finish button.
The launch of QuickStart Configuration Wizard opens the Fusion Middleware Configuration wizard. Refer to the next section in this guide entitled: Section 4.6, "Using Fusion Middleware Configuration Wizard to Configure Oracle WebLogic 12.1.2".

4.6 Using Fusion Middleware Configuration Wizard to Configure Oracle WebLogic 12.1.2

You can use QuickStart to create a starter domain using the Configuration Wizard. These instructions guide you in the creation of a domain for JD Edwards EnterpriseOne.

If you selected the Run Quickstart check box on the Installation Complete menu of the installer, QuickStart is automatically launched.

To manually launch the QuickStart configuration wizard, run this executable:

<MW_HOME>\oracle_common\common\bin\config.cmd

1. On Configuration Type, enter or browse to your domain location. For example:
C:\Oracle\Middleware\user_projects\domains\base_domain

where in this example base_domain is the domain name.

Tip:
The typical default domain location is:
<MW_HOME>\user_projects\domains

2. Click the Next button.

3. On Templates, select the checkbox for this template:
Basic WebLogic Server Domain - 12.1.2.0 [wlserver]*

4. Click the Next button.

5. On Administrator Account, complete the fields for user name and password for the default user that will start the domain.

Tip:
The default user is:
weblogic

The default password is:

welcome1

6. Click the Next button.

7. On Domain Mode and JDK, for use with JD Edwards EnterpriseOne you must select this radio button in the Domain Mode section:
Production

8. In the JDK section, ensure the radio buttonis selected for the available JDK. For example:
Oracle HotSpot 1.7.0_25 C:\PROGRA~\Java\JDK17~1.0_2

9. Click the Next button.

10. On Advanced Configuration, check these boxes to modify their settings:

- Administration Server

- Node Manager

- Manager Servers, Clusters and Coherence

11. Click the Next button.

12. On Administrative Server, complete these fields:

- Server Name
Enter a name for the Administration Server. For example:

AdminServer

- Listen address
You can accept the default selection, which is:

All Local Addresses

- Listen Port

Tip:
The default port value is 7001.
You can override the default value if desired. For example, you could enter this port value: 8000.

You must specify this same port number in the URL that starts the Admin Console.

13. Click the Next button.

14. On Node Manager, in the Node Manager Type section, select this radio button:
Per Domain

Note:
The Per Domain value is the only supported Node Manager Type for use with JD Edwards EnterpriseOne.

15. On Node Manager, in the Node Manager Credentials section, enter valid values for your Node Manager.

Note:
A valid username and password are required to start the node manager.

16. Click the Next button.

17. On Managed Servers, ensure that the specified Listen Port is unique for this server and click the Next button.

18. On Configure Clusters, click the Next button to skip this step for purposes of this guide. Refer to the Note below.

Caution:
Clustering is not part of the basic Oracle WebLogic 12.1.2 License. In order to use the Clustering feature you must upgrade and obtain a license for an Oracle Enterprise WebLogic Server.

19. On Machines, click the Machine tab and then click the Add button to define a machine name.

Note:
You also can define the Machine from the Oracle WebLogic 12.1.2 Administration Console after the configuration.

20. Click the Next button.

21. On Assign Servers to Machines, in the left pane highlight available servers and use the right arrow button to assign the available server(s) to the newly defined machine.

22. On Configuration Summary, review your selections.

23. Click the Create button.

24. On Configuration Progress, when the Progress bar indicates the process is 100% complete, click the Next button.

25. On Configuration Success, click the Finish button to exit the wizard.

5 Installing and Configuring Oracle WebLogic 10.3.6.0

This chapter includes these tasks:

- Section 5.1, "Overview"

- Section 5.2, "Downloading Oracle WebLogic 10.3.6.0 from the Oracle Software Delivery Cloud"

- Section 5.3, "Before You Begin"

- Section 5.4, "Installing and Verifying the JDK Version"

- Section 5.5, "Installing Oracle WebLogic 10.3.6.0"

- Section 5.6, "Using QuickStart to Configure Oracle WebLogic 10.3.6.0"

- Section 5.7, "Post Installation and Configuration"

5.1 Overview

This document provides instructions for installing and running the Oracle installer for the Oracle WebLogic 10.3.6.0.

Additional information regarding the Oracle WebLogic 10.3.6.0 is available at this link:

http://docs.oracle.com/cd/E23943_01/wls.htm

5.2 Downloading Oracle WebLogic 10.3.6.0 from the Oracle Software Delivery Cloud

This section describes how to download Oracle WebLogic 10.3.6.0 from the Oracle Software Delivery Cloud located at this link:

http://edelivery.oracle.com

5.3 Before You Begin

This section describes these topics:

- 64-Bit Support - General

- 64-Bit - JDK

- System Requirements

- Installation Considerations

5.3.1 64-Bit Support - General

Per the Minimum Technical Requirements for JD Edwards, Oracle WebLogic 10.3.6.0 is supported with 64-bit JDKs on 64-bit platforms. You should always review the JD Edwards EnterpriseOne MTRs for the supported platforms as described in Chapter 1, "Accessing the Minimum Technical Requirements".

5.3.2 64-Bit - JDK

The installation of Oracle WebLogic 10.3.6.0 for 64-bit platforms does not include the 64-bit JDK. Therefore, prior to installing Oracle WebLogic 10.3.6.0 for 64-bit platforms, you must manually download and install the requisite JDK. For the latest information about the specifically supported JDK, refer to the Oracle Fusion Middleware Certification document at this link:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html">>http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Additionally, JD Edwards EnterpriseOne requires that a 64-bit JDK be installed so that the \bin directory of the JDK is located at the beginning of the PATH variable definition.

5.3.3 System Requirements

Refer to the JD Edwards EnterpriseOne MTRs (Chapter 1, "Accessing the Minimum Technical Requirements") for Oracle WebLogic 10.3.6.0 for specific system requirements including minimum processor and memory.

5.3.4 Installation Considerations

Oracle recommends the following:

- Do not exceed a maximum of 12 characters when naming your home directory. If the name of this directory has more than 12 characters and if there are spaces in the directory name, the CLASSPATH may not be resolved properly.

- You can install only one instance of each version of an Oracle WebLogic product in a single home directory

- If you launch the installation from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log stores messages (informational, warning, error, and fatal) about events that occur during the installation process.

5.4 Installing and Verifying the JDK Version

Starting with Oracle WebLogic 10.3.6.0, the JD Edwards EnterpriseOne HTML Server only supports the Oracle JDK 7+.

Note:
JRockit and HotSpot are merged into a single JVM starting with Oracle JDK 7. There is not a version called JRockit 7. The WebLogic Server does not ship with JDK 7. You can download Oracle JDK 7 from the following link:
http://www.oracle.com/technetwork/java/javase/downloads/index.html

(A plus sign '+' in the version number indicates that this and its subsequent versions are supported)

To verify your version of an installed JDK, use this command from the command prompt:

>java -version

>java -d64 -version

The system returns results as shown in the example:

For Oracle JDK 7+:

Note:
Verify the returned result indicates that a 64-bit version of the JDK is installed.
JD Edwards EnterpriseOne requires that a 64-bit JDK be installed so that the \bin directory of the JDK is located at the beginning of the PATH variable definition.

Caution:
In order for the JDK 7 to function properly with the JD Edwards EnterpriseOne HTML Server, after you have installed WebLogic Server, you must manually copy JDK specific .jar files. Refer to the section of this chapter entitled: Section 5.7, "Post Installation and Configuration".

5.5 Installing Oracle WebLogic 10.3.6.0

This section describes running the Oracle Universal Installer (OUI) to install Oracle WebLogic 10.3.6.0.

1. Run the Oracle WebLogic 10.3.6.0 installer from the image that you downloaded from the Oracle Software Delivery Cloud.
The item name of the installer is (V29856-01). The filename of the installer is:

wls1036_generic.jar

Upon execution, the installer starts preparing the OUI install program.

2. Open a Command window with Run as Administrator option and run this command from the prompt:
>java -jar wls1036_generic.jar

Note:
You must have a valid value for the Java_Home in your system path.

3. On Welcome, click the Next button.

4. On Choose Middleware Home Directory, click this radio button:
Create a new Middleware Home

For example, your Middleware Home Directory might be:

C:\Oracle\Middleware

Tip:
The location you enter here will be your MW_HOME value.

5. Click the Next button.

6. On Register for Security Updates, Oracle strongly recommends you complete the Email address and/or the My Oracle Support Password fields to register your installation of Oracle WebLogic 10.3.6.0. This registration will enable you to be informed of security issues.

7. Click the Next button.

8. On Choose Install Type, select the type of installation you wish to perform.
In this guide, it is assumed you select the Typical installation type, which installs the Oracle WebLogic 10.3.6.0 and the Oracle Coherence Server.

Note:
The Typical selection automatically includes the Oracle Coherence server, which is part of Oracle WebLogic 10.3.6.0. This new server is a stand-alone cache server that enables dedicated JVM instances responsible for maintaining and managing cached data. As of the initial publication of this guide, the JD Edwards EnterpriseOne HTML Server has not been certified with the Oracle Coherence Server.

9. Click the Next button.

10. On JDK Selection, click the check box for the JDK you wish to use and install with this product installation.

11. Click the Next button.

12. On Choose Product Installation Directories, complete these fields:

- WebLogic Server
Enter or browse to a location where you wish to install an Oracle WebLogic 10.3.6.0.

For example:

c:\Oracle\Middleware\wlserver_10.3

- Oracle Coherence
Enter or browse to a location where you wish to install the Oracle Coherence Server.

For example:

c:\Oracle\Middleware\coherence_3.7

13. Click the Next button.

Note:
If you are not running the installer as an Administrator, the following screen will not display.

14. If the above screen does display (because you are not running the installer as an Administrator), on Choose Shortcut Location, click this radio button:
"All Users" Start Menu folder (recommended)

15. Click the Next button.

16. On Installation Summary, review the products that will be installed.

17. Click the Next button.

18. The installer starts copying files.
A progress bar is displayed in the lower right-hand portion of the screen.

As the installer progresses it displays the new features of the Oracle WebLogic 10.3.6.0.

19. On Installation Complete, ensure the Run Quickstart check box is selected in order to launch to the Quickstart menu so that you can create your Domain.

20. Click the Done button.
The QuickStart menu is displayed. Refer to the next section in this guide entitled: Section 5.6, "Using QuickStart to Configure Oracle WebLogic 10.3.6.0".

5.6 Using QuickStart to Configure Oracle WebLogic 10.3.6.0

You can use QuickStart to create a starter domain using the Configuration Wizard. These instructions guide you in the creation of a domain for JD Edwards EnterpriseOne.

If you selected the Run Quickstart check box on the Installation Complete menu of the installer, QuickStart is automatically launched.

To manually launch the QuickStart configuration wizard, run this executable:

<MW_HOME>\utils\quickstart\quickstart.cmd

1. On the QuickStart links panel, select this link:
Getting started with WebLogic Server 10.3.6

A Configuration Wizard is launched.

2. On Welcome, click this radio button to create an Oracle WebLogic 10.3.6.0 domain in your projects directory.
Create a new WebLogic domain

3. On Select Domain Source, click this radio button:
Generate a domain configured automatically to support the following products

In this section, ensure this default check box is also selected:

Basic WebLogic Server Domain - 10.3.6.0 [wlserver_10.3]*

Tip:
For operation with JD Edwards EnterpriseOne, you do not need to select any other check boxes in this section.

4. Click the Next button.

5. On Specify Domain Name and Location, complete these fields:

- Domain name: (the default is base_domain)
The default value is base_domain. You should enter a domain name for JD Edwards EnterpriseOne. For example:

E1_Apps

- Domain location:
Enter or browse to your domain location. For example:

C:\Oracle\Middleware\user_projects\domains

Tip:
The typical default domain location is:
<MW_HOME>\user_projects\domains

6. On Configure Administrator User Name and Password, complete the fields for user name and password for the default user that will start the domain.

Tip:

The default user is:

weblogic

The default password is:

welcome1

7. Click the Next button.

8. On Configure Server Start Mode and JDK, in the left-hand pane entitled: WebLogic Domain Startup Mode, for use with JD Edwards EnterpriseOne you must select this radio button:
Production Mode

In the right-hand pane, ensure the radio button for Available JDKs button is selected and your installed JDK is highlighted.

9. Click the Next button.

10. On Select Optional Configuration, select these check boxes to modify the server settings:

- Administration Server

- Managed Servers, Clusters and Machines

11. Click the Next button.

12. On Configure the Administration Server, complete these fields:

- Name
Enter a name for the Administration Server. For example:

AdminServer

- Listen address
You can accept the default selection, which is:

All Local Addresses

- Listen Port

Tip:
The default port value is 7001.
You can override the default value if desired.

You must specify this same port number in the URL that starts the Admin Console.

13. Click the Next button.

14. Because the Oracle WebLogic 10.3.6.0 implementation with JD Edwards EnterpriseOne uses EnterpriseOne Server Manager for this functionality, on Configure Managed Servers, click the Next button to skip this step.

15. On Configure Clusters, click the Next button to skip this step.

Note:
Clustering is not part of the basic Oracle WebLogic 10.3.6.0 License. You must upgrade to an Oracle Enterprise WebLogic Server License in order to use the Clustering feature.

16. On Configure Machines, click the Machine tab and then click the Add button to define a machine name.
You also can define the Machine from the Oracle WebLogic 10.3.6.0 Administration Console after the configuration.

17. On Assign Servers to Machines, in the left pane highlight available servers and use the right arrow button to assign the available server(s) to the newly defined machine.

18. Click the Next button.

19. On Configuration Summary, review your selections.

20. Click the Create button.

21. On Creating Domain, when the Progress bar indicates the process is 100% complete, click the Done button to exit the wizard.

5.7 Post Installation and Configuration

After installing WebLogic Server, copy these files:

- javax.annotation_1.0.0.0_1-0.jar

- javax.xml.bind_2.1.1.jar

- javax.xml.ws_2.1.1.jar

from:

MW_HOME\modules

where MW_HOME is the WebLogic Server installation home directory

to:

JAVA_HOME\jre\endorsed

Note:
You will need to create the endorsed folder.

6 Installing and Configuring Oracle WebLogic 10.3.5.0

This chapter includes these tasks:

- Section 6.1, "Overview"

- Section 6.2, "Downloading Oracle WebLogic 10.3.5.0 from the Oracle Software Delivery Cloud"

- Section 6.3, "Before You Begin"

- Section 6.4, "Installing and Verifying the JDK Version"

- Section 6.5, "Installing Oracle WebLogic 10.3.5.0"

- Section 6.6, "Using QuickStart to Configure Oracle WebLogic 10.3.5.0"

6.1 Overview

This document provides instructions for installing and running the Oracle installer for the Oracle WebLogic 10.3.5.0.

Additional information regarding the Oracle WebLogic 10.3.5.0 is available at this link:

http://download.oracle.com/docs/cd/E21764_01/wls.htm

6.2 Downloading Oracle WebLogic 10.3.5.0 from the Oracle Software Delivery Cloud

This section describes how to download Oracle WebLogic 10.3.5.0 from the Oracle Software Delivery Cloud located at this link:

http://edelivery.oracle.com

6.3 Before You Begin

This section describes these topics:

- 64-Bit Support - General

- 64-Bit - JDK

- System Requirements

- Installation Considerations

6.3.1 64-Bit Support - General

Per the Minimum Technical Requirements for JD Edwards, Oracle WebLogic 10.3.5.0 is supported with 64-bit JDKs on 64-bit platforms. You should always review the JD Edwards EnterpriseOne MTRs for the supported platforms as described in Chapter 1, "Accessing the Minimum Technical Requirements".

6.3.2 64-Bit - JDK

The installation of Oracle WebLogic 10.3.5.0 for 64-bit platforms does not include the 64-bit JDK. Therefore, prior to installing Oracle WebLogic 10.3.5.0 for 64-bit platforms, you must manually download and install the requisite JDK. For the latest information about the specifically supported JDK, refer to the Oracle Fusion Middleware Certification document at this link:

http://www.oracle.com/technology/software/products/ias/files/fus ion_certification.html">>http://www.oracle.com/technology/software/products/ias/files/fus ion_certification.html

Additionally, JD Edwards EnterpriseOne requires that a 64-bit JDK be installed so that the \bin directory of the JDK is located at the beginning of the PATH variable definition.

6.3.3 System Requirements

Refer to the JD Edwards EnterpriseOne MTRs (Chapter 1, "Accessing the Minimum Technical Requirements") for Oracle WebLogic 10.3.5.0 for specific system requirements including minimum processor and memory.

6.3.4 Installation Considerations

Oracle recommends the following:

- Do not exceed a maximum of 12 characters when naming your home directory. If the name of this directory has more than 12 characters and if there are spaces in the directory name, the CLASSPATH may not be resolved properly.

- You can install only one instance of each version of an Oracle WebLogic product in a single home directory

- If you launch the installation from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log stores messages (informational, warning, error, and fatal) about events that occur during the installation process.

6.4 Installing and Verifying the JDK Version

Oracle WebLogic 10.3.5.0 supports Sun JDK 1.6.0_24+ or Oracle JRockit R28.1.3-1.6.0_24+ version . Oracle JRockit can be downloaded from the Oracle Software Delivery Cloud at this link:

http://edelivery.oracle.com

(A plus sign '+' after the fourth digit in the version number indicates that this and its subsequent versions are supported)

To verify your version of an installed JDK, use this command from the command prompt:

>java -version

The system returns results as shown in the example:

For Oracle JRockit JDK:

Note:
Verify the returned result indicates that a 64-bit version of the JDK is installed.
JD Edwards EnterpriseOne requires that a 64-bit JDK be installed so that the \bin directory of the JDK is located at the beginning of the PATH variable definition.

For Oracle Sun (HotSpot) JDK:

6.5 Installing Oracle WebLogic 10.3.5.0

This section describes running the Oracle Universal Installer (OUI) to install Oracle WebLogic 10.3.5.0.

1. Run the Oracle WebLogic 10.3.5.0 installer from the image that you downloaded from the Oracle Software Delivery Cloud.
The file name of the installer is:

wls1035_generic.jar

Upon execution, the installer starts preparing the OUI install program.

2. Open a Command window with Run as Administrator option and run this command from the prompt:
>java -jar wls1035_generic.jar

Note:
You must have a valid value for the Java_Home in your system path.

3. On Welcome, click the Next button.

4. On Choose Middleware Home Directory, click this radio button:
Create a new Middleware Home

For example, your Middleware Home Directory might be:

C:\Oracle\Middleware

Tip:
The location you enter here will be your MW_HOME value.

5. Click the Next button.

6. On Register for Security Updates, Oracle strongly recommends you complete the Email address and/or the My Oracle Support Password fields to register your installation of Oracle WebLogic 10.3.5.0. This registration will enable you to be informed of security issues.

7. Click the Next button.

8. On Choose Install Type, select the type of installation you wish to perform.
In this guide, it is assumed you select the Typical installation type, which installs the Oracle WebLogic 10.3.5.0 and the Oracle Coherence Server.

Note:
The Typical selection automatically includes the Oracle Coherence server, which is new with Oracle WebLogic 10.3.5.0. This new server is a stand-alone cache server that enables dedicated JVM instances responsible for maintaining and managing cached data. As of the initial publication of this guide, the JD Edwards EnterpriseOne HTML Server has not been certified with the Oracle Coherence Server.

9. Assuming you chose Typical install, on Choose Install Type click the Next button. If you chose Custom install, on Choose Products and Components, click the Next button.

10. On JDK Selection, click the check box for the JDK you wish to use and install with this product installation.

Note:
If you did not install the Oracle JRockit JDK and instead installed the Oracle Sun JDK, the following screen is displayed:

11. Verify your JDK selection and click the Next button.

12. On Choose Product Installation Directories, complete these fields:

- WebLogic Server
Enter or browse to a location where you wish to install an Oracle WebLogic 10.3.5.0.

For example:

c:\Oracle\Middleware\wlserver_10.3

- Oracle Coherence
Enter or browse to a location where you wish to install the Oracle Coherence Server.

For example:

c:\Oracle\Middleware\coherence_3.6

13. Click the Next button.

Note:
If you are not running the installer as an Administrator, the following screen will not display.

14. If the above screen does display (because you are not running the installer as an Administrator), on Choose Shortcut Location, click this radio button:
"All Users" Start Menu folder (recommended)

15. Click the Next button.

16. On Installation Summary, review the products that will be installed.

17. Click the Next button.

18. The installer starts copying files.
A progress bar is displayed in the lower right-hand portion of the screen.

As the installer progresses it displays the new features of the Oracle WebLogic 10.3.5.0.

19. On Installation Complete, ensure the Run Quickstart check box is selected in order to launch to the Quickstart menu so that you can create your Domain.

20. Click the Done button.
The QuickStart menu is displayed. Refer to the next section in this guide entitled: Section 6.6, "Using QuickStart to Configure Oracle WebLogic 10.3.5.0".

6.6 Using QuickStart to Configure Oracle WebLogic 10.3.5.0

You can use QuickStart to create a starter domain using the Configuration Wizard. These instructions guide you in the creation of a domain for JD Edwards EnterpriseOne.

If you selected the Run Quickstart check box on the Installation Complete menu of the installer, QuickStart is automatically launched.

To manually launch the QuickStart configuration wizard, run this executable:

<MW_HOME>\utils\quickstart\quickstart.cmd

1. On the QuickStart links panel, select this link:
Getting started with WebLogic Server 10.3.5

A Configuration Wizard is launched.

2. On Welcome, click this radio button to create an Oracle WebLogic 10.3.5.0 domain in your projects directory.
Create a new WebLogic domain

3. On Select Domain Source, click this radio button:
Generate a domain configured automatically to support the following products

In this section, ensure this default check box is also selected:

Basic WebLogic Server Domain - 10.3.4.0 [wlserver_10.3]*

Tip:
For operation with JD Edwards EnterpriseOne, you do not need to select any other check boxes in this section.

Note:
Even though the version on this screen is showing as 10.3.4.0, this is a valid step for version 10.3.5.0.

4. Click the Next button.

5. On Specify Domain Name and Location, complete these fields:

- Domain name: (the default is base_domain)
The default value is base_domain. You should enter a domain name for JD Edwards EnterpriseOne. For example:

E1_Apps

- Domain location:
Enter or browse to your domain location. For example:

C:\Oracle\Middleware\user_projects\domains

Tip:
The typical default domain location is:
<MW_HOME>\user_projects\domains

6. On Configure Administrator User Name and Password, complete the fields for user name and password for the default user that will start the domain.

Tip:

The default user is:

weblogic

The default password is:

welcome1

7. Click the Next button.

8. On Configure Server Start Mode and JDK, in the left-hand pane entitled: WebLogic Domain Startup Mode, for use with JD Edwards EnterpriseOne you must select this radio button:
Production Mode

In the right-hand pane, ensure the radio button for Available JDKs button is selected and your installed JDK is highlighted.

9. Click the Next button.

10. On Select Optional Configuration, select these check boxes to modify the server settings:

- Administration Server

- Managed Servers, Clusters and Machines

11. Click the Next button.

12. On Configure the Administration Server, complete these fields:

- Name
Enter a name for the Administration Server. For example:

AdminServer

- Listen address
You can accept the default selection, which is:

All Local Addresses

- Listen Port

Tip:
The default port value is 7001.
You can override the default value if desired. For example, you could enter this port value:

8000

You must specify this same port number in the URL that starts the Admin Console.

13. Click the Next button.

14. Because the Oracle WebLogic 10.3.5.0 implementation with JD Edwards EnterpriseOne uses EnterpriseOne Server Manager for this functionality, on Configure Managed Servers, click the Next button to skip this step.

15. On Configure Clusters, click the Next button to skip this step.

Note:
Clustering is not part of the basic Oracle WebLogic 10.3.5.0 License. You must upgrade to an Oracle Enterprise WebLogic Server License in order to use the Clustering feature.

16. On Configure Machines, click the Machine tab and then click the Add button to define a machine name.
You also can define the Machine from the Oracle WebLogic 10.3.5.0 Administration Console after the configuration.

17. On Assign Servers to Machines, in the left pane highlight available servers and use the right arrow button to assign the available server(s) to the newly defined machine.

18. Click the Next button.

19. On Configuration Summary, review your selections.

20. Click the Create button.

21. On Creating Domain, when the Progress bar indicates the process is 100% complete, click the Done button to exit the wizard.

7 Preparing the WebLogic Server for JD Edwards EnterpriseOne HTML Server Installation

This section describes these tasks:

- Section 7.1, "Start the WebLogic Administration Console"

- Section 7.2, "Start the Node Manager Manually"

- Section 7.3, "Enable Node Manager as a Windows Service"

- Section 7.4, "Create the Machine Definition"

7.1 Start the WebLogic Administration Console

To start the WebLogic Admin Console:

1. Sign on as WebLogic Server user.

2. Open a command window with Run as Administrator option.

3. Change directory to:
<weblogic_server_install_location>\user_projects\domains\<yourdomain>\bin

4. Start the WebLogic Admin Console by executing this script from the command prompt:
> startWebLogic.cmd

5. At the prompts, enter the Admin user and password for the WebLogic Admin Console.

As indicated at the bottom of the above screen sample, when the console completes normally, the WebLogic Admin Console can be accessed after this message is displayed:

<Server Started in RUNNING mode>

Caution:
The Admin Server Console will shut down if this process is closed.

6. To access the WebLogic Admin Console, enter this URL into a browser such as Firefox or Internet Explorer:
http://<host>:<port>/console

For example:

http://your_machine_name:7001/console

The WebLogic Admin Console is displayed.

Alternatively, you also can start the WebLogic Admin Console from Windows Start > All Programs Menu.

1. Select your domain from this directory:
MW_HOME\user_projects\<your_domain>\

2. Locate the WebLogic Admin Console and execute it with Run as Administrator option.
A sample screen is shown below:

Optionally you also can add the Start WebLogic Admin Console process to the Windows Services. There is an install script called installSvc.cmd that is available for this task. However, you need to modify the script to create a parameter list.

The remainder of this section contains these optional tasks:

- Section 7.1.1, "Creating a boot.properties File for User and Password"

- Section 7.1.2, "Adding WebLogic Admin Server or Managed Server Process to Windows Services"

- Section 7.1.3, "Creating a Process to Remove the WebLogic Admin Console from the Windows Services"

7.1.1 Creating a boot.properties File for User and Password

In order to start the WebLogic Admin Console without prompting for user and password, you need to enter the admin user and password in a boot.properties file. As a result, the start up process uses the user and password from this file instead of prompting for it.

1. If existing, edit the boot.properties file (see directory location below). If this file does not exist, it must be created in this directory:
<MW_HOME>/user_projects/domains/<your_domain>/servers/<server_name>/security

Caution:
You might need to create the security directory if it does not already exist. Also beware of the file type. The boot.properties file should be a Properties File type, and the filename should not have an extension. If you save the file as "boot.properties.txt", then the startup process will not recognize this file. A correctly formed boot.properties file will have a PROPERTIES type as shown in this example:

2. Edit the boot.properties file to complete these parameters:

Caution:
You must enter these two parameters in lower case.

- username=weblogic
The default value for username is weblogic. You should change this value in this file to a valid value for your WebLogic Admin Server.

- password=welcome1
The default value for username is welcome1. You should change this value in this file to a valid value for your WebLogic Admin Server.

Caution:
The information entered in this file is encrypted after the first access.

7.1.2 Adding WebLogic Admin Server or Managed Server Process to Windows Services

To add the WebLogic Admin Console process to Windows Services:

1. Change the directory to:
<MW_HOME>\wlserver_10.3\server\bin

2. Create a CreateWLSSvc.cmd file and add the following lines, where you should add your own values for the bolded values:

SETLOCAL
set DOMAIN_NAME=E1_Apps
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\E1_Apps
set SERVER_NAME=[AdminServer or Managed Server Name]
set PRODUCTION_MODE=true
set JAVA_VENDOR=Oracle or Sun
set JAVA_HOME=C:\Oracle\JDK_1.7
set JAVA_OPTIONS=-XX:MaxPermSize=350m -Xms32m -Xmx1024m -Djava.xml.rpc.ServiceFactory=oracle.j2ee.ws.client.ServiceFactoryImpl
call "%USERDOMAIN_HOME%\bin\setDomainEnv.cmd"
call "C:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL

Note:
The JD Edwards EnterpriseOne One View reporting functionality requires that the JAVA_OPTIONS be set.

3. Save the file, ensuring that it has no extension (such as .txt).

4. Adjust the service name in the installSvc.cmd file as described in these steps:

1. Open the installSvc.cmd file and scroll to the bottom to locate this Comment line:
rem *** Install the service

2. In the section following the above line, change the bolded values as shown in this example:

"%WL_HOME%\server\bin\beasvc" -install -svcname:"Oracle WebLogic %DOMAIN_NAME%_%SERVER_NAME%" -javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" -maxconnectretries:"%MAX_CONNECT_RETRIES%" -host:"%HOST%" -port:"%PORT%" -extrapath:"%EXTRAPATH%" -password:"%WLS_PW%" -cmdline:%CMDLINE%

In the above example, the default service name is changed to Oracle WebLogic <domain><server>.

Note:
The default service name is:
beasvc <domain><server>

5. Execute your CreateWLSSvc.cmd script as Administrator and check the Windows Services window. For example:

6. The uninstall service script is located in the same directory:
<MW_HOME>\wlserver_10.3\server\bin

7.1.3 Creating a Process to Remove the WebLogic Admin Console from the Windows Services

Use this procedure to create a process that will remove the WebLogic Admin Console Process from Windows Services.

1. Create a RemoveWLSSvc.cmd file with these lines:

echo off
SETLOCAL
set DOMAIN_NAME=E1_Apps
set SERVER_NAME=AdminServer
call "C:\Oracle\Middleware\wlserver_10.3\server\bin\uninstallSvc.cmd"
ENDLOCAL

2. Edit this section of the uninstallSvc.cmd to have the exact service name you have used before. For example, using the example in this guide the lines would be:

rem *** Uninstall the service

"%WL_HOME%\server\bin\beasvc" -remove -svcname:"Oracle WebLogic %DO-MAIN_NAME%_%SERVER_NAME%"

7.2 Start the Node Manager Manually

Note:
The JD Edwards EnterpriseOne Server Manager requires that Node Manager is running in order to start and stop managed servers. You can start Node Manager as a background process.

To start the Node Manager:

1. Open a command window with the Run as Administrator option.

2. Change directory to:
Oracle WebLogic 12c

<weblogic_server_install_location>\user_projects\domains\<domain_name>\bin

Oracle WebLogic 10.3.5 and 10.3.6

<weblogic_server_install_location>\wlserver_10.3\server\bin

3. Start the Node Manager by executing this script from the command prompt:
> startNodeManager.cmd

7.3 Enable Node Manager as a Windows Service

When running on Microsoft Windows, Oracle recommends that you configure Node Manager to run as a Windows service as described in the following procedure.

1. Open a command window with Run as Administrator option.

Note:
If you do not execute this command as an Administrator, you cannot install the service.

2. Change directory to:
Oracle WebLogic 12c

<weblogic_ server_install_location>\user_projects\domains\<domain_name>\bin

Oracle WebLogic 10.3.5 and 10.3.6

<MW_HOME>\wlserver_10.3\server\bin

3. Execute this command to install Node Manager
> installNodeMgrSvc.cmd

4. Open the Windows Services and verify this service is installed:
Oracle WebLogic NodeManager

If the service is successfully installed, now you can start and stop Node Manager from Services.

Note:
By default the Node Manager is set to listen on port 5556. You can change the default port in the nodemanager.properties file that is located in this directory:
Oracle WebLogic 12c

<MW_HOME>\user_projects\domains\<domain_name>\nodemanager

Oracle WebLogic 10.3.5 and 10.3.6

<MW_HOME>/wlserver_10.3/common/nodemanager

If you need to change the default port value, you must verify the listen port matches your new value. Use this procedure to verify that your port value matches your new value:

1. Open the WebLogic Server Administration Console.

2. Go to this section:
Domain - Environment - Machines

3. Double click on your machine name.
Click the Node Manager tab and verify the Listen Port.

4. You also need to edit these scripts to match your new listen port:
installNodeMgrSvc.cmd

uninstallNodeMgrSvc.cmd

7.4 Create the Machine Definition

Caution:
JD Edwards EnterpriseOne Server Manager requires a Machine to be defined prior to creating a J2EE Server.

Note:
You can skip this step if you have created the machine definition during the installation.

To create the machine definition:

1. Open a supported web browser.

2. Open the Oracle WebLogic Admin Console using this URL syntax:
http://host:port/console

3. At the prompts, enter the Admin user and password.

4. From the Domain Structure, navigate to Environment > Machines.

5. In the top-left Change Center pane, click the Lock & Edit button.

6. In the Summary of Machines pane, click the New button.

7. On Create a New Machine, enter the machine name in the Name field.

8. In the Machine OS drop-down menu, select the machine OS type. Use Other for Windows and other non-UNIX operating systems.

9. Click Next.

10. Accept the following default values for the Node Manager Properties:

- (Protocol) Type = SSL

- Listen Port = 5556

11. Click Finish.

12. In the Change Center pane, click the Activate Changes button.

8 Upgrading to WebLogic Server 10.3.6.0

This chapter discusses these topics:

- Section 8.1, "Before You Begin"

- Section 8.2, "Installing and Verifying the JDK Version"

- Section 8.3, "Running OUI to Upgrade an Existing WebLogic Server to 10.3.6"

8.1 Before You Begin

Before you begin upgrading your existing WebLogic Server version to WebLogic 10.3.6.0:

- Shut down all WebLogic processes you want to upgrade such as:

- Node Manager

- Admin Server

- All Managed Servers

- Download a new version of JDK 1.7+.

Note:
A plus sign '+' after the version number indicates that this and its subsequent versions are supported.

- Download this patch set for Oracle WebLogic 10.3.6.0: Patch 13529623 (p13529623_1036_Generic.zip)
Unzip the file in a temporary location and confirm the extracted contains this file:

wls1036_upgrade_generic.jar

8.2 Installing and Verifying the JDK Version

In order to meet the MTRs for the requisite JDK, if you need to install a new JDK you should install it to a different location. Otherwise you should completely uninstall the existing JDK and replace it with the newer version.

To install and verify the level of an existing JDK, refer to the section of this guide entitled: Section 6.4, "Installing and Verifying the JDK Version."

8.3 Running OUI to Upgrade an Existing WebLogic Server to 10.3.6

This section describes running the Oracle Universal Installer (OUI) to upgrade an existing WebLogic Server to 10.3.6.

1. Locate this patchset from the temporary location where you downloaded it in Section 8.1, "Before You Begin":
wls1036_upgrade_generic.jar

2. Open a Command window with Run as Administrator option and run this command from the prompt:
>java -jar wls1036_upgrade_generic.jar

Upon execution, the installer starts preparing the OUI install program.

3. On Choose Middleware Home Directory, select the existing Middleware home you wish to upgrade.

4. Click the Next button.

5. On Register for Security Updates, the Email address and/or the My Oracle Support Password fields as applicable.

6. Click the Next button.

7. On Choose Products and Components, verify the components.

Note:
The OUI installer automatically selects the Oracle Coherence component. You can choose to select or deselect this component, keeping in mind that this server type has not yet been verified with Oracle JD Edwards EnterpriseOne.

8. Click the Next button.

9. On Choose Product Installation Directories, verify the directory locations for the previously selected products and components.

Note:
A new version of Oracle Coherence_3.7 will be installed.

10. Click the Next button.
OUI begins copying the files and performs the upgrade.

11. On Installation Complete, click the check box for Run Quickstart to continue with the upgrade of the Oracle WebLogic domains.

12. Click the Done button to complete the installation and exit OUI.
The Quickstart configuration screen appears.

To manually launch the QuickStart configuration wizard, run this executable:

<MW_HOME>\oracle_common\common\bin\config.cmd

13. On the QuickStart links panel, select this link:
Upgrade domains to version 10.3.6

An Upgrade Wizard is launched.

14. On the Welcome panel of the Upgrade Wizard, review and complete the tasks listed in the Prerequisites section of the above screen.

15. When the Prerequisite tasks are complete, click the Next button.

16. On Select WebLogic Version, select this radio button:
9.0 or higher

17. Click the Next button.

18. On Select a Domain to Upgrade, drill down through the Oracle\Middleware\user_projects\domains directory structure and select the Oracle JD Edwards domain. For example:
E1_Apps

19. Click the Next button.

20. On Inspect Domain, review the upgrade configuration selections.

21. Click the Next button.

22. On Select Upgrade Options, select this check box:
Back up current domain (recommended)

Caution:
The wizard advises you that if you choose the check box or Add log files to backup zip, the resultant zip file can be extremely large.

23. On Domain Backup, review the message.

24. Click the Next button.

25. On Select Directory for Domain Backup, you can accept or change location and filename of the backup zip file.

26. The wizard shows the progress of the domain backup.

27. When the backup is complete, click the Next button.

28. On Finalize Domain Upgrade, review the message.

29. Click the Next button to begin the Upgrade.

30. On Upgrade Complete, click the Done button to exit OUI.

Note:
As a result of this domain upgrade, you do not need to individually upgrade any Managed Server.

31. Start the WebLogic NodeManager.

32. Start the WebLogic Administration Console.

33. Start the existing Managed Server such as the Oracle JD Edwards EnterpriseOne HTML server.

34. Test and verify the upgrade.

9 Upgrading to WebLogic Version 10.3.5.0

This chapter discusses these topics:

- Section 9.1, "Before You Begin"

- Section 9.2, "Installing and Verifying the JDK Version"

- Section 9.3, "Running OUI to Upgrade an Existing WebLogic Server to 10.3.5"

9.1 Before You Begin

Before you begin upgrading your existing WebLogic Server version to WebLogic 10.3.5.0:

- Shut down all WebLogic processes you want to upgrade such as:

- Node Manager

- Admin Server

- All Managed Servers

- Download a new version of JDK, where your options are:

- JRockit-R28.1.3-1.6.0_24+

- Oracle Sun JDK 1.6.0_24+

Note:
A plus sign '+' after the fourth digit in the version number indicates that this and its subsequent versions are supported.

- Download this patch set for Oracle WebLogic 10.3.5.0: 12395574. (p12395574_ 1035_Generic.zip)
Unzip the file in a temporary location and confirm the extracted contains this file:

wls1035_upgrade_generic.jar

9.2 Installing and Verifying the JDK Version

In order to meet the MTRs for the requisite JDK, if you need to install a new JDK you should install it to a different location. Otherwise you should completely uninstall the existing JDK and replace it with the newer version.

To install and verify the level of an existing JDK, refer to the section of this guide entitled: Section 6.4, "Installing and Verifying the JDK Version."

9.3 Running OUI to Upgrade an Existing WebLogic Server to 10.3.5

This section describes running the Oracle Universal Installer (OUI) to upgrade an existing WebLogic Server to 10.3.5.

1. Locate this patchset from the temporary location where you downloaded it in Section 9.1, "Before You Begin":
wls1035_upgrade_generic.jar

2. Open a Command window with Run as Administrator option and run this command from the prompt:
Upon execution, the installer starts preparing the OUI install program.

3. On Choose Middleware Home Directory, select the existing Middleware home you wish to upgrade.

4. Click the Next button.

5. On Register for Security Updates, the Email address and/or the My Oracle Support Password fields as applicable.

6. Click the Next button.

7. On Choose Products and Components, verify the components.

Note:
The Oracle Coherence Server is a new component for 10.3.5. The OUI installer automatically selects this component. You can choose to select or deselect this component, keeping in mind that this server type has not yet been verified with Oracle JD Edwards EnterpriseOne.

8. Click the Next button.

9. On Choose Product Installation Directories, verify the directory locations for the previously selected products and components.

10. Click the Next button.
OUI begins copying the files and performs the upgrade.

11. On Installation Complete, click the check box for Run Quickstart to continue with the upgrade of the Oracle WebLogic domains.

12. Click the Done button to complete the installation and exit OUI.
The Quickstart configuration screen appears.

13. On the QuickStart links panel, select this link:
Upgrade domains to version 10.3.5

An Upgrade Wizard is launched.

14. On the Welcome panel of the Upgrade Wizard, review and complete the tasks listed in the Prerequisites section of the above screen.

15. When the Prerequisite tasks are complete, click the Next button.

16. On Select WebLogic Version, select this radio button:
9.0 or higher

17. Click the Next button.

18. On Select a Domain to Upgrade, drill down through the Oracle\Middleware\user_projects\domains directory structure and select the Oracle JD Edwards domain. For example:
E1_domain

19. Click the Next button.

20. On Inspect Domain, review the upgrade configuration selections.

21. Click the Next button.

22. On Select Upgrade Options, select this check box:
Back up current domain (recommended)

Caution:
The wizard advises you that if you choose the check box or Add log files to backup zip, the resultant zip file can be extremely large.

23. On Domain Backup, review the message.

24. Click the Next button.

25. On Select Directory for Domain Backup, you can accept or change location and filename of the backup zip file.

26. Click the Next button.

27. On Restructure Domain Directory, review the message.

28. Click the Next button.

29. On Finalize Domain Upgrade, review the message.

30. Click the Next button to begin the Upgrade.

31. On Upgrade Complete, click the Done button to exit OUI.

Note:
As a result of this domain upgrade, you do not need to individually upgrade any Managed Server.

32. Start the WebLogic NodeManager.

33. Start the WebLogic Administration Console.

34. Start the existing Managed Server such as the Oracle JD Edwards EnterpriseOne HTML server.

35. Test and verify the upgrade.

10 Understanding EnterpriseOne HTML Server Package Discovery

Starting with JD Edwards EnterpriseOne release 8.12, EnterpriseOne specs are delivered in XML format. The new format enables the specs to be stored in database tables instead of the TAM files, and is called Shared Object Configuration. In this configuration, both Enterprise Servers and HTML Servers access the same database for the same set of specs.

Before release 8.12, whenever a new package was deployed to the Enterprise Server, you had to install the package on a development client and manually generate serialized objects for the HTML Server. With release 8.12, however, manual generation is now optional. Instead, the JD Edwards EnterpriseOne now automatically generates objects on the fly if they do not exist in the serialized object tables.

When you deploy a package to the Enterprise Server, the HTML Server automatically discovers the new package and purges all serialized records impacted by the package. If a full package is deployed, the HTML Server deletes all serialized object records. If an update package is deployed, the HTML Server deletes only those records that are included in the update package. It also removes the impacted objects from in-memory cache. After the package deployment is complete, when a user accesses an EnterpriseOne object, this object is generated on the fly using the new specs delivered in the package.

To ensure the integrity of the specs, the HTML Server must be configured so that:

- Each EnterpriseOne HTML Server instance includes only one path code and one package within the path code.

- All users accessing a JD Edwards EnterpriseOne HTML Server instance access only one package.

- Serialized object databases are not shared among multiple EnterpriseOne HTML Server instances, unless all these instances run on the same path code and same package.

This section describes these topics:

- Impacts to End Users

- Understanding the Manifest

10.1 Impacts to End Users

During package deployment, the HTML Server stops responding to user requests until the package is deployed and serialized objects are purged. During this process, user will not able to log in. Users that are already logged in prior to the package deployment will not be able to launch new forms until the package deployment is complete.

10.2 Understanding the Manifest

Each package now contains a package manifest. The manifest is a record in a new table that is created every time a package is built. The package manifest contains a date/time stamp for the package build and information about the package content. For update packages, it also contains a list of objects included in the package.

Each serialized object table now contains a serialized object manifest. This manifest indicates what specs are used to generate the serialized objects. For example, the manifest includes the name of the package used to generate the serialized objects. To ensure the integrity of the system, all serialized objects are generated from the same package.

When the HTML Server detects a package deployment, it compares the package manifest with the serialized object manifest. If a new package is deployed, the package manifest will be different than the serialized object manifest. The HTML Server purges the serialized objects table of objects listed in the package manifest. The HTML Server then updates the serialized object manifest so it is consistent with the package manifest. This entire process is automatic and does not need administrator involvement.

If you decide to generate objects manually using the eGenerator, you must generate the manifest manually for the discovery process to work. For instructions on how to generate the manifest, see Section A.4, "Generating the Serialized Object Manifest" in Appendix A, "Generating JD Edwards EnterpriseOne Serialized Objects".

11 Uninstalling or Deinstalling WebLogic

This chapter discusses these topics:

- Section 11.1, "Uninstalling WebLogic 10.3.5.0 or 10.3.6.0"

- Section 11.2, "Deinstalling WebLogic 12c"

11.1 Uninstalling WebLogic 10.3.5.0 or 10.3.6.0

To uninstall WebLogic 10.3.5.0 or 10.3.6.0:

1. Stop all Oracle WebLogic processes such as the Admin Server, Managed Server, and Node Manager.

2. Stop the JD Edwards EnterpriseOne Server Manager agent associated with the Oracle WebLogic Server that you wish to uninstall.

3. On the WebLogic Server that you wish to uninstall, navigate to this directory:
uninstall.cmd

4. Execute this command to launch and execute the deinstaller program:
uninstall.cmd

5. Once the uninstall program completes the deinstallation, you should manually remove any WebLogic Server directories if they exist.

11.2 Deinstalling WebLogic 12c

To deinstall WebLogic 12c:

1. Navigate to this directory:
MW_Home\oui\bin

2. Launch this Oracle Universal Installer (OUI) deinstaller program that is located in the above directory
deinstall.cmd

A Generating JD Edwards EnterpriseOne Serialized Objects

Note:
To generate objects using an Release 9.1 application server, you must use JDK Version 1.6 on the client machine. Additionally, you must modify the gen_oas.bat file on the client machine to point to the location of your JDK Version 1.6.

Starting with application release 8.12, JD Edwards EnterpriseOne specs are delivered in XML format, which allows for on-demand generation of serialized objects from these XML specs. Objects are now automatically generated when the first user accesses an application, and the only objects not automatically generated are FDA-created portlets.

Note:
If you are running JD Edwards EnterpriseOne application version 8.9, 8.10, 8.11, or 8.11 SP1 with the 8.96 Tools Release, refer to the 8.95 version of the guide to install and configure eGenerator. The tasks described in this appendix are only valid for the JD Edwards EnterpriseOne 8.12 application.

eGenerator can still be used to manually generate serialized objects. It is the only method for generating FDA-created portlets, so is required if you installed a JD Edwards EnterpriseOne Portal. eGenerator is also an optional path for generating any set of objects, including a complete set of objects.

The eGenerator allows manual control over the process that turns JD Edwards EnterpriseOne specifications into Java code, which enables you to access JD Edwards EnterpriseOne applications in HTML. The JD Edwards EnterpriseOne forms and applications that you generate, either manually from eGenerator, or automatically using on-demand generation, are serialized Java objects. JD Edwards EnterpriseOne stores these objects in a database (in serialized object tables F989998 & F989999), and retrieves them at runtime.

eGenerator requires a specific machine configuration. While it is possible to configure a web server as the generation machine for release 8.12, you should dedicate a separate generation machine for this process. The configuration of this machine depends on the release of JD Edwards EnterpriseOne you installed.

For a list of all requirements for the generation machine, refer to Chapter 1, "Accessing Certifications (formerly Minimum Technical Requirements)" in this guide.

If you upgraded to JD Edwards EnterpriseOne from a previous release and customized your JD Edwards EnterpriseOne objects, you should first test your custom modifications, then generate serialized JAS objects from the upgraded path code.

Complete the tasks below to install eGenerator and generate JD Edwards EnterpriseOne JAS objects from a set of JD Edwards EnterpriseOne objects.

- Section A.1, "Installing eGenerator"

- Section A.2, "Logging In"

- Section A.3, "Configuring eGenerator"

- Section A.4, "Generating the Serialized Object Manifest"

- Section A.5, "Generating an FDA-Created Portlet"

- Section A.6, "Generating All Standard Serialized Objects"

- Section A.7, "Generating a List of Objects (Bulk Generation)"

- Section A.8, "Verifying the Generation Process"

- Section A.9, "Generating Other Selected Objects Using JD Edwards EnterpriseOne 8.12"

A.1 Installing eGenerator

This section discusses the tasks you follow to install the eGenerator:

- Section A.1.1, "Prerequisites"

- Section A.1.2, "Installing the Generator Program (JD Edwards EnterpriseOne 8.9 only)"

- Section A.1.3, "Setting the Default Storage Parameter (SQL only)"

- Section A.1.4, "Preparing JD Edwards EnterpriseOne for Serialized Objects"

A.1.1 Prerequisites

Before you install the eGenerator, verify that the tasks below are completed for your version of JD Edwards EnterpriseOne:

- Tasks for JD Edwards EnterpriseOne 8.9:

- Install a JD Edwards EnterpriseOne client that is running at the same Tools Release level as the HTML Server. For instructions on installing a JD Edwards EnterpriseOne client, see the JD Edwards EnterpriseOne Development Client Installation Guide.

Note:
Make sure you install an appropriate database client for your JD Edwards EnterpriseOne client.

- The Web Development client cannot be installed using JD Edwards EnterpriseOne 8.9. Instead, complete the task below, Section A.1.2, "Installing the Generator Program (JD Edwards EnterpriseOne 8.9 only)", to configure the JD Edwards EnterpriseOne client.

- Tasks for JD Edwards EnterpriseOne 8.10, 8.11, and 8.11 SP1:

- Complete the task: "Copying the JDBC Drivers and the tnsnames.ora file to the Deployment Server" in the JD Edwards EnterpriseOne Development Client Installation Guide.

Caution:
This task must be completed by a JD Edwards EnterpriseOne system administrator before you complete any of the tasks below.

- Install the Web Development Client to set up eGenerator.
If the Web Development Client installs successfully, eGenerator is automatically configured to run without modifying any of the files used in the generation process.

Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for instructions to install the Web Development Client.

- Secondary tasks for all JD Edwards EnterpriseOne releases:

- Complete this task if you are using DB2 UDB on the Enterprise Server.
On the Generation machine, open the db2cli.ini file and comment out or remove the LobCachSize parameters under database aliases associated with JD Edwards EnterpriseOne. This file is typically located under DB_HOME\SQLLIB\.

A.1.2 Installing the Generator Program (JD Edwards EnterpriseOne 8.9 only)

Complete this task to install and configure the generator program on the generation machine. If you are using JD Edwards EnterpriseOne 8.10, 8.11, or 8.11 SP1, skip this task.

To install the generator program

1. On the generation machine, open Microsoft Windows Explorer and navigate to this directory on the Deployment Server:
\\<deployment_server>\EnterpriseOne\OneWorld Client Install\Third Party\WebDevFeature

2. Run the OH4A_setup.exe file.
The program runs automatically and complete the installation with no input from the installer.

3. From Microsoft Windows Explorer, navigate to this directory on the generation machine:
x:\B9\system\OC4J\j2ee\home\applications\webclient.ear\webclient

4. Open gen_oas.bat in a text editor.

5. Replace this line in the gen_oas.bat file:

set JAVA_PGM=C:\B9\system\JRE\1.4\bin\java.exe

with this line:

set JAVA_PGM=<WebSphere Install Location>\AppServer\java\bin\java.exe

where <WebSphere Install Location> is the location where WebSphere is installed.

6. Replace this line in the gen_oas.bat file:

set GEN_CLASSPATH=%GEN_CLASSPATH%;%J2EE_HOME_LIB%\servlet.jar

with these three lines:

set GEN_CLASSPATH=%GEN_CLASSPATH%;<WebSphere Install Location>\AppServer\lib\j2ee.jar
set GEN_CLASSPATH=%GEN_CLASSPATH%;<WebSphere Install Location>\AppServer\lib\xalan.jar
set GEN_CLASSPATH=%GEN_CLASSPATH%;<WebSphere Install Location>\AppServer\lib\xerces.jar

7. Save the changes to the gen_oas.bat file.

A.1.3 Setting the Default Storage Parameter (SQL only)

The default storage parameter on your JD Edwards EnterpriseOne database might not enable enough space to transfer all the standard JD Edwards EnterpriseOne Java objects. To avoid this problem, complete the task below that is relevant to your database:

To set the default storage parameter:

1. Open the SQL database and set your database Maximum File Size parameter to "Unrestricted file growth."
Complete this step for each database (for example, PY900) to which you are installing the Java objects.

A.1.4 Preparing JD Edwards EnterpriseOne for Serialized Objects

Before you generate serialized Java objects in JD Edwards EnterpriseOne, complete this task to link to the JD Edwards EnterpriseOne serialized object tables on the Java generation machine.

Complete this task to configure the [JDBj-SPECDATASOURCE] section of the jdbj.ini file to point to the JD Edwards EnterpriseOne serialized object tables. If this file does not point to the correct database, you cannot access the JD Edwards EnterpriseOne serialized object tables. Alternately, you can comment out this section. If the [JDBj-SPECDATASOURCE] section is commented out or deleted from the jdbj.ini file, the HTML Server uses the Object Configuration Manager (OCM) to access the serialized object tables.

To link to the JD Edwards EnterpriseOne server database:

1. Using a text editor, open the jdbj.ini file located in the following directory:
<JAS_HOME>\EA_JAS_80.ear\webclient.war\WEB-INF\

2. Modify the [JDBj-SPECDATASOURCE] section of the jdbj.ini file to point to the JD Edwards EnterpriseOne database server containing the serialized object tables, or comment out this section to use the OCM to access these tables.

3. Save the jdbj.ini file.

A.2 Logging In

Using eGenerator, you can generate JD Edwards EnterpriseOne objects in one of these ways:

- Section A.2.2, "Generate to the Web Server"

- Section A.2.3, "Bypass the Web Server and Generate Serialized Objects Directly to the Serialized Object Tables"

Each method of generation has a specific way to log into eGenerator. Select the task that corresponds to the way you want to generate objects.

A.2.1 Running the eGenerator Diagnostic Tool

eGenerator now includes an application that is automatically launched every time eGenerator is started. This application is a diagnostic tool that checks the configuration of eGenerator and reports incorrect settings. The diagnostic tool categorizes errors into two types: fatal and non-fatal. If a fatal error is detected, the application displays an error message and does not enable eGenerator to launch. If a non-fatal error is detected, the application displays an error message but enables you to continue with the Generation process.

Note:
The auto diagnostic tool can be suppressed by launching gen.bat with the -nodiag parameter.

The auto diagnostic tool performs these operations for general use:

The auto diagnostic tool performs these operations for general use for Direct Generation:

Operation

Fatal Error

Generates a Web Code Level Object, which is used by JAS at startup to determine if its code matches the generated objects.

X

Checks the location of the jas.ini file and validates these key parameters in the file.

Checks the location of the location of the jas logs.

For JAS Generation Only

Operation

Fatal Error

Verifies that the Tools Release of the JAS code on the generation machine matches the Tools Release of the JAS code on the HTML Server (fatal error).

X

A.2.2 Generate to the Web Server

Complete this task if you want to generate objects to the web server. If you want to bypass the Web server and generate objects directly to a database, skip this task and complete the next task below.

To generate to the web server

1. On your generation machine, select your configuration below, navigate to the corresponding directory, and run the launchGen.bat file in that directory:

- For JD Edwards EnterpriseOne 8.10, 8.11, or 8.11 SP1 running WebSphere:
x:\<release>\JAS

- For JD Edwards EnterpriseOne 8.9 (either application server)
x:\<release>\system\OC4J

Note:
If you do not want to run the diagnostic program, include the parameter -nodiag in the command statement when you run launchGen.bat. See the section, Section A.2.1, "Running the eGenerator Diagnostic Tool", for more information about the autodiagnostic tool.

2. On JD Edwards EnterpriseOne Sign On, log on to a Java environment in JD Edwards EnterpriseOne (for example, JPY900).

Tip:
After you click OK to log on to a JD Edwards EnterpriseOne environment, it can take up to 2 minutes for JD Edwards EnterpriseOne to complete the log on process.

3. On Generator, complete this field:

- JAS Server Name
Enter machine name:port, where machine name is the name of your web server and port is the port number for the EnterpriseOne instance.

eGenerator generates all objects to this Web server.

4. Select where the specs exist for generation. You can generate specs from a specific set of Central Objects or a particular path code. By default, Default Spec Files will be used. Default Spec Files reside on the local machine.
Choose one of the following options:

- To generate specs from a particular set of Central Objects:
Click the Central Objects radio button, and enter the Path Code where the specs are stored.

- To generate specs from a specific package:
Click the Package radio button, and enter the name of the Package and the DataSource where the specs are stored.

5. Click Connect.
The system connects to the Web server that you indicated. A message appears on the status bar when login is complete.

Once you have logged in to a Web server, skip the following task and refer to the sections below it for information on how to generate objects.

A.2.3 Bypass the Web Server and Generate Serialized Objects Directly to the Serialized Object Tables

Select direct generation by clicking the Direct Generation radio button in the Connection section on the eGenerator application.

In this mode, the generator initializes a "mini" JAS Server instance on the generation machine. During generation, the generator will by-pass the actual JAS Server and store the objects directly to the serialized object tables. After you complete this task, you can set up the HTML Server to read from the pre-populated serialized object tables.

Advantages:

- Can generate objects before setting up the HTML Server.

- Faster for all forms of generation.

- Easier to maintain.

Disadvantages: You have to configure the generation machine.

Complete this task to generate objects directly to a database.

To generate objects directly to a database

1. Run launchGen.bat.

Note:
If you do not want to run the diagnostic program, include the parameter -nodiag in the command statement when you run launchGen.bat. See the section, Section A.2.1, "Running the eGenerator Diagnostic Tool", for more information about the autodiagnostic tool.

2. On JD Edwards EnterpriseOne Sign On, log in to a Java environment (for example, JPY9).

3. Click the Direct Generation radio button.

In Direct Generation Mode the eGenerator locates the serialized object database by looking for the database server in the server= setting of the JDBj-SPEC DATA SOURCE section of the jdbj.ini file located on the generation machine.

4. Click Connect.
The system bypasses the Web server and connects directly to the database specified in the jdbj.ini file.

A.3 Configuring eGenerator

eGenerator includes a number of options you can set up for your particular environment. The configuration process consists of these tasks:

- Section A.3.1, "Setting eGenerator Options"

- Section A.3.2, "Choosing Languages"

- Section A.3.3, "Configuring the genapp.ini File"

A.3.1 Setting eGenerator Options

Before generating objects, you can define a variety of parameters that affect how the eGenerator functions.

To set eGenerator options

1. From the pull-down menu, select OptionsAdvanced Settings.

2. On Advanced Settings, select the options appropriate for your generation requirements

- Logging
Specify whether to log the generation process by clicking the check boxes next to the Status and Error logs. You can also enter the location of the log files. Logging is crucial for troubleshooting problems with the generation process.

- Generation Modes
Specify if the generation of All Objects will be done in parallel mode or sequential mode by checking the appropriate radio button.

For more information on Generation Modes, see Section A.3.1.1, "Generation Modes".

- User Option
You can generate a public version of the applications or a personal version by choosing the relevant option. Personal versions are only available to the person who created the versions, and are only intended for developers.

A.3.1.1 Generation Modes

The eGenerator has these modes for generating web objects:

- Section A.3.1.1.1, "Sequential Generation"

- Section A.3.1.1.2, "Parallel Generation"

A.3.1.1.1 Sequential Generation

In this mode the web objects are generated one after the other when you select the Generate-All Objects option. You can set this mode by clicking OptionsAdvanced Settings, then clicking Sequential Generation.

Advantages:

- Most stable mode of generation.

- Requires the least system resources, e.g. memory.

- Safe to use during a JITI (Just in Time Install) process.

Disadvantage: The generation process can take longer.

A.3.1.1.2 Parallel Generation

This is the default mode of generation. You can turn off this mode of generation by clicking Advanced Settings, then clicking Sequential Generation.

In this mode of generation the web objects are generated concurrently when you select the Generate-All Objects option

Advantage: Faster than Sequential Generation, especially with multi-processor workstations and fast database connections.

Disadvantages:

- Cannot be used when the user doesn't have the full set of spec files, because JITI might occur.

- If a JITI occurs during parallel generation, the spec files can get corrupted.

A.3.2 Choosing Languages

You can generate applications and reports in the language you desire by selecting any of the supported languages on the eGenerator application.

Note:
You must install the Language CD for each language you want to use.

To select languages

1. On eGenerator, select OptionsLanguages from the pull-down menu.

2. Click the check box next to each of the languages you want to use.

3. Click OK.

A.3.3 Configuring the genapp.ini File

The genapp.ini file contains the list of applications that you want generated in a mode other than the default mode, which is mode 1. In the genapp.ini file, you can list applications you want generated in one of the other modes: Mode 2 or Mode 3.

Do not modify this file unless you created custom applications using Mode 2 or Mode 3.

A.4 Generating the Serialized Object Manifest

The section describes how to generate the manifest for the set of objects in the serialized object tables. For an overview of the serialized object manifest and a description of the package discovery process, refer to Chapter 10, "Understanding EnterpriseOne HTML Server Package Discovery".

To generate serialized object manifests

1. From the pull-down menu, select GenerateManifest.

2. Click Create Manifest.

3. Click Yes.
The program creates the manifest and closes the window.

4. To view the manifest that was created, from the pull down menu, select GenerateManifest.

The Manifest Info section displays the name of the package, the build date, and the deployment date. This manifest shows that no update packages were deployed.

The Manifest Audit Info field contains information about the user and the machine that created the manifest.

A.5 Generating an FDA-Created Portlet

You can create Portlets using EnterpriseOne Form Design Aid. Before these portlets can be used by the portal server, you must manually generate them from eGenerator.

To generate a FDA-created portlet

1. On eGenerator, select GeneratePortlet Deployment.

2. Select the .war file that you want to generate.
Typically, the .war file for the local version of Collaborative Portal resides in C:\B9\system\Generator\WebClient_Portal.war.

eGenerator reads the local specifications for JD Edwards EnterpriseOne and lists all portlets it discovers.

3. Select the version you want to generate.
eGenerator creates a new portlet descriptor file and bundles it into a new WebClient_Portal.war file.

Note:
For an overview of portlet creation and deployment, see Generating Portlets for Collaborative Portal in the JD Edwards EnterpriseOne Tools 8.98 Development Tools: Form Design Aid Guide.

4. Clear the check box next to any portlet that you do not want to generate, and click Start.
If multiple versions of an application exist, each version is listed.

A.6 Generating All Standard Serialized Objects

eGenerator can generate a complete set of Java Serialized Objects from JD Edwards EnterpriseOne objects. These serialized objects enable you access to all JD Edwards EnterpriseOne objects when you run your web server. If, however, you only want to generate a partial set of objects, skip this task and complete the relevant task in the section: Section A.9, "Generating Other Selected Objects Using JD Edwards EnterpriseOne 8.12".

Complete this task to generate a complete set of JD Edwards EnterpriseOne objects.

To generate all JD Edwards EnterpriseOne objects

1. From the pull-down menu, select FileCore Objects.
For more information on generating core objects, see Section A.9.1, "Generating Core Objects".

2. If the core objects generate successfully, from the pull-down menu, select GenerateAll Objects .

3. On Generate All Objects, check all the objects listed.

4. Click Start.
eGenerator checks the database connection before it attempts to generate objects.

If it cannot connect to the database, eGenerator displays this screen:

5. If this screen displays, click Stop and verify the connection to the database.

6. If the last Generate-All session did not conclude successfully, eGenerator displays a screen with the details of the failed generation.
Select one of these options:

- To resume the previous generation process, click RESUME OLD SESSION. You should select this option, which restarts the previous process from the point of failure. Once the previous process completes, you can repeat this task to generate the new set of objects.

- To cancel the previous generation process and generate the new objects, click CREATE NEW SESSION.
Select this option if you are currently generating a complete new set of all object types.

In either case, an object set starts generating. The progress of object generation is displayed on the screen: the blue progress bar indicates the progress of the generation process, and the green progress bar indicates the progress of objects inserted into the database.

If the database insertion of objects is not complete when the generation is done, the eGenerator displays the number of objects remaining in the queue.

Once all the objects are inserted into the database, the program displays a message that the "Generation completed successfully."

A.7 Generating a List of Objects (Bulk Generation)

If you are running EnterpriseOne release 812, the JAS servers generates objects on demand. To reduce the performance impact of on-demand generation, you can manually generate a list of the most frequently used applications from a list defined in a text file, and let other applications or reports to be generated on demand.

A sample text file named BulkGen.txt is included with the HTML Server or Web Development Client under the WEB-INF directory. This file contains sample entries in the format that can be read by the eGenerator. Modify this file to include just the large, frequently used applications.

To run the bulk generation file

1. Run launchGen.bat.

2. On eGenerator, complete this field:

- Bulk Generation File: Enter the name of the file, or click Select File, and select the Bulk Generation File.

It may take some time for the system to connect to the file.

3. Select a Connection option (either Direct Generation or JAS Server).

4. Select Default Spec Files.

5. Click Connect.

6. Log on to JD Edwards EnterpriseOne and click OK.

7. From the pull-down menu at the top of the screen, select FileBulk Generation.

8. Click Start.
eGenerator will generate all the objects listed in the file you selected. When the process is complete, eGenerator displays a message: Generation Completed Successfully.

Tip:
The update package build generates a GeneratorList.txt file in the work directory of the package. The GeneratorList.txt file is a well formed bulk generation file that lists the objects included in the update package. You can use this file for Bulk Generation after deploying the update package.

A.8 Verifying the Generation Process

Complete these tasks to verify the generation is successful:

- Section A.8.1, "Checking Log Files"

- Section A.8.2, "Checking Database Acknowledgements"

A.8.1 Checking Log Files

eGenerator enables you to automatically display the Status Log and Error Log files by selecting these options from a menu.

To display the Status Log

1. On eGenerator, select LogsStatus Log from the pull-down menu.

To display the Error Log

1. On Generator, select LogsError Log from the pull-down menu.

A.8.2 Checking Database Acknowledgements

The status log records whether an object is successfully inserted in the database. This enables the user to monitor the generation process and verify that objects are successfully generated.

These acknowledgments will not be printed for data dictionary Items or Data Structures, however, because they are too numerous to be printed on the command line screen.

Below is an example of the output:

Generating application P01012 ...
-->Database Ack:ER_P01012_W01012D successfully inserted into database
-->Database Ack:P01012_HTML_W01012D successfully inserted into database
-->Database Ack:ER_P01012_W01012B successfully inserted into database
-->Database Ack:P01012_HTML_W01012B successfully inserted into database
-->Database Ack:ER_P01012_W01012A successfully inserted into database
-->Database Ack:P01012_HTML_W01012A successfully inserted into database App
generation finished Generating 2 NERs -->Database Ack: ER_P01012_W01012C
successfully inserted into database -->Database Ack: P01012_HTML_W01012C
successfully inserted into database -->Database Ack: NER_PlugAndPlay_P0101
successfully inserted into database NER generation finished Generating 1 PO
Data Structure Items PO Data Structure generation finished Generating 2
Business Views Business View generation finished Generating 5 Tables Table
generation finished Generating 294 Data Dictionary Items Data Dictionary
generation finished Generating 30 Data Structure Items Data Structure
generation finished -->Database Ack:NER_UpdateChangedGeoCode successfully
inserted into database -->Database Ack: PODATAP01012 successfully inserted
into database -->Database Ack:VIEW_V0101E successfully inserted into
database -->Database Ack: TABLE_F0101 successfully inserted into database
-->Database Ack: TABLE_F0111 successfully inserted into database
-->Database Ack: TABLE_F0116 successfully inserted into database
-->Database Ack: TABLE_F03012successfully inserted into database
-->Database Ack: TABLE_F0401 successfully inserted into database

A.9 Generating Other Selected Objects Using JD Edwards EnterpriseOne 8.12

When you deploy an update package of JD Edwards EnterpriseOne objects, you can either depend on the on-demand feature of the HTML Server to generate serialized objects, or you can manually generate selected objects using eGenerator. eGenerator includes several methods of generating a partial set of serialized objects. All but one method, "Generating objects using the Bulk Generation File," are performed by selecting options from the eGenerator screen. The Bulk Generation file enables you to type selected objects directly into a text file and run this file in eGenerator.

Complete one of these tasks to generate a partial set of serialized objects.

- Section A.9.1, "Generating Core Objects".

- Section A.9.2, "Generating Applications".

- Section A.9.3, "Generating Forms".

- Section A.9.4, "Generating Reports".

- Section A.9.5, "Generating NERs".

- Section A.9.6, "Generating Data Dictionary Items".

- Section A.9.7, "Generating Tables".

- Section A.9.8, "Generating Business Views".

- Section A.9.9, "Generating Data Structures".

A.9.1 Generating Core Objects

The core objects are the foundation objects required by other JD Edwards EnterpriseOne components. Generating these objects enables the Java server to run Task Explorer and the Portal without installing specific applications.

To generate core objects

1. On eGenerator, select FileCoreObjects from the pull-down menu.
eGenerator begins generating the core objects and their dependent Data Dictionary Items.

The eGenerator displays the status of the generation once the process is complete.

A.9.2 Generating Applications

Complete one of these tasks to generate one or more applications:

- Section A.9.2, "To generate an application"

- Section A.9.2, "To generate applications by system code"

- Section A.9.2, "To generate applications by mode"

To generate an application

1. From the pull-down menu, select Generate -> Applications.

2. Select Application Name, and enter the program number of the application (for example, P01012).

3. Click Start.
The Generator generates all forms contained in the application and all dependent objects used by the application.

4. Check the Status Log for status of generation.

To generate applications by system code

1. From the pull-down menu, select Generate ->Application.

2. Select Generate by System Code, and type the number of the System Code in the field to the right.

3. Click Start.
eGenerator fetches all the applications under that system code.

4. Confirm the applications were generated by checking the status and error logs.

5. Use this SQL command to verify the applications reside in the database:
SQL> select wboid from f989999 where wboid like 'P%W%';

You can generate applications by modes 1, 2 or 3. These modes determine the look and feel of the applications. For more information on Generation Modes, see the section "Generating Options" in Designing JD Edwards EnterpriseOne Web Applications.

To generate applications by mode

1. From the pull-down menu, select Generate -> Application.

2. Select a mode.

3. Click Application Name, and enter the name of an application (for example, P01012).

4. Click Start.

A.9.3 Generating Forms

To generate a form

1. From the pull-down menu, select GenerateApplications.

2. Enter the form name in the Form Name field, for example, P01012_W01012A.

3. Click Start.
If the form name is invalid, this error message appears:

If the application name is invalid, this error message appears:

4. Check the status log for the generation status.

A.9.4 Generating Reports

Complete one of these tasks to generate one or more reports:

- To generate a report

- To generate a report version

- To generate reports by system code

To generate a report

1. From the pull-down menu, select Generate -> Reports.

2. Enter the name of a report, (for example, R0006P).

3. Click Start.

4. Check the status log for the generation status.
The Generator generates all versions of the report and their corresponding data selection, data sequencing, and Print Information Objects.

5. Confirm the presence of the objects by checking the Status logs, or use this query to check the database:
SQL> select wboid from f989999 where wboid like '%<report_name>%';

To generate a report version

1. From the pull-down menu, select Generate -> Reports.

2. Enter a Report Name and Report Version, for example, R0006P, and XJDE0001.

3. Click Start.
The Generator generates the version and any dependent objects.

4. Check the status log for the generation status.

To generate reports by system code

1. From the pull-down menu, select Generate ->Reports.

2. Select Generate by System Code, and enter a number for the code.

3. Click Start.

eGenerator fetches all the reports under that system code.

4. Check the status and error logs to confirm that all the reports for that system code were generated.

A.9.5 Generating NERs

To generate NERs

1. From the pull-down menu, select GenerateNERs.

2. Enter the name of an NER, for example, GetObjectDesc.

Note:
NERs are case sensitive.

3. Click Start.

4. Check the status log for the generation status.

5. Use this SQL command to verify that the objects reside in the database.
SQL> select wboid from f989999 where wboid like '<NER_ name>'

A.9.6 Generating Data Dictionary Items

To generate Data Dictionary items

1. From the pull-down menu, select Generate -> Data Dictionary.

2. Generate any data dictionary item, for example, OBNM.

3. Check the status log for the generation status.

4. Use this SQL command to verify that the objects reside in the database.
SQL> select wboid from f989999 where wboid like 'DICT_<dd_name>';

A.9.7 Generating Tables

To generate tables

1. From the pull-down menu, select Generate -> Tables.

2. Enter a table number, for example, F9860.

3. Click Start.
eGenerator generates the table and all data dictionary items used by the table.

4. Check the status log for the generation status.

A.9.8 Generating Business Views

To generate business views

1. From the pull-down menu, select Generate -> Business Views.

2. Enter the name of a business view, for example, e.g. V9001B.

3. Click Start.
eGenerator generates the View and all associated tables and data dictionary items.

4. Check the status log for the generation status.

A.9.9 Generating Data Structures

To generate data structures

1. From the pull-down menu, select Generate -> Data Structures.

2. Enter the name of a data structure, for example, D9800150C.

3. Click Start.
eGenerator generates the data structure.

4. Check the status log for the generation status.

5. Use this SQL command to verify that the objects reside in the database:
SQL> select wboid from f989999 where wboid like 'DSTR_ <datastructure_name>'

B Understanding Media Objects on the Web Server

This section provides an overview of jas.ini settings required to access Media Objects on the HTML Server, and the process by which the web server accesses these objects from the network. The last section describes how to secure Media Objects on web-based client machines.

B.1 Required jas.ini Settings

Ensure that these parameters are set in the [OWWEB] section of the jas.ini file.

[OWWEB]

Parameter

Recommended Setting

Description

MO QUEUE=

Site-dependent path

Identifies the media object directory location on your HTML Server. This path must translate into virtual path /jde/moqueue/ for the web browser.

FtpPort=

21

Specifies the default port to be used for FTP.

FtpUsr=

anonymous

Specifies the user id to be used for FTP access to the media Object File Server.

FtpPwd=

anonymous

Specifies the password to be used for FTP access to the media Object File Server.

UseMOWinNTShare=

TRUE

Specifies that the web server use the Microsoft Windows file sharing mechanism for fetching Media Object files from their location into the cached location of the web server.
Note: If this setting is TRUE, media object queue paths set in P98MOQUE must be accessible by the owner of the application server from the application server machine (the application server is the server program hosting web servlets). To test the accessibility of a media object queue path, log in as the owner of the application server, open Windows Explorer, and paste the path to the media object queue into the address field. The path should be accessible without entering a user ID and password.

If this path is not accessible, you can change the media object queue setting to a path accessible by the owner of the application server. For example, you can specify a path on the application server machine as the media object queues directory.

B.2 How Media Objects are Displayed by the HTML Server

This section explains how Media Objects are sent to the HTML client by the HTML Server.

1. A user selects attachments on an application which has support for media objects.

2. The Media Object window displays the image, file, or OLE objects, and the user selects one of these objects.

3. The request goes to the web server.

4. The web server reads the location of the object from the Media Object queue table (F98MOQUE), finds the file, and caches it in the location specified by the MO QUEUE path.
If UseMOWinNTShare is TRUE, files are transferred using Microsoft Windows file sharing mechanism, otherwise files are transferred using FTP protocol.

This diagram illustrates the process:

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.