enterpriseone tools 8.93 web server installation …...server. to install the web server on a...

EnterpriseOne Tools 8.93Web Server InstallationPeopleBookfor Windows 2000 - Based Systems and WebLogic8.1

Published May 12, 2004

EnterpriseOne Tools 8.93Web Server InstallationPeopleBook

Copyright © 2004 PeopleSoft, Inc. All rights reserved.

All material contained in this documentation is proprietary and confidential to PeopleSoft, Inc.("PeopleSoft"), protected by copyright laws and subject to the nondisclosure provisions of the applicablePeopleSoft agreement. No part of this documentation may be reproduced, stored in a retrieval system, ortransmitted in any form or by any means, including, but not limited to, electronic, graphic, mechanical,photocopying, recording, or otherwise without the prior written permission of PeopleSoft.

This documentation is subject to change without notice, and PeopleSoft does not warrant that the materialcontained in this documentation is free of errors. Any errors found in this document should be reported toPeopleSoft in writing.

The copyrighted software that accompanies this document is licensed for use only in strict accordance withthe applicable license agreement which should be read carefully as it governs the terms of use of the soft-ware and this document, including the disclosure thereof.

PeopleSoft, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, PeopleTalk, and Vantive are registeredtrademarks, and Pure Internet Architecture, Intelligent Context Manager, and The Real-Time Enterprise aretrademarks of PeopleSoft, Inc. All other company and product names may be trademarks of their respectiveowners. The information contained herein is subject to change without notice.

Open Source Disclosure

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE ISPROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PAR-TICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWAREFOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENT-AL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIM-ITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, ORPROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LI-ABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCEOR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF AD-VISED OF THE POSSIBILITY OF SUCH DAMAGE.

PeopleSoft takes no responsibility for its use or distribution of any open source or shareware software ordocumentation and disclaims any and all liability or damages resulting from use of said software or docu-mentation.

Table of Contents

Introduction .................................................................................................................. 1Before You Begin ................................................................................................... 1Naming Conventions for WebLogic Components .......................................................... 2

Installing and Configuring the Web Server ....................................................................... 3Configuring JDBC Drivers ........................................................................................ 3

Microsoft SQL Server 2000 Driver for JDBC ....................................................... 3Obtaining the JDBC driver ........................................................................ 3Installing the JDBC Driver ........................................................................ 3

➤ To Install the JDBC driver ............................................................ 3Oracle ........................................................................................................... 4

Obtaining the JDBC driver ........................................................................ 4Configuring the tnsnames.ora File .............................................................. 4

DB2/UDB ..................................................................................................... 4Obtaining the JDBC driver ........................................................................ 4Cataloging the DB2/UDB database ............................................................. 4

➤ To Catalog the DB2/UDB database ................................................ 4Installing the Web Server .......................................................................................... 5

➤ To Install the Web Server ............................................................................. 5Adding the Web Server to the EnterpriseOne Installation Plan ....................................... 17

➤ To add the Java Server to the EnterpriseOne Installation Plan ............................ 17Configuring JAS Logging ....................................................................................... 18

Sample jdelog.properties file ........................................................................... 19

Running the Web Server .............................................................................................. 21Starting the WebLogic Application Server ................................................................. 21

➤ To start the WebLogic Application Server ..................................................... 21Stopping the Web Server ........................................................................................ 22

➤ To stop the Web Server .............................................................................. 22Accessing the Web Server ...................................................................................... 22

➤ To access the Web Server ........................................................................... 22Starting the WebLogic Administrative Console ........................................................... 23

➤ To Start the WebLogic Administrative Console .............................................. 23Extracting the EnterpriseOne Help files ..................................................................... 23

➤ To extract the EnterpriseOne Help files (8.9) .................................................. 24➤ To extract the EnterpriseOne Help files (8.10) ................................................ 24

Setting up the Inherited Trust system on the Portal ...................................................... 25➤ To set up the Inherited Trust system on the Portal ............................................ 26

Setting up AutoComplete on the Web Server .............................................................. 27➤ To activate the AutoComplete feature in Internet Explorer ................................ 27

Generating EnterpriseOne Serialized Objects ................................................................. 29Before You Begin ................................................................................................. 29Installing eGenerator ............................................................................................. 30

Before You Begin ......................................................................................... 30Setting the Default Storage Parameter ............................................................... 30

➤ To set the default storage parameter (Oracle only) ................................... 30➤ To set the default storage parameter (SQL only) ...................................... 30

Setting up the Win32 Client to Generate Serialized Objects ................................... 31➤ To set up the EnterpriseOne client to generate serialized objects ................. 31

Configuring the Generation Machine ................................................................ 31

8.93, version 1.1 Web Server Installation v

➤ To copy the genapp.ini file to the default Windows directory ..................... 31➤ To copy the jas.ini file and tnsnames file to the generation machine ............ 32

Preparing EnterpriseOne for Serialized Objects ................................................... 32➤ To populate the Data Dictionary ........................................................... 32➤ To populate the global specs ................................................................ 33

Modifying gen.bat ......................................................................................... 33➤ To modify gen.bat ............................................................................. 33

Logging In ........................................................................................................... 35Before You Begin ......................................................................................... 35jas.ini Settings .............................................................................................. 36JDBj.ini Settings ........................................................................................... 36Running the eGenerator Diagnostic Tool ........................................................... 36Generate to the Web Server ............................................................................. 38

➤ To generate to the web server .............................................................. 38Bypass the Web server and generate directly to a database .................................... 41

➤ To generate objects directly to a database ............................................... 42Configuring eGenerator .......................................................................................... 43

Setting eGenerator Options ............................................................................. 44➤ To set eGenerator options ................................................................... 44Generation Modes ................................................................................. 46

Sequential Generation .................................................................... 46Parallel Generation ........................................................................ 46

Choosing the HTMLOverrides File ................................................................... 46➤ To Choose the HTMLOverrides File ..................................................... 46

Choosing Languages ...................................................................................... 47➤ To choose languages .......................................................................... 47

Configuring the genapp.ini File ........................................................................ 48Generating All Standard Serialized Objects ................................................................ 50

Running the TAM Analyzer ............................................................................ 51➤ To run the TAM Analyzer ................................................................... 51

Generating all objects .................................................................................... 52➤ To generate all EnterpriseOne objects ................................................... 52

Verifying the Generation Process ............................................................................. 55Checking log files ......................................................................................... 55

➤ To display the Status Log ................................................................... 56➤ To display the Error Log ..................................................................... 56

Checking Database Acknowledgements ............................................................. 56Generating Selected Objects .................................................................................... 57

Generating Objects From an Update Package ..................................................... 58Creating a Bulk Generation File ............................................................... 58

➤ To create a Bulk Generation File .................................................. 59Running the Bulk Generation File ............................................................ 59

➤ To run the Bulk Generation File ................................................... 59Generating Core Objects ................................................................................. 61

➤ To generate core objects ..................................................................... 61Generating Applications ................................................................................. 63

➤ To Generate an application ................................................................. 63➤ To generate applications by system code ................................................ 65➤ To Generate Applications by Mode ...................................................... 66

Generating Forms .......................................................................................... 67➤ To generate a form ............................................................................ 67

Generating Reports ........................................................................................ 69➤ To generate a report ........................................................................... 69➤ To generate a report version ................................................................ 69➤ To generate reports by system code ...................................................... 70

Generating NERs .......................................................................................... 72➤ To Generate NERs ............................................................................ 72

Generating Data Dictionary Items .................................................................... 73

Web Server Installation

vi Web Server Installation 8.93, version 1.1

➤ To generate Data Dictionary Items ....................................................... 73Generating Tables ......................................................................................... 74

➤ To generate tables ............................................................................. 74Generating Business Views ............................................................................. 75

➤ To generate Business Views ................................................................ 75Generating Data Structures ............................................................................. 77

➤ To generate Data Structures ................................................................ 77Converting Grid Tabs .................................................................................... 78

➤ To Convert Grid Tabs ........................................................................ 78

A. DB Password Encryption Rollout .................................................................................Introduction ......................................................................................................... 81

Solution ...................................................................................................... 81Impacted Components .................................................................................... 81

Security Kernel & JAS ........................................................................... 82Security Administration .......................................................................... 82

Configuration ............................................................................................... 82Pre-Installation Process .......................................................................................... 82

➤ To copy security tables to the Server Map data source ...................................... 83Installation ........................................................................................................... 83Things to keep in mind ........................................................................................... 85Roll-back Procedures ............................................................................................. 86Copyright ............................................................................................................ 87

B. Parameters and Values for the jas.ini file .......................................................................[SECURITY] ....................................................................................................... 93[OWWEB] .......................................................................................................... 96[PORTALCONFIGURATION] ............................................................................. 100[CACHE] .......................................................................................................... 108[SERVER COMPONENTS] ................................................................................. 109[JDENET] ......................................................................................................... 110[SERVER] ......................................................................................................... 111[LOGIN] ........................................................................................................... 112[LOGS] ............................................................................................................. 113[TRANSACTIONS] ............................................................................................ 114[ERPINTERACTIVITY] ...................................................................................... 114[WEB GUI] ....................................................................................................... 116

C. Parameters and Values for the jdbj.ini file .....................................................................PeopleSoft EnterpriseOne Data-Specific Sections ...................................................... 119

[JDBj-BOOTSTRAP SESSION] .................................................................... 119[JDBj-BOOTSTRAP DATA SOURCE] .......................................................... 120[JDBj-SPEC DATA SOURCE] ..................................................................... 121

General Sections ................................................................................................. 122[JDBj-JDBC DRIVERS] .............................................................................. 123[JDBj-ORACLE] ........................................................................................ 123[JDBj-LOGS] ............................................................................................. 124[JDBj-CONNECTION POOL] ...................................................................... 124[JDBj-RUNTIME PROPERTIES] .................................................................. 125

Web Server Installation

8.93, version 1.1 for Windows 2000 - Based Systems and WebLogic 8.1 vii

viii This page intentionally left blank

IntroductionThis document describes the installation and configuration of a PeopleSoft HTML Web Server (referred toas "Web Server" thorughout the rest of this document) running EnterpriseOne on a Windows 2000 plat-form. The installation process consists of:

• Installing and Configuring the Web Server

• Running the Web Server

• Generating EnterpriseOne Serialized Objects

Caution

If you plan on running an older Tools Release concurrently with this Tools Release, read the ap-pendix below before you install this Tools Release, and perform the tasks in the order indicated:

Appendix A: DB Password Encryption Rollout

The PeopleSoft Web Server can be installed on either an IBM WebSphere (4.0 or 5.0) or BEA WebLogic8.1 Application Server. This document describes how to install the Web Server on a WebLogic ApplicationServer. To install the Web Server on a WebSphere Application Server, refer the EnterpriseOne 8.9 WebServer Installation PeopleBook for WebSphere and your platform.

For information about installing multiple Tools Releases on the same Java Server, see the following docu-ment on the Knowledge Garden:

https://knowledge.jdedwards.com/jdecontent/WWAT/TipsTechniques/ttdk_JAS_Multi_Foundations.doc

If you are using the Portal, you can find documentation on the use of this product by searching the Know-ledge Garden for the term: "Collaborative Portal document."

Note

This document provides the instructions necessary to install the Web Server. However, we assumethat the installer has basic knowledge of Windows and System Administration.

Before You Begin

• You must install the BEA WebLogic 8.1 Application Server on the same machine as the Web Server.For instructions on how to install the WebLogic 8.1 Application Server, refer to the following pageonthe BEA website:

http://edocs.bea.com/wls/docs81/install/index.html

• Verify that your system meets the Minimum Technical Requirements (MTRs) for the hardware andsoftware required to install a Web Server running on your particular platform. Navigate to the followingweb page on the Knowledge Garden for a list of these requirements:

8.93, version 1.1 Web Server Installation 1

https://knowledge.jdedwards.com/jdecontent/WWAT/TipsTechniques/ttdk_JAS_Multi_Foundations.doc

http://edocs.bea.com/wls/docs81/install/index.html

Home->Product->Software Engineering->Minimum Technical Requirements (under Platform Techno-logies)

• In order to implement the Portal, you must complete special instructions for SARs 5274158, 5897371,and 6107095.

• Verify that a EnterpriseOne ™enterprise server is properly installed and functioning.

Naming Conventions for WebLogic ComponentsFor WebLogic components, we recommend you use the following naming conventions. Using these namesallows you to differentiate between various web server components from different instances of Enter-priseOne. A set of all the components in the table defines a single instance of EnterpriseOne.

Application Server Recommended Name

Application Server AS_JS_[portNumber]

Virtual Host VH_JS_[portNumber]

Web Application EA_JS_[portNumber]

Standard Out SystemOut.log

Standard Error SystemErr.log

where [portNumber] is the port number assigned to that instance of the Application Server.

For example, if you only have one instance or port of EnterpriseOne™, you can define [portNumber] as“7003,” and the Application Server name for that instance would be: AS_JS_7003.

Introduction

2 Web Server Installation 8.93, version 1.1

Installing and Configuring the Web ServerIn this chapter you will use a PeopleSoft installation program - the JAS Installer, to install the Web Server,configure an instance of the web server in WebLogic, and configure the jas.ini file.

Complete the following tasks to install the Web Server and supporting software:

• Configuring JDBC Drivers [3]

• Installing the Web Server [5]

• Adding the Web Server to the EnterpriseOne Installation Plan [17]

• Configuring JAS Logging [18]

Configuring JDBC DriversThe EnterpriseOne Web Server requires JDBC drivers to connect to the EnterpriseOne/ERP data server.The EnterpriseOne Web Server Install wizard will help you configure the drivers for WebLogic. At thispoint, you need to obtain the JDBC drivers for the database you are using and install them on the server.

Microsoft SQL Server 2000 Driver for JDBC

Complete the following sections to configure the SQL 2000 database.

Obtaining the JDBC driver

Microsoft provides a type 4 JDBC driver for SQL Server 2000 with full support at no additional charge tolicensed customers. Download the appropriate JDBC driver directly from Microsoft's website.

Installing the JDBC Driver

Complete the following task to install the SQL Server 2000 Type 4 driver. Note that installation document-ation comes with the download.

➤ To Install the JDBC driver

1. From Windows Explorer, execute the setup.exe file that you downloaded from the Microsoft website.

2. On the Welcome screen, click Next.

3. On the Legal Agreement screen, select Accept the terms of the license agreement thenclick Next.

4. On the Setup Type screen, verify that the setup type is Complete.

5. Click Next.

6. On the Ready to Install the Program screen, click Install.

7. From Windows Explorer, navigate to the following directory:


x:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib

where x: is your Windows system drive.

8. Verify that the following files exist.

• mssqlserver.jar

• msbase.jar

• msutil.jar

Oracle


The JDBC driver for Oracle will automatically be downloaded to your system when you install Oracle cli-ent or server. Verify that the classes12.zip file is present in the /jdbc/lib/ directory under Oracledirectory. If this file is not present, download it into the above directory from the Oracle web site.

Configuring the tnsnames.ora File

You must configure the tnsnames.ora file if you are using an Oracle database on the Web Server. Thisfile defines the connection between the Oracle database and the Java server. If your configuration uses anOracle database, you can copy the tnsnames.ora file on your EnterpriseOne client installation to a direct-ory on the Java server. You will either define a path to this file or to an existing tnsnames.ora file on theJava server when you configure the jdbj.ini file.

DB2/UDB

Complete the following tasks to obtain and configure the JDBC driver for DB2/UDB.


If you have not yet installed a DB2/UDB client or server on the Web Server Java server, refer to the follow-ing link for installation instructions:

http://www-3.ibm.com/software/data/db2/

The JDBC driver for DB2/UDB is delivered with DB2/UDB server or client installation.

Cataloging the DB2/UDB database

On the Web Server, you must run the DB2/UDB Client Configuration Assistant program and access a fileon the Deployment server that catalogs the DB2/UDB databases. Refer to the "EnterpriseOne InstallationGuide" for other options to catalog databases and for how to create the oneworld.spf file.

➤ To Catalog the DB2/UDB database

1. From your Desktop, click on Start->Programs->IBM DB2->Client Configuration Assistant.

2. If the Add Database screen appears, close it.

Installing and Configuring the Web Server


http://www-3.ibm.com/software/data/db2/

3. Click Import at the bottom of the screen.

4. Click on Network and browse to the B9 directory on the Deployment server.

5. Open the oneworld.spf file in the Client directory.

6. On both the Java Server and Generation machine, open the db2cli.ini file.

This file is typically located under DB_HOME\SQLLIB\

7. Comment out or remove the LobCachSize paramenters under database aliases associated with Enter-priseOne. These parameters are not applicable to either the Java Server or the Generation machine.

Installing the Web ServerUse the InstallShield Wizard to install the PeopleSoft Java Application Server on your computer.

➤ To Install the Web Server

