[1]
JD
Edwards World
Web Enablement Installation and Configuration Guide
Release A9.4
E58800-01
April 2015
Describes how to install and configure JD Edwards World
Web Enablement and the Windows Client.
JD Edwards World Web Enablement Installation and Configuration Guide, Release A9.4
E58800-01
Copyright © 2015, 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......................................................................................................................................................
Documentation Accessibility ....................................................................................................................
Related Information ...................................................................................................................................
Conventions ................................................................................................................................................
vii
vii
vii
vii
1 Overview
2 Preinstallation Conditions
3 Install or Upgrade the Seagull License and Message Server
3.1
3.2
3.3
Step 1 - Install or Upgrade the Seagull License and Message Server.................................. 3-1
Step 2 - Obtain Authorization Codes ....................................................................................... 3-2
Step 3 - Enter Authorization Codes.......................................................................................... 3-2
4 Deployment Option 1 - Install the LegaSuite Server on IBM i
4.1
4.2
4.3
4.4
4.5
4.6
4.7
Step 1 - Install the Seagull LegaSuite Server ........................................................................... 4-1
Step 2 - Install the JD Edwards World Components for IBM i............................................. 4-7
Step 3 - Upload the Seagull LegaSuite Server and JDE Components to the IBM i......... 4-10
Step 4 - Verify the Seagull LegaSuite Server on IBM i........................................................ 4-11
Step 5 - Verify Seagull License and Message Server on IBM i .......................................... 4-12
Step 6 - Verify the HTTP server on IBM i ............................................................................. 4-12
Step 7 - Connect the Client Browser...................................................................................... 4-12
5 Deployment Option 2 - Install the LegaSuite Server on Windows
5.1
5.2
5.3
5.4
5.5
Step 1 - Install the Seagull LegaSuite Server ........................................................................... 5-1
Step 2 - Install the JD Edwards World Components for Windows ..................................... 5-7
Step 3 - Verify the Seagull LegaSuite Server on Windows ................................................ 5-11
Step 4 - Verify Seagull License and Message Server on IBM i .......................................... 5-11
Step 5 - Connect the Client Browser...................................................................................... 5-11
6 Deployment Option 3 - Install the LegaSuite Client on Windows
6.1
6.2
Step 1 - Install the Seagull LegaSuite Server ........................................................................... 6-1
Step 2 - Install the JD Edwards World Components for Windows ..................................... 6-7
iii
7 Set up Delivery of Reports Using E-mail
7.1
7.2
7.3
7.4
Step 1 - Verify User ID is set up on the IBM i .........................................................................
Step 2 - Set up E-mail Messages from the IBM i.....................................................................
Step 3 - Set up the “From” Address for E-mail Messages.....................................................
Step 4 - Finish Set up ..................................................................................................................
7-1
7-1
7-2
7-2
A Troubleshooting
A.1
A.2
A.3
A.4
A.5
L03 Errors ....................................................................................................................................
J01 and J03 Errors .......................................................................................................................
425 NOT ABLE TO OPEN DATA CONNECTION ..............................................................
Window Server Timeout Issue.................................................................................................
Wrong Images Displayed .........................................................................................................
A-1
A-1
A-1
A-1
A-2
B Alternate Language Special Install Instructions
C Package Files
C.1
C.2
Controlling the Order in which .LWR Files are Accessed ................................................... C-1
Adding or Replacing Custom Images..................................................................................... C-2
D WRKSPLF Printing
E Attachment Link Access
F Calculator Access
G Double byte
G.1
G.2
For Windows Server Install ...................................................................................................... G-1
For IBM i Server Install ............................................................................................................. G-1
H Customized Signon
I Registration Wizard
I.1
I.2
Setting Up the Registration Wizard for IBM i Server ............................................................. I-1
Setting Up the Registration Wizard for Windows Servers .................................................... I-5
J Activating Sign off Button on Menu Panels
K JD Edwards World Help Menu Integration
K.1
Overview of Help Menu Integration ......................................................................................
K.1.1
Plan for Deploying In-Application Support ...................................................................
K.1.1.1
Who Needs to be Involved? .......................................................................................
K.1.1.2
When Does it Have to Happen? ................................................................................
K.1.1.3
What Needs to be Done? ............................................................................................
K.2
JD Edwards World Web Enablement Help Menu Integration............................................
iv
K-1
K-2
K-2
K-2
K-2
K-3
K.2.1
K.2.2
Configure the Text Files..................................................................................................... K-3
Configure the JavaScript File ............................................................................................ K-4
L Restriction of Creation of Virtual Devices
M E-mail Separator Character
N E-mail Special Instructions
O Session Resume
P Parameterized URL
Q Function Keys Case Sensitive
R Action Code Icon Display
S Logo Push Button
T Text File Entry Table
T.1
Text File Entry Table.................................................................................................................. T-1
v
vi
Preface
Welcome to the JD Edwards World Web Enablement Installation and Configuration
Guide.
Audience
This guide is intended for implementers and end users of JD Edwards World Web
Enablement Installation and Configuration.
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 Information
For additional information about JD Edwards World applications, features, content,
and training, visit the JD Edwards World pages on the JD Edwards Resource Library
located at:
http://learnjde.com
Conventions
The following text conventions are used in this document:
Convention
Meaning
boldface
Indicates cautionary information or terms defined in the glossary.
italic
Indicates book titles or emphasis.
vii
viii
1
Overview
1
JD Edwards World Web Enablement web-based user interface is a statement of
Oracle's continued commitment to the JD Edwards World product family. Web
Enablement allows you to extend the advantages realized within your enterprise to
anywhere in the world, at any time, through a simple Internet browser.
This guide explains installation and configuration options and steps for JD Edwards
World Web Enablement and the Windows Client. This includes the JWalk GUI product
from Seagull Software, formerly named LegaSuite. To match the version of the product
JD Edwards World is using, the name LegaSuite is referenced throughout this guide.
To use JD Edwards World Web Enablement, you must first decide whether you want
to run the Seagull LegaSuite Server on the IBM i (Deployment Option 1),
Windows/NT server (Deployment Option 2), or install the LegaSuite Client
(Deployment Option 3). All options are explained in this guide.
Overview 1-1
1-2 JD Edwards World Web Enablement Installation and Configuration Guide
2
Preinstallation Conditions
2
Before you install JD Edwards World Web Enablement, be sure you meet the following
conditions:
■
■
■
You uninstall any previous LegaSuite Server for IBM i V5Rx installations from
your workstation using the Add or Remove Programs from the Control Panel
If you have any Seagull products previously installed on your server or PC, ensure
you have a copy or backup of your folders LEGASRV and JWALK located in the
root directory. This new JD Edwards World Web Enablement install replaces your
current settings files with new versions of the configuration file (LEGASUITE.INI)
and html files
The Web Enablement Java Client requires a running HTTP server
Note: Refer to the JD Edwards World Minimum Technical
Requirements Guide specific to your release level available on My
Oracle Support for hardware and software, which must be installed
prior to this installation.
iSeries-i5, iSeries, and IBM i are referring to the same type of IBM
server machine and are interchangeably used in this documentation.
Preinstallation Conditions
2-1
2-2 JD Edwards World Web Enablement Installation and Configuration Guide
3
Install or Upgrade the Seagull License and
Message Server
3
This chapter contains these topics:
■
Section 3.1, "Step 1 - Install or Upgrade the Seagull License and Message Server,"
■
Section 3.2, "Step 2 - Obtain Authorization Codes,"
■
Section 3.3, "Step 3 - Enter Authorization Codes."
Ensure you complete the following procedures included in this section. Install the
Seagull License and Message Server (LMS) for all deployment options. If the LMS is
already installed, upgrade it to the current version.
Before you Begin
■
Ensure the Seagull License and Message Server (LMS) is not running by typing the
following on the command line:
SEALMS/ENDLMSTCP
■
If you are upgrading an existing LMS, backup the SEALMS library
Note: If you are using the LMS for products other than JD Edwards
World software, it may be necessary to obtain new license codes from
third-party vendors.
■
■
■
If you are upgrading an existing LMS currently at version 4.32 or higher (with the
exception of version 4.33), your existing JD Edwards World Authorization Codes
will continue to be valid; therefore, you can skip the following sections:
■
Obtain Authorization Codes
■
Enter Authorization Codes
If you are upgrading an existing LMS that is currently at a version lower than 4.32,
contact My Oracle Support, JD Edwards World Technical to obtain new
Authorization Codes
Ensure you have a TCP/IP connection to the IBM i on which you are installing the
server, as well as QSECOFR authority
3.1 Step 1 - Install or Upgrade the Seagull License and Message Server
1.
From a PC, double-click the file named SETUP.EXE from the JD Edwards World
LegaSuite Web Enablement download or CD.
Install or Upgrade the Seagull License and Message Server
3-1
Step 2 - Obtain Authorization Codes
2.
From the Web Enablement options menu choose License Server.
3.
Type the TCP/IP Address or IBM i Name in the TCP/IP Address field and type
the QSECOFR password in the Password field. Click OK.
The system automatically uploads and starts the Seagull License and Message Server.
Note: To start the Seagull License and Message Server manually,
type the following on the IBM i command line:
SEALMS/STRLMSTCP
Note: To end the Seagull License and Message Server manually, type
the following on the IBM i command line:
SEALMS/ENDLMSTCP
Note:
If you receive the following error message during installation:
425 NOT ABLE TO OPEN DATA CONNECTION
Refer to Appendix A - Troubleshooting for instructions on how to
resolve this issue. Ensure to rerun the License and Message Server
Installation after resolving this issue.
3.2 Step 2 - Obtain Authorization Codes
Prior to requesting authorization codes, run the License Report (LISTLIC).
1.
From the IBM i command line type:
SEALMS/REPORTLIC
Press Enter.
WRKSPLF
Press Enter.
Save the LISTLIC spooled file to be attached to your Service Request, e.g. Notepad
or PDF.
2.
Open a Service Request (SR) with My Oracle Support, JD Edwards World
Technical under JD Edwards World GUI.
Attach the LISTLIC report to the Service Request (SR) or provide the following
information found in the LISTLIC report.
3.
■
IBM i serial number
■
Logical Partition Number (LPAR)
You receive your authorization codes within 48 hours.
3.3 Step 3 - Enter Authorization Codes
1.
Connect to the IBM i using the LegaSuite connection through a browser.
2.
Signon to the IBM i as QSECOFR.
3-2 JD Edwards World Web Enablement Installation and Configuration Guide
Step 3 - Enter Authorization Codes
3.
From the IBM i command line type, enter:
SEALMS/WRKSEALIC
4.
Select Change Option on the Client Package Type.
5.
Enter the Authorization Code.
Note: You are now ready to access your IBM i applications through
the Web using Seagull LegaSuite.
Install or Upgrade the Seagull License and Message Server
3-3
Step 3 - Enter Authorization Codes
3-4 JD Edwards World Web Enablement Installation and Configuration Guide
4
Deployment Option 1 - Install the LegaSuite
Server on IBM i
4
This chapter contains these topics:
■
Section 4.1, "Step 1 - Install the Seagull LegaSuite Server,"
■
Section 4.2, "Step 2 - Install the JD Edwards World Components for IBM i,"
■
Section 4.3, "Step 3 - Upload the Seagull LegaSuite Server and JDE Components to
the IBM i,"
■
Section 4.4, "Step 4 - Verify the Seagull LegaSuite Server on IBM i,"
■
Section 4.5, "Step 5 - Verify Seagull License and Message Server on IBM i,"
■
Section 4.6, "Step 6 - Verify the HTTP server on IBM i,"
■
Section 4.7, "Step 7 - Connect the Client Browser."
4.1 Step 1 - Install the Seagull LegaSuite Server
1.
From a PC, unzip the file A931WEB.ZIP file into a temporary folder.
2.
From the temporary folder, double-click the file named SETUP.EXE. SETUP.EXE
starts the Options Menu where you can launch the following installations.
3.
From the Setup screen, Installations Options menu, select the LegaSuite Servers
link.
Deployment Option 1 - Install the LegaSuite Server on IBM i 4-1
Step 1 - Install the Seagull LegaSuite Server
Figure 4–1 Install Options screen
4.
From the Setup screen, LegaSuite Servers menu, select the Seagull IBM i (iSeries)
Server link. The setup program launches.
Figure 4–2 LegaSuite Servers screen
5.
From the Welcome screen, click Next.
4-2 JD Edwards World Web Enablement Installation and Configuration Guide
Step 1 - Install the Seagull LegaSuite Server
Figure 4–3 Welcome screen
6.
From the Software License Agreement screen, if you accept the license agreement,
click I Agree.
Figure 4–4 Software License Agreement screen
7.
On the Installation Mode screen. Choose Manual Installation and click Next.
Deployment Option 1 - Install the LegaSuite Server on IBM i 4-3
Step 1 - Install the Seagull LegaSuite Server
Figure 4–5 Installation Mode screen
8.
From the Choose Install Location Screen, accept the default and click Next.
Figure 4–6 Choose Install Location screen
9.
From the Choose Start Menu Folder screen, click Next.
4-4 JD Edwards World Web Enablement Installation and Configuration Guide
Step 1 - Install the Seagull LegaSuite Server
Figure 4–7 Choose Start Menu Folder screen
10. From Installation Settings screen, enter the TCP/IP Address. Enter a User Name
with QSECOFR authority, but do not enter your password on this screen. Accept
the other default values and click Next.
Figure 4–8 Installation Settings screen
11. From the GUI Engine Settings screen, enter your IBM i host address and click
Next.
Deployment Option 1 - Install the LegaSuite Server on IBM i 4-5
Step 1 - Install the Seagull LegaSuite Server
Figure 4–9 GUI Engine Settings screen
12. From the Web Server Settings screen, verify your Domain and click Install.
Figure 4–10
Web Server Settings screen
13. From the Completion screen, click Finish.
4-6 JD Edwards World Web Enablement Installation and Configuration Guide
Step 2 - Install the JD Edwards World Components for IBM i
Figure 4–11
Completion Setup Wizard screen
14. Complete the procedures in Appendix I, "Registration Wizard," and then proceed
to complete Step 2 of the Deployment Option 1, Section 4.2, "Step 2 - Install the JD
Edwards World Components for IBM i".
4.2 Step 2 - Install the JD Edwards World Components for IBM i
1.
From the Setup screen, LegaSuite Servers Menu that you launched in the previous
section, click on the JDE World IBM i Components link.
Figure 4–12
LegaSuite Servers screen
Deployment Option 1 - Install the LegaSuite Server on IBM i 4-7
Step 2 - Install the JD Edwards World Components for IBM i
2.
From the Oracle Universal Installer (OUI) Welcome screen, click Next.
Figure 4–13
3.
Oracle Universal Installer (OUL) Welcome screen
Enter a folder Name for the installation, for example A93WEB and any OraHome
directory and then click Next. Oracle recommends that you retain the OraHome
name in some form for your path directory.
Using the OraHome name is an Oracle convention that facilitates consistent
directory names among Oracle product installations.
Figure 4–14
4.
Choose Destination Directory screen
Accept the default destination directory and then click Next.
4-8 JD Edwards World Web Enablement Installation and Configuration Guide
Step 2 - Install the JD Edwards World Components for IBM i
Figure 4–15
5.
From the Summary screen, click Install.
Figure 4–16
6.
Choose Destination Directory screen
Summary screen
From the End of Installation screen, click Exit.
Deployment Option 1 - Install the LegaSuite Server on IBM i 4-9
Step 3 - Upload the Seagull LegaSuite Server and JDE Components to the IBM i
Figure 4–17
7.
End of Installation screen
From the Exit screen, click Yes.
Figure 4–18
Exit screen
4.3 Step 3 - Upload the Seagull LegaSuite Server and JDE Components
to the IBM i
The first part of the IBM i installation is complete. Now you need to upload the Seagull
LegaSuite Server and the JDE Components to your IBM i using the Seagull FTP
Wizard.
1.
To start the FTP upload to the IBM i, run the following program from the
Windows Start Menu:
Start Menu->Programs->LegaSuite->LegaSuite GUI Engine for IBM i ->6.xxxx.x.xx
->LegaSuite GUI Engine for IBM i
2.
From the FTP Connection settings screen, ensure you have QSECOFR authority to
start the IBM i install. Click OK.
4-10 JD Edwards World Web Enablement Installation and Configuration Guide
Step 4 - Verify the Seagull LegaSuite Server on IBM i
Figure 4–19
FTP Connections screen
Note: Depending on your network connections, the install can take
longer than 20 minutes to FTP all the objects to the IBM i.
3.
From the LegaSuite GUI Engine for IBM i installation screen, click OK to complete
the installation.
Figure 4–20
LegaSuite GUI Engine for IBM iSeries Installation screen
Note: If you experience difficulty transferring the objects, contact My
Oracle Support, JD Edwards World Technical for assistance.
Note:
If you receive the following error message during installation:
425 NOT ABLE TO OPEN DATA CONNECTION
Refer to Appendix A - Troubleshooting for instructions on how to
resolve this issue.
4.4 Step 4 - Verify the Seagull LegaSuite Server on IBM i
1.
Ensure the following server is running on your IBM i, by typing:
WRKACTJOB
Subsystem
Server
Description
QSYSWRK
LEGASRVSVR
LegaSuite Server
■
If the LegaSuite Server is not running, start it by typing the following on a
command line:
LEGASRV/STRLEGASRV
Deployment Option 1 - Install the LegaSuite Server on IBM i
4-11
Step 5 - Verify Seagull License and Message Server on IBM i
4.5 Step 5 - Verify Seagull License and Message Server on IBM i
Note: This step assumes you have previously installed the Seagull
License and Message server. If you have not, follow the instructions in
the section Install or Upgrade the Seagull License and Message Server.
1.
Ensure the following servers are running on your IBM i, type the following on the
IBM i command line:
WRKACTJOB
Subsystem
Server
Description
QSYSWRK
SEALMSDMN
License Message Server
QSYSWRK
SEALMSSVR
License Message Server
2.
If the License Message Server is not running, start it by typing the following on the
IBM i command line:
SEALMS/STRLMSTCP
4.6 Step 6 - Verify the HTTP server on IBM i
1.
Ensure the following server is running on your IBM i, type the following on the
IBM i command line:
WRKACTJOB
Subsystem
Server
Description
QHTTPSVR
APACHEDFT
The HTTP Server
2.
If the default HTTP server is not running, start it by typing the following on a
command line:
STRTCPSVR SERVER(*HTTP) HTTPSVR(APACHEDFT)
4.7 Step 7 - Connect the Client Browser
1.
Use a web browser to launch Web Enablement.
2.
Type the following URL in the web browser and press Enter.
http://your_IBM i/legasuite/LEGASUITE.HTML
Note: Ensure you replace the text IBM i with the name used for your
IBM i, as specified during the install.
4-12 JD Edwards World Web Enablement Installation and Configuration Guide
5
Deployment Option 2 - Install the LegaSuite
Server on Windows
5
This chapter contains these topics:
■
Section 5.1, "Step 1 - Install the Seagull LegaSuite Server."
■
Section 5.2, "Step 2 - Install the JD Edwards World Components for Windows,"
■
Section 5.3, "Step 3 - Verify the Seagull LegaSuite Server on Windows,"
■
Section 5.4, "Step 4 - Verify Seagull License and Message Server on IBM i,"
■
Section 5.5, "Step 5 - Connect the Client Browser."
5.1 Step 1 - Install the Seagull LegaSuite Server
1.
From a PC, unzip the file A93WEB.ZIP file into a temporary folder.
2.
From the temporary folder, double-click the file named SETUP.EXE. SETUP.EXE
starts the Options Menu where you can launch the following installations.
3.
From the Setup screen, Installations Options menu, select the LegaSuite Servers
link.
Deployment Option 2 - Install the LegaSuite Server on Windows
5-1
Step 1 - Install the Seagull LegaSuite Server
Figure 5–1 Installation Options screen
4.
From the Setup screen, LegaSuite Servers menu, select the Seagull Windows
Server link.
Figure 5–2 LegaSuite Servers screen
5.
From the Welcome screen, click Next
5-2 JD Edwards World Web Enablement Installation and Configuration Guide
Step 1 - Install the Seagull LegaSuite Server
Figure 5–3 Welcome screen
6.
From the Software License Agreement screen, if you accept the license agreement,
click I Agree.
Figure 5–4 Software License Agreement screen
7.
From the Choose Components screen expand Client Types and deselect HTML
Clients.
Deployment Option 2 - Install the LegaSuite Server on Windows
5-3
Step 1 - Install the Seagull LegaSuite Server
Figure 5–5 Choose Components screen
8.
Accept the default location and copy this location for use later in the install.
C:\Program Files\SEAGULL\LegaSuite GUI Engine for 32-bit\6.1859.1.82\
Figure 5–6 Choose Install Location screen
9.
In the Host Settings section, in the Address: field enter the IBM i name or IP
Address.
The default Port: setting is 23.
Leave the Working Directory: field in the Server Settings section blank.
The default Server Port: is 1289.
5-4 JD Edwards World Web Enablement Installation and Configuration Guide
Step 1 - Install the Seagull LegaSuite Server
Figure 5–7 Configuration screen
10. For Webroot: enter your Apache webserver root folder then type in a subfolder of
legasuite.
For Domain: enter the domain name with legastuite subfolder at the end.
Uncheck the Restart IIS to apply configuration changes checkbox.
A message asks to create the legasuite subfolder, click Yes.
Figure 5–8 Configuration (Webroot) screen
Figure 5–9 Create LegaSuite Subfolder screen
11. On the Java Client screen, check if last two subfolders in the path for the Path: and
URL: fields end in \legasuite\java. If not, manually add \legasuite\java at the
end.
Deployment Option 2 - Install the LegaSuite Server on Windows
5-5
Step 1 - Install the Seagull LegaSuite Server
Figure 5–10
Java Client screen
12. No changes need to be made on the ActiveX Client screen. Click Next.
Figure 5–11
ActiveX Client screen
13. On the Choose Start Menu Folder screen, click Install to begin the installation.
5-6 JD Edwards World Web Enablement Installation and Configuration Guide
Step 2 - Install the JD Edwards World Components for Windows
Figure 5–12
Choose Start Menu Folder screen
14. On the Completion screen, ensure the Run Registration Wizard checkbox is
checked. Click Finish and follow the steps in Appendix I - Registration Wizard.
Once completed, proceed with Step 2 – Install the JD Edwards World Components
for Windows.
Figure 5–13
InstallShield Wizard Completed screen
Note: If you miss step 14, you can access the same Registration
Wizard through the LegaSuite Registration Wizard link from
START>ALL PROGRAMS>LEGASUITE>REGISTRATION WIZARD.
5.2 Step 2 - Install the JD Edwards World Components for Windows
1.
From the LegaSuite Servers menu that you launched in the previous section, click
the JDE World Windows Components link.
Deployment Option 2 - Install the LegaSuite Server on Windows
5-7
Step 2 - Install the JD Edwards World Components for Windows
Figure 5–14
2.
From the Oracle Universal Installer (OUI): Welcome screen, click Next.
Figure 5–15
3.
Installation Options screen
Oracle Universal Installer (OUI) Welcome screen
Enter a folder Name for the installation, for example A93WEB and any OraHome
directory and then click Next. Oracle recommends that you retain the OraHome
name in some form for your path directory.
Using the OraHome name is an Oracle convention that facilitates consistent
directory names among Oracle product installations.
5-8 JD Edwards World Web Enablement Installation and Configuration Guide
Step 2 - Install the JD Edwards World Components for Windows
Figure 5–16
4.
Enter your Apache web server Directory and then click Next.
Figure 5–17
5.
Specify Home Details screen
Choose Web Server Directory screen
From the Summary screen, click Next.
Deployment Option 2 - Install the LegaSuite Server on Windows
5-9
Step 2 - Install the JD Edwards World Components for Windows
Figure 5–18
6.
From the End of Installation, click Exit.
Figure 5–19
7.
Summary screen
End of Installation screen
From the Exit screen, click Yes.
5-10 JD Edwards World Web Enablement Installation and Configuration Guide
Step 5 - Connect the Client Browser
Figure 5–20
Exit screen
5.3 Step 3 - Verify the Seagull LegaSuite Server on Windows
1.
■
From the Windows server, when the LegaSuite Server is running, this icon must
display on your icon tray at the bottom right-hand corner of your screen:
If the icon above does not display, start the LegaSuite Sever:
START>ALL PROGRAMS>LEGASUITE>LEGASUITE GUI ENGINE FOR
32-BIT>6.1859.1.82>LegaSuite GUI Engine for 32-bit
5.4 Step 4 - Verify Seagull License and Message Server on IBM i
Note: This step assumes you have previously installed the Seagull
License and Message server. If you have not, follow the instructions in
the section Install or Upgrade the Seagull License and Message Server.
Ensure the following servers are running on your IBM i, by typing on the IBM i
command line:
WRKACTJOB
Subsystem
Server
Description
QSYSWRK
SEALMSDMN
License Message Server
QSYSWRK
SEALMSSVR
License Message Server
If the License Message Server is not running, start it by typing the following on the
IBM i command line:
SEALMS/STRLMSTCP
5.5 Step 5 - Connect the Client Browser
1.
Start the LegaSuite Server before you connect a web browser to the Java
application.
2.
Type the following URL in the web browser and press Enter.
http://your_Windows_server/legasuite/
Note: Ensure you replace the text your_Windows_server with the
name used for your Windows server, as specified during the install.
Deployment Option 2 - Install the LegaSuite Server on Windows
5-11
Step 5 - Connect the Client Browser
5-12 JD Edwards World Web Enablement Installation and Configuration Guide
6
Deployment Option 3 - Install the LegaSuite
Client on Windows
6
This chapter contains these topics:
■
Section 6.1, "Step 1 - Install the Seagull LegaSuite Server,"
■
Section 6.2, "Step 2 - Install the JD Edwards World Components for Windows."
This is a client install provided for both single and double-byte installs.
6.1 Step 1 - Install the Seagull LegaSuite Server
1.
From a PC, unzip the file A931WEB.ZIP file into a temporary folder.
2.
From the temporary folder, double-click the file named SETUP.EXE. SETUP.EXE
starts the Options Menu where you can launch the following installations.
3.
From the Setup screen, Installations Options menu, select the LegaSuite Servers
link.
Figure 6–1 Installation Options screen
Deployment Option 3 - Install the LegaSuite Client on Windows
6-1
Step 1 - Install the Seagull LegaSuite Server
4.
From the Setup screen, LegaSuite Servers menu, select the Seagull Windows
Server link.
Figure 6–2 LegaSuite Servers screen
5.
From the Welcome screen, click Next.
Figure 6–3 Welcome screen
6.
From the Software License Agreement screen, if you accept the license agreement
click I Agree.
6-2 JD Edwards World Web Enablement Installation and Configuration Guide
Step 1 - Install the Seagull LegaSuite Server
Figure 6–4 License Agreement screen
7.
From the Choose Components screen expand Client Types and deselect HTML
Clients.
Figure 6–5 Choose Components screen
8.
Accept the default location and copy this location for use later in the install.
C:\Program Files\SEAGULL\LegaSuite GUI Engine for 32-bit\6.1859.1.82\
Deployment Option 3 - Install the LegaSuite Client on Windows
6-3
Step 1 - Install the Seagull LegaSuite Server
Figure 6–6 Choose Install Location screen
9.
In the Host Settings section, in the ‘Address:’ field enter the IBM I name or IP
Address.
The default Port: setting is 23.
Leave the Working Directory: field in the Server Settings section blank.
The default Server Port: is 1289.
Figure 6–7 Configuration screen
10. For Webroot: enter your Apache webserver root folder then type in a subfolder of
legasuite.
For Domain: enter the domain name with legastuite subfolder at the end. Uncheck
the Restart IIS to apply configuration changes checkbox.
The screen is for IIS, but we assume that Apache HTTP is being used on a user’s
machine.
6-4 JD Edwards World Web Enablement Installation and Configuration Guide
Step 1 - Install the Seagull LegaSuite Server
Figure 6–8 Configuration (Webroot) screen
A message asks to create the legasuite subfolder, click Yes.
Figure 6–9 Create LegaSuite Subfolder screen
11. On the Java Client screen, ensure the last two subfolders in the path for the Path:
and URL: fields end in \legasuite\java
Figure 6–10
Java Client screen
12. No changes need to be made on the ActiveX Client screen. Click Next.
Deployment Option 3 - Install the LegaSuite Client on Windows
6-5
Step 1 - Install the Seagull LegaSuite Server
Figure 6–11
ActiveX Client screen
13. On the Choose Start Menu Folder screen click Install to begin the installation.
Figure 6–12
Choose Start Menu Folder screen
14. On the Completion screen, ensure the Run Registration Wizard checkbox is
checked. Click Finish and follow the steps in Appendix I - Registration Wizard.
Once completed, proceed with Step 2 – Install the JD Edwards World Components
for Windows.
6-6 JD Edwards World Web Enablement Installation and Configuration Guide
Step 2 - Install the JD Edwards World Components for Windows
Figure 6–13
Completion Setup Wizard screen
Note: If you miss step 14, you can access the same Registration
Wizard through the LegaSuite Registration Wizard link from
START>ALL
PROGRAMS>LEGASUITE>LEGASUITELEGASUITEREGISTRATIO
N WIZARD.
6.2 Step 2 - Install the JD Edwards World Components for Windows
1.
From the LegaSuite Servers menu that you launched in the previous section, click
the JDE World Windows Components link.
Figure 6–14
2.
Installation Options screen
From the Oracle Universal Installer (OUI): Welcome screen, click Next.
Deployment Option 3 - Install the LegaSuite Client on Windows
6-7
Step 2 - Install the JD Edwards World Components for Windows
Figure 6–15
3.
Oracle Universal Installer (OUI) screen
Enter a folder Name for the installation, for example A93WEB and any OraHome
directory and then click Next. Oracle recommends that you retain the OraHome
name in some form for your path directory.
Using the OraHome name is an Oracle convention that facilitates consistent
directory names among Oracle product installations.
Figure 6–16
4.
Specify Home Details screen
Enter your Apache web server Directory and then click Next.
6-8 JD Edwards World Web Enablement Installation and Configuration Guide
Step 2 - Install the JD Edwards World Components for Windows
Figure 6–17
5.
From the Summary screen, click Next.
Figure 6–18
6.
Choose Web Server Directory screen
Summary screen
From the End of Installation screen, click Exit.
Deployment Option 3 - Install the LegaSuite Client on Windows
6-9
Step 2 - Install the JD Edwards World Components for Windows
Figure 6–19
7.
From the Exit screen, click Yes.
Figure 6–20
8.
End of Installation screen
Exit screen
Using Windows Explorer open the folder:
C:\Program Files\SEAGULL\LegaSuite GUI Engine for 32-bit\6.1859.1.82
9.
Find the file legaclt.exe (program type application) and right-click to display
options.
Select Send To, and then select Desktop create shortcut.
10. A new icon is created on the Desktop; right-click the new icon to access the
Properties.
Figure 6–21
Shortcut to legaclt.exe
6-10 JD Edwards World Web Enablement Installation and Configuration Guide
Step 2 - Install the JD Edwards World Components for Windows
Figure 6–22
Shortcut to legaclt.exe Properties screen
11. Enter a space and the text /eA91App in the Target input field after the last
character on the line. Click OK to save your changes.
12. Double-click the new icon to access the A91 Web Enablement client installation.
Note: To upgrade the A93 Web Enablement Client for Windows,
contact My Oracle Support, JD Edwards World Technical prior to
altering the current configuration.
Deployment Option 3 - Install the LegaSuite Client on Windows 6-11
Step 2 - Install the JD Edwards World Components for Windows
6-12 JD Edwards World Web Enablement Installation and Configuration Guide
7
Set up Delivery of Reports Using E-mail
7
This chapter contains these topics:
■
Section 7.1, "Step 1 - Verify User ID is set up on the IBM i,"
■
Section 7.2, "Step 2 - Set up E-mail Messages from the IBM i,"
■
Section 7.3, "Step 3 - Set up the “From” Address for E-mail Messages,"
■
Section 7.4, "Step 4 - Finish Set up."
A set up is required to ensure the successful delivery of reports through e-mail.
Appropriate IBM i authority is required to set up e-mail availability.
7.1 Step 1 - Verify User ID is set up on the IBM i
1.
From the IBM i command line, type the following command:
WRKDIRE USER (Web Enablement User ID)
Where Web Enablement User ID is the User ID of the user you wish to set up on
IBM i e-mail.
2.
Press Enter.
If the following error message displays:
User not enrolled in system distribution directory.
Proceed to Step 2 - Set up E-mail Messages from the IBM i.
If no error message displays, then proceed to Step 3 - Set up the “From” Address
for E-mail Messages.
7.2 Step 2 - Set up E-mail Messages from the IBM i
1.
Create authority for the Web Enablement User ID on the IBM i. From the IBM i
command line, type the following commands:
ADDDIRE USRID(E-mail User ID My_IBM i) USRD('User Name') USER(User ID)
Where My_IBM i is the IBM i machine name and E-Mail User ID is the new E-mail
directory User ID and User ID is the Web Enablement User ID.
2.
Execute the following two statements, once, on the IBM i:
ADDDIRE USRID(INTERNET GATEWAY) USRD('Allow OS/400 to send
INTERNET Mail') SYSNAME(INTERNET) MSFSRVLVL(*USRIDX)
PREFADR(NETUSRID *IBM ATCONTXT)
Set up Delivery of Reports Using E-mail
7-1
Step 3 - Set up the “From” Address for E-mail Messages
CHGDSTA SMTPRTE(INTERNET GATEWAY)
7.3 Step 3 - Set up the “From” Address for E-mail Messages
The following steps set up the “From” address for e-mail messages sent from Web
Enablement. Ensure the “From” address is set to a valid address that gets through the
firewall issues when sending e-mail message to outbound source.
1.
If a User ID existed from the verification above, proceed to Step 4 - Finish set up to
continue with setup. Otherwise, on the IBM i command line, type the following
command:
WRKDIRE USRID (E-mail User ID My_IBM i)
Where My_IBM i is the IBM i machine name and E-mail User ID is the new E-mail
directory User ID.
2.
Press Enter.
3.
Type 2 on the line that has the user profile set up for Web Enablement. Press Enter.
Figure 7–1 Add Name for SMTP
4.
Press F19 and then press Enter.
5.
Complete the following fields with the respective portions of the e-mail address.
■
SMTP User ID…………..John_Doe
■
SMTP Domain………….companyname.com
Example of From e-mail address:
John_Doe@companyname.com
6.
Press Enter until return to main menu.
7.4 Step 4 - Finish Set up
1.
If you have a firewall and/or a mail proxy, type the following on the OS/400
command line:
CHGSMTPA MAILROUTER(MAIL.ROUTER.NAME) FIREWALL(*YES)
2.
Ensure that MAIL.ROUTER.NAME is in the AS/400 Host Table (CFGTCP, Option
10) or can be resolved via your Name Server (DNS).
7-2 JD Edwards World Web Enablement Installation and Configuration Guide
Step 4 - Finish Set up
After all configurations are complete, proceed to step 3 below.
3.
From the IBM i command line, type the following:
ENDTCPSVR *SMTP
Press Enter.
4.
From the IBM i command line, type the following:
ENDMSF
Press Enter.
5.
On the IBM i command line, type the following:
STRTCPSVR *SMTP
Press Enter.
6.
On the IBM i command line, type the following:
STRMSF
Press Enter.
7.
On the IBM i command line, type the following:
WRKACTJOB SBS(QSYSWRK)
Press Enter.
8.
Verify the following results:
■
3 jobs named QMSF running
■
A job named QTSMTPBRCL running
■
A job named QTSMTPBRSR running
■
A job named QTSMTPCLNT running
■
A job named QTSMTPSRVR running
Note: If e-mail does not work after following the above instructions
above, you can do some preliminary troubleshooting by looking at the
job logs for QMSF and for QTSMTPBRSR, QTSMTPBRCL,
QTSMTPCLNT, and QTSMTPSRVR. If any of these jobs is not
running, check the job logs.
Most error messages found in those logs have a workable recovery procedure or
lead to a PTF.
9.
Create a folder on the IBM i. Type in the following command on the IBM i:
CRTFLR FLR(My_Folder) TEXT('Folder_Description')
Where My_Folder is the IBM i IFS Folder Name and Folder_Description is the
description of the folder.
To return to the User Options menu, press Enter.
10. To grant authority for your folder, type the following on a command line on the
IBM i:
WRKFLR My_Folder
Option 14 for authority change Public to *ALL.
Set up Delivery of Reports Using E-mail
7-3
Step 4 - Finish Set up
11. Verify the appropriate text file entry is set accordingly on the WV93.LWM and
DYNBLD93.LWM.
Use a text editor tool such as MS Notepad or MS WordPad to open the
WV93.LWM and DYNBLD93.LWM files.
The following are example paths for location of WV93.LWM and
DYNBLD93.LWM.
For IBM i Installation:
■
Your IBM i root folder /LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows
Installations:
■
C:\Inetpub\wwwroot\JWALKAPP\A93APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
■
SNDDSTFLR set to name of My_Folder
7-4 JD Edwards World Web Enablement Installation and Configuration Guide
A
Troubleshooting
A
This appendix contains these topics:
■
Section A.1, "L03 Errors,"
■
Section A.2, "J01 and J03 Errors,"
■
Section A.3, "425 NOT ABLE TO OPEN DATA CONNECTION,"
■
Section A.4, "Window Server Timeout Issue,"
■
Section A.5, "Wrong Images Displayed."
A.1 L03 Errors
Solution - Start the License and Message Server on the IBM i.
From a command line, type SEALMS/STRLMSTCP to start the LMS. If you have not
installed LMS then refer to the Installing the License and Message Server section in
this guide.
If this does not fix the issue, refer to My Oracle Support.
A.2 J01 and J03 Errors
To troubleshoot most errors, refer to My Oracle Support.
A.3 425 NOT ABLE TO OPEN DATA CONNECTION
If you receive the error above during installation, open the file INSTFTP.txt and add a
semicolon ';' in front of the following two lines. The following example displays the
lines with the semicolon added:
; LIT=RCMD DLTF FILE(QTEMP/QREXSRC)
; LIT=RCMD DLTF FILE(QTEMP/JWKTEMP)
A.4 Window Server Timeout Issue
The session is timing out when the screen is inactive over a short period of time.
Solution - Change the timeout settings by going to Start | Control Panel |
Administration | Internet Service Manager and then from the Internet Information
Services screen right-click Default Web Site for properties.
Troubleshooting A-1
Wrong Images Displayed
To select properties:
■
From the Default Web Site Properties screen, select the Home Directory tab and
then select Configuration.
■
From the Application Configuration screen, select the App Options tab where the
Session timeout value can be adjusted.
A.5 Wrong Images Displayed
If the system displays wrong images, such as old PeopleSoft images instead of Oracle
images, you need to delete cached files from Microsoft Internet Explorer.
To delete cached files:
■
Open a new session of Internet Explorer.
■
Click Tools from the menu bar.
■
Select Internet Options…
■
Click Delete Files… on the General Tab.
■
Click OK.
A-2 JD Edwards World Web Enablement Installation and Configuration Guide
B
Alternate Language Special Install Instructions
B
Several LegaSuite components, such as button text and hover help text, can be
translated to other languages. The translation does not require that you have the
LegaSuite Developer. The WV93.LWM and DYNBLD93.LWM text files have different
language translations.
The following are example paths for location of WV93.LWM and DYNBLD93.LWM:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/Translation Text Files
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations,
copy to the following folder:
■
C:\Inetpub\wwwroot\JWALKAPP\A93APP\Translation Text Files
To reference the WV93.LWM and DYNBLD93.LWM text files, you need to set up a new
instance of the LegaSuite Server and then copy the text files WV93_ccc.LWM and
DYNBLD93_ccc.LWM to the new LegaSuite Server instance located with the LWR and
LWX files.
The ccc is the three-character name for the respective language. Delete the existing
WV93.LWM and DYNBLD93.LWM files and rename the _ccc files without the _ccc.
In addition, based on the language you want to display, you may need to change the
CCSID parameter for that group in the LEGASUITE.INI file and, you may need to edit
the value of a parameter in LEGASUITE.HTML file. Contact the My Oracle Support,
JD Edwards World Technical for more information.
Users who need the translated text, must sign in using a URL, which points to this
instance of the LegaSuite Server.
Alternate Language Special Install Instructions
B-1
B-2 JD Edwards World Web Enablement Installation and Configuration Guide
C
Package Files
C
This appendix contains these topics:
■
Section C.1, "Controlling the Order in which .LWR Files are Accessed,"
■
Section C.2, "Adding or Replacing Custom Images."
The following is a list of package files to be installed on either a Windows NT Server or
the IBM i:
■
.LWR
Compiled panel file (or package file) that contains all the GUI panels that display
at runtime.
■
.LWM
External text file that contains text references that are referenced from compiled
application panels.
■
.LWC
Control file used to handle .LWR sequencing and automatically update .LWR files
based on date stamp.
■
Graphics files (.JPG, .GIF)
Graphics used in GUI panels or referenced individually.
■
.INI
Configuration settings such as host session address, router, emulator, automatic
signon, dynamic transformation. They are edited when you run the Configuration
Assistant and referenced using the / parameter in the Target field of the Client
shortcut properties.
C.1 Controlling the Order in which .LWR Files are Accessed
If you have created your own custom .LWR panel files, you can use a control file
(.LWC) to control the order in which these files are accessed.
If you deploy more than one .LWR panel file, they are accessed in reverse-alphabetical
order. For example, if you have three files (apples.LWR, bananas.LWR, and
oranges.LWR) in your A91APP directory, application accesses oranges first, then
bananas, then apples. If you want to have more control over the order in which these
files are accessed:
■
Use a control file (.LWC) to manage your compiled panel files. Use the Runtime=
parameter to specify runtime package files that must be accessed at runtime to
display GUI panels instead of host screens. For example:
Package Files C-1
Adding or Replacing Custom Images
■
Runtime=APPLES.LWR
■
Runtime=ORANGES.LWR
■
Runtime=BANANAS.LWR
In this example, the APPLES.LWR is searched first for the panel that matches the
current host screen. If a matching panel is found, it is displayed. If not, the next
file, ORANGES.LWR, is searched and so forth.
C.2 Adding or Replacing Custom Images
If you have any custom images to add or replace, copy the images to the following
folder. For the BKGRD2.jpg and BKGRD3.jpg images, the size is 784 by 550 pixels.
For IBM i Installation prior to uploading, copy your custom images into the following
path on the installation PC:
■
C:\Program Files\SEAGULL\LegaSuite Server for IBM i
V5Rx\4.1xxx.x.xxx\bin\jwalk\JWALKAPP\A9100App\Images
For IBM i Installation after uploading, copy your custom images into the following
path on the IBM i:
■
Your IBM i root folder/LEGASUITE/A93App/Images
For Windows NT-2000-2003 Server and LegaSuite Client on Windows Installations,
copy to the following folder:
■
C:\Inetpub\wwwroot\JWALKAPP\A93App\Images
C-2 JD Edwards World Web Enablement Installation and Configuration Guide
D
WRKSPLF Printing
D
The ability to print a WRKSPLF entry was added to JD Edwards World Web
Enablement. To have this process work correctly when you click print icon on the
WRKSPLF or WRKSBMJOB panels, some setup is required.
To print WRKSPLF entries, the administrator installing the JD Edwards World Web
Enablement needs to verify that the appropriate text file entry is set accordingly on the
WV93.LWM and DYNBLD93.LWM files.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
The following are example paths for location of WV93.LWM and DYNBLD93.LWM:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\JWALKAPP\A9100APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
MASTSSURL set to the appropriate path for the type of install:
■
If NT Java Client, http://<PC server name>
■
If Native Java Client install, http://IBM i machine name
■
If LegaSuite Client on Windows install, http://<PC Server name>
ERMURL set to the appropriate path for the type of install for Web Enablement:
■
If NT Java Client, http://<PC server name>
■
If Native Java Client install, http://IBM i machine name
■
If LegaSuite Client on Windows install, http://<PC Server name>
INSTALL and ERMPRTURL default is WAS for a Native Java Client. If NT Java Client,
this value must be changed to NT. If LegaSuite Client on Windows, this value must be
changed to WIN.
WRKSPLF Printing D-1
Note: When you attach a WRKSPLF (work spool file) to an electronic
message (e-mail), there are size limitations for the WRKSPLF.
The system uses the IBM i e-mail messaging process to include the
WRKSPLF as an attachment to the e-mail.
When the WRKSPLF is converted to a .TXT file, there is a size
limitation. The IBM i e-mail messaging works for reports less than 30
pages.
In addition, if the WRKSPLF report to be printed is more than 132 characters wide, the
user needs to change the Scaling before printing to print at less than 100% and to print
as a landscape display. This applies to the NT Java Client, LegaSuite Client for
Windows, and Native Java Client WRKSPLF print.
D-2 JD Edwards World Web Enablement Installation and Configuration Guide
E
Attachment Link Access
E
JD Edwards World added the ability to access URL addresses, documents, and an
Email to Web Enablement. You have two different ways to access these Attachment
Links.
■
■
You use the Header Links at the top of each main panel.
You use a right-click within an input capable field that is 20 characters or more in
length.
You need to change the setup to have this work correctly when you click on a Header
Link or right-click within an input capable field on a panel.
To access this required setup process, the administrator installing the JD Edwards
World Web Enablement needs to verify that the appropriate text file entries are set
accordingly on the WV93.LWM and DYNBLD93.LWM files.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
The following are example paths for location of WV93.LWM and DYNBLD93.LWM:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\JWALKAPP\A9100APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
DYNBLDURL and ERMSSURL set to the appropriate path for the type of install:
■
If NT Java Client, http://<PC server name>/Docs/
■
If Native Java Client install, http://IBM i machine name/Docs/
■
If LegaSuite Client for Windows, http://<PC servername>/Docs/
■
SAMPLE.PDF
Note: The document, SAMPLE.PDF, must be included in the Docs
folder within your install.
For the first Header Link button:
■
OTHTEXT1 set to the text displayed (e.g. URL)
■
OTHPATH1 set to the path of the URL, Document, or Email (e.g. www.oracle.com)
Attachment Link Access
E-1
■
OTHTYP1 set to the attachment type of URL, Document, or E-mail (e.g. URL),
available choices are:
URL for a URL address
EML for an E-mail
DOC for a file with an extension of .doc
To use the following three attachment types, the files to be accessed have to be added
to the Docs folder on the LegaSuite Server. In addition, using any one of these three
attachment types requires the OTHPATHx to contain only the file name (e.g.
SAMPLE.PDF).
EXC for a file with an extension of .xls
PDF for a file with an extension of .pdf
EXE for a file with an extension of .exe
Copy any one of these files into the following folder:
For IBM i Installation:
www/<HTTP server>, such as apachedft/htdocs/Docs/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
C:\Inetpub\wwwroot\Docs\
However, a file with extension .xls, .pdf, or .exe can also be accessed using a URL or
DOC attachment type and does not have to be added to the Docs folder on the
LegaSuite Server. This allows access to a file on a PC that does not contain a LegaSuite
Server.
For the URL file type, the OTHPATHx path is:
· http://<Computer Name or IP Address of PC>/<folder path to file>/<File name>
For the Doc file type, the path is:
· file://<Computer Name or IP Address of PC>/<folder path to file>/<File name>
Or
· http://<Computer Name or IP Address of PC>/<folder path to file>/<File name>
Note: For file extensions of .doc, .xls, .pdf, or .exe where these files are not within the
LegaSuite Server Docs folder, verify shared permission is set up for file accessibility.
For the second Header Link button:
■
OTHTEXT2 set to the text displayed (e.g. Document)
■
OTHPATH2 set to the path of the URL, Document, or Email (e.g. SAMPLE.PDF)
■
OTHTYP2 set to the attachment type of URL, Document, or E-mail (e.g. PDF); see
available choices under OTHTYP1 above.
For the third Header Link button:
■
■
OTHTEXT3 set to the text displayed (e.g. Email)
OTHPATH3 set to the path of the URL, Document, or Email (e.g.
World.Web.Enablement@domain.com&subject=Test of EMALSEP&body=insert
body of text here, where & is the e-mail parameter character for the respective
e-mail client)
E-2 JD Edwards World Web Enablement Installation and Configuration Guide
■
OTHTYP3 set to the attachment type of URL, Document, or E-mail (e.g. EML); see
available choices under OTHTYP1 above.
For the fourth Header Link button:
■
■
■
OTHTEXT4 set to the text displayed (e.g. World Resources)
OTHPATH4 set to the path of the URL, Document, or Email (e.g.
https://metalink3.oracle.com/od/faces/index.jspx)
OTHTYP4 set to the attachment type of URL, Document, or E-mail (e.g. URL); see
available choices under OTHTYP1 above.
For the fifth Header Link button:
■
■
■
OTHTEXT5 set to the text displayed (e.g. Support)
OTHPATH5 set to the path of the URL, Document, or Email (e.g.
http://support.oracle.com)
OTHTYP5 set to the attachment type of URL, Document, or E-mail (e.g. URL); see
available choices under OTHTYP1 above.
For the Text display for the right-click drop down:
■
■
OTHTEXT7 set to the text displayed for URL or Email access (e.g. URL
Open/Email)
OTHTEXT8 set to the text displayed for Document access (e.g. Document).
Attachment Link Access
E-3
E-4 JD Edwards World Web Enablement Installation and Configuration Guide
F
Calculator Access
F
To use the calculator within JD Edwards World Web Enablement, CALC.EXE must be
retrieved from any PC and be placed within the Deployment area of the LegaSuite
Server or Client. The executable file, CALC.EXE, is retrieved from any PC in either
C:\WINNT\system32 or C:\WINDOWS\system32 or wherever your Windows
Operating System files are. Copy this file into the following folder.
For IBM i Installation:
■
www/<HTTP server>, such as apachedft/htdocs/Docs/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\Docs\
To access the calculator, the administrator installing the JD Edwards World Web
Enablement needs to verify that the appropriate text file entry is set accordingly on the
WV93.LWM and DYNBLD93.LWM files.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
Example paths for location of WV93.LWM and DYNBLD93.LWM are:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\ JWALKAPP\A9100APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
CALCEXEPTH set to the appropriate path for the type of install:
■
If NT Java Client, http://<PC server name>/Docs/
■
If Native Java Client install, http://IBM i machine name/Docs/
■
If LegaSuite Client for Windows, http://<PC servername>/Docs/
OTHPATH6 set to name of file to open (e.g. calc.exe)
OTHTEXT6 set to text that displays when right click on an input capable field (e.g.
Calculator)
OTHTYP6 set to type of file to open (e.g. EXE)
Users can access an input capable field on a panel display, right-click and choose
Calculator from the drop-down menu.
Calculator Access F-1
F-2 JD Edwards World Web Enablement Installation and Configuration Guide
G
Double byte
G
This appendix contains these topics:
■
Section G.1, "For Windows Server Install,"
■
Section G.2, "For IBM i Server Install."
G.1 For Windows Server Install
1.
Stop LegaSuite server if it is running. Use a text editor tool such as MS Notepad or
MS WordPad to open the LEGASUITE.INI file, located in the following folder:
C:\Program Files\SEAGULL\LegaSuite Server\4.1xxx.xxxx
2.
In [A93APP] section, change the value of CCSID parameter from 500 to the
appropriate values (i.e. 930 for Japanese, 933 for Korean, 927 for Traditional
Chinese, or 926 for Simplified Chinese).
3.
Use a text editor tool, such as MS Notepad or MS WordPad to open
LEGASUITE.HTML file, located in the following folder:
C:\Inetpub\wwwroot
4.
Change the value of the parameter for 'FontUsage' from 2 to 0. Example of the
value of the parameter after your change:
"theApplet.addParameter('FontUsage', '0')"
G.2 For IBM i Server Install
1.
Stop LegaSuite server if it is running. Open LEGASUITE.INI file located in the
following IFS directory path:
\root\LEGASRV
2.
In [A91APP] section, change the value of CCSID parameter from 500 to the
appropriate values (i.e. 930 for Japanese, 933 for Korean, 927 for Traditional
Chinese, or 926 for Simplified Chinese).
3.
Use a text editor tool, such as MS Notepad or MS WordPad, to open
LEGASUITE.HTML file, located in the following directory path:
Your_webserver_root/jwalk/ (/www/apachedft/htdocs/JWALK if you use
Apache web server)
4.
Change the value of the parameter for 'FontUsage' from 2 to 0. Example of the
value of the parameter after your change:
"theApplet.addParameter('FontUsage', '0')"
Double byte G-1
For IBM i Server Install
G-2 JD Edwards World Web Enablement Installation and Configuration Guide
H
Customized Signon
H
If you have a customized Signon screen and want to use it with the A9.3.1 Web
Enablement, you need to set some text file entries and add one entry to the Signon
screen DDS so that the LegaSuite product can:
■
Uniquely identify this client customized Signon screen
■
Display this panel correctly
■
Allow the user to continue to navigate through Web Enablement
■
Have panel SIGNONCS with custom background image or panel SIGNONCD
dynamically building the green screen signon display correctly, some setup is
required. See below for more detailed instructions. Contact My Oracle Support, JD
Edwards World Technical for further assistance.
The change is to display three periods on Line 1 of the screen, starting in Column 2. In
the following DDS example, line 49 displays the three periods on Line 01, Column 02:
Figure H–1 Record Format Text File
The following is an example of a Signon screen with the … added in the upper left
corner, row 1, columns 2, 3, and 4:
Customized Signon H-1
Figure H–2 Signon Screen After Alteration
Several text file entries can be set to display the fields on the Customized Signon
panel. Text File Entry SIGNONCS in WV93.LWM and DYNBLD93.LWM is used to
determine which signon panel to display, SIGNONCS(with custom image) or
SIGNONCD(dynamically built view).
Verify images BKGRDSGN1.JPG, BKGRDSGN2.JPG and SIGNONCS SubWindow.jpg
are setup with chosen images. These images are within the Resources folder under the
A93APP folder path below.
To set up the display of Signon fields, the administrator installing the JD Edwards
World Web Enablement needs to verify that the appropriate text file entry is set
accordingly on the WV93.LWM file.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
Example paths for locations of WV93.LWM and DYNBLD93.LWM
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
C:\Inetpub\wwwroot\ JWALKAPP\A9100APP\
■
C:\Inetpub\wwwroot\ JWALKAPP\A9100APP\
WV93.LWM Text File Entry Updates:
SIGNONCS set to indicate if displaying dynamically built signon panel (Default,
e.g.No) set to YES to display dynamically built signon panel
CUSTUSRTRW set to the row of the text field description for User (e.g. 06)
CUSTUSRTCL set to the column of the text field description for User (e.g. 17)
CUSTUSRTL set to the length of the text field description for User (e.g. 33)
CUSTUSRRW set to the row of the input capable field for User (e.g. 06)
CUSTUSRCL set to the column of the input capable field for User (e.g. 53)
CUSTUSRIL set to the length of the input capable field for User (e.g. 10)
CUSTPSWTRW set to the row of the text field description for Password (e.g. 07)
CUSTPSWTCL set to the column of the text field description for Password (e.g. 17)
H-2 JD Edwards World Web Enablement Installation and Configuration Guide
CUSTPSWTL set to the length of the text field description for Password (e.g. 33)
CUSTPSWRW set to the row of the input capable field for Password (e.g. 07)
CUSTPSWCL set to the column of the input capable field for Password (e.g. 53)
CUSTPSWIL set to the length of the input capable field for Password (e.g. 10)
The following list of text file entries is optional:
CUSTALT1TR set to the row of the text field description for Program/procedure (e.g.
08)
CUSTALT1TC set to the column of the text field description for Program/procedure
(e.g. 17)
CUSTALT1TL set to the length of the text field description for Program/procedure
(e.g. 33)
CUSTALT1R set to the row of the input capable field for Program/procedure (e.g. 08)
CUSTALT1C set to the column of the input capable field for Program/procedure (e.g.
53)
CUSTALT1IL set to the length of the input capable field for Program/procedure (e.g.
10)
CUSTALT2TR set to the row of the text field description for Menu (e.g. 09)
CUSTALT2TC set to the column of the text field description for Menu (e.g. 17)
CUSTALT2TL set to the length of the text field description for Menu (e.g. 33)
CUSTALT2R set to the row of the input capable field for Menu (e.g. 09)
CUSTALT2C set to the column of the input capable field for Menu (e.g. 53)
CUSTALT2IL set to the length of the input capable field for Menu (e.g. 10)
CUSTALT3TR set to the row of the text field description for Current library (e.g. 10)
CUSTALT3TC set to the column of the text field description for Current library (e.g.
17)
CUSTALT3TL set to the length of the text field description for Current library (e.g. 33)
CUSTALT3R set to the row of the input capable field for Current library (e.g. 10)
CUSTALT3C set to the column of the input capable field for Current library (e.g. 53)
CUSTALT3IL set to the length of the input capable field for Current library (e.g. 10)
CUSTSYS1TR set to the row of the text field description for System (e.g. 02)
CUSTSYS1TC set to the column of the text field description for System (e.g. 48)
CUSTSYS1TL set to the length of the text field description for System (e.g. 20)
CUSTSYS1R set to the row of the output field for System (e.g. 02)
CUSTSYS1C set to the column of the output field for System (e.g. 70)
CUSTSYS1IL set to the length of the output field for System (e.g. 08)
CUSTSYS2TR set to the row of the text field description for Subsystem (e.g. 03)
CUSTSYS2TC set to the column of the text field description for Subsystem (e.g. 48)
CUSTSYS2TL set to the length of the text field description for Subsystem (e.g. 20)
CUSTSYS2R set to the row of the output field for Subsystem (e.g. 03)
Customized Signon H-3
CUSTSYS2C set to the column of the output field for Subsystem (e.g. 70)
CUSTSYS2IL set to the length of the output field for Subsystem (e.g. 10)
CUSTSYS3TR set to the row of the text field description for Display (e.g. 04)
CUSTSYS3TC set to the column of the text field description for Display (e.g. 48)
CUSTSYS3TL set to the length of the text field description for Display (e.g. 20)
CUSTSYS3R set to the row of the output field for Display (e.g. 04)
CUSTSYS3C set to the column of the output field for Display (e.g. 70)
CUSTSYS3IL set to the length of the output field for Display (e.g. 10)
DYNBLD93.LWM Text File Entry Updates:
SIGNONCS set to indicate if displaying dynamically built signon panel (Default,
e.g.No) set to YES to display dynamically built signon panel
If Text File entry SIGNONCS is using the Default value of No in WV93 and
DYNBLD93, the following panel is displayed.
Figure H–3 Sign On screen
If Text File entry SIGNONCS is set with value of YES in WV93 and DYNBLD93, the
following panel is displayed.
H-4 JD Edwards World Web Enablement Installation and Configuration Guide
Figure H–4 Sign On (User Information) screen
Customized Signon H-5
H-6 JD Edwards World Web Enablement Installation and Configuration Guide
I
Registration Wizard
I
This appendix contains these topics:
■
Appendix I.1, "Setting Up the Registration Wizard for IBM i Server,"
■
Appendix I.2, "Setting Up the Registration Wizard for Windows Servers."
I.1 Setting Up the Registration Wizard for IBM i Server
For IBM i server, follow the steps from 1 to 10:
1.
You can access the Registration Wizard through the LegaSuite Registration Wizard
link from
START>ALL PROGRAMS>LEGASUITE>REGISTRATION WIZARD
From the Welcome to SEAGULL Registration Wizard screen, click Next.
Figure I–1 Welcome to SEAGULL Registration Wizard screen
2.
Enter LegaSuite for Product Family, 5250 GUI Engine for Product Part, and IBM
iSeries for Platform. Click Next.
Registration Wizard I-1
Setting Up the Registration Wizard for IBM i Server
Figure I–2 SEAGULL Registration Wizard screen
3.
From the Select installation machine screen, select Host machine (IBM i, zSeries,
Solaris, HP-UX, AIX, and Linux). Click Next.
Figure I–3 Select Installation Machine screen
4.
From the Host system serial number screen, enter your host system serial number
and select your LPAR number from the drop down option. Click Next.
Note: You can identify your serial number and partition (LPAR)
from the License Report (LISTLIC). From an IBM i command line type:
SEALMS/REPORTLIC
Press Enter.
WRKSPLF
Press Enter.
I-2 JD Edwards World Web Enablement Installation and Configuration Guide
Setting Up the Registration Wizard for IBM i Server
Figure I–4 Host System Serial Number screen
5.
From the Registration information screen, complete your information and enter
the Installation key E073B1A714FC428DC7EC. Click Next.
Figure I–5 Registration Information screen
6.
From the Activation Request submit screen, select Via Web (requires direct Internet
connection). Click Next.
Registration Wizard I-3
Setting Up the Registration Wizard for IBM i Server
Figure I–6 Activation Request Submit screen
7.
From the Submit by Web screen, click Next.
Figure I–7 Submit by Web screen
Note: The registration key legsrv5250as400.saf is stored in the
following folder:
■
■
Windows XP or Vista: C:\Documents and Settings\All
Users\Application Data\SEAGULL\Registration Wizard
Windows 7: C:\ProgramData\SEAGULL\Registration Wizard
Figure I–8 Registration Wizard Path
I-4 JD Edwards World Web Enablement Installation and Configuration Guide
Setting Up the Registration Wizard for Windows Servers
8.
From the Successfully downloaded Activation File screen, click Next.
Figure I–9 Submitted by Web screen
9.
From the Success screen, click Finish.
Figure I–10 Success screen
10. Copy the file legsrv5250as400.saf from the following folder:
■
■
Windows XP or Vista: C:\Documents and Settings\All Users\Application
Data\SEAGULL\Registration Wizard\
Windows 7: C:\ProgramData\SEAGULL\Registration Wizard
To the following folder:
■
C:\Program Files\SEAGULL\LegaSuite Server for IBM i
V5Rx\4.1xxx.x.xxx\bin\LEGASRV
If JDE components have been installed, (FTP process has been executed) then copy
file to: \LEGASRV folder in the Root IFS.
I.2 Setting Up the Registration Wizard for Windows Servers
For windows servers, follow the steps from 1 to 8:
Registration Wizard I-5
Setting Up the Registration Wizard for Windows Servers
1.
Start Registration Wizard by going to Start>All Programs>Legasuite>LegaSuite
Registration Wizard. Then click Next.
Figure I–11
2.
Enter Legasuite for Product Family, 5250 GUI Engine for Product Part, and
Windows for Platform. Click Next.
Figure I–12
3.
SEAGULL Registration Wizard screen
Select SEAGULL Product to Activate screen
Select This machine for the activation of Seagull product. Click Next.
I-6 JD Edwards World Web Enablement Installation and Configuration Guide
Setting Up the Registration Wizard for Windows Servers
Figure I–13 Select Installation Machine screen
4.
Enter a user’s information in Registration information screen. Enter
E073B1A714FC428DC7EC for Installation key. Click Next.
Figure I–14 Registration Information screen
5.
Select Via web (requires direct Internet connection). Click Next.
Registration Wizard I-7
Setting Up the Registration Wizard for Windows Servers
Figure I–15
6.
If successful, the system displays the following screen. Click Next.
Figure I–16
7.
Activation Request Submit screen
Submit by Web screen
The path to which an Activation file is downloaded is displayed in the screen.
Click Next.
I-8 JD Edwards World Web Enablement Installation and Configuration Guide
Setting Up the Registration Wizard for Windows Servers
Figure I–17 Submitted by Web (Activation File) screen
8.
Click Finish to complete the process of activation.
Figure I–18 Success screen
Registration Wizard I-9
Setting Up the Registration Wizard for Windows Servers
I-10 JD Edwards World Web Enablement Installation and Configuration Guide
J
Activating Sign off Button on Menu Panels
J
To have the Sign off push button display on a Menu panel, the administrator installing
the JD Edwards World Web Enablement needs to verify that the appropriate text file
entry is set accordingly on the WV93.LWM and DYNBLD93.LWM files.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
Example paths for location of WV93.LWM and DYNBLD93.LWM:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\JWALKAPP\A9100APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
■
MENUCPYR1 set to the exact character text on row 23, columns 46-51 of the menu
screen.
If the content of MENUCPYR1 contains the same text as listed on row 23, columns
46-51 of the menu screen, the Sign off push button displays only on a Menu panel and
functions as a “90” (e.g. Sign Off) and the standard menu panel push button displays
and functions as F12.
A partial match between row 23, columns 46-51 of the menu
screen and the value in MENUCPYR1 is considered a match. Verify
the value in MENUCPYR1 differs completely.
Note:
If the content of MENUCPYR1 differs from what is listed on row 23, columns 46-51 of
the menu screen, the Sign off push button does not display and the standard
application panel push button displays and functions as F3.
Activating Sign off Button on Menu Panels
J-1
J-2 JD Edwards World Web Enablement Installation and Configuration Guide
K
JD Edwards World Help Menu Integration
K
This appendix contains these topics:
■
Section K.1, "Overview of Help Menu Integration,"
■
Section K.2, "JD Edwards World Web Enablement Help Menu Integration."
For UPK Content Sensitive Help, refer to this appendix, which is available after
installing the UPK (User Productivity Kit) Help Menu Integration patch. This
appendix contains set up instructions using Web Enablement.
K.1 Overview of Help Menu Integration
The Player deployment format from the Developer is not only useful in various
training & educational initiatives; this output is also designed to provide
in-application performance support for the end users.
There are specific add-ons and instructions for certain major enterprise applications to
accommodate context-sensitive in-application performance support; these applications
are referred to as target applications throughout this document. Content for target
applications can generally be deployed using one of the following two methods:
■
■
Help Menu Integration - This method allows the target application end users to
invoke context-sensitive in-application performance support material using the
application's existing Help menu.
SmartHelp - This is a toolbar button for browsers that a target application end
user may use to invoke context-sensitive in-application performance support
material.
The mechanism for context-sensitivity for target applications is known as ExactMatch.
This technique allows the Player to display a list of content material that is related to
the end user's activity in the application. The relevancy of the content list is
determined based on content items that contain exactly the same context information
as recorded during content creation in the Developer.
For browser-based non-target applications, the SmartHelp toolbar button can still be
used to deploy context sensitive in-application performance support; however, there is
a difference in how the applicable list is generated. Unlike ExactMatch where the
recorded context information is matched exactly with the end user's context in the
application, a statistical analysis is used to rank the most probable content items in
order to generate the list of applicable content items. This method of generating the
applicable list is called SmartMatch.
Finally, content created for non-target applications prior to the introduction of
SmartMatch technology may still be deployed using the SmartHelp toolbar button for
the browser in a non-context sensitive manner. In this case, the Player displays all of
JD Edwards World Help Menu Integration
K-1
Overview of Help Menu Integration
the content items; however, the user may find the appropriate items using the Search
feature or by browsing the content hierarchy.
Please refer to the Help Menu Integration Guide for each target
application for specific instructions on Help Menu Integration as well
as SmartHelp based content deployment.
Note:
K.1.1 Plan for Deploying In-Application Support
Once your organization decides to deploy content for in-application performance
support, some of the fundamental questions that need to be addressed are:
■
What deployment mechanism is most appropriate for your organization, Help
Menu Integration with a target application or SmartHelp based deployment?
■
Who needs to be involved?
■
When does it have to happen?
■
What needs to be done?
Understanding the answers to these questions will give your organization the
information it needs to implement help menu integration and context sensitive help
successfully.
K.1.1.1 Who Needs to be Involved?
A few roles across typical organizational boundaries are needed. They are:
■
Content Developer
■
Web Server Administrator
■
Application Administrator
■
Test User
K.1.1.2 When Does it Have to Happen?
For some target applications, steps must be taken before production recording begins
in order to support context sensitive help. For most applications, application
configuration can occur after and independently of production recording. If your
organization wants context sensitive help, always check that context is being captured
while recording.
Please refer to the Help Menu Integration Guide for each target
application for specific instructions about Help Menu Integration as
well as SmartHelp based content deployment.
Note:
K.1.1.3 What Needs to be Done?
These are the tasks each role needs to complete to successfully deploy in-application
performance support content.
Content Developer
■
Create content in the Developer - While ExactMatch information for target
applications and SmartMatch information for browser-based non-target
applications will be automatically captured, it is recommended to validate that
context is being captured.
K-2 JD Edwards World Web Enablement Installation and Configuration Guide
JD Edwards World Web Enablement Help Menu Integration
■
Publish the player package
■
Give the published player package to the web server administrator
Web Server Administrator
Deploy the published player package to a web server
■
■
Provide the URL for the published player package to the application administrator
Application Administrator
■
Perform the configuration steps detailed in the Help Menu Integration guide for
each application
■
Receive the player package URL from the web server administrator
■
Perform the Help Menu Integration guide steps for URL configuration
Test User
■
Verify the published player package appears from the application using the Help
Menu Integration option or the SmartHelp button, as deployed
■
If you are deploying context sensitive help, the test user should coordinate with
the content developer to note which parts of the application were used to create
content and then verify that the Player launches with an appropriate list of
applicable topics.
Note: Please refer to the appropriate Help Menu Integration guide
for specific instructions about
K.2 JD Edwards World Web Enablement Help Menu Integration
The ability to access context-sensitive Player help has been added to JD Edwards
World Web Enablement. Some setup is required for this process to work correctly.
The instructions that follow are for the JWalk Java client interface. A button to launch
Player content appears on the program menus; no configuration is necessary for this
button to appear. However, it must be configured to point to the Player help content
through entries in two text files.
K.2.1 Configure the Text Files
To launch the context-sensitive Player help content, the JD Edwards World Web
Enablement administrator needs to set entries appropriately in the WV9100.JVM and
DYNBLD9100.JVM text files. These files are located within the Deployment area of the
JWalk server or client.
■
For the iSeries-i5 Installation:
www/<HTTP server>, such as:
apachedft/htdocs/JWALK/JWALKAPP/A9100APP
■
For the Windows NT-2000-2003 Server Installation:
C:\Inetpub\wwwroot\JWALKAPP\A9100APP
Or
C:\Program Files\Apache Software
Foundation\Apache2.2\htdocs\JWALKAPP\A9100APP
JD Edwards World Help Menu Integration
K-3
JD Edwards World Web Enablement Help Menu Integration
The Text File entries to be updated are:
■
■
UPKVIEWI - Set this to Y to display the Context aware icon on the program
menus.
UPKVIEWH - Set this to Y to display the View Content Option from the Help
Drop Down menu.
■
UPKHELP - This displays text when hovering over the Context aware icon.
■
UPKHELPOPT - This displays text for the option on the Help Drop Down menu.
■
UPKPath - This should be set to the path of the UPK server. For example:
http://<server>/<virtual directory>/jdewalk/hemi/jdewalk_gateway.html_
?CTXEX=
If you place the Player help content on the Windows server supporting the JWalk
client interface, no additional configuration is necessary. If the help content is on a
non-Windows server, you need to configure the odcustomurl.js file. See the following
section for details.
K.2.2 Configure the JavaScript File
If the Player help content is located on a non-Windows server, you need to configure
the odcustomurl.js file to point to the content location.
To configure the Javascript file
1. In the jdeworld\hemi folder of the published UPK Help content, copy the
odcontenturl.js file and rename it to odcustomurl.js.
2.
Open the odcustomurl.js file with Notepad or any text editor.
3.
Define the Gkod.Variables.OD_DEFAULT_URL variable to point to the location of
the content.
4.
Save and close the file.
K-4 JD Edwards World Web Enablement Installation and Configuration Guide
L
Restriction of Creation of Virtual Devices
L
If your system restricts the creation of virtual devices, you can activate the following
two settings within the LEGASUITE.INI to create named virtual devices within the
Web Enablement client.
Use a text editor tool such as MS Notepad or MS WordPad to open the
LEGASUITE.INI file, located in the following folder:
■
■
If Native Java Client install, /Your IBM i root folder/LEGASRV/
If NT Java Client or LegaSuite Client on Windows, C:\Program
Files\SEAGULL\LegaSuite Server\4.1xxx.x.xxx
To activate creation of Virtual Devices for Web Enablement, remove the semicolon in
front of the two LEGASUITE.INI settings:
■
DeviceNameSequence=001
■
DeviceName=A93WEB, can change the A93WEB to any other six character value
Restriction of Creation of Virtual Devices L-1
L-2 JD Edwards World Web Enablement Installation and Configuration Guide
M
E-mail Separator Character
M
A text file entry has been set up to allow correct creation of e-mail parameter
information. The administrator installing the JD Edwards World Web Enablement
needs to verify that the appropriate text file entry is set accordingly on the WV93.LWM
and DYNBLD93.LWM files.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
Example paths for location of WV93.LWM and DYNBLD93.LWM are:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\ JWALKAPP\A9100APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
■
EMALSEP set to the separator character for the respective email client server.
Default value is & for Microsoft Outlook.
E-mail Separator Character M-1
M-2
JD Edwards World Web Enablement Installation and Configuration Guide
N
E-mail Special Instructions
N
A text file entry has been set up to add the parameter CCSID (65535) to the CRTPF
command within the scripted process to e-mail a spooled file (WRKSPLF). Adding the
CCSID (65535) parameter states that no language conversion should occur. The default
value is N, which does not add this parameter.
The administrator installing the JD Edwards World Web Enablement needs to verify
that the appropriate text file entry is set accordingly on the WV93.LWM file.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
file.
Example paths for location of WV93.LWM and DYNBLD93.LWM:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\ JWALKAPP\A9100APP\
WV93.LWM Text File Entry Updates:
■
Change CRTPFCHG value to Y to add the parameter CCSID(65535)
In addition, text file entries can be set to fill in the To address, Subject or the Body of
the e-mail when you click the Email Header link at the top of main panels. However, if
the text file entry for OTHPATH3 has a value other than blank, then the following text
file entries are not used:
■
Change EMAILTO to the value for the To e-mail address
■
Change EMAILSUB to the value for the Subject in an e-mail
■
Change EMAILBODY to the value for the Body in an e-mail
E-mail Special Instructions
N-1
N-2 JD Edwards World Web Enablement Installation and Configuration Guide
O
Session Resume
O
You can set up Session Resume on a LegaSuite Server. When you use Session Resume,
the system allows users only one session at time, but does not require users to signon
more than once as long as that session is active.
Use a text editor tool such as MS Notepad or MS WordPad to open the
LEGASUITE.INI file, located in the following folder:
■
■
If Native Java Client install, /Your IBM i root folder/LEGASRV/
If NT Java Client or LegaSuite Client on Windows, C:\Program
Files\SEAGULL\LegaSuite Server\4.1xxx.x.xxx
Add the following two lines to the LegaSuite Server group in the LEGASUITE.INI file:
■
SessionResume=1
■
ClientAliveCheckTime=N, where a new session is initiated after N minutes
Add a line to the LEGASUITE.HTML file.
Use a text editor took, such as MS Notepad or MS WordPad, to open
LEGASUITE.HTML, located in the following directory path:
■
Your_webserver_root/jwalk/ (/www/apachedft/htdocs/JWALK if you use
Apache web server)
Use the following example to assist you updating the LEGASUITE.HTML file. The text
that appears in red must be added to the file:
Figure O–1 Additional Text for the LEGASUITE.HTML File
Example: LEGASUITE.HTML file
Session Resume O-1
O-2 JD Edwards World Web Enablement Installation and Configuration Guide
P
Parameterized URL
P
Note: Parameterized URL processing is only available when using
JD Edwards World A9.2 or above.
Parameterized URL is the functional process that allows external systems to launch a
native JD Edwards World application through the use of a simple URL. The
functionality provides an external system a near seamless user interface integration
with most JD Edwards World applications.
The Parameterized URL process simulates an interactive web user interface with JD
Edwards World applications (similar to the way modern applications communicate
through the use of a URL) using the LegaSuite GUI (formerly LegaSuite) Web
Enablement product.
An interactive request initiates a Web Enablement session within JD Edwards World
and then allows users to interact with the results and/or proceed to other JD Edwards
World applications.
There are two options to access JD Edwards World Parameterized URL:
■
■
Option one does not use Session Resume, the system requires users to signon
every time when a Web Enablement session is initiated(each time a parameterized
URL is executed)
Option two utilizes Session Resume. Session Resume parks a session when the
browser window is closed, then when JD Edwards World is accessed again, the
system reuses the current active session and returns the user to the previous panel.
A timer is set to keep the current Web Enablement session active. A parameterized
URL call can reuse an active session, so the user does not have to sign in each time
a call to JD Edwards World is issued
Four different application group processes have to be set up for Parameterized URL to
function properly:
■
Web Enablement
■
HostedWorldServlet
■
World Application Parameters
■
External System
Parameterized URL P-1
Note: For the Parameterized URL process to function correctly,
J98INITA is a requirement for the Initial program to call value for a
user profile whether this user has access to a single environment or
multiple environments.
Web Enablement
There is an update to the LEGASUITE.INI file for both option types.
Use a text editor tool such as MS Notepad or MS WordPad to open the
LEGASUITE.INI file, located in the following folder:
■
■
If Native Java Client install, /Your IBM i root folder/LEGASRV/
If NT Java Client or LegaSuite Client on Windows, C:\Program
Files\SEAGULL\LegaSuite Server\4.1xxx.x.xxx
Add the following two lines to the LegaSuite Server group in the LEGASUITE.INI file
within the LEGASRV folder:
■
DeviceName=JWALK
■
DeviceNameSequence=00000
Note: To use Parameterized URL, the Device Name has to begin
with JWALK.
The Session Resume second option requires additional updates to the Web Enablement
set up. See instructions in Appendix O, "Session Resume."
HostedWorldServlet
1. Download the most current Web Enablement software update and extract the
archive, which creates the folder in the download directory.
2.
Access the following download directory folder:
■
A91_A93_JWalk_CD_SUx_v1038_1_xxx\Parameterized URL
Deploy the jdeworld.war file to the Application Server.
Note: See MTRs for Application Server requirements for
Parameterized URL.
3.
Stop and restart this Application Server. Next, the system creates the folder
jdeworld in this Application Server area.
4.
Access the following path in this Application Server area:
applications/jdeworld/jdeworld/WEB-INF/classes/config/
5.
Edit the config.xml file.
Update the server path and point to the LegaSuite server IP Address and keep the
:80 indicating the Default port used for the HTTP Server for LegaSuite. However,
if the HTTP Server port is not 80, then it needs to be changed to the correct port.
Also, update the LegaSuite Server port value within <port>1289</port> if it is
different than port 1289.
P-2 JD Edwards World Web Enablement Installation and Configuration Guide
Use the following example to assist you updating the config.xml file. The text that
appears in red must be added to the file:
Figure P–1
Additional Text for the config.xml File
Example: config.xml file
6.
Save the changes and exit out of config.xml.
World Application Parameters
The RPG programs LegaSuite Script/Shell Processor (J00JMNU) and Parse a Piped
URL Command String (P98URLPRC), translate incoming commands in a defined
piped format into executable system commands. Incoming command strings can be
program CALL commands or system commands. Each piped command is prefixed by
a function to identify the command type, the execution environment, and the
command strings must be null terminated.
A piped command consists of two parts:
■
The function followed by the command string
■
The function and command string must be separated by a pipe
a) Command string formats
Function
Environment
Command Format
*CALL
Inline Call
|<Piped Command
String>|x'00'
*SBM
Submitted
|<Piped Command
String>|x'00'
*CMDI
Inline Call
|<IBM Command>x'00'
*CMDB
Submitted
|<IBM Command>x'00'
*CALL and *SBM are CALL commands which invoke the pipe parser. The final
structured CALL command is then executed inline (*Call) or submitted as a batch job
(*Sbm).
*CMDI and *CMDB are the inline or batch submission functions for all other IBM
commands.
Note: The primary difference between CALL commands and other
commands is that all CALL commands must be terminated with a
pipe, then the null terminator. Other IBM commands are terminated
with only the null terminator.
Parameterized URL P-3
JD Edwards World application entry parameters are required to be defined in the
F98016 file to enable the pipe parser to verify the pipe string and map the data from
the string to program entry parameters for the call to a JD Edwards World application.
Access to the parameter definition program (P98016) is through SVR (P9801) via
function key F16. Program Entry Parameter definition (P98016) incorporates the ability
to map scalar parameters as well as data structures with subfield definitions. The later
enables passing of structure subfield values to be reconstructed into data structure
parameters.
The following are examples of Program Entry Parameter panels, SVR, inquire on
program, F16:
Figure P–2
Program Entry Parameters (1 of 3)
Figure P–3
Program Entry Parameters (2 of 3)
P-4 JD Edwards World Web Enablement Installation and Configuration Guide
Figure P–4
Program Entry Parameters (3 of 3)
In JD Edwards World, access Library List Revisions, 5/G944, and update the value for
Menu/Pgm with J00JMNU for all production environment library lists.
Update the following two JD Edwards World System i System values:
■
QAUTOVRT, Autoconfigure virtual devices
■
QDEVRCYACN, Device I/O error action
To view the System values on a System i command line, type the following:
■
DSPSYSVAL SYSVAL(QAUTOVRT) and then press Enter
■
DSPSYSVAL SYSVAL(QDEVRCYACN) and then press Enter
Note: QAUTOVRT is a required update and QDEVRCYACN is a
recommended update.
To update these System values, on a command line, type the following:
■
■
CHGSYSVAL SYSVAL(QAUTOVRT) VALUE(9999) and then press Enter
CHGSYSVAL SYSVAL(QDEVRCYACN) VALUE(*ENDJOBNOLIST) and then
press Enter
External System
The following are two set up examples to access application programs in JD Edwards
World Web Enablement using a Web Link.
To setup a Web Link for Customer Integration:
Specify the URL of the Customer Name Search application using this format:
■
■
■
http://[Server]:[port]/jdeworld/hostedworldservlet?&@PID=[N]|P01200&@DataStr
ucture=|P01200|[Version]|%20|[Name]
[Server]:[port] is the JD Edwards World System i and port for the System i
WebSphere Application server or another Application server and port
[N] is the Call Switch
Parameterized URL P-5
The Call Switch values are:
■
N = call Parameterized URL application when DataStructure values have changed
■
Y = always call Parameterized URL application
[Version] is the DREAM Writer Version of P01200 to execute
[Name] is the customer alpha name for the Address Book record.
To setup a Web Link for World to CRM On Demand Sales Order Integration:
■
Specify the URL of the View Sales Quote / Order program using this format:
http://[Server]:[port]/jdeworld/hostedworldservlet?&@PID=[Y]|P42180&@DataStru
cture=|P42180|[Version]|[External System Name][ID]|[Name]
[Server]:[port] is the JD Edwards World System i and port for the System i WebSphere
Application server or another Application server and port
[Y] is the Call Switch
The Call Switch values are:
· N = call Parameterized URL application when DataStructure values have changed
· Y = always call Parameterized URL application
[Version] is the DREAM Writer Version of P42180 to execute
[External System Name] is the name of the External System Instance
The External System Name:
Value retrieved from the User Defined Code Table, system 98S and Code ES.
[ID] is the External System Key
[Name] is the description, assigned in an External System, for an integration
transaction.
P-6 JD Edwards World Web Enablement Installation and Configuration Guide
Q
Function Keys Case Sensitive
Q
The first three function keys displayed in the left-side navigation bar are retrieved
from Text File entries. Hence, the administrator must verify if the display of the
Function key text on F24, within the JD Edwards World environment, is not a mixed
case, and then the following text file entries must be updated.
The administrator installing the JD Edwards World Web Enablement needs to verify
that the appropriate text file entries are set accordingly on the WV93.LWM and
DYNBLD93.LWM files.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
Example paths for location of WV93.LWM and DYNBLD93.LWM:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\ JWALKAPP\A9100APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
DETAIL
DETAILS
DISPERR
EXITPROG
FIELDSH
FLDSH
MOREFUN
MOREFUNF24
Function Keys Case Sensitive Q-1
Q-2 JD Edwards World Web Enablement Installation and Configuration Guide
R
Action Code Icon Display
R
To display the Action Code icons correctly on an application panel with an Action
Code field, you need to set several text file entries to the various text descriptions for
the Action Code field. The value of the text file entry is case sensitive.
The administrator installing the JD Edwards World Web Enablement needs to verify
that the appropriate text file entries are set accordingly on the WV93.LWM and
DYNBLD93.LWM files.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
Example paths for location of WV93.LWM and DYNBLD93.LWM:
For IBM i Installation:
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
C:\Inetpub\wwwroot\ JWALKAPP\A9100APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
ACTIONTEXT set to the first variation of the text description for Action Code field
(e.g. Action Code)
ACTIONTXT2 set to the second variation of the text description for Action Code field
(e.g. Action code)
ACTIONTXT3 set to the third variation of the text description for Action Code field
(e.g. Action Type)
ACTIONTXT4 set to the fourth variation of the text description for Action Code field
(e.g. Action)
ACTIONTXT5 set to the fifth variation of the text description for Action Code field
(e.g. Action)
ACTIONTXT6 set to the sixth variation of the text description for Action Code field
(e.g. Action)
ACTIONTXT7 set to the seventh variation of the text description for Action Code field
(e.g. ACTION CODE)
ACTIONTXT8 set to the eighth variation of the text description for Action Code field
(e.g. ACTION TYPE)
ACTIONTXT9 set to the ninth variation of the text description for Action Code field
(e.g. ACTION)
Action Code Icon Display R-1
If you need more than one language for the variations above, JD Edward World
recommends to set up another LegaSuite Server instance for each language needed.
For more information, see Appendix B, "Alternate Language Special Install
Instructions."
R-2 JD Edwards World Web Enablement Installation and Configuration Guide
S
Logo Push Button
S
On each Main panel, you can see a push button over the Oracle logo. The
administrator installing the JD Edwards World Web Enablement can set up the push
button access for a URL address, document, or an e-mail. The administrator must
verify that the appropriate text file entries are set accordingly on the WV93.LWM and
DYNBLD93.LWM files.
Use a text editor tool such as MS Notepad or MS WordPad to open the WV93.LWM
and DYNBLD93.LWM files.
Example of paths for location of WV93.LWM and DYNBLD93.LWM:
For IBM i Installation:
■
Your IBM i root folder/LEGASUITE/A93App/
For Windows NT-2000-2003 Server and LegaSuite Client for Windows Installations:
■
C:\Inetpub\wwwroot\ JWALKAPP\A9100APP\
WV93.LWM and DYNBLD93.LWM Text File Entry Updates:
■
■
ORACLECOM set to the path of the URL, Document, or Email (e.g.
www.oracle.com)
ORACLEURLT set to the type of URL, Document, or E-mail (e.g. URL), see
available choices under OTHTYP1 within Appendix E, "Attachment Link Access."
Logo Push Button
S-1
S-2 JD Edwards World Web Enablement Installation and Configuration Guide
T
Text File Entry Table
T
The following table displays all the text file entries that need to be updated. The table
lists the file where the text file entry resides (WV93.LWM or DYNBLD93.LWM), a
description of what the text file entry does and the value of the entry. The value of the
text file entry is case sensitive.
T.1 Text File Entry Table
Entry Name
File
Description
Value
MASTSSURL
WV93.LWM and
DYNBLD93.LWM
WRKSPLF
Printing
http://<IBM i machine name>
for Native Java Client
http://<PC server name> for
NT Java Client and LegaSuite
Client on Windows
ERMURL
WV93.LWM and
DYNBLD93.LWM
WRKSPLF
Printing
See values for MASTSSURL
INSTALL
WV93.LWM and
DYNBLD93.LWM
WRKSPLF
Printing
Default is WAS for Native Java
Client
NT for NT Java Client
WIN for LegaSuite Client on
Windows
ERMPRTURL
WV93.LWM and
DYNBLD93.LWM
WRKSPLF
Printing
See values for INSTALL
DYNBLDURL
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
http://<IBM i machine
name>/Docs/ for Native Java
Client
http://<PC servername>/Docs/
for NT Java Client and LegaSuite
Client for Windows
Note: SAMPLE.PDF must be
included in the Docs folder
within the respective install.
ERMSSURL
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
See values for DYNBLDURL
OTHTEXT1
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is URL
OTHPATH1
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is www.oracle.com
Text File Entry Table T-1
Text File Entry Table
Entry Name
File
Description
Value
OTHTYP1
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is URL
Available choices are:
URL for a URL address
EML for an E-mail
DOC for a file with extension
.doc
EXC for a file with extension .xls
PDF for a file with extension .pdf
EXE for a file with extension .exe
OTHTEXT2
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is Document
OTHPATH2
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is SAMPLE.pdf
OTHTYP2
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is PDF See available
choices for OTHTYP1
OTHTEXT3
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is Email
OTHPATH3
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is World.Web.Enable
ment@oracle.com
OTHTYP3
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is EML See available
choices for OTHTYP1
OTHTEXT4
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is World Resources
OTHPATH4
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is https://metalink3.ora
cle.com/od/faces/ind ex.jspx
OTHTYP4
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is URL See available
choices for OTHTYP1
OTHTEXT5
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is Support
OTHPATH5
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is http://supp
ort.oracle.com
OTHTYP5
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is URL See available
choices for OTHTYP1
OTHTEXT7
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is URL Open/Email
OTHTEXT8
WV93.LWM and
DYNBLD93.LWM
Attachment Link
Access
Default is Document
CALCEXEPTH
WV93.LWM and
DYNBLD93.LWM
Calculator Access
See values for DYNBLDURL
OTHTEXT6
WV93.LWM and
DYNBLD93.LWM
Calculator Access
Default is Calculator
OTHPATH6
WV93.LWM and
DYNBLD93.LWM
Calculator Access
Default is calc.exe
OTHTYP6
WV93.LWM and
DYNBLD93.LWM
Calculator Access
Default is EXE
T-2 JD Edwards World Web Enablement Installation and Configuration Guide
Text File Entry Table
Entry Name
File
Description
Value
ORACLECOM
WV93.LWM and
DYNBLD93.LWM
Oracle Logo
Attachment Link
Access
Default is
http://www.oracle.com
ORACLEURLT
WV93.LWM and
DYNBLD93.LWM
Oracle Logo
Attachment Link
Access
Default is URL See available
choices for OTHTYP1
CUSTUSRTRW
WV93.LWM
Customized
Signon
Row of text field description for
User Default is 06
CUSTUSRTCL
WV93.LWM
Customized
Signon
Column of text field description
for User Default is 17
CUSTUSRTL
WV93.LWM
Customized
Signon
Length of text field description
for User Default is 33
CUSTUSRRW
WV93.LWM
Customized
Signon
Row of input capable field for
User Default is 06
CUSTUSRCL
WV93.LWM
Customized
Signon
Column of input capable field
for User Default is 53
CUSTUSRIL
WV93.LWM
Customized
Signon
Length of input capable field for
User Default is 10
CUSTPSWTRW
WV93.LWM
Customized
Signon
Row of text field description for
Password Default is 07
CUSTPSWTCL
WV93.LWM
Customized
Signon
Column of text field description
for Password Default is 17
CUSTPSWTL
WV93.LWM
Customized
Signon
Length of text field description
for Password Default is 33
CUSTPSWRW
WV93.LWM
Customized
Signon
Row of input capable field for
Password Default is 07
CUSTPSWCL
WV93.LWM
Customized
Signon
Column of input capable field
for Password Default is 53
CUSTPSWIL
WV93.LWM
Customized
Signon
Length of input capable field for
Password Default is 10
CUSTALT1TR
WV93.LWM
Customized
Signon
Optional text file entry Row of
the text field description for
Program/procedure Default is
blank
CUSTALT1TC
WV93.LWM
Customized
Signon
Optional text file entry Column
of the text field description for
Program/procedure Default is
blank
CUSTALT1TL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the text field description for
Program/procedure Default is
blank
CUSTALT1R
WV93.LWM
Customized
Signon
Optional text file entry Row of
the input capable field for
Program/procedure Default is
blank
CUSTALT1C
WV93.LWM
Customized
Signon
Optional text file entry Column
of the input capable field for
Program/procedure Default is
blank
Text File Entry Table T-3
Text File Entry Table
Entry Name
File
Description
Value
CUSTALT1IL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the input capable field for
Program/procedure Default is
blank
CUSTALT2TR
WV93.LWM
Customized
Signon
Optional text file entry Row of
the text field description for
Menu Default is blank
CUSTALT2TC
WV93.LWM
Customized
Signon
Optional text file entry Column
of the text field description for
Menu Default is blank
CUSTALT2TL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the text field description for
Menu Default is blank
CUSTALT2R
WV93.LWM
Customized
Signon
Optional text file entry Row of
the input capable field for Menu
Default is blank
CUSTALT2C
WV93.LWM
Customized
Signon
Optional text file entry Column
of the input capable field for
Menu Default is blank
CUSTALT12IL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the input capable field for Menu
Default is blank
CUSTALT3TR
WV93.LWM
Customized
Signon
Optional text file entry Row of
the text field description for
Current library Default is blank
CUSTALT3TC
WV93.LWM
Customized
Signon
Optional text file entry Column
of the text field description for
Current library Default is blank
CUSTALT3TL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the text field description for
Current library Default is blank
CUSTALT3R
WV93.LWM
Customized
Signon
Optional text file entry Row of
the input capable field for
Current library Default is blank
CUSTALT3C
WV93.LWM
Customized
Signon
Optional text file entry Column
of the input capable field for
Current library Default is blank
CUSTALT13IL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the input capable field for
Current library Default is blank
CUSTSYS1TR
WV93.LWM
Customized
Signon
Optional text file entry Row of
the text field description for
System Default is blank
CUSTSYS1TC
WV93.LWM
Customized
Signon
Optional text file entry Column
of the text field description for
System Default is blank
CUSTSYS1TL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the text field description for
System Default is blank
CUSTSYS1R
WV93.LWM
Customized
Signon
Optional text file entry Row of
the output field for System
Default is blank
T-4 JD Edwards World Web Enablement Installation and Configuration Guide
Text File Entry Table
Entry Name
File
Description
Value
CUSTSYS1C
WV93.LWM
Customized
Signon
Optional text file entry Column
of the output field for System
Default is blank
CUSTSYS1IL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the output field for System
Default is blank
CUSTSYS2TR
WV93.LWM
Customized
Signon
Optional text file entry Row of
the text field description for
Subsystem Default is blank
CUSTSYS2TC
WV93.LWM
Customized
Signon
Optional text file entry Column
of the text field description for
Subsystem Default is blank
CUSTSYS2TL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the text field description for
Subsystem Default is blank
CUSTSYS2R
WV93.LWM
Customized
Signon
Optional text file entry Row of
the output field for Subsystem
Default is blank
CUSTSYS2C
WV93.LWM
Customized
Signon
Optional text file entry Column
of the output field for Subsystem
Default is blank
CUSTSYS12IL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the output field for Subsystem
Default is blank
CUSTSYS3TR
WV93.LWM
Customized
Signon
Optional text file entry Row of
the text field description for
Display Default is blank
CUSTSYS3TC
WV93.LWM
Customized
Signon
Optional text file entry Column
of the text field description for
Display Default is blank
CUSTSYS3TL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the text field description for
Display Default is blank
CUSTSYS3R
WV93.LWM
Customized
Signon
Optional text file entry Row of
the output field for Display
Default is blank
CUSTSYS3C
WV93.LWM
Customized
Signon
Optional text file entry Column
of the output field for Display
Default is blank
CUSTSYS13IL
WV93.LWM
Customized
Signon
Optional text file entry Length of
the output field for Display
Default is blank
Text File Entry Table T-5
Text File Entry Table
Entry Name
File
Description
Value
MENUCPYR1
WV93.LWM and
DYNBLD93.LWM
Activating Sign
Off Button on
Menu Panels
Exact character text on row 23,
columns 46 - 51 of the menu
screen(Text at end of Copyright
statement on row 23) Default is
Oracle
Note: A partial match between
row 23, columns 46-51 of the
menu screen and the value in
MENUCPYR1 is considered a
match. Verify the value in
MENUCPYR1 matches
completely.
UPKPATH
WV93.LWM and
DYNBLD93.LWM
UPK Content
Sensitive Help
Contains path to server where
UPK information is accessed
Default is
http:/localhost/upkcontent/jde
world/hem i/jdeworld_
gateway. Html?CTXEX=
UPKVIEWH
WV93.LWM and
DYNBLD93.LWM
UPK Content
Sensitive Help
Default is N If N, then UPK will
not display in Help Drop Down
left click choices. If Y, then left
click on Help Drop Down and
choose UPK.
UPKVIEWI
WV93.LWM and
DYNBLD93.LWM
UPK Content
Sensitive Help
Default is N If N, then UPK icon
will not display in upper right
hand corner. If Y, then UPK icon
will display in upper right hand
corner.
EMALSEP
WV93.LWM and
DYNBLD93.LWM
E-mail Separator
Character
Set to the separator character for
the respective email client server.
Default is & for Microsoft
Outlook
CRTPFCHG
WV93.LWM
E-mail Special
Instructions
Default is N If Y, will add
parameter CCSID(65535) to the
CRTPF command within the
scripted process to e-mail a
spooled file(WRKSPLF).
EMAILTO
WV93.LWM
E-mail Special
Instructions
Value for the recipient's e-mail
address('To') Default is blank
Note: EMAILTO, EMAILSUB,
and EMAILBODY will only be
used if text file entry
OTHPATH3 is blank
EMAILSUB
WV93.LWM
E-mail Special
Instructions
Value for the Subject in an e-mail
Default is Insert Subject text here
EMAILBODY
WV93.LWM
E-mail Special
Instructions
Value for the body of in an
e-mail Default is Insert body of
text here
DETAIL
WV93.LWM and
DYNBLD93.LWM
Function Keys
Case Sensitive
Text value for a Function key in
the Navigation Bar Default is
Detail
DETAILS
WV93.LWM and
DYNBLD93.LWM
Function Keys
Case Sensitive
Text value for a Function key in
the Navigation Bar Default is
Details
T-6 JD Edwards World Web Enablement Installation and Configuration Guide
Text File Entry Table
Entry Name
File
Description
Value
DISPERR
WV93.LWM and
DYNBLD93.LWM
Function Keys
Case Sensitive
Text value for a Function key in
the Navigation Bar Default is
Display Error Message
EXITPROG
WV93.LWM and
DYNBLD93.LWM
Function Keys
Case Sensitive
Text value for a Function key in
the Navigation Bar Default is
Exit Program
FIELDSH
WV93.LWM and
DYNBLD93.LWM
Function Keys
Case Sensitive
Text value for a Function key in
the Navigation Bar Default is
Field Sensitive Help
FLDSH
WV93.LWM and
DYNBLD93.LWM
Function Keys
Case Sensitive
Text value for a Function key in
the Navigation Bar Default is
Field Sensitive Help
MOREFUN
WV93.LWM and
DYNBLD93.LWM
Function Keys
Case Sensitive
Text value for a Function key in
the Navigation Bar Default is
Display Functions
MOREFUNF24
WV93.LWM and
DYNBLD93.LWM
Function Keys
Case Sensitive
Text value for a Function key in
the Navigation Bar Default is
Display Functions - F24
ACTIONTEXT
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
First variation for text
description for Action Code field
Default is Action Code
ACTIONTXT2
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
Second variation for text
description for Action Code field
Default is Action code
ACTIONTXT3
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
Third variation for text
description for Action Code field
Default is Action Type
ACTIONTXT4
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
Fourth variation for text
description for Action Code field
Default is Action.
ACTIONTXT5
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
Fifth variation for text
description for Action Code field
Default is Action.
ACTIONTXT6
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
Sixth variation for text
description for Action Code field
Default is Action:
ACTIONTXT7
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
Seventh variation for text
description for Action Code field
Default is ACTION CODE
ACTIONTXT8
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
Eighth variation for text
description for Action Code field
Default is ACTION TYPE
ACTIONTXT9
WV93.LWM and
DYNBLD93.LWM
Action Code Icon
Display
Ninth variation for text
description for Action Code field
Default is ACTION
SIGNONCS
WV93.LWM and
DYNBLD93.LWM
Display
Dynamically Built
Custom Signon
panel
Default is No If No, then
SIGNONCS panel is displayed
with custom background image.
If YES, then dynamically built
SIGNONCDpanelisdisplayed.
Text File Entry Table T-7
Text File Entry Table
T-8 JD Edwards World Web Enablement Installation and Configuration Guide