JD Edwards EnterpriseOne HTML Web Server WebSphere

[1]
JD
Edwards EnterpriseOne
HTML Server on WebSphere Reference Guide
Release 9.2.x for UNIX
E55808-05
November 2017
Describes reference material for the HTML Server.
JD Edwards EnterpriseOne HTML Server on WebSphere Reference Guide, Release 9.2.x for UNIX
E55808-05
Copyright © 2011, 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 ................................................................................................................................................................ vii
Audience...................................................................................................................................................... vii
Documentation Accessibility .................................................................................................................... vii
Related Documents .................................................................................................................................... vii
Conventions ............................................................................................................................................... viii
1 Accessing Certifications
2 Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1)
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10.5
2.11
2.12
2.13
2.14
Before You Begin......................................................................................................................... 2-1
Installing the IBM Installation Manager.................................................................................. 2-2
Installing an IBM WebSphere Application Server 8.5.x/9.0................................................. 2-5
Creating a New Profile for WebSphere Application Server 8.5.x/9.0 ............................. 2-12
Installing the IBM HTTP Server 8.5.x/9.0 ............................................................................ 2-17
Installing Web Server Plug-ins for IBM WebSphere Application Server ........................ 2-22
Enabling SDK 7.0 on WebSphere Application Server 8.5.5 ............................................... 2-26
Switching to SDK 7.0 on WebSphere Application Server 8.5.5 ......................................... 2-28
Installing the WebSphere Customization Toolbox ............................................................. 2-29
Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack................................................... 2-34
Updating the IBM Installation Manager to WebSphere 8.5.x or Greater ................. 2-34
Updating WebSphere Application Server 8.5.x or Greater ........................................ 2-35
Working with the HTTP Server Component................................................................ 2-38
Working with the Plug-ins Component ........................................................................ 2-38
Working with the Customization Toolbox Component ............................................. 2-39
Configuring the IBM Web Server Plug-in ............................................................................ 2-40
Setting the HTTP Server Properties ...................................................................................... 2-46
Manually Generating a Plug-in.............................................................................................. 2-47
Manually Editing the HTTP Configuration File.................................................................. 2-49
3 Installing and Configuring WebSphere 7.0
3.1
3.2
3.3
3.4
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or
Downloaded Image) 3-1
Installing the IBM HTTP Server 7.0....................................................................................... 3-11
Installing IBM HTTP Server Plug-ins for WebSphere Application Server...................... 3-18
Installing the WebSphere Update Installer .......................................................................... 3-27
iii
3.5
3.6
3.7
3.8
3.8.1
3.8.2
3.8.3
3.9
3.10
3.11
3.12
3.13
3.14
3.15
3.16
3.16.1
3.16.2
3.17
3.18
3.19
Installing WebSphere 7.0 Fix Pack 29....................................................................................
Installing the IBM HTTP Server Fix Pack ............................................................................
Installing the WebSphere 7.0 Plug-ins Fix Pack ..................................................................
Verifying the Versions of Installed WebSphere Products..................................................
WebSphere Application Server.......................................................................................
IBM HTTP Server..............................................................................................................
WebSphere Plugins for IBM WebSphere Application Server ....................................
Starting the WebSphere Application Server ........................................................................
Stopping the WebSphere Application Server ......................................................................
Determining the Name and Status of the WebSphere Application Server .....................
Starting the IBM HTTP Server ...............................................................................................
Stopping the IBM HTTP Server .............................................................................................
Accessing the WebSphere Administration Console ...........................................................
Testing the WebSphere and IBM HTTP Server Installation ..............................................
Generating and Propagating WebSphere Plug-ins (optional)...........................................
Generating WebSphere Plug-ins ....................................................................................
Propagating WebSphere Plug-ins ..................................................................................
Creating a New Application Server Profile (optional) .......................................................
Deleting a Profile (optional) ...................................................................................................
Adding a New Web Server for a New Profile (optional)...................................................
3-31
3-35
3-39
3-43
3-43
3-44
3-44
3-44
3-45
3-45
3-46
3-46
3-46
3-48
3-49
3-49
3-51
3-53
3-59
3-60
4 Running the HTML Server
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.9.1
4.9.2
4.9.3
Starting the HTML Server..........................................................................................................
Stopping the HTML Server .......................................................................................................
Accessing the HTML Server......................................................................................................
Generating Serialized Objects for the HTML Server .............................................................
Configuring the HTML Server for Non-Western European Languages ............................
Enabling the Browser Side Debugging Feature on the Web Client.....................................
Customizing the Disclaimer for the Sign-In Page ..................................................................
Setting Up Quick Links for Pervasive Device Support .........................................................
Clearing File Attachments from the Browser Cache .............................................................
Securing Internet Explorer .................................................................................................
Securing Safari......................................................................................................................
Securing Mozilla Firefox.....................................................................................................
4-1
4-2
4-2
4-2
4-3
4-3
4-3
4-4
4-6
4-6
4-7
4-7
5 Understanding EnterpriseOne HTML Server Package Discovery
5.1
5.2
5.3
Overview of EnterpriseOne HTML Server Package Discovery........................................... 5-1
Impacts to End Users.................................................................................................................. 5-2
Understanding the Manifest...................................................................................................... 5-2
A Configuring Secure Socket Layer with the HTML Server
A.1
A.2
Configuring SSL on the IBM HTTP Server ............................................................................ A-1
Configuring SSL on IBM WebSphere...................................................................................... A-5
B Uninstalling a WebSphere 8.5.x/9.0 Fix Pack
B.1
iv
Uninstalling a WebSphere 8.5.x/9.0 Fix Pack........................................................................ B-1
B.2
Uninstalling a WebSphere 7.0 Fix Pack .................................................................................. B-1
C Enabling Compression on IBM HTTP Server
C.1
C.2
C.2.1
C.2.2
Understanding Compression ...................................................................................................
Configuring the mod_deflate directive ..................................................................................
Logging Compression Results ..........................................................................................
Example: Configuring mod_deflate for EnterpriseOne ................................................
C-1
C-1
C-2
C-2
D Understanding Media Objects on the Web Server
D.1
D.2
Required jas.ini Settings............................................................................................................ D-1
How Media Objects are Displayed by the HTML Server .................................................... D-1
E Generating JD Edwards EnterpriseOne Serialized Objects
E.1
E.1.1
E.1.2
E.1.3
E.2
E.2.1
E.2.2
E.2.3
E.3
E.3.1
E.3.1.1
E.3.2
E.3.3
E.4
E.5
E.6
E.7
E.7.1
E.7.2
E.8
E.8.1
E.8.2
E.8.2.1
E.8.2.2
E.8.2.3
E.8.3
E.8.4
E.8.4.1
E.8.4.2
E.8.4.3
E.8.5
E.8.6
E.8.7
Installing eGenerator .................................................................................................................
Prerequisites ........................................................................................................................
Setting the Default Storage Parameter (SQL Server Only) ...........................................
Preparing JD Edwards EnterpriseOne for Serialized Objects ......................................
Logging In ...................................................................................................................................
Running the eGenerator Diagnostic Tool........................................................................
Direct Generation to the Serialized Object Tables .........................................................
Generate using the JD Edwards EnterpriseOne HTML Server ...................................
Configuring eGenerator ............................................................................................................
Setting eGenerator Options ...............................................................................................
Generation Modes ......................................................................................................
Choosing Languages ..........................................................................................................
Configuring the genapp.ini File......................................................................................
Generating the Serialized Object Manifest...........................................................................
Generating All Standard Serialized Objects.........................................................................
Generating a List of Objects (Bulk Generation)...................................................................
Verifying the Generation Process ..........................................................................................
Checking Log Files ...........................................................................................................
Checking Database Acknowledgements.......................................................................
Generating Other Selected Objects........................................................................................
Generating Core Objects ..................................................................................................
Generating Applications..................................................................................................
Generate an Application...........................................................................................
Generate Applications by System Code.................................................................
Generate Applications by Mode..............................................................................
Generating Forms .............................................................................................................
Generating Reports...........................................................................................................
Generating a Report ..................................................................................................
Generating a Report Version ...................................................................................
Generating Reports by System Code ......................................................................
Generating NERs ..............................................................................................................
Generating Data Dictionary Items .................................................................................
Generating Tables .............................................................................................................
E-2
E-2
E-2
E-2
E-3
E-3
E-3
E-5
E-7
E-7
E-8
E-9
E-10
E-10
E-12
E-14
E-15
E-15
E-15
E-16
E-16
E-16
E-16
E-17
E-17
E-18
E-18
E-18
E-19
E-19
E-20
E-20
E-21
v
E.8.8
E.8.9
vi
Generating Business Views ............................................................................................. E-21
Generating Data Structures ............................................................................................. E-22
Preface
Welcome to the JD Edwards EnterpriseOne Tools HTML Server on WebSphere
Reference Guide for UNIX. This guide has been updated for JD Edwards
EnterpriseOne Tools release 9.2.1.
Audience
This guide is intended for system administrators and technical consultants who are
responsible for installing and configuring IBM WebSphere and 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
To navigate to this page from the My Oracle Support home page, click the Knowledge
tab, and then click the Tools and Training menu, JD Edwards EnterpriseOne, Welcome
Center, Release Information Overview.
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.
vii
Conventions
The following text conventions are used in this document:
viii
Convention
Meaning
Bold
Indicates field values.
Italics
Indicates emphasis and JD Edwards EnterpriseOne or other
book-length publication titles.
Monospace
Indicates a JD Edwards EnterpriseOne program, other code
example, or URL.
1
Accessing Certifications
1
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
Accessing Certifications
1-1
1-2 HTML Server on WebSphere Reference Guide
2
Installing, Updating, and Configuring
WebSphere 8.5.x/9.0 (Release 9.2.1)
2
IBM WebSphere Application Server 8.5.5 supports SDK 1.6
as the basic configuration but with SDK 1.7 as an optional
configuration. For JD Edwards EnterpriseOne, the implementation
requires SDK 1.7 as the default run-time configuration for WebSphere
Application Server 8.5.5. Therefore, after WebSphere Application
Server is installed with the basic configuration, you MUST change the
default SDK to 1.7.
Caution:
This chapter describes these tasks:
■
Section 2.1, "Before You Begin"
■
Section 2.2, "Installing the IBM Installation Manager"
■
Section 2.3, "Installing an IBM WebSphere Application Server 8.5.x/9.0"
■
Section 2.4, "Creating a New Profile for WebSphere Application Server 8.5.x/9.0"
■
Section 2.5, "Installing the IBM HTTP Server 8.5.x/9.0"
■
Section 2.6, "Installing Web Server Plug-ins for IBM WebSphere Application
Server"
■
Section 2.7, "Enabling SDK 7.0 on WebSphere Application Server 8.5.5"
■
Section 2.8, "Switching to SDK 7.0 on WebSphere Application Server 8.5.5"
■
Section 2.9, "Installing the WebSphere Customization Toolbox"
■
Section 2.10, "Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack"
■
Section 2.11, "Configuring the IBM Web Server Plug-in"
■
Section 2.12, "Setting the HTTP Server Properties"
■
Section 2.13, "Manually Generating a Plug-in"
■
Section 2.14, "Manually Editing the HTTP Configuration File"
2.1 Before You Begin
Before you begin the installation of WebSphere 8.5.x/9.0 on UNIX systems, you should
perform the steps in this section.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-1
Installing the IBM Installation Manager
■
■
In the WebSphere Application Server Version 8.5.x/9.0 Information Center, review
the section entitled: "Preparing the operating system for product installation".
Update your system according to the requirements.
For WebSphere Application Server Version 8.5.x see:
http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.i
bm.websphere.installation.nd.doc%2Fae%2Ftins_prepare.html
■
For WebSphere Application Server Version 9.0 see:
http://www.ibm.com/support/knowledgecenter/SSAW57_
9.0.0/com.ibm.websphere.installation.nd.doc/ae/tins_prepare.html
■
Download all the required software from IBM web site:
–
WebSphere Application Server Network Deployment
–
WebSphere Application Server Supplement
–
WebSphere Application Server SDK 1.7 for 8.5.x
–
WebSphere Application Server SDK 1.8 for 9.0
2.2 Installing the IBM Installation Manager
For all supported platforms, you must install the IBM Installation Manager before an
IBM WebSphere Application Server can be installed. Follow the steps below to install
the Installation Manager.
1.
From the IBM web site, download the IBM Installation Manager.
2.
Unzip the IBM Installation Manager software and locate the install executable,
which is named install.exe.
3.
On Install Packages, package selection, select the check box for the latest version of
the IBM Installation Manager.
4.
Click the Next button.
2-2 HTML Server on WebSphere Reference Guide
Installing the IBM Installation Manager
5.
On Install Packages, review the International Program License Agreement and
click the radio button to accept the terms if you want to continue with the
installation.
6.
Click the Next button.
7.
On Install Packages, Select a location for Installation Manager, enter an installation
directory.
For example:
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-3
Installing the IBM Installation Manager
/u01/WebSphere855/InstallationManager/eclipse
8.
On Install Packages, summary information, review the summary information and
click the Install button to begin the installation.
2-4 HTML Server on WebSphere Reference Guide
Installing an IBM WebSphere Application Server 8.5.x/9.0
9.
On Install Packages, if you are ready to install using the IBM Installation Manager,
click the Restart Installation Manager button.
10. After the Installation Manager is restarted, continue to the next section in this
chapter entitled: Section 2.3, "Installing an IBM WebSphere Application Server
8.5.x/9.0".
2.3 Installing an IBM WebSphere Application Server 8.5.x/9.0
IBM WebSphere Application Server (WAS) 8.5.x/9.0 is installed through the IBM
Installation Manager. Fix Pack 8.5.x/9.0 can be installed as a new installation or an
update.
To install an IBM WebSphere Application Server 8.5.x/9.0:
1.
Start the IBM Installation Manager, which you must have previously installed as
described in the preceding chapter of this guide entitled: Section 2.2, "Installing the
IBM Installation Manager".
To start the Installation Manager manually, execute IBMIM from <IM_
HOME>/eclipse folder. For example:
/u01/WebSphere855/InstallationManager/eclipse
The IBM Installation Manager screen displays.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-5
Installing an IBM WebSphere Application Server 8.5.x/9.0
2.
You must configure the software repository in the Installation Manager before you
can start the product installation. On the initial screen of the IBM Installation
Manager, navigate File > Preferences.
2-6 HTML Server on WebSphere Reference Guide
Installing an IBM WebSphere Application Server 8.5.x/9.0
3.
On Preferences, click on the Add Repository... button and enter the location of the
repository.config for each of the product. For example:
/u01/software/was855/nd/repository.config
/u01/software/was855/suppl/repository.config
/u01/software/was855/java17/repository.config
4.
Optionally, if needed for your installation, you should enable a proxy server and
enter proxy information.
5.
After all repositories are added, click the Install option from the Installation
Manager.
IBM Installation Manager displays a list of available products, as shown in the
following example:
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-7
Installing an IBM WebSphere Application Server 8.5.x/9.0
6.
The IBM Install Manager displays a list of available products (packages) to install.
7.
On Install Packages, select packages, select the products you want to install such
as:
8.
■
WebSphere Network Deployment
■
SDK 1.7 / SDK 1.8
Click the Next button.
2-8 HTML Server on WebSphere Reference Guide
Installing an IBM WebSphere Application Server 8.5.x/9.0
Note: Once the installation begins, the installer may prompt to
inform you that updates are available.
If Updates are available, the installer will display a list as shown in this example:
If the IBM Install Manager displays a list of updates, it is
recommended that you click the Select Recommended button to
accept and install the updates.
Note:
9.
On Install Packages, review the International Program License Agreement and
click the radio button to accept the terms if you want to continue with the
installation.
10. On Install Packages, select location for the shared resources directory, enter an
appropriate location for IMShared. These files will be used by all IBM products
installed through the Installation Manager (such as HTTP Server and
Customization Toolbox).
For example:
/u01/WebSphere855/IMShared
11. Click the Next button.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-9
Installing an IBM WebSphere Application Server 8.5.x/9.0
12. On Install Packages, package group, click the radio button entitled: Create a new
package group.
In the Installation Directory field, enter an appropriate location to install the IBM
WebSphere Application Server 8.5.x/9.0 software. It does not have to be the same
location as the shared location.
For example:
/u01/WebSphere855/AppServer
13. Click the Next button.
14. On Install Packages, translations, select your desired language.
15. Click the Next button.
2-10 HTML Server on WebSphere Reference Guide
Installing an IBM WebSphere Application Server 8.5.x/9.0
16. On Install Packages, select features, verify that the package for Java JDK 1.7/JDK
1.8 is selected.
Although JDK 1.6 is the default installation for Websphere
Application Server 8.5.x, you must choose to install JDK 1.7 in order to
be compatible with JD Edwards EnterpriseOne.
Caution:
17. Click the Next button.
18. Review the summary information and click the Install button.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-11
Creating a New Profile for WebSphere Application Server 8.5.x/9.0
19. On Install Packages, the packages are installed, click the Finish button.
20. To create a profile, ensure this radio button in the right pane is selected:
Profile Management Tool to create a profile.
Continue to the next section of this chapter entitled: Section 2.4, "Creating a New
Profile for WebSphere Application Server 8.5.x/9.0".
2.4 Creating a New Profile for WebSphere Application Server 8.5.x/9.0
The section describes how to create a new profile. This profile will be used later in the
installation process to create a web server and configure the plugin.
Note: This document describes how to create a "standalone" application server. For
information on how to create a cell and managed node, refer to IBM's Infocenter:
http://www-01.ibm.com/software/webservers/appserv/was/library/
You can choose to create your first profile now or after the remaining software
packages have been installed. If you create your profile now, you will need to
manually define the web server before configuring the plug-in later in this chapter. As
an alternative, you can use the advanced profile creation option to automatically create
a web server, but this must be done after all of the other software components
described in this guide are installed and updated to the correct level.
This procedure assumes you are creating a new profile at this time so that you can
verify your installation.
2-12 HTML Server on WebSphere Reference Guide
Creating a New Profile for WebSphere Application Server 8.5.x/9.0
If the Profile Management wizard did not launch, you might
have encountered a bug within the eclipse XWindow Client product.
You might see this error:
Note:
show 'BadWindow (invalid Window parameter)'
If you see the above error, follow the suggestions in IBM doc PM56382
at the below link, and re-launch the Profile Management Tools:
http://www-01.ibm.com/support/docview.wss?uid=swg1PM56382
1.
If you followed the last step in the preceding chapter entitled: Section 2.3,
"Installing an IBM WebSphere Application Server 8.5.x/9.0", the Profile
Management Tool was launched.
2.
On WebSphere Customization Toobox, Profile Management Tool, with the Profiles
tab selected, click the Create button.
3.
On Profile Management Tools, Environment Selection, highlight the Application
server environment type.
4.
Click the Next button.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-13
Creating a New Profile for WebSphere Application Server 8.5.x/9.0
5.
On Profile Creation Options, select the Typical profile creation radio button.
Choosing Typical profile creation uses the default
configuration settings. It assigns unique names to the profile, node,
and host. The tool also assigns unique port values.
Note:
Alternatively, you can choose Advanced profile creation to specify
your own values for settings such as the location of the profile and
names of the profile, node, and host.
6.
Click the Next button.
7.
On Administrative Security, clear the Enable administrative security checkbox.
8.
Click the Next button.
2-14 HTML Server on WebSphere Reference Guide
Creating a New Profile for WebSphere Application Server 8.5.x/9.0
9.
On Profile Creation Summary, review the information for accuracy and click the
Create button.
The progress screen is displayed. Wait for the progress to complete 100%, which
may take several minutes.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-15
Creating a New Profile for WebSphere Application Server 8.5.x/9.0
10. Optionally, on Profile Creation Complete, you can select the check box for Launch
the First steps console.
11. Click the Finish button.
2-16 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server 8.5.x/9.0
12. If you chose to run First Steps, on WebSphere Application Server, First steps, select
the first option, which is entitled: Installation verification.
13. Verify that the installation verification completed successfully. You should get the
message entitled: The installation verification is complete.
14. Close the screen for the First steps output.
15. Verify that you can sign on to the Administration Console. For example:
http://host:9060/ibm/console
2.5 Installing the IBM HTTP Server 8.5.x/9.0
The IBM HTTP Server 8.5.x/9.0 must be installed through the IBM Installation
Manager.
In order to install the IBM HTTP server, you must have the Supplemental images in
the repository, as shown in the second line item in the following screen sample.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-17
Installing the IBM HTTP Server 8.5.x/9.0
To install an IBM HTTP Server 8.5.x/9.0:
1.
Start the IBM Installation Manager, which you must have previously installed as
described in the preceding chapter of this guide entitled: Section 2.2, "Installing the
IBM Installation Manager".
2.
Click the Install option.
2-18 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server 8.5.x/9.0
3.
On Install Packages, select packages, click the checkboxes for the HTTP Server for
WebSphere Application Server and the HTTP Server Version (8.5.x/9.0).
4.
Click the Next button.
5.
Review the International Program License Agreement and click the radio button to
accept the terms if you want to continue with the installation.
6.
Click the Next button.
7.
On Install Packages, package group, click the radio button entitled: Create a new
package group. In the Installation Directory field, enter an appropriate location to
install the IBM HTTP Server 8.5.x/9.0 software. It does not have to be the same
location as the shared location.
For example:
/u01/WebSphere855/HTTPServer
This document refers to a local IBM HTTP server installed on the same machine as
the IBM WebSphere Application Server. For instructions on how to install a remote
HTTP server, refer to the IBM info center:
http://www-01.ibm.com/software/webservers/appserv/was/library/
Also note that the shared location that you defined when you installed the IBM
WebSphere Application Server in the previous section cannot be changed.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-19
Installing the IBM HTTP Server 8.5.x/9.0
8.
Click the Next button.
9.
On Install Packages, select the features to install, verify the package you chose is
selected.
10. Click the Next button.
11. On Install Packages, configuration, complete these fields:
■
HTTP Port
Specify a port for IBM HTTP Server to communicate. The default port is 80. If
the default port is already in use, then change to another port that is available.
Running IBM HTTP Server without root or Administrative privilege might
restrict use of ports below 1024.
12. Click the Next button.
2-20 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server 8.5.x/9.0
13. On Install Packages, review summary information, verify the accuracy of the
selections.
14. Click the Install button to begin the installation of the IBM HTTP Server.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-21
Installing Web Server Plug-ins for IBM WebSphere Application Server
15. On Install Packages, verify the installation completed successfully. You may want
to click the link: View Log File.
16. Click the Finish button.
You are returned to the IBM Installation Manager home screen.
17. To install the plug-ins, continue to the next section entitled: Section 2.6, "Installing
Web Server Plug-ins for IBM WebSphere Application Server".
2.6 Installing Web Server Plug-ins for IBM WebSphere Application Server
As with the previous software packages described in this guide, the plug-ins for IBM
WebSphere Application Server 8.5.x/9.0 must be installed using the IBM Installation
Manager.
In order to install the IBM HTTP server, you must have the Supplemental images in
the repository, as shown in the second line item in the following screen sample.
To install Web Server Plug-ins for IBM WebSphere Applications Server:
2-22 HTML Server on WebSphere Reference Guide
Installing Web Server Plug-ins for IBM WebSphere Application Server
1.
Start the IBM Installation Manager, which you must have previously installed as
described in the preceding chapter of this guide entitled: Section 2.2, "Installing the
IBM Installation Manager".
2.
On IBM Installation Manager, click the Install option.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-23
Installing Web Server Plug-ins for IBM WebSphere Application Server
3.
On Install Packages, select packages, click the checkboxes for the Web Server
Plug-ins for WebSphere Application Server and the HTTP Server Version
(8.5.x/9.0).
4.
Click the Next button.
5.
On Install Packages, review the International Program License Agreement and
click the radio button to accept the terms if you want to continue with the
installation.
6.
Click the Next button.
7.
On Install Packages, package group, click the radio button entitled: Create a new
package group.
In the Installation Directory field, enter an appropriate location to install the Web
Server Plugins for IBM WebSphere Application Server 8.5.x/9.0.
For example:
/u01/WebSphere85/Plugins
2-24 HTML Server on WebSphere Reference Guide
Installing Web Server Plug-ins for IBM WebSphere Application Server
8.
Verify the SDK level. At this point in the process in this guide, SDK 1.6 is still the
default installation for WebSphere Application Server 8.5.x and SDK 1.8 is the
default installation for Websphere Application Server 9.0.
9.
On Install Packages, review summary information, verify the accuracy of the
selections.
10. Click the Install button to begin the installation of the JDK.
The progress screen is displayed. Wait for the progress to complete 100%, which
may take several minutes.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-25
Enabling SDK 7.0 on WebSphere Application Server 8.5.5
11. On Install Packages, verify the installation completed successfully. You may want
to click the link: View Log File.
12. Click the Finish button.
You are returned to the IBM Installation Manager home screen.
13. To install the plug-ins, continue to the next section entitled: Section 2.9, "Installing
the WebSphere Customization Toolbox".
2.7 Enabling SDK 7.0 on WebSphere Application Server 8.5.5
Starting with WebSphere Application Server 8.5.x/9.0, SDK 7.0 is supported as an
optional feature. The Java version1.6 SDK is still the default installation.
JD Edwards EnterpriseOne supports WebSphere
Application Server 8.5.5 running with SDK 7.0 only. You must switch
the java level after the installation is completed.
Caution:
You can switch the java level by using the managesdk command. The executable for
the managesdk command is located in the bin directory of your application server. For
example:
/u01/WebSphere85/AppServer/bin
This section discusses how to use the managesdk command for these purposes:
■
View Available Java Products
2-26 HTML Server on WebSphere Reference Guide
Enabling SDK 7.0 on WebSphere Application Server 8.5.5
■
View Available Java Products with Detail Information
■
Syntax Examples using the managesdk Command
View Available Java Products
Use this command to view the available Java products:
managesdk.sh -listAvailable
The following shows a sample of returned information.
View Available Java Products with Detail Information
Use this command to view the available Java products with detail information:
managesdk.sh -listAvailable -verbose
The following shows sample returned information.
Syntax Examples using the managesdk Command
The following examples demonstrate correct syntax when you run the managesdk
command:
managesdk.sh -listAvailable [-verbose]
managesdk.sh -listEnabledProfile -profileName AppSrv01 [-verbose]
managesdk.sh -listEnabledProfileAll [-verbose]
managesdk.sh -enableProfile -profileName AppSrv01 -sdkname 1.7_64 -enableServers
managesdk.sh -enableProfileAll -sdkname 1.7_64 -enableServers
managesdk.sh -getNewProfileDefault [-verbose]
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-27
Switching to SDK 7.0 on WebSphere Application Server 8.5.5
managesdk.sh -setNewProfileDefault -sdkname 1.7_64
managesdk.sh -getCommandDefault [-verbose]
managesdk.sh -setCommandDefault -sdkname 1.7_64
2.8 Switching to SDK 7.0 on WebSphere Application Server 8.5.5
JD Edwards EnterpriseOne supports WebSphere
Application Server 8.5.5 running with SDK 7.0 only. You must switch
the java level after the installation is completed.
Caution:
This section discusses how to use the managesdk command for these purposes:
■
View List of Available SDK Names
■
Set the command default to the version 7.0 SDK
■
Set the New Profile Default to the Version 7.0 SDK
■
If Profiles Already Exist, Enable the Profiles to use the Version 7.0 SDK
View List of Available SDK Names
Use this command to view a list of available SDK names for the product installation:
managesdk.sh -listAvailable
The following shows sample returned information.
Set the command default to the version 7.0 SDK
Use this command to set the command default to the version 7.0 SDK:
managesdk.sh -setCommandDefault -sdkname 1.7_64
The following shows sample returned information.
Set the New Profile Default to the Version 7.0 SDK
Use this command to set the new profile default to version 7.0 SDK:
managesdk.sh -setNewProfileDefault -sdkname 1.7_64
The following shows sample returned information.
2-28 HTML Server on WebSphere Reference Guide
Installing the WebSphere Customization Toolbox
If Profiles Already Exist, Enable the Profiles to use the Version 7.0 SDK
If profiles already exist, use this command to enable the profiles to use the version 7.0
SDK:
managesdk.sh -enableProfileAll -sdkname 1.7_64 -enableServers
The following shows sample returned information.
Note: To change federated profiles in a Network Deployment
installation, the deployment manager must be running. The
managesdk command updates the master configuration repository.
After the command runs, a synchronization operation must occur
before the new SDK can be used for federated profiles.
2.9 Installing the WebSphere Customization Toolbox
New tool functionality with IBM WebSphere 8.5.x/9.0 includes the requirement to
install the WebSphere Customization Toolbox. This tool aids in configuring your
plug-in properly. The WebSphere Customization Toolbox comes from the
supplemental software repository that was downloaded, decompressed, and added to
the repository list as described in previous procedures in this document.
1.
Start the IBM Installation Manager.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-29
Installing the WebSphere Customization Toolbox
2.
On IBM Installation Manager, click the Install option.
3.
On Install Packages, select packages, select the two check boxes for WebSphere
Customization Toolbox and his package and version 8.5.x/9.0.
4.
Click the Next button.
5.
On Install Packages, review the International Program License Agreement and
click the radio button to accept the terms if you want to continue with the
installation.
6.
Click the Next button.
2-30 HTML Server on WebSphere Reference Guide
Installing the WebSphere Customization Toolbox
7.
On Install Packages, package group, click the radio button entitled: Create a new
package group.
In the Installation Directory field, enter an appropriate location to install the
WebSphere Customization Toolbox 8.5.x/9.0.
For example:
/u01/WebSphere855/Toolbox
8.
Click the Next button.
9.
On Install Packages, select features, select Web Server Plug-ins Configuration
Tool.
10. Click the Next button.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-31
Installing the WebSphere Customization Toolbox
11. On Install Packages, review summary information, verify the accuracy of the
selections.
12. Click the Install button to begin the installation of the WebSphere Customization
Toolbox.
2-32 HTML Server on WebSphere Reference Guide
Installing the WebSphere Customization Toolbox
The progress screen is displayed. Wait for the progress to complete 100%, which
may take several minutes.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-33
Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack
13. On Install Packages, verify the installation completed successfully. You may want
to click the link: View Log File.
14. Click the Finish button.
You are returned to the IBM Installation Manager home screen.
2.10 Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack
Use these procedures to install or update your existing WebSphere components to
WebSphere 8.5.x/9.0 Fix Pack:
■
Section 2.10.1, "Updating the IBM Installation Manager to WebSphere 8.5.x or
Greater"
■
Section 2.10.2, "Updating WebSphere Application Server 8.5.x or Greater"
■
Section 2.10.3, "Working with the HTTP Server Component"
■
Section 2.10.4, "Working with the Plug-ins Component"
■
Section 2.10.5, "Working with the Customization Toolbox Component"
2.10.1 Updating the IBM Installation Manager to WebSphere 8.5.x or Greater
Use this procedure to update the IBM Installation Manager.
2-34 HTML Server on WebSphere Reference Guide
Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack
Note: For instructions on installing the Update Installer itself, refer
to the section of this guide entitled: Section 3.4, "Installing the
WebSphere Update Installer".
1.
Start the IBM Installation Manager using the IBMIM executable..
2.
Open the Preferences of the IBM Installation Manager.
3.
Highlight the Updates node and select this checkbox:
Search for Installation Manager Updates
4.
Log out of IBM Installation Manager.
5.
Log in to the Installation Manager and you will be prompted if a new version of
Installation Manager is available.
6.
On IBM Installation Manager, click the Yes button and follow the installation
wizard to complete the upgrade.
2.10.2 Updating WebSphere Application Server 8.5.x or Greater
Use this procedure to update WebSphere 8.5.x or greater.
1.
Stop all the WebSphere Processes including the HTTP Server and Web Server.
2.
Launch the IBM Installation Manager using the IBMIM executable.
3.
Select the Update option.
4.
On Package Group Name, select the IBM WebSphere Application Server product
to which you wish to upgrade. For example:
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-35
Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack
IBM WebSphere Application Server V8.5.x
5.
On Password Required, enter valid credentials for your IBM ID to connect to the
IBM download site by completing these fields:
■
User name
■
Password
Note: You can uncheck the Show Recommended only option to list
all available fix packs.
6.
Review the license agreement and accept the terms in order to continue.
7.
You can accept the recommended fix packs that are automatically checked.
Note: The recommended fix packs may vary depends on the
platform.
2-36 HTML Server on WebSphere Reference Guide
Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack
8.
On Features, use the checkboxes to select the components you want to install.
9.
On Features to Install, review the summary of components that you have selected
and click the Update button.
The update process downloads the fix pack from the IBM web site. The download
speed depends on the network connections.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-37
Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack
10. Click the Finish button when the update is completed as indicated by this
message:
The packages are updated.
2.10.3 Working with the HTTP Server Component
Use this procedure to install or update the IBM HTTP Server Component for
WebSphere 8.5.x or greater.
1.
Launch the IBM Installation Manager using the IBMIM executable.
2.
Select the Update option.
3.
On Update, select this component for the version you want to install or update:
IBM HTTP Server
4.
On Features to Install, review the summary of selected features and click Update.
5.
Click the Finish button when the update is completed as indicated by this
message:
The packages are updated.
2.10.4 Working with the Plug-ins Component
Use this procedure to install or update the Plug-ins Component for WebSphere 8.5.x or
greater.
1.
Launch the IBM Installation Manager using the IBMIM executable.
2.
Select the Update option.
2-38 HTML Server on WebSphere Reference Guide
Installing or Updating to WebSphere 8.5.x/9.0 Fix Pack
3.
On Update, select this component for the version you want to install or update:
Web Server Plug-ins for IBM WebSphere Application Server
4.
On Features, review the summary of selected features and click Update.
5.
Click the Finish button when the update is completed as indicated by this
message:
The packages are updated.
2.10.5 Working with the Customization Toolbox Component
Use this procedure to install or update the Customization Toolbox Component to
WebSphere 8.5 or greater.
1.
Launch the IBM Installation Manager using the IBMIM executable.
2.
Select the Update option.
3.
On Update, select this component for the version you want to install or update:
WebSphere Customization Toolbox
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-39
Configuring the IBM Web Server Plug-in
4.
On Features, verify the component you want to installed is selected..
5.
On Update, review the summary of selected features and click Update.
6.
Click the Finish button when the update is completed as indicated by this
message:
The packages are updated.
7.
Restart all HTTP Services.
8.
Restart all Web Server instances.
2.11 Configuring the IBM Web Server Plug-in
After you have updated all software packages as described in the preceding section of
this document entitled: Section 2.10, "Installing or Updating to WebSphere 8.5.x/9.0
Fix Pack", you must configure the plug-in. This process is performed through the IBM
WebSphere Customization Toolbox. You must complete this configuration before you
install the JD Edwards EnterpriseOne HTML Web Server.
1.
Start the WebSphere Customization Toolbox by starting the executable in this
directory:
/u01/WebSphere855/Toolbox/WCT/wct.sh
Note:
If the Customization Toolbox failed to start with this error:
See the log file in
/root/.ibm/.WebSphere/workspace/WCT85/.metadata/.log
For details on the above error, review the IBM solution at this link:
http://www-01.ibm.com/support/docview.wss?uid=swg21673199
2-40 HTML Server on WebSphere Reference Guide
Configuring the IBM Web Server Plug-in
2.
On WebSphere Customization Toolbox, Welcome, in the list of provided tools,
highlight the Web Server Plug-ins Configuration Tool.
3.
Click the Launch Selected Tool button.
4.
In the Web Server Plug-in Runtime Location section, click the Add button.
5.
On Add Web Server Plug-in Location, complete these fields:
■
Name
Enter a name for the plug-in location. For example:
IHS_webserver1
■
Location
Enter the location of your plug-in. The default plug-in directory is:
/u01/WebSphere855/Plugins
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-41
Configuring the IBM Web Server Plug-in
6.
Click the Finish button.
7.
In the upper half of the form (shown above), verify the plug-in location that you
just defined is displayed in the Web Server Plug-in Runtime Locations section in
the upper half of the form.
8.
In the lower half of the screen (shown above), click the Create button.
9.
On Web Server Selection, choose this radio button:
IBM HTTP Server V8.5/9.0.
10. On Web Server Architecture Selection, choose your bitness.
11. On Web Server Configuration File Selection, complete these fields:
■
Select the existing IBM HTTP Server httpd.conf file
Enter in the location of your httpd.conf file. For example:
/u01/WebSphere855/HTTPServer/conf/httpd.conf
2-42 HTML Server on WebSphere Reference Guide
Configuring the IBM Web Server Plug-in
■
Specify the Web server port
Specify a web server port that matches the port used by your HTTP server.
12. Click the Next button.
You will receive the Non-Administrative user configuration limitation screen if
you are not logged on as an administrative user.
13. Click the Next button.
14. If you are signed on as an Administrative User, you will see the above screen. You
can choose to create a user ID for IBM HTTP Server.
15. Click the Next button.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-43
Configuring the IBM Web Server Plug-in
16. You can choose whether to use a Windows service to run IBM HTTP Server
administration server. It is recommended that you select to run the Server as a
Windows Service. Optionally you can change the startup type to Manual if you
are not going to use the HTTP Administration server often.
17. On Web Server Definition name, specify a web server name. If you already have a
web server defined (for example, webserver1), then you should use the same
name here.
For the purposes of this guide, it is assumed that the HTTP Server and WebSphere
Application Server are located on the same machine. Therefore, on Configuration
Scenario Selection, the radio button for (Local) Installation location of
WebSphere Application Server is selected.
2-44 HTML Server on WebSphere Reference Guide
Configuring the IBM Web Server Plug-in
18. Use the Browse button to locate the installation location of the WebSphere
Application Server. For example:
/u01/WebSphere855/AppServer
19. Click the Next button.
20. On WebSphere Application Server Profile Selection, use the drop-down menu in
Available Profiles to select the WebSphere Application Server profile to configure
with the current Web server plug-in and create the Web server definition. For
example, an available profile might be named AppSvr01.
Note: If the Available Profiles field is blank and no options show on the drop
down, you must Cancel from this procedure. Create a profile and either use the
advanced option to automatically create a web server definition or manually
create the web server in the IBM WebSphere Application Server Administrative
Console. For more information on either option, refer to the IBM info center:
http://www-01.ibm.com/software/webservers/appserv/was/library/
21. Click the Next button.
22. On Plug-in Configuration Summary, review the information for accuracy.
23. Click the Configure > button.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-45
Setting the HTTP Server Properties
24. On Plug-in Configuration Result, verify that the configuration completed
successfully. If necessary, follow the instructions to correct any errors.
25. Click the Finish button.
26. On WebSphere Customization Toolbox, with the Web Server Plug-in
Configurations tab selected, verify that the server definition exists.
2.12 Setting the HTTP Server Properties
To use IBM WebSphere Application Server 8.5.x/9.0 properly with Oracle JD Edwards
EnterpriseOne, you must set the HTTP server to automatically generate and propagate
the plug-in. These steps briefly describe this process.
1.
Log into the admin console for IBM WebSphere Application Server
2.
Select Servers > Server Types > Web Servers.
3.
Select your web server.
2-46 HTML Server on WebSphere Reference Guide
Manually Generating a Plug-in
4.
On the right hand side of the screen, select Additional Properties > Plug-in
properties.
5.
Make any necessary changes and ensure the checkboxes are selected next to these
two properties:
■
Automatically generate the plug-in configuration file
■
Automatically propagate plug-in configuration file
6.
Click Apply.
7.
Click the Save button to save all changes.
2.13 Manually Generating a Plug-in
Occasionally, you may to manually generate the web server plug-in. The most
common error that requires manual plug-in generation is the "HTTP 404" when trying
to access the software. This section briefly explains how to manually generate the
plug-in.
1.
Log in to the WebSphere Application Server Administration Console for your
profile.
2.
Select Server Types > Web Servers.
3.
Check the box next to the web server definition.
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-47
Manually Generating a Plug-in
4.
Click the Generate Plug-in button.
5.
Click the Propagate Plug-in button.
6.
Log off of the Admin Console.
Note: Federated (Clustered) Web Servers. If you are using
WebSphere Application Server and running JD Edwards
EnterpriseOne as part of a federated (or clustered) web server, you
may need to regenerate the WebSphere global plugin configuration
after deploying the newest tools release. This is required when new
servlets have been added to the tools release you are deploying.
To update (regenerate) plugins, refer to the following procedure.
To update (regenerate) and propagate the global web server plugin configuration:
1.
Log on to the Deployment Manager Administration Console using the Dmgr01
profile.
2.
Expand the Environment node and select Update global Web server plug-in
configuration.
3.
Review the content in the right-hand pane and note the location of the plug-in file
in the description. For example, the description might say:
The global plugin-cfg.xml file is placed in the %was_profile_
home%/config/cells directory.
4.
Click the OK button.
2-48 HTML Server on WebSphere Reference Guide
Manually Editing the HTTP Configuration File
2.14 Manually Editing the HTTP Configuration File
You must perform this step in order for JD Edwards
EnterpriseOne HTML Server to work correctly.
Caution:
To manually edit the HTTP configuration file (httpd.conf):
1.
Locate your httpd.conf file. Typically the file is located in this directory:
/u01/WebSphere855/HTTPServer/config
2.
Open the file with an ASCII editor.
3.
Assuming the location of your httpd.conf is that shown in the previous step, add
the following lines to the bottom of the file:
LoadModule was_ap22_module "/u01/WebSphere855/Plugins/bin/64bits/mod_
was_ap22_http.so"
The extension of the mod_was_ap22_http file varies based on
platform.
Note:
WebSpherePluginConfig
"/u01/WebSphere855/Plugins/config/webserver1/plugin-cfg.xml"
4.
Save and close the httpd.conf file.
5.
Stop the HTTP Server from the bin directory using this command:
./apachectl stop
6.
Restart the HTTP Server from the bin directory using this command:
./apachectl start
Installing, Updating, and Configuring WebSphere 8.5.x/9.0 (Release 9.2.1) 2-49
Manually Editing the HTTP Configuration File
2-50 HTML Server on WebSphere Reference Guide
3
Installing and Configuring WebSphere 7.0
3
This chapter describes how to install and configure WebSphere 7.0. It contains the
following topics:
■
■
■
Section 3.1, "Installing WebSphere Application Server 7.0 (Using Network
Deployment CD or Downloaded Image)"
Section 3.2, "Installing the IBM HTTP Server 7.0"
Section 3.3, "Installing IBM HTTP Server Plug-ins for WebSphere Application
Server"
■
Section 3.4, "Installing the WebSphere Update Installer"
■
Section 3.5, "Installing WebSphere 7.0 Fix Pack 29"
■
Section 3.6, "Installing the IBM HTTP Server Fix Pack"
■
Section 3.7, "Installing the WebSphere 7.0 Plug-ins Fix Pack"
■
Section 3.8, "Verifying the Versions of Installed WebSphere Products"
■
Section 3.9, "Starting the WebSphere Application Server"
■
Section 3.10, "Stopping the WebSphere Application Server"
■
Section 3.11, "Determining the Name and Status of the WebSphere Application
Server"
■
Section 3.12, "Starting the IBM HTTP Server"
■
Section 3.13, "Stopping the IBM HTTP Server"
■
Section 3.14, "Accessing the WebSphere Administration Console"
■
Section 3.15, "Testing the WebSphere and IBM HTTP Server Installation"
■
Section 3.16, "Generating and Propagating WebSphere Plug-ins (optional)"
■
Section 3.17, "Creating a New Application Server Profile (optional)"
■
Section 3.18, "Deleting a Profile (optional)"
■
Section 3.19, "Adding a New Web Server for a New Profile (optional)"
3.1 Installing WebSphere Application Server 7.0 (Using Network
Deployment CD or Downloaded Image)
It is important to follow the exact sequence of steps in this
procedure.
Note:
Installing and Configuring WebSphere 7.0
3-1
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
Complete these steps to install the WebSphere Application Server version 7.0, and then
install the EnterpriseOne Web Server to that installation. The WebSphere 7.0 Network
Deployment CD may be used to install WebSphere Application Server for a base or
standalone configuration.
Note: The typical IBM WebSphere installation includes the
Application Server itself, HTTP Server, and the Plug-in components.
You must install all these components to ensure WebSphere
Application Server 7.0 is functioning correctly. For any additional
requirements and Fix Packs once the basic install is completed, review
the minimum technical requirements (MTRs) as described in
Chapter 1, "Accessing Certifications" in this document.
1.
If you have not already set the display, complete this step. For example, if your
local display has an IP address of 10.139.157.46:0.0, enter this command to
properly set the display:
export DISPLAY=10.139.157.46:0.0
Note: For Solaris only, verify that you are in the ksh shell before
executing the command using the echo $SHELL command.
2.
If you are installing WebSphere 7.0 on Solaris with Exceed, enter this command to
set the environment variable:
export NO_J2D_DGA=1
3.
Insert the WebSphere Application Server Network Deployment CD, Version 7.0 or
extract the downloaded image into a temporary location.
4.
Enter this command to mount the CD drive:
mount /cdrom
Note: The syntax of the mount command can vary by platform, and
is not required for Sun platforms.
5.
Enter this command to change to the CD drive:
cd /cdrom
6.
Run the launchpad executable from the extracted directory:
./launchpad.sh
3-2 HTML Server on WebSphere Reference Guide
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
7.
From that launchpad window, select the first link on the right panel:
Launch the installation wizard for WebSphere Application Server Network Deployment
Installing and Configuring WebSphere 7.0
3-3
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
8.
On the Welcome panel, click the Next button to continue.
3-4 HTML Server on WebSphere Reference Guide
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
9.
On Software License Agreement, review the License Agreement and select a radio
button to accept or decline.
If you chose to accept, click the Next button to continue.
If you do not accept the terms of the license agreement, you cannot continue with
the installation.
10. On System Prerequisites Check, the installer performs a quick system
requirements check on the server. Once the check is complete and successful, click
the Next button to continue.
Installing and Configuring WebSphere 7.0
3-5
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
11. On the Optional Features Installation screen, click the Next button to continue.
Tip: For production environments, it is recommended that you not
enable the Install the Sample application check box.
You should enable the check box for non-English support for the
WebSphere Administrative Console if applicable to your installation.
3-6 HTML Server on WebSphere Reference Guide
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
12. On Installation Directory, enter or browse to a valid location where you want to
install WebSphere Application Server Network Deployment (the default is
opt/IBM/WebSphere/AppServer). For example:
/u01/IBM/WebSphere/AppServer
13. Click the Next button to continue.
14. On WebSphere Application Server Environments, select Application Server to create
a standalone application server profile and then click the Next button to continue.
Note: The Application Server environment will create a default
stand-alone application server called AppSrv01 during the
installation. To use federated nodes configuration, select Cell
environment to create a deployment manger (such as Dmgr01) and a
managed node (for example, AppSrv01) during the installation.
Installing and Configuring WebSphere 7.0
3-7
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
15. On Enable Administrative Security, the check box for the application server profile
is checked by default. You can choose either to:
■
■
Clear the check box for Enable administrative security to disable server
administrative security, or
If the check box is enabled for Enable administrative security, server
administration security will be enabled and you must enter the User ID and
Password
When you enable the check box the fields on this screen are enabled and you
must enter valid credentials for the WebSphere administrator for this
installation.
Tip: JD Edwards EnterpriseOne Business Services Server. If you are
using these instructions to install a JD Edwards EnterpriseOne
Business Services Server into this WebSphere instance, you must
enable administrative security.
16. Click the Next button to continue.
3-8 HTML Server on WebSphere Reference Guide
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
17. On Installation Summary, review the information and click the Next button to
begin the installation of WebSphere Application Server Network Deployment.
You should enable the check box for Verify my permissions to
perform the installation in order for the installer to validate the
permissions required for installation of the product.
Note:
Installing and Configuring WebSphere 7.0
3-9
Installing WebSphere Application Server 7.0 (Using Network Deployment CD or Downloaded Image)
Note: On Installation Results, you can click on the
AboutThisProfile.txt link to see the port assignment for this profile.
Note the Administrative console port on which AppSrv01 will be
running (for example, 9060). You can use Profile Management Tool to
create as many profiles as you like. Each profile is a separate instance
of the WebSphere running on a different set of ports.
18. On Installation Results, click the Finish button.
The First steps menu is launched.
19. On the First steps menu, click Installation verification to verify the installation.
After you click Installation verification, you can verify the success of the installation
by reviewing the contents of the resulting display. For example:
3-10 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server 7.0
20. Ensure that the Installation Verification utility completes with a success message.
21. Close the First steps output and click Exit on the First steps screen.
This completes the profile creation activity.
3.2 Installing the IBM HTTP Server 7.0
Note: Although the IBM HTTP Server is integrated into the
WebSphere Application Server, the installation is a separate process.
To install the IBM HTTP Server:
1.
Insert the WebSphere Application Server Supplement CD, Version 7.0 or extract
the downloaded image (if you haven't done so already).
2.
Run the install executable that is located in the IHS directory from the extracted
location by typically using these commands:
mount /cdrom
cd /cdrom
./IHS/install.sh
Note: The syntax of the mount command can vary by platform, and
is not required for Sun platforms.
Installing and Configuring WebSphere 7.0
3-11
Installing the IBM HTTP Server 7.0
3.
On Welcome, click the Next button to continue.
4.
On Software License Agreement, review the License Agreement and choose an
option to accept or decline.
5.
Click the Next button to continue.
3-12 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server 7.0
6.
On System Prerequisites Check, the installer performs a quick system
requirements check on the server. Once the check is complete and successful, click
the Next button to continue.
7.
For the install location, enter a valid value for your IBM HTTP Server installation
directoryopt/IBM/HTTPServer). Use a value such as:
/u01/IBM/HTTPServer
Installing and Configuring WebSphere 7.0
3-13
Installing the IBM HTTP Server 7.0
8.
Click the Next button to continue.
9.
On Port Values Assignment, use the default port or enter different ports.
10. Click the Next button to continue.
11. Click the Next button to continue.
12. On HTTP Administration Server Authentication, the check box enabling HTTP
server administration security is checked by default. You can choose either to:
3-14 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server 7.0
■
■
Clear the check box for Create a user ID for IBM HTTP administration server
authentication to disable HTTP server administration security, or
If the check box is enabled for Create a user ID for IBM HTTP administration
server authentication, HTTP server administration security will be enabled and
you must enter the User ID and Password
13. Click the Next button to continue.
14. On Setup HTTP Administration Server, clear the Setup IBM HTTP administration
server to administer IBM HTTP Server or enter an User ID and Group to Setup
IBM HTTP administration server.
15. Click the Next button to continue.
Installing and Configuring WebSphere 7.0
3-15
Installing the IBM HTTP Server 7.0
16. On IBM HTTP Administration Server Plug-in For IBM WebSphere Application
Server, clear the check box for Install the IBM HTTP Server Plug-in for IBM
WebSphere Application Server to disable the silent install of the plug-in at this time.
The installation of IBM HTTP Server Plug-in for IBM WebSphere Application
Server will be described in the section Installing IBM HTTP Server Plug-ins for
WebSphere Application Server.
17. Click the Next button to continue.
3-16 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server 7.0
18. On the summary screen, click the Next button to begin the installation.
19. On the successfully installed screen, click Finish.
Installing and Configuring WebSphere 7.0
3-17
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
3.3 Installing IBM HTTP Server Plug-ins for WebSphere Application
Server
With the IBM HTTP Server successfully installed, the final portion of the WebSphere
Application Server installation is to install WebSphere Plug-ins.
Prior to installing WebSphere Plug-ins, it is recommended to ensure the IBM HTTP
Server services (Apache) are not already running.
To install WebSphere Plug-ins:
1.
Insert the WebSphere Application Server Supplement CD, Version 7.0 or extract
the downloaded image (if you haven't done so already).
2.
Run the install executable in the plugin directory. For example:
mount /cdrom
cd /cdrom
./plugin/install.sh
Note: The syntax of the mount command can vary by platform, and
is not required for Sun platforms.
3.
On the Welcome screen, you can deselect all "learning" options and click the Next
button to begin the wizard.
3-18 HTML Server on WebSphere Reference Guide
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
4.
On Software License Agreement, review the License Agreement and choose an
option to accept or decline.
5.
Click the Next button to continue (not available if license agreement is not
accepted).
6.
On System Prerequisites Check, the installer performs a verification of system
requirements.
Installing and Configuring WebSphere 7.0
3-19
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
After the installer indicates the check was successful, click the Next button to
continue.
7.
On Select the Web server to configure, select the following radio button:
IBM HTTP Server V7
3-20 HTML Server on WebSphere Reference Guide
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
Note: All plug-in binaries are installed, but only the selected Web
server will be configured.
8.
Click the Next button to continue.
9.
On Select installation scenario, if your WAS server is located on the same machine
on which you are installing, select this radio button:
WebSphere Application Server machine (local)
If your WAS server is located on a different machine than the one on which you
are running the installer, select this radio button:
Web server machine (remote)
10. Click the Next button to continue.
Installing and Configuring WebSphere 7.0
3-21
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
11. On Web server plug-ins installation location, enter a directory. The default
directory is:
/opt/IBM/HTTPServer/Plugins
For example:
/u01/IBM/HTTPServer/Plugins
12. Click the Next button to continue.
3-22 HTML Server on WebSphere Reference Guide
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
13. On Installation location of WebSphere Application Server V7.0, enter a directory.
For example:
/u01/IBM/WebSphere/AppServer
14. Click the Next button to continue.
Installing and Configuring WebSphere 7.0
3-23
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
15. On Select the existing IBM HTTP Server httpd.conf file, enter a directory path. For
example:
/u01/IBM/HTTPServer/conf/httpd.conf
You must also specify the Web Server port. Typically you can accept the default
value of 80 for the IBM HTTP server.
Note: The plug-ins installer directly modifies the IBM HTTP Server
configuration file with the information you specify on this screen.
16. Click the Next button to continue.
17. On Specify a unique Web Server definition name, enter the name of your IBM
HTTP to allow the WebSphere Administration Console to administer the IBM
HTTP configuration and status.
Typically you can accept the default value of webserver1.
18. Click the Next button to continue.
3-24 HTML Server on WebSphere Reference Guide
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
19. On Web Server plugin-cfg.xml file, you can accept the default location for the
plugin-cfg.xml file.
20. Click the Next button to continue.
21. The installation wizard detects the default profile (such as AppSrv01) that does
not have a Web server defined. Click the Next button to continue.
Installing and Configuring WebSphere 7.0
3-25
Installing IBM HTTP Server Plug-ins for WebSphere Application Server
22. On the Summary screen, click the Next button to begin the installation.
23. The installation wizard shows that a Web server definition is created for the
default Application server profile (such as AppSrv01).
24. Click the Next button to proceed.
3-26 HTML Server on WebSphere Reference Guide
Installing the WebSphere Update Installer
The installation wizard launches a web browser with more detailed information
about the Plug-ins road map. You can close the browser at any time or return to
the installation wizard.
25. On the completion screen, click Finish to exit the WebSphere Plug-ins installation
wizard.
3.4 Installing the WebSphere Update Installer
The Update Installer for WebSphere Software includes a new installation program for
IBM WebSphere Version 7.0, Installation Wizard starting with Fix Pack 7. The Update
Installer is backwards compatible. You should download the Update Installer that
match with your WebSphere product. You can use a single installation of the Update
Installer to install maintenance packs on all the WebSphere software products such as
WebSphere Application Server, Java SDK, IBM HTTP Server, and Web server plug-ins.
Before you can install Refresh or Fix pack for WebSphere software, you need to install
the Update Installer engine as described in this procedure.
Note: Make sure all WebSphere processes including IBM HTTP
Server V7 are not running before starting Update Installer installation.
This document uses Fix Pack 29 (7.0.0.29) to describe the process of installing
WebSphere Fix Pack. Check the Certification for the latest supported WebSphere Fix
Pack for the JD Edwards EnterpriseOne HTML Web Server (refer to Chapter 1,
"Accessing Certifications").
To install the WebSphere update installer:
1.
Enter these commands:
mount /cdrom
Installing and Configuring WebSphere 7.0
3-27
Installing the WebSphere Update Installer
cd /cdrom
2.
From the downloaded image run the install executable using this command:
./UpdateInstaller/install
3.
On the Welcome screen, click the Next button to begin the wizard.
4.
On Software License Agreement, review the License Agreement and choose an
option to accept or decline.
3-28 HTML Server on WebSphere Reference Guide
Installing the WebSphere Update Installer
5.
Click the Next button to continue.
6.
On System Prerequisites Check, the Installer performs a verification of system
requirements.
7.
After the Installer indicates the check was successful, click the Next button to
continue.
8.
On Directory Name, enter a valid value for the Update Installer installation
directory. For example:
Installing and Configuring WebSphere 7.0
3-29
Installing the WebSphere Update Installer
/u01/IBM/WebSphere/UpdateInstaller
Note: To facilitate maintenance, it is recommended that you install
the Update Installer under the WebSphere root directory. For example:
/u01/IBM/WebSphere/UpdateInstaller
9.
Click the Next button to continue.
10. On Installation Summary, click the Next button to begin the installation.
3-30 HTML Server on WebSphere Reference Guide
Installing WebSphere 7.0 Fix Pack 29
11. On Installation Complete, deselect the check box for Launch IBM Update Installer for
WebSphere software on exit.
12. Click the Finish button.
3.5 Installing WebSphere 7.0 Fix Pack 29
Note: This document uses Fix Pack 29 (7.0.0.29) to describe the
process of installing WebSphere Fix Pack. Check the Certification for
the latest supported WebSphere Fix Pack for the JD Edwards
EnterpriseOne HTML Web Server (refer to Chapter 1, "Accessing
Certifications").
To install the WebSphere 7.0 Fix Pack:
1.
Ensure that all WebSphere and HTTP Services are stopped prior to updating the
software.
2.
Download all the fix pack files to the "maintenance" directory under the
installation directory of the Update Installer, such as:
/u01/IBM/WebSphere/UpdateInstaller/maintenance
For example:
7.0.0-WS-WAS-WinX32-FP0000005.pak
For example, on Solaris the files are named:
7.0.0-WS-WAS-SolarisSparc-FP0000005.pak
7.0.0-WS-WASSDK-SolarisSparc-FP0000005.pak
7.0.0-WS-IHS-SolarisSparc-FP0000005.pak
7.0.0-WS-PLG-SolarisSparc-FP0000005.pak
Note: The example filename for the .pak file is specific to Solaris.
Other versions of UNIX will have their own unique filenames. You do
not need to untar these files, just put them in the
\UpdateInstaller\maintenance directory.
3.
Run the update executable from the UpdateInstaller directory using these
commands:
cd /u01/IBM/WebSphere/UpdateInstaller
./update.sh
Installing and Configuring WebSphere 7.0
3-31
Installing WebSphere 7.0 Fix Pack 29
4.
Click the Next button to continue.
5.
On the Product selection screen, use the drop down to select the installation
location of the WebSphere Application Server. For example:
/u01/IBM/WebSphere/AppServer
6.
Click the Next button to continue.
3-32 HTML Server on WebSphere Reference Guide
Installing WebSphere 7.0 Fix Pack 29
7.
On Maintenance Operation Selection, select the following radio button:
Install maintenance package
8.
Click the Next button to continue.
The installer inspects the UpdateInstaller directory for maintenance packages
(.pak files); specifically in the maintenance sub-directory.
9.
On Maintenance Package Selection, validate the directory name that was located
by the Installer wizard.
Installing and Configuring WebSphere 7.0
3-33
Installing WebSphere 7.0 Fix Pack 29
10. On Available Maintenance Package to Install, check the WAS and WASSDK fix
pack files since the WebSphere Application Server components are being updated.
11. Click the Next button to continue.
12. On Installation Summary, review the information and click the Next button to
begin the installation.
3-34 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server Fix Pack
Note: You should check the Verify my permissions to perform the
installation check box in order for the installer to validate the
permissions required for installation of the product.
13. Click the Next button to continue.
14. On Installation Complete, Success, click the Relaunch button to relaunch the
wizard and install the HTTP server components.
3.6 Installing the IBM HTTP Server Fix Pack
To install the IBM HTTP Server Fix Pack:
1.
Ensure that all WebSphere and HTTP Services are stopped prior to updating the
software.
2.
Download and copy the fix pack file for the IBM HTTP Server to the
\UpdateInstaller\maintenance directory.
For example, on Solaris the file is named:
7.0.0-WS-IHS-SolarisSparc-FP0000005.pak
3.
Once the wizard has restarted, select the HTTP server components.
Installing and Configuring WebSphere 7.0
3-35
Installing the IBM HTTP Server Fix Pack
4.
On the Welcome screen, click the Next button to begin the Update Installer wizard.
5.
On Product Selection, use the drop down to select the installation location of the
IBM HTTP Server. For example:
/u01/IBM/HTTPServer
6.
Click the Next button to continue.
3-36 HTML Server on WebSphere Reference Guide
Installing the IBM HTTP Server Fix Pack
7.
On Maintenance Operation Selection, select this radio button:
Install maintenance package
8.
Click the Next button to continue.
9.
On Maintenance Package Directory Selection, validate the directory path that was
located by the Installer wizard.
10. Click the Next button to continue.
Installing and Configuring WebSphere 7.0
3-37
Installing the IBM HTTP Server Fix Pack
11. On Available Maintenance Package to Install, ensure that the available IHS and
WASSDK fix pack files are checked since the IBM HTTP Server components are
being updated.
12. Click the Next button to continue.
13. On Installation Summary, click the Next button to begin the installation.
3-38 HTML Server on WebSphere Reference Guide
Installing the WebSphere 7.0 Plug-ins Fix Pack
Note: You should check the Verify my permissions to perform the
installation check box in order for the installer to validate the
permissions required for installation of the product.
14. On Installation Complete, verify that the proper maintenance packages for the
IBM HTTP Server were successfully installed.
15. Click the Relaunch button and continue to the next section to install WebSphere
Plug-ins Fix Pack.
3.7 Installing the WebSphere 7.0 Plug-ins Fix Pack
Note: It is very important to following the exact sequence of steps in
this procedure.
To install the WebSphere 7.0 Plug-ins Fix Pack:
1.
Ensure that all WebSphere and IBM HTTP Services are stopped prior to updating
the software.
2.
Download and copy the fix pack file for the WebSphere Plug-ins to the
\UpdateInstaller\maintenance directory.
For example, on Solaris:
7.0.0-WS-PLG-SolarisSparc-FP0000005.pak
Note: The example filename is specific to Solaris. Other versions of
UNIX with have their own unique filenames.
Installing and Configuring WebSphere 7.0
3-39
Installing the WebSphere 7.0 Plug-ins Fix Pack
3.
Run the update executable from the copied UpdateInstaller directory using these
commands:
cd /u01/IBM/WebSphere/UpdateInstaller
./update.sh
4.
Once is wizard is restarted, select the Plugins component.
5.
On Product Selection, use the drop down to select the installation location of the
Web server plugin. For example:
/u01/IBM/HTTPServer/Plugins
6.
Click the Next button to continue.
3-40 HTML Server on WebSphere Reference Guide
Installing the WebSphere 7.0 Plug-ins Fix Pack
7.
On Maintenance Operation Selection, select the following radio button:
Install maintenance package
8.
Click the Next button to continue.
9.
On Maintenance Package Directory Selection, validate the directory path that was
located by the Installer wizard.
The installer inspects the \UpdateInstaller\maintenance
directory for maintenance packages (.pak files).
Note:
10. Click the Next button to continue.
Installing and Configuring WebSphere 7.0
3-41
Installing the WebSphere 7.0 Plug-ins Fix Pack
11. On Available Maintenance Package to Install, ensure that the PLG and WASSDK
fix pack files are checked since the WebSphere Plugin components are being
updated.
12. Click the Next button to continue the update for the WebSphere Plug-ins.
13. On the Installation Summary screen, review the information and click the Next
button to begin the installation.
3-42 HTML Server on WebSphere Reference Guide
Verifying the Versions of Installed WebSphere Products
14. After the Plug-ins update is complete, the Success screen indicates the status of the
maintenance package installation.
15. Click the Finish button to exit the Update Installer wizard.
3.8 Verifying the Versions of Installed WebSphere Products
This section describes how to verify the versions of these installed WebSphere
products:
■
WebSphere Application Server
■
IBM HTTP Server
■
WebSphere Plugins for IBM WebSphere Application Server
3.8.1 WebSphere Application Server
Use this procedure to verify the version of the IBM WebSphere Application Server.
Alternatively, you can execute versionInfo.sh from the <was_home>/bin directory as
shown in the screen sample below.
Installing and Configuring WebSphere 7.0
3-43
Starting the WebSphere Application Server
3.8.2 IBM HTTP Server
Use this procedure to verify the version of the IBM HTTP Server.
3.8.3 WebSphere Plugins for IBM WebSphere Application Server
Use this procedure to verify the version of the IBM HTTP Server.
3.9 Starting the WebSphere Application Server
Note: By default, WebSphere Application Server 7.0 creates and
configures a default server named server1 during installation. If you
named your server something other than the default value, then
substitute that name for server1 in the following steps.
To start the WebSphere Application Server:
1.
Start a command prompt.
3-44 HTML Server on WebSphere Reference Guide
Determining the Name and Status of the WebSphere Application Server
2.
Navigate to the WebSphere/AppServer/profiles/profile_name/bin directory. For
example:
cd /u01/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
3.
Issue the command startServer followed by the Application Server name. For
example:
./startServer.sh server1
This command is case sensitive.
Note: Starting with Tools Release 8.97, you can use the Server
Manager to start the WebSphere process.
3.10 Stopping the WebSphere Application Server
Note: By default, WebSphere Application Server 7.0 creates and
configures a default server named server1 during installation. If you
named your server something other than the default value, then
substitute that name for server1 in the following steps.
To stop the WebSphere Application Server:
1.
Start a command prompt.
2.
Navigate to the WebSphere/AppServer/profiles/profile_name/bin directory. For
example:
cd /u01/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
3.
Issue the command stopServer followed by the Application Server name. For
example:
./stopServer.sh server1
This command is case sensitive.
Note: Starting with Tools Release 8.97, you can use the Server
Manager to stop the WebSphere process.
3.11 Determining the Name and Status of the WebSphere Application
Server
To determine the name and status of any or all WebSphere Application servers:
1.
Start a command prompt.
2.
Navigate to the WebSphere/AppServer/profiles/profile_name/bin directory. For
example:
cd /u01/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
3.
Issue the command serverStatus followed by the Application Server name (or with
the all option to view the status of all the servers in the profile). For example, to
view the status of all Application Servers:
./serverStatus.sh -all
Installing and Configuring WebSphere 7.0
3-45
Starting the IBM HTTP Server
3.12 Starting the IBM HTTP Server
To start the IBM HTTP Server:
1.
Start a command prompt.
2.
Navigate to the <ibm_http_server_location>/bin directory and issue the start
command with the -k option. For example:
cd /u01/IBM/HTTPServer/bin
./apachectl -k start
This command is case sensitive.
Note: Starting with Tools Release 8.97, you can use the Server
Manager to start the IBM HTTP Server process.
3.13 Stopping the IBM HTTP Server
To stop the IBM HTTP Server:
1.
Start a command prompt.
2.
Navigate to the <ibm_http_server_location>/bin directory and issue the stop
command with the -k option. For example:
cd /u01/IBM/HTTPServer/bin
./apache -k stop
This command is case sensitive.
Note: Starting with Tools Release 8.97, you can use the Server
Manager to stop the IBM HTTP Server process.
3.14 Accessing the WebSphere Administration Console
The WebSphere Administration Console is completely web-based and can be accessed
from any supported web browser. The default URL is:
http://<machinename>:<profile_port>/admin
where machine_name is the name of the machine on which WebSphere Application
Server has been installed, and
where profile_port was defined during the profile creation in the profile creation
wizard. For the first profile created, the default value is usually 9060.
To access the WebSphere Administration Console on the installed machine:
1.
Ensure that the WebSphere Application Server (default name is server1) is
started.
2.
Start a web browser.
3.
Enter this URL to access the WebSphere Administration Console:
http://localhost:9060/admin
3-46 HTML Server on WebSphere Reference Guide
Accessing the WebSphere Administration Console
Tip: If the port number is unknown and the default port is not
working, the AboutThisProfile.txt file contains the key
Administrative console port, which typically lists the assigned
admin port number. Typically this file is located in this directory:
/u01/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThi
sProfile.txt
4.
On the Log in to the console screen, enter a valid or new user.
Installing and Configuring WebSphere 7.0
3-47
Testing the WebSphere and IBM HTTP Server Installation
Upon successful logon, the WebSphere Application Server welcome screen is
displayed. You can use this application to manage your WebSphere servers and
related machines.
3.15 Testing the WebSphere and IBM HTTP Server Installation
To test the WebSphere Administration Console:
1.
Ensure that the WebSphere Application Server (default name is server1) is
started.
2.
Ensure that the IBM HTTP Server is started.
3.
Start a web browser.
4.
Enter this URL to test the WebSphere Administration Console:
http://<machine_name>:<http_port>/snoop
where machine_name is your server, and
where http_port is the port of your IBM HTTP Server. The default value is 80.
For example:
http://localhost:80/snoop
3-48 HTML Server on WebSphere Reference Guide
Generating and Propagating WebSphere Plug-ins (optional)
Upon successful execution, the resulting page should display information similar
to the above. This indicates that your WebSphere Application Server is
successfully installed and functioning.
3.16 Generating and Propagating WebSphere Plug-ins (optional)
Note: This section is informational only and is not required before
you install the Oracle JD Edwards EnterpriseOne HTML Web server.
Whenever you install new enterprise applications, or create new virtual hosts, you
must regenerate Web Server plug-ins. If your WebSphere installation is on a single
machine, you can generate plug-ins from the WebSphere Administrative console.
However, your configuration is across multiple machines, you might need to manually
generate plug-ins.
This section describes these topics:
■
Generating WebSphere Plug-ins
■
Propagating WebSphere Plug-ins
3.16.1 Generating WebSphere Plug-ins
To generate WebSphere plug-ins:
1.
Log on to the WebSphere Administrative console as described in Accessing the
WebSphere Administration Console.
2.
On the left hand navigation pane, select Servers > Server Types > Web servers
Installing and Configuring WebSphere 7.0
3-49
Generating and Propagating WebSphere Plug-ins (optional)
3.
Click the check box next to the webserver definition for which you want to
regenerate plug-ins.
4.
To generate plug-ins, click the Generate Plug-in button, which is located above the
webserver definition.
The Plug-in file plugin-cfg.xml is regenerated in place, typically at this location:
/u01/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/
densun30Node01Cell/nodes/densun30Node01/servers/webserver1
A status message will display under the Web servers section.
3-50 HTML Server on WebSphere Reference Guide
Generating and Propagating WebSphere Plug-ins (optional)
5.
You must restart the IBM HTTP for any plug-in changes to take effect.
3.16.2 Propagating WebSphere Plug-ins
To propagate the generated WebSphere plug-ins:
1.
Log on to the WebSphere Administrative console as described in Accessing the
WebSphere Administration Console.
2.
On the left hand navigation pane, select Servers > Server Types > WebServers.
3.
Click the check box next to the webserver definition for which you want to
propagate plug-ins.
4.
To generate plug-ins, click the Propagate Plug-in button, which is located above the
webserver definition.
The Plug-in file plugin-cfg.xml is propagated in place, typically at this location:
/u01/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml
A status message displays under the Web servers section as indicated in this
screenshot sample:
Installing and Configuring WebSphere 7.0
3-51
Generating and Propagating WebSphere Plug-ins (optional)
Note: Federated (Clustered) Web Servers. If you are using
WebSphere Application Server and running JD Edwards
EnterpriseOne as part of a federated (or clustered) web server, you
may need to regenerate the WebSphere global plugin configuration
after deploying the newest tools release. This is required when new
servlets have been added to the tools release you are deploying.
To update (regenerate) plugins, refer to the following procedure.
To update (regenerate) and propagate the global web server plugin configuration:
1.
Log on to the Deployment Manager Administration Console using the Dmgr01
profile.
3-52 HTML Server on WebSphere Reference Guide
Creating a New Application Server Profile (optional)
2.
Expand the Environment node and select Update global Web server plug-in
configuration.
3.
Review the content in the right-hand pane and note the location of the plug-in file
in the description. For example, the description might say:
The global plugin-cfg.xml file is placed in the %was_profile_
home%/config/cells directory.
4.
Click the OK button.
3.17 Creating a New Application Server Profile (optional)
Note: This section is informational only and is not required before
you install Oracle JD Edwards EnterpriseOne HTML Web server.
To create a new application server profile:
1.
Launch the profile creation wizard. For example:
cd /u01/IBM/WebSphere/AppServer/bin/ProfileManagement
./pmt.sh
Installing and Configuring WebSphere 7.0
3-53
Creating a New Application Server Profile (optional)
2.
On the Welcome screen, click the Launch Profile Management Tool button.
3.
On Profile Management Tool, click the Create button to begin the profile
configuration.
3-54 HTML Server on WebSphere Reference Guide
Creating a New Application Server Profile (optional)
4.
On Environment Selection, select Application Server as the type of environment to
create.
5.
Click the Next button to continue.
Installing and Configuring WebSphere 7.0
3-55
Creating a New Application Server Profile (optional)
6.
On Profile Creation Options, select the Typical profile creation radio button.
7.
Click the Next button to continue.
3-56 HTML Server on WebSphere Reference Guide
Creating a New Application Server Profile (optional)
8.
Administrative security is enabled for the profile by default. Clear the check box to
disable administrative security or enter the user name and password.
On Enable Administrative Security, the check box for the application server profile
is checked by default. You can choose either to:
■
■
9.
Clear the check box for Enable administrative security to disable server
administrative security, or
If the check box is enabled for Enable administrative security, server
administration security will be enabled and you must enter the User ID and
Password
Click the Next button to continue.
Installing and Configuring WebSphere 7.0
3-57
Creating a New Application Server Profile (optional)
10. On Profile summary, review your selections.
11. Click the Create button to start the profile creation.
3-58 HTML Server on WebSphere Reference Guide
Deleting a Profile (optional)
When complete, the installer displays the message: The Profile Management Tool
created the profile successfully. It is not necessary to Launch the First Steps
console at this time; you can clear the check box, which is checked by default.
12. Click the Finish button to complete the wizard and the profile configuration and
proceed to the final Profiles screen.
13. Exit the Profile Management Tool by choosing File > Exit.
3.18 Deleting a Profile (optional)
This section is provided as reference in case you need to delete a WebSphere base or
Network Deployment profile.
1.
From a command prompt, change to this directory:
cd /u01/IBM/WebSphere/AppServer/bin
2.
To delete a profile, issue this command:
./manageprofiles.sh delete profileName profile_name
where profile_name is the name of the profile to be deleted.
If the profile_name is valid, and the command successfully executed, the system
returns this message:
Installing and Configuring WebSphere 7.0
3-59
Adding a New Web Server for a New Profile (optional)
INSTCONFSUCCESS: Success: The profile no longer exists.
When you delete a profile, the profile and its directory are deleted, except for the
logs directory. You must manually delete the logs directory and then delete the
profile directory.
3.19 Adding a New Web Server for a New Profile (optional)
Each profile should be associated with a Web Server. The EnterpriseOne HTML Web
Server install fails if it does not find a webserver associated with the profile specified
during the install. If the newly created profile is an ND profile, you can create the Web
Server by using the button Create a New Web Server from the Web Servers page on the
WebSphere Administrator Console. However, if the newly created profile is not an ND
profile, the option to Create a New Web Server is not available. Instead, you must create
a new web server must be created from the command line.
To add a new web server for a new profile from the command line:
1.
Locate a copy of this Web Server configuration file which is typically located in
this directory with this name:
/u01/IBM/HTTPServer/Plugins/bin
2.
Make a copy of the configurewebserver<webserver_port>.bat file assigning a
new port value to the copy. For example, assuming you have changed directory to
/u01/IBM/HTTPServer/Plugins/bin:
cp configurewebserver1.sh configurewebserver2.sh
Do not manually copy the configurewebserver1.sh file to the specific profile
directory.
3.
Edit the new configuration file (configurewebserver2.sh) file that resides in the
/u01/IBM/HTTPServer/Plugins/bin directory to change the settings to be unique
to and specific to your newly created profile.
Change the settings to be unique to and specific to your newly created profile.
A sample file is provided below where:
the newly created profile is called AppSrv02, and
the new webserver will be called webserver81, and
the name of the node that we specified for our new profile is SERVERNode02, and
the name of the server itself is SERVER.domain.com.
The above is illustrated by the bolded settings in this sample file:
/u01/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/wsadmin.sh
$PRO-FILE_NAME_PARAMETER
$WSADMIN_USERID_PARAMETER
$WSADMIN_PASSWORD_PARAMETER
-conntype NONE -f
'/u01/IBM/WebSphere/AppServer/bin/configureWebserverDefinition.jacl'
web-server2 IHS '/u01/IBM/HTTPServer'
'/u01/IBM/HTTPServer/conf/httpd.conf' 81
MAP_ALL '/u01/IBM/HTTPServer/Plugins' managed
densun30Node02 den-sun30.mlab.jdedwards.com solaris
3-60 HTML Server on WebSphere Reference Guide
Adding a New Web Server for a New Profile (optional)
Note: Where the original settings for these bolded entries were
probably something similar to these:
■
AppSrv01
■
web-server1
■
80
■
SERVERNode01
4.
Save the file.
5.
From the directory where the shell script exists, execute it using this command:
./configurewebserver2.sh
The console displays these messages when the shell script is running and finishes:
6.
Verify your newly created Web Server is created by logging into the WebSphere
Admin Console and clicking on Web Servers. For example:
Installing and Configuring WebSphere 7.0
3-61
Adding a New Web Server for a New Profile (optional)
3-62 HTML Server on WebSphere Reference Guide
4
Running the HTML Server
4
This chapter contains the following topics:
■
Section 4.1, "Starting the HTML Server"
■
Section 4.2, "Stopping the HTML Server"
■
Section 4.3, "Accessing the HTML Server"
■
Section 4.4, "Generating Serialized Objects for the HTML Server"
■
Section 4.5, "Configuring the HTML Server for Non-Western European
Languages"
■
Section 4.6, "Enabling the Browser Side Debugging Feature on the Web Client"
■
Section 4.7, "Customizing the Disclaimer for the Sign-In Page"
■
Section 4.8, "Setting Up Quick Links for Pervasive Device Support"
■
Section 4.9, "Clearing File Attachments from the Browser Cache"
Tip: In order to enable any modifications, you should always stop
and restart the Application Server any time you modify the
configuration.
Note: Beginning with Tools Release 8.97, many administrative tasks
(such as starting and stopping services) for both the HTTP server and
the JD Edwards EnterpriseOne HTML Web server can be performed
through the Server Manager Console.
4.1 Starting the HTML Server
The JD Edwards EnterpriseOne HTML Server is installed in the instance of the
application server that you defined when you installed the Web Server (for example,
AS_JS_81). Complete this task to start the server.
To start the HTML Server:
1.
Start the Server Manager console.
2.
Select the Server and Instance you want to start.
3.
Select the Start button.
4.
If you are using the 64-bit instance of DB2 8.1, 8.2, 9.1 on a 64-bit kernel, open the
startServer.sh script and verify that the environment variable is correct for your
platform.
Running the HTML Server 4-1
Stopping the HTML Server
Note: This step does not apply to the Linux platform, since JD
Edwards EnterpriseOne is not supported on 64-bit db2 on Intel 32
hardware.
Note that $<DB2_Instance_Home>/sqllib/lib32 must be in the path. If the path to
lib32 is missing, add the path as shown in these examples:
■
For AIX:
LIBPATH="$WAS_LIBPATH":$<DB2_Instance_Home>/sqllib/lib32:$LIBPATH
■
For Solaris:
LD_LIBRARY_PATH="$WAS_LIBPATH":$<DB2_Instance_Home>/sqllib/lib32:
$LD_LIBRARY_PATH
■
For HP-UX:
SHLIB_PATH="$WAS_LIBPATH":$<DB2_Instance_Home>/sqllib/lib32:$SHLIB_
PATH
4.2 Stopping the HTML Server
The JD Edwards EnterpriseOne HTML Server is installed in an instance of the
application server that you defined when you installed the Web Server (for example,
AS_JS_81). Complete this task to stop the server.
To Stop the HTML Server:
1.
Start the Server Manager console.
2.
Select the Server and Instance you want to stop.
3.
Select the Stop button.
4.3 Accessing the HTML Server
You can access the HTML Server from any web browser connected to your network.
To access the HTML Server:
1.
Open the JD Edwards HTML client by opening a browser and entering this URL:
http://<web_server_name>:<port_number>/jde/owhtml or
http://<web_server_name>:<port_number>/jde/E1Menu.maf
For example:
http://jdewebs1.myserver.com:81/jde/owhtml or
http://jdewebs1.myserver.com:81/jde/E1Menu.maf
4.4 Generating Serialized Objects for the HTML Server
Starting with application release 8.12, JD Edwards EnterpriseOne specs are delivered
in XML format, which allows for on-demand generation of serialized Java objects from
4-2 HTML Server on WebSphere Reference Guide
Customizing the Disclaimer for the Sign-In Page
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.
4.5 Configuring the HTML Server for Non-Western European Languages
If you are setting up the HTML Server to run Non-Western European Languages,
complete this task to ensure that the Application Server is properly configured for
Unicode.
To configure the HTML Server for Non-Western European Languages:
1.
Open the WebSphere Administrative Console, and select the Application Server
for the JD Edwards HTML Server.
2.
Using Server Manager, verify this code page parameter and setting:
codePage=1252
3.
Using Server Manager, verify this UBE queue parameter and setting:
UBEQueue=QB900
4.6 Enabling the Browser Side Debugging Feature on the Web Client
In past releases, a user working on a form in the web client could press the Ctrl+D
keys to display GUI elements at the bottom of the page that are used for browser side
debugging. Starting with release 8.96, this feature is disabled in the default mode, and
the web client no longer displays this debugging feature when Ctrl+D is pressed. To
enable this feature for developers and support personnel, the system administrator
must modify the JDEDTA.js file as described in this task.
To enable the browser side debugging feature:
1.
On the HTML Server, navigate to the webclient.war/js/ directory, and open the
JDEDTA.js file in a text editor.
2.
Search for the following line:
var allowDebug=false;
and change the value to true.
3.
Save the file.
You do not need to restart the server to activate the change.
4.
Open Internet Explorer, and press the Refresh button to reload the page.
This action refreshes the .js files cached in the browser to activate the Ctrl-D
feature.
4.7 Customizing the Disclaimer for the Sign-In Page
When web-based clients log on to JD Edwards EnterpriseOne, the sign-in page
includes a default disclaimer that is included in a file shipped with the HTML Server
software. This task describes how to modify this file to include your own disclaimer.
To specify an additional disclaimer for the sign-in page:
1.
Open this file in a text editor:
<JAS_HOME>\webcontent\share\html4login.jsp
Running the HTML Server 4-3
Setting Up Quick Links for Pervasive Device Support
where <JAS_HOME> is the installation directory of the HTML Server.
2.
Make a backup of this file.
3.
Locate the following line and specify your disclaimer with the following element:
String companyDisclaimerHTML = "";
For example:
String companyDisclaimerHTML = "By signing in, you agree to the <a
href=\"http://server/path-to/privacypolicy.html\">privacy policy</a>.";
Tip: This element is Java code. Therefore, quotation marks must be
preceded by a back-slash character, as shown above.
4.
Save the file.
Your changes should take effect immediately. If not, restart the portal.
4.8 Setting Up Quick Links for Pervasive Device Support
JD Edwards EnterpriseOne offers support for Pervasive Devices. Developers can write
custom applications for PocketPC 2003 devices using the EnterpriseOne toolset.
However, JD Edwards EnterpriseOne menus are not supported on Pervasive Device
clients, so a new XML file (PervasiveAppQuickLinks.xml) was added to the HTML
Server that allows a system administrator define the list of applications that can be
executed on the Pervasive Device client. This file can be edited to add, modify, or
delete JD Edwards EnterpriseOne applications that are accessible to Pervasive Device
clients. Each application listed in this file is defined by a quick-link tag that describes
the application, form, and version of the object, and includes a description. A sample
quick-link tag is shown below:
<quick-links>
<quick-link launchAction="launchForm"
appID="P0411"
formID="W0411G"
version="ZJDE0001"
description="3 G0411 - Standard Voucher Entry
(P0411_W0411G_ZJDE0001)"/>
</quick-links>
Quick-link tags can include the following attributes:
Attribute
Required?
launchActi yes
on
Description
Specifies the action that occurs when users click on the
quick-link. Valid values are:
■
launchForm
Launch the form directly.
■
promptForValue
Request values for the processing options.
■
promptForVersion
Request which version of the form to open.
appID
yes
4-4 HTML Server on WebSphere Reference Guide
Program number of the application. For UBE type
objects, the AppID is the UBE name.
Setting Up Quick Links for Pervasive Device Support
Attribute
Required?
Description
appType
Required for
promptForVersion
action.
Type of application.
Valid values are:
■
APP
■
UBE
formID
Required for
Number of the specific form within the application.
launchForm and
promptForValue actions.
Also required with the
appType attribute.
version
No
description Yes
Version number of the form.
Description of the form. This description appears in the
list displayed on the Pervasive Device client.
To edit the PervasiveAppQuickLinks.xml file
1.
On the HTML Server, navigate to this directory: <JAS_
Home>/installedApps/<node_name>/EA_JS_81.ear/webclient.war/classes.
Open the PervasiveAppQuickLinks.xml file in a text editor.
2.
Add quick-link tags for each of the JD Edwards EnterpriseOne applications you
want to make accessible to Pervasive Devices.
You can also delete or modify existing tags to remove or change the forms that
Pervasive Device clients can access. When clients access JD Edwards
EnterpriseOne from a Pervasive Device, the forms are listed as links in the same
order they appear in the PervasiveAppQuickLinks.xml file.
Save and exit the file.
Below is an example of the PervasiveAppQuickLinks.xml file:
<?xml version="1.0" encoding="UTF-8" ?>
<quick-links>
<quick-link launchAction="launchForm" appID="P0411" formID="W0411G"
version="ZJDE0001" description="3 G0411 - Standard Voucher Entry
(P0411_W0411G_ZJDE0001)" />
<quick-link launchAction="launchForm" appID="P01012"
formID="W01012B" version="ZJDE0001" description="P01012_W01012B" />
<quick-link launchAction="promptForValue" appID="P01012"
formID="W01012B" version="ZJDE0001" mode="1" appType="APP"
description="Prompt for Values(P01012_W01012B,ZJDE0001,1,APP)" />
<quick-link launchAction="promptForValue" appID="P4210"
formID="W4210E" description="Prompt for Values(P4210_W4210E)" />
<quick-link launchAction="promptForVersion" appID="P01012"
formID="W01012A" appType="APP" description="Prompt for
Version(P01012_W01012A)" />
<quick-link launchAction="promptForVersion" appID="R0006P"
appType="UBE" description="Prompt for Version(R0006P)" />
<quick-link launchAction="launchForm" appID="P98TREE"
formID="W98TREEA" description="P98TREE_W98TREEA" />
<quick-link launchAction="launchForm" appID="P98SYSGR"
formID="W98SYSGRB" description="P98SYSGR_W98SYSGRB" />
<quick-link launchAction="launchForm" appID="P98CTRL"
formID="W98CTRLA" description="P98CTRL_W98CTRLA" />
<quick-link launchAction="launchForm" appID="P98RUNPC"
formID="W98RUNPCM" description="P98RUNPC_W98RUNPCM" />
Running the HTML Server 4-5
Clearing File Attachments from the Browser Cache
<quick-link launchAction="launchForm" appID="P98SYSFM"
formID="W98SYSFMA" description="P98SYSFM_W98SYSFMA" />
<quick-link launchAction="launchForm" appID="P98SYSFM"
formID="W98SYSFMB" description="P98SYSFM_W98SYSFMB" />
<quick-link launchAction="launchForm" appID="P98FRMFL"
formID="W98FRMFLA" description="P98FRMFL_W98FRMFLA" />
<quick-link launchAction="launchForm" appID="P98MEDIA"
formID="W98MEDIAA" description="P98MEDIA_W98MEDIAA" />
<quick-link launchAction="launchForm" appID="P90CB050"
formID="W90CB050A" description="P90CB050_W90CB050A" />
<quick-link launchAction="launchForm" appID="P55SFRU1"
formID="W55SFRU1A" description="P55SFRU1_W55SFRU1A" />
<quick-link launchAction="launchForm" appID="P99WIZ01"
formID="W99WIZ01B" description="P99WIZ01_W99WIZ01B" />
<quick-link launchAction="launchForm" appID="P99WIZ03"
formID="W99WIZ03A" description="P99WIZ03_W99WIZ03A" />
<quick-link launchAction="launchForm" appID="PMODAL"
formID="WMODALA" description="PMODAL_WMODALA" />
<quick-link launchAction="launchForm" appID="P42101"
formID="W42101C" description="New Sales Order Application" />
</quick-links>
4.9 Clearing File Attachments from the Browser Cache
In a typical environment, file attachments (such as Media Object attachments and JD
Edwards EnterpriseOne reports) are automatically cached into the \Temporary
Internet Files directory on web-based client machines when these attachments are
opened from a browser. This situation allows copies of confidential documents, such
as Media Objects, images, and web pages, to proliferate across workstations on which
these objects are opened.
To prevent these objects from persisting in the internet cache, administrators should
configure the browsers to automatically clear the cache when the client closes the
browser. This protection is particularly important in a kiosk environment. The
procedure for clearing the cache depends on the type of browser. Refer to the relevant
task below to secure the browser used in your system.
In addition to securing the browser cache, Media Object Security was added in 8.96 to
ensure that media objects can be secured within the application. For more information
on this topic, see "Managing Media Object Security" in the JD Edwards EnterpriseOne
Tools Security Administration Guide.
This section describes these tasks:
■
Section 4.9.1, "Securing Internet Explorer"
■
Section 4.9.2, "Securing Safari"
■
Section 4.9.3, "Securing Mozilla Firefox,"
4.9.1 Securing Internet Explorer
Complete this task to automatically clear the cache in Internet Explorer.
1.
In Internet Explorer, select Tools, Internet Options from the drop down menu.
2.
Click the Advanced tab.
4-6 HTML Server on WebSphere Reference Guide
Clearing File Attachments from the Browser Cache
3.
In the "Settings" box, scroll down to the section labeled "Security," and select the
check box next to Empty Temporary Internet Files folder when browser is
closed."
4.
Click OK to save the change.
This option does not delete cookies, but will clear your cache of other files when
you close the browser.
Tip:
Access the following web page for more details:
http://www.microsoft.com/windows/ie/using/howto/customizing/
clearcache.mspx
4.9.2 Securing Safari
Activate the Private Browsing feature of Safaris to secure the browser. When activated,
no web addresses, personal information, or pages are saved or cached on the browser,
and no trace of any activity is recorded.
4.9.3 Securing Mozilla Firefox
Activate the Clear Private Data tool to secure Firefox. This tool allows you to delete all
personal data, including browsing history, cookies, Web form entries and passwords
with a single click. Mozilla Firefox can also be configured to automatically clear this
information when you close the browser.
Running the HTML Server 4-7
Clearing File Attachments from the Browser Cache
4-8 HTML Server on WebSphere Reference Guide
5
Understanding EnterpriseOne HTML Server
Package Discovery
5
This chapter contains the following topics:
■
Section 5.1, "Overview of EnterpriseOne HTML Server Package Discovery"
■
Section 5.2, "Impacts to End Users"
■
Section 5.3, "Understanding the Manifest"
5.1 Overview of 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 JAS 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 JAS
instances, unless all these instances run on the same path code and same package.
Understanding EnterpriseOne HTML Server Package Discovery
5-1
Impacts to End Users
5.2 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.
5.3 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.
5-2 HTML Server on WebSphere Reference Guide
A
Configuring Secure Socket Layer with the
HTML Server
A
The chapter describes how to configure Secure Socket Layer (SSL) with the HTML
Server, and includes the following tasks:
■
Appendix A.1, "Configuring SSL on the IBM HTTP Server"
■
Appendix A.2, "Configuring SSL on IBM WebSphere"
A.1 Configuring SSL on the IBM HTTP Server
SSL requires a Signed Personal Certificate. You can either request a CA-Signed
Personal Certificate directly from IBM, or you can generate a Self-Signed Certificate
yourself. This task describes how to generate and use a Self-Signed Certificate. For
production environments, we recommend you request one from CA. For instructions
to request a CA-Signed Personal Certificate, refer to the IBM Info Center.
1.
Create a folder named keys in the HTTP Server installation directory.
2.
Start the ikeyMan utility which is located in the bin directory of your HTTP Server.
For example:
/u01/IBM/WebSphere/AppServer/bin
3.
In the IikeyMan utility, create a Key Database File by navigating Key Database File >
New.
Configuring Secure Socket Layer with the HTML Server
A-1
Configuring SSL on the IBM HTTP Server
4.
At the prompt, enter the following information:
■
Key Database Type = CMS
Only CMS is supported with the IBM HTTP Server.
■
File Name = serverkey.kdb
■
Location = /u01/IBM/HTTPServer/keys
5.
Enter the password (for example, "serverkey") and select the option stash the
password file.
6.
Click the OK button.
7.
From the drop down box, select Personal Certificates.
8.
Click New Self-Signed.
9.
Enter following information on the screen that appears:
■
Key Label= Enter any label (for example, server_cert)
■
Version= X509V3
■
Key Size = 1024
■
Common Name = Fully Qualified Server Name (for example,
denicint2.mlab.jdedwards.com)
■
Organization = your organization name (for example, Oracle).
■
Country or region = US
■
Validity Period = 365 days
A sample screen shot is provided below:
A-2 HTML Server on WebSphere Reference Guide
Configuring SSL on the IBM HTTP Server
10. On Create New Self-Signed Certificate, after the fields are complete click the OK
button.
The program displays your certificate in the list.
11. Delete all the other certificates.
12. Open the httpd.conf file in a text editor, and add the following virtual host
definition.
Note: The text in the httpd.conf is case sensitive; type the host
definition exactly as shown.
If you have already configured a port on the HTTP Server (for example, port 91),
the file will include an Alias. Use the same alias under your Virtual Host definition
as described here.
For version 8.5.x. make the changes listed below:
# Example SSL configuration which supports SSLv3 and TLSv1
# To enable this support:
#
1) Create a key database with ikeyman
#
2) Update the KeyFile directive below to point to that key database
#
3) Uncomment the directives up through the end of the example
#
Note: The IPv6 Listen directive must only be uncommented if
#
IPv6 networking is enabled.
#
# uncomment below line to enable ssl
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
<IfModule mod_ibm_ssl.c>
Listen 0.0.0.0:443
Configuring Secure Socket Layer with the HTML Server
A-3
Configuring SSL on the IBM HTTP Server
# IPv6 support:
# Listen [::]:443
<VirtualHost *:443>
Alias /jde
"/u01/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/denicint2Node01Ce
ll/EA_JS_9x.ear/webclient.war"
SSLEnable
SSLProtocolDisable SSLv2
</VirtualHost>
<Directory
"/u01/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/denicint2Node01Ce
ll/EA_JS_9x.ear/webclient.war/WEB_INF">
Order Deny,Allow
Deny from All
</Directory>
<Directory
"/u01/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/denicint2Node01Ce
ll/EA_JS_9x.ear/webclient.war">
Order Deny,Allow
Allow from All
</Directory>
</IfModule>
KeyFile /u01/IBM/HTTPServer/keys/WebServerKeys.kdb
SSLDisable
# End of example SSL configuration
For version 9.x onward make the changes listed below:
# Example SSL configuration
# To enable this support:
#
1) Create a key database with ikeyman
#
2) Update the KeyFile directive below to point to that key database
#
3) Uncomment the directives up through the end of the example
#
Note: The IPv6 Listen directive must only be uncommented if
#
IPv6 networking is enabled.
#
# uncomment below line to enable ssl
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
<IfModule mod_ibm_ssl.c>
# IPv6 support:
Listen 0.0.0.0.443
<VirtualHost *:443>
Alias /jde
"/u01/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/denicint2Node01Ce
ll/EA_JS_9x.ear/webclient.war"
SSLEnable
</VirtualHost>
<Directory
"/u01/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/denicint2Node01Ce
ll/EA_JS_9x.ear/webclient.war/WEB_INF">
Require all denied
</Directory>
<Directory
"/u01/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/denicint2Node01Ce
ll/EA_JS_9x.ear/webclient.war">
Require all granted
</Directory>
</IfModule>
SSLDisable
KeyFile /u01/IBM/HTTPServer/keys/WebServerKeys.kdb
# End of example SSL configuration
A-4 HTML Server on WebSphere Reference Guide
Configuring SSL on IBM WebSphere
A.2 Configuring SSL on IBM WebSphere
1.
Log on to your WebSphere Admin Console.
2.
Navigate to EnvironmentVirtual Hosts.
3.
Select your virtual host.
For example, if you initially installed your application on port 91, then the virtual
host should be VH_EA_JS_9x.
4.
Under the virtual host, select Additional PropertiesHostAliases.
5.
Under Host Aliases, click New.
A sample screen shot is provided below:
6.
Create a new host alias using the fully qualified name of the server and a port
number of 443.
■
Host: *
■
port: 443 (Default SSL Port)
7.
Regenerate and propogate the HTTP Server plug-in file and restart your HTTP
Server.
8.
Select your particular webserver.
9.
Select Plug-in properties.
10. Click on Copy to Web server key store directory.
Configuring Secure Socket Layer with the HTML Server
A-5
Configuring SSL on IBM WebSphere
11. Restart the Application Server.
You should be able to login to the following URL:
https://fully_qualified_server_name/jde/E1Menu.maf
A-6 HTML Server on WebSphere Reference Guide
B
Uninstalling a WebSphere 8.5.x/9.0 Fix Pack
B
These appendix describes these tasks:
■
Section B.1, "Uninstalling a WebSphere 8.5.x/9.0 Fix Pack"
■
Section B.2, "Uninstalling a WebSphere 7.0 Fix Pack"
B.1 Uninstalling a WebSphere 8.5.x/9.0 Fix Pack
To uninstall a WebSphere fix pack:
1.
Launch the Update Installer wizard.
2.
Select the Uninstall option.
3.
On Uninstall Packages, use the checkboxes to select the Installation Package that
you want to uninstall
4.
Click the Uninstall button.
B.2 Uninstalling a WebSphere 7.0 Fix Pack
To uninstall a WebSphere 7.0 fix pack:
1.
Launch the Update Installer wizard.
Uninstalling a WebSphere 8.5.x/9.0 Fix Pack
B-1
Uninstalling a WebSphere 7.0 Fix Pack
2.
On Product Selection, use the pulldown to select the directory path for the
component that you wish to uninstall.
3.
On Maintenance Operation Selection, choose the radio button for Uninstall
maintenance package.
B-2 HTML Server on WebSphere Reference Guide
Uninstalling a WebSphere 7.0 Fix Pack
4.
On the maintenance package to uninstall screen, select the radio button associated
with an available package to uninstall and click Next.
Repeat the same process for other packages as necessary.
Uninstalling a WebSphere 8.5.x/9.0 Fix Pack
B-3
Uninstalling a WebSphere 7.0 Fix Pack
B-4 HTML Server on WebSphere Reference Guide
C
Enabling Compression on IBM HTTP Server
C
You can set the mod_deflate directive within the httpd.conf file to enable the IBM
HTTP Server to compress output files and log the compression ratios. mod_deflate is
an Apache module in the httpd.conf file that compresses content sent from the web
server to the client browser.
This appendix contains the following topics:
■
Section C.1, "Understanding Compression"
■
Section C.2, "Configuring the mod_deflate directive"
C.1 Understanding Compression
Regular text and most non-image content are well suited for compression. Text files
can typically be compressed by 70% or more. Compression can save significant
bandwidth and enable faster browser response times. The effect is negligible in most
high speed LAN environments, but is quite noticeable for users on slow WAN
connections.
Compression is not recommended for files that are already compressed. A partial list
includes these types of files:
■
zip
■
PDF
■
exe
■
image files
Compressing these file types using mod_deflate can actually increase their size or
corrupt the files.
There are 9 levels of compression available when using mod_deflate. The difference
between the default level (6) and the maximum compression level (9) is minimal, and
the cost in extra CPU time necessary to process the higher compression level is
significant and ultimately not beneficial. For this reason, you should use the default
compression level.
C.2 Configuring the mod_deflate directive
For specific instructions to configure the mod_deflate directive, access the Apache
documentation on this web page, http://httpd.apache.org/docs/2.0/, and click on
the link for http://httpd.apache.org/docs/2.0/mod/directives.html. Refer to this
web page for instructions to configure each of the parameters discussed below. Also
refer to the sample mod_deflate module at the end of this appendix.
Enabling Compression on IBM HTTP Server
C-1
Configuring the mod_deflate directive
To enable compression, open the httpd.conf file, and verify that the LoadModule
deflate_module is uncommented (see the example below). You can configure mod_
deflate to compress documents in one of two ways (both of which are specified in the
httpd.conf file):
■
Explicit exclusion of files by extension
This method lists the file types that should NOT be compressed by the http server.
■
Explicit inclusion of files by MIME type.
This method lists file types that should always be compressed by the http server.
C.2.1 Logging Compression Results
The following three directives can be added to the httpd.conf file to enable the
writing of compression statistics to a log file. These directives will record the bytes
before compression (Input), the bytes after compression (Output), and calculate the
compression ratio:
DeflateFilterNote Input instream
DeflateFilterNote Output outstream
DeflateFilterNote Ratio ratio
The following line defines a new logging format to be used for the compression log.
The format is named "deflate." The second line below specifies the path and file name
of the log file (deflate.log) where the output is written.
LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate
CustomLog /u01/IBM/HTTPServer/logs/deflate.log deflate
C.2.2 Example: Configuring mod_deflate for EnterpriseOne
The following load module line enables compression for EnterpriseOne. Verify that the
line is uncommented in the httpd.conf file.
LoadModule deflate_module modules/mod_deflate.so
In the httpd.conf file, add the following lines under the existing <IfModule mod_
deflate.c> section. Note that the compression method used in this example is explicit
exclusion.
For specific instructions to configure the mod_deflate directive, access the Apache
documentation on this web page, http://httpd.apache.org/docs/2.0/, and click on
the link for http://httpd.apache.org/docs/2.0/mod/directives.html.
<IfModule mod_deflate.c>
DeflateFilterNote Input instream
DeflateFilterNote Output outstream
DeflateFilterNote Ratio ratio
LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate
CustomLog /u01/IBM/HTTPServer/logs/deflate.logdeflate
<Location / >
# Insert filter
SetOutputFilter DEFLATE
# Don't compress images or binaries
SetEnvIfNoCase Request_URI \
\.(?:gif|[jm]pe?g|png|t?gz|bz2*|zip|exe|iso|avi)$ no-gzip dont-vary
</Location>
</IfModule>
C-2 HTML Server on WebSphere Reference Guide
D
Understanding Media Objects on the Web
Server
D
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.
This appendix contains the following topics:
■
Section D.1, "Required jas.ini Settings"
■
Section D.2, "How Media Objects are Displayed by the HTML Server"
D.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=
FALSE
Specifies that the web server does not use
Microsoft Windows file sharing mechanism and
uses FTP access instead.
D.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.
Understanding Media Objects on the Web Server
D-1
How Media Objects are Displayed by the HTML Server
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.
Files are transferred using FTP protocol.
This diagram illustrates the process:
D-2 HTML Server on WebSphere Reference Guide
How Media Objects are Displayed by the HTML Server
Understanding Media Objects on the Web Server
D-3
How Media Objects are Displayed by the HTML Server
D-4 HTML Server on WebSphere Reference Guide
E
Generating JD Edwards EnterpriseOne
Serialized Objects
E
Note: To generate objects using Oracle WebLogic Server, you must
use the same JDK Version as your Application Server on the
Development Client machine. Additionally, you must modify the gen_
wls.bat file on the client machine to point to the location of your JDK
version.
Important: The JDK for the local Oracle WebLogic Server on the
Development Client machine is a 32-bit version.
Beginning with JD Edwards EnterpriseOne Release 9.2, specs are delivered in XML
format, which allows for on-demand generation of serialized objects from these XML
specs. Objects are automatically generated when the first user accesses an application.
Therefore, for Release 9.2 and beyond it is not necessary to manually generate
serialized objects using the eGenerator.
However, the eGenerator can still be used to manually generate serialized objects. The
eGenerator is 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 and F989999), and
retrieves them at runtime.
For a list of all requirements for the generation machine, refer to Chapter 1, "Accessing
Certifications" 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 HTML objects.
■
Section E.1, "Installing eGenerator"
■
Section E.2, "Logging In"
■
Section E.3, "Configuring eGenerator"
Generating JD Edwards EnterpriseOne Serialized Objects E-1
Installing eGenerator
■
Section E.4, "Generating the Serialized Object Manifest"
■
Section E.5, "Generating All Standard Serialized Objects"
■
Section E.6, "Generating a List of Objects (Bulk Generation)"
■
Section E.7, "Verifying the Generation Process"
■
Section E.8, "Generating Other Selected Objects"
E.1 Installing eGenerator
This section discusses the tasks you follow to install the eGenerator:
■
Section E.1.1, "Prerequisites"
■
Section E.1.3, "Preparing JD Edwards EnterpriseOne for Serialized Objects"
E.1.1 Prerequisites
Before you install the eGenerator, verify that the tasks below are completed:
■
Install a JD Edwards EnterpriseOne Development 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. This is also described in the JD
Edwards EnterpriseOne Development Client Installation Guide.
E.1.2 Setting the Default Storage Parameter (SQL Server Only)
The default storage parameter on your JD Edwards EnterpriseOne SQL Server
database might not enable enough space to transfer all the standard JD Edwards
EnterpriseOne Java objects. To avoid this potential problem, set the default storage
parameter as described below:
1.
Open the SQL Server database and set your database Maximum File Size
parameter to Unrestricted file growth.
Complete this step for each database to which you are installing the Java objects.
E.1.3 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:
E-2 HTML Server on WebSphere Reference Guide
Logging In
<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.
E.2 Logging In
Using eGenerator, you can generate JD Edwards EnterpriseOne objects in one of these
ways:
■
Section E.2.2, "Direct Generation to the Serialized Object Tables"
■
Section E.2.3, "Generate using the JD Edwards EnterpriseOne HTML Server"
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.
E.2.1 Running the eGenerator Diagnostic Tool
The eGenerator 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.
The auto diagnostic tool can be suppressed by launching
gen.bat with the -nodiag parameter.
Note:
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
E.2.2 Direct Generation to the Serialized Object Tables
The advantages of direct generation to the serialized object tables are:
Generating JD Edwards EnterpriseOne Serialized Objects E-3
Logging In
■
This is the recommended option.
■
You can generate objects before setting up the HTML Server.
■
This is the fasted method for all forms of generation.
■
This is the easiest method of generation to maintain.
To generate objects directly to a database:
1.
Run generator batch file for your Application Server.
For WebLogic Server
Run gen_wls.bat.
For WebSphere
Run gen.bat.
2.
In the Specify Settings section, click the Direct Generation radio button.
Note: 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. If this section is not
defined, the generation is based on the OCM configuration.
3.
Click the Connect button.
The system bypasses the HTML Server and connects directly to the database
specified in the jdbj.ini file.
4.
On EnterpriseOne Java Generation Login, enter the login information and click the
OK button.
Once you have logged in to a Web server, you can generate the serialized objects.
E-4 HTML Server on WebSphere Reference Guide
Logging In
E.2.3 Generate using the JD Edwards EnterpriseOne HTML Server
Complete this task if you want to generate objects using the JD Edwards
EnterpriseOne HTML server. This method uses the database configuration from the JD
Edwards EnterpriseOne HTML Server for the serialized object tables.
1.
On your generation machine, open a Microsoft Windows command window with
the Run as Administrator option
2.
Navigate to the corresponding directory for your application server, and run the
launchGen.bat file in that directory:
For JD Edwards EnterpriseOne running on WebLogic Server
x:\<release>\system\JAS\
For JD Edwards EnterpriseOne running on WebSphere Application Server:
x:\<release>\JAS
Note: You must edit the launchGen.bat to call the correct executable
file.
The default calls gen_wls.bat for WebLogic Server.
For WebSphere Application Server, you should edit the file to call
gen.bat.
3.
When the Generator launches, the Generator forms is displayed. You must enter a
valid value in this field:
Enter JAS Server Name
In addition to specifying the name, you must also specify the port value. For
example:
JASSERVER:8080
4.
Optionally, if you prefer to use the HTTPS protocol, you must complete the
following additional steps depending on you Application Server:
a.
Open the gen_wls.bat file with a text editor.
b.
Disable the non-SSL connection and enable the SSL connection. For example:
c.
Download the EnterpriseOne HTML WebLogic Keystore to the eGenerator
machine.
Generating JD Edwards EnterpriseOne Serialized Objects E-5
Logging In
Note: You can look up the Keystore location from WebLogic
Administration Console, or you can download the HTML Server
certificate and import it to a keystore on the eGenerator machine.
d.
Edit the Keystore location that is specified by this parameter:
-Djavax.net.ssl.trustStore
e.
Run the eGenerator application.
f.
Navigate to Options > Advanced Settings.
g.
In the Protocol Option section, select the radio button for HTTPS Protocol.
h.
In the Connection section, enter a JAS Server Name and HTTPS port. For
example:
JASSERVER:9090
WebSphere Application Server. For WebSphere Application
Server, you should follow the above steps plus some extra steps, all of
which are listed in the gen.bat file.
Note:
5.
Click the Connect button.
6.
On EnterpriseOne Java Generation Login, enter the login information and click the
OK button.
Once you have logged in to a Web server, you can generate the serialized objects.
E-6 HTML Server on WebSphere Reference Guide
Configuring eGenerator
E.3 Configuring eGenerator
The eGenerator includes a number of options you can set up for your particular
environment. The configuration process consists of these tasks:
■
Section E.3.1, "Setting eGenerator Options"
■
Section E.3.2, "Choosing Languages"
■
Section E.3.3, "Configuring the genapp.ini File"
E.3.1 Setting eGenerator Options
Before generating objects, you can use this procedure to define a variety of parameters
that affect how the eGenerator functions.
1.
From the pull-down menu, select Options > Advanced Settings.
2.
On Advanced Settings, select the options appropriate for your generation
requirements
■
Logging
Generating JD Edwards EnterpriseOne Serialized Objects E-7
Configuring eGenerator
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 E.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.
■
Protocol Option
You can use HTTPS protocol to connect to your HTML Server. You must have
SSL configured on the HTML server and download the trust store to the
generation machine. See the applicable steps in Section E.2.3, "Generate using
the JD Edwards EnterpriseOne HTML Server".
E.3.1.1 Generation Modes
The eGenerator has these modes for generating web objects:
■
Section E.3.1.1.1, "Sequential Generation"
■
Section E.3.1.1.2, "Parallel Generation."
■
Section E.3.1.1.3, "Using HTTPS Protocol to Connect to the HTML Server."
E.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
choosing Options > Advanced Settings> Sequential Generation.
The advantages of method are:
■
Most stable mode of generation.
■
Requires the least system resources such as memory.
■
Safe to use during a JITI (Just in Time Install) process.
The disadvantage is that the generation process can take longer.
E.3.1.1.2 Parallel Generation. This is the default mode of generation. You can turn off
this mode of generation by choosing Advanced Settings > Sequential Generation.
In this mode of generation the web objects are generated concurrently when you select
the Generate-All Objects option
The advantage is that this method is faster than Sequential Generation, especially with
multi-processor workstations and fast database connections.
The disadvantages are:
■
■
Cannot be used when the user does not have the full set of spec files, because JITI
might occur.
If a JITI occurs during parallel generation, the spec files can get corrupted.
E-8 HTML Server on WebSphere Reference Guide
Configuring eGenerator
E.3.1.1.3 Using HTTPS Protocol to Connect to the HTML Server. By default the eGenerator
uses the HTTP protocol for connection. However, you can change the setting using this
procedure.
1.
From the eGenerator, choose Options > Advanced Setting.
2.
On Protocol Option, choose this radio button to enable SSL on the HTML Server:
HTTPS Protocol
3.
Download the HTML Server certificate to a local machine using the x509.base
format.
4.
Import the certificate to a keystore. Below is an example of the syntax of the
import command:
Keytool -import -trustcacerts -file c:\temp\HTMLServer.cer -keystore
Z:\E920\e1keystore
5.
Edit the gen_wls.bat (WebLogic Server) or gen.bat (WebSphere) to use HTTPS
connection. This is done by:
■
Commenting out the non-SSL Java Program Call, and
■
Enabling the SSL connection.
For example:
6.
Edit the location of the trustStore in this parameter:
-Djavax.net.ssl.trustStore=
Upon completion of the steps in this procedure, you can now connect to the HTML
Server using the SSL port and the HTTPS protocol.
E.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, from the pulldown menu choose Options > Languages.
Generating JD Edwards EnterpriseOne Serialized Objects E-9
Generating the Serialized Object Manifest
2.
Click the check box next to each of the languages you want to use.
3.
Click the OK button.
E.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.
E.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 5, "Understanding
EnterpriseOne HTML Server Package Discovery".
Use this procedure to generate serialized object manifests:
1.
From the pull-down menu, choose Generate> Manifest.
E-10 HTML Server on WebSphere Reference Guide
Generating the Serialized Object Manifest
2.
Click the Create Manifest button.
3.
Click the Yes button.
The program creates the manifest and closes the window.
4.
To view the manifest that was created, from the pull down menu, select Generate
> Manifest.
Generating JD Edwards EnterpriseOne Serialized Objects
E-11
Generating All Standard Serialized Objects
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.
E.5 Generating All Standard Serialized Objects
The 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 E.8, "Generating Other Selected Objects".
Complete this task to generate a complete set of JD Edwards EnterpriseOne objects.
1.
From the pull-down menu, select File > Core Objects.
For more information on generating core objects, see Section E.8.1, "Generating
Core Objects".
2.
If the core objects generate successfully, from the pull-down menu, select Generate
> All Objects.
E-12 HTML Server on WebSphere Reference Guide
Generating All Standard Serialized Objects
3.
On Generate All Objects, check all the objects listed.
4.
Click the Start button.
The eGenerator checks the database connection before it attempts to generate
objects.
If it cannot connect to the database, the eGenerator displays this screen:
5.
If this screen displays, click the Stop button and verify the connection to the
database.
6.
If the last Generate-All session did not conclude successfully, the 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
Generating JD Edwards EnterpriseOne Serialized Objects
E-13
Generating a List of Objects (Bulk Generation)
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 the
message Generation completed successfully.
E.6 Generating a List of Objects (Bulk Generation)
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.
Use this procedure 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 the Connect button.
6.
Log on to JD Edwards EnterpriseOne and click the OK button.
7.
From the pull-down menu at the top of the screen, choose File > Bulk Generation.
8.
Click the Start button.
The eGenerator generates all the objects listed in the file you selected. When the
process is complete, eGenerator displays the message Generation Completed
Successfully.
E-14 HTML Server on WebSphere Reference Guide
Verifying the Generation Process
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.
Tip:
E.7 Verifying the Generation Process
Complete these tasks to verify the generation is successful:
■
Section E.7.1, "Checking Log Files"
■
Section E.7.2, "Checking Database Acknowledgements"
E.7.1 Checking Log Files
The eGenerator enables you to automatically display the Status Log and Error Log
files by selecting these options from a menu:
■
Status Log
■
Error Log
E.7.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
Generating JD Edwards EnterpriseOne Serialized Objects
E-15
Generating Other Selected Objects
E.8 Generating Other Selected Objects
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 E.8.1, "Generating Core Objects"
■
Section E.8.2, "Generating Applications"
■
Section E.8.3, "Generating Forms"
■
Section E.8.4, "Generating Reports"
■
Section E.8.5, "Generating NERs"
■
Section E.8.6, "Generating Data Dictionary Items"
■
Section E.8.7, "Generating Tables"
■
Section E.8.8, "Generating Business Views"
■
Section E.8.9, "Generating Data Structures"
E.8.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, on eGenerator, from the pulldown choose File > CoreObjects.
The 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.
E.8.2 Generating Applications
Complete one of these tasks to generate one or more applications:
■
Section E.8.2.1, "Generate an Application"
■
Section E.8.2.2, "Generate Applications by System Code"
■
Section E.8.2.3, "Generate Applications by Mode"
E.8.2.1 Generate an Application
Use this procedure to generate an application:
1.
From the pull-down menu, select Generate > Applications.
E-16 HTML Server on WebSphere Reference Guide
Generating Other Selected Objects
2.
Select Application Name, and enter the program number of the application (for
example, P01012).
3.
Click the Start button.
The eGenerator generates all forms contained in the application and all dependent
objects used by the application.
4.
Check the Status Log for status of generation.
E.8.2.2 Generate Applications by System Code
Use this procedure 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 the Start button.
The 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
entitled: Generating Options in the JD Edwards EnterpriseOne Form Design Aid Guide.
E.8.2.3 Generate Applications by Mode
Use this procedure to generate applications by Mode.
1.
From the pull-down menu, select Generate > Application.
2.
Select a mode.
Generating JD Edwards EnterpriseOne Serialized Objects
E-17
Generating Other Selected Objects
3.
Click Application Name, and enter the name of an application (for example,
P01012).
4.
Click the Start button.
E.8.3 Generating Forms
Use this procedure to generate forms:
1.
From the pull-down menu, choose Generate > Applications.
2.
Enter the form name in the Form Name field, for example, P01012_W01012A.
3.
Click the Start button.
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.
E.8.4 Generating Reports
Complete one of these tasks to generate one or more reports:
■
Section E.8.4.1, "Generating a Report"
■
Section E.8.4.2, "Generating a Report Version"
■
Section E.8.4.3, "Generating Reports by System Code"
E.8.4.1 Generating a Report
Use this procedure to generate a report:
E-18 HTML Server on WebSphere Reference Guide
Generating Other Selected Objects
1.
From the pull-down menu, select Generate > Reports.
2.
Enter the name of a report, (for example, R0006P).
3.
Click the Start button.
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>%';
E.8.4.2 Generating a Report Version
Use this procedure 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 the Start button.
The Generator generates the version and any dependent objects.
4.
Check the status log for the generation status.
E.8.4.3 Generating Reports by System Code
Use this procedure 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 the Start button.
Generating JD Edwards EnterpriseOne Serialized Objects
E-19
Generating Other Selected Objects
The 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.
E.8.5 Generating NERs
Use this procedure to generate NERs:
1.
From the pull-down menu, select Generate > NERs.
2.
Enter the name of an NER, for example, GetObjectDesc.
Note:
The names of NERs are case sensitive.
3.
Click the Start button.
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>'
E.8.6 Generating Data Dictionary Items
Use this procedure to generate Data Dictionary items:
1.
From the pull-down menu, select Generate > Data Dictionary.
2.
Generate any data dictionary item, for example, OBNM.
E-20 HTML Server on WebSphere Reference Guide
Generating Other Selected Objects
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>';
E.8.7 Generating Tables
Use this procedure to generate tables:
1.
From the pull-down menu, select Generate > Tables.
2.
Enter a table number, for example, F9860.
3.
Click the Start button.
The eGenerator generates the table and all data dictionary items used by the table.
4.
Check the status log for the generation status.
E.8.8 Generating Business Views
Use this procedure to generate business views:
1.
From the pull-down menu, select Generate > Business Views.
2.
Enter the name of a business view, for example, V9001B.
3.
Click the Start button.
Generating JD Edwards EnterpriseOne Serialized Objects
E-21
Generating Other Selected Objects
The eGenerator generates the View and all associated tables and data dictionary
items.
4.
Check the status log for the generation status.
E.8.9 Generating Data Structures
Use this procedure 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>'
E-22 HTML Server on WebSphere Reference Guide
Download PDF