1. Insert the PeopleSoft Java Installation CD into the CD ROM drive, or download the platform-specificWeb Server installation software from the Update Center on the Knowledge Garden.

2. From Windows Explorer, navigate to the base directory of the Java Server Installation CD, or navigateto the directory where you downloaded the installation software.

3. Select one of the following options:

• If you are running the Installer from the CD, double click on setup.exe.

• If you are running the Installer from the Update Center, double click on 8.93J_IntelNT.exe,where xx is the number of the Tools Release (for example, 8.93J_IntelNT.exe).

It can take a few minutes for the PeopleSoft Installer program to load.


8.93, version 1.1 for Windows 2000 - Based Systems and WebLogic 8.1 5

4. Click Next.

The program displays the default installation path for the Web Server.

5. If you want to install the PeopleSoft Java Server in a different directory, click Browse and select a dif-ferent directory.



6. Click Next.

7. Choose HTML Web Server for WebLogic 8.1.

8. Click Next.

The program displays the default installation directory (<BEA_HOME>) where the WebLogic softwareis installed:



x:\BEA.

9. If you installed the WebLogic software in a different directory other than the default path, enter thatpath in the Directory Name field.

10. Click Next.

The program displays the default domain directory for the WebLogic Application Server.

11. If you want to define an existing PeopleSoft domain directory, enter that path in the DirectoryName field. Otherwise, accept the default path

12. Click Next.

If you accepted the default path (to create a new domain), the program displays the following screen.If you are configuring an existing domain, skip to Step 16 [10].



13. Click Next to verify the WebLogic domain you selected.

14. Enter the Administration Server Port, or accept the default value.

15. Click Next.



The JAS Server Setup screen displays the default settings required to set up the Java server in theWebLogic Server.

16. Review the field descriptions below and verify or change the field values as necessary.

• JAS Server Port Number:

The install program will create a new PeopleSoft Application Server (AS_JS_portNumber) withthe port you select.

• JAS Server Name:

Enter the name of the JAS Server (for example, AS_JS_portNumber).

• Enterprise Application Name

Enter the name of the Enterprise Application (for example, EA_JS_portNumber).

17. Click Next.



18. The remaining screens configure the critical settings in the jdbj.ini file. The Database System Set-tings screen contains the critical settings for the [JDBj BOOTSTRAP SESSION] section of the jd-bj.ini file. See [JDBj-BOOTSTRAP SESSION] for additional information about these settings,which define the connection to the EnterpriseOne database on the EnterpriseOne database server. Con-sult your CNC administrator, or review the EnterpriseOne Installation guide for more informationabout these settings.

Most of these fields will default to their correct values.

Tip

If during the course of this installation you mistakenly input the wrong value for one of the set-tings in either the jas.ini or jdbj.ini file, you can open these files and manually edit the set-ting. Refer to Appendix B: Parameters and Values for the jas.ini file for information about each ofthese settings.

Verify the following fields and make changes if necessary.

• Database Type: Oracle, MS SQL, UDB/DB2, or DB2 (iSeries)

• Default User: JDE

• Default Password: JDE

• Default Environment: enter the default environment. (For example, DV9)

• System Datasource: System - B9

• Database User Role: *ALL



For more information on the [JDBj-BOOTSTRAP DATA SOURCE] values, see [JDBj-BOOTSTRAPDATA SOURCE] in Appendix B: Parameters and Values for the jas.ini file.

19. Click Next.

20. The screen that appears next depends on the database you selected as your Database Type in thescreen above. Complete the following screen that corresponds to the Database Type you selected.

For Oracle. The Oracle Database Settings screen contains the critical settings for the[JDBj-BOOTSTRAP DATA SOURCE] section of the jdbj.ini file. See [JDBj-BOOTSTRAPDATA SOURCE] for additional information about these settings, which define the connection to theEnterpriseOne database on the EnterpriseOne database server. Consult your CNC administrator, or re-view the EnterpriseOne Installation guide for more information about these settings.

• Object Owner: SY9

• OCM Server

Name of the server where the OCM table resides. This server is typically the enterprise server orthe database server. This field populates the Server= setting in the [JDBj-BOOTSTRAP DATASOURCE] section of the JDBj.ini file.

• Database: Enter the connect string.

For MS SQL. The SQL Database Settings screen contains the critical settings for the[JDBj-BOOTSTRAP DATA SOURCE] section of the jdbj.ini file. See [JDBj-BOOTSTRAPSESSION] for additional information about these settings, which define the connection to the Enter-priseOne database on the EnterpriseOne database server. Consult your CNC administrator, or reviewthe EnterpriseOne Installation guide for more information about these settings.



Complete or verify the following fields (most will default to their correct values).

• OCM Server

Name of the server where the OCM table resides. This server is typically the enterprise server orthe database server. This field populates the Server= setting in the [JDBj-BOOTSTRAP DATASOURCE] section of the JDBj.ini file.

• OCM Server Port: SQL Database Port on which OCM is running.

• Database Name for System Tables: Enter the name of the library that includes the OCMmappings. Typically, this is SY9.

• Object Owner: SY9.

For UDB/DB2. The UDB Database Settings screen contains the critical settings for the[JDBj-BOOTSTRAP DATA SOURCE] section of the jdbj.ini file. See [JDBj-BOOTSTRAPSESSION] for additional information about these settings, which define the connection to the Enter-priseOne database on the EnterpriseOne database server. Consult your CNC administrator, or reviewthe EnterpriseOne Installation guide for more information about these settings.



Complete or verify the following fields (most will default to their correct values):

• OCM Server: Name of the server where the OCM table resides. This server is typically the enter-prise server or the database server. This field populates the Server= setting in the[JDBj-BOOTSTRAP DATA SOURCE] section of the JDBj.ini file.

• OCM Server Port: Database Port on which OCM is running.

• Object Owner: SY9

• Database: Enter the name of the database.

21. Click Next.



22. Browse to the path of the directory that contains the JDBC drivers you installed earlier in the installa-tion.

23. Click Next.

24. The Environment Settings screen contains the critical settings for various sections of the jas.ini file.These values define how the JAS server is configured (what path codes are used, what enterprise serv-



er to connect to, etc.).

Verify or change the following fields as needed.

• Enterprise Server Platform: Choose the platform of your Enterprise Server

• Windows

• Unix

• iSeries

• Enterprise Server Name: Enter the name of your Enterprise Server

• Default Environment: Use the same value that you used for the default environment in Step 18[11] (for example, DV9)

• Enterprise Server Port:6011

• UBE Queue: QB9

• Temporary File Directory: Defaults to a standard temporary folder on the local drive.

Change this value to a valid temporary directory on your system.

25. Click Next.

26. On the verification screen, check the information carefully to ensure that your input values are correct.

To make changes, click Back, until you find the value you wish to change.



27. After verifying the information, click Next.

The program begins installing the PeopleSoft Web Server. This process can take several minutes tocomplete.

28. Click Finish to complete the installation.

Adding the Web Server to the EnterpriseOne Installation PlanIn order for the Web Server to communicate with EnterpriseOne, the Java server must be added to the En-terpriseOne installation plan and defined as part of the EnterpriseOne environments. Follow the steps belowto complete two chapters in either the EnterpriseOne Installation guide or the EnterpriseOne Upgradeguide.

➤ To add the Java Server to the EnterpriseOne Installation Plan

Perform the following steps on the deployment server:

1. Start the tasks in the chapter titled "Adding a Server to an Existing Configuration" in the Planner Util-ity section of the EnterpriseOne Installation (or Upgrade) guide.

Sign on to EnterpriseOne™ as user JDE in the planner environment, and double-click Add-on ServersPlan from the System Installation Tools menu (GH961). Follow the instructions in the EnterpriseOneInstallation/Upgrade guide to define your plan.

2. On the Add on Servers Plan - [Server Add] screen, select the JAS server option and click OK.

3. Click OK.

4. On Add-on Server Plan [JAS Server Revisions], complete the following fields:

• Machine Name

Name of the JAS server

• Description

Description of the JAS server

• Release: 8.9

• Host Type

Click the visual assist button and choose the type of server you are adding to the plan. The defaultvalue of 50 is for the Intel NT server.

• Primary User

JDE

• Installation Path

Path to the \jas directory on the JAS server. For example, x:\Program Files\PeopleSoft\JAS

• HTTP Port:



Enter the port number on which you configured the Web Server.

• Protocol: http

5. Click OK.

6. Complete the following screens until you get to the Add-on Servers Plan - [Select Environments]screen.

7. On the Add-on Servers Plan - [Select Environments] screen, select a J environment (for example,JPY9).

8. Accept the default data sources.

9. Repeat the above step for all other J environments that you want to add to the plan.

10. Complete the following steps in the chapter to finalize the installation plan.

11. On Work with Installation Plans, click Find, then expand your new plan and click the enterprise serv-er.

12. Click Add.

13. On Enterprise Server, click Select.

14. On Add on Servers Plan - [Machine Search], choose the enterprise server that will store the Java ob-jects and click Select.

15. On Add on Servers Plan - [Enterprise Server Revisions], click on Environments in the Form menu.

16. On Add on Servers Plan - [Machine Environment Revisions], select the environments that will not beinstalled with this plan and click Delete.

17. Click on the Environment field in an empty row then click the visual assist button.

18. On Add on Servers Plan - [Environment Search], choose a J environment and click Select.

19. Repeat the above step for all J environments you installed.

20. On Add on Servers Plan - [Machine Environment Revisions], click OK.

21. On Add on Servers Plan - [Enterprise Server Revisions], click OK.

22. Accept the default data sources and complete the remaining screens.

EnterpriseOne will finalize the additions to your plan.

23. Complete the Installation Workbench section of the EnterpriseOne Installation (or Upgrade) guide toconfigure the Java server in EnterpriseOne.

Configuring JAS LoggingStarting with Release 8.9, JAS uses new logging API's to monitor JAS processes and write the informationto log files. The new logging process uses a file called jdelog.properties to configure the location of



the log files and set logging parameters. By default, the jdelog.properties file is located in the follow-ing path:

C:\Program Files\PeopleSoft\JAS\EA_JS_portNumber\webclient.war

The sample jdelog.properties file is shown below:

Sample jdelog.properties file

# This is a sample configuration file for root configuration

jdelog.rootLogger=DEBUG,JDELOG,JASLOGjdelog.loggerFactory=com.jdedwards.base.logging.log4j.JdeLoggerFactoryjdelog.reloadInterval=60

# These are the settings for file handlers.jdelog.handler.JDELOG=com.jdedwards.base.logging.log4j.FileHandlerjdelog.handler.JDELOG.File= webclient.war/logs/jderoot.logjdelog.handler.JDELOG.Level=ERRORjdelog.handler.JDELOG.Append=TRUEjdelog.handler.JDELOG.MaxBackupIndex=1jdelog.handler.JDELOG.MaxFileSize=10MBjdelog.handler.JDELOG.format=com.jdedwards.base.logging.log4j.DefaultFormat

# These are the settings for file handlers.jdelog.handler.JASLOG=com.jdedwards.base.logging.log4j.FileHandlerjdelog.handler.JASLOG.File=webclient.war/logs/jas.logjdelog.handler.JASLOG.Level=ERRORjdelog.handler.JASLOG.Append=TRUEjdelog.handler.JASLOG.MaxBackupIndex=1jdelog.handler.JASLOG.MaxFileSize=10MBjdelog.handler.JASLOG.format=com.jdedwards.base.logging.log4j.DefaultFormat

#This is added for debug logging. Please uncomment following to start debug.#jdelog.Debug=DEBUG, jasdebug#jdelog.handler.jasdebug=com.jdedwards.base.logging.log4j.FileHandler#jdelog.handler.jasdebug.File=webclient.war/logs/jasdebug.log#jdelog.handler.jasdebug.Level=DEBUG

The sample above shows parameter settings for three different log files: jde.log, jas.log, and jasde-bug.log. The list below describes each of the parameters for the jde.log file, where JDELOG is thehandler name. This name can be anything, but should match the handler name given to a logger, root or auser.

Use these descriptions as a guide to modify the parameters for each of the log files.

Defines the interval in which the jdelog.properties file is reloaded by the Web Server.

This is a global parameter that determines the time it takes for the system to update the configurationsettings after you modify the jdelog.properties file. The default value is 60 (in seconds). Youcan modify this value to specify a different interval.

Tip

If you change the value to 0, the system will never reload the updated parameters.

Defines the file handler settings for the root.Defines the location and name of the file.

You must modify this path to specify a directory for your log file. The path is relative to the JAS in-stallation directory.



Note

When you type the path, make sure you use double back slashes “\\" while specifying the file path,or you can use a single forward slash “/” instead. Never use a single back slash “\” for specifying afile path.

Defines the log level for the handlerDefines whether to append new log information to the existing file when your application is restarted.Defines the number of backup files the system will create when the log file size becomes larger thanthe MaxFileSize specified below.Defines the maximum size of the log file.Defines the format for logging messages.



Running the Web ServerWhen you first install the PeopleSoft HTML Web Server, you must stop the WebLogic Application Serverand then restart it.

This section includes the following tasks:

• Starting the WebLogic Application Server [21]

• Stopping the Web Server [22]

• Accessing the Web Server [22]

• Starting the WebLogic Administrative Console [23]

• Setting up the Inherited Trust system on the Portal [25]

• Setting up AutoComplete on the Web Server [27]

Tip

In order to enable any modifications, you should always stop and restart the WebLogic Applica-tion Server any time you modify the configuration.

Starting the WebLogic Application Server

➤ To start the WebLogic Application Server

1. From Microsoft Windows, Select Start->Run.

2. On the command line, type cmd and click OK.

3. From the command line, navigate to the domain directory. For example:

c:\Program Files\PeopleSoft\Domain\peoplesoft

4. Run the following command to start the WebLogic Application server. (In this example, the applica-tion server is AS_JS_7003):

startAS_JS_7003.cmd

The program requests a username and password.

5. Enter the username and password.

The default for both values is weblogic

As WebLogic starts, the program displays a series of messages which can take several minutes tocomplete. The program displays the following message when the startup process is complete:

<Dec 29, 2003 3:25:40 PM MST> <Notice> <WebLogicServer> <BEA-000355> <Thread


"ListenThread.Default" listening on port 7003, ip address *.*>

6. Open a browser and enter the following url:

http://localhost:7003/jde/owhtml/index.html

7. On the EnterpriseOne login screen, complete the following fields:

• Username: jde

• Password: jde

Stopping the Web Server

➤ To stop the Web Server





4. Run the following command to stop the WebLogic Application server. (In this example, the applica-tion server is AS_JS_7003):

stopAS_JS_7003.cmd

Accessing the Web ServerYou can access the Web Server from any web browser connected to your network.

➤ To access the Web Server

1. Invoke the PeopleSoft Portal client by opening a browser and entering the following URL:

http://<web_server_name>:<port_number>/jde/owportal/

For example:

http://jdewebs1.jdedwards.com:7003/jde/owportal/index.html

2. Invoke the PeopleSoft HTML client by opening a browser and entering the following URL:

http://<web_server_name>:<port_number>/jde/owhtml/

For example:

http://jdewebs1.jdedwards.com:7003/jde/owhtml/

Running the Web Server


3. Invoke PeopleSoft SAW using the URL:

http://<web_server_name>:<port_number>/jde/saw/

For example:

http://jdewebs1.jdedwards.com:7003/jde/saw/

Errors are reported in the jas.log, jasdebug.log, stderr.txt and stdout.txt.

Starting the WebLogic Administrative ConsoleComplete this task if you need to access the WebLogic Administrative Console. The Administrative Con-sole can be used to administer the WebLogic Application server and modify configuration settings.

➤ To Start the WebLogic Administrative Console





4. Run the following command to start the WebLogic Application server. (In this example, the applica-tion server is AS_JS_7003):

startweblogic.cmd

The program requests a username and password.

5. Enter the username and password.

The default for both values is weblogic

6. Open a browser and enter the following url:

http://localhost:7001/console

Note

The default port number for the Administrative Console is 7001. If you are using a different portnumber, replace 7001 with the correct value in the url above.

For more information about the WebLogic Administrative Console, refer to WebLogic Server docu-mentation at the following URL:

http://edocs.bea.com/liquiddata/docs81/admin/console.html

Extracting the EnterpriseOne Help filesComplete the relevant task below to extract your version of the EnterpriseOne Help files into the owhelpdirectory. If you do not complete this task, the Help files will not be accessible from the Web Server.



http://edocs.bea.com/liquiddata/docs81/admin/console.html

Note

During the 8.93 Web Server installation process, compressed Help files for EnterpriseOne 8.9 arecopied into the owhelp directory. If you are configuring the Web Server to run with Enter-priseOne 8.10, you must get the compressed Help files from either the 8.10 Deployment Server orcopy them from a Deployment Server installation CD, as described below.

➤ To extract the EnterpriseOne Help files (8.9)

1. On the Web Server, extract the helps.cab file in the following directory:

x:\Program Files\PeopleSoft\JAS\EA_JS_<port number>\webclient.war\owhelp

2. Open the jas.ini file, and verify that the HelpPath setting in the [OWWEB] section points to theabove path where you extracted the Help files.

➤ To extract the EnterpriseOne Help files (8.10)

1. On the Web Server, navigate to the following directory:

x:\Program Files\PeopleSoft\JAS\EA_JS_<port number>\webclient.war\owhelp

2. Delete the Helps.cab file for EnterpriseOne 8.9 from the owhelp directory.

3. Complete one of the following options:

• For the following languages, continue with Step 4 [24]:

• English

• French

• Spanish

• Chinese

• For other languages, continue with Step 5 [25].

4. Complete the following substeps to extract Help files for the languages listed above.

a. Open a web browser, and download the latest Helps.cab file for your language from the UpdateCenter.

Note

To find the Help files on the Update Center, use the following search criteria:



• Type: PeopleSoft EnterpriseOne

Release: 8.10

• Search for

Enter the relevant SAR number below:

• English: 7126571

• French: 7130431

• Spanish: 7130449

• S. Chinese: 7130465

• T. Chinese: 7130473

b. Extract the helps.cab file to the owhelp directory on the WebServer.

Continue with Step 6 [25]

5. Complete the following substeps to extract Help files for languages other than those listed above.

a. Insert the EnterpriseOne 8.10 Deployment Server Setup CD #2 into the CD ROM drive.

b. Extract the helps.cab file from the Helps directory on the CD to the owhelp directory on theWebServer.

6. Open the jas.ini file, and verify that the HelpPath setting in the [OWWEB] section points to theabove path where you extracted the Help files.

Setting up the Inherited Trust system on the PortalComplete this task to set up the Secret Enterprise Key for the Inherited Trust servlets. These servlets areused to link to the Portal log in with the authentication systems of other PeopleSoft products, such as Busi-ness Intelligence (BI) and Customer Relationship Management (CRM). The Inherited Trust system allowsusers to move from product to product without the need to log in more than once; simply log into the Portaland you are automatically authenticated for other products that use the Inherited Trust system. Each systemmust be configured with the same Secret Enterprise Key and same User IDs (User Passwords need not bethe same). For information on configuring BI and CRM, refer to the configuration documents for theseproducts.

Using the instructions and the sample file below, you will add the following two new servlets to theweb.xml file:

• oneworld.owportal



• portal

These servlets define the Inherited Trust configuration. You might only need one servlet, but for maximumcompatibility, it is best to specify both.

➤ To set up the Inherited Trust system on the Portal

1. Navigate to the following directory:

x:\Program Files\PeopleSoft\JAS\EA_JS_<port number>\webclient.war\WEB-INF

This is the directory where the JAS class and resource files were deployed during installation.

2. In this directory, open the web.xml file in a text editor.

Caution

Do not modify the first servlet in the file - the Servlet Proxy Servlet. This servlet was created bythe PeopleSoft Installer during the installation process and contains critical configuration settings.

3. Using the sample file below as a template, add the oneworld.owportal servlet to web.xml file.Insert this servlet in the file after the last </servlet> end tag and before the </web-app> end tag.

Use the following settings:

• Servlet ID:Servlet_2

If that Servlet ID already exists, choose the next number in sequence.

• servlet-name, display-name, and servlet-class:

com.jdedwards.oneworld.owportal.InheritedTrustManagerServlet

• init-parameter id: Choose an exclusive ID.

• param-name: secretEnterpriseKey

• param-value: set with an Arbitrary Enterprise Key value.

• load-on-startup: 0

An example of Servlet_2 is shown below:

<servlet id="Servlet_2"> <servlet-name>com.jdedwards.oneworld.owportal.InheritedTrustManagerServlet</servlet-name><display-name>com.jdedwards.oneworld.owportal.InheritedTrustManagerServlet</display-name><servlet-class>com.jdedwards.oneworld.owportal.InheritedTrustManagerServlet</servlet-class><init-param id="InitParam_2"> <param-name>secretEnterpriseKey</param-name><param-value>key</param-value> <description>For Inherited Trust</description></init-param> <load-on-startup>0</load-on-startup> </servlet>

4. Using the sample settings below, append the portal servlet to web.xml. Insert this servlet in the file



after the last </servlet> end tag and before the </web-app> end tag.

Use the following settings:

• Servlet ID: Servlet_3

If that Servlet ID already exists, choose the next number in sequence.

• servlet-name, display-name, and servlet-class:

com.jdedwards.portal.InheritedTrustManagerServlet

• init-parameter id: Choose an exclusive ID.

• param-name: secretEnterpriseKey

• param-value: set with an Arbitrary Enterprise Key value.

• load-on-startup: 0

An example of Servlet_3 is shown below:

<servlet id="Servlet_3"> <servlet-name>com.jdedwards.portal.InheritedTrustManagerServlet</servlet-name><display-name>com.jdedwards.portal.InheritedTrustManagerServlet</display-name><servlet-class>com.jdedwards.portal.InheritedTrustManagerServlet</servlet-class><init-param id="InitParam_3"> <param-name>secretEnterpriseKey</param-name><param-value>key</param-value> <description>For InheritedTrust</description> </init-param> <load-on-startup>0</load-on-startup></servlet>

5. Save the changes to web.xml.

6. Restart the Web Application Server.

Setting up AutoComplete on the Web ServerThe AutoComplete feature in HTML forms records information entered into text fields on EnterpriseOneforms. Internet Explorer saves the AutoComplete information in an encrypted format for the user based onthe PeopleSoft EnterpriseOne form name, the input field name and URL of the Web Server. The next timethe user open the form and begin typing in a text field with the same name, an AutoComplete box appearsand provides the user with a list of previously used data. The user can select a value from the AutoCom-plete list box using the arrow keys.

To set up AutoCorrect on the Web Server, complete the following tasks:

• Refer to the [OWWEB] setting of the jas.ini file, and activate the AutoComplete setting.

• Each user must complete the task below to verify that the AutoComplete feature is activated on InternetExplorer.

➤ To activate the AutoComplete feature in Internet Explorer



1. Open Internet Explorer.

2. From the pull-down menu, select Tools->InternetOptions

3. On the Internet Options form, choose the Content tab, then click the AutoComplete button.

4. On the AutoComplete form, ensure the Forms option is checked.

5. Click OK on the AutoCompleteform.

6. Click OK on the Internet Options form.



Generating EnterpriseOne Serialized ObjectsIn order to run the Web Server, the server must have access to a set of serialized EnterpriseOne™ JAS ob-jects. These objects can be generated directly from EnterpriseOne™ objects using the appropriate set of En-terpriseOne specifications.

To generate EnterpriseOne™ serialized objects requires a specific machine configuration. While it is pos-sible to configure a web server to generate EnterpriseOne™ serialized objects, the recommended method isto dedicate a separate generation machine for this process. Navigate the following path on the KnowledgeGarden for a list of all requirements for the generation machine:

Home->Employee->Product->Software Engineering->Platform Technologies->Minimum Technical Re-quirements ->Current Products

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

Tip

JDE strongly recommends that you generate all objects so that JAS is working with the samespecs as your EnterpriseOne™ Windows clients. Although we ship pre-generated objects for allplatforms, the ability to successfully generate objects is key to implementing the Web Server.Since generating JAS objects is equivalent to building a package for EnterpriseOne™ clients, youmust be able to generate objects to ensure a complete and successful implementation.

Complete the tasks below to install eGenerator and generate EnterpriseOne™ JAS objects from a set of En-terpriseOne™ objects.

To generate serialized objects for the Java server, your developers must install and use the eGenerator, aPeopleSoft tool that turns EnterpriseOne™ specifications into Java code, which allows you to access Enter-priseOne™ applications in HTML. The EnterpriseOne™ forms and applications that you generate usingthe tool are HTML objects. EnterpriseOne stores the objects in a database and retrieves them at runtime.

Complete the following procedures to install and run eGenerator:

• Installing eGenerator [30]

• Logging In [35]

• Generating All Standard Serialized Objects [50]

• Verifying the Generation Process [55]

• Generating Selected Objects [57]

Before You BeginEnsure that you have installed and are running a EnterpriseOne client that is running at the same Tools Re-lease level as the Web Server. In this task you will configure the EnterpriseOne client as the generation ma-chine. For instructions on installing a EnterpriseOne client, see the EnterpriseOne Installation Guide forWindows-Based Systems.


Installing eGeneratorThis topic discusses the tasks you follow to install the eGenerator:

• Setting the Default Storage Parameter [30]

• Setting up the Win32 Client to Generate Serialized Objects [31]

• Configuring the Generation Machine [31]

• Preparing EnterpriseOne for Serialized Objects [32]

• Modifying gen.bat [33]

Before You Begin

• Verify that the paths indicated in the gen.bat file on your generation machine are valid for your con-figuration. If needed, change them to point to the correct local jar files on your generation machine.

• Complete this task if you are using DB2 UDB on the Enterprise Server. On the Generation machine,open the db2cli.ini file and comment out or remove the LobCachSize paramenters under databasealiases associated with EnterpriseOne.

This file is typically located under DB_HOME\SQLLIB\.

Setting the Default Storage Parameter

The default storage parameter on your EnterpriseOne™ database might not allow enough space to transferall the standard EnterpriseOne™ Java objects. To avoid this problem, complete the task below that is relev-ant to your database:

• Set the default storage parameter (Oracle only)

• Set the default storage parameter (SQL only)

➤ To set the default storage parameter (Oracle only)

• Log in to the Oracle database and enter the following command:

Alter tablespace xx9T default storage (maxextents unlimited);

where "xx" is the environment, and 9 is the release of J.D. Edward's ERP software to which you areinstalling the Java objects. (For example, use "PY9T" for the 8.9 Prototype environment).

➤ To set the default storage parameter (SQL only)

• Open the SQL database and set your database Maximum File Size parameter to "Unrestrictedfilegrowth."

Complete this step for each environment (for example, PY9) to which you are installing the Java ob-

Generating EnterpriseOne Serialized Objects


jects.

Setting up the Win32 Client to Generate Serialized Objects

Once you install a EnterpriseOne™ client, you can use this machine to generate serialized objects.

➤ To set up the EnterpriseOne client to generate serialized objects

1. In Windows NT Explorer, find the directory that stores the jde.ini file. (usually c:\winnt)

2. In the [Interactive Runtime] section of the jde.ini file, add the following parameter and value:

WebAdmin=1

Setting the value for this parameter to 1 allows you to view and use the eight tabs in the eGenerator,thus enabling the generation of all serialized objects for the default user.

3. Click Save.

Note

Any changes to the jde.ini file will be overwritten when you deploy a full package to the Genera-tion machine. To preserve these settings, you can copy the jde.ini file to a backup directory. Afteryou deploy a new package, you can copy the customized settings for the Java generation (listedbelow) from the [Interactive Runtime] section of the backup file to the updated jde.ini file. Do notoverwrite the entire updated jde.ini file with the backup file after a package build. Doing so candelete updated settings that are required by the new package.

Configuring the Generation Machine

Starting with Service Pack 21, the JAS build is automatically installed in the x:\b9\system\generatordirectory when you install the EnterpriseOne client. The \generator directory is preconfigured, and con-tains most of the files you need to run EnterpriseOne properly. However, you need to complete to followingtasks set up a few of the configuration files:

• To copy the genapp.ini file to the default Windows directory [31]

• To copy the jas.ini file and tnsnames file to the generation machine [32]

➤ To copy the genapp.ini file to the default Windows directory

1. On the generation machine, navigate to the x:\b9\system\generator directory, and locate thegenapp.ini file.

2. Copy the genapp.ini file to the default Windows directory on your generation machine.

The default Windows directory for Windows 2000 is x:\WINNT



➤ To copy the jas.ini file and tnsnames file to the generation machine

• On the JAS server, navigate to the x:\Program Files\PeopleSoft\JAS\EA_JS_<portnumber>\webclient.war\WEB-INF directory, and copy the following files to thex:\b9\system\Generator\WEB-INF directory on the generation machine:

• jas.ini

• tnsnames.ora (Oracle only)

• jdelog.properties

• jdbj.ini

Note

The above directories are the default locations of the files, but the directory paths might be differ-ent on your machines.

The tnsnames file might reside in a different place on the JAS server. To find the location of thisfile, open the JDBj.ini file, and note the value (directory path) of the following setting:

• tns setting in the [JDBj-Oracle] section (Oracle only)

Preparing EnterpriseOne for Serialized Objects

Before you generate serialized Java objects in EnterpriseOne, complete the following tasks to populate theData Dictionary and global specs on the Java generation machine:

• Populating the Data Dictionary

• Populating the global specs

➤ To populate the Data Dictionary

1. On the Java generation machine, log on to a valid local environment in EnterpriseOne™.

2. In the Fast Path, type BV and press Enter.

3. On Batch Applications - [Work with Batch Versions - Available Versions], type R92TAM in theBatch Application field.

4. Click Find.

5. Choose the XJDE001 version and click Select.

6. On Batch Applications - [Version Prompting], click Advanced on the form menu.



7. On Batch Applications - [Advanced Version Prompting], click Override Location.

8. Click OK.

9. On Batch Applications - [Version Prompting], click Submit.

10. On Batch Applications - [JDE Data Sources], choose Local and click Select.

The application starts a UBE that populates databases stored in the x:\b9 directory. This processruns for an hour or more.

11. When the process is complete, copy the following files from the x:\b9 directory to the \spec direct-ory under the path code of the environment you will use to generate the serialized Java objects (for ex-ample, x:\b9\PY9\spec):

• dddict.xdb

• ddtext.xdb

• dddict.ddb

• ddtext.ddb

➤ To populate the global specs

1. In the Fast Path, type BV and press Enter.

2. On Batch Applications - [Work with Batch Versions - Available Versions], type R98CRTGL in theBatch Application field.

3. Click Find.

4. Choose the XJDE001 version and click Select.

5. On Batch Applications - [Version Prompting], click Advanced on the form menu.

6. On Batch Applications - [Advanced Version Prompting], click Override Location.

7. Click OK.

8. On Batch Applications - [Version Prompting], click Submit.

9. On Batch Applications - [JDE Data Sources], choose Local and click Select.

The application starts a UBE that runs for an hour or more.

Modifying gen.bat

eGenerator includes a bat file (gen.bat) that contains a list of standard configuration settings. These set-tings must be modified for your environment.

➤ To modify gen.bat



1. From Windows Explorer, navigate to the x:\b9\system\Generator directory on your generationmachine.

2. Right click on gen.bat, and choose Edit.

3. In the gen.bat configuration files, change the following settings:

Parameter Setting

set JDK= Path to the location of the JDK application used by WebLogic. Thispath is typically x:\BEA\jdkxxx\java

set JAS INI= Path to the location of the jas.ini file. (Required for direct generationonly.) Typically, this path is:

x:\b9\system\Generator\WEB-INF

Note

The gen.bat program assumes that the jdbj.ini file resides inthe same location as the jas.ini file. Make sure both of thesefiles are located in the path you enter.

set DBDRIVERS= Paths and file names of the database JDBC drivers.

(Required for Direct generation only)

Enter the path to the JDBC driver for your particular database:

For Oracle:classes12.zip

For SQL 2000: msbase.jar, mssqlserver.jar, msutil.jar

For DB2/UDB: db2java.zip

For DB2 (iSeries): jt400.jar

Safe Mode Adding the safe mode switch in gen.bat makes parallel generationmore stable and less prone to hanging. When the safe mode is activ-ated, the Generator defaults to Sequential Generation during "Gener-ate All," and inserts one object at a time to the serialized database.Safe Mode reduces the number of concurrent threads from 11 to 1,and enhances the stability, although the "safe mode" is 30% slowerthan regular parallel generation.

To activate Safe Mode, add the following (bolded) text to the com-mand line in the gen.bat file:

%JDK%\bin\java %GENERATOR_OPT% -Dmode=safe -Ddefault_path=%JAS_INI% -classpath %GEN_CLASSPATH%com.jdedwards.runtime.generator.Generator %1

JASLOGGER= WEB-INF\lib\log4j.jar;

Delete the following comment, and replace it with the path to thefolder containing the jdelog.properties file:

<folder containing jdelog.properties>.

For example, the default location for the jdelog.properties file



Parameter Setting

is the WEB-INF directory. Then the JASLOGGER setting is:

WEB-INF\lib\log4j.jar;\WEB-INF

GEN_CLASSPATH= At the end of the GEN_CLASSPATH setting, append the path to theweblogic.jar file (for examplex:\<BEA_HOME_DIRECTORY>\weblogic81\server\lib).

If the WebLogic Application Server resides on a different machine,copy the weblogic.jar file from the WebLogic installation direct-ory to the generation machine, and enter the local path to this file.

Note

If your path name to the jas.ini file or the database driver contains a space character, you needto wrap the whole path with double quote. For example, for Windows, set JAS INI="x:\ProgramFiles\PeopleSoft\JAS\EA_JS_<port number>\webclient.war\WEB-INF"

Logging InUsing eGenerator, you can generate EnterpriseOne objects in one of the following ways:

• Generate to the Web Server [38]

• Bypass the Web server and generate directly to a database [41]

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

Before You Begin

Ensure that the following files and folders reside on your workstation:

• gen.bat

• OWResource.jar

• xalan.jar

• xerces.jar

• images.jar

• classes folder

• weblogic.jar

For direct generation to a database, you also need the following additional files:



• jas.ini

• jdbj.ini

• Database drivers

• tnsnames.ora

jas.ini Settings

Verify that the following sections in the jas.ini file are configured correctly. If necessary, change themto match your configuration.

• [LOGS]

Verify that the paths to the log files point to a valid directory.

• [OWWEB]

OracleTNS= If you are using an Oracle database, verify that this setting points to the location of thetnsnames.ora file.

JDBj.ini Settings

Verify that the following sections in the JDBj.ini file are configured correctly.

• [JDBj-SPEC DATA SOURCE]

Change the settings to match your configuration. For more information on these settings, refer to[JDBj-SPEC DATA SOURCE] in Appendix C: Parameters and Values for the jdbj.ini file.

• [JDBj-ORACLE]

Even if you are not using Oracle as the database, a path to this database must be present in the follow-ing setting:

tns=c:\B9\system\Generator\tnsnames.ora

The path and tnsnames.ora file are required for the eGenerator Diagnostic tool to work. If you are notusing Oracle, use a text editor to create a blank file called tnsnames.ora and place it in the abovepath.

Running the eGenerator Diagnostic Tool

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

Note



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

When you launch gen.bat, the diagnostic tool automatically performs the following checks on the generalparameters, and displays a message asking if you want to validate the configuration for direct generation. Ifyou press y, the program also diagnoses the direct generation parameters.

The auto diagnostic tool performs the following operations:



For general use.

Operation Fatal error

Validates the location of the JDK driver. X

Reads the classpath and checks that all the classpath files are in their stated directories. X

Verifies that the genapp.ini and jde.ini file are in the default Windows directory(c:\winnt).

Verifies that jnigen.dll is in the system/bin32 folder on the Generation machine. X

Checks if the R92TAM and R98CRTGL reports must be run to populate the Data Dictionaryand global table specs.

X

Verifies that the jnigen.dll file matches the java part of the Generator. (Fatal error) X

Verifies that the serialized object tables have the correct indices.

For Direct Generation only.

Operation Fatal Error

Validates the location of the database drivers. X

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

X

Checks the location of the jas.ini file and validates the following key parameters in thefile:

The location of the tnsnames.ora and tnsnames.sql files.

The location of the jas logs.

For JAS Generation only.

Operation Fatal Error

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

X

Generate to the Web Server

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

➤ To generate to the web server



On your generation machine:

1. Under the x:\b9\system\Generator directory on your generation machine, run gen.bat. Thisbatch file calls an initialization file called genapp.ini. You can use this file to configure specific ap-plications for serialized object generation.

Note

If you do not want to run the diagnostic program, include the parameter -nodiag in the commandstatement when you run gen.bat. See the section, Running the eGenerator Diagnostic Tool [36],for more information about the autodiagnostic tool.

Tip

Ensure that the genapp.ini file is located in the WINNT directory on your generation machine.

A sample genapp.ini file is included below in the section Configuring the genapp.ini File[?].

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

Tip

After you click OK to log on to a EnterpriseOne™ environment, it can take up to 2 minutes for En-terpriseOne to complete the log on process.



3. On eGenerator, complete the following field:

• JAS Server Name

Type the name of the JAS server that you want to log in to.

The system gets the database path from your jas.ini file. eGenerator generates all objects to thisWeb server.

Note

If you are running multiple web server ports on your generation machine, type machine

name:port, where machine name is the name of your generation machine and port is the portnumber.

4. If you want to generate specs from a remote location, click the Remote Spec Folder radio button,and type the machine name and path into the field to the right of this radio button.



For example, \\machinename\c$\8.9\DV9\SPEC.

Tip

You can use this field to point to the latest specs on the deployment server and generate objectsfrom the most recent, undeployed specs.

5. Click Connect.

The system connects to the Web server that you indicated. A message appears on the status bar whenlogin is complete.

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

Bypass the Web server and generate directly to a database

Select direct generation by clicking the Direct Generation check box at the bottom of the Connect to WebServer screen of the eGenerator.



In this mode, the generator initializes a "mini" JAS Server instance on the generation machine. During gen-eration, the generator will by-pass the JAS Server and store the objects directly to the database.

Pros:

• Can generate objects before setting up the Java server.

• Faster for all forms of generation.

• Easier to maintain.

Cons:

• Harder to initially setup.

Complete this task to generate objects directly to a database.

➤ To generate objects directly to a database

1. Launch Gen.bat.

Note

If you do not want to run the diagnostic program, include the parameter -nodiag in the commandstatement when you run gen.bat. See the section, Running the eGenerator Diagnostic Tool [36],for more information about the autodiagnostic tool.

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

3. Click the Direct Generation radiobutton.



In Direct Generation Mode the eGenerator locates the database by looking for the server in the JDBj-SPEC DATA SOURCE section of the jdbj.ini file located on the local disk.

4. Click Connect.

The system bypasses the Web server and connects directly to the database specified in the jdbj.inifile.

Configuring eGeneratoreGenerator includes a number of options you can set up for your particular environment. The configurationprocess consists of the following tasks:

• Setting eGenerator Options [44]

• Choosing the HTMLOverrides File [46]

• Choosing Languages [47]



• Configuring the genapp.ini File [48]

Setting eGenerator Options

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

➤ To set eGenerator options

1. From the pull-down menu, select Options->Advanced Settings.

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



• Logging

Specify whether to log the generation process by clicking the checkboxes next to the Status andError logs. You can also enter the location of the log files. Logging is crucial for troubleshootingproblems with the generation process.

• Generation Modes

Specify if the generation of All Objects will be done in parallel mode or sequential mode bychecking the appropriate radio button.

For more information on Generation Modes, see Generation Modes [46].

• Report Licensing

Click the checkbox to generate Report Licensing after every report.

• User Option

You can generate a public version of the applications or a personal version by choosing the relev-ant option. Personal versions are only available to the person who created the versions.

• Application Entry Point

Choose this option to generate Application Entry Point information after every application.



Generation Modes

The eGenerator has the following modes for generating web objects:

• Sequential Generation [46]

• Parallel Generation [46]

Sequential Generation

In this mode the web objects are generated one after the other when you select the Generate-All Ob-jects option.

Pros:

• Most stable mode of generation

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

• Safe to use when JITI(Just in Time Install) is happening

Cons:

• Slowest mode of generation.

Parallel Generation

This is the default mode of generation. You can select this mode of generation by clicking AdvancedSettings, then clicking Parallel Generation.

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

Pros:

• Much faster than Sequential Generation, especially on multi-processor workstations.

Cons:

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

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

Choosing the HTMLOverrides File

Choose the HTML Overrides file to generate HTML objects with advanced features such as multiline edit.

➤ To Choose the HTMLOverrides File



1. Launch Gen.bat.

2. On EnterpriseOne Sign On, log in to EnterpriseOne™.


• HTMLOverrides File: Type in the path and name of the htmloverrides.ini file, or click theSelect File Button and browse for the file in the pop-up window.

When you run eGenerator and generate applications, the generator will process the htmlover-rides.ini file.

Choosing Languages

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

Note

You must install the Language Tools Release for each language you want to use.

➤ To choose languages

1. On eGenerator, select Options->Languages from the pull-down menu.



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

3. Click OK.

Configuring the genapp.ini File

The genapp.ini file contains the list of applications that you want generated in a mode other than the defaultmode, which is mode 1 for the windows look-and- feel. In the genapp.ini file, you can list applications youwant generated in one of the other modes: Mode 2 for java or Mode 3 for html.

The following file is a sample genapp.ini file. eGenerator reads this file. You can use this file to config-ure specific applications for generation.

# genapp.ini Last Revised 3/15/00# Application is the name of the application to generate# Mode is the FDA mode used to create the new "version" of the application.# Attach a mode to a menu from menu design. This determines which mode of# the application is displayed. The mode has nothing to do with whether or



# not it gets generated in HTML or Java - they are always generated for both.# An application can only be specified for a mode once.# Footer is the name of the menu you want displayed at the bottom of the# application. Footer menus are optional.

P4015:2:G42314P4015:3:G42314P4210:3:G4231P4210:2:G42314P4101H:3:G42314P41202:2:G42314P41202:3:G42314P03B2002:2:G42314P03B2002:3:G42314P42050:2:G42314P42050:3:G42314P4015W:2:G42314P4015W:3:G42314P40215:2:G42314P40215:3:G42314P41829W:2:G42314P41829W:3:G42314P42232:2:G42314P42232:3:G42314P4006:2:G42314P4006:3:G43S11P42045:2:G42314P42045:3:G42314P01012:2:G42314P01012:3:G43S11P4310:2:P4310:3:G43S11P43214:2:P43214:3:P4334:2:P4334:3:G43S11P0411:2:P0411:3:G43S11P34301:2:P34301:3:G43S11P40ITM3:2:G42314P40ITM3:3:G42314P4960:2:P01013:2:G42314P01013:3:G42314P3460:2:G42314P3460:3:G42314P43214:3:G43S11P41201:3:G43S11P43230:3:G43S11P44200:3:G43S11P430114:3:G43S11P43100:2:G43S11P43100:3:G43S11P0150R:3:G42314P0150S:3:G42314P055011:2:G05BESS1P055011:3:G05BESS1



P4915:3:G43S11P4960:3:G43S11P17500:2:G1715P17500:3:G1715P17501:2:G1715P17501:3:G1715P48201:2:G1715P48201:3:G1715P17714:2:G1715P17714:3:G1715P1723:2:G1715P1723:3:G1715P4947:2:G1705P4947:3:G1705P32942:3:P053020:3:

# P986116 and P986110B do not use modes in B733.3# They are being kept in genapp.ini to prevent any# potential issues with previous releases.

P986116:2:P986116:3:P986110B:2:P986110B:3:

#These apps were added for the project DONUT (6/22/01)P0092SS:3:P01012SS:3:P4334SS:3:P4311S:3:P4312S:3:P4310SS:3:P41204:3:P04111:3:P3462:3:P4210SS:3:P4947S:3:P03B2003:3:P43230SA:3:P42230:3:P42235:3:P42240:3:P34301:3:

#SAR 5336769P0005S:3:P0006S:3:P0101S:3:

Generating All Standard Serialized ObjectsThe eGenerator, in combination with a JAS build, can generate a complete set of Java Serialized Objects.These serialized objects allow you access to all EnterpriseOne™ objects when you run your web server. Ifyou are installing the Web Server or upgrading to a new Tools Release, you will likely want to generate acomplete set of serialized objects. If, however, you only want to generate a partial set of objects, skip thistask and complete the relevant task in the following section: Generating Selected Objects [57].




• Running the TAM Analyzer [51]

• Generating all objects [52]

Running the TAM Analyzer

Running the Tam Analyser enables eGenerator to generate all the objects without saving them to the data-base. This allows you to quickly test the generation process and detect corrupt specs by checking the logfiles. To use the TAM Analyzer, you must activate logging for both the Status log and Error log.

➤ To run the TAM Analyzer


2. Click the check boxes next to Error Log and Status Log, and click OK.

3. From the pull-down menu, select File -> Tam Analyser.



The Generator will start generating all the objects

4. When the generation is complete, check the Status Log and Error Log for corrupt specs.

Generating all objects

Complete the following task to generate a complete set of EnterpriseOne™ objects.

➤ To generate all EnterpriseOne™ objects

1. From the pull-down menu, select File->Core Objects.

For more information on generating core objects, see Generating Core Objects [61].

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

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



4. Click the Start button.

5. eGenerator checks the database connection before it attempts to generate objects. If it cannot connectto the database, eGenerator displays the following screen:

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

6. If the last Generate-All session did not conclude successfully, the following screen appears.

Select one of the following options



• To resume the previous generation process, click RESUME OLD SESSION. We recommend youchoose this option, which restarts the previous process from the point of failure. Once the previousprocess completes, you can repeat this task to generate the new set of objects.

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

In either case, an object set will start generating. The progress of object generation is displayed on thescreen: the blue progress bar indicates the progress of the generation process, and· the green progressbar indicates the progress of that objects are inserted into the database.

If the database insertion of objects is not complete when the generation is done, the Generator will dis-play the number of objects remaining in the queue.

Once all the objects are inserted into the database, the program displays the following message.



Verifying the Generation ProcessComplete the following tasks to verify the generation is successful.

• Checking log files [55]

• Checking Database Acknowledgements [56]

Checking log files

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

Note

These logs are generated every time you select the Generate All Objects option, regardless



of which types of objects you selected.

➤ To display the Status Log

• On eGenerator, select Logs->Status Log from the pull-down menu

➤ To display the Error Log

• On eGenerator, select Logs->Error Log from the pull-down menu.

Checking Database Acknowledgements

When generating a single object, the system sends a message to the DOS command window to acknow-ledge the successful insertion of the object into the database. This enables the user to monitor the genera-tion process and verify that objects are being successfully inserted in the database.

These acknowledgments will not be printed for Data Dictionary Items or Data Structures, however, because



they are too numerous to be printed on the command line screen.

Below is an example of the output to the DOS command line:

Generating application P01012 ...-->Database Ack:ER_P01012_W01012D successfully inserted into database-->Database Ack:P01012_HTML_W01012D successfully inserted into database-->Database Ack:ER_P01012_W01012B successfully inserted into database-->Database Ack:P01012_HTML_W01012B successfully inserted into database-->Database Ack:ER_P01012_W01012A successfully inserted into database-->Database Ack:P01012_HTML_W01012A successfully inserted into database Appgeneration finished Generating 2 NERs -->Database Ack: ER_P01012_W01012Csuccessfully inserted into database -->Database Ack: P01012_HTML_W01012Csuccessfully inserted into database -->Database Ack: NER_PlugAndPlay_P0101successfully inserted into database NER generation finished Generating 1 POData Structure Items PO Data Structure generation finished Generating 2Business Views Business View generation finished Generating 5 Tables Tablegeneration finished Generating 294 Data Dictionary Items Data Dictionarygeneration finished Generating 30 Data Structure Items Data Structuregeneration finished -->Database Ack:NER_UpdateChangedGeoCode successfullyinserted into database -->Database Ack: PODATAP01012 successfully insertedinto database -->Database Ack:VIEW_V0101E successfully inserted intodatabase -->Database Ack: TABLE_F0101 successfully inserted into database-->Database Ack: TABLE_F0111 successfully inserted into database-->Database Ack: TABLE_F0116 successfully inserted into database-->Database Ack: TABLE_F03012successfully inserted into database-->Database Ack: TABLE_F0401 successfully inserted into database

Generating Selected ObjectsAfter you have initially generated EnterpriseOne objects, any time you subsequently create or customizeEnterpriseOne™ objects (such as UBEs or applications) you must individually generate those objects.

eGenerator includes several methods of generating a partial set of serialized objects. All but one method,"Generating objects using the Bulk Generation File," are performed by selecting options from the eGenerat-or screen. The Bulk Generation file allows you to type selected objects directly into a text file and run thisfile in eGenerator.

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

• Generating Objects From an Update Package [58]

• Generating Core Objects [61]

• Generating Applications [63]

• Generating Forms [67]

• Generating Reports [69]

• Generating NERs [72]

• Generating Data Dictionary Items [73]

• Generating Tables [74]



• Generating Business Views [75]

• Generating Data Structures [77]

• Converting Grid Tabs [78]

Generating Objects From an Update Package

Starting with Service Pack 21, every update package includes a list of changed applications and data struc-tures in a bulk generation file. This file is created during the package build process, and allows administrat-ors to generate only those objects that have changed since the last update. The bulk generation file for eachupdate package is called generatorList.txt, and is located in the following path:

pathcode\work

where pathcode is the pathcode to which the update package was generated. Below is an example of ageneratorList.txt file:

The Bulk Generation file is a text file containing a set of generation parameters. You can use Bulk Genera-tion to easily configure and store one or more sets of generation parameters into files. A set of generationparameters can then be automatically loaded into eGenerator by selecting the appropriate Bulk Generationfile.


• Creating a Bulk Generation File [58]

For update packages, this file is automatically created when you build the package.

• Running the Bulk Generation File [59]

Creating a Bulk Generation File

A template for creating a Bulk Generation file is provided along with gen.bat. To create a new Bulk Gener-ation file, you must modify the template and save it as the same file.



➤ To create a Bulk Generation File

1. From Windows Explorer, open the BulkGen.txt file. This file is usually located in the following dir-ectory:

x:\b9\system\Generator\WebClient

2. Using the existing objects in the file as examples, type in the objects that you want to generate (be sureto delete the examples when you are done).

Caution

Do not delete or modify the Magic_Number at the top of the file. This number identifies the file asa bulk generation file.

3. Save the file.

Running the Bulk Generation File

➤ To run the Bulk Generation File



1. Launch Gen.bat.

2. On OneWorld Sign On, log in to OneWorld.


• Bulk Generation File: Type in the name of the file, or click Select File, and choose theBulk Generation File.

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

4. From the pull-down menu at the top of the screen, select File->Bulk Generation.



eGenerator will generate all the objects listed in the file you selected.

Generating Core Objects

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

➤ To generate core objects

1. On eGenerator, select File->CoreObjects from the pull-down menu.



eGenerator begins generating the core objects and their dependent Data Dictionary Items.

2. Check the status logs and the database to ensure that the following objects were generated:

Tables F9860, F9865, F0005, F983051, F9210, F98980, F98950, F0092, F0101, F00950,F95921, F9060, F9060D, F9061, F9062, F9064, F0010, F0093, F986101, F00921,F00922, F0004, F00941, F0094, F95921, F9065, F0082, F00821, F0083, F0084, F9000,F9001, F9002, F9006

Views V9001B



Generating Applications

Complete one of the following tasks to generate one or more applications:

• To Generate an application [63]

• To generate applications by system code [65]

• To Generate Applications by Mode [66]

➤ To Generate an application

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





4. Click on Application Name, and type the name of an application (for example, P01012).

5. Click Start.

The Generator should first generate the Dependency Table ‘F9860’ and 38 DDs.

The Generator also determines if the Report-Licensing and App-Entry-Point objects should be gener-ated by checking for the existence of these objects in the database. You can override the Generator'srecommendations to generate these objects.

6. Check the Status Log for status of generation.

For P01012, the generator should generate the following:

• 3 forms: P01012_W01012A, P01012_W01012B and P01012_W01012C, and their correspondingER Objects.

• Views and Tables and data dictionary items contained in the Application.



7. Verify that these objects were generated by checking the Status logs.

➤ To generate applications by system code

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



4. Truncate the database.

5. Select Generate by System Code.

6. Click Start.

eGenerator fetches all the applications under that system code. (For example, Masters Environmentfetches 26 applications.)

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



8. Use the following SQL command to verify the applications reside in the database:

SQL> select wboid from f989999 where wboid like ‘P%W%’;

➤ To Generate Applications by Mode

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

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



4. Truncate the Database.

5. Choose Mode 3.

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



7. Click Start.

8. Use the following SQL command to verify that the database includes the HTML version of the applic-ation:

SQL> select wboid from f989999 where wboid like ‘P01012_HTML%’;

Generating Forms

➤ To generate a form

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




5. Type the form name in the Form Name field, for example, P01012_W01012A.

6. Click Start.



If the form name is invalid, the following error message will display:

If the application name is invalid, the following error message will display:

7. The Generator should first generate the Dependency Table ‘F9860’ and 38 data dictionary items.

8. Check the status log for the generation status.

For W01012A, the generator should generate the following objects:

• The form P01012_W01012A and its corresponding ER Objects

• The views, tables, and data dictionary items contained in the application

• For example, for P01012, the generator creates the following objects and 294 data dictionaryitems.

• NER_UpdateChangedGeoCode

• NER_PlugAndPlay_P0101

• F0101

• F03012

• F0116

• F0111

• F0401

• V0101E

9. Confirm that these objects are in the Status logs, or check the database using the following query:



SQL> select wboid from f989999

Generating Reports

Complete one of the following tasks to generate one or more reports:

• To generate a report [69]

• To generate a report version [69]

• To generate reports by system code [70]

➤ To generate a report

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




5. Type the name of a report, (for example, R0006P).

6. Click Start.

The Generator first generates the dependency table (F983051) and 28 data dictionary items.

The Generator also determines if the Report-Licensing and App-Entry-Point objects should be gener-ated by checking for the existence of these objects in the database. You can override the Generator'srecommendations to generate these objects.


The Generator should generate all versions of the report and their corresponding DSEL , DSEQ andPRINTINFO Objects.

8. Confirm the presence of the objects by looking in the Status logs, or use the following query to checkthe database:

SQL> select wboid from f989999 where wboid like ‘%R0006P%’;

➤ To generate a report version

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






5. Type a Report Name and Report Version, for example, R0006P, and XJDE0001.

6. Click Start.

The Generator should first generate the Dependency Table (F983051) and 28 data dictionary items.


Generator should generate all the versions of that report and their corresponding DSEL , DSEQ andPRINTINFO Objects.

8. Confirm the presence of the objects by looking in the Status logs, or use the following query to checkthe database:

SQL> select wboid from f989999 where wboid like ‘%R0006P%’;

➤ To generate reports by system code

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






5. Select Generate by System Code, and type a number for the code.

6. Click Start.

eGenerator fetches all the applications under that system code. (For example, Masters Environmentfetches 26 applications.)

If the version name you entered is incorrect, the following error message will display:



If the report name is incorrect, the following error message will display:

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

8. Use the following SQL command to verify the reports reside in the database:

SQL> select wboid from f989999 where wboid like ‘P%W%’;

Generating NERs

➤ To Generate NERs

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




5. Type in the name of an NER, (for example, GetObjectDesc).

Note

NERs are case sensitive.



6. Click Start.


8. Use the following SQL command to verify that the objects reside in the database.

SQL> select wboid from f989999 where wboid like ‘NER_ GetObjectDesc’

Generating Data Dictionary Items

➤ To generate Data Dictionary Items

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




5. Generate any Data Dictionary Item (for example, OBNM).





SQL> select wboid from f989999 where wboid like 'DICT_OBNM';

Generating Tables

➤ To generate tables

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




5. Type a Table Name, (for example, F9860).





SQL> select wboid from f989999 where wboid like 'TABLE_F9860';

8. Open UTBrowse and verify that the Data-Dictionary Items are in the table.

9. Check the logs to verify the Data Dictionary Items were generated.


SQL> select wboid from f989999 where wboid like 'DICT%';

The F9860 table should have 38 Data Dictionary Items.

Generating Business Views

➤ To generate Business Views



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




5. Type the name of a Business View, (for example, e.g. V9001B).

6. Click Start.



SQL> select wboid from f989999 where wboid like ‘VIEW_V9001B’;


SQL> select wboid from f989999 where wboid like 'TABLE_%';

For example, the Business View V9001B includes tables F9000 and F9001, and 78 Data dictionary



Items.

Generating Data Structures

➤ To generate Data Structures

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




5. Type in the name of a Data Structure , (for example, D9800150C).

6. 6. Click Start.





SQL> select wboid from f989999 where wboid like 'DSTR_ D9800150C

Converting Grid Tabs

Grid Tabs select the GD and GF record types in the F98950 table and converts binary blob data to xml blobdata. Complete this task to convert the Grid Tabs.

➤ To Convert Grid Tabs

1. From the pull-down menu, select File->Grid Tabs.

eGenerator displays the Grid Tabs Conversion Window.

2. Check the jde.log to verify that the conversion was successful.

3. Verify that grid tabs are active by opening an application and verifying that the User Overrides are act-ive.

This verification is only relevant if you perform the conversion on a pristine environment. If you areconverting a different environment, verify that the grid formats on the web are the same as the Win-



dows client.



80 This page intentionally left blank


Note

THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EX-PRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WAR-RANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. This publication could include technical inaccuracies or typographical errors.This publication does not make recommendations, implied or actual. It provides guidelines;however, due the wide variety of networking, hardware and software configurations found in En-terpriseOne™ installations, no guarantees can be made that specific results are achievable in anyparticular installation. Changes are periodically added to the information herein. These changeswill be incorporated in new editions of the publication. PeopleSoft may make improvements and/or changes at any time to the product(s) and/or the program(s) described in this publication.

IntroductionThe algorithm used to encrypt and decrypt EnterpriseOne™ passwords has been compromised and hasbeen posted to web. This enhancement will address the vulnerability that exists when storing passwords inthe database and the associated installation/migration issues. The solution will update the passwords storedin the database to a higher encryption standard.

This appendix is intended for an administrator who is going to apply the Tools Release & ESU at the cus-tomer site. It is assumed that the reader has knowledge of EnterpriseOne™ and CNC technology.

Solution

This enhancement improves the security of passwords stored in the database by replacing existing pass-word encryption with 3DES encryption. This conversion from the old encryption to the new encryption oc-curs in the following instances:

• When user login occurs

During the user login, the security kernel checks whether the user record in the security table is storedusing the old encryption. If it is stored using the old encryption, the kernel updates all user records insecurity tables to the new encryption. Since this happens only once, the impact to login process is min-imal.

• When the administrator adds a user to EnterpriseOne™

When the administrator adds a user record, a message is sent to the Security Kernel for processing. TheSecurity kernel encrypts the password using the new encryption and inserts the user records in the se-curity tables.

This enhancement also encapsulates administrative functionality for updating user passwords, and for copy-ing and modifying user records. These features are now part of the security kernel. When the administratorcopies/updates a user record, a message is sent to the Security Kernel for processing, and the Security ker-nel performs the required operation.

Impacted Components


Security Kernel & JAS

The Security Kernel has been updated to detect the old encryption and to re-encrypt records using the newencryption. The functionality that allows the software to add users and update user records was moved fromthe administration business functions to the security kernel. Similarly, JAS code has been updated to com-municate with Security Kernel for validating user records instead of going directly to the security tables.The changes are available as a Tools Release one-off as listed below:

Release Tools Release GA Date

EnterpriseOne™ 8.9 SP2_D1 January 19, 2004

• The Tools Release must be deployed on enterprise servers, JAS/web servers and clients in the or-der listed in the instructions below.

Security Administration

Security administration business functions have been modified to call system APIs for adding users and up-dating user records. This change is available on the ESU listed below:

Release SAR#

EnterpriseOne™ 8.9 6929072

• The ESU must be deployed on enterprise servers and clients in the order listed in this document.

Configuration

Once this update is installed on the enterprise servers, the security kernel stores passwords in the securitytables using the new encryption, and there is no way to disable the encryption or rever to the old configura-tion.

Pre-Installation ProcessBefore starting the pre-installation process, make sure you create a backup copy of the F98OWSEC &F98OWPU tables as identified in the ESU download.

To handle multiple foundations running different Tools Releases, we recommend using the following twodata sources for security tables:

• Use the existing data source (such as current system data source) to point Enterprise Servers runningservice packs older than SP2_D1.

• Create a new data source containing security tables to point Enterprise Servers running Tools ReleaseSP2_D1 or newer.



Note

If you are not using multiple foundations, your existing data source will be sufficient.

Configuring these data sources will help avoid data conflict due to overlap between new and old EnterpriseServers.

Complete the following steps before installing the Tools Release and/or ESU.

This task copies security tables to your server map data source. These tables are used as a secondary loca-tion to support the new encryption

➤ To copy security tables to the Server Map data source

1. Log on to the Deployment Server in the DEPB9 environment.

2. Open OMW and copy the F98OWSEC and F98OWPU tables to the existing Server Map Data Sourcewhere your security kernel is running (such as SERVERNAME – B9 Server Map).

3. Open OMW and copy the F9312 table to the existing Server Map Data Source where your securitykernel is running (such as SERVERNAME – B9 Server Map).

See Also

• Development Tools Guide for more information about using the Object Management Workbench andTable Design Aid to copy tables

InstallationTo complete this update, you must update all the servers and workstations in your EnterpriseOne™ envir-onment. Complete the tasks below that are relevant to your configuration when installing Tools ReleaseSP2_D1 or newer.

See Also

• EnterpriseOne™ Tools Release Installation PeopleBook for more information about installing theTools Release

• EnterpriseOne 8.9™ Web Server Installation PeopleBook for more information about installing thePeopleSoft Web Server

The Tools Release and the ESU must be deployed in following order.

1. Deployment Server

a. Follow the instructions in the Deployment Server Installation section of the EnterpriseOne™Tools Release Installation Instructions to install the Tools Release to your deployment server.



b. Follow the instructions in the EnterpriseOne™ Software Update Installation PeopleBook to in-stall the ESU to the deployment server and apply it to the path codes.

2. Enterprise Server

a. Follow the instructions in the Service Pack Installation Guide to install the Tools Release the ap-propriate host installation .

b. If you copied the F98OWSEC, F98OWPU, and F9312 tables to the server map data source dur-ing the pre-installation process, complete the relevant steps below for your enterprise server plat-form:

Platform Steps

AS/400® ServerInstallation

Before doing the final step (Sign Off and then sign back...) in the ToolsRelease installation instructions:

Update your JDE.INI file on the enterprise server with the followingchanges:

[SECURITY]

DataSource=SERVERNAME – B9 Server Map

This is the data source defined in the pre-installation process.

HP 9000™ ServerInstallation

Before doing the final two steps (Start Release 8.9 Services ...) in the in-stallation instructions for the Tools Release


[SECURITY]



RS/6000 ServerInstallation

Before doing the final two steps (Start EnterpriseOne Services for...) inthe Tools Release installation instructions:


[SECURITY]



Sun Server Install-ation

Before doing the final two steps (Start EnterpriseOne Services for...) inthe Tools Release installation instructions:

Update your JDE.INI file on the enterprise server with the following



Platform Steps

changes:

[SECURITY]



Windows ServerInstallation

Before doing the final two steps (Start Services for JDE B9 Network...)in the Tools Release installation instructions:


[SECURITY]



c. Verify that you can run PORTTEST successfully.

3. Follow the EnterpriseOne™ Web Server Installation PeopleBook to install the JAS/Web Serverchanges.

4. Deploy a package for the ESU & Tools Release

a. Modify the Deployment Server update package created by the ESU process (see the DeploymentServer section above). Compression the foundation to include the newer Tools Release (SP2_D1or newer)

b. Make sure this package is defined for both client & server(s).

c. Build and deploy the package to all workstations and servers.

5. Run the Web and Windows Clients to make sure users can login.

6. Run the security administration application to make sure a new user can be added and passwords forexisting users can be modified.

Things to keep in mind

1. Once the system is updated, the user records are encrypted with the new encryption when the user logson. There is no way to disable the encryption or revert back to the old security configuration.

2. There is no procedure to rollback user records to the old encryption nor is there a procedure for con-verting all user records to the new encryption. The back up copy of the F98OWSEC & F98OWPUtables can be used to reset the user data.



3. If the customer has multiple enterprise servers at different Tools Release levels, make sure each ofthem is pointing to the correct security data sources.

• If an enterprise server running an older Tools Release accesses data encrypted using the new en-cryption, authentication will fail and user will not be able to login.

• If an enterprise server running the new Tools Release accesses data encrypted using the old en-cryption, it will update the user records in Security tables to the new encryption on the fly.

4. If the customer has multiple enterprise servers at different Tools Release levels, a dual maintenance ofusers and passwords is required. Once all the foundations are running SP2_D1 or newer,

a. The INI setting for SECURITY Data Source can be changed back to the SYSTEM Data Sourcevalue.

b. The F98OWSEC, F98OWPU, and F9312 tables from the Server Map Data Source can be re-moved.

5. If the Tools Release is installed and the ESU is not installed:

• Since this ESU is not a planner ESU, the customer will not be able to use the Deployment Serverto change passwords or copy user records encrypted using new encryption. From the DeploymentServer, they can use the old encryption to add users and copy user records.

• To a workstation, the administrator will not be able to change passwords. The administrator will beable to add/delete/copy users. These users will have a password in the old encryption. The encryp-tion change will occur when the user logs in.

6. If the ESU is installed and the Tools Release is not installed,

• Since the ESU is backwards compatible, it detects that the Tools Release is not installed and willcontinue to function normally.

Roll-back ProceduresThe improved encryption will be part of all future Tools Releases and it can not be disabled. If the custom-er decides to rollback to previous Tools Release, complete the following steps:

1. Follow the installation instructions to rollback enterprise server and client workstations.

2. Reset the user records in the F98OWSEC & F98OWPU tables in the system data source from thebackup copy.

3. Change the INI setting for SECURITY Data Source back to the SYSTEM Data Source value.

4. Run PORTTEST on the enterprise server to make sure user can login.



Copyright/* ====================================================================

* Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

*

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

*

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

*

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

*

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* [email protected].

*

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

*

* 6. Redistributions of any form whatsoever must retain the following



* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

*

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

*

* This product includes cryptographic software written by Eric Young

* ([email protected]). This product includes software written by Tim

* Hudson ([email protected]).

*

*/

/* Copyright (C) 1995-1998 Eric Young ([email protected])

* All rights reserved.

*

* This package is an SSL implementation written

* by Eric Young ([email protected]).

* The implementation was written so as to conform with Netscapes SSL.

*



* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson ([email protected]).

*

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young ([email protected])"

* The word 'cryptographic' can be left out if the routines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:



* "This product includes software written by Tim Hudson ([email protected])"

*

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PUR-POSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

*

* The license and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution license

* [including the GNU Public Licence.]

*/



Appendix B: Parameters and Values for the jas.ini fileThe jas.ini file defines the startup OCM and other Web Server specific properties for the Web Server tocommunicate back to your enterprise environment. It is also the key to the installation. If there are any crit-ical settings that are incorrect or left blank, Web Server will not run. The critical settings are listed in aseperate table for each of the sections below.

The jas.ini file is automatically updated during the installation of the Web Server using the Java Server In-staller. However, you can modify the jas.ini settings after installation using a text editor.The jas.ini fileis functionally similar to the jde.ini file on the EnterpriseOne Enterprise Server.

Note

Starting with ERP9, many of the settings in the jas.ini file were moved to a new file called JD-Bj.ini. For information about this new file, see Appendix C: Parameters and Values for the jd-bj.ini file

To configure the jas.ini file you must:

• Add server names specific to your installation to parameters in the [SECURITY] and [SERVER] sec-tions.

• Verify the path names for various settings that are path name specific. If you follow the PeopleSoft re-commendations, you should not need extensive modifications to these paths.

• Verify the port numbers for your TCP/IP connections.

Tip

It is generally good practice to add comment line to your .ini files to include such information as:

• The current JAS package version (as labeled on the CD)

• The date you manually updated the file

• The person’s name who performed the updates

The jas.ini settings used by the Web Server are summarized in the following table:

Section Description

[DB SYSTEM SETTINGS] [JDBj-BOOTSTRAP SESSION]

[JDBj-BOOTSTRAP DATA SOURCE]

[SECURITY] [93] Contains EnterpriseOne security server information.


Section Description

[OWWEB] [96] Web Server specific settings.

[PORTALCONFIGURATION] [100]This optional section is not delivered as part of the standard jas.ini.

Contains optional settings for the Portal. The settings shown in this sec-tion are the default settings and are not required to be included as part ofthe jas.ini. That is, if no value is specified in the jas.ini, the Portal auto-matically uses the default setting listed in this section.

However, for sites wishing to modify any values that can be read from thejas.ini, the values must be entered and modified as appropriate for thatcustom installation. Note, however, that future installations may not pre-serve the custom modifications, so it is important to save a copy of thejas.ini before doing an upgrade.

[CACHE] [108] HTTP Session settings

[DB CONNECTION POOL] Starting with ERP9, this section was moved to JDBj.ini file and re-named. For information about the new section, see [JDBj-CONNECTIONPOOL].

[SERVER COMPONENTS] [109] Loads Web Server packages. Do not modify this section

[JDENET] [110] Specifies values for your Web Server to communication with your Enter-priseOne Enterprise Server.

[SERVER] [111] Specifies values for your Web Server to retrieve data dictionary error de-scriptions from your EnterpriseOne Enterprise Server.

[LOGIN] [112] Contains settings for login and the Local Director.

[LOGS] [113] Turns on debug logging and specifies the location of your log files.

[TRANSACTIONS] [114] Contains configuration settings to customize transaction processing withinJAS.

[JAS Instance] This optional section is not delivered as part of the standard jas.ini.

Contains settings to define multiple JAS instances using the Redirectorfunctionality. Multiple instances can be defined to improve performanceand to scale installations for large user bases. The default mechanism forallocating users among multiple JAS instances is "round robin", or se-quential selection.

[JAS Weight] This optional section is not delivered as part of the standard jas.ini.

Contains settings that enable load balancing for multiple JAS instancesusing the Redirector functionality.

[Redirector] This optional section is not delivered as part of the standard jas.ini.

Specifies the location that the Redirector will redirect to if no Web Server

Appendix B: Parameters and Values for the jas.ini file


Section Description

is available. This is typically an HTML page that provides an explanation.

[ERPINTERACTIVITY] [114] This section is used to activate and configure the Interactive HTML set-tings.

[WEB GUI] [116] This section is used to customize the web GUI interface.

[SECURITY]The critical settings that provide the basic functionality for the Web Server are listed in the table below:

[SECURITY]

Parameter Recommended Setting Description

DefaultEnvironment= JPD9 Specifies the default EnterpriseOneenvironment.

SecurityServer= Site-dependent variable Specifies the name of the securityserver defined for your Enter-priseOne Enterprise Server installa-tion.

Factory=• For Portal integrated with EnterpriseOne:

com.jdedwards.system.security.SecurityServerProxyFactory

• For Independent Portal:

com.jdedwards.system.security.SecurityServerDBFactory

• For Independent Portal using iSeries as asecurity server:

com.jdedwards.system.security.SecurityServerAS400Factory

Specifies the method used to verifythe user name and password.

Note that the method depends on thePortal configuration. If you do notspecify a value for Factory, the sys-tem defaults in the value for a Portalintegrated with EnterpriseOne.

The non-critical settings are listed below:

[SECURITY]


NumServers= 1 Specifies the total number of Enter-priseOne security servers that are



[SECURITY]


defined as being available to userswho sign on to this Web Server.

If this parameter is missing or has avalue of blank, the default value is 1and the sign n is handled by theprimary security server defined bythe SecurityServer= parameter inthe [SECURITY] section of thejas.ini

SecurityServerN= Site-dependent variable Specifies the name of the secondaryserver. You can define multiple se-curity servers if you want sign on tofail over to valid secondary serversif users cannot sign on to theprimary server.

Valid values for N are numeric val-ues from 1 to n where:

1. Defines the first secondary se-curity server.

2. Defines the second secondarysecurity server.

n Defines any number of sequen-tially accessed security servers.

UserLogonCookie= FALSE Defines whether user sign on in-formation is saved in an encryptedcookie on the HTML client ma-chine. This information includesuser name, password, and environ-ment.

Valid values are:

TRUE User information is saved inan encrypted cookie that automatic-ally populates the login screen.

DIRECT Enables users to access lo-gin information in the cookie andbypass the login screen.

FALSE User information is notsaved in an encrypted cookie. Youmust use this setting when using theJAS Redirector.



[SECURITY]


CookieLifeTime unit is "day" Specifies the unit of time used bythe CookieLifeTime= parameter.

CookieLifeTime= 7 Specifies the amount of time beforea cookie expires, measured by thevalue of the CookieLifeTime unitparameter.

Data Source= Site dependent variable Specifies the data source used toconnect to the security table

This setting is used for IndependentPortal only. If Data Source is spe-cified, you must also specify a Userand Password.

User= JDE Specifies the database user ID

This setting is used for IndependentPortal only.

Password= JDE Specifies the database password

This setting is used for IndependentPortal only.

The configuration of the [Security] section depends on type of security server you are using to authenticatethe users. Below are examples of the basic configurations:

Using a OneWorld Security Server.

[Security]Factory=com.jdedwards.system.security.SecurityServerProxyFactoryNumServers=3SecurityServer=JDEDSecurityServer1=JDECSecurityServer2=corowhp

Using a Database Security Server (Independent Portal).

[Security]Factory=com.jdedwards.system.security.SecurityServerDBFactoryDataSource=System-SecurityUser=JDEPassword=JDE

If you specify a database security server with your Independent Portal, the system uses a Java implementa-tion of a database proxy user.



Using an iSeries Security Server (Independent Portal).

[Security]Factory=com.jdedwards.system.security.SecurityServerAS400FactorySecurityServer=JDEC

Specify the name of your iSeries Security Server in the SecurityServer setting.

[OWWEB]The critical settings that provide the basic functionality for the Web Server are listed in the table below:

[OWWEB]

Parameter RecommendedSetting

Description

PathCodes= ('JD9','DV9','PY9','PD9')

This key lists the standard PeopleSoft path codes. If you use standard pathcodes you will not have to modify these values. If you modify this key, itmust be a valid path code for EnterpriseOne.

The default environment is listed by path code. If this value is empty, allavailable environments will be available to a particular user or group.Each path code is single quoted and separated by commas.

MO QUEUE= Site-dependentpath

Identifies the media object directory location on your Web Server. Thispath must translate into virtual path /jde/moqueue/ for the webbrowser.

The web server process must have write and create authority to this path.

Note

You may need to create this directory.

The default value is:

x:\Program Files\PeopleSoft\JAS\EA_JS_<portnumber>\webclient.war\moqueue

UseMOWinNT-Share=

TRUE Specifies that the web server use the Windows file sharing mechanism forfetching Media Object files from their location into the cached location ofthe web server.

InYourFaceEr-ror=

TRUE Specifies that the web server display error messages associated with theweb interface at the top of the current form.

If this setting is changed to False, a small red icon is displayed in the up-per-right corner instead. Clicking on the icon displays the text of the errormessage.





LargeLoginImage/jde/share/images/jdelogin_large.gif

Specify a URL relative to the document rootof the HTTP server. This image displays onthe login page when a standard desktopbrowser (IE 5, Netscape 6) is used.

Tip

You can specify a different graphicfor Independent Portal. For example,

/jde/share/images/portallogin_large.gif

SmallLoginImage/jde/share/images/jdelogin_small.gif

Specify a URL relative to the document rootof the HTTP server. This image displays onthe login page when a pervasive device(PocketPC, Windows CE) is used.

Tip

You can specify a different graphicfor Independent Portal. For example,

/jde/share/images/portallogin_small.gif

F0005Prefix= DR Column prefix for F0005 table.

F0004Prefix= DT Column prefix for F0004 table

MaxUser= 100 The maximum number of EnterpriseOne(internet) users.

PrintImmediate= FALSE When set to FALSE, the enterprise servergenerates a PDF file only. When set toTRUE, the enterprise server generates a PDFfile and converts the PDF file to PostScript.PDL or Line output for the UBE job.

KeepUBE= TRUE When set to FALSE, the JDE.LOG andJDEDEBUG.LOG files are deleted when theUBE job is completed. When set to TRUE,the JDE.LOG and JDEDEBUG.LOG are keptwhen the UBE job is completed.

UBEQueue= QB9 The batch queue to which UBE jobs are sub-mitted.




SystemDateFormat= MDE Specifies the system data format.

SystemDateSeparator= / Specifies the system data separator.

HelpPath= /jde/owhelp This setting specifies the directory path forthe help files. The syntax of the setting is:

http://[machine]/[path]/

The Web Server builds an absolute help pathbased on the current instance of the JAS serv-er.

For example, if the URL for the Web Serveris:

http://machinename:82/

Then the Web Server assumes the URL forthe help path is:

http://machinename:82/jde/owhelp

Once this directory is set up, you must extractthe helps.CAB file to this location.

If you are installing Help files for Enter-priseOne 8.10, see Extracting the Enter-priseOne Help files .

Note

• The directory /jde in the abovepath is a relative path. The abso-lute (default) path for the /jdealias is x:\ProgramFiles\PeopleSoft\JAS\EA_JAS_81.ear\webclient.warwhere x is the drive letter whereJAS is installed.

OWJRNL= OWJRNL This setting is only applicable to Web Serversrunning on iSeries platforms. If you havemanual commit turned on to update the AS/400 DB2 database records, this setting allowsthe Web Server to turn on the JOURNAL forthe applicable iSeries tables.

The value you specify for this setting must bethe name of the library name on the AS/400for the STRJOURNAL stored procedure.




AutoPilotIDs= FALSE This setting controls whether the Java Servergenerates IDs useful for scripting HTML cli-ent actions using the PeopleSoft Auto Pilottool. Valid values are:

FALSE The Java Server does not generateany Auto Pilot IDs.

Note

If you are setting up the Web serverfor visually impaired users, theAutoPilotIDs setting must be setto FALSE.

TRUE The Java Server generates Auto PilotIDs.

AnonAccess= TRUE Enable anonymous user access

DefaultEnvironment= Site-dependent variable Default environment for login. Used in con-junction with Basic Authentication.

InitialLanguageCode= EN ISO language code for initial user language.

LogoutProcessTimeout= 90 Number of seconds after logout that a busi-ness function activated by the user will con-tinue to run.

TurnOnJargonText= FALSE This setting determines if menu system codeJargon is enabled or disabled. By default, Jar-gon is disabled (FALSE). Regardless of thissetting, application system code Jargon is ap-plied. When TurnOnJargonText=TRUE, theGlossary Text, Alpha Description,and Jargon Row/Column Descriptionare retrieved from the database. When thissetting is FALSE, the Glossary Text andAlpha Description are retrieved from theGlossary Text Server, and the Row/ColumnDescriptions are retrieved from specifica-tions on the generation machine.

workcenter= ItemManager If you enter the value WorkCenter, the WebServer displays the menu item "Work withWork Center" in the client's browser, andlaunches P012503_W012503F. If workcenteris any other value (or if the property isn'tentered in the jas.ini file), then the WebServer displays the menu item as "Work withItem Manager" and launchesP012502_W012502A.

AutoComplete= on The AutoComplete feature in HTML formsstores information entered into text fields. In-




ternet Explorer saves the AutoComplete in-formation in an encrypted format for the user,and retrieves the list of stored entries for thatform when the user begins typing in a textfield with the same name. The user can selecta value from the AutoComplete list box usingthe arrow keys.

OneUserOnly= 0 Setting this value to 1 gives each user of thisJava Virtual Machine their own dedicatedCallObject kernel on the Enterprise Server forBusiness Function processing. To enable thisfeature, you must also set the bAllo-wOneUserOnly setting in the JDEN-ET_KERNEL_DEF6 section of the JDE.INIfile to 1.

This setting should only be used for testingbusiness functions running on the EnterpriseServer.

[PORTALCONFIGURATION]This section contains optional settings for the Portal.

If you are using a load balancer such as a Cisco LocalDirector, you must specify the localhost setting.

If you are using the Portal Component Importer, you must specify the backup, jde, and servlet settings.

With the exception of the above settings, all of the settings shown in this section are the default settings andare not required to be included as part of the jas.ini. That is, if no value is specified in the jas.ini, thePortal automatically uses the default settings as listed in this section.

However, for sites wishing to modify any values that can be read from the jas.ini, the values must beentered and modified as appropriate for that custom installation. Note, however, that future installationsmay not preserve the custom modifications, so it is important to save a copy of the jas.ini before doingany upgrade.

The following settings are required to configure the importer/exporter component for the Portal.

[PORTALCONFIGURATION]

Paramet-er

Recommended Setting Description

jde x:\Program Files\PeopleSoft\JAS\EA_JS_<portnumber>\webclient.war

The web directory created atJAS install time. The Compon-ent Importer/Exporter uses thedirectory to find and writeHTML resources such as .html,.gif, and jpg files.



[PORTALCONFIGURATION]

Paramet-er

Recommended Setting Description

servlet x:\Program Files\PeopleSoft\JAS\EA_JS_<portnumber>\webclient.war\classes

The directory where Portal ser-vlets reside, and where com-ponents from the update centerare stored. The Component Im-porter/ Exporter uses the direct-ory to find and write servlets.This is a directory that the JASadministrator must create andconfigure to be included in theJDE Web Application'sclasspath.

backup x:\temp\backup A location where files that areabout to be overwritten by theComponent Importer are saved.This provides a backup of theoverwritten files.

This location should not be inthe classpath and should not beviewable from the web server.

One-WorldP-resent=

TRUE This setting tells the Portalwhether EnterpriseOne is in-tegrated with this web server. Ifthis setting is not specified injas.ini file, a value of TRUEwill be used. If this value is setto FALSE, Portal componentsflagged as requiring One-World/ERP system will notrun.



Admin

(for SP 13.1 and above)

Site dependent variable; no defaultvalue is used.

This setting specifies a list of userIDs separated by the | character.These users can administer all com-ponents and workspaces – regard-less of relationship.

cache_workspace_purge 3600000 The time in milliseconds to retain aworkspace in cache without beingaccessed before being deleted. If setto zero, the system never purgesworkspaces from the cache.




Changing this value can drasticallyaffect portal performance. Youshould use caution when changingthis value.

cache_workspace_expire 900000 For expirable components, the timein milliseconds in addition to thelast loaded timestamp before aworkspace is deleted. To make acomponent expirable, implementpublic long getLastLoaded-Timestamp();. A workspace doesnot expire unless a user accesses it.If set to zero, the system never ex-pires workspaces from the cache


cache_workspace_timeout 300000 The interval in milliseconds the sys-tem should wait before checkingcache for items to purge or expire.The lower the number, the better thememory conservation, but theslower the cache. If set to zero, thesystem never expires or purgesworkspaces from the cache.


cache_workspace_refresh 0 The time in milliseconds before thesystem deletes all workspaces fromthe cache.


cache_component_purge 3600000 The time in milliseconds to retain acomponent in cache without beingaccessed before being deleted. If setto zero, the system never purgescomponents from the cache.





cache_component_expire 900000 For expirable components, the timein milliseconds in addition to thelast loaded timestamp before a com-ponent is deleted. To make a com-ponent expirable, implement publiclong getLastLoadedTimestamp();. Acomponent does not expire unless auser accesses it. If set to zero, thesystem never expires componentsfrom the cache.


cache_component_timeout 300000 The interval in milliseconds the sys-tem should wait before checkingcache for items to purge or expire.The lower the number, the better thememory conservation, but theslower the cache. If set to zero, thesystem never expires or purges com-ponents from the cache.


cache_component_refresh 0 The time in milliseconds before thesystem deletes all components fromthe cache.


cache_itrust_purge 60000 The time in milliseconds to retain aninherited trust session in cachewithout being accessed before beingdeleted. If set to zero, the systemnever expires or purges inheritedtrust session from the cache.

Changing this value can drasticallyaffect portal performance and secur-ity. You should use caution whenchanging this value.

cache_itrust_expire 0 For expirable components, the timein milliseconds in addition to thelast loaded timestamp before an in-




herited trust session is deleted. Tomake a component expirable, imple-ment public long getLastLoaded-Timestamp();. An inherited trustsession does not expire unless a useraccesses it.

You should not change this settingunless instructed to do so byPeopleSoft

cache_itrust_timeout= 30000 The interval in milliseconds the sys-tem should wait before checkingcache for items to purge or expire.The lower the number, the better thememory conservation, but theslower the cache. If set to zero, thesystem never expires or purges in-herited trust sessions from thecache.

cache_itrust_refresh 0 The time in milliseconds before thesystem deletes all inherited trust ses-sions from the cache.

cache_entbutton_purge 3600000 The time in milliseconds to retain anEnterprise Navigation Bar button incache without being accessed beforebeing deleted. If set to zero, the sys-tem never purges enterprise naviga-tion buttons from the cache.

Changing this value can drasticallyaffect portal performance. Youshould use caution when changingthis value

cache_entbutton_expire 0 For expirable components, the timein milliseconds in addition to thelast loaded timestamp before an En-terprise Navigation Bar button is de-leted. To make a component expir-able, implement public long get-LastLoadedTimestamp();. If set tozero, the system never expires enter-prise navigation buttons from thecache.

If set to zero, the system never ex-pires enterprise navigation buttonsfrom the cache.

cache_entbutton_timeout 900000 The interval in milliseconds the sys-tem should wait before checking




cache for items to purge or expire.The lower the number, the better thememory conservation, but theslower the cache. If set to zero, thesystem never expires or purges En-terprise Navigation Bar buttonsfrom the cache.

cache_entbutton_refresh 0 The time in milliseconds before thesystem deletes all Enterprise Navig-ation Bar buttons from the cache.

pagegreeting Welcome to your Portal Default page greeting when addinga new workspace. This setting has ablank default value.

localhost Site dependent variable If you are using a Cisco LocalDir-ector router, you must include thissetting. If the port of your web serv-er is other than 80, you must specifythe port. The syntax is:ip_address:port, whereip_address:port refers to thelocal EnterpriseOne Java Server ma-chine (not the Cisco LocalDirectormachine). This is required to enablethe portal code to determine the ori-gin of machine requests so re-sponses can be routed accordingly.

For example:

10.0.110.79:85

styleurl /jde/owportal/portal.css URI of portal style sheet

Both relative and fully qualifiedURLs are valid.

hlpimg /jde/owportal/images/ help2.gif Name of help image in componenttool bar


perimg /jde/owportal/images/ edit2.gif Default personalize icon file pathand name such as: /jde/images/edit2.gif.


maximg /jde/owportal/images/ maxim-ize2.gif

Default expand icon file path andname such as: /




jde/images/maximize2.gif.


minimg /jde/owportal/images/ minimize2.gif Default contract icon file path andname such as: /jde/images/minimize2.gif


resimg /jde/owportal/images/ restore2.gif. Default restore icon file path andname such as: /jde/images/restore2.gif.


retimg /jde/owportal/images/ return.gif. Default return icon file path andname such as: /jde/images/return.gif.


ShowCurrentEnvironmentRole FALSE Environment display. When set toTRUE, the system displays the cur-rent environment in the WorkspaceNavigation bar.

ShowSignin TRUE Shows the regular login hyperlinkon the Workspace Navigation Barwhen the user logs in anonymously.

corplogourl /jde/owportal/images/jdelogo.gif The URL of the default corporatelogo. This image is used when thecurrent workspace does not specifyan image.


corplogolinkurl The URL of the default corporatelogo hyperlink. This link is usedwhen the current workspace doesnot specify a link.

This setting has no default value.


DataMigrationHasOccurred This is a system setting, do not True if B9 pristine component and




modify this setting or add it thejas.ini file.

workspace data had been updated.

DefaultWorkspace The workspace to display when noother workspace is specified orwhen DefaultWorkspaceOnly is setto TRUE.

Set this value equal to the Work-space ID, not the Workspace Name.

Use upper case letters to set thisparameter.

This setting has no default value.

DefaultWorkspaceOnly FALSE Allows access to the default work-space only.

ForceDefaultWorkspace TRUEWhen a DefaultWorkspace isentered, and ForceDefaultWork-space is True, a user will always seethe default workspace as the firstworkspace when they log in.

edtimg /jde/owportal/images/ edit2.gif The URL of the default edit icon.The edit icon is used for buttons thatallow the user to alter an object.


NumberOfIcons 34 Number of enterprise navigation baricons override.

colorscheme1 De-fault|#FFFFFF|#00009C|#0063CE|#080029

|#CECECE|#FFFFFF|#636363|#FFFFFF |background.jpg|

/jde/owportal/owportal.css

Delimited String for color schemes.String consists of name, backgroundcolor, tool bar color, tool bar toolscolor, fixed area color, border color,text color, menu color, greeting col-or, top background image color,style sheet URL.

colorscheme2 Spring-time|#FFFFFF|#218C7B|#84BDB5|#006B63|#CECECE|#FFFFFF|#FF6B29 |#FFFFFF|springtimebkgd.gif|

/jde/owportal/portal.css

Delimited String for color schemes.String consists of name, backgroundcolor, toolbar color, tool bar toolscolor, fixed area color, border color,text color, menu color, greeting col-or, top background image color,style sheet URL.

colorscheme3 Blue-dot|#FFFFFF|#4A5A9C|#849CC6|#

Delimited String for color schemes.String consists of name, background




001873|#CECECE|#FFFFFF|#737BB5|#FFFFFF |bluedotbkgd.gif|


color, toolbar color, tool bar toolscolor, fixed area color, border color,text color, menu color, greeting col-or, top background image color,style sheet URL.

colorscheme4 Techno|#FFFFFF|#006363|#739C9C|#004242|#CECECE|#FFFFFF|#B5C6C6|#FFFFFF |technobkgd.gif|



colorscheme5 City-scape|#FFFFFF|#FF9C00|#FFC66B|#000063|#CECECE|#FFFFFF|#636363 |#FFFFFF |cityscapebkgd.gif|

|/jde/owportal/portal.css


[CACHE]Note that the values specified for these keys are in milliseconds. For example, 60000ms is equal to oneminute.

None of the following settings affect the basic functionality of the Web Server.

Note

Many of the settings that were in this section before ERP9 have been moved to the following sec-tions in the JDBj.ini file:

• [JDBj-CONNECTION POOL]

• [JDBj-RUNTIME PROPERTIES]


Description

UserSession= 1200000 The time in milliseconds before an inactive user session is cleaned upfrom cache. This User Session is maintained on the Server side inPeopleSoft code, which is different from the HTTP Session of Web-Logic. PeopleSoft recommends that the UserSession setting betwice that of the WebLogic HTTP session timeout (Invalida-tionIntervalSecs) setting.




Description

Note

This value must be greater than the "InvalidationInter-valSecs" setting in WebLogic to prevent the Java Serverfrom timing out before WebLogic.

To check the InvalidationIntervalSecs setting in Web-Logic, open the weblogic.xml file (located in the /WEB-INF directory), and verify that InvalidationInter-valSecs is listed and set to an appropriate value (inseconds). If the setting is not listed, the default is 60 seconds.

Default value: 60 (seconds)

Min: 1 (second)

Max: 604,800 (seconds) - one week

Effect of Change: When the InvalidationIntervalSecs value isreached, JAS receives notification to remove the UserSession fromcache. Changing the UserSession value does not effect change aslong as this value greater than the InvalidationIntervalSecsvalue in WebLogic.

CacheCheck= 300000 The time in milliseconds to check the status of all the objects stored inCache. PeopleSoft recommends using the default value.

Default value: 300000

Minimum value: 60000. If a lower value than 60000 is used, CacheM-anager will check value stored in cache too frequently which will cre-ate more overhead on the JAS server.

Maximum value: 600000. Do not use a greater value than 600000 be-cause the CacheManager will not be able to check the status of cachedobjects often ,and invalid objects will remain in cache even after theyexpire.

Relationship: This value does not depend on any other parameters inthe JAS.INI file.

Effect of Change: If you decrease this value, CacheManager willcheck the value stored in cache very frequently, which will createoverhead in the JAS server. If you increase this value to a very bignumber, then CacheManager will not check the status of cached ob-jects often, and invalid objects will remain in cache even after they ex-pire.

[SERVER COMPONENTS]Confirm the following settings within the [SERVER COMPONENTS] section. This section of thejas.ini is used by the Web Server to set environment variables. This section should not be modified un-



less instructed to do so by PeopleSoft.

[SERVER COMPONENTS]

com.jdedwards.jas.UserManager

com.jdedwards.jas.JDBCProxy

com.jdedwards.jas.JDEORB

com.jdedwards.jas.DDValidation

com.jdedwards.jas.security.SecurityBroker

com.jdedwards.jas.UDCJDBC

com.jdedwards.jas.JDEUDCText

com.jdedwards.jas.JDEUpdates

com.jdedwards.jas.JDEQueries

com.jdedwards.jas.JDEOWDirect

com.jdedwards.jas.ServerQuery

com.jdedwards.jas.JDESignon

com.jdedwards.jas.AuditComponent

com.jdedwards.runtime.virtual.MAFComponentLoader

Note

This last entry, com.jdedwards.runtime.virtual.MAFComponentLoader, is required forMAF (Multiple Application Framework) to fuction correctly. If this setting is missing, Enter-priseOne applications will not launch under MAF.

[JDENET]This section is used only if you are running business functions and launching UBEs without the JOWProxyservice.

The critical settings that provide the basic functionality for the Web Server are listed in the table below:

[JDENET]


serviceNameConnect= 6011 The TCP port on which the PeopleSoft Enter-prise Server is listening. You must modifythis setting for your environment.

By default, PeopleSoft increments this defaultport by one per EnterpriseOne Release. ForEnterpriseOne, the default value is 6011.





enterpriseServerTimeout= 90000 The time in milliseconds before atimeout condition can occur.

MaxPoolSize= 50 The maximum number of connec-tions to the enterprise server.

TempFileDir= c:\b9\internet A temporary directory for JDENET.This entry must be a valid directoryon your system.

[SERVER]This section is used only if you are running business functions and launching UBEs without the JOWProxyservice.

The critical settings that provide the basic functionality for the Web Server are listed in the table below:

[SERVER]


GlossaryTextServer=

Site-dependent variable This entry specifies the Enterprise Server andthe port number EnterpriseOne is listening onto provide glossary text information for theWeb Server.

The syntax is:

machine_name:6011

where machine_name is a valid machine foryour site.



codePage= 1252 The code page for displaying theglossary text information. Supportedencoding schemes include:

• 1252 English and WesternEuropean

• 932 Japanese




• 950 Traditional Chinese

• 936 Simplified Chinese

• 949 Korean

enableJargon = FALSE This setting determines if menu sys-tem code Jargon is enabled or dis-abled. By default, Jargon is disabled(FALSE). Regardless of this setting,application system code Jargon isapplied. When enableJargon=TRUE,the Glossary Text, Alpha De-scription, and Jargon Row/Column Description are re-trieved from the database. Whenthis setting is FALSE, the GlossaryText and Alpha Descriptionare retrieved from the Glossary TextServer, and the Row/Column De-scriptions are retrieved fromspecifications on the generation ma-chine.

jargonCacheTimeout = 360000 The time, in milliseconds, that theJDBj will cache the GlossaryText, Alpha Description orRow/Column Description re-trieved from database. This settingonly applies if enableJargon isset to TRUE. The default is 360000.

[LOGIN]This section is used for setting login and Local Director options.


PassKey= Site-dependent variable Alphanumeric override for the keyused to encrypt cookies.

externalhost= machine:port Use to build fully qualified URLsfor a browser request for a resource.

DisplayEnvironment= Administrator preference Environment display rule if a de-fault environment has been set withDefaultEnvironment.

Show: User can override the defaultenvironment at login.

Hidden: The user cannot see the en-




vironment box at login.

ReadOnly: The user cannot tamperwith the environment setting at lo-gin.

UseDefault: The user can select dif-ferent environments at login, but thesystem overrides any other userchoice and logs in to the default en-vironment anyway.

DisablePasswordAboutToExpire TRUE Override that suppresses "passwordabout to expire" notification.

[LOGS]This section is used to set system-dependent value for various logging functions related to the Web Server.

[LOGS]


Debug= FALSE TRUE Debug logging is enabled.

FALSE Debug logging is disabled.

jdbcTrace= FALSE TRUE Trace logging of JDBC statements are included in thestandard output log file.

FALSE No trace logging is performed.

stderr= Site-dependent variable Specifies the WebLogic log directory for input errors.

The STDERR and STDOUT keys must point to the same direct-ory that was supplied for the STDERR and STDOUT fieldswhen defining the WebLogic Application Server. This is usuallythe directory under 8.9. The default path is:

x:\Program Files\PeopleSoft\JAS\EA_JS_<port num-

ber>\webclient.war\log\stderr.log

stdout= Site-dependent variable Specifies the WebLogic log directory for output errors.

The STDERR and STDOUT keys must point to the same direct-ory that was supplied for the STDERR and STDOUT fieldswhen defining the WebLogic Application Server. This is usuallythe directory under 8.9. The default path is:


ber>\webclient.war\log\stdout.log



[LOGS]


rtlog= Site-dependent variable The name and location of runtime log file. The default value is:


ber>\webclient.war\log\rt.log

rtdebug= Site-dependent variable The name and location of runtime debug log file. The defaultvalue is:


ber>\webclient.war\log\rtdebug.log

rtdebugTrace= TRUE Specifies whether to turn on the runtime log file.

rtlogType= ALL Indicates the types of events you can log in the runtime debuglog file. Instead of "ALL", , you can enter one or more of thefollowing settings:

BSFN|TableIO|SYSFUNC|MISC|ER|EVENT

[TRANSACTIONS]This section is used to set configuration settings to customize transaction processing within JAS.

[TRANSACTIONS]


ReapInterval= 5 Interval in minutes of how often the TransactionReaper should check for abandoned transactions.Valid values: Integer from 1 to n. Default: 5 minutes

MaxAge= 10 Maximum age in minutes of a transaction. Transac-tions older than this will be rolled back by theTransactionReaper. Valid values: Integer from 1 ton. Default: 10 minutes

[ERPINTERACTIVITY]This section is used to activate and configure the Interactive HTML settings and Multiple ApplicationFramework (MAF) .

Note

Multiple Application Framework (MAF) may not work with third party 'Web Advertisement-Popup Stoppers'. When the Advertisement Stoppers are enabled on the user's machine and MAF isenabled in the jas.ini file, MAF may not operate properly. Third party programs that preventweb advertisements from popping up use a simplistic method to determine which windows to sup-press. As a result, when a user pops up a new browser in the Web Server, the advertisement stop-



pers believe it is an advertisement, and the browser is prevented from displaying. In this situation,the Runtime Engine thinks the application is open even though the user cannot see it. The usermay get messages warning that the maximum number of applications is open (see theMaxBrowsersOpen setting below), even though they can't see any of them. PeopleSoft does notsupport the use of these programs with the Web client when MAF is enabled. However, you canuse Web Advertisement-Popup Stoppers if you disable MAF. But if you enable MAF, you mustdisable all third party Web Advertisement-Popup Stoppers.

You might be able to configure some of these third party programs to allow certain windows toopen when MAF is enabled, but PeopleSoft does not support these programs, and we will requestthat you disable these programs if we think the program is causing a problem.

[ERPINTERACTIVITY]


InteractivityLevel= LOW or HIGH Indicates the level of interactivity for the entire in-stance of JAS. Valid values are LOW, MEDIUM,and HIGH. The default value is LOW.

In Low Interactivity mode, whenever a critical ornon-critical posting event happens, the whole pageis sent to the web server and the user has to wait forthe page to come back. When it does, the wholepage is repainted, and that usually causes a flash onthe browser. This is equivalent to the functionality inSP21 and below. An example of Critical Eventswhich force a post are: Form.Row,View,Tools Exitor Toolbar Button clicks, Clicking on Visual Assist,Switching Tab pages, Expanding/Collapsing TreeNodes, Parent Child Tree drag and drops, and Click-ing on clickable static text control. Certain otherevents can be marked in FDA to force a post.

Note

If you are setting up the Web server forvisually impaired users, the Interactiv-ityLevel must be set to LOW.

In Medium Interactivity mode, the data transfer andevent execution occurs at the same points that LowInteractivity causes a full page refresh. However,unlike low interactivity mode, medium interactivitydoes not send the whole page when these eventshappen. It sends only the queued events and data tothe server. Furthermore, it does not do a whole pagerefresh. It uses JavaScript and DHTML to repaintonly the changed controls. The page flash does nothappen in this mode.

In High interactivity, events and data are transferredfar more frequently. It posts when critical eventshappen. It also posts whenever there is a change onthe form. For example, it posts whenever a control isexited and changed, or when grid columns are exitedand changed. It sends only the queued events anddata to the server. Furthermore, it does not do a



[ERPINTERACTIVITY]


whole page refresh. It uses JavaScript and DHTMLto repaint only the changed controls. The page flashdoes not happen in this mode.

Note

There is not a perceived performance dif-ference between High Interactivity and Me-dium Interactivity, because neither levelcauses a page refresh. The differencebetween these levels is in the amount andsize of network traffic. High Interactivityhas more traffic, but it is small in size. Me-dium Interactivity has less traffic but moredata because it sends a batch of events atone time.

MultipleBrowserEnabled= FALSE This setting determines whether to launch multipleapplications in seperate browsers from Task Ex-plorer and portal links. Valid values are TRUE/FALSE. Default value is FALSE

MaxOpenBrowsers= 10 [1-n] The default value is 10.

This is the maximum number of open browsers auser can have at any time. When this limit isreached, the system will NOT open the newbrowser. Instead, it will display the list of currentopen browsers and ask the user to close one before anew one can be opened.

DBFetchLimitBeforeWarning= 500 The default value is 500.

Maximum number of records that is retrieved from aQuery / Find before a warning is issued. This warn-ing allows the user to modify the query so that itdoesn't retrieve so many records.

The Web Server displays a warning for every 500records. For example, if you do a Find and the queryretrieves 1000 records, you'll get a warning. Afteryou click OK, the Web Server will display a secondwarning for the second set of 500 records.

[WEB GUI]This section is used to customize the web GUI interface.

[WEB GUI]


bandwidth= narrow or wide The bandwidth setting is used to customize the GUIinterface to account for networks with low band-width. By default, the PeopleSoft Web Server uses



[WEB GUI]


tab decoration on all EnterpriseOne forms displayedin html. Tab decoration displays tabs with roundedcorners but requires more bandwidth to display inthis format.

Setting the bandwidth to narrow disables tab decor-ation, and uses less bandwidth to display tabs. Usingthis setting, tabs displayed on html forms look like asimple rectangular box.

Setting the bandwidth to wide enables tab decora-tion.

This setting is optional. If it is not set, web decora-tion is wide by default.



Appendix C: Parameters and Values for the jdbj.ini fileThe jdbj.ini file contains configuration information for JDBj, which allows the PeopleSoft Web Serverto access EnterpriseOne databases. The parameters in this file are only used for accessing EnterpriseOnedata, and are ignored for standalone database access.

The critical parameters of the jdbj.ini file are automatically updated during the installation of the WebServerusing the Java Server Installer. However, you can modify these settings after installation using a texteditor.The jdbj.ini.ini file is functionally similar to the jde.ini file on the EnterpriseOne EnterpriseServer.

Tip

It is generally good practice to add comment line to your .ini files to include such information as:

• The current JAS package version (as labeled on the CD)

• The date you manually updated the file

• The person’s name who performed the updates

The sections in the jdbj.ini file are divided into the following categories:

• PeopleSoft EnterpriseOne Data-Specific Sections [119]

• General Sections [122]

PeopleSoft EnterpriseOne Data-Specific SectionsThe following jdbj.ini sections apply only when accessing EnterpriseOne data. These sections are ig-nored for standalone database access.

Setting Description

[JDBj-BOOTSTRAP SESSION][?]

Contains sign on information that provides access to system tables..

[JDBj-BOOTSTRAP DATASOURCE] [120]

Defines the data source where the OCM and some other system tablesreside.

[JDBj-SPEC DATA SOURCE] [121]Defines the data source where the serialized spec tables reside

[JDBj-BOOTSTRAP SESSION]

This information is used to sign on to provide access to system tables. JDBj signs this user on via the secur-ity server during the bootstrap process. if the sign on information is not valid, then no access to the Enter-


priseOne database is possible.

Note

This information in this section should match the corresponding information specified in the [DBSYSTEM SETTINGS] section of the JDE.INI file of your previous installation (before ERP 9).

[JDBj-BOOTSTRAP SESSION]


user= Site-dependent variable User name for logging in to the Enter-priseOne security server.

password= Site-dependent variable Password for logging in to the EnterpriseOnesecurity server.

environment= Site-dependent variable The EnterpriseOne environment that containsthe system tables.

role= *ALL Enter *ALL to access all roles.


This section defines the data source where the OCM and some other system tables reside. JDBj uses this atbootstrap time and later to look up OCM entries on demand. If it is not valid, then no EnterpriseOne data-base access is possible.

Note

This information in this section should match the corresponding information specified in the [DBSYSTEM SETTINGS] section of the JDE.INI file of your previous installation (before ERP 9).



name= Site-dependent variable The name of the data source. This isnot critical for bootstrap connec-tions, but shows up in error mes-sages and in the log file.

(All servers)

databaseType= I = AS/400

O = Oracle

S = SQL Server

Select the type of database used bythe EnterpriseOne system.

(All servers)

Appendix C: Parameters and Values for the jdbj.ini file




W = UDB

server= Site-dependent variable Name of the server.

(AS/400, SQL Server)

database= Site-dependent variable Name of the database.

(Oracle, UDB)

serverPort= Site-dependent variable The port number of the server.

(SQL Server)

physicalDatabase Site-dependent variable The physical database (used as thelibrary qualifier for the AS/400)


owner Site-dependent variable The database owner.

(Oracle, SQL Server, UDB)

lob= true or false Supports lobs.

(Oracle and AS/400)

unicode= true or false Performs unicode conversion.

(SQL Server)

[JDBj-SPEC DATA SOURCE]

This optional section defines the data source where the serialized spec tables reside. JDBj uses these para-meters at bootstrap time and after to look up serialized spec objects on demand. If this section is not spe-cified, then JDBj will use the OCM to find the serialized spec table. If it is not valid, no EnterpriseOnedatabase access is possible.

See the description for the parameters in [JDBj-BOOTSTRAP DATA SOURCE] [120] above for informa-tion about which fields must be filled in for a given database platform.



name= Site-dependent variable The name of the data source. This is not critical for bootstrapconnections, but shows up in error messages and in the log file.

(All servers)





databaseType= I = AS/400

O = Oracle

S = SQL Server

W = UDB

Select the type of database used by the EnterpriseOne system.

(All servers)

server= Site dependent variable Name of the server.


serverPort= Site-dependent variable The port number of the server.

(SQL Server)

database= Site-dependent variable Name of the database.

(Oracle, UDB)

physicalDatabase= Site-dependent variable The physical database (used as the library qualifier for the AS/400)


owner= Site-dependent variable The database owner.

(Oracle, SQL Server, UDB)

lob= true or false Supports lobs.

(Oracle and AS/400)

unicode= true or false Performs unicode conversion.

(SQL Server)

user= Site-dependent variable User name for logging in to the EnterpriseOne server.

password= Site-dependent variable Password for logging in to the EnterpriseOne server.

General SectionsThe rest of the sections apply when accessing both EnterpriseOne and standalone data.

Setting Description

[JDBj-JDBC DRIVERS] [123] Defines JDBC drivers and JDBC specific settings.



Setting Description

[JDBj-ORACLE] [123] Defines the location of the tnsnames.ora file on the Web Server.

[JDBj-LOGS] [124] Enables JDBC tracing from the JDBC drivers.

[JDBj-CONNECTION POOL] [124] Currently, these settings are always used for pooling JDBC connections.

[JDBj-RUNTIME PROPERTIES][?]

These settings correspond to system runtime properties applicable to JDBjlogical connections.

[JDBj-JDBC DRIVERS]

These values are used to specify the JDBC drivers used by the Web Server to access database types. In pre-vious releases of EnterpriseOne, it was not necessary to set Oracle and iSeries drivers because they weredefaults for the Web Server. However, EnterpriseOne does not assume any default drivers in order to avoidJAS classpath exceptions. The Web Server will only load the drivers that you specify in this section.

[JDBC DRIVERS]


Oracle= oracle.jdbc.driver.OracleDriver This driver is used for Oracle databases.

SQLSERVER= com.microsoft.jdbc.sqlserver.SQLServerDriver

This driver is used for the Microsoft JDBCdrivers used with SQL Server 2000.

AS400= com.ibm.as400.access.AS400JDBCDriver This driver is used for DB2 UDB for the AS/400

UDB= com.ibm.db2.jdbc.app.DB2Driver This driver is used for DB2 UDB for Win-dows

[JDBj-ORACLE]

This section defines the location of the tnsnames.ora file on the Web Server. This path is only requiredfor data connections to an Oracle database.


tns= Site-dependent variableSpecifies the location of your Oracletnsnames.ora file. This entry can beleft blank if you are not using Oracle.You must un-comment this statementif you are using an Oracle database.

The default value is:




D:\Oracle\Ora9\ net-work\ADMIN\tnsnames.ora

The value "Ora9" identifies the versionof Oracle you are using. This valuewill change if you install a differentversion of Oracle.

[JDBj-LOGS]

This section enables JDBC tracing from the JDBC drivers.


jdbcTrace= false This setting can enable JDBC tra-cing from the JDBC drivers. It istypically used only for debugging.Enabling JDBC tracing in a produc-tion environement has a negativeimpact on perfomance.

[JDBj-CONNECTION POOL]

These settings are used for pooling JDBC connections.


jdbcPooling= false Currently JDBC pooling is not sup-ported, so even if this setting is en-abled, pooling is still done by JDBj.

MaxConnection= 50 The maximum number of connec-tions to a data source. Connectionrequests beyond this number will bequeued on the next available con-nection.

MinConnection= 0 The minimum number of connec-tions to a data source. When closingold connections, this many will re-main in the pool regardless of use.

PoolGrowth= 5 The number of connections that thesystem creates when a request for aconnection cannot be satisfied withthe current allocation.

InitialConnection= 5 The number of connections to create



upon pool creation.

connectionTimeout 1800000 The time (in milliseconds) before aninactive connection cache is re-moved from the pool.

Before ERP 9, this setting was theConnection parameter in the[cache] section.

CleanPoolInterval= 300000 Specifies how often the pool cleaneris set to clean data sources that havea validation string. Note that the val-ues specified for these keys are inmilliseconds. For example,60000ms is equal to one minute.

The validation string is in the form:

<statemen

ValidationString_x=t>

where x is I, 4, or R for DB2/400,S for SQL Server, O for Oracle

and statement is a SQL statementthat any user can execute.

For example:

ValidationString_I=Select * fromQSYS2.SYSCOLUMNS WHERE1=2

ValidationString_S=Select@@connections

ValidationString_O=Select sysdatefrom dual

maxSize 50 Maximum number of JDBC pre-pared statements cached on eachJDBC connection.

cachePurgeSize5 Number of JDBC statements that

are purged from a JDBC connectionif the maxSize limit is reached.

[JDBj-RUNTIME PROPERTIES]

The settings in this section correspond to system runtime properties applicable to JDBj logical connections.

Note



In each case, the values listed are the defaults. The template default entries are commented out.Remove the pound sign (#) when changing these values.


dataCacheEntrySizeThreshold= 500 Sets the maximum size (in rows) fora single entry in the data cache. If apotential entry exceeds thisthreshold, then it will not be cached.A value of -1 indicates that all eli-gible entries should be cached.

Valid values: -1 or greater

dataCacheEntryThreshold= 100 Sets the maximum size (in entries)for the data cache. If the data cacheexceeds this size, then the least re-cently used entries are removed tomake room for the new entry. Avalue of -1 indicates that there is nomaximum.

forceSingleDataSource= false Indicates whether JDBj should forceoperations involving multiple data-base objects to run against a singledata source. If this is value is true,JDBj will only resolve the physicaldata source for the first database ob-ject involved in an operation. If thisvalue is false, JDBj will resolvephysical data sources for all data-base objects and throw an exceptionif a single operation spans multipledata sources.

Valid values are true, false

resultSetTimeout= 60000 Time (in milliseconds) before a res-ult set will timeout if it has not hadany operations.

We recommend using the defaultsetting.

Valid values: -1 or greater.

Before ERP 9, this setting was theResultSet parameter in the[cache] section.

retryInterval= 0 Retry interval property. Sets the in-terval (in milliseconds) to wait be-fore retrying idempotent databaseoperations. -1 means not to retry, 0means retry immediately.




retryMaximum= 5 Sets the number of times to retryidempotent database operations. -1means to retry indefinitely.


ocmCachePurge= 3600000 Sets the number of millisecondsafter which inactive OCM cacheentries are purged.

0 means to never purge OCM cacheentries.

personalSpecVersions= false Indicates if a user's personal versioncan be read. This is only enforcedduring a read and not during a specgeneration. If it set to a true, the per-sonal version will be returned if itexists, otherwise the public versionwill be returned. If the property isset to a false, then the personal ver-sion will not be read and will defaultto the public version

Valid values: true , false

securityCachePurge= 3600000 Time (in milliseconds) before an in-active service cache entries arepurged. 0 means to never purge ser-vice cache entries.

We recommend using the defaultvalues.

Valid values: 0 or greater

Before ERP 9, this setting was theSecurity parameter in the [cache]section.

serviceCachePurge= 3600000 Time (in milliseconds) before inact-ive service cache entries are purged.0 means to never purge servicecache entries.


Before ERP 9, this setting was theUDCInfo parameter in the [cache]section.

specCachePurge= 3600000 Time (in milliseconds) before inact-ive spec cache entries are purged. 0means to never purge spec cache



entries.


Before ERP 9, this setting was theViewTable parameter in the[cache] section.

specConsistencyCheck= minimal The level of spec consistency check-ing. Set this property to a higherlevel to improve exception mes-sages relating to spec inconsistencyproblems. Set this to a lower levelwhen it is not needed since it maydegrade performance.

Valid values: full, minimal, none

transactionIsolation= default Sets the isolation level to be usedfor transactions.

Valid values: default, none, read un-committed, read committed, repeat-able read, serializable

transactionTimeout= 120000 Time (in milliseconds) before atransaction will timeout. A transac-tion will timeout if it has not hadany operations for the specifiedperiod of time. If this timeout is setto a -1, then the transaction timeoutfeature is disabled. (This currentlyonly happens when JDBj is run aspart of a JAS transaction.)


triggerAutoFetch= none Indicates whether JDBj should auto-matically fetch rows to be changedin order to pass them to OneWorldtriggers. This is needed for certaintriggers to work properly.

Valid values: none, single, all

updatableResultSetTimeout= -1 Time (in milliseconds) before an up-datable result set will timeout if ithas not had any operations. -1 indic-ates that updatable result sets shouldhave the same value as RES-ULT_SET_TIMEOUT.


usageExecutionThreshold= 20000 Maximum time (in milliseconds) fora single database operation to ex-



ecute. If a single database operationtakes longer than this threshold,then the statement and time will belogged as part of usage tracking.


usageFetchSizeThreshold= 500 Expected maximum fetch size (inrows) for a single fetch to return. Ifa single fetch returns more than thanthis threshold, then the actual fetchsize will be logged as part of usagetracking. -1 indicates that any fetchsize is valid.


usageResultSetOpenThreshold= 60000 Maximum time (in milliseconds) fora result set to remain open. If a res-ult set is left open longer than thisthreshold, then the result set andtime will be logged as part of usagetracking. When this setting isreached, the system does not auto-matically close the result set. A us-age result set open threshold valueof -1 indicates that no such usagetracking will occur.


usageTracking= false Enables or disables usage tracking.This setting provides additionaltracking and logging to use duringtesting. Usage tracking does incur aperformance penalty so it should bedisabled for production code.

Valid values: true, false

usageTrackingOutput= log Specifies the destination of usagetracking output.

Valid values: log, exception

usageTransactionActiveThreshold= 120000 Valid values: -1 or greater



enterpriseone tools 8.93 web server installation …...server. to install the web server on a...

Documents