JD Edwards EnterpriseOne Tools

System Administration Guide

Release 8.98 Update 4

E14721-02

March 2011

JD Edwards EnterpriseOne Tools System Administration Guide, Release 8.98 Update 4

E14721-02

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

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

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

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

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

List of Figures

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction to JD Edwards EnterpriseOne Tools System Administration

- 1.1 System Administration Overview

2 Administering the Data Dictionary

- 2.1 Understanding Data Dictionary Administration

- 2.2 Updating Display Decimals in Data Dictionary

- 2.2.1 Forms Used to Update Display Decimals

- 2.2.2 Updating Display Decimals

3 Understanding JD Edwards EnterpriseOne OMW Administration

- 3.1 JD Edwards EnterpriseOne OMW Administration Overview

4 Working with Servers

- 4.1 Understanding the Work With Servers Program (P986116)

- 4.2 Managing Server Jobs

- 4.2.1 Understanding Server Jobs

- 4.2.1.1 Job Status and Priority

- 4.2.1.2 Overriding Printer Location for Jobs

- 4.2.1.3 Viewing Reports Online

- 4.2.1.4 Job Logs

- 4.2.1.5 Terminating Jobs

- 4.2.1.6 Holding and Releasing Jobs

- 4.2.2 Forms Used to Manage Server Jobs

- 4.2.3 Setting Processing Option for Work with Servers (P986116)

- 4.2.4 Checking the Status of Reports

- 4.2.5 Changing the Priority and the Printer for Jobs

- 4.2.6 Printing Jobs

- 4.2.7 Viewing Reports Online

- 4.2.8 Viewing the Logs for a Job

- 4.2.9 Terminating Jobs

- 4.2.10 Holding and Releasing Jobs

- 4.3 Managing Job Queues

- 4.3.1 Understanding Job Queues

- 4.3.1.1 Administering Job Queues

- 4.3.1.2 Overriding a Job Queue

- 4.3.2 Prerequisites

- 4.3.3 Forms Used to Manage Job Queues

- 4.3.4 Adding a Job Queue

- 4.3.5 Copying a Job Queue

- 4.3.6 Changing the Status of a Job Queue

- 4.3.7 Overriding a Job Queue

- 4.4 Managing JD Edwards EnterpriseOne Subsystems

- 4.4.1 Understanding JD Edwards EnterpriseOne Subsystems

- 4.4.1.1 How JD Edwards EnterpriseOne Uses Subsystems

- 4.4.1.2 Enabling Subsystems

- 4.4.1.3 Subsystem Job Records

- 4.4.1.4 Terminating Subsystems

- 4.4.2 Forms Used to Manage JD Edwards EnterpriseOne Subsystems

- 4.4.3 Locating Subsystems Running on a Server

- 4.4.4 Reviewing Job Records for Subsystems

- 4.4.5 Terminating Subsystems

5 Setting Up PIM Synchronization for JD Edwards EnterpriseOne CRM Users

- 5.1 Understanding PIM Synchronization

- 5.1.1 User Defined Codes for PIM

- 5.1.1.1 Understanding the 01|SG UDCs

- 5.1.2 Data Mapped Through PIM Synchronization

- 5.1.2.1 Appointments

- 5.1.2.2 Contacts

- 5.1.2.3 Tasks

- 5.1.3 Prerequisite

- 5.2 Setting the Processing Option for the PIM Server

- 5.3 Setting Up Users for PIM Synchronization

- 5.4 Exporting PIM User Records

- 5.4.1 Exporting All User records

- 5.4.2 Exporting a Selected List of PIM User Records

- 5.5 Importing PIM Synchronization Files into Intellisync Server

6 Enabling Mobile Client Functionality

- 6.1 Understanding Distributed Next Numbers for Mobile Clients

- 6.2 Setting Up Distributed Next Numbers for Mobile Clients

- 6.2.1 Activating Mobile Client Functionality

- 6.2.2 Defining the Starting Next Number

- 6.2.3 Enabling Distributed Next Numbers

- 6.2.4 Setting Up Distributed Next Numbers by System

- 6.2.5 Mapping the JD Edwards EnterpriseOne User ID to the Distributed Next Numbers Application (P950411)

- 6.2.6 Setting Up Distributed Next Numbers by Application

- 6.2.7 Scheduling Updates to Distributed Next Numbers Applications

7 Setting Up Viewable and Configurable Portlets

- 7.1 Understanding Viewable and Configurable Portlet Types

- 7.2 Initializing Viewable and Configurable Portlets

- 7.2.1 Prerequisites

- 7.2.2 Initializing Viewable HTML, URI, IURI Portlets

- 7.2.3 Initializing Configurable HTML, URI, IURI Portlets

- 7.2.4 Initializing a Viewable SRM Portlet

- 7.2.5 Initializing a Configurable SRM Portlet

8 Dropping Indexes from a Table

- 8.1 Understanding the Index Selection Tool

- 8.1.1 Flagging indexes

- 8.1.2 Determining the Data Source

- 8.1.3 Index Selection Logs

- 8.2 Using the Index Selection Tool

- 8.2.1 Forms Used with the Index Selection Tool

- 8.2.2 Adding a Table to the Index Selection Tool

- 8.2.3 Selecting a Data Source

- 8.2.4 Dropping a Single Index from a Table

- 8.2.5 Dropping Multiple Indexes from a Table

- 8.2.6 Restoring Indexes to a Table

- 8.2.7 Viewing the Index Selection Logs

9 Using Interactive Versions for Applications

- 9.1 Understanding Interactive Versions for Applications

- 9.1.1 How Processing Options Affect Versions

- 9.1.2 How Interactive and Batch Versions Differ

- 9.2 Working with Interactive Versions

- 9.2.1 Understanding How to Work with Interactive Versions

- 9.2.2 Working with Version Detail for Interactive Versions

- 9.2.3 Copying an Interactive Version

- 9.2.4 Creating (Adding) an Interactive Version

10 Working with User Defined Codes

- 10.1 Understanding User Defined Codes

- 10.1.1 UDCs, UDC Types, and Category Codes

- 10.1.1.1 Example: User Defined Codes in Address Book

- 10.2 Understanding UDC and UDC Type Customization

- 10.2.1 Consequences of Customizing UDCs

- 10.3 Understanding UDC Tables

- 10.3.1 Prerequisite

- 10.4 Customizing User Defined Codes

- 10.4.1 Change a UDC

- 10.4.2 Adding a UDC

- 10.4.3 Deleting a UDC

- 10.5 Customizing UDC Types

- 10.5.1 Understanding How to Customize UDC Types

- 10.5.2 Understanding How to Add UDC Types

- 10.5.3 Prerequisite

- 10.5.4 Changing a UDC Type

- 10.5.5 Adding a UDC Type

- 10.5.6 Deleting a UDC Type

- 10.6 Translating User Defined Codes into Alternate Languages

- 10.6.1 Understanding How to Translate User Defined Codes into Alternate Languages

- 10.6.2 Translating UDC Type Descriptions into Alternate Languages

- 10.6.3 Translate UDC Descriptions into Alternate Languages

11 Working with User Overrides

- 11.1 Understanding User Overrides

- 11.1.1 User Overrides Overview

- 11.1.2 Search Hierarchy

- 11.1.3 Cached Override Information

- 11.2 Setting Up User Overrides

- 11.2.1 Understanding How to Create User Overrides

- 11.2.2 Creating User Overrides

- 11.2.3 Changing an Individual User Override to a Group User Override

- 11.2.4 Fixing User Overrides after a Form Change

12 Working with Vocabulary Overrides

- 12.1 Understanding Vocabulary Overrides

- 12.2 Creating Vocabulary Overrides

- 12.2.1 Forms Used to Work with Vocabulary Overrides

- 12.2.2 Accessing Vocabulary Overrides from JD Edwards EnterpriseOne Solution Explorer

- 12.2.3 Accessing Vocabulary Overrides from JD Edwards EnterpriseOne OMW

- 12.2.4 Creating Vocabulary Overrides

- 12.2.5 Creating Batch Vocabulary Overrides

- 12.2.6 Reviewing Vocabulary Overrides

- 12.2.7 Resetting a Vocabulary Override

- 12.2.8 Resetting All Vocabulary Overrides on a Form (Interactive and Batch)

13 Using the Scheduler Application

- 13.1 Understanding the Scheduler Application

- 13.2 Working with the Job Scheduler

- 13.2.1 Understanding the Job Scheduler

- 13.2.2 Prerequisite

- 13.2.3 Forms Used to Work with the Job Scheduler

- 13.2.4 Setting Processing Options for the Job Scheduler

- 13.2.4.1 Display

- 13.2.4.2 Process

- 13.2.4.3 Defaults

- 13.2.5 Scheduling a Job

- 13.2.6 Scheduling a Recurring Job

- 13.2.7 Revising a Scheduled Job

- 13.2.8 Reviewing All Jobs or Local Jobs

- 13.3 Using Advanced Scheduling Options

- 13.3.1 Understanding Advanced Scheduling Options

- 13.3.2 Forms Used to Work with Advanced Scheduling Options

- 13.3.3 Overriding the Environment

- 13.3.4 Overriding Job Expiration Specifications

- 13.3.5 Defining When the Scheduler Resubmits a Job

- 13.3.6 Overriding Batch Application Specifications

- 13.3.7 Adding Values to a Report Interconnect

- 13.4 Reviewing the Job Schedule

- 13.4.1 Understanding Job Schedule Reviewing

- 13.4.2 Forms Used to Review the Job Schedule

- 13.4.3 Reviewing All Job Schedules

- 13.4.4 Changing the Launch Status of a Job

- 13.4.5 Viewing Job Details

- 13.4.6 Setting the Job Status Manually

- 13.4.7 Resetting the Job Schedule

- 13.5 Working with the Scheduler Server

- 13.5.1 Understanding the Scheduler Server

- 13.5.1.1 Control Record

- 13.5.1.2 Dispatch Function

- 13.5.1.3 Launch Loop

- 13.5.1.4 Job Monitor Loop

- 13.5.2 Forms Used to Work with the Scheduler Server

- 13.5.3 Stopping or Restarting the Scheduler Server

- 13.5.4 Pausing the Job Launcher or Job Monitor

- 13.5.5 Resetting the Scheduler Server

- 13.5.6 Refreshing the Scheduler Server Settings

- 13.5.7 Modifying the Scheduler Server and Monitor Sleep Time

- 13.6 Creating Daylight Savings Rules

- 13.6.1 Understanding Daylight Savings Rules

- 13.6.2 Prerequisites

- 13.6.3 Adding Daylight Savings Rules

- 13.6.4 Adding an Additional Daylight Savings Record to a Daylight Savings Rule

- 13.6.5 Revising Daylight Savings Rules

- 13.7 Running Scheduler Reports

- 13.7.1 Printing the Scheduled Jobs or Purge Scheduled Jobs Report

14 Understanding Media Objects and Imaging

- 14.1 Media Objects

- 14.1.1 JD Edwards EnterpriseOne Text Items

- 14.2 Imaging

- 14.3 Media Object Queues

- 14.3.1 Image Media Objects

- 14.3.2 OLE Media Objects

- 14.3.3 URL Media Objects

- 14.4 Media Object Tables

- 14.5 Language Considerations for Media Objects

15 Setting Up Media Objects and Imaging

- 15.1 Understanding Media Object Processing

- 15.1.1 Prerequisite

- 15.1.2 Enabling JD Edwards EnterpriseOne to Use Media Objects

- 15.1.3 Adding a Language-Specific Media Object Attachment

- 15.2 Setting Up Media Object Queues

- 15.2.1 Forms Used to Set Up Media Object Queues

- 15.2.2 Adding a Media Object Queue

- 15.2.3 Defining the Location of a Media Object Queue

- 15.2.4 Deleting a Media Object Queue

- 15.3 Setting Up Imaging

- 15.3.1 Understanding Imaging

- 15.3.1.1 Understanding Flow for Imaging Systems

- 15.3.2 Forms Used to Set Up Imaging

- 15.3.3 Enabling Imaging in Media Objects

- 15.4 Setting up the HTML Editor

16 Administering Text Search Indexes

- 16.1 Understanding Text Search Indexes

- 16.2 Defining Text Search Indexes

- 16.2.1 Understanding Text Search Indexes

- 16.2.2 Forms Used to Define Text Search Indexes

- 16.2.3 Designating Data Sources for a Business View

- 16.2.4 Defining Media Objects for a Text Search Index

- 16.2.5 Defining Languages for a Text Search Index

- 16.3 Building Text Search Indexes

- 16.4 Defining Text Search Properties

- 16.4.1 Understanding Text Search Properties

- 16.4.2 Forms Used to Define Text Search Properties

- 16.4.3 Adding a New Text Search Business View-Data Source Pair

- 16.4.4 Defining Stop Words

- 16.4.5 Defining Synonyms

- 16.4.6 Defining Topics

- 16.5 Understanding Text Search with Secure Enterprise Search

- 16.5.1 Configuring SES for Text Search

- 16.5.1.1 Prerequisites

- 16.5.1.2 Configuring Enterprise Server for SES

- 16.5.1.3 JAR files required for SES Admin Api's

- 16.5.1.4 JDE.INI settings for Text Search Kernel (Enterprise Server)

- 16.5.1.5 JDE.INI Settings for Media Object Queue for IBM i Enterprise Server Only

- 16.5.2 Understanding Text Search Indexes

- 16.5.2.1 Designating Data Sources for a Business View

- 16.5.2.2 Defining Media Objects for a Text Search Index

- 16.5.2.3 Defining Languages for a Text Search Index

- 16.5.2.4 Building Text Search Indexes

- 16.5.3 Understanding Text Search Properties

- 16.5.3.1 Forms Used to Define Text Search Properties

- 16.5.3.2 Global Properties

- 16.5.3.3 Business View/Data Source Specific Properties

- 16.5.3.4 Troubleshooting

17 Setting Up Application Failure Recovery

- 17.1 Understanding Application Failure Recovery

- 17.1.1 Prerequisite

- 17.2 Enabling/Disabling Application Failure Recovery

- 17.3 Saving Application Data

18 Using the Universal Table Browser

- 18.1 Understanding the Universal Table Browser

- 18.2 Working with the Universal Table Browser

- 18.2.1 Viewing the Data in Tables

- 18.2.2 Viewing Column Properties in a Table

19 Working with Flat File Encoding

- 19.1 Understanding Flat File Encoding

- 19.1.1 Example: Setting Up Flat File Encoding Records

- 19.2 Work with Flat File Encoding Records

- 19.2.1 Forms Used to Work with Flat File Encoding Records

- 19.2.2 Adding a Flat File Encoding Record

- 19.2.3 Activating a Flat File Encoding Record

20 Understanding Naming Conventions

- 20.1 Path Codes

- 20.2 Data Sources

- 20.2.1 Data Source Description

- 20.3 Package Names

- 20.4 Server Names

- 20.5 Workstation Names

Glossary

Index

List of Figures

- 4-1 Logical sequence of events associated with subsystems

- 5-1 E1 - PIM User Information Setup form

- 13-1 The scheduling process

- 15-1 JD Edwards EnterpriseOne imaging architecture

- 15-2 Imaging process flow

- 15-3 Web Runtime Form

- 15-4 ActiveX Controls Option

- 16-1 Oracle Enterprise Search

- 16-2 Text Search Engine Selection

- 16-3 Text Search Engine Selection

- 16-4 Text Search Properties Revisions Form

Preface

Welcome to the JD Edwards EnterpriseOne Tools System Administration Guide.

Audience

This guide is intended for system administrators who are responsible for performing JD Edwards EnterpriseOne administration tasks.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Related Documents

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

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

To navigate to this page from the My Oracle Support home page, click the Knowledge tab, and then click the Tools and Training menu, JD Edwards EnterpriseOne, Welcome Center, Release Information Overview.

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

Conventions

The following text conventions are used in this document:

Convention

Meaning

Bold

Indicates field values.

Italics

Indicates emphasis and JD Edwards EnterpriseOne or other book-length publication titles.

Monospace

Indicates a JD Edwards EnterpriseOne program, other code example, or URL.

1 Introduction to JD Edwards EnterpriseOne Tools System Administration

This chapter contains the following topics:

- Section 1.1, "System Administration Overview"

1.1 System Administration Overview

This guide describes the tools necessary to administer JD Edwards EnterpriseOne and perform system maintenance. This guide also contains instructions on how to use various JD Edwards EnterpriseOne administrative applications to increase the usability of JD Edwards EnterpriseOne software and increase system performance.

In the planning phase of your implementation, take advantage of all Oracle sources of information for JD Edwards EnterpriseOne, including the installation guides and troubleshooting information.

2 Administering the Data Dictionary

This chapter contains the following topics:

- Section 2.1, "Understanding Data Dictionary Administration"

- Section 2.2, "Updating Display Decimals in Data Dictionary"

2.1 Understanding Data Dictionary Administration

Just as a dictionary contains word definitions, Oracle's JD Edwards EnterpriseOne data dictionary is a central repository that contains data item definitions and attributes. These attributes determine how a data item:

- Appears on reports and forms.

- Validates data entry within an application.

- Assigns column and row descriptions.

- Provides text for field-sensitive help.

The data dictionary is active because changes that you make are automatically reflected in applications without having to recompile the software.

You should assign one or two people to be the data dictionary administrator for each application area in the enterprise. Data dictionary administrators should be experienced with JD Edwards EnterpriseOne and have a comprehensive knowledge of their product area, such as finance or manufacturing. The data dictionary administrator makes all additions, changes, and deletions to data items for the product group. Such changes are reflected in the pristine data dictionary on the enterprise server.

If the setup is similar to the suggested typical customer configuration, then all environments share the same data dictionary. Therefore, the administrator can sign on to any environment to make changes. We recommend that you use the Security Workbench to assign application security on the Data Dictionary application (P92001) to prevent unauthorized users from making data dictionary changes.

2.2 Updating Display Decimals in Data Dictionary

Data items that belong to the QTYINV data item class come with the display decimal set at 0 (zero). You can change the display decimal to any number up to 8. For example, if you change the display decimal to 4, instead of seeing 100 you will see 100.0000.

Important:
You should change the display decimal value in a CRP environment before any live production data is entered. JD Edwards EnterpriseOne does not have a data conversion feature, so if you change display decimals after users have entered data, the data entered before changing the display decimals will be wrong.

2.2.1 Forms Used to Update Display Decimals

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

Report Management (GH9111), Batch Versions (P98305)

Work with existing versions of a batch program.

Version Prompting

W98305D

Select the version on the Work With Batch Versions - Available Versions form, and then click Select.

Submit a batch version for processing.

2.2.2 Updating Display Decimals

Enter GH9111 in the Fast Path. Double-click Batch Versions.

1. On the Work With Batch Versions - Available Versions form, enter R9200100 in the Batch Application field and then click Find.

2. Select one of these versions and click Select:

- Update Display Decimals for Class - Proof
The proof version produces only a report of what the process would do if run in final mode.

- Update Display Decimals for Class - Final
The final version actually makes the changes.

3. On the Version Prompting form, click Data Selection and then click Submit.

4. On the Data Selection form, create this statement:
If BC Data Item Class (F9210) = QTYINV

Note:
QTYINV is the only data item class for which you can modify display decimals. If you modify other data item classes, you must research and test how the modifications affect the software. Also, if you modify which data items reside in the QTYINV data item class, you must research and test how the modifications affect the software.

5. If you changed the Data Selection statement, click OK.

6. On the Processing Options form, complete these fields and then click OK:

- Enter 1 to run in Update Mode or 0 to run in Proof Mode. The default is 0.

- Data Item Class

- New Data Display Decimals

7. On the Printer Selection form, click OK to run the batch application.

8. On each workstation, delete these spec files:

qlbltbl.ddb, qlbltbl.xdb

dddict.ddb, dddict.xdb

ddtext.ddb, ddtext.xdb

9. To push the display decimal changes out to users, run R92TAM on the server on which the changes were made.

3 Understanding JD Edwards EnterpriseOne OMW Administration

This chapter contains the following topic:

- Section 3.1, "JD Edwards EnterpriseOne OMW Administration Overview"

3.1 JD Edwards EnterpriseOne OMW Administration Overview

JD Edwards EnterpriseOne OMW automates many of the object management tasks that users perform in the software. Much of this automation requires careful configuration by the system administrator through the Object Management Workbench Configuration program (P98220).

Use P98220 to configure these features:

Option

Description

Constants

Enables you to set general constants pertaining to JD Edwards EnterpriseOne OMW projects.

SAR System Integration

Enables you to disable SAR system integration with JD Edwards EnterpriseOne OMW and, thus, JD Edwards EnterpriseOne development tools.

Logging System

Enables you to specify the project and object events to be logged. In the event that logging fails, you can also disable development or allow development but disable transfers.

Object Action Notification

Enables you to enable and disable Object Action Notification, which sends a notification message when an action such as checkin or checkout is performed on an object.

Notification Setup

Enables developers to be notified, using subscription, when actions are performed on an object.

Activity Rules

Enables you to add and modify project statuses and object transfer activity rules.

User Roles

Enables you to maintain user roles.

Allowed Actions

Enables you to assign to a user role the actions allowed for each object type during a specific project status.

Save Locations

Enables you to add, modify, and delete the locations where you save objects.

For instructions on how to perform these JD Edwards EnterpriseOne OMW administrative tasks, see JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

4 Working with Servers

This chapter contains the following topics:

- Section 4.1, "Understanding the Work With Servers Program (P986116)"

- Section 4.2, "Managing Server Jobs"

- Section 4.3, "Managing Job Queues"

- Section 4.4, "Managing JD Edwards EnterpriseOne Subsystems"

4.1 Understanding the Work With Servers Program (P986116)

The Work With Servers program (P986116) in Oracle's JD Edwards EnterpriseOne provides a central location from which system administrators can monitor and control:

- Server jobs

- JD Edwards EnterpriseOne subsystems

As a system administrator, you can use the Work With Servers program to print, view, remove, terminate, release, or hold any jobs that currently reside in a queue on any JD Edwards EnterpriseOne server. Similarly, workstation users can control only those jobs submitted by them. This option is generally restricted to only those jobs associated with a specific user ID.

Also, you can use the Work With Servers program to end and to stop JD Edwards EnterpriseOne subsystems, and to view the status of JD Edwards EnterpriseOne subsystems that are running or are waiting to process jobs.

4.2 Managing Server Jobs

This section provides an overview of server jobs and discusses how to:

- Set processing option for Work With Servers.

- Check the status of reports.

- Change the priority and the printer for jobs.

- Print jobs.

- View reports online.

- View the logs for a job.

- Terminate jobs.

- Hold and release jobs.

4.2.1 Understanding Server Jobs

By using the Work With Servers application, system administrators can print, view, and delete job records from the outqueue. They can also terminate, release, or hold any jobs that currently reside in a queue on any JD Edwards EnterpriseOne server. Similarly, using the Submitted Job Search form, users can, in general, control only those jobs submitted by them.

You should use JD Edwards EnterpriseOne security to restrict access to the Work With Servers application. In general, access to this program should be granted only to administrator-level users because the ZJDE0001 version of the Work With Servers program enables users to view and control server jobs for all users. End users should be restricted to the ZJDE0002 version, which is known as the Submitted Job Search form. This version of the application restricts users to viewing and modifying only those jobs that were submitted under their user ID initially. Both programs are located on the System Administration Tools menu (GH9011).

4.2.1.1 Job Status and Priority

After you submit the report, you can check the status of the job in the queue. Depending on the status of the job, you can perform tasks such as printing or deleting the report, viewing the report output online, and holding the report in the queue.

You can also move the priority of the job to a lower or higher status while the job is at the status of W (Waiting).

4.2.1.2 Overriding Printer Location for Jobs

You can override the location where the job prints. For jobs with a status of D (Done) and E (Error), you can send the job directly to the default printer without viewing the PDF file online. A status of D means that the processing for the job completed successfully. A status of E means that an error occurred during processing. If you print a job with a status of E, you print an error log to aid you when you troubleshoot the report.

4.2.1.3 Viewing Reports Online

After the job finishes processing on the server, you can view the report output online. For most jobs, the output is in Portable Document Format (PDF), which can be viewed with Adobe Acrobat Reader. When you view the report output online, the system also creates a PDF file for the report in the following directory on the workstation:

\812\PrintQueue

You can attach PDF files to email messages; move or copy the files; and, because most current web browsers can read PDF files, post the reports to a web site. Also, you can copy text from Acrobat Reader to the clipboard and paste that text into other applications.

4.2.1.4 Job Logs

You can view logs that detail the steps taken while the job processed. From the Submitted Job Search form, you can access the jde.log and the jdedebug.log for the report. These logs are helpful if you need to troubleshoot a report that resulted in error. These logs exist on the machine where the job ran.

The jde.log is a general-purpose log used to track error messages generated by JD Edwards EnterpriseOne processing. The jde.log tracks any fault that might occur within the software, including whether the sign on is successful. When you are looking for startup errors, you should read the jde.log from the top down. For other errors, you should read from the bottom up.

The jdedebug.log contains API calls, BSFN logs, and SQL statements, as well as other messages. You can use this log to determine at what time normal execution stopped. The system does not use thejdedebug.log to track errors; instead, it uses this log to track the timing of processes.

4.2.1.5 Terminating Jobs

You can manually terminate a job that is processing. When you terminate a job, you do not delete it; rather, you move the job to the status of E (Error). With the job at the status of E, you can print an error log or delete the job.

4.2.1.6 Holding and Releasing Jobs

If a job is at the status of W (waiting), you can hold the job. You might choose to hold a job if the job is large enough to affect the performance of the server on which it processes. You can release a job when server performance is not an issue, such as after regular business hours.

Note:
If you want to stop a job that is at a status of P (Processing), you must terminate the job. You cannot restart a job after you terminate it; you must resubmit the job to the server.

See Also:

- JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide.

4.2.2 Forms Used to Manage Server Jobs

Form Name

FormID

Navigation

Usage

Work With Servers

W986116A

System Administration Tools (GH9011), Data Source Management, Work With Servers (P986116).

Select a server in which you want to locate a job.

Submitted Job Search

W986110BA

On the Work With Servers form, from the Row menu, select Server Jobs.

Print, terminate, hold, release, or view a job. Users can manage jobs submitted by their user ID initially. Depending on the security level, you can change the User ID field and the Job Queue field to search for other jobs.

Job Maintenance

W986110BC

On the Submitted Job Search form, select a job with which to work and click Select.

Review information about the batch job, modify the priority of the job, or change the printer on which the job will print.

Printer Selection

W986162B

On the Submitted Job Search form, select a job and then select Print from the Row menu.

Override printer-specific information.

View Logs

W986110BD

On the Submitted Job Search form, select the job for which you want to view a log, and then select View Logs from the Row menu.

View the jde.log and the jdedebug.log.

4.2.3 Setting Processing Option for Work with Servers (P986116)

Although processing options are set up during the JD Edwards EnterpriseOne implementation, you can change processing options each time you run a batch application.

1. Security Flag

Use this processing option to specify how submitted jobs can be viewed. Values are:

Blank

No Security

1

Allow users to view jobs by group.

2

Allow users to view only their own jobs.

4.2.4 Checking the Status of Reports

Access the Submitted Job Search form.

User ID

Change the user ID if you want to work with a report submitted by a different user. You can use a wildcard (*) to find a specific user. The default user ID is the user logged on to the current session.

Job Queue

Enter the name of the logical queue on the server for which you want to view jobs.

Status

Click the search button in the Status field to read the UDCs for status codes in the installation.

4.2.5 Changing the Priority and the Printer for Jobs

Access the Work With Servers form.

1. Select a server with which to work and, from the Row menu, select Server Jobs.
By default, the Submitted Job Search form lists jobs for the User ID for the requesting workstation. Depending on the application security level, you can change the User ID field and the Job Queue field to search for other jobs.

Note:
A job must be at a status of W (Waiting) to change the priority.

2. Select a job with which to work and click Select.

3. On the Job Maintenance form, modify the information in the Job Priority field and click OK. The value that you enter in this field determines how the job will execute based on this priority. Values 0-9 are valid, where 0 is the highest priority.

4.2.6 Printing Jobs

Access the Work With Servers form.

1. From the Row menu, select Server Jobs.

2. On the Submitted Job Search form, select the job that you want to print, and then choose Print from the Row menu.
The Printer Selection form appears. This form provides printer-specific information as well as information about the format of the report.

3. To print the job, click OK.

4.2.7 Viewing Reports Online

Access the Work With Servers form.

Note:
Before you view the report online, verify that you have Adobe Acrobat Reader installed on the workstation.

1. Select a server from the list and then click Select or select Server Jobs from the Row menu.

2. On the Submitted Job Search form, select the job that you want to view and then select View Job from the Row menu.
Adobe Acrobat Reader displays an online version of the report output.

4.2.8 Viewing the Logs for a Job

Access the Work With Servers form.

1. Select the server that processed the job that you want to view, and click Select, or select Server Jobs from the Row menu.

2. On the Submitted Job Search form, select the job for which you want to view a log, and then select View Logs from the Row menu.
The View Logs form appears. On this form, you can view the jde.log and the jdedebug.log.

3. Click OK to view the logs.

Note:
If you choose both the jde.log and the jdedebug.log, the logs open in the same window. To view the logs separately, you must select the logs separately.

4.2.9 Terminating Jobs

Access the Work With Server form.

1. Select a server from the list or use the query by example row to select a specific server.

2. Click Select or select Server Jobs from the Row menu.

3. On the Submitted Job Search form, select the job to terminate, and then select Terminate from the Row menu.

Note:
A job must be at a status of P (processing) to terminate the job.

4. Click Find to update the detail area.
The status of the job changes to E (error).

4.2.10 Holding and Releasing Jobs

Access the Work With Servers form.

1. Select a server from the list or use the query by example row to select a specific server.

2. Click Select or select Server Jobs from the Row menu.
The Submitted Job Search form appears.

3. To hold a job, select the job and then select Hold from the Row menu.

4. Click Find to update the detail area.
The status of the job changes to H (Hold).

5. To release a job, select the job and then select Release from the Row menu.
The job must be at the status of H (Hold).

6. Click Find to update the detail area.
The status of the job changes to reflect the position of the job in the queue, for example, W (Waiting), S (In Queue), or P (Processing).

4.3 Managing Job Queues

This section provides an overview of job queues and discusses how to:

- Add a job queue.

- Copy a job queue.

- Change the status of a job queue.

- Override a job queue.

4.3.1 Understanding Job Queues

Each JD Edwards EnterpriseOne server instance starts a queue kernel process that manages batch processes across operating system platforms. The process keeps track of all jobs that are submitted and controls the order in which the jobs run.

JD Edwards EnterpriseOne uses two tables to maintain queue records:

- Job Control Status Master table (F986110), which maintains records on the status of each job submitted to a queue.

- Queue Control Status Master table (F986130), which stores the names of each queue, such as QBATCH, the name of the server on which the queue runs, the port number for the server instance, the queue status and type, and the maximum number of active jobs allowed.

Note:
Since F986130 is a system table, be sure to account for it when you map objects using Object Configuration Manager (OCM).

The following list summarizes how the software, using the queue kernel, manages a UBE that you launch:

- Starts queue kernel when the server instance starts.

- Verifies that a record exists in the F986130 table for the queue to which the job is submitted. If the job is intended for a non-EnterpriseOne queue, verifies that the native queue (for example, IBM i) exists.

- Inserts job record into the F986110 table.

- Sends a message to the queue kernel that the new job exists.

- Adds the job to a wait list.

- Schedules the job or submits it to the native queue.

- Starts the job.

- Runs the job.

- Updates the job record in the F986110 table upon receiving a message from the UBE process that the job is complete.

- Removes the job from the list of active jobs.

- Schedules another job.

The queue kernel also follows a subroutine in scheduling jobs. The following list summarizes the subroutine that the queue kernel follows:

- Verifies that jobs in the queue are waiting to be run.

- Verifies that the number of jobs waiting to be run is less than the maximum number of jobs allowed for the queue.

- Takes the highest priority job from the wait list and updates its status to S (Submitted).

- Removes the job from the wait list and adds it to the active list.

4.3.1.1 Administering Job Queues

Use the Job Queue Maintenance application (P986130) to define and manage job queues. This application enables you to dynamically administer job queues. You can use this application to create, modify, copy, delete, or change the status of job queues, regardless of platform. For example, you can use this application to add a queue record to the Queue Control Status Master table (F986130). You can also revise an existing queue record. For example, you might want to change the maximum number of jobs that can run in a queue.

In addition, when you set up job queues, you can define a default queue in which to submit jobs.

4.3.1.2 Overriding a Job Queue

When you prepare to submit a batch application, you can change the values of the parameters that define the submission by overriding the job queue. Overriding the job queue means that you change the job queue to which the job is submitted on the server.

To override the job queue for a batch version, you launch the Batch Versions application (P98305), select a batch version, and access the Advanced Version Prompting form (W98305I). The override queue must be one that is available for the server and port.

In working with the Advanced Version Prompting form, you can override the job queue only if the queue kernel is active and if the batch version is mapped to run on the server. If the batch version is mapped to run locally, you cannot override the job queue, even if the queue kernel is active, unless you select the Override Location option.

Note:
Overriding the job location means that you change the machine that will run the batch application. For example, a batch application might run locally by default. You can override the processing location to a server, and the batch application will run on the server. Conversely, you can change the processing location from a server to a workstation.

JD Edwards EnterpriseOne displays a Verify Overriding the Job Queue form if the job runs locally and you do not override the processing location.

The status of the queue kernel and the default processing location for the batch application determine the way the Override Job Queue option appears in the Advanced Version Prompting form. The following table summarizes the queue kernel status and processing location combinations that can occur, and the effect each combination has on the Override Job Queue option:

Queue Kernel Status

UBE Processing Location

Status of Job Queue Override Option

Inactive

Local or server

Not visible

Active

Local

Visible but disabled

Active

Local, but Override Location option chosen

Enabled

Active

Server

Enabled

4.3.2 Prerequisites

Before you work with job queues, you must activate the queue kernel. To do so, perform these tasks:

- Make sure that the server's jde.ini file contains these settings:

[JDENET_KERNEL_DEF14]
krnlName=QUEUE KERNEL
dispatchDLLName=jdekrnl.dlldispatchDLLFunction=_DispatchQueueMessage@28max
NumberofProcesses=1numberofAutoSartProcesses=0

[DEBUG]
QKLog=0

Where a value of 0 means that only an error log is generated. You can change the setting to 1 if you need to generate debug logs for troubleshooting purposes.

[NETWORK QUEUE SETTINGS]
QKActive=1QKOnIdle=300

Where a value of 1 means that the queue kernel is active and a value of 300 sets the queue kernel on idle time to 300 seconds.

- Add the following setting to the client jde.ini file:

[NETWORK QUEUE SETTINGS]
QKActive=1

4.3.3 Forms Used to Manage Job Queues

Form Name

FormID

Navigation

Usage

Work With Job Queues

W986130A

Batch Processing Setup menu (GH9013), Job Queues (P986130).

Add a job queue and change the status of a queue.

Job Queue Revisions

W986130B

On the Work With Job Queues form, click Add.

Add information for a new job queue. Revise or copy a job queue.

Work With Batch Versions - Available Versions

W98305A

Report Management (GH9111), Batch Versions (P98305).

Override a job queue.

Version Prompting

W98305D

On the Work With Batch Versions - Available Versions form, select a version, and then click Select.

Access the Advanced Version Prompting form. Enter data selection or data sequencing.

Advanced Version Prompting

W983051

On Version Prompting, select Advanced from the Form menu.

Select the Override Job Queue option.

Job Queue Search

W986130C

On Version Prompting, click Submit.

Find and select the job queue that you want to override.

4.3.4 Adding a Job Queue

Access the Work With Job Queues form.

1. Click Add.

2. On the Job Queue Revisions form, in the Host field, enter the name of the server on which the queue will run.

3. Enter the name of the queue in the Job Queue field.

4. In the Job Queue Status field, enter 01 if you want the queue to be active, or 02 if you want the queue to be inactive.

5. In the Queue Type field, define whether the queue is a JD Edwards EnterpriseOne queue or a non-EnterpriseOne queue.
A non-EnterpriseOne queue works only on the IBM i server.

6. In the Maximum Batch Jobs field, define the maximum number of jobs that can run in the queue.

7. In the Port Number field, specify the port number for the server instance on which the queue will run.

8. In the Default Queue field, check the box for the default queue, or leave it blank for a non-default queue.

4.3.5 Copying a Job Queue

Access the Work With Job Queues form.

1. On the Work With Job Queues form, find the queue that you want to copy and click Copy.

2. On Job Queue Revisions, you can modify any of these fields:

- Host

- Job Queue

- Job Queue Status

- Queue Type

- Maximum Batch Jobs

- Port Number

- Default Queue

3. Click OK to complete the copy.

4.3.6 Changing the Status of a Job Queue

Access the Work With Job Queues form.

1. On the Work With Job Queues form, find the queue whose status you want to change.

2. From the Row menu, select Change Status.
JD Edwards EnterpriseOne changes the status of the queue from Active to Inactive or from Inactive to Active, depending on its previous status.

4.3.7 Overriding a Job Queue

Access the Work With Batch Versions - Available Versions form.

1. On the Work With Batch Versions - Available Versions form, find a version of a job that you want to submit and click Select.

2. On the Version Prompting form, select Advanced from the Form menu.

3. On the Advanced Version Prompting form, select the Override Job Queue option and click OK.

Note:
If the queue kernel is not active, this option is not visible.

4. In the Version Prompting form, select either, both, or neither of these options and click Submit:

- Data Selection

- Data Sequencing

5. On the Job Queue Search form, find the name of an available queue for the host and port name.

6. Select the queue that you want to override to and click Select.

7. Complete the data selection and sequencing and the processing options required to submit the job and select a printer, if necessary.

4.4 Managing JD Edwards EnterpriseOne Subsystems

This section provides an overview of JD Edwards EnterpriseOne subsystems and discusses how to:

- Locate subsystems running on a server.

- Review job records for subsystems.

- Terminate subsystems.

4.4.1 Understanding JD Edwards EnterpriseOne Subsystems

Within JD Edwards EnterpriseOne, subsystems are defined as continuously running batch jobs that run independently of, and asynchronously with, JD Edwards EnterpriseOne applications. Subsystem jobs function within the logical process of the operating system or the queue defined for the server platform. You can configure JD Edwards EnterpriseOne to use one or more subsystems.

The term subsystem is an industry-wide generic term that usually indicates a system that is a subprocess to an operating system. On IBM i server platforms, a subsystem is a logical process that is used to run system jobs, whether they are JD Edwards EnterpriseOne or other application jobs. For UNIX, JD Edwards EnterpriseOne subsystem is functionally equivalent to a daemon. On UNIX and Windows server platforms, system jobs are processed in queues; these queues are functionally equivalent to subsystems on the IBM i platform.

4.4.1.1 How JD Edwards EnterpriseOne Uses Subsystems

Some JD Edwards EnterpriseOne applications are designed to use subsystems to complete needed work. For example, you can instruct Sales Order Processing to print pick slips through a JD Edwards EnterpriseOne subsystem. You activate a subsystem through the processing options of a batch application. Then you create a specific version of the batch application, using that processing option to run the application in subsystem mode.

You must manually start subsystems to minimize the consumption of system resources. When started, JD Edwards EnterpriseOne subsystems run continuously, looking for and processing requests from JD Edwards EnterpriseOne applications. Subsystems run until you terminate them.

Typically, you use subsystem jobs running on the enterprise server to off load processor resources from the workstation. Instead of queuing requests and running them in batches at specified times of the day, you can direct the requests to a subsystem, where they are processed in realtime. For example, you might be running the Sales Order Entry application on a workstation and want to print pick slips. If you are using a version of pick slips that has the Subsystem Job function enabled, the request is executed by a subsystem job. The pick slip request is routed to and processed by the subsystem job on the defined enterprise server. As a result, no additional processing resources are required from the workstation machine to actually print the pick slip.

When an application issues a request for a job to run in a subsystem, it places a record in the Subsystem Job Master table (F986113). These records are identified by subsystem job name and contain status and operational indicators. Embedded in the record is key information that allows the subsystem to process the record without additional interaction with the requesting application. The continuously running subsystem monitors the records in this table. If the subsystem finds a record with its process ID and appropriate status indicators, it processes the record and updates the status accordingly.

This illustration displays the logical sequence of events associated with subsystems:

Figure 4-1 Logical sequence of events associated with subsystems

4.4.1.2 Enabling Subsystems

To prevent excessive processing overhead during server startup and to prevent unnecessary uses of processor resources for subsystem jobs that might be in use, you must manually start subsystems. Generally, the system administrator or manager-level user is responsible for this task. To manually start subsystems, a version of a JD Edwards EnterpriseOne batch process with a processing option set to enable the use of subsystems is run.

As described, the way that you initially control the creation and start-up of these subsystems and queues depends on the server platform.

Platform (Subsystem or Queue)

Description

IBM i (JDENET)

One IBM i subsystem is used for JD Edwards EnterpriseOne. This subsystem is started automatically when you issue the JD Edwards EnterpriseOne startup command STRNET. The subsystem name is version-specific. For example, for release 9.0, the subsystem name is psft900.
To process requests that are destined for JD Edwards EnterpriseOne subsystems, you must define a specific job queue running under the JDENET subsystem. For example, a job queue might be named QBATCH.

User requests for JD Edwards EnterpriseOne subsystem-defined batch jobs are executed by the job queue that is based on definition in the IBM i user profile.

UNIX (jdequeue)

One or more queues can exist for JD Edwards EnterpriseOne. These queues can be named the same or differently. You define queues by parameters in the startup shell scrip RunOneWorld.sh.
To process requests that are destined for subsystems, you must define one or more queues. For example, a jdequeue might be named QBATCH.

User requests for subsystem-defined batch jobs are executed by the job queue, based on the process ID.

NT (jde.ini settings)

One or more queues can exist for JD Edwards EnterpriseOne. These queues must have the same name. You define queues using settings in the jde.ini file.
To process requests that are destined for subsystems, you must define the name and number of queues in the [NETWORK QUEUE SETTINGS] section of the jde.ini file. For example, a jdequeue might be named QBATCH.

User requests for subsystem-defined batch jobs are executed by the job queue, based on the process ID.

System administrators can display all of the subsystems that are running on a server by using the Subsystem Jobs application (P986113). Use this application to:

- Locate a list of subsystems that are running on a server.

- Locate a list of subsystem records that are unprocessed (not available for IBM i servers).

- Locate the current record that a subsystem is processing (not available for IBM i servers).

- Stop or delete any subsystem.

4.4.1.3 Subsystem Job Records

Multiple JD Edwards EnterpriseOne processes write records to the Subsystem Job Master table (F986113). Each record has a status code that identifies subsystem request types and operational status. You can use Work With Server Jobs to view the records in this table.

4.4.1.4 Terminating Subsystems

You can use Work With Server Jobs to terminate subsystems. The following two methods of termination are available:

- Stopping a subsystem job causes it to terminate after it completes processing the current record. Additional unprocessed records in the Subsystem Job Master table (F986113) will not be processed, and no new records can be written. Essentially, the unprocessed records will be lost; that is, the process that initiated the record is not notified that the record was not processed.

- Ending a subsystem job causes it to terminate after processing all of the existing subsystem records. No new records can be written to the Subsystem Job Master table (F986113).

4.4.2 Forms Used to Manage JD Edwards EnterpriseOne Subsystems

Form Name

FormID

Navigation

Usage

Work With Servers

W986116A

System Administration Tools (GH9011), Data Source Management, Work With Servers (P986116).

Select a server in which you want to locate a subsystem.

Work With Subsystems

W986113A

On the Work With Servers form, from the Row menu, select Subsystem jobs.

Review the status and type of the subsystem. Stop or end a subsystem.

View Jobs

NA

On the Work With Subsystems form, from the Row menu, select View Jobs.

Review server jobs and job types.

4.4.3 Locating Subsystems Running on a Server

Access the Work With Servers form.

1. On the Work With Servers form, select a server from the list or use the query by example row to select a specific server.

2. From the Row menu, select Subsystem Jobs.

3. On the Work With Subsystems form, select one of these options:

- &Processes
A process is a subsystem that is waiting for work. It is identified by an S (subsystem job) value in the Job Type field.

- &Waiting Jobs
Waiting jobs are report jobs that are queued for a subsystem. They are identified by an R (subsystem record) value in the Job Type field.

All currently running subsystems are displayed. Report number and version identify the running subsystems.

4. Review these fields in the detail area to note the type and status of the subsystem:

Field

Description

Job Type

Indicates the subsystem type. Values are:

- R
Subsystem record.

- S
Subsystem job.

Job Status

Indicates the status of the subsystem job or record. Values are:

- W
Subsystem record waiting.

- P
Subsystem record processing.

- E
Subsystem record to end the job.

- R
Subsystem job running.

4.4.4 Reviewing Job Records for Subsystems

Access the Work With Subsystems form.

1. After locating a subsystem job, on the Work With Subsystems form, click Find.

2. Select a record in the detail area, and then select View Jobs from the Row menu.

3. On the View Jobs form, click Find.
A list is displayed for all server jobs in the Subsystem Job Master (F986113) with an R (subsystem job running) job type.

4.4.5 Terminating Subsystems

Access the Work With Subsystems form.

1. Select the running subsystem that you want to stop.

2. To stop a subsystem, from the Row menu, select Stop Subsystem.

Note:
If you are viewing Waiting Jobs from Work With Server Jobs or if you are viewing subsystem jobs by selecting the View Jobs from Work With Server Jobs, the Stop Subsystem selection is disabled from the Row menu selection.

3. To end a subsystem, from the Row menu, select End Subsystem Job.

Note:
If you are viewing Waiting Jobs from Work With Subsystems, the End Subsystem selection is disabled from the Row menu selection.

4. On End Subsystem Job, click OK.

5 Setting Up PIM Synchronization for JD Edwards EnterpriseOne CRM Users

This chapter contains the following topics:

- Section 5.1, "Understanding PIM Synchronization"

- Section 5.2, "Setting the Processing Option for the PIM Server"

- Section 5.3, "Setting Up Users for PIM Synchronization"

- Section 5.4, "Exporting PIM User Records"

- Section 5.5, "Importing PIM Synchronization Files into Intellisync Server"

5.1 Understanding PIM Synchronization

Oracle's JD Edwards EnterpriseOne provides the ability to synchronize user data between third-party PIM systems and JD Edwards EnterpriseOne CRM users. With this synchronization, CRM users can share and manage personal information such as contacts, appointments, and tasks stored in IBM Domino or Microsoft Exchange PIM systems. For example, as appointments are created in the CRM system, corresponding objects are created in the PIM system database. If users update or delete items in either the CRM or PIM system, the changes are synchronized in both locations.

JD Edwards EnterpriseOne relies on a third-party software product, Intellisync Server, to enable data synchronization between JD Edwards EnterpriseOne CRM and PIM systems. Intellisync Server uses these items to synchronize PIM data:

- CSV file.
The CSV file contains the PIM server records for each JD Edwards EnterpriseOne user that you set up for PIM synchronization. You generate this file from JD Edwards EnterpriseOne after you set up users for PIM synchronization.

- Synchronizing template.
This template determines the types of information that are synchronized between the JD Edwards EnterpriseOne and PIM systems.

The process for setting up PIM synchronization is:

1. Enter each JD Edwards EnterpriseOne user's PIM system information into JD Edwards EnterpriseOne.

2. Export this information from JD Edwards EnterpriseOne into a CSV file.

3. Using Intellisync Server Bulk User Import, import the CSV file, along with a synchronizing template, into the Intellisync Server.

Note:
JD Edwards EnterpriseOne provides a standard synchronizing template for PIM synchronization.

5.1.1 User Defined Codes for PIM

JD Edwards EnterpriseOne uses these user defined codes (UDCs) to categorize the data shared with PIM systems:

UDC Type

UDC Codes and Definitions

01|PH (Phone Type)

HOM: PIM-Home
<blank>: PIM-Business

FAX: PIM-Fax

CAR: PIM-Car

01|RT (Relation Type)

A: PIM-Assistant
S: PIM-Spouse

C: PIM-Child

01|AT (Address Type)

H: PIM-Home
W: PIM-Work

01|ET (Electronic Address Type)

E: PIM-Email Address
I: PIM-Web Address

01|SG (PIM Sync Category)

PIMSG: PeopleSoft
This UDC is used with MS Exchange only.

ACTTY: APPOINTMT

TASK: TODOTASK

CALTY: PERSONAL

Note: The ACTTY, TASK, and CALTY codes apply only to JD Edwards EnterpriseOne 8.12 and later releases.

Note:
You should not change the Description Line 2 values of PIM UDCs.

5.1.1.1 Understanding the 01|SG UDCs

The 01|SG UDCs were created solely for PIM synchronization and are hard-coded, which means that you can only change the Description Line 1 values of these UDCs. The PIM server uses the default value in the Description Line 1 of the 01|SG UDCs to categorize events, tasks, and contacts in JD Edwards EnterpriseOne.

This table describes how the PIM server uses the UDCs in 01|SG to categorize PIM data:

01|SG UDC

Description

PIMSG

The PIM server uses the Description Line 1 value of PIMSG to categorize the data that is synchronized between JD Edwards EnterpriseOne and Microsoft Exchange or Domino. The default value of Description Line 1 is "PeopleSoft." You can modify this value.
In Microsoft Outlook, appointments, tasks, and contacts have a Categories field. When PIM users create appointments, tasks, or contacts in Microsoft Outlook, they must enter a value in the Categories field that is the same as the value in Description Line 1 of PIMSG. The PIM server uses this value to categorize PIM data in JD Edwards EnterpriseOne.

In JD Edwards EnterpriseOne, there is no equivalent Categories field for appointments, tasks, and contacts. However, when PIM users create these items in JD Edwards EnterpriseOne, the PIM server associates the value in Description Line 1 of PIMSG with these items. When users open these appointments, tasks, and contacts in Microsoft Outlook, the Categories field is populated with the value from the Description Line 1.

CALTY

The Description Line 1 value in the CALTY UDC specifies the JD Edwards EnterpriseOne calendar type that is being used by PIM users. JD Edwards EnterpriseOne contains different types of calendars, such as PERSONAL and CRM. When importing information from the PIM server, JD Edwards EnterpriseOne uses the value that you enter in the Description Line 1 of the CALTY UDC to determine which calendar the information belongs. The default value for Description Line 1 is PERSONAL.

ACTTY

JD Edwards EnterpriseOne contains several event types, such as MEETING, CALL, DOWNTIME, and APPOITMNT. The 01|AC UDC type contains a code for each event type. The PIM server uses the value in the Line Description 1 of ACTTY to categorize events sent from the PIM system to JD Edwards EnterpriseOne. The default value is APPOITMNT.

TASK

JD Edwards EnterpriseOne contains several task types, such as TODOTASK, RESEARCH, and FOLLOWUP. UDCs for these tasks are defined in the 01|AC UDC type along with the event types. The PIM server uses the value in the Line Description 1 of the TASK UDC to categorize tasks sent from the PIM system to JD Edwards EnterpriseOne. The default value for Description Line 1 is TODOTASK.

5.1.2 Data Mapped Through PIM Synchronization

The tables in this section contain the appointment, contact, and task data that is mapped between JD Edwards EnterpriseOne and IBM Domino or Microsoft Exchange.

5.1.2.1 Appointments

This table shows the appointment data in the JD Edwards EnterpriseOne F01301 table that is mapped between systems:

JD Edwards EnterpriseOne DD Item

JD Edwards EnterpriseOne Field

IBM Domino Field

Microsoft Exchange Field

TDSTR

Start Date

Begin Date

Start Date

TDSTR

Start Time

Begin Time

Start Time

TDEND

End Date

End Date

End Date

TDEND

End Time

End Time

End Time

ALRM

Alarm Flag

Alarm Flag

Reminder Set Flag

LEADTIME +
LEADTMEU

Alarm Date

Alarm Date

Alarm Date

LEADTIME +
LEADTMEU

Alarm Time

Alarm Time

Alarm Time

ACTVDESC

Description

Description

Body

LOCATION

Location

Location

Location

ACTPRV

Private Flag

Mark Private

Private

SUBJECT

Subject

Subject

Subject

STPIM

Category

Category

Categories

N/A

Attendees

Alarm Message

Meeting Attendees

N/A

Link

Room

Link

N/A

Show time as

N/A

N/A

N/A

Custom Field1

N/A

N/A

N/A

Custom Field2

N/A

N/A

N/A

Custom Field3

N/A

N/A

N/A

Custom Field4

N/A

N/A

N/A

Custom Field5

N/A

N/A

N/A

Custom Field6

N/A

N/A

N/A

Custom Field7

N/A

N/A

N/A

Custom Field8

N/A

N/A

N/A

Custom Field9

N/A

N/A

N/A

Custom Field10

N/A

N/A

N/A

Custom Field11

N/A

N/A

N/A

Custom Field12

N/A

N/A

5.1.2.2 Contacts

This table shows the contact data in various JD Edwards EnterpriseOne tables that is mapped between systems:

JD Edwards EnterpriseOne Table

JD Edwards EnterpriseOne DD Item

JD Edwards EnterpriseOne Field

IBM Domino Field

Microsoft Exchange Field

F0111

GNNM

First Name

First Name

First Name

F0111

SRNM

Last Name

Last Name

Last Name

F0111

MDNM

Middle Name

Middle Name

Middle Name

F0111

ATTL

Job Title

Job Title

Job Title

F0101

ALPH

Company Name

Company

Company Name

F0115

AR1, PH1

Office Phone

Office Phone

Business Telephone Number

F0115

AR1, PH1

Home Phone

Home Phone

Home Telephone Number

F0115

AR1, PH1

Mobile Phone

Cell Phone

Mobile Telephone Number

F0115

AR1, PH1

Fax

Office Fax

Business Fax Number

F0115

AR1, PH1

Home Fax

Home Fax

Home Fax Number

F0115

AR1, PH1

Pager

Pager

Pager Number

F01151

EMAL

Email

eMail address

Email1 Address

F0116

ADD1

Office Street

Business Street

Business Address Street

F0116

CTY1

Office City

Business City

Business Address City

F0116

ADDS

Office State/Province

Business State

Business Address State

F0116

CTR

Office Country

Business Country

Business Address Country

F0116

ADDZ

Office Zip

Business Zip

Business Address Postal Code

F01161

ADD1

Home Street

Home Street

Home Address Street

F01161

CTY1

Home City

Home City

Home Address City

F01161

ADDS

Home State/Province

Home State

Home Address State

F01161

CTR

Home Country

Home Country

Home Address Country

F01161

ADDZ

Home Zip

Home Zip

Home Address Postal Code

F0111

REM1

Notes

Comment

Body

F0112

DDATE, DMON, DYR

Birthdate

Birthday

Birthday

F01151

EMAL

Business Web

Web page

Web page

F01112

RALP

Assistant Name

Assistant

Assistant Name

F01112

RCK7

Suffix

Suffix

Suffix

F01151

EMAL

Email2

Nick Name

Email2 Address

F01161

ADD1

Office Street Line 1

Location

Business Address Street 1

F01161

ADD2

Office Street Line 2

Manager

Business Address Street 2

F01161

ADD1

Home Street Line 1

Spouse

Home Address

F01161

ADD2

Home Street Line 2

Children

Home Address PO Box

F0115

AR1, PH1

Other Phone

N/A

Other Telephone Number

F0115

AR1, PH1

Business Phone 2

N/A

Business Telephone Number 2

F0115

AR1, PH1

Assistant Phone

N/A

Assistant Telephone Number

F01151

EMAL

Link

N/A

Link

5.1.2.3 Tasks

This table shows the task data in the JD Edwards EnterpriseOne F01301 table that is mapped between systems:

JD Edwards EnterpriseOne DD Item

JD Edwards EnterpriseOne Field

IBM Domino Field

Microsoft Exchange Field

SUBJECT

Description

Subject

Subject

ACTVDESC

Notes

Description

Body

TDSTR

Start Date

Start Date

Start Date

ACTCMPL

Completed Flag

Completed?

Completion Flag

TDEND

Due Date

Due Date

Due Date

ALRM

Alarm Flag

Alarm Flag

Reminder Flag

LEADTIME
+

LEADTMEU

Alarm Date

Alarm Date

Reminder Date

LEADTIME
+

LEADTMEU

Alarm Time

Alarm Time

Reminder Time

COMITLVL

Priority

Priority

Priority

ACTPRV

Private Flag

Mark Private

Private Flag

STPIM

Category

Category

Categories

TDSTR

Alarm Message

Start Time

Companies

TDCMPL

Completed Date

N/A

Date Completed

TDCMPL

Completed Time

N/A

Billing Information

TDEND

Due Time

N/A

Mileage

N/A

Status

N/A

Status

N/A

Link

N/A

Link

N/A

Owner

N/A

Owner

N/A

Percent Complete

N/A

Percent Complete

N/A

Custom Field1

N/A

Actual Work

N/A

Custom Field2

N/A

Total Work

N/A

Custom Field3

N/A

Do not AutoArchive

5.1.3 Prerequisite

Install the PIM Sync Servlet.

See the Server Manager Guide on My Oracle Support.

5.2 Setting the Processing Option for the PIM Server

If all users use the same type of PIM system (Microsoft Exchange or IBM Domino), you can set a processing option to specify the type of PIM server to set up synchronization with.

Note:
Do not set this processing option if both PIM servers are used.

From the System Administration Tools menu (GH9011), select User Management. Right-click User Profiles, select Prompt for, and then select Values.

On the Processing Options form, select the PIM Server Setup tab and then enter the appropriate value for the PIM server:

- Enter D for IBM Domino Server.

- Enter X for Microsoft Exchange Server.

5.3 Setting Up Users for PIM Synchronization

Access the E1 - PIM User Information Setup form.From the System Administration Tools menu (GH9011), select User Management, User Profiles. On the Work with Users/Roles form, select a user record and then select PIM User Setup from the Row menu.

Figure 5-1 E1 - PIM User Information Setup form

1. Select the user's PIM server type:

- IBM Domino Server

- Microsoft Exchange Server

Note:
If you specified the PIM server type in the PIM Server Setup processing option, you cannot select this option here.

2. For IBM Domino Server, complete these fields:

Field

Description

Mail File Location

Enter the user's Lotus Notes mail database file. Specify the full name relative to the Domino Data Directory, without the .nsf extension, for example mail\UserMailDatabase.

Address Book Name

Enter the user's Lotus Notes address book database name. Specify the full name relative to the Domino Data Directory, without the .nsf extension, for example contacts\UserAddressBook.

Address Book Server

Enter the user's Lotus Notes address book database server.

3. In the Template field, click the search button to specify the Intellisync Server synchronizing template:

1. On E1 – PIM Template Revisions, complete these fields:
Template

Enter a name for the template. You can name the template based on the role or function of the JD Edwards EnterpriseOne users that you associate this template to, for example you can name the template CRMHR template for human resources users or DEFAULT as the name of the default template for all users.

Template File

Enter a fully qualified pathname to the synchronizing template file. This must be a pathname that Intellisync can recognize.

2. After you create the template, double-click the template to select it and then click OK.

4. For Microsoft Exchange Server, complete these fields:

- Primary Windows NT Account
Enter the user's Windows NT account user name and domain name. The Intellisync server user name must be unique, for example Domain\SampleUser1.

- Alias
Because an Intellisync account can only reference one mailbox, you must enter an alias to specify which mailbox to use.

- Template
See step 3 for instructions on how to specify the template.

5.4 Exporting PIM User Records

After you set up users for PIM synchronization, you must export each user record to a CSV file. The CSV file contains each user's PIM system information. Subsequently, you must import this file into the Intellisync Server to complete the synchronization setup.

This section discusses how to:

- Export all user records.

- Export a selected list of PIM user records.

5.4.1 Exporting All User records

Access the Work With User/Role Profiles form. From the System Administration Tools menu (GH9011), select User Management, User Profiles (P0092).

1. On the Work With User/Role Profiles form, click Find.

2. From the Form menu, select PIM Export All Users.

3. On the Report Output Destination form, make sure that the Export to CSV option is selected and click OK.

5.4.2 Exporting a Selected List of PIM User Records

Access the Work With User/Role Profiles form. From the System Administration Tools menu (GH9011), select User Management, User Profiles (P0092).

1. On the Work With User/Role Profiles form, click Find and then select the user records that have been set up for PIM synchronization.
To determine which users have been set up for PIM synchronization, scroll to the PIM Server column. Records that have a value in this column have been set up for PIM synchronization.

2. From the Row menu, select PIM Export User(s).

3. On the Report Output Destination form, make sure that the Export to CSV option is selected and click OK.
The system generates and displays a CSV file. Use this file to import PIM synchronization records into Intellisync Server.

5.5 Importing PIM Synchronization Files into Intellisync Server

To complete the PIM data synchronization with JD Edwards EnterpriseOne, use the Intellisync Server Bulk User Import tool to import these items into Intellisync Server:

- CSV file

- Synchronizing template

Note:
The synchronizing template must match the template that you associated with JD Edwards EnterpriseOne users when you set up users for PIM synchronization.

See JD Edwards EnterpriseOne Tools 8.98 PIM Sync Server Reference Guide on My Oracle Support for information on how to import these files.

6 Enabling Mobile Client Functionality

This chapter contains the following topics:

- Section 6.1, "Understanding Distributed Next Numbers for Mobile Clients"

- Section 6.2, "Setting Up Distributed Next Numbers for Mobile Clients"

6.1 Understanding Distributed Next Numbers for Mobile Clients

Any of JD Edwards EnterpriseOne mobile applications that assign unique numbers using the number facilities (namely the X0010 and X00022 business functions) must have their parameters registered as distributed next numbers. These parameter sets are identified during application development. For applications that call X0010, these parameters include a system code, next numbering index, company, document type, century, and fiscal year. For applications that call X00022, the parameter is an object name.

6.2 Setting Up Distributed Next Numbers for Mobile Clients

This section discusses how to:

- Activate mobile client functionality.

- Define the starting next number.

- Enable distributed next numbers.

- Set up distributed next numbers by system code.

- Map the JD Edwards EnterpriseOne user ID to the Distributed Next Numbers application (P950411).

- Set up distributed next numbers by application.

- Schedule updates to distributed next numbers applications.

See Also:

- Setting Up System Next Numbers in the JD Edwards EnterpriseOne Address Book 9.0 Guide.

6.2.1 Activating Mobile Client Functionality

Access the Work with EnterpriseOne System Control form. On the JD Edwards EnterpriseOne enterprise server, access the P99410 application.

1. On the Work with EnterpriseOne System Control form, click Add.

2. On the EnterpriseOne System Control Revisions form, enter each of the following system codes, one at a time, in the Data Item field:

- SY90CA

- CRMMSL

- SY49

The F99410 table must contain records for these system codes before you can enable mobile client functionality.

3. Click Yes.

4. Click OK.

5. Repeat these steps to add each system code.

6.2.2 Defining the Starting Next Number

On the JD Edwards EnterpriseOne enterprise server, access the Next Number Revisions application (P0002) through the JD Edwards EnterpriseOne web client.

1. On the Work with Next Numbers form, click Add.

2. Enter 42E in the System field.

3. In the Use field, enter a description of the next number parameter.

4. In the Next Number field, enter the starting next number, for example 1.

5. Select the Check Digit Used option if you want JD Edwards EnterpriseOne to append a random digit to the next number for uniqueness, and then click OK.

6.2.3 Enabling Distributed Next Numbers

On the JD Edwards EnterpriseOne enterprise server, access the P00098 application through the JD Edwards EnterpriseOne web client.

1. On the Work With Enable Distributed Next Numbers form, click Add.

2. Create separate rows for each of these product codes:

Product Code

Order Type Next Number

Enabled

42E

1

Y

47

2

Y

32

2

Y

01

1

Y

3. Create additional rows for the following tables:

Object Name

Enabled

F0111 (Address Book - Who's Who)

Y

F01112 (Related Person)

Y

F0115 (Address Book - Phone Numbers)

Y

F01151 (Electronic Address)

Y

F0450 (Payee Control)

Y

F42140 (Customer Master Commission Information)

Y

F42150Z1 (Header Commission Unedited Transaction File)

Y

F42160Z1 (Detail Commission Unedited Transaction File)

Y

F90CA06A (Competitor_KillSheet Table)

Y

F90CB010 (Lead Table)

Y

F90CB020 (Opportunity Table)

Y

F90CB02E (Opportunity - Employee Table)

Y

F90CB02J (Opportunity - Sales Cycle Table)

Y

F90CB030 (CRM Address Table)

Y

F90CB043 (Qualification Object Table)

Y

F90CB05A (Sales Cycle Table)

Y

F90CB05C (Sales Cycle Notification Ledger Table)

Y

F90CB060 (Forecast Table)

Y

4. Click OK.

6.2.4 Setting Up Distributed Next Numbers by System

On the JD Edwards EnterpriseOne enterprise server, access the P00023A application through the JD Edwards EnterpriseOne web client.

1. On the Work with Distributed Next Numbers by System Code form, select ZJDE0001.

2. Click Add.

3. On the Distributed Next Number form, for each JD Edwards EnterpriseOne mobile user, create the following additional rows for the different system codes, and then click OK:

Third-Party User ID

System Code

OrderType Next Number

Allotment

Enter the JD Edwards EnterpriseOne user ID of a mobile client

42E

1

500

47

2

500

N/A

32

2

500

N/A

01

1

Assign a large enough allotment of next numbers so that users can enter enough new records before synchronizing with JD Edwards EnterpriseOne.
Note: The mobile client is not allowed to add more records than specified by this allotment. When the mobile client synchronizes with the server, the user is granted a new allotment of next numbers.

N/A

6.2.5 Mapping the JD Edwards EnterpriseOne User ID to the Distributed Next Numbers Application (P950411)

On the JD Edwards EnterpriseOne enterprise server, access the P950411 application.

1. On the Work with Third Party User ID Map form, for each mobile user, click Add.

2. On the Third Party UserID Map Detail form, accept the default value (Synchronization Application) in the UserID Type field

3. In the User ID field, enter the user ID of the mobile client.

4. In the Environment Name field, enter the JD Edwards EnterpriseOne environment that you are currently signed on to.

5. Accept the default value in the Third-Party User ID field, and then click OK.

6.2.6 Setting Up Distributed Next Numbers by Application

On the JD Edwards EnterpriseOne enterprise server, access the P00023A application through the JD Edwards EnterpriseOne web client.

Note:
You must make sure that you perform the steps in this task in the order that they appear. Particularly, you must enter the server user ID before you enter the JD Edwards EnterpriseOne user IDs.

1. On the Work with Distributed Next Numbers by Object Name form, select ZJDE0002 and click Add.

2. Enter the following information into separate rows:

Third-Party User ID

JD Edwards EnterpriseOne Table

Allotment

SERVER

F0111 (Who's Who)

6250

SERVER

F01112 (Related Person)

2500

SERVER

F0115 (Phone Numbers)

1250

SERVER

F01151 (Electronic Address)

1250

Note:
The SERVER value must be entered in upper case.

3. Click OK.

4. Select ZJDE0002 and click Add.

5. For each JD Edwards EnterpriseOne mobile user, create rows for each of these JD Edwards EnterpriseOne tables:

Third-Party User ID

JD Edwards EnterpriseOne Table

Allotment

Enter the JD Edwards EnterpriseOne user ID of a mobile client.

F0111

Assign a large enough allotment of next numbers so that users can enter enough new records before synchronizing with JD Edwards EnterpriseOne.
Note: The mobile client is not allowed to add more records than specified by this allotment. When the mobile client synchronizes with the server, the user is granted a new allotment of next numbers.

F01112

N/A

N/A

F0115

N/A

N/A

F01151

N/A

N/A

F0450

N/A

N/A

F42140

N/A

N/A

F42150Z1

N/A

N/A

F42160Z1

N/A

N/A

F90CA06A

N/A

N/A

F90CB010

N/A

N/A

F90CB020

N/A

N/A

F90CB02E

N/A

N/A

F90CB02J

N/A

N/A

F90CB030

N/A

N/A

F90CB043

N/A

N/A

F90CB05A

N/A

N/A

F90CB05C

N/A

N/A

F90CB060

N/A

N/A

6. Click OK.

6.2.7 Scheduling Updates to Distributed Next Numbers Applications

You should schedule the Distributed Next Number Update UBE (R0002D1) to run at a regular interval. This UBE is typically set up to run nightly.

7 Setting Up Viewable and Configurable Portlets

This chapter contains the following topics:

- Section 7.1, "Understanding Viewable and Configurable Portlet Types"

- Section 7.2, "Initializing Viewable and Configurable Portlets"

Note:
The SRM, HTML, URI, and IURI portlets that are discussed in this chapter are available in the JD Edwards Collaborative Portal and Oracle Portal.

7.1 Understanding Viewable and Configurable Portlet Types

In JD Edwards Collaborative Portal and Oracle Portal, you can set up viewable and configurable portlets for these types of portlets:

- Isolated URI (IURI)
This type of portlet is the most flexible because it is not actually integrated into the Portal. IURI portlets allow you full access to the browser frame and to take existing web content and display it in the Portal.

- URI
This type of portlet always requires interaction between the Portal and a web server. URI portlets can be written as CGI, Java servlets, or HTML pages, and they can reside on a server other than the Portal server. URI portlets tend to be slower than the other portlets.

- HTML
This type of portlet requires no interaction with an external server, so it provides quick response with very little external resource load. HTML portlets can contain references to applets, ActiveX controls, and images, but the HTML is taken directly from JD Edwards EnterpriseOne database, so the content is static. You can take advantage of pass-through functions, such as RunOWApp and addRunOWAppFI with HTML portlets as well. These functions enable you to launch JD Edwards EnterpriseOne applications.

- Supplier Relationship Management (SRM)
This portlet provides a fully configurable shell portlet that you can modify without Java programming. You can select the queries to display in the portlet at runtime using a wizard interface.

Viewable portlets can be initialized only to an existing portlet type, but may be initialized by anyone. After initializing a viewable portlet, users cannot modify its definition.

Configurable portlets enable you to initialize a portlet to an existing portlet type or create a new portlet definition. In addition, when you initialize a configurable portlet, you define permissions to determine the type of access users have to the configurable portlet. You can grant either View or View,Config access. View permissions allow users to use a configurable portlet, but prevents them from modifying the definition of the portlet. View,Config permissions allow users to modify the definition and the permissions of a portlet. A user who has View,Config permissions basically has the same permissions of a system administrator. Therefore, you should carefully consider the users to which you grant View,Config permissions.

If a user only has view access to a configurable SRM portlet, the user may still edit the portlet if it contains alert parameters that can be personalized. In this case, the SRM portlet displays an Edit icon that users can select to modify the alert parameters.

7.2 Initializing Viewable and Configurable Portlets

This section discusses how to:

- Initialize viewable HTML, URI, IURI portlets.

- Initialize configurable HTML, URI, IURI portlets.

- Initialize a viewable SRM Portlet.

- Initialize a configurable SRM portlet.

7.2.1 Prerequisites

If you are using the JD Edwards Collaborative Portal, make sure that the WebClient_Portal.war file that contains these portlets has been deployed on the IBM WebSphere Portal.

If you are using the Oracle Portal, make sure that the webclient_Oracle_Portal.war file has been deployed as a portal provider and that the provider has been registered with the Oracle Portal.

7.2.2 Initializing Viewable HTML, URI, IURI Portlets

You can initialize viewable HTML, URI, IURI portlets only to an existing portlet type.

Access the portal page that contains the viewable HTML_URI_IURI Component portlet.

1. In the portlet, click the Configure icon.

2. Under Configure Portlet Choice, select an existing portlet from the drop-down list box and then click the Done button.
The initialized portlet appears on the Portal page.

7.2.3 Initializing Configurable HTML, URI, IURI Portlets

Access the portal page that contains the Configurable_HTML_URI_IURI_Component portlet.

1. In the portlet, click the Configure icon.

2. If you want to use an existing portlet definition, perform these steps:

1. Select the Select an existing portlet option.

2. Select an existing portlet from the drop-down list box, and then click the Done button.

3. To create a new portlet definition, select the Create a new portlet of portlet type option, and then select HTML, URI, or IURI from the drop-down list box.

4. Click the Next button and then complete the fields according to the type of portlet selected:

Portlet Type

Fields

Description

HTML

Name

Enter a unique ID for the portlet. The maximum field length is 10 characters. This ID must be unique across the system.

N/A

Title

Enter a name for the portlet. This is the name that appears when the system provides a list of portlets for a user to select from. The maximum field length is 30 characters.

N/A

HTML Code

Enter or edit existing HTML for this component.

URI

Name

Enter a unique ID for the portlet. The maximum field length is 10 characters. This ID must be unique across the system.

N/A

Title

Enter a name for the portlet. This is the name that appears when the system provides a list of portlets for a user to select from. The maximum field length is 30 characters.

N/A

Support Cookies

Indicates whether the component can support cookies.

N/A

Component URL

Enter a URL to existing web content. Select one of the following protocols from the drop-down list box and then enter the remaining path for the URL:

- http://

- https://

Select none if the URL is relative to the context of the portlet.

IURI

Name

Enter a unique ID for the portlet. The maximum field length is 10 characters. This ID must be unique across the system.

N/A

Title

Enter a name for the portlet. This is the name that appears when the system provides a list of portlets for a user to select from. The maximum field length is 30 characters.

N/A

Width

Select the percent or pixels option, and then enter the appropriate value to determine the width of the component IFRAME.

N/A

Height

Indicates the height in pixels of the component IFRAME.

N/A

Scrolling

Select Yes to always display scrollbars in the IFRAME. Select No to never display scrollbars. Select Auto to allow the IFRAME to display scrollbars if they are needed.

N/A

Component URL

Enter a URL to existing web content. Select one of the following protocols from the drop-down list box and then enter the remaining path for the URL:

- http://

- https://

Select none if the URL is relative to the context of the portlet.

5. Click the Next button.

6. In the Add Permissions region, select the type of permission that you want to assign from the Permissions drop-down list box.

- View
Select this option to grant only view access to the portlet.

- View,Config
Select this option to grant users the capability to re-configure the portlet definition and permissions.

7. In the Who group box, select the option according to the users to which you want to assign permissions and complete the fields accordingly:

- User

- Role

- *PUBLIC

8. Select the Update button to add the permissions record.
The record appears in the Edit/Remove Permissions region.

9. In the Edit/Remove Permissions region, you can modify or remove permissions.

10. Select the Done button to complete the portlet initialization.

7.2.4 Initializing a Viewable SRM Portlet

You can initialize viewable SRM portlets only to an existing portlet.

Access the portal page that contains the viewable SRMComponent portlet.

1. In the portlet, click the Configure icon.

2. Under Supplier Relationship Management Portlet Choice, select an existing portlet from the drop-down list box.
The initialized portlet appears on the portal page.

An initialized viewable SRM portlet may contain an edit icon if the portlet contains an alert that a user can personalize.

7.2.5 Initializing a Configurable SRM Portlet

Access the Portal page that contains the Configurable_ SRMComponent portlet.

1. In the Configurable_SRMComponent portlet, click the Configure icon.

2. If you want to use an existing portlet definition, perform these steps:

1. Select the Select an existing portlet option.

2. Select a portlet from the drop-down list box, and then click the Done button.

3. To create a new SRM portlet definition, select the Create a new portlet option, and then click the Next button.

4. For a new portlet definition, perform the necessary steps to select and configure the SRM alerts.
See "Configuring the SRM Portlet Using the Configuration Wizard" in the JD Edwards EnterpriseOne Supplier Relationship Management Collaboration 9.0 Implementation Guide.

After you select the SRM alerts and configure the alert parameters, the portal displays the page that you use to define permissions for the portlet.

5. In the Add Permissions region, select the type of permission that you want to assign from the Permissions drop-down list box.

- View
Select this option to only allow users to view the portlet.

- View, Config
Select this option to grant users the capability to re-configure the portlet definition and permissions.

6. In the Who group box, select the option according to the users to which you want to assign permissions and complete the fields accordingly:

- User

- Role

- *PUBLIC

7. Click the Update button to add permissions.
The record appears in the Edit/Remove Permissions region.

8. In the Edit/Remove Permissions region, you can modify permissions or remove permissions.

9. Click the Done button to complete the portlet initialization.

8 Dropping Indexes from a Table

This chapter contains the following topics:

- Section 8.1, "Understanding the Index Selection Tool"

- Section 8.2, "Using the Index Selection Tool"

8.1 Understanding the Index Selection Tool

Database administrators drop indexes from tables in a physical database to increase system performance. Instead of using the actual database application to drop table indexes, you can use the Index Selection Tool (P95150). The advantage of using P95150 to drop indexes is that Oracle's JD Edwards EnterpriseOne keeps track of the indexes that are dropped, even if the indexes have been restored or rebuilt. For example, during a software update, the system restores indexes to tables that are affected by the update. Typically, after an update, you would have to perform another analysis to determine the indexes that need to be re-dropped. However, JD Edwards EnterpriseOne retains this information so that you can easily find the indexes that were previously dropped, reducing the time it takes to drop the indexes again.

Note:
P95150 should only be used by system administrators or database administrators. Use Security Workbench (P00950) to apply the proper security to this application.

See "Using Security Workbench" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

8.1.1 Flagging indexes

The P95150 program enables you to locate and display the table indexes in a tree structure. You expand the tree to view and flag the indexes that you wish to drop. You can flag a single index or multiple indexes at a time. The P95150 program only allows you to drop indexes that are not unique or primary to the table since dropping these types of indexes would disrupt the integrity of the table.

When you open a table in P95150, the program displays the table and all of its columns in a tree. Each item, or node, in the tree has an icon next to it. The Tree Node Key tab contains a description of each of these icons, which include:

- Table

- Data Source Override

- Primary Index

- Unique Index

- Unflagged Index
The Unflagged Index is the only type of index that you can flag or drop. The system does not permit you to drop a primary or unique index.

- Index Flagged for Drop

- Column in Index

8.1.2 Determining the Data Source

A table can reside in multiple data sources, so you must determine the data source from which you want the table index to be dropped. When you initially open a table in P95150, by default, the system displays a table in a Default node. A table in the Default node is not associated with a data source. If you flag and then try to drop an index from this node, the program prompts you to specify a data source. If you specify a data source before flagging and dropping an index, the program displays another node besides the Default node. This node is named after the data source that you selected and contains the same tree as the Default node. When you drop an index from the data source node, the index is automatically dropped.

8.1.3 Index Selection Logs

The P95150 program contains an option that enables you to view the history of actions that have been performed using the tool. You can view the following information in the index selection logs:

- Table name

- Data Source

- Index ID

- Log Description

- User

- Machine

- Date Updated

- Time Updated

8.2 Using the Index Selection Tool

This section discusses how to:

- Add a table to the Index Selection Tool.

- Select a data source.

- Drop a single index from a table.

- Drop multiple indexes from a table.

- Restore indexes to a table.

- View the Index Selection Logs.

8.2.1 Forms Used with the Index Selection Tool

Form Name

FormID

Navigation

Usage

Machine Search & Select

W95150H

In the Solution Explorer Fast Path, enter P95150.

Provide the location of the data source master table that the Index Selection Tool validates data sources against.

Index Selection Tool

W95150A

On Machine Search & Select, select a row and then click Select.

Flag, drop, and restore table indexes.

Choose OCM or Regular Data Source

W95150D

On Index Selection Tool, click the search button in the Data Source field.

Choose the method in which you want to select a data source.

Select Data Source By Object Configuration Manager

W95150C

On Choose OCM or Regular Data Source, select the "Select data source by OCM (recommended)" option and click OK.

Select the data source that the table is mapped to by OCM.

Database Data Source Search and Select

W986101WB

On Choose OCM or Regular Data Source, select the "Select data source from list of all data sources" option and click OK.

Select a data source from which you want to drop table indexes.

Add Table to Index Selection Tool

W95150B

On Index Selection Tool, click the Add button.

Select a table for flagging or dropping indexes.

Index Selection Logs

W95150I

On Index Selection Tool, from the Form menu, select Index Selection Logs.

View the Index Selection Logs.

8.2.2 Adding a Table to the Index Selection Tool

Access the Machine Search & Select form.

1. Click the search button in the Data Source column to find the data source master table that you want the Index Selection Tool to validate data sources against.
Once you select a table, the system automatically displays the machine in which the table resides in the Machine Name column.

2. Click Select to continue.

3. On the Index Selection Tool, click the Add button.

4. On the Add Table to Index Selection Tool form, select a table and click OK.
The left pane displays the table in a default node tree.

8.2.3 Selecting a Data Source

Before you drop an index from a table, you can select a specific data source location for the table. When you use this method, the Index Selection Tool tree displays the data source in a node for the table.

Access the Index Selection Tool form.

1. Select a table in the tree and then click the Add Data Source button in the center column.

2. On Choose OCM or Regular Data Source, click one of these options and then click OK to continue:

- Select data source by OCM (recommended).
Use this option to ensure that the table exists in any data source that you select.

- Select data source from list of all data sources.
If you select this option, you must select a data source from the Database Data Source Search and Select form, which lists all available data sources.

3. If you selected the "Select data source by OCM (recommended)" option, on Select Data Source by Object Configuration Management, click one of these options and then click the search button in the Data Source column:

- List data sources that the table is specifically mapped to by OCM.
Use this option to select from a list of data sources that the table has been specifically mapped to.

- List data sources that the table is specifically and by "DEFAULT" mapped by OCM.
Use this option to select from a list of data sources that the table has been specifically mapped to, as well as mapped to by default.

4. Click Select.
The Index Selection Tool displays the data source in a new node under the table.

8.2.4 Dropping a Single Index from a Table

Access the Index Selection Tool form.

The instructions in this section assume that you have already selected a table and a specific data source from which you want to drop the table index.

1. Expand the data source node to view the indexes for the table.

2. To flag an index, select an index and then click the Flag/Unflag Index button.

3. To drop a single index, select a flagged index and then click the Drop Single Index button.

4. On Drop Single Index, click one of these options and then click OK:

- Use proxy user and password.

- Specify user and password.
This option activates the Owner ID and Password fields, which you must complete before clicking OK.

5. On the dialog box, click OK to continue.

8.2.5 Dropping Multiple Indexes from a Table

Access the Machine Search & Select form.

The instructions in this section assume that you have already selected a table and a specific data source from which you want to drop indexes.

1. From the data source node, select an index, and then click the Flag/Unflag Index button. Repeat until you have flagged all of the indexes that you want to drop from the table.

2. To drop multiple indexes, select the data source node that contains the indexes that are flagged to be dropped, and then click the Update Table Indices button.

3. On Update Table Indices, click one of these options and then click OK:

- Use proxy user and password.

- Specify user and password.
This option activates the Owner ID and Password fields, which you must complete before clicking OK.

8.2.6 Restoring Indexes to a Table

Access the Index Selection Tool form.

1. Locate the table and data source that you want to restore indexes to.

2. Expand the data source node to view the indexes that have been dropped.

3. If you want to restore a single index, select the index and then click the Create Single Index button.

4. If you want to restore all of the indexes to the table, select the appropriate data source node and then click the Update Table Indices button.

8.2.7 Viewing the Index Selection Logs

Use the Index Selection Logs to view all of the actions that you have taken when working with table indexes.

Access the Work with Index Selection Logs form.

1. Enter a table name in the Table Name field or enter an asterisk (*) to view all the tables that have been acted upon in the Index Selection Tool.

2. Click Find.
The program displays the records for all actions taken based on the search criteria. Each record contains this information:

- Table Name

- Data Source

- Index ID

- Log Description

- User

- Machine

- Date Updated

- Time Updated

9 Using Interactive Versions for Applications

This chapter contains the following topics:

- Section 9.1, "Understanding Interactive Versions for Applications"

- Section 9.2, "Working with Interactive Versions"

9.1 Understanding Interactive Versions for Applications

In JD Edwards EnterpriseOne applications, a version is a user-defined set of specifications. These specifications help to control how interactive applications run. Interactive versions are associated with applications (usually as a menu selection) and always run on a workstation.

Interactive versions for applications contain processing options with different sets of data for each version. These processing options are passed to the application when it runs.

Versions enable you to modify the behavior of applications because they exist independently of the application. Typically, administrators control the creation, modification, and location of the actual version tables. When you upgrade JD Edwards EnterpriseOne software applications to a new release level, you can apply the existing versions to the new applications.

When a user starts an interactive application, the user might have the option to select from a list of versions. A user only has this option if the application designer attached processing options to the application. If the system administrator sets the version for blind execution, when the user starts the application, the application uses the saved processing option values for the version without prompting you for new processing option values. If the system administrator sets the version for Prompt for Values, the user will be prompted to enter processing option values. Depending on how you assign security to your JD Edwards EnterpriseOne software applications, end users can select or create different versions based on business requirements.

For example, on the System Administration Tools menu (GH9011), the Interactive Versions option (P983051) does not have processing options attached, so a version does not exist for the application. However, the Work With Servers application (P986116) has processing options attached so that the system administrator must attach a version for the application. Otherwise, the application uses the default. For each interactive application, the system administrator can set up multiple versions that contain different processing options values for each version.

9.1.1 How Processing Options Affect Versions

The processing options that you define in versions are a set of parameters that alter how an application runs. They are similar to initialization (.ini) files and command-line arguments for a traditional executable. These processing options let you specify the options that you want when you open an application. For example, you can specify the appearance of a form, show or hide a field, change the default status for order activity rules, and set default information to appear in a field. Depending on how the developer coded the application, the following functionality could be available:

- Change the functionality of an application. For example, you can set up processing options to select or deselect logic in order holds. You also can specify whether you want to automatically print pick slips after you enter an order.

- Change default values. For example, in Sales Order Entry you can set up processing options to set default values for document type values (such as Sales Order or Sales Quote) or line type (such as stock or nonstock item).

- Control the display of forms. For example, you can set processing options to hide or show a cost field, a price field, or a commission field.

Not all JD Edwards EnterpriseOne applications have processing options. If the Prompt For Values option on the Edit menu is grayed out, either no processing options are associated with the application or the system administrator has disabled the processing options. To use versions with an application, you must first attach processing options to the interactive application.

The system administrator can secure a version for an application. In this case, the Prompt For Version option on the Edit menu appears grayed out. When a user opens a secured version of an application from the Work With Interactive Versions application, a security message appears to alert the user that she or he does not have access to the version.

9.1.2 How Interactive and Batch Versions Differ

Interactive versions have processing options. Batch versions have processing options, data selection and sequencing, and template overrides. You do not check in and check out interactive versions, whereas batch versions have local specifications that must be checked in and checked out.

9.2 Working with Interactive Versions

This section provides an overview of how to work with interactive versions and discusses how to:

- Work with version detail for interactive versions.

- Copy an interactive version.

- Create an interactive version.

9.2.1 Understanding How to Work with Interactive Versions

When you work with interactive versions, you change processing options, version detail, and copy or create versions. You can also review information such as the date the version was last modified and the user who performed the modification. Interactive versions must be associated with a menu selection in order to run the specified version.

In JD Edwards Solution Explorer, you can display the available versions of an interactive application by choosing Prompt for Version from the Edit menu or by choosing the Interactive Versions (P983051) menu selection. You can filter the versions that you want to display to show all versions or only your versions. To filter the version display, select the Display option from the Form menu.

9.2.2 Working with Version Detail for Interactive Versions

Access the Work With Interactive Versions form. Enter IV in the Fast Path.

Note:
Depending on your security level and the level of security for the version, you might not be able to change the version detail information.

1. Enter an application ID in the Interactive Application field and click Find.
For example, to locate a version for the Sales Order Entry application, enter P42101.

2. In the grid, select a version with which to work, and then from the Row menu, select Version Detail.

3. On the Interactive Application Version Details form, you can modify the information in these fields:

Field

Description

Version Title

Enter information that describes the use of a version in this field. This field should describe the use of a version. For example, an application for generating pick slips might have a version called Pick Slips - Accounting and another version called Pick Slips - Inventory Management.

Prompting

Enter a value to determine whether the processing options for the version are disabled, run with blind execution, or chosen by the user at run time.

Security

Enter a value to determine the security for the version, ranging from no security to full security. This security is based on the user and is not related to the application security. Depending upon your security level and the level of security for the version, you might not be able to work with version detail.

4. Review the additional information that appears on the form, as needed.

9.2.3 Copying an Interactive Version

You can copy an existing version and then tailor its information to fit your needs. The copied version inherits the processing option values of the existing version.

When you copy a version, you should add security to the new version. Security settings range from none (anyone has the authority to modify or run the version) to full (only the person who last modified the version can modify and run the version).

Note:
Depending on your security level and the level of security for the version, you might not be able to copy the version.

Access the Work With Interactive Versions form. Enter IV in the Fast Path.

1. Enter an application ID in the Interactive Application field and click Find.

2. In the grid, select a version with which to work, and then click Copy.

3. On the Copy Interactive Application Version form, complete these fields and then click OK:

Field

Description

New Version

Enter a unique identifier for this version of the application in this field.

Version Title

Enter information that describes the use of a version in this field.

Security

Enter a value to determine the security for the version, ranging from no security to total security.

4. On the Interactive Version Design form, click one of these buttons:

Option

Description

Revise Version

Click this option to access the Version Detail form and modify this version.
See Working with Version Detail for Interactive Versions.

Processing Options

Click this option to change the processing options for the version.

Run Local Web

Click this option to run the version.

5. Click OK when you are finished modifying the interactive version.

9.2.4 Creating (Adding) an Interactive Version

You can create (add) a new interactive version that is not based on an existing version. When you create an interactive version, you should add security to the new version. Security settings range from none (anyone has the authority to modify or run the version) to full (only the person who last modified the version can modify and run the version).

Access the Work With Interactive Versions form. Enter IV in the Fast Path.

1. Enter an application ID in the Interactive Application field.
For example, to add a version for the Sales Order Entry application, enter P42101.

2. Click Add to create a new version.

3. On the Version Add form, complete these fields, and then click OK:

Field

Description

Version

Enter a unique identifier for this version of the application in this field.

Version Title

Enter information that describes the use of a version in this field.

Prompting Options

Enter a value to determine how the version assigns processing options, such as no processing options or blind execution, or prompts the user to select options at runtime.
Blank is not a valid value when you add a version. All versions for interactive applications must have processing options attached.

Security

Enter a value to determine the security for the version, ranging from no security to full security.

4. On the Interactive Version Design form, click one of these options:

Option

Description

Revise Version

Click this option to access the Version Detail form and modify this version.
See Working with Version Detail for Interactive Versions.

Processing Options

Click this option to change the processing options for the version.

Run

Click this option to run the version.

5. Click OK when you are finished adding the interactive version.

10 Working with User Defined Codes

This chapter contains the following topics:

- Section 10.1, "Understanding User Defined Codes"

- Section 10.2, "Understanding UDC and UDC Type Customization"

- Section 10.3, "Understanding UDC Tables"

- Section 10.4, "Customizing User Defined Codes"

- Section 10.5, "Customizing UDC Types"

- Section 10.6, "Translating User Defined Codes into Alternate Languages"

10.1 Understanding User Defined Codes

Most forms in JD Edwards EnterpriseOne contain fields. Some fields enable you to enter any value, and some require you to select from a list of values. A user defined code (UDC) is one value in a set of values that is assigned as valid for a field. You can use UDCs to categorize your data and make sure that users provide consistent input on forms. Because users can select only values from the list, UDCs simplify, standardize, and validate the data that is contained in fields.

From any JD Edwards EnterpriseOne application, you can identify fields that have UDCs attached to them by using the visual assist button that appears when you tab into or click in a field. If you do not know the value to enter in a field with a user defined code attached to it, click the visual assist button, which accesses the Select User Define Code form. This form displays all values contained in the user defined code tables for this field. You can then select the value to use.

JD Edwards EnterpriseOne provides predefined UDCs, but many of the UDCs that you will use are unique to your enterprise, and your needs are likely to change. Therefore, the system lets you change, add, and delete UDCs to meet the needs of your enterprise. When you upgrade JD Edwards EnterpriseOne software, your customized UDCs will remain.

10.1.1 UDCs, UDC Types, and Category Codes

A UDC is one value in a set of values that you have assigned as valid for a field. A UDC is made up of two parts. The first part is the code, which consists of the characters that you enter in a field. The second part is the description, which is text that describes what the code means. For example, on the Work With Addresses form, you can enter A in the Search Type field to designate an Applicant; this code becomes part of the data stored with the record.

A UDC type is the complete set of UDCs that are allowed as values for a field. A UDC type is made up of a code type, which is its two-character name, and a description. Examples of UDC types are ST - Search Type and UM - Unit of Measure. UDC types are sometimes referred to as UDC lists.

Each UDC type is associated with a JD Edwards EnterpriseOne product code. You can identify any set of UDCs by its product code and its code type. For example, the Address Book (product code 01) list of search types (code type ST) is referred to as UDC 01/ST.

Throughout the system, you will see references to category codes. Category codes are UDC types that JD Edwards EnterpriseOne provides for you to customize according to your needs. You can change the code type and the description, and you can redefine the UDCs as appropriate for your purposes. For example, you might see a UDC type called Category Code 01. You can change its description and define the UDCs within it to suit your business needs.

10.1.1.1 Example: User Defined Codes in Address Book

JD Edwards EnterpriseOne systems use UDCs. For example, Address Book uses a field called Search Type to classify the entries in the address book. When you click the visual assist button in the Search Type field on the Work With Addresses form, a list of the search types appears. These search types are UDCs. Some of the search types include the following:

- A - Applicants

- C - Customers

- V - Suppliers

- E - Employees

You can use these UDCs to classify your address book entries, and you can add or change UDCs to accommodate your needs. For example, if you need to categorize some of your address book entries as students, you can add a UDC to the list, such as S - Students.

UDCs are also used to supply values for the following:

- State and province codes

- Units of measure

- Document types

- Languages

When you click the visual assist for a field and the system displays the Select User Defined Code form, you know that you are working with UDCs.

10.2 Understanding UDC and UDC Type Customization

JD Edwards EnterpriseOne provides many UDC types that contain predefined UDCs. Some of the UDCs are hard-coded, which means that certain applications depend on specific values, so you should not change these UDCs. However, if a UDC is not hard-coded, you can change it to suit your business needs.

Many of the UDCs that you need to use are unique to your enterprise, and your needs are likely to change. Therefore, you can change, add, and delete UDCs. UDCs enable you to customize JD Edwards EnterpriseOne software to meet your needs without having to write complex programs or modify the system code. When you upgrade JD Edwards EnterpriseOne software, your customized UDCs remain.

You can change, add, and delete UDCs in these ways:

- Change the code or the description of a UDC in an existing UDC type. For example, in UDC 01/ST, a medical institution might change the UDC for C - Customers to P - Patients to more accurately describe the category.

- Add UDCs to an existing UDC type. For example, in the Search Type list, you might add a UDC for S - Students.

- Delete UDCs from a UDC type. For example, if you want to prevent users from choosing a UDC, you can delete it from the UDC type.

You can also change, add, and delete UDC types in the following ways:

- Change the code type or the description of an existing UDC type, which is useful if you want to customize one of the generic category code lists for your needs.

- Create a new UDC type and add UDCs to it. For example, an educational institution might create a UDC type called MA - Major Field of Study to classify its students, and it might define the following UDCs:

- LA - Liberal Arts

- MA - Mathematics

- CS - Computer Science

- EN - Engineering

- MD - Medicine

10.2.1 Consequences of Customizing UDCs

Because UDCs can significantly affect the integrity of your data, you should customize them only as part of a coordinated plan within your enterprise. When you add or change a UDC, you are affecting the set of values against which the system validates the data entry. However, you are not affecting the actual content of any existing data records. By changing UDCs within a working production environment, you might affect the integrity of your data. For example, you use Address Book to enter address book records, and you use search types to classify those records. Suppose that you select a search type of C - Customers to classify some of the records that you enter. Later, you decide to change that UDC from C - Customers to P - Patients. Any address book records that you entered with the original UDC value of C will still contain that value. When Address Book displays these records, you will see an error in the Search Type field because C is no longer a valid value.

10.3 Understanding UDC Tables

You use the User Defined Codes program (P0004A) to create and customize UDCs and UDC types. The program stores UDC information in the following tables:

- User Defined Code Types (F0004)

- User Defined Codes (F0005)

10.3.1 Prerequisite

Every UDC belongs to a UDC type. Verify that a UDC type exists where you will add the UDC.

See Adding a UDC Type.

10.4 Customizing User Defined Codes

A UDC is made up of two parts. The first part is the code, which consists of the characters that you enter in a field. The second part is the description, which is text that describes what the code means. You can change both the code and the description. For example, the UDC list of search types contains the code C, which designates Customers. A medical facility might change this code and description to P for Patients.

This section discusses how to:

- Change a UDC.

- Add a UDC.

- Delete a UDC.

10.4.1 Change a UDC

Access the Work With User Defined Codes form. On the JD Edwards EnterpriseOne web client, from a System Setup menu for your product, access the P0004A program.

1. Complete the Product Code and User Defined Codes fields and click Find.
For example, to display the list of Address Book search types, which is UDC 01/ST, type 01 in the Product Code field and ST in the User Defined Codes field.

2. Select the code that you want to modify and click Select.

3. On the User Defined Codes form, modify any of these fields and click OK:

Field

Description

Codes

A user defined code (98/SY) that identifies a system. Valid values include:
01

Address Book

03B

Accounts Receivable

04

Accounts Payable

09

General Accounting

11

Multicurrency

Description 01

A code that identifies the table that contains user defined codes. The table is also referred to as a UDC type.

Special Handling

A code that indicates special processing requirements for certain user defined code values. The value that you enter in this field is unique for each user defined code type.
The system uses the special handling code in many ways. For example, special handling codes defined for Language Preference specify whether the language is double-byte or does not have uppercase characters. Programming is required to activate this field.

Hard Coded

A code that indicates whether a user defined code is hard-coded. Valid values are:
Y

The user defined code is hard-coded

N

The user defined code is not hard-coded

A check mark indicates that the user defined code is hard-coded.

10.4.2 Adding a UDC

Add a UDC to a UDC type when none of the existing codes is appropriate for your needs. For example, if you need to identify the entries in the address book that are your business partners, you can add a search type B - Business Partners to UDC 01/ST.

Access the Work With User Defined Codes form. On the JD Edwards EnterpriseOne web client, select the appropriate program for changing UDCs.

1. Complete the Product Code and User Defined Codes fields and click Find. In the User Defined Codes field, enter the UDC type for which you want to add the UDC.

2. On the Work With User Defined Codes form, click Add.

3. On the User Defined Codes form, scroll to the last empty row of the detail area.

Important:
Be sure to add each new code on the last detail row so that you do not inadvertently overwrite a blank code, which might appear in the first detail row. A blank code might have only a period in the Description field.

4. Enter a code in the Codes field. To allow a blank as a valid value, leave this field blank.

5. Enter a description in the Description 1 field. To allow a blank as a valid value, type any character (such as a period) in the last space in this field.

6. Complete the Special Handling and Hard Coded fields, and then click OK.

10.4.3 Deleting a UDC

You can delete UDCs from a UDC type, but do so with caution. Only delete UDCs as part of a coordinated plan within your enterprise. For example, you might delete the F - Facilities UDC from the list of search types if you do not want users to select that UDC.

If you delete a UDC, the system deletes only the code from the UDC type. UDC values in existing records are not deleted.

Important:
Do not delete hard-coded UDCs because JD Edwards EnterpriseOne applications might depend on them. Hard-coded UDCs have the value Y in the Hard Coded field on the Work With User Defined Codes form.

Access the Work With User Defined Codes form. On the JD Edwards EnterpriseOne web client, from a System Setup menu for your product, access the P0004A program, or enter UDC in the Fast Path field.

1. Complete the Product Code and User Defined Codes fields and click Find.

2. On the Work With User Defined Codes form, select the UDC from the detail area that you want to delete and click Delete.

Important:
Ensure that you want to delete this UDC. The only way to replace a deleted UDC is to add it again.

3. Click OK to confirm that you want to delete the UDC.

10.5 Customizing UDC Types

This section provides overviews of how to customize UDC types and add UDC types and discusses how to:

- Change a UDC type.

- Add a UDC type.

- Delete a UDC type.

10.5.1 Understanding How to Customize UDC Types

A UDC type is the complete set of UDCs that is allowed for a field. A UDC type is made up of a code type, which is its two-character name, and a description. Examples of UDC types are search types and units of measure. UDC types are sometimes referred to as UDC lists.

Each UDC type is associated with a JD Edwards EnterpriseOne product code. You can identify any set of UDCs by its product code and its code type. For example, the Address Book (product code 01) list of search types (code type ST) is referred to as UDC 01/ST.

You can change the code type and the description of an existing UDC type to meet your needs. Typically, you would change only the description so that it provides a meaningful description of the UDCs within the UDC type. For example, to classify your customers according to how much business they provide, you can change the description for Category Code 01 to Customer Volume. Then, you can customize the individual UDCs within that UDC type to describe the following classifications for your customers:

- H - High-volume customer

- M - Medium-volume customer

- L - Low-volume customer

You can change the code type, but you should do so with caution. If you change a code type, you could invalidate any existing records that use the original code type.

You can also follow this procedure to see a complete list of UDC types for a product code.

10.5.2 Understanding How to Add UDC Types

Add a UDC type when you need to categorize your data using UDCs and when none of the existing UDC types is appropriate. For example, an educational institution might add a UDC type called "Major" to categorize its students by any of the following fields of study:

- LA - Liberal Arts

- MA - Mathematics

- CS - Computer Science

- EN - Engineering

- MD - Medicine

Note:
When you add a UDC type, you also must modify the JD Edwards EnterpriseOne applications that use the UDC type.
Because modifying a JD Edwards EnterpriseOne application might require significant effort, whenever possible, you should change an existing UDC type (such as a category code) instead of adding a new UDC type.

See Changing a UDC Type and "Understanding Edit Controls" in the JD Edwards EnterpriseOne Tools Development Tools: Form Design Aid Guide.

10.5.3 Prerequisite

Delete all individual UDCs from the UDC type.

See Deleting a UDC.

10.5.4 Changing a UDC Type

Access the Work With User Defined Codes form. From a System Setup menu for your product, select the appropriate program for changing UDCs; or enter UDC in the Fast Path field.

1. Select Code Types from the Form menu.

2. On the Work With User Defined Code Types form, complete the Product Code field and click Find.
The system displays the UDC types that exist for that product code.

3. Select the UDC type that you want to change and click Select.

4. On the User Defined Code Types form, change the values in any of these fields and click OK:

Field

Description

Code Types

Enter a code that identifies the table that contains user defined codes. The table is also referred to as a UDC type.
Note: It is suggested that you do not change code types. If you change a code type, you might invalidate existing records that use the original code type.

Description

Enter a description for the UDC type.

Code Length

Enter the length of the user defined code. It cannot be greater than 10 characters.

2nd Line (Y/N)

Determines if the Select User Defined Code form will display a second line of description. Valid values are:
Y Enables the second line of description.

M For maintenance only for second line display. This capability is seldom used, but has applicability in areas such as inventory product codes. The M value will not display the second line of description in the Select User Defined Code form.

N Enables the Select User Defined Code form to display only one line of description.

Numeric (Y/N)

Determines whether a user defined code is numeric or alphanumeric.
Valid values are:

Y Indicates that the code is numeric and should be right-justified.

N Indicates that the code is alphanumeric and should be left-justified.

10.5.5 Adding a UDC Type

Access the Work With User Defined Codes form. From a System Setup menu for your product, select the appropriate program for changing UDCs; or enter UDC in the Fast Path field.

1. Select Code Types from the Form menu.

2. On the Work With User Defined Code Types form, complete the Product Code field and click Find.

3. Click Add.

4. On the User Defined Code Types form, scroll to the last empty row of the detail area, complete these fields, and then click OK:

10.5.6 Deleting a UDC Type

You can delete a UDC type, but you should do so with caution. JD Edwards EnterpriseOne applications and the integrity of the data within your database might depend on the existence of UDCs and UDC types. Only delete UDC types as part of a coordinated plan within your enterprise.

Important:
Do not delete UDC types that contain hard-coded UDCs because JD Edwards EnterpriseOne applications might depend on them. Hard-coded UDCs have the value Y in the Hard Coded field on the Work With User Defined Codes form.

Access the Work with User Defined Codes form. From a System Setup menu for your product, access the P0004A program, or enter UDC in the Fast Path field.

To delete a user defined code type:

1. On the Work With User Defined Codes form, select Code Types from the Form menu.

2. On the Work With User Defined Code Types form, complete the Product Code field and click Find:

3. On the Work With User Defined Code Types form, select the code type that you want to delete and click Delete.

Important:
Ensure that you want to delete this code type. The only way to replace a deleted UDC type is to add it again.

4. Click OK to confirm that you want to delete the code type.

10.6 Translating User Defined Codes into Alternate Languages

This section provides an overview on how to translate UDCs into alternate languages and discusses how to:

- Translate UDC type descriptions into alternate languages.

- Translate UDC descriptions into alternate languages.

10.6.1 Understanding How to Translate User Defined Codes into Alternate Languages

Multinational enterprises can translate the descriptions for both UDCs and UDC types into alternate languages. The system displays the descriptions in the language designated by the user's language preference. For example, you can provide a translated description for this UDC:

- Code: E

- English Description: Employees

- Spanish Description: Empleados

In this way, users can select the same UDCs, regardless of their language preference.

The User Defined Code Alternate Descriptions program (P0004D) stores the translated descriptions in the following tables:

- User Defined Codes - Alternate Language Descriptions (F0004D)

- User Defined Codes - Alternate Language Descriptions (F0005D)

10.6.2 Translating UDC Type Descriptions into Alternate Languages

Access the Work With User Defined Codes form. From a System Setup menu for your product, access the P0004A program, or enter UDC in the Fast Path field.

1. Select Code Types from the Form menu.

2. On the Work With User Defined Code Types form, complete the Product Code field and click Find.

3. Select the UDC type that you want to translate and then select Language from the Row menu.

4. On the UDC Alternate Languages form, enter information in a blank row for these fields and click OK:

Field

Description

L

Select the user defined code (01/LP) that specifies the language to use on forms and printed reports. Before you specify a language, a code for that language must exist at either the system level or in your user preferences.

Description

Type the translated description into this field.

10.6.3 Translate UDC Descriptions into Alternate Languages

Access the Work With User Defined Codes form. From a System Setup menu for your product, access the P0004A program, or enter UDC in the Fast Path field.

1. On the Work With User Defined Code form, complete the Product Code and User Defined Codes fields and click Find.

2. Select the code that you want to translate and then select Language from the Row menu.

3. On the UDC Value Alternate Descriptions form, enter the following information in a blank row in the grid, and then click OK:

Field

Description

L

Select the user defined code (01/LP) that specifies the language to use on forms and printed reports. Before you specify a language, a code for that language must exist at either the system level or in your user preferences.

Description

Type the translated description into this field.

11 Working with User Overrides

This chapter contains the following topics:

- Section 11.1, "Understanding User Overrides"

- Section 11.2, "Setting Up User Overrides"

11.1 Understanding User Overrides

This section provides an overview of user overrides and discusses:

- Search hierarchy

- Cached override information

11.1.1 User Overrides Overview

User Overrides enable you to change the appearance of an application to fit the needs of your business. For some user overrides, such as an object linking and embedding (OLE) attachment to a form, no consequences exist when you upgrade your software because your user overrides are merged into the new release. For other user overrides, such as grid or toolbar formats, the system gives you the options of reconciling your user overrides with the new software or deleting your user overrides.

A user override changes only the appearance of an application; it does not affect the application's functions. You can set overrides by user ID, role, or the keyword *PUBLIC. If you set your override by user ID, only that user is affected when he or she signs on to any workstation in the enterprise. If you set your overrides by role, those users who are set up within User Profiles to be members of that group are affected. If you set your user overrides by *PUBLIC, all users in the enterprise are affected. After you create an override for a role or *PUBLIC, each employee inherits that override, regardless of the workstation he or she signs on to. Even with role or *PUBLIC overrides, each employee can further customize a version to fit individual needs. For example, if someone in a department has trouble seeing text on a form, he or she can switch to a larger font. This change applies only to the individual, not to the entire group or company.

Oracle's JD Edwards EnterpriseOne stores these modifications in the User Overrides Table (F98950). Because the system tracks the overrides by your user ID or role, the modifications will appear on any workstation that you sign on to. User overrides enable you to make the following modifications:

- Resequence the grid.

- Change the sort order of rows and columns.

- Freeze columns and rows.

- Move and resize columns and rows.

- Change the magnification and font size.

- Add charts and graphs to an application, and embed third-party products that support OLE automation.

The following overrides are local only; they can be considered workstation preferences. The system stores these overrides on your workstation; therefore, they are accessible only from that workstation:

- Sizing of the parent and child windows.

- Changing the parent window.

- Changing fonts on a form.

- Maximizing the form.

- Turning on the exit bar.

See Also:

- "Using the JD Edwards EnterpriseOne Web Application User Interface" in the JD Edwards EnterpriseOne Tools Foundation Guide.

11.1.2 Search Hierarchy

During the execution of an application, the system uses a search hierarchy to locate a user override. The system searches by user and group for each unique combination of application, form, version, and language in the following order:

Hierarchy

Description

User ID

When you access a specific application, the system searches first for an override for the application under your user ID.

Role

If the system does not find an override under your user ID for the application, it then searches for it at the role level. For example, if you are in the Accounts Payable role, the system searches for an override for that role.

*PUBLIC

If the system does not find an override for the application at the role level, it searches for it under *PUBLIC. If no override is found at the *PUBLIC level, the system uses the No Overrides default value.

11.1.3 Cached Override Information

The first time that a user opens an application form, the system reads the User Overrides Table (F98950) and creates a disk cache on the workstation. This table contains form-specific information such as menus, buttons, and formats. This cache improves network performance because multiple database fetches are not required to retrieve individual form elements.

However, if a system administrator or the user modifies user overrides with the User Overrides Revision application (P98950), the system writes the override information directly to the F98950 table, and not to the cached table. Because the system always reads overrides from the cached information, any modified user overrides cannot become effective until the user exits and reenters the system, causing the cached table to be refreshed.

For example, assume that you want to modify a journal entry by adding tabs and then associating those tabs with your user overrides. You would create the tab and then use the P98950 application to associate the tab with your user profile. You would not immediately see any records of the journal entry form because the user override is stored in the User Overrides Table, and the system is looking at the cached information. This process does not affect your ability to create and use local form changes, or workstation preferences, that are not stored in the User Overrides Table.

If for some reason you have two users who share the same user ID, be aware that the system does not share user override records. If both users sign on to the system at about the same time, the first of these two users to sign on will see the user overrides; the second user to sign on will not. Furthermore, the first user to make an override change during simultaneous sessions takes control of the F98950 record, and all other users signed on to the same user ID are locked out.

11.2 Setting Up User Overrides

This section provides an overview of how to create user overrides and discusses how to:

- Create user overrides.

- Change an individual user override to a group user override.

- Fix user overrides after a form change.

11.2.1 Understanding How to Create User Overrides

You can create user overrides for a user ID, a group, or for *PUBLIC. After you create a user override, your user override will be available on any workstation that you sign on to in the enterprise.

If a form for which you have created user overrides has changed after upgrading your software, the system attempts to merge your user overrides with the changed form. You might need to reset your user overrides; at the least, you will need to verify that your user overrides are still intact.

11.2.2 Creating User Overrides

You can create individual user overrides in which the changes that you make to an application reside on an enterprise server and are associated with your user ID. This override is available to you at any workstation that you sign on to. To create a group override, you first create an individual override, and then you change that override to a group override, thereby making the override available to employees within a group or to the entire company (*PUBLIC).

1. Access the application for which you want to create an override (for example, Standard Voucher Entry).

2. Modify the application (for example, rearrange columns or rows on the grid). When you exit the application, the preferences that you just set up are stored in User Overrides under your user ID.

11.2.3 Changing an Individual User Override to a Group User Override

Enter P98950 in the Fast Path.

Note:
The User Overrides application (P98950) is available on the Microsoft Windows client and the web client.

1. On the Work With User Overrides form, enter a user ID in the User/Role field, and then click Find to locate and select the individual override record that you wish to make available to a group.

Note:
Be sure that you select the correct type of override. The two types available are GF for grid tab format overrides, and HC for menu and toolbar overrides. For example, to deploy a grid tab to other users, you need to select a GF record; to deploy a changed menu bar or toolbar, you need to select an HC record.

2. On the Work With User Overrides form, scroll to the right to see the override type, and then click Copy.

3. On the Copy Overrides form, in the User/Role field, enter either a valid role, which has been set up in User Profiles, or *PUBLIC to copy the user override to a role or the entire company.
If you want to change a JD Edwards EnterpriseOne demo version and want the copied version to use the same user overrides as the demo version, do not change the User/Role, but name the version to represent your custom version.

4. In the Version field, enter the version name to copy user overrides set up for one version to another version.

Note:
User Overrides does not create versions.

5. In the Language field, enter a valid language code to select the user override language for the specified user and application.

6. If you copied and modified the version, delete the individual user record that you copied.
Deleting this record ensures that when you log on, you are viewing the overrides for the sign on role, not the override that is specific to your user ID.

Note:
The system creates a record for each form that you modify.

11.2.4 Fixing User Overrides after a Form Change

When you install a package on your workstation, you might have a discrepancy between the changed forms included with the new package and the grid, menu, or toolbar user overrides that you made before the installation. For example, a new column might have been added to a grid for which you have user overrides. After the package installation, the first time that you access the changed form, the system detects the discrepancy between the newly installed form and your existing user overrides. The system asks if you want to fix your user overrides to include the new column or delete your user overrides altogether. If the system cannot fix the discrepancy between the changed form and your user overrides, the system automatically deletes your user overrides.

The system performs this fix only for grid, menu, or toolbar user overrides because all other user overrides, such as an OLE attachment to a form, do not interfere with changes to a form.

The first time that you access a form after a package installation and have a discrepancy between the newly installed form and your user overrides, a message box appears. This box prompts you to either delete your user overrides for that form or have the system try to fix your user overrides to match the changed form.

On the message box that appears, perform one of these tasks:

- To delete your user overrides, click Delete.
The system deletes your user overrides for that form. You can add your overrides again by following the process for creating user overrides.

- To try to fix your user overrides, click Fix.
The system tries to merge the changes from the newly installed form with your user overrides for that form. If successful, verify that the form works properly with your user overrides. If any errors exist with the grid formats or menu and toolbar customization after the system tries to fix the discrepancy, you should delete your user overrides for that form. On the Work With User Overrides form, select your overrides and then click Delete.

If the system is unable to merge the changes with your user overrides, the system automatically deletes your user overrides for that form. You can add your overrides again by following the process for creating user overrides.

12 Working with Vocabulary Overrides

This chapter contains the following topics:

- Section 12.1, "Understanding Vocabulary Overrides"

- Section 12.2, "Creating Vocabulary Overrides"

12.1 Understanding Vocabulary Overrides

Vocabulary Overrides (P9220) is an application that you can use to change the text that appears on forms and reports. You can specify both form columns and row headings, provide customization for multiple languages and industries, and retain your overrides with the next software update.

Because the Vocabulary Overrides application (P9220) affects the user interface throughout JD Edwards EnterpriseOne, it is important that you secure this application from most users. When you work with vocabulary overrides for an interactive or batch application, the Vocabulary Overrides application simulates an application checkout from the central objects repository, just as if you checked out the application by using JD Edwards EnterpriseOne OMW. This checkout is done so that, while you are working on the application in the Vocabulary Overrides application, no one can check out the application.

Note:
When the OMW line is written for the Vocabulary Overrides application, the system does not bring down specifications to the requesting workstation. Instead, the requesting workstation accesses the relational database tables directly.

After you make vocabulary override changes, use an update package to push these changes to the users.

12.2 Creating Vocabulary Overrides

You can create vocabulary overrides to customize the interactive and batch applications. After you make vocabulary override changes, use an update package to push these changes to the users. For example, you could create vocabulary overrides for the Verify OCM report. After you make vocabulary override changes, you should use an update package to push these changes to the users.

Note:
When you create a vocabulary override for a report, the override occurs at the version level. When you run the version, the vocabulary override appears on the report instead of the data dictionary description. The vocabulary override does not affect the base report specifications or any other version of the report.

12.2.1 Forms Used to Work with Vocabulary Overrides

Form Name

FormID

Navigation

Usage

Work With Vocabulary Overrides

W9220H

Application Development (GH902), Object Management, Vocabulary Overrides (P9220)

Locate an interactive or batch application to which you want to apply vocabulary overrides. Review existing vocabulary overrides.

Object Management Workbench

W98220A

In Solution Explorer, enter OMW in the Fast Pathfield.

Locate an interactive or batch application to which you want to apply vocabulary overrides.

SAR Requirement

W559220A

On the Work With Vocabulary Overrides form, select an application and click Select.

This form only appears if the system administrator set up the processing option for vocabulary overrides to require a software action request (SAR) number for overrides.

Interactive Vocabulary Overrides

W9220A

On the Work With Vocabulary Overrides form, select the Interactive option and click Find. Select an application, and click Select.

Create and reset interactive vocabulary overrides.

Batch Vocabulary Overrides

W9220B

On the Work With Vocabulary Overrides form, select the Batch option and click Find. Select a batch version and click Select.

Create and reset batch vocabulary overrides.

Overridden Data Item Search

W9220E

On the Work With Vocabulary Overrides form, from the Form menu, select Data Item Search.

Review data items that contain vocabulary overrides.

12.2.2 Accessing Vocabulary Overrides from JD Edwards EnterpriseOne Solution Explorer

Access the Work With Vocabulary Overrides form.

1. Select the Interactive or Batch option and click Find.
Use the query by example fields to refine the search.

2. Select an application and click Select.
If the application that you selected is checked out or is in the save location, the system displays the following error message: This object is currently in use by a project in JD Edwards EnterpriseOne OMW (either through check out or in the save location) and is, therefore, unavailable.

You must create vocabulary overrides for this application at another time or contact the users of the application to check in, erase their checkout, or delete the object from the save location.

3. If the SAR Requirement form appears, enter a SAR number in the SAR Number field.
This form appears if the system administrator set up the processing option for vocabulary overrides to require a SAR number for overrides.

4. Click OK.
The Interactive Vocabulary Overrides form or the Batch Vocabulary Overrides form appears. All of the interactive forms or batch versions associated with the application that you chose appear in the detail area. You can expand any row that has a plus (+) sign on the left side.

The Vocabulary Overrides application essentially checks out this application in JD Edwards EnterpriseOne OMW so that while you are working on the application in Vocabulary Overrides, no one else can check out the application. After you finish creating overrides, Vocabulary Overrides erases the checkout in JD Edwards EnterpriseOne OMW.

12.2.3 Accessing Vocabulary Overrides from JD Edwards EnterpriseOne OMW

Access the Object Management Workbench program (P98220).

1. On Object Management Workbench, add the object to an OMW project.

2. Select the interactive or batch application, and then click the Design button.
The Interactive Application Design form or the Batch Application Design form appears.

3. On the Design Tools tab, click Vocabulary Overrides.
The system displays the following warning: Warning! You are now accessing Vocabulary Overrides. This application will override currently checked in objects. You must have authority to make changes.

4. If you have authorization to make vocabulary override changes, click OK.

5. If the SAR Requirement form appears, enter a SAR number in the SAR Number field.
This form only appears if the system administrator sets the processing option that requires a SAR number for vocabulary overrides.

6. On the Work with Vocabulary Overrides form, click Select.
The Interactive Vocabulary Overrides form or the Batch Vocabulary Overrides form appears. All of the interactive forms or batch versions associated with the application appear in the detail area. You can expand any row that has a plus (+) sign on the left side.

The Vocabulary Overrides application essentially checks out this application in OMW so that while you are working on the application in Vocabulary Overrides, no one else can check out the application. After you finish creating overrides, Vocabulary Overrides erases the checkout in OMW.

12.2.4 Creating Vocabulary Overrides

Access the Interactive Vocabulary Overrides form.

1. To work with a language other than the domestic language, on Interactive Vocabulary Overrides, complete the Language field, and then click Find.

2. Enter a language code.
Leave this field blank if you are creating vocabulary overrides in the domestic language.

3. Double-click the + button next to one of the forms listed in the detail area.
The form expands, displaying the types of text that are available on that form, such as find/browse text, control text, grid column text, exit text, and text variables.

4. Double-click the + button for one of the types of text.
The type of text expands, displaying all of the text that you can override.

5. To create a vocabulary override, change the text in the Description column for a particular item.
Click OK when you finish creating overrides.

Note:
Some descriptions for data items contain carriage returns and new-line characters. To create a vocabulary override for these descriptions (indicated with an icon to the left of the row), select the data item row and, from the Row menu, select Extended Text Revision.

6. On the Extended Text Revision form, change the text in the field and click OK.

The Vocabulary Overrides application essentially checks out this application in OMW so that while you are working on the application in Vocabulary Overrides, no one can check the application out. After you finish creating overrides, Vocabulary Overrides erases the checkout in OMW.

To actually see the description change applied to the application, you must first retrieve the specifications for the application to the local client machine and run it. Do this by clicking either the Check Out or Get button in OMW.

12.2.5 Creating Batch Vocabulary Overrides

Access the Batch Vocabulary Overrides form.

1. To work with a language other than the domestic language, on Batch Vocabulary Overrides, complete the Language field, and then click Find.

2. Enter a language code.
Leave this field blank if you are creating vocabulary overrides in the base (domestic) language.

3. Double-click the + button next to one of the versions listed in the detail area.
The version expands, displaying the types of text that are available on that version, such as page header and group sections.

4. Double-click the + button next to one of the types of text.
The type of text expands, displaying all of the text that you can override.

5. To create a vocabulary override, change the text in the Description column for a particular item.

6. Click OK when you finish creating overrides.

The Vocabulary Overrides application essentially checks out this application in OMW so that while you work on the application in Vocabulary Overrides, no one can check the application out. After you finish creating overrides, Vocabulary Overrides erases the checkout in OMW.

12.2.6 Reviewing Vocabulary Overrides

Access the Work With Vocabulary Overrides form.

You can use vocabulary overrides to review every location where someone has overridden a data item. You can view the override locations from a form or from a report.

1. On the Work With Vocabulary Overrides form, from the Form menu, select Data Item Search.

2. On the Overridden Data Item Search form, enter a data item to search for and then click OK.

3. Click one of these options to select a scope for the application search:

- Interactive Application

- Batch

- Both

4. Select one of these options for the output results:

- Interactive
If you view the search results by using the interactive application, the Data Item Locator form appears when this search is complete. This form displays a list of all of the applications in which the data item appears.

- Printed Report
If you view the search results by using the printed report, an Adobe Acrobat Portable Document Format (.pdf) file is created, which you can view or print.

5. From the Form menu, select Run Report.

12.2.7 Resetting a Vocabulary Override

Access the Interactive Vocabulary Overrides form or the Batch Vocabulary Overrides form, depending on the type of application in which you want to reset a vocabulary override.

You can reset vocabulary overrides to the original data dictionary definition. If you need to reset multiple vocabulary overrides to the default data dictionary definition, JD Edwards EnterpriseOne provides an automated process that resets overrides at the interactive form level, the batch version level, and the interactive and batch application level. When you reset vocabulary overrides at the form level, you reset all vocabulary overrides on a specific form—for example, the Work with Addresses form (W01012B) in the Address Book application. When you reset vocabulary overrides at the application level, you reset all vocabulary overrides on all forms or versions in an entire interactive or batch application—for example, the Address Book application (P0101) or the Print Mailing Labels report (R01401).

1. Double-click the + button in the row header for one of the forms or versions in the detail area, and then double-click the + button in the row header for a type of text on the form or a type of section in the version.
The detail area expands to display the data items associated with the type of text or section.

2. Select the data item that you want to reset, and then, from the Row menu, select Reset Description.

Note:
The Reset Description menu option is inactive if a vocabulary override does not exist for the data item.

3. Click OK to return to the Work With Vocabulary Overrides form.
If you click Cancel to return to the Work With Vocabulary Overrides form after you reset a vocabulary override, you do not cancel the action. The data item remains at the default data dictionary definition.

12.2.8 Resetting All Vocabulary Overrides on a Form (Interactive and Batch)

Access the Work With Vocabulary Overrides form.

1. Click one of these options and then click Find:

- Interactive

- Batch

2. Select an application and click Select.
Depending on the type of application, either the Interactive Vocabulary Overrides form or the Batch Vocabulary Overrides form appears. The detail area displays forms for interactive applications and versions for batch applications.

3. From the Form menu, select Reset by Application for interactive applications or Reset by Batch for batch applications.
The software clears all vocabulary overrides from the entire application and resets the data items to the base definitions. If no base definition exists for a data item, the software resets the data item to the default data dictionary definition.

Important:
When you select either the Reset by Application or the Reset by Batch menu option, the decision is final; the software does not provide a confirmation box or a proof mode.

13 Using the Scheduler Application

This chapter contains the following topics:

- Section 13.1, "Understanding the Scheduler Application"

- Section 13.2, "Working with the Job Scheduler"

- Section 13.3, "Using Advanced Scheduling Options"

- Section 13.4, "Reviewing the Job Schedule"

- Section 13.5, "Working with the Scheduler Server"

- Section 13.6, "Creating Daylight Savings Rules"

- Section 13.7, "Running Scheduler Reports"

13.1 Understanding the Scheduler Application

Occasionally, you might want to run batch jobs that take up a great deal of machine resources or that require users to be signed off after normal working hours. You also might want the flexibility to run jobs at scheduled intervals during the day or even periodically throughout the month or year.

The Scheduler application enables you to schedule batch jobs to run after hours or periodically throughout the day, according to a schedule that you define. You can schedule jobs by time (daily, weekly, monthly, yearly) or based on a specified period. You also can set up the scheduler to restart a job in the event of a job failure.

You can specify the server on which you want the job to run, as well as the time zone, regardless of the locale. The Scheduler system uses a modified version of Universal Coordinated Time (UCT), which counts the number of minutes, not seconds.

The following graphic illustrates the scheduling process:

Figure 13-1 The scheduling process

When you define a scheduled job, the parameters of that job are stored in the Scheduled Job Master table (F91300).

After the job is scheduled, the system writes records to the Schedule table (F91320), indicating each time that the job should be launched. As the job runs, the Job Monitor monitors the progress of the job.

When the job ends, the Job Monitor assigns an end status to the job and updates the record of the job in the Job Schedule table to indicate that the job either ended successfully or in error.

13.2 Working with the Job Scheduler

This section provides an overview of the Job Scheduler in Oracle's JD Edwards EnterpriseOne and discusses how to:

- Set processing options for the Job Scheduler.

- Schedule a job.

- Schedule a recurring job.

- Revise a scheduled job.

- Review all jobs or local jobs.

13.2.1 Understanding the Job Scheduler

When you schedule a batch process to run through the Scheduler, you can also add a recurrence pattern to the job, which means that the job will restart at the intervals that you define, such as once a week, once a month, or once a year. You can also specify how many times you want the job to run before it ends, or you can define a date after which the job will no longer run.

You schedule jobs in the local time of the server on which the job will run. For example, when you schedule a job, you might select the version that specifies the eastern time zone to run jobs in eastern standard time (EST).

13.2.2 Prerequisite

To use a server's time zone, you must first specify the time zones that you want to use. To do this, copy the Scheduler processing options (version ZJDE0001 on the Work with Versions form), and modify them according to your needs. If you use more than one time zone, you should modify the processing options to display the Work with Versions form each time that you invoke the Schedule Jobs application. That way, you can select the correct version for the time zone in which you want to schedule the job.

See Also:

- Scheduling a Recurring Job.

- Setting Processing Options for the Job Scheduler.

13.2.3 Forms Used to Work with the Job Scheduler

Form Name

FormID

Navigation

Usage

Work With Versions

W983050B

Report Management (GH9111), Job Scheduler (GH9015), Schedule Jobs (P91300)

Locate the version that specifies the time zone in which the scheduled job will run.

Work With Scheduled Jobs

W91300B

Report Management (GH9111), Job Scheduler (GH9015), Schedule Jobs (P91300). On the Work With Versions form, click the version and then click Add.

Access forms to schedule a job.

Scheduling Information Add

W91300A

On the Work With Scheduled Jobs form, click Add.

Schedule a job.

Scheduling Advanced Options

W91300I

On the Scheduling Information Add form, select Advanced Options from the Form menu.

Enter the user and machine information for the scheduled job.

Recurring Scheduling Information Revisions

W91300C

On the Scheduling Information Add form, select Recurrence from the Form menu.

Schedule a recurring a job.

13.2.4 Setting Processing Options for the Job Scheduler

Processing options enable you to specify the default processing for programs and reports.

13.2.4.1 Display

Although processing options are set up during a JD Edwards EnterpriseOne implementation, you can change processing options each time you run a program.

View Local Time

Local Time Zone

Enter '1' to adjust time for daylight savings. Enter '0' to never adjust for daylight savings.

Use this Daylight Savings Rule when adjusting for daylight savings.

13.2.4.2 Process

Although processing options are set up during JD Edwards EnterpriseOne implementation, you can change processing options each time you run a program.

Maximum number of job schedule records

13.2.4.3 Defaults

Although processing options are set up during JD Edwards EnterpriseOne implementation, you can change processing options each time you run a program.

Default Job Type

Number Of Job Occurrences

Max Number of Job re-submissions

13.2.5 Scheduling a Job

Access the Work With Scheduled Jobs form. On the Work with Versions form, double-click the version that specifies the time zone in which the scheduled job will run.

Note:
If you use only one time zone, you might not be prompted to select a version. In this case, the Work With Versions form does not appear. You can delete the Work With Versions form in the menu properties for P91300. By default, GH9015/P91300 prompts for the version.

1. On the Work With Scheduled Jobs form, click Add.

2. On the Scheduling Information Add form, in the Scheduled Job Name field, enter a name that uniquely identifies to the system and the user of a scheduled job.
Use this name to indicate the job function, such as Monthly Close or Nightly Back Up.

3. In the Scheduled Job Status, determine the status of the scheduled job.
As long as the status is active, the Scheduler determines if the job should be submitted to the server for execution. When the scheduled end date for the job has been reached, the status changes to Not Active. To stop the Scheduler from considering the job for submission, you can change the status to Not Active (or suspended) at any time prior to the end date. You can reactivate the job if you want the Scheduler to include the job again, but you can reactivate a job only if the end date is in the future.

4. In the Scheduled Batch Application, specify the object name of the report that the Scheduler submits to the server.

5. In the Scheduled Version, specify the version of the report that is scheduled to run. A version identifies a specific set of data selections and sequencing settings that the batch job uses.

6. In the Scheduled Start Date/Time, determine the next date on which the Scheduler submits the scheduled job to the server for execution, and then click OK.

13.2.6 Scheduling a Recurring Job

Access the Recurring Scheduling Information Revisions form.

1. Select one of these options, and complete the accompanying fields that appear after you select an option:

- By Time
Run the job every n days or every weekday.

Run the job at the specified time interval. For example, run the job every 40 minutes or every eight hours.

- Daily
Run the job at the specified interval of days or every weekday. For example, run the job every seven days or every weekday.

- Weekly
Recur every n weeks on Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

Run the job at the specified weekly interval on the specified day of the week. For example, run the job every two weeks on Monday.

- Monthly
Day n of every x months or the [first, last, and so on] [day, Sunday, Friday, and so on] of every n months.

Run the job on the specified day of every n months or on a specific day of every n months. For example, run the job on day one of every four months or on the last Friday of every second month.

- Period
Day n of every x periods or the [first, last, and so on] [day, Sunday, Friday, and so on] of every n periods.

- Company

- Yearly
Every [month name] [date] OR

The [first, last, and so on] [day, Sunday, Friday, and so on] of [month name] OR

Day x of the [first, last, and so on] period OR

The [first, last, and so on] [day, Sunday, Friday, and so on] of the [first, last, and so on] period.

Schedule the job at the specified time of the year. For example, you might want to run the job on the last day of December of each year, every January 1, on the first Monday of June, on day 15 of the last period, or on the second Tuesday of the fourth period.

2. Specify when you want the Scheduler to stop submitting the job by selecting one of these options:

- No end date

- End after

- End by
Enter the month, day, and year on which you want the job to expire.

3. Click OK.

13.2.7 Revising a Scheduled Job

Access the Work With Versions form.

You might want to revise the information for a job. For example, you might want to change the job status to Active or Not Active, enter a new batch process as the scheduled job, or change the job start date and time.

1. On the Work With Versions form, select the version that specifies the time zone in which the job will run and click Select.

2. On the Work with Scheduled Jobs form, select the job that you want to revise, and then select Job Revisions from the Row menu.

3. On the Scheduling Information Revisions form, modify the following fields as necessary and click OK:

- Scheduled Job Status

- Scheduled Batch Applications

- Scheduled Version

- Scheduled Start Date/Time

4. If you want to remove recurrence from a scheduled job, select Remove Recurrence from the Form menu.

5. If you want to add category codes to the scheduled job, select Category Codes from the Form menu.

6. On the Scheduler Category Codes form, if you want to revise the advanced options for this job, select Advanced Options from the Form menu.
The Scheduling Advanced Options form appears.

Note:
You can also activate or inactivate a job by selecting the job on the Work With Scheduled Jobs form, and then selecting Change Status from the Row menu.

13.2.8 Reviewing All Jobs or Local Jobs

Access the Work With Scheduled Jobs form.

If necessary, you can review all of the jobs in all time zones, or local jobs only. Depending on the view that you are currently using, the system protects the other choice. For example, if you are currently viewing local jobs, the system protects the Local Jobs choice and enables you to select only All Jobs.

1. On the Work With Scheduled Jobs form, select Display from the Form menu.

2. Click either All Jobs or Local Jobs.

13.3 Using Advanced Scheduling Options

This section provides an overview of the advanced scheduling options and discusses how to:

- Override the environment.

- Override job expiration specifications.

- Define when the Scheduler resubmits a job.

- Override batch application specifications.

- Add values to a report interconnect.

13.3.1 Understanding Advanced Scheduling Options

You can use advanced options to override the job properties, such as the location where the job will run and the environment in which it will run. You can also use advanced options to specify whether you want the system to resubmit a job if it ends in error or if you want to change job expiration specifications.

You can define whether to log errors to the jde.log or jdedebug.log, and whether you want the system to override printer locations and job queues. You can also add a report interconnect to a job if you want to pass parameters to it.

Note:
To restore the default values in the advanced options application, click the default button on the Scheduling Advanced Options forms.

13.3.2 Forms Used to Work with Advanced Scheduling Options

Form Name

FormID

Navigation

Usage

Work With Scheduled Jobs

W91300B

Report Management (GH9111), Job Scheduler (GH9015), Schedule Jobs (P91300)System. On the Work With Versions form, click the version and then click Add.

Access forms to schedule a job.

Scheduling Advanced Options

W91300I

On the Work With Scheduled Jobs form, select the job, and then select Advanced Options from the Row menu.

Override the environment, job expiration, and batch application specifications. Define when the Scheduler resubmits a job.

13.3.3 Overriding the Environment

Access the Scheduling Advanced Options form. Select the Launch Overrides tab.

A situation might exist in which you need to override an environment. For example, you would override the environment if the environment in which you want to run the job is not available or is different from the environment that you were logged into when you scheduled the job.

13.3.4 Overriding Job Expiration Specifications

Access the Scheduling Advanced Options form. Select the Job Expirations tab.

Job expiration specifications ensure that servers do not become overloaded with unexpired jobs. If necessary, you can override job expiration specifications so that the job never expires, or expires after a certain number of minutes.

For example, suppose you schedule a job to run at midnight and another job for 1:00 a.m., but the server goes down and probably will not come back up again before the jobs are scheduled to run. In this case, you can specify that the first job, which you scheduled to run at midnight, expires in 30 minutes (12:30 a.m.), so that if the server does not come back up within 30 minutes, the job expires.

13.3.5 Defining When the Scheduler Resubmits a Job

Access the Scheduling Advanced Options form.

You can define when the Scheduler resubmits jobs. This feature is useful if a job ends in error, for example, because the Scheduler will submit the job after a certain period of time.

To avoid the use of system resources, you can limit the number of times that a job can be resubmitted. You also can have the Scheduler check for connection errors or runtime errors when the job runs. Connection errors occur when the system fails to connect to the server to submit the job. Runtime errors occur when the server on which the job is running places the job in an error state. You can set up the system to monitor for both cases.

To define when the system resubmits jobs:

1. On the Scheduling Advanced Options form, select the Job Resubmission tab.

2. Specify the number of minutes that elapse before the job continues or terminates, and then activate one of the following options:

- Let the job continue.

- Terminate the job.

- Terminate the job and resubmit.

3. If you want to terminate the job and resubmit it after a certain period of time, select the terminate the job and resubmit after option, and enter the number of minutes that you want to elapse before the system resubmits the job.

4. Select one of the following options that apply when the job ends in error:

- Do nothing.

- Resubmit immediately.

- Resubmit after.

5. Specify whether you want the system to check for connection errors, runtime errors, or both.

6. In the Max Number of Job Resubmissions field, specify the maximum number of times that you want the job to be resubmitted.

7. Click OK.

13.3.6 Overriding Batch Application Specifications

Access the Scheduling Advanced Options form.

You can specify if you want errors written to the jde.log. If you want errors written to the jdedebug.log, you can set the trace level to determine what types of errors to include in the log.

You can also override the printer at which a report is printed. This feature is useful if a specific printer is down or if you want to print a report to a printer other than the default. You can specify whether a job should be printed immediately upon completion or held in the job queue to be printed later.

Also, you can override the queue to which the output of a submitted job is sent. If you want to pass parameters to a particular batch job, you can attach a report interconnect through Batch Application Specifications.

To override batch application specifications:

1. On the Scheduling Advanced Options form, select the Batch Application Overrides tab.

2. Select one or more of the following options:

- Jde.log

- Jdedebug.log
If you select jdedebug.log, you must also select the jde.log option.

3. Complete these fields:

- UBE Logging Level
If you select jdedebug.log, you can set a trace level to log certain levels of errors.

- Printer Name
Enter the name of the printer to which you want to print the report that the job generates. If you want to use a default printer, specify DEFAULT.

- Print Immediate
If you want the job output to be sent to the printer immediately, select this option.

- Job Queue
Enter the name of the job queue to which you want the job output sent.

4. Click OK.

13.3.7 Adding Values to a Report Interconnect

Access Work With Scheduled Jobs form.

You can add values to be passed through a report interconnect into a batch process when that batch process is launched. The batch process must first contain a report interconnect.

1. On the Work With Scheduled Jobs form, select the job and then select Advanced Options from the Row menu.

2. On the Scheduling Advanced Options form, select Parameters from the Form menu.

3. On the Report Interconnect form, enter the values that you want to pass to the batch process when the process runs.

4. Click OK.

13.4 Reviewing the Job Schedule

This section provides an overview of how to review scheduled job information and discusses how to:

- Review all job schedules.

- Change the launch status of a job.

- View job details.

- Set the job status manually.

- Reset the job schedule.

13.4.1 Understanding Job Schedule Reviewing

When you schedule a job that includes a recurrence pattern, the system creates a set of schedule records, or instances, for the job in the F91320 table. The F91320 table indicates the times and dates that the job will run. You can review these instances and their statuses, and also change the scheduled job information. For example, you can change the location at which you want a job to process, delete a job instance, or override any advanced functions.

Note:
Because the F91320 table is also used for audit information, you can modify or delete only jobs that have not yet run.

See Also:

- Revising a Scheduled Job.

13.4.2 Forms Used to Review the Job Schedule

Form Name

FormID

Navigation

Usage

Work With Versions

W983050B

Job Scheduler (GH9015), Schedule Jobs.

Locate a version that you want to review.

Work With Scheduled Jobs

W91300B

On the Work With Versions form, select a version and then click Select.

Review all scheduled jobs for a version.

Work With All Job Schedule

W91300M

On the Work With Scheduled Jobs form, select All Schedules from the Form menu.

Review all scheduled jobs for a version.

Job Schedule

W91300F

On the Work With Scheduled Jobs form, select the job, and then select Job Schedule from the Row menu.

Change the launch status of a job instance. Reset the job schedule.

Job Maintenance

W986110BC

On the Job Schedule form, select the job, and then select View Detail from the Row menu.

View details about a job, as well as the job queue, the priority in which the job will run, and the location of the report printer. From this form, you can also change the job priority or the location where the report will print.

Manually Set Job Status

W91300L

On the Job Schedule form, select the job instance for which you want to manually set the job status, and then select Set Status from the Row menu.

Set the job status manually.

13.4.3 Reviewing All Job Schedules

Access the Work With All Job Schedule form.

When you review all of the job schedules, you can view all instances of jobs that have been launched. You can even revise a job by choosing a job instance and then selecting Revise Job from the Row menu.

You can filter the job instances that you want to review by launch date, start date, and time. For example, you can review all of the job instances for today's date by entering that date in the Scheduled Start Date field. Or you can review all job instances that were launched on a certain date by entering that date in the Job Launch Date field. You can also filter job instances by scheduled job name, launch status, report name, or scheduled version.

1. On the Work With All Job Schedule form, filter by start date or start time by completing these fields:

- Scheduled Start Date

- Scheduled Start Time

2. To filter by launch date or launch time, complete these fields:

- Job Launch Date

- Job Launch Time

3. To filter by job name, launch status, report name, or scheduled version, complete these fields:

- Scheduled Job Name

- Launch Status

- Report Name

- Scheduled Version

4. To view all scheduled jobs in all time zones, select All Time Zones from the Form menu.

5. To view all scheduled jobs in the local time zone, select Local Time Zone from the Form menu.

13.4.4 Changing the Launch Status of a Job

Access the Work With Version form.

You can change the launch status of a job. For example, you might need to put a job on hold or reschedule a job.

1. On the Work With Versions form, select the time zone in which the job will run, and then click Select.

2. On the Work With Scheduled Jobs form, locate the job that you want to change.

3. From the Row menu, select Job Schedule.

4. On the Job Schedule form, select the job instance for which you want to change the status, and then enter a new status in the Launch Status field.
Enter 1 for a scheduled status or 50 for hold.

5. Click OK.

13.4.5 Viewing Job Details

Access the Job Schedule form.

1. On the Job Schedule form, select the job, and then select View Detail from the Row menu.

2. On the Job Maintenance form, complete the following fields, if necessary, and click OK:

- Job Priority

- Printer Name

13.4.6 Setting the Job Status Manually

Access the Work With Scheduled Jobs form.

As a system administrator, you can change the status of jobs if the Scheduler is not updating the launch status or if the Job Monitor is disabled.

Note:
If you need to stop a job, select Work with Servers from the Form menu on the Work with Scheduled Jobs form.

Important:
You should secure other users from accessing the Set Status option. Only the JD Edwards EnterpriseOne administrator should have access to this option.

1. On the Work With Scheduled Jobs form, select the job, and then select Job Schedule from the Row menu.

2. On the Job Schedule form, select the job instance for which you want to manually set the job status, and then select Set Status from the Row menu.

3. On the Manually Set Job Status form, complete the Scheduled Launch Status field.

13.4.7 Resetting the Job Schedule

Access the Job Schedule form.

If you configure a job schedule and then change your mind, you can remove the changes and regenerate the job schedule by using the previously defined recurrence pattern. The job schedule is reset to the way it was before you made the changes.

1. On the Job Schedule form, select Reset Schedule from the Form menu.
The system displays the following warning message: This will remove any custom changes to this job's schedule and regenerate the schedule using the recurrence pattern. Are you sure you want to continue?

2. Click Yes to confirm resetting the job's schedule.

13.5 Working with the Scheduler Server

This section provides an overview of the Scheduler server and discusses how to:

- Stop or restart the Scheduler server.

- Pause the job launcher or job monitor.

- Reset the Scheduler server.

- Refresh the Scheduler server settings.

- Modify the Scheduler server and monitor sleep time.

13.5.1 Understanding the Scheduler Server

The Scheduler server is a process that performs two distinct functions: it launches all jobs at the scheduled times, and it monitors each job's progress and ending state. These functions are started by a JDENET message, as defined in the following kernel type in the jde.ini file:

[JDENET_KERNEL_DEF10]
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchScheduler@24
maxNumberOfProcesses=1
beginningMsgTypeRange=2001
endingMsgTypeRange=2256
newProcessThresholdRequests=0
numberOfAutoStartProcesses=1

The Scheduler launches batch processes in a server, environment, and user combination, based on the information in the F91300 table. After the Scheduler is started, JDENET keeps it in a wait state by calling the Scheduler dispatch function every minute with an idle message. This idle message enables the Scheduler process to check whether it should launch a job or monitor the jobs that are running. In addition, JDENET sends the Scheduler any message sent from the workstation (for example, messages that new job schedules were added).

You can stop, reset, restart, and refresh the Scheduler server. For example, if the server goes offline, it needs to be reset. You can also modify the server and monitor sleep time, specifying how many seconds you want JDENET to wait until it checks to see if it needs to initialize, or wake up, the Scheduler server.

You also might encounter situations for which you need to activate or deactivate the Job Launcher or Job Monitor. For example, you might need to take down the servers to which you submit jobs and for which you want to avoid unnecessary connection errors when jobs are submitted.

You can also change the jde.ini file to enable the Scheduler to restart automatically by changing the numberOfAutoStartProcesses line. If you enable this feature, and the server on which the Scheduler server is running comes down, the Scheduler server automatically restarts when the server comes back up, instead of having to be restarted manually. When the Scheduler server restarts, the Scheduler checks the F91320 table to determine if it should restart on that server. If not, the Scheduler shuts down.

JDENET handles the calls to initialize the Scheduler server. The JDENET process either sends a message to initialize the Scheduler to launch a job if it receives a message that table F91320 has changed, or it sends an idle message if no change is detected. For faster response time, you can decrease the number of seconds that you want JDENET to wait until it checks to see if table F91320 has changed.

Note:
This application is for administrators only. You should secure users from accessing the Scheduler server application.

13.5.1.1 Control Record

A control record is a job record in the F91300 table. It is named *SCHEDULE and is hidden from the user. The *SCHEDULE record contains information about the state of the Scheduler processes on the server, and it is the method of communicating to those processes.

For example, when the launch loop starts on the server, it sets a flag in this record to indicate that it is up and running. You can end the launch loop by toggling the corresponding end process flag (such as Job Launcher Status or Job Monitor status) from the Form menu on Scheduler Server Control. The next time that the launch loop fetches the control record, it finds the flag, resets both flags, and ends.

If the system does not find the control record when it is fetched, the record is recreated by P91300 when entering the Scheduler Server Control form. In addition, if the record is corrupt, the aforementioned function is called to recreate it. The sleep times for the job monitor are reset to 15 minutes, and the audit information in this record is updated with the user ID set to SCHEDULER.

13.5.1.2 Dispatch Function

The dispatch function handles the incoming message from the workstation and starts the requested process. The JDENET process either sends a message to initialize the Scheduler, signals that the F91320 table has changed, or gives an idle message. The idle message is sent every minute unless one of the other messages is sent. When the idle message is sent, the dispatch function checks to see if the launch loop or job monitor needs to be called. If neither does, control is given back to JDENET.

13.5.1.3 Launch Loop

The launch loop function selects all of the jobs up to the current time. It then loops through the selected records and launches the active jobs if they have not expired. After launching all current jobs, the launch loop fetches all future jobs sorted by start time. If the fetch succeeds, the next select time (NST) is set to the difference between the current time and the start of the next job. If the fetch fails, the NST is set to zero, which indicates that this function should be run the next time that any record is added to or updated by the F91320 table. In addition to launching jobs, the launch loop checks the control record periodically to see if it should exit.

The launch loop also looks for updates of all the schedule instances (F91320 records) and job headers (F91300 records) that it fetches. After the launch loop has processed these records, it then commits any changes and unlocks all of the records.

13.5.1.4 Job Monitor Loop

The job monitor loop monitors the ending statuses of the launched jobs and relaunches those that end in error if requested to do so by the user. This loop cycles through the internal job list that the job launch loop populates. In addition, it terminates jobs that run too long, if requested to do so. A job cannot be relaunched for more times than specified in the F91300 record of the job.

Like the launch loop, the job monitor loop periodically fetches the control record to see if it should end.

See Also:

- "Defining Report Interconnects" in the JD Edwards EnterpriseOne Tools Development Tools: Report Design Aid Guide.

- "Using Debug Tracing" in the JD Edwards EnterpriseOne Tools Development Tools: APIs and Business Functions Guide.

13.5.2 Forms Used to Work with the Scheduler Server

Form Name

FormID

Navigation

Usage

Work with Versions

W983050B

Job Scheduler (GH9015), Schedule Jobs (P91300).

Locate the version that specifies the time zone in which the scheduled jobs run.

Work with Scheduled Jobs

W91300B

On the Work with Versions form, select a version and then click Select.

Access the Scheduler Server Control form.

Scheduler Server Control

W91300G

On the Work with Scheduled Jobs form, select Scheduler Server from the Form menu.

Stop, restart, reset, refresh, or modify the Scheduler server. Pause the job launcher and job monitor. Modify the Job Monitor sleep time.

13.5.3 Stopping or Restarting the Scheduler Server

Access the Work with Versions form.

1. On the Work with Versions form, select the version that specifies the time zone in which the scheduled jobs run, and then click Select.

2. On the Work with Scheduled Jobs form, select Scheduler Server from the Form menu.

3. On the Scheduler Server Control form, perform one of these operations and click OK:

- To stop the server, select Stop Scheduler from the Form menu.

- To restart the server, select Start Scheduler from the Form menu.

13.5.4 Pausing the Job Launcher or Job Monitor

Access the Scheduler Server Control form.

Note:
You might want to pause the job launcher or job monitor, such as when you want to take down the servers to which you submit jobs, and you want to avoid server connection errors that might occur while those servers are down. When you pause the job launcher, the Scheduler stops looking at the F91320 table for jobs to launch. When you pause the job monitor, the Scheduler stops monitoring the status of launched jobs.

1. On the Scheduler Server Control form, select Pause Job Launcher from the Form menu to pause the job launcher.

2. To pause the job monitor, select Pause Job Monitor from the Form menu.

13.5.5 Resetting the Scheduler Server

Access the Scheduler Server Control form.

Note:
You reset the Scheduler server after you change the status of the Job Monitor or Job Launcher. For example, if you change the status of the Job Monitor, you would select Reset to refresh the settings on the server.

1. On the Scheduler Server Control form, select Reset from the Form menu.

2. Click OK.

13.5.6 Refreshing the Scheduler Server Settings

Access the Scheduler Server Control form.

Note:
When you refresh the Scheduler server settings, the server refreshes its cache of launched jobs, and closes and restarts all environment and table handles. It is a refresh of the server's internal structures. You might want to refresh the Scheduler server settings if you had to restart the server.

1. On the Scheduler Server Control form, select Refresh from the Form menu.

2. Click OK.

13.5.7 Modifying the Scheduler Server and Monitor Sleep Time

Access the Scheduler Server Control form.

Note:
Sleep time is the time that the Scheduler server or monitor is idle.

Scheduler Sleep Time

This field indicates the number of seconds that the scheduler server will sleep (or idle). For example, if this field is set to 60 seconds, the Scheduler server checks every 60 seconds to see if it needs to launch or monitor jobs. The default is 60, and it must be greater than zero.

Job Monitor Sleep Time

This field indicates the number of minutes the job monitor will pause between job status checks.

13.6 Creating Daylight Savings Rules

This section provides an overview of daylight savings rules and discusses how to:

- Add daylight savings rules.

- Add an additional daylight savings record to a daylight savings rule.

- Revise daylight savings rules.

13.6.1 Understanding Daylight Savings Rules

Daylight savings rules tell the system how each locale implements its daylight savings time. You associate a daylight savings rule to each user profile depending on the geographic location of the user. In addition, you can assign a daylight savings rule to a batch job that is scheduled to run in the Scheduler. The Scheduler uses these daylight savings rules, along with time zone information, to determine when batch jobs run on a particular server.

You can only associate one daylight savings rule with a user or scheduled job. However, in the Daylight Savings Time program (P00085), you can create multiple records for the same rule to account for variations in the daylight savings time from one year to the next. For example, if the daylight savings time period for a region is the same from 2008 through 2010, and then changes for 2011, you can create one daylight savings time rule that contains the following two records:

- DST Rule1–2008–Start and end dates for the daylight savings period

- DST Rule1–2011–Start and end dates for the daylight savings period

When the DST Rule1 in this example is associated to a user or scheduled job, JD Edwards EnterpriseOne uses the 2008 daylight savings record to determine the time until 2011, when it will automatically use the daylight savings time dates defined in the rule for 2011.

In the Southern Hemisphere, daylight saving time starts in one year and ends in another. When you set up a daylight savings time rule, the year that you enter for the daylight savings time rule must be the year in which the daylight savings time begins.

13.6.2 Prerequisites

The daylight savings time functionality that enables you to create multiple records for one rule is a JD Edwards EnterpriseOne Tools feature that is applicable to the JD Edwards EnterpriseOne Applications 8.12 and 9.0 releases. This feature comes automatically with the 9.0 release. However, to obtain this feature for the 8.12 release, you must download an electronic software update (ESU). On My Oracle Support, access SAR 8414822 to locate the ESU. In addition to the Daylight Savings Rule program changes, the ESU contains instructions on performing a table conversion to convert existing daylight savings rule data from the F00085 table to the F00085A.

13.6.3 Adding Daylight Savings Rules

From the Job Scheduler menu (GH9015), select Daylight Savings Rules (P00085).

1. On Work With Daylight Savings Rules form, click Add.

2. On the Add Daylight Savings Rule form, complete these fields:

- Rule Name
Enter a unique name for the daylight savings rule.

- Daylight Savings Effective Year
Enter the year in which the daylight savings rule begins.

- Description
Enter a description of the daylight savings rule.

3. In the Rule Type area, select one of these options to indicate the method that you want to use to determine the daylight savings rule dates:

- y Day of Week Instance
Select this option to enter start and stop dates for daylight savings on a certain day of the week for a certain month, such as the first Sunday of April to the first Sunday of October.

- By Day of the Month
Select this option to enter start and stop dates for daylights savings on a certain day of a certain month, such as April 3 to October 10.

4. Depending on the method that you chose, complete the remaining fields to specify when daylight savings starts and ends, and then click OK.

13.6.4 Adding an Additional Daylight Savings Record to a Daylight Savings Rule

To add another set of dates to accommodate for a change in the daylight savings period, you can add another record that contains new dates to an existing daylight savings rule.

From the Job Scheduler menu (GH9015), select Daylight Savings Rules (P00085).

1. On the Work With Daylight Savings Rules form, click Copy.

2. On the Add Daylight Savings Rule form, complete these fields:

Note:
Do not modify the Rule Name field because doing so will create a new rule that you will have to reassign to a user profile or scheduled job.

- Daylight Savings Effective Year.
Enter the year in which the daylight savings rule begins.

- Description.

3. In the Rule Type area, select one of these options to determine which method that you want to use to determine the daylight savings rule dates:

- By Day of Week Instance.

- By Day of Month.

4. Depending on the method that you chose, complete the remaining fields to specify when daylight savings starts and ends, and then click OK.

13.6.5 Revising Daylight Savings Rules

When you revise an existing daylight saving time rule, you cannot change the rule name or the year that the daylight savings rule takes affect.

From the Job Scheduler menu (GH9015), select Daylight Savings Rules (P00085).

1. On the Work With Daylight Savings Rule form, select the rule that you want to revise and then click Select.

2. In the Rule Type area, select the method that you want to use to determine a daylight savings rule:

- By Day of Week Instance.

- By Day of Month.

3. Depending on the method that you chose, complete the remaining fields to specify when daylight savings starts and ends, and then click OK.

13.7 Running Scheduler Reports

Run the Scheduled Jobs report when you want to review a summary of scheduled jobs and their statuses. You can use processing options to specify whether to run this report based on UCT or local time. You also can adjust for daylight savings time.

If you want to purge records from the F91320 table, run the Scheduler Purge program. You can run the purge program in proof mode or final mode.

See Also:

- "Batch Versions at Submission" in the JD Edwards EnterpriseOne Tools Development Tools: Report Printing Administration Technologies Guide.

13.7.1 Printing the Scheduled Jobs or Purge Scheduled Jobs Report

Access the Work With Batch Versions - Available Versions form.

1. Select a version in the detail area, and then click Select.

2. On the Version Prompting form, select one or both of the following options, and then click Submit:

- Data Selection

- Data Sequencing

3. On the Report Output Destination form, select one of these options, and then click OK:

- On Screen

- To Printer

14 Understanding Media Objects and Imaging

This chapter contains the following topics:

- Section 14.1, "Media Objects"

- Section 14.2, "Imaging"

- Section 14.3, "Media Object Queues"

- Section 14.4, "Media Object Tables"

- Section 14.5, "Language Considerations for Media Objects"

14.1 Media Objects

Media objects and imaging features in Oracle's JD Edwards EnterpriseOne enable you to attach useful information to an application, including information that might currently exist as a paper-based document. The media objects feature enables you to attach the information to applications, forms and rows, and Object Librarian objects. The imaging feature within media objects gives you flexibility to create a more efficient method of information storage.

This table describes the types of information that you can attach to a grid row or a form:

Media Object

Description

Text

Media objects provide a word processor that lets you create a text-only attachment. For example, you can use a text attachment to provide specific instructions for a form or additional information about a record.

Image

Images include files such as Windows bitmaps, Graphics Interchange Format (GIF) files, and JPEG files. These files might represent electronically created files, as well as scanned images of paper-based documents.

OLE

Media objects can be files that conform to the OLE standard. OLE enables you to create links between different programs. By using these links, you can create and edit an object from one program in a different program. JD Edwards EnterpriseOne provides the links that you need to attach OLE objects.
You attach OLE media objects at the base form level. Media objects attached at this level are attached to a form and not to any data that might appear in the form. You can attach media objects to a detail area or a form, but the files themselves exist in separate directories. The only file information that is included with the application to which the OLE object links is the path to the supporting file.

You can only use OLE objects that you properly register and install as OLE objects through JD Edwards EnterpriseOne.

Shortcuts

A shortcut is a link that opens JD Edwards EnterpriseOne application. Within media objects, you can only attach JD Edwards EnterpriseOne shortcuts; that is, you cannot attach Windows shortcuts to media objects.

Uniform Resource Locations (URL) and files

Media objects can be links to web page URLs or other related files. When a developer attaches a URL media object to a control object on a form, the web page appears as part of the form. When a user attaches a URL to a form or Object Librarian object, the media object acts as a link to the URL.

System administrators can also set up templates. A template might include attachments of its own, such as images and shortcuts. For example, you can create a letterhead and a standard form for a memo. You might create a shortcut in the template to provide access to an application that uses data specific to the information that you add to the template.

14.1.1 JD Edwards EnterpriseOne Text Items

Text items are items that you create using the JD Edwards EnterpriseOne media objects word processor. They do not require media object queues. The F00165 table contains both the associated key value of the data record to which the text media object is attached, and the text itself. Text items that originate from applications external to JD Edwards EnterpriseOne (for example, Microsoft Word or WordPad) must be stored as OLE objects.

14.2 Imaging

The imaging capabilities available in JD Edwards EnterpriseOne enable you to link to a third-party imaging product. Imaging systems enable you to scan and electronically store paper-based information. For example, this information might include documents such as sales orders, purchase orders, vendor invoices, and product schematics. JD Edwards EnterpriseOne imaging integration includes a media objects viewer and a third-party product that provides scanning and searching interfaces to enable you to find and display images. Implementation of imaging also provides a view of integrated images by using the viewer of the native imaging product.

When you use a third-party vendor, the F00165 table stores the reference to image attachments, but the third-party software controls the search and retrieval of images.

14.3 Media Object Queues

JD Edwards EnterpriseOne media object queues enable the storage location of media objects to be tracked by reference rather than physical network location, which simplifies the administration of media location. For example, the location for media objects on the server can change, and the change is reflected in only one place in JD Edwards EnterpriseOne.

You must define a media object queue to identify the pointer to the location where the actual image files or OLE objects reside. Media object queues provide the system administrator with the ability to easily manage the storage of media objects in the software. Within JD Edwards EnterpriseOne, you must set up media object queues to use images that are outside of the imaging product's domain (for example, scanned images). You can set up media object queues for these types of objects:

- Image objects (actual files).

- OLE objects (links to files).

- URLs (internet addresses).

14.3.1 Image Media Objects

Image media objects are individual files that are accessed and viewed by using a third-party imaging product. These objects are stored in locations defined with a name and a network-qualified path. For example, if all of the images for financial applications are stored in a directory on the network called \\server1\financials\images, an image media object queue could be defined as:

- Path: \\server1\financials\images

- Name: FIN_IMAGES.BMP

14.3.2 OLE Media Objects

OLE media objects are individual objects that are created and viewed by using an OLE-compliant application outside of JD Edwards EnterpriseOne. In JD Edwards EnterpriseOne, the OLE object attached to a row or form is actually a link to the OLE object that resides in a media object queue. The distinction between OLE objects and non-OLE objects is important because, other than graphics files, you cannot attach non-OLE objects from JD Edwards EnterpriseOne if they are not compliant. Examples of valid OLE objects are Microsoft Windows OLE-compliant applications such as Word, Excel, PowerPoint, and Visio. Other examples include sound or video files (.wav or .avi extensions).

14.3.3 URL Media Objects

URL media objects are internet addresses that point to web sites that are identified by industry-standard URLs. When defined in the media object table, these addresses can be connected to internet locations.

14.4 Media Object Tables

Media object queues typically represent network directory locations for JD Edwards EnterpriseOne media object files, such as OLE objects and images. The two media object tables are F98MOQUE and F98101.

The media object queues are stored in the Media Object Queues table, which, along with the Imaging Constants table, should be located in the system data source. The Media Object Queues table contains the associated key value of the data record to which the media object is attached, the image reference, and the OLE reference. The image reference and the OLE reference are queue names. The queue name is used to access the Media Object Queue table for the location of the OLE object or image.

Media object keys are stored in the F00165 table. Media object characterization properties are stored in the F00166 table. The F00167 table stores information indicating which categories the system activates for any given data structure.

14.5 Language Considerations for Media Objects

If you create a custom application that you want to enable for media object language handling, you must include a data item language preference (alias LNGP) in the generic text data structure that you create.

When you design an application, you can allow the end user to add separate and unique media objects to the same record or different records, based on the language chosen.

If language (LNGP) is not a database column, then you define the media object (GT) data structure to include language as part of the data structure. You place a data dictionary control (LNGP) on the application as a filter field, which should then be loaded with the system value for language. When you design the application this way, you attach two separate media objects, based on the language, to the same record.

If language (LNGP) is a database column, then you include LNGP (database) as a filter field, but you must add a separate record to the database table along with its media object attachment. The media object data structure still contains language as part of the key to retrieve the media object attachment. In both cases, the language filter fields (LNGP) must be loaded with the system value for language. LNGP must be built into the key and not associated with the LNGP column in the F00165 table.

For any database table that contains language as part of its key, you can attach media object functionality for records with different languages. For example, you can create one record for English and a copy of the record for French with unique media object attachments. For tables that do not include language as part of the key to that table, you can have media object languages.

15 Setting Up Media Objects and Imaging

This chapter contains the following topics:

- Section 15.1, "Understanding Media Object Processing"

- Section 15.2, "Setting Up Media Object Queues"

- Section 15.3, "Setting Up Imaging"

15.1 Understanding Media Object Processing

To use media objects, JD Edwards EnterpriseOne requires a set of event rules to process the media objects. This processing includes:

- Tracking where the media object files are stored.

- Tracking which media objects are attached to which objects (rows, forms, and reports).

- Indicating which objects have attachments.

- Creating or viewing attachments.

You can set up JD Edwards EnterpriseOne to use standard processing for media objects, which enables you to bypass all event rules that are required to implement media objects. All of the required information is gathered from a form in Form Design Aid and does not require you to define any event rules. Standard processing provides these benefits:

- Standardizes the usage of media objects across forms.

- For any detail area, places a paper clip button on the row header if a media object is defined for that row.

- For a form, places a button in the status bar if a media object is defined for the form.

- Enables you to attach documents to the form or to a row in the detail area.

- Enables you to double-click the paper clip in a row to view media objects for that row.

- Enables you to click the paper clip in the status bar to view media objects for the form.

If you choose not to use standard processing for a form, you can still develop a system for handling media objects by using existing event rules or event rules that you develop.

JD Edwards EnterpriseOne uses the F00165 table to store link records for media objects and imaging. You must define the media object data structure by using a unique key structure so that the F00165 table can store data correctly. The layout of this table is as follows:

GTxxx || F4211Keys || The media object text

Where:

GT (generic text) xxx is the naming convention used when defining a media object data structure.

F4211Keys is what the system uses to access the unique media object attachment for that particular record. The keys typically match what the unique key would be in the F4211 table for each detail line.

The media object text is the actual text attachment that stores information typed in by the user.

In addition to the media object categories provided by JD Edwards EnterpriseOne, you can define as many as 40 more. Users can associate these categories with a media object to group certain media objects and to enable other users to search for specific media objects. User defined categories reside in the F00166 table and are referenced using each object's unique key. The default titles for these categories are Category Codes 1-30, Dates 1-5, and Numeric 1-5.

15.1.1 Prerequisite

To enable users to see the media object paper clip column on a form, clear the Hide Row Headers option on the grid properties for the form.

15.1.2 Enabling JD Edwards EnterpriseOne to Use Media Objects

In JD Edwards EnterpriseOne OMW, access an application on which you want to enable media objects and open it in Form Design Aid.

1. In Form Design Aid, select Media Objects Setup from the Form menu.

2. On Media Objects Setup, select the Enable Automatic Media Object Functionality option.
Selecting this option enables imaging and activates the other fields on the form.

3. On Media Objects Setup, select one of these options:

- Media Objects Only
Select this option if you do not want to interface with third-party products that include imaging. If you choose this option, you will only be able to use media objects that are defined for and supported from within JD Edwards EnterpriseOne.

- Document Handling Only
Select this option if you are developing a form that is enabled for media objects using functionality in event rules and you want to bypass standard processing.

- Media Objects & Document Handling
Select this option if you want to enable standard processing later. You must delete all of the event rules for media objects when you choose this option.

4. Click Edit mode or Display mode.
Edit mode allows the user to make changes; display mode is read-only.

5. Click Define Form Key.
The System Functions form appears. This form is identical to the parameter definition form used to define system functions in event rules, except that it includes only the Media Object header.

6. On the Function Selection tab, double-click the Media Object Structures folder.
A list of all currently defined data structures for Media Objects appears.

7. Select the appropriate structure and define it on the Parameter Mapping tab.

15.1.3 Adding a Language-Specific Media Object Attachment

Open the application to which you want to add a language-specific media object attachment.

1. On the application that you want to use, type a language in the filter field.

2. Click Add.

3. Add multiple records if you want the attachment for multiple languages or base.

15.2 Setting Up Media Object Queues

This section discusses how to:

- Add a media object queue.

- Define the location of a media object queue.

- Delete a media object queue.

15.2.1 Forms Used to Set Up Media Object Queues

Form Name

FormID

Navigation

Usage

Work With Media Object Queues

W98MOQUEA

System Administration Tools (GH9011), Media Object Administration, Media Object Queues (P98MOQUE)

Add a media object queue. Locate existing queues and delete queues.

Media Object Queue Revisions

W98MOQUEB

On the Work With Media Object Queues form, click Add.

Add information for a new media object queue. Define the location of a media object queue.

15.2.2 Adding a Media Object Queue

Access the Work With Media Object Queues form.

1. Click Add.

2. On the Media Object Queue Revisions form, in the Queue Name field, define the media object queue name where images may be found. The queue name is a symbolic reference only. The media object queue name is one-half of a properly defined media object queue. The other half is the media object path. complete these fields:

- Queue Name

- Queue Path On-Line

- Queue Path Off-line

- On-Line Access Type

- Off-Line Access Type

3. In the Queue Path On-Line field, enter a path that points to the location of OLE objects, images, or URLs. The queue path is the second half of a properly defined queue for a media object. The first half is the name of the media object. A valid queue path for a network location might be \\server1\share3\images\financial. To set the queue for a CD ROM, use cd: in the pathname; the system automatically substitutes the appropriate drive letter when it resolves the path.

4. In the Queue Path Off-line field, enter a local path that points to the location of OLE objects, images, or URLs. The queue path is the second half of a properly defined queue for a media object. The first half is the name of the media object. A valid queue path when working off-line might be d:\data\media\images.

15.2.3 Defining the Location of a Media Object Queue

Access the Work With Media Object Queues form.

1. If an OLE queue does not exist, click Add.

2. On the Media Objects Queue Revisions form, complete these fields:

- Queue Name

- Queue Path On-Line

- Queue Path Off-line

- Type

- On-Line Access Type

- Off-Line Access Type

3. Click OK.

4. If you want to change an existing media object queue, on the Work With Media Object Queues form, click Find to display a list of queue names and their paths.

5. Select the queue name that you want to modify and click Select.

6. On the Media Object Queue Revisions form, change the information in the Queue Path On-Line field to reflect the new location, and then click OK.

15.2.4 Deleting a Media Object Queue

Access the Work With Media Object Queues form.

1. Click Find.

2. Select the queue name that you want to delete.

3. From the Form menu, select Delete.
Deleting a media object queue deletes only the definition of the queue, not the associated path or objects themselves.

15.3 Setting Up Imaging

This section contains an overview of imaging and the flow for imaging systems and discusses how to enable imaging in media objects.

15.3.1 Understanding Imaging

One way to attach images to JD Edwards EnterpriseOne forms and grid rows is to use the Image function of the Media Objects feature; however, this solution is not designed for use with sophisticated document handling systems. See My Oracle Support for a complete list of imaging vendors partnered with JD Edwards EnterpriseOne.

The software uses the OLE client/server model to interface with third-party document handling systems, including the OLE client interface and the OLE server. For the currently supported imaging systems, JD Edwards EnterpriseOne meets these minimum design goal tasks:

- Search
The search mechanism locates a document stored in the indexing system of a document handling system. The search mechanism navigates the storage structures of the document handling system so that the user can find a particular document or set of documents easily.

- Link
Upon a successful search operation, the link mechanism returns the unique document identifier to JD Edwards EnterpriseOne. This identifier is stored with the transaction.

- View
The view mechanism passes the unique document identifier to a document viewing mechanism so that the user can view the document.

Customers with requirements for third-party imaging systems other than those that the software currently supports can design custom OLE automation servers for interfacing purposes. The OLE server can be written in any OLE-compliant language. JD Edwards EnterpriseOne has a published set of APIs to enable you to develop compatible middleware applications. The published APIs are described in a Windows help file that is installed with the software.

15.3.1.1 Understanding Flow for Imaging Systems

You can use imaging with a document handling system. The imaging system enables you to automatically scan and catalog documents. The system indexes the images so that you can recall them, based on certain sets of criteria. For example, you might index images according to type, department, and date. You can recall, view, and analyze an image at any given time. For example, in a transaction entry scenario, you might scan a paper-based file when the document enters the mailroom so that a data entry clerk can retrieve the image to use as a source document.

JD Edwards EnterpriseOne can retrieve and view documents based on selection criteria that are defined by the user. A linking system associates the JD Edwards EnterpriseOne transaction to the document for later retrieval and reference. You can attach a transaction identifier with the scanned image in the document handling system to enable a user to access an application directly from the image.

You set up imaging by enabling the imaging at the system level. For an imaging system to be enabled, it must have a registration record in the F98101 table.

This illustration explains how the software supports third-party imaging products through a middleware OLE server layer. Customers also can create their own OLE servers to support additional imaging systems:

Figure 15-1 JD Edwards EnterpriseOne imaging architecture

This diagram is a typical imaging scenario:

Figure 15-2 Imaging process flow

15.3.2 Forms Used to Set Up Imaging

Form Name

FormID

Navigation

Usage

Work With Media Object Queues

W98MOQUEA

System Administration Tools (GH9011), Media Object Administration, Media Object Queues (P98MOQUE).

Set up imaging.

Imaging Constants Revisions

W98101A

On the Work With Media Object Queues form, select Imaging from the Form menu.

Enter information about the imaging system and enable the imaging system.

15.3.3 Enabling Imaging in Media Objects

Access the Work With Media Object Queues.

1. From the Form menu, select Imaging.

2. On the Imaging Constants Revisions form, in the Imaging System Vendor field, enter the name of the imaging system vendor that you are using on the system.

3. In the Imaging Vendor Description field, enter a description of the imaging system vendor.

4. If the image type is an OLE, in the Image Program ID/DLL field, enter the program ID that uniquely identifies the imaging system in the system registry. If the image type is a DLL, enter the imaging system DLL name.

5. Select the Imaging Active option to indicate that an imaging system is currently active for the system.

6. Select the OLE option to indicate the type of interface used by the imaging system.

15.4 Setting up the HTML Editor

JD Edwards EnterpriseOne supports the media object ActiveX rich text editor only in Internet Explorer. JD Edwards EnterpriseOne 8.98.3 provides an alternative to the media object ActiveX rich text editor. The HTML editor creates browser independency and users will be able to add, view, modify, and delete the media object rich text attachments using the HTML editor in Internet Explorer and Fire Fox.

Note:
The value of the attachment is saved in XHTML format. Once the data is converted and saved to the database in XHTML it cannot be returned to the ActiveX RTF format.

JD Edwards EnterpriseOne 8.98.3 default media object editor is the ActiveX rich text editor. The ActiveX rich text editor can be replaced with the HTML rich text editor through Server Manager.

To configure JD Edwards EnterpriseOne 8.98.3 to utilize the HTML editor

Navigate to the HTML server in Server Manager

1. Access the Web Runtime properties.

Figure 15-3 Web Runtime Form

2. Scroll down and remove the check mark from Use ActiveX Controls.

Figure 15-4 ActiveX Controls Option

This action modifies the property SupportActiveXIE=TRUE in the jas.ini under [OWWEB] section on the HTML server to FALSE. Users are able to work with only one type of editor at a time either the ActiveX or HTML rich text editor.

This ini setting specifies whether JD Edwards supplied ActiveX controls are supported within the IE browser. Since this is an ini setting the behavior will be for all users of the HTML server.

When this ini setting is set to false it will override the settings in the users IE browser and will not load or run JD Edwards ActiveX controls. The user will not see prompting for installing of the JD Edwards ActiveX controls.

When this ini setting is set to true or is not found in the jas.ini, the application will try to load the ActiveX control. If the control is not loaded, then a flag will be set for the user session that ActiveX controls are not supported and all JD Edwards ActiveX controls will be unavailable for that user session. This will occur for the user that has disabled ActiveX control installation and running in the IE browser. For the first ActiveX control within a user session that we attempt to load and it fails, the user will see the download prompt. If they have previously allowed for all downloads from Oracle, by checking the checkbox on the options on the download prompt, they will not see the prompt. After the first control load fails we will no longer prompt the user for installing the ActiveX control. If the load of the ActiveX control does not fail, then the user will experience the same behavior as before this change. All JD Edwards ActiveX controls will be available for the user.

16 Administering Text Search Indexes

This chapter contains the following topics:

- Section 16.1, "Understanding Text Search Indexes"

- Section 16.2, "Defining Text Search Indexes"

- Section 16.3, "Building Text Search Indexes"

- Section 16.4, "Defining Text Search Properties"

Note:
With JD Edwards EnterpriseOne Tools Release 8.98.4, you have the option to use Oracle Secure Enterprise Search instead of the default text search tool. For information about Oracle Secure Enterprise Search, see Understanding Text Search with Secure Enterprise Search.

16.1 Understanding Text Search Indexes

JD Edwards EnterpriseOne contains a text search engine that takes information from the tables and associated media objects and builds a text search index. When a text search is initiated, it goes through the text search index and returns database records that match the search criteria. In JD Edwards EnterpriseOne, the text search engine uses a business view-data source pair to retrieve table data.

Text search indexes exist as folders on a file system, so text search indexes must be accessible using a path name to the enterprise server. Administrators must designate the locations of these folders by specifying the base folder in Text Search Properties.

16.2 Defining Text Search Indexes

This section provides an overview of text search indexes and discusses how to:

- Designate data sources for a business view.

- Define media objects for a text search index.

- Define languages for a text search index.

16.2.1 Understanding Text Search Indexes

To create a text search index, define the following items:

- Business view
To be able to perform a text search over a business view, the developer must select the Text Search option on the business view's properties form in JD Edwards EnterpriseOne OMW. Otherwise, the business view is not available for a text search.

See JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

- Data source
The data source tells the text search engine where to search for the data defined in the business view. If you do not select a data source, the text search engine searches the default data source defined in the OCM mapping.

- Media objects
To associate media objects with a business view-data source pair, use the Text Search Index Media Object Queue Revisions form. If no queues are specified, then all queues will be scanned.

- Languages
To build the index for any languages other than your base language, enter the language on the Text Search Index Language Revisions form.

16.2.2 Forms Used to Define Text Search Indexes

Form Name

FormID

Navigation

Usage

Work With Text Search Indices

W95800B

ext Search Administration menu (GH9077), Text Search Indices.

View and select text search business views with the associated data sources. Build, clear, and optimize text search indexes.

Text Search Index Revisions

W95800A

On the Work with Text Search Indices form, select a business view.

Edit data sources for each business view.

Text Search Index Media Object Queue

W95800E

On the Work with Text Search Indices form, highlight a data source, then select Media Object Queues from the Row menu.

Edit text search indexes for media object queues

Text Search Index Language Revisions

W95800F

On the Work with Text Search Indices form, highlight a data source, then select Languages from the Row menu.

Edit text search indexes for language.

16.2.3 Designating Data Sources for a Business View

Access the Text Search Index Revisions form.

Text Search Business View

Displays the business view selected using the Work with Text Search Indices form.

Text Search Data Source

The text search data source defined for the Text Search business view.

16.2.4 Defining Media Objects for a Text Search Index

Access the Text Search Index Media Object Queue Revisions form.

Text Search Business View

The business view selected using the Work with Text Search Indices form.

Text Search Data Source

The data source selected using the Work with Text Search Indices form.

Media Object Queue Name

The name of the media object queue from the table F98MOQUE.

16.2.5 Defining Languages for a Text Search Index

Access the Text Search Index Language Revisions form.

Text Search Business View

The business view selected using the Work with Text Search Indices form.

Text Search Data Source

The data source selected using the Work with Text Search Indices form.

Language

The user defined code indicating the language.

Description

The name of the language.

16.3 Building Text Search Indexes

There are four types of builds you can perform:

- Full

- Incremental

- Optimize

- Clear

A full build indexes all the data referenced by a business view and creates a new text search index or replaces an existing text search index. You should schedule full builds regularly, depending on the frequency with which the data changes.

Note:
If a user adds a new media object to a specific record in a business view and as a result, exceeds the media object limit defined in the previous full build, the change will only take affect after the next full build is complete. In other words, the incremental build will not add this change in the text search index for this business view.

Some applications automatically perform incremental builds. An incremental build takes data entered since the last full build and adds it to the end of the text search index. This makes the data available for searching, but each time an incremental build runs, it decreases the efficiency of the text search index. To optimize the efficiency of the text search index, you need to run an optimize build.

An optimize build takes the data entered since the last full build and re-indexes it. This increases text search efficiency and ensures that text searches cover recently added data. An optimize build is not as resource-intensive as a full build, so you can schedule it more frequently.

A clear build removes all data from the text search index. Under normal circumstances you would not clear a text search index, except to free file system storage. Before you can search again, you need to do a full build. However, if you do a search after a clear build, there is no data in the index to return.

You can perform builds manually or schedule them to occur automatically. The manual Build options are off the Report and Row menus. Schedule builds using the JD Edwards EnterpriseOne Scheduler by running the following UBEs:

- R958001 — XJE001 (Full Build).

- R958001 — XJDE002 (Optimize).

- R958001 — XJDE003 (Clear).

16.4 Defining Text Search Properties

This section provides an overview of text search properties and discusses how to:

- Add a new text search business view-data source pair.

- Define stop words.

- Define synonyms.

- Define topics.

16.4.1 Understanding Text Search Properties

There are three properties you can define for a text search:

- Stop Words
Stop words are words that are too common to search for. For example, if every service ticket uses the word "broken", you would not search on "broken". Similarly, if you only sold automobiles, searching sales receipts for the words "automobile" or "car" would be useless. Instead, you might search for specific makes and models of automobiles. By making "car" and "automobile" stop words, if you entered the search "1998 Ford Mustang Car", the system would only search for "1998 Ford Mustang", taking out the common word, "car". Stop words reduce the required file system storage for text search indexes and improve search performance.

- Synonyms
Synonyms are words that mean the same thing. For example, in a motorcycle dealership, the words "bike", "chopper", and "hog" all refer to a motorcycle. Motorcycle is the thesaurus word, that is the word all the synonyms point to. "Bike", "chopper", and "hog" are the synonyms. When a user enters the search word "chopper", all records containing "motorcycle", and any of its synonyms are returned.

The text search engine has predefined common stop words and synonyms for each language supported. You only need to define those that are specific to your business.

You can define synonyms and stop words globally or for specific business view-data source pairs.

16.4.2 Forms Used to Define Text Search Properties

Form Name

FormID

Navigation

Usage

Work with Text Search Properties

W95820A

Text Search Administration menu (GH9077), Text Search Properties.

View, add, and select text search business views-data source pairs and define maximum results and base folders.

Text Search Properties Revisions

W95820B

On the Work with Text Search Properties form, click Add.

Add a new text search business view-data source pair and define maximum results and base folder.

Work with Text Search Stop Words

W95820E

On the Work with Text Search Properties form, select Stop Words from the Row or Form menu.

When entered from the Row menu, view the stop words defined for a text search business view-data source pair or global stop words. When entered from the Form menu, view and edit stop words already set up in the system.

Work with Text Search Synonyms

W95820C

On the Work with Text Search Properties form, select Synonyms from the Form or Row menu.

When entered from the Row menu, view the synonyms defined for a text search business view-data source pair, or global synonyms.
When entered from the Form menu, view and edit synonyms already set up in the system.

Work with Text Search Topics

W95820I

On the Work with Text Search Properties form, select Topics from the Form or Row menu.

When entered from the Row menu, view the topics defined for a text search business view-data source pair, or global topics.
When entered from the Form menu, view and edit topics already set up in the system.

16.4.3 Adding a New Text Search Business View-Data Source Pair

Access the Text Search Properties Revisions form.

Text Search Business View

The name of the business view of the business view-data source pair from which to build the text search indexes.

Data Source

The name of the data source of the business view-data source pair from with to build the text search indexes.

Base Folder

The folder to contain the text search index. This folder must be accessible to the enterprise server.

Max Results

The maximum number of matches to be returned from this text search index.

16.4.4 Defining Stop Words

Access the Work with Text Search Stop Words form.

Global

This option defines stop words for all business view-data source pairs.

Business View/Data Source Specific

This option defines stop words for only one business view-data source pair.

Text Search Business View

The business view used to build the text search index.

Text Search Data Source

The database used to build the text search index.

Language

The language defined for the text search index.

16.4.5 Defining Synonyms

Access the Work with Text Search Synonyms form.

Global

This option defines synonyms for all business view-data source pairs.

Business View/Data Source Specific

This option defines synonyms for only one business view-data source pair.

Text Search Business View

The business view used to build the text search index.

Text Search Data Source

The database used to build the text search index.

Language

The language defined for the text search index.

16.4.6 Defining Topics

Access the Work with Text Search Topics form.

Global

This option defines topics for all business view-data source pairs.

Business View/Data Source Specific

This option defines topics for only one business view-data source pair.

Text Search Business View

The business view used to build the text search index.

Data Source

The database used to build the text search index.

Language

The language defined for the text search index.

16.5 Understanding Text Search with Secure Enterprise Search

This section provides an overview of Secure Enterprise Search (SES) based text search index in EnterpriseOne:

- Configuring SES for Text Search

- Understanding Text Search Indexes

- Understanding Text Search Properties

Secure Enterprise Search is a standalone, self-contained server for search; it operates as a black box that indexes information from the crawler and serves up the results. It comes with its own user interface and administration; it does not, for example, need you to program using SQL or administer as a DBA.

16.5.1 Configuring SES for Text Search

This section provides an overview of SES text search and discusses:

Component

Description

Crawler

The SES Crawler is a Java process activated by your Oracle server according to a set schedule. When activated, the crawler spawns a configurable number of processor threads that fetch documents from various data sources. The crawler maps link relationships and analyzes them to avoid going in circles and taking wrong turns. Whenever the crawler encounters embedded, non-HTML documents during the crawling it uses filters to automatically detect the document type and to filter and index the document.

Database

An Oracle11g database contains the SES-repository, which stores information about the repositories indexed by SES and the search engine index (information collected by the crawler, filtered and indexed by Oracle11g Text).

Search UI & API

SES provides an out-of-the-box user interface to the Server. It also provides a web services API for building custom applications for querying indexed data, and contains interfaces for Basic Search Form, Advanced Search Form, Query Result Display, URL registration, authentication and authorization, and so on.

Administration Tool and Interface

The SES administration tool is a browser-based application that you use to configure and schedule the crawler, configure the server, run several reporting features, and other similar tasks.

Federator

Via the Suggested Content feature, SES also provides the ability to federate queries to other engines that implement their own search mail servers, Internet search engines, and specific applications. Additionally, SES provides the ability to federate queries to other SES instances. These results can be combined and displayed together along with those results served off the internal index of SES Server.

Figure 16-1 Oracle Enterprise Search

16.5.1.1 Prerequisites

- SES is installed and running

- Create RSS Crawler Source

To create the RSS Crawler Source; install the RSS Crawler plugin as "RSSCrawler".

1. Login at the SES Admin screen.

2. Go to Global Settings tab.

3. Click Source Types.

4. Click the Create button.

5. Specify the following details:

Field

Description

Name

RSSCrawler

Description

Crawler plug-in for RSS connector

Plug-in Manager Java Class Name

oracle.search.plugin.rss.RSSCrawlerManager

Plug-in JAR file name

oracleapplications/rsscrawler.jar

6. Click next.

7. Click Finish.

16.5.1.2 Configuring Enterprise Server for SES

To configure the Enterprise Server for SES create an FTP user with read-only permission to the FTP folder. This is necessary because if you give full permission to the FTP user, the SES crawler will delete the actual XML feed after successfully crawling/indexing. The JDE user(i.e user account used for starting the kernels) should have full permission (r+w) to the FTP folder.

16.5.1.3 JAR files required for SES Admin Api's

javax.activation_1.1.jar
javax.xml.soap_1.3.1.0.jar
javax.xml.stream_1.1.1.0.jar
javax.jws_2.0.jar
glassfish.jaxb.xjc_1.2.0.0_2-1-7.jar
javax.xml.bind_2.1.1.jar
oracle.webservices.standalone.client.jar
search_adminapi_wsclient.jar (patched version)

Note:
There is a limitation on 1.5 SES Admin JAR's to be in a specific order in CLASSPATH to work on certain JVM's especially Solaris.On Windows and Linux we didn't see any issues.To fix this issue below JAR's should be added to the JDE.INI's [JDE_CG]CLASSPATH settings in the same order as listed below (give these entries in single)

Example:

[JDE_CG]
CLASSPATH=/jdedwards/e900/system/classes/javax.activation_1.1.jar:/jdedwards/e900/system/classes/javax.xml.soap_1.3.1.0.jar:/jdedwards/e900/system/classes/javax.xml.stream_1.1.1.0.jar:/jdedwards/e900/system/classes/javax.jws_2.0.jar:/jdedwards/e900/system/classes/glassfish.jaxb.xjc_1.2.0.0_2-1-7.jar:/jdedwards/e900/system/classes/javax.xml.bind_2.1.1.jar:/jdedwards/e900/system/classes/oracle.webservices.standalone.client.jar:/jdedwards/e900/system/classes/search_adminapi_wsclient.jar

16.5.1.4 JDE.INI settings for Text Search Kernel (Enterprise Server)

[JDENET]
...
...
maxKernelRanges=34
....
....
[JDENET_KERNEL_DEF34]
krnlName=TEXTSEARCH KERNEL
dispatchDLLName=searchkrnl.dll
dispatchDLLFunction=_JDEK_DispatchTextSearchMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=1

16.5.1.5 JDE.INI Settings for Media Object Queue for IBM i Enterprise Server Only

Below setting is required on IBM i Enterprise server if Media Object Queue location on Deployment server is not shared and requires an FTP access. By default UseFTPMOQUE is set to FALSE meaning the MOQUEUE folder is shared and doesn't require FTP.

[TEXTSEARCH]
UseFTPMOQUE=TRUE
FTPUser=anonymous
FTPPwd=anonymous

16.5.2 Understanding Text Search Indexes

This section provides an overview of text search indexes and discusses how to:

- Designate data sources for a business view.

- Define media objects for a text search index.

- Define languages for a text search index.

- Building Text Search Indexes

To create a text search index, define the following items:

- Business view
To be able to perform a text search over a business view, the developer must select the Text Search option on the business view's properties form in JD Edwards EnterpriseOne OMW. Otherwise, the business view is not available for a text search.

See JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

- Data source
The data source tells the text search engine where to search for the data defined in the business view. If you do not select a data source, the text search engine searches the default data source defined in the OCM mapping.

- Media objects
To associate media objects with a business view-data source pair, use the Text Search Index Media Object Queue Revisions form. If no queues are specified, then all queues will be scanned.

- Languages
To build the index for any language, enter the language on the Text Search Index Language Revisions form.

Forms Used to Define Text Search Indexes

Application: P95800A

Form Name

Form ID

Navigation

Usage

Work With Text Search Indices

W95800AB

Text Search Administration menu (GH9077), Text Search Indices.Fast Path P95800A

View and select text search business views with the associated data sources. Build and clear text search indexes.

Text Search Index Revisions

W95800AA

On the Work with Text Search Indices form, select a business view.

Edit data sources for each business view.

Text Search Index Media Object Queue Revisions

W95800AC

On the Work with Text Search Indices form, highlight a data source, then select Media Object Queues from the Row menu.

Edit text search indexes for media object queues

Text Search Index Language Revisions

W95800AD

On the Work with Text Search Indices form, highlight a data source, then select Languages from the Row menu.

Edit text search indexes for language.

16.5.2.1 Designating Data Sources for a Business View

Access the Text Search Index Revisions form.

Text Search Business View Displays the business view selected using the Work with Text Search Indices form.

Text Search Data Source The text search data source defined for the Text Search business view.

16.5.2.2 Defining Media Objects for a Text Search Index

Access the Text Search Index Media Object Queue Revisions form.

Text Search Business View The business view selected using the Work with Text Search Indices form.

Text Search Data Source The data source selected using the Work with Text Search Indices form.

Media Object Queue Name The name of the media object queue from the table F98MOQUE.

16.5.2.3 Defining Languages for a Text Search Index

Access the Text Search Index Language Revisions form.

Text Search Business View The business view selected using the Work with Text Search Indices form.

Text Search Data Source The data source selected using the Work with Text Search Indices form.

Language The user defined code indicating the language.

Description The name of the language.

16.5.2.4 Building Text Search Indexes

The three types of builds you can perform are:

- Full

- Incremental

- Clear

Full

A full build indexes all the data referenced by a business view and creates a new text search index or replaces an existing text search index. You should schedule full builds regularly, depending on the frequency with which the data changes.

Note:
If a user adds a new media object to a specific record in a business view and as a result, exceeds the media object limit defined in the previous full build, the change will only take affect after the next full build is complete. In other words, the incremental build will not add this change in the text search index for this business view.

Incremental

Some applications automatically perform incremental builds. An incremental build takes data entered since the last full build and adds it to the end of the text search index. This makes the data available for searching.

See "Understanding Text Search Controls" in the JD Edwards EnterpriseOne Tools Development Tools: Form Design Aid Guide

Clear

A clear build removes all data from the text search index. Under normal circumstances you would not clear a text search index, except to free file system storage. Before you can search again, you will need to do a full build. If you do a search after a clear build, there is no data in the index to return.

You can perform builds manually or schedule them to occur automatically. The manual Build options are on the Report and Row menus.

The Full Build and clear build can be called either interactively (via Row->Build) or as a batch (via Report->Build).

The build can also be scheduled using the JD Edwards EnterpriseOne Scheduler by running the following UBEs:

- R958001A - XJDE0001 (SES Text Search Build).

- R958001A - XJDE0003 (SES clear build).

Note:
Using interactive applications to run the full build is not recommended for views having a large number of records. This is because JDENETTimeout of the FAT/Enterprise server and the EnterpriseServerTimeout of the JAS server have to be increased so that requests sent to Enterprise Server or the requests sent to Text Search Kernel from Call Object kernel will not timeout.
The numbers to which these settings have to be increased vary from view to view and changing these settings will have an impact on other functionality as well.

When building views with a large number of records, it is recommended to use the Report R958001A (i.e. by creating version for the desired view).

16.5.3 Understanding Text Search Properties

This section provides an overview of the text search properties and defines:

- Global properties

- Business View/Data Source Specific

16.5.3.1 Forms Used to Define Text Search Properties

Application: P95820A

Form Name

Form ID

Navigation

Usage

Work with Text Search Properties

W95820AA

Fast path the application P95820A

View, add, and select text search business views-data source pairs and define maximum results and base folders.

Text Search Properties Revisions

W95820AB

On the Work with Text Search Properties form, Select BusinessView/ Datasource Specific and click Add.

Add a new text search business view-data source pair and define maximum Text search results.

Text Search Engine Selection

W95820B

On the Work with Text Search Properties form, Select Global and click add/ select existing record

Select /change the text search Engine

16.5.3.2 Global Properties

As part of Tools release 8.98.4.0, both Oracle SES and Verity are supported. Only one text search engine may be used at a time. The SES Text Search Properties (P95820A) application is used to define the active text search engine

To define the active text search engine:

1. Access the 'Text Search Engine Selection' form.

2. Select the text search engine between Verity and Oracle SES.

If Verity Search Engine is selected, Server properties will be disabled and Verity is used as the active text Search engine.

Figure 16-2 Text Search Engine Selection

If Oracle SES Engine is selected, server properties will be enabled to enter the required details.

Figure 16-3 Text Search Engine Selection

Note:
If the SES Index Build Definition (P95800A) and SES Text Search Properties (P95820A) applications are not present the correct ESUs have not been applied and Verity is assumed to be the default Text Search Engine. If a Text Search Engine is not explicitly selected Verity is the default text search engine.

Oracle SES Engine server properties fields:

Field

Description

SES Server URL

Valid SES server's admin url http://mySESServer:7777/search/api/admin/AdminService

SES Server User ID

'eqsys' is the standard user id

SES Server password:

Password for the eqsys userid

Validate SES

To verify the SES server URL, eqsys user id and password details given in the form.

FTP Server URL

Valid ftp URL pointing to the RSS feeds directory

FTP Server User ID

FTP user id

FTP Server password

FTP password

Validate FTP

To verify the userID, password and the server information given in the FTP server URL.

Base folder

Local directory on the enterprise server.RSS feeds will be generated in this location.

Text Search Max Results

Default max results for any Text search view. 300 is the default value.

16.5.3.3 Business View/Data Source Specific Properties

There are specific properties applicable to each Business view and Data Source pair.

To add a new text search business view and data source pair access the Text Search Properties Revisions form.

Figure 16-4 Text Search Properties Revisions Form

Field

Description

Text Search Business View

The name of the business view of the business view-data source pair from which to build the text search indexes.

Text Search Data Source

The name of the data source of the business view-data source pair to build the text search indexes.

Text Search Max Results

The maximum number of matches to be returned from this text search index.

16.5.3.4 Troubleshooting

If an error occurs during indexing, check the following:

1. Call object kernel that processed the Business Function.

2. Text Search kernel log on the Enterprise Server.

3. Access the SES admin page -> Schedules -> Identify the schedule name based on the view, data source and language you are indexing. Open the log file and look for errors/exceptions.

The SES_CLEANUP environment variable can be set to FALSE to look at the RSS feeds generated as part of the indexing. Ex: - SES_CLEANUP=FALSE. The default value is TRUE which means the RSS feed will be deleted automatically after an index build operation.

Web client error:

JAS_MSG346: JAS database failure: [TEXT_SEARCH_ERROR] A text search error has occurred: http.proxyPort must be set to a integer value. Value set is &apos;&apos; [java.lang.IllegalArgumentException]

Access the FAT clients JDE.ini settings and modify the following:

[LOCALWEB]
httpProxySet=true

# HTTP Proxy server host
httpProxyHost=< address of proxy server >
#Ex:-httpProxyHost=www-proxy.us.oracle.com

# HTTP Proxy server port
httpProxyPort= port of proxy server
#Ex:-httpProxyPort=80

17 Setting Up Application Failure Recovery

This chapter contains the following topics:

- Section 17.1, "Understanding Application Failure Recovery"

- Section 17.2, "Enabling/Disabling Application Failure Recovery"

- Section 17.3, "Saving Application Data"

17.1 Understanding Application Failure Recovery

JD Edwards EnterpriseOne web client users may need to recover data from failed applications due to:

- Transaction failures

- Session time outs

- User Voluntary Save

The Application Failure Recovery program (P95400) enables users to access data from any failed transaction in which they are involved. Using P95400, users can review data from failed transactions.

Additional links may be added to the JD Edwards EnterpriseOne Menu or the Application Recovery Form for application failure recovery if data is saved during the transaction. The system adds a link named "Failure Recovery Data" to the JD Edwards Menu if there is a transactional failure saved for the user. The system adds a link named "Application Saved Data" to the JD Edwards EnterpriseOne Menu if there is no transactional failure, but there are other saved data due to voluntary save or time out.

In addition, on the Application Recovery Form, the Export option is enabled so that a user can export the saved records.

See Also:

- "Recovering Data" in the JD Edwards EnterpriseOne Tools Foundation Guide.

17.1.1 Prerequisite

Use the Security Workbench program (P00950) to secure P95410 to system administrators only.

See "Managing Application Security" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

17.2 Enabling/Disabling Application Failure Recovery

Application Failure Recovery is enabled out of the box with the jas.ini setting set to ALL, which is the default setting. To disable Application Failure Recovery set the jas.ini to NONE. The Application Recovery setting is found in the [OMWEB} — Web Runtime section of the jas.ini.

See the Server Manager Guide on My Oracle Support.

17.3 Saving Application Data

Saving Application Data needs to be set up for when sessions time out. Access the Work with Application Failure Records form. In the JD Edwards EnterpriseOne web client, enter P95400 in the Fast Path.

As an application failure administrator, you can allow users to recover failed application data for specific applications. The P95400 application enables you to grant this access to a user, a role, or all users.

1. From the Form menu, select Time Out Subscriptions.

2. On the Work with Time Out Subscriptions form, click Add.

3. On the Add Time Out Subscription form, in the User field, enter the user ID or role that you want the system to save when the session times out. Enter *Default to allow access to all users.

4. In the Application Name field, enter the application for which the user or role can save data, and then click OK.

18 Using the Universal Table Browser

This chapter contains the following topics:

- Section 18.1, "Understanding the Universal Table Browser"

- Section 18.2, "Working with the Universal Table Browser"

18.1 Understanding the Universal Table Browser

To view the data in tables in different databases, use the Universal Table Browser. This tool lets you verify the existence of data in a table, as well as determine the structure of the table. The Universal Table Browser uses JDEBASE APIs to retrieve data from the database, making it independent of the database that you access.

You can determine whether the data that the Universal Table Browser displays is formatted or non-formatted.

For formatted data, the Universal Table Browser displays the data according to the specifications of the JD Edwards EnterpriseOne data dictionary item. For example, assume that the data item PROC is a numeric field of size 15, with four display decimals. For a value of 56.2185, the Universal Table Browser displays a formatted value (using the data dictionary editing) as 56.2185, even though this value is stored in the database as 562185.

For non-formatted data, the Universal Table Browser displays the data according to the specification of the database and the data item type (such as numeric) from which the data came. For example, assume that the table data item PROC is a numeric field stored in the database. Depending on the database, this field might have a default value size of 32, with a precision of 15 being a numeric data type. Because JD Edwards EnterpriseOne does not store the decimals in the database, a value 56.2185 is stored and displayed in the database as 562185.000000000000000.

The tables that display in the Universal Table Browser contain the query by example (QBE) feature, which functions as it does in any other JD Edwards EnterpriseOne application. For example, you can enter >50 in the ABAN8 column QBE to display records with an address book number that is greater than 50. You can enter F* in the ABALPH column QBE to display records with an alpha name that begins with the letter F.

In addition, the column sequence and column width features function as in any other JD Edwards EnterpriseOne application. You can rearrange the columns. For example, you might want to move a column that you use often from the end to the beginning, or move a column next to an associated column. You also can size columns.

18.2 Working with the Universal Table Browser

This section discusses how to:

- View the data in tables.

- View column properties in a table.

18.2.1 Viewing the Data in Tables

Access the Universal Table Browser. In Solution Explorer, select the Cross Application Development Tools (GH902) menu, Object Management, Universal Table Browser.

Note:
All column and row security that you set up using Security Workbench applies to the Universal Table Browser.

1. On Universal Table Browser, select Open Table from the File menu.

2. On the Table and Data Source Selection form, in the Table field, click the search button to select a table.

3. In the Data Source field, click the search button to select a valid data source in which the table resides. This default value is obtained from the Object Configuration Manager (OCM) settings in the current environment.

4. Select the Format Data option if you want the program to display formatted data.

18.2.2 Viewing Column Properties in a Table

Access the Universal Table Browser. In Solution Explorer, select the Cross Application Development Tools (GH902) menu, Universal Table Browser.

1. On Universal Table Browser, view a table as described in the previous task.

2. Right-click a column and select Column Properties.
If you are viewing a formatted table, the data dictionary properties are displayed in the upper-right portion of the Column Properties form. If you are viewing an unformatted table, the data dictionary properties are not displayed.

19 Working with Flat File Encoding

This chapter contains the following topics:

- Section 19.1, "Understanding Flat File Encoding"

- Section 19.2, "Work with Flat File Encoding Records"

19.1 Understanding Flat File Encoding

Because JD Edwards EnterpriseOne software uses Unicode and not all third-party software does, there is a preprocessing and postprocessing intercept of all flat files. During the intercept, the software converts the flat file into the Unicode character set or back into the original character set. You can assign the conversion character set applied to a flat file—based on the user or role, the program ID, the program version, and the environment—by adding and activating a flat file encoding record.

Using Unicode Flat File Encoding Configuration (P93081), you create records for a table that specifies what character sets are used for programs. The character sets are based on the user or role, the program ID, program version, and the environment. When the pre- or post-processing intercept occurs, the intercept program calls the table, searches it, and applies the record. The search is from more specific records to less specific records.

The primary users of Unicode Flat File Encoding Configuration are power users and system administrators. The business manager can provide the character set that is used to encode the third-party flat file.

Before setting up a flat file encoding record, you need to know the encoding of the flat file being transferred. You also need to know the user or role, program, program version, and environment that is calling the flat file.

To ensure that all files are encoded to the primary character set, set up a default flat file encoding record for the primary character set, and then add any exceptions. The system applies the more specific records before the more general records, so the default record is only used if no other records apply to the incoming flat file. If you do not add and activate a flat file encoding record, the default record is UCS2, UTF16_BE/UTF16_LS, which is a Unicode character set.

This table displays the character sets, from user defined code H95/FE, that are currently supported:

Code

Description

.ini Setting

BIG5

Chinese, Traditional

TC_BIG5

CP1250

WIN-Latin2, Central Europe

EE_CP1250

CP1251

WIN-Cyrillic

RS_CP1251

CP1252

WIN-Latin 1, Western European

WE_ISO88591

CP1253

WIN-Greek

GR_CP1253

CP1254

WIN-Latin5, Turkish

TK_CP1254

CP1256

Win-Arabic

AR_CP1256

GB2312

Chinese, Simplified

SC_GB

IBM-1123

EBCDIC-Cyrillic

RS-EBCDIC

IBM-420

EBCDIC-Arabic

AR_EBCDIC

IBM-933

EBCDIC-Korean

KO_EBCDIC

IBM-935

EBCDIC-Simplified Chinese

SC_EBCDIC

IBM-937

EBCDIC-Traditional Chinese

TC_EBCDIC

IBM-939

EBCDIC-Japanese

JA_EBCDIC

IBM-37

EBCDIC-Latin 1 or Western Euro

US_EBCDIC

KSC-5601

Korean

KO_KSC

SHIFT_JIS

WIN-Japanese

JA_SJIS

UCS2

UTF16_BE/UTF16_LE

UTF-16LE

UTF16_LE

UTF-16BE

UTF16_BE

UTF8

UTF8

IBM-858

# PC Latin 1 with Euro

19.1.1 Example: Setting Up Flat File Encoding Records

The example company primarily uses the flat file encoding character set CP1252, WIN-Latin 1, Western European. However, the Sales Order Entry program (P42101) uses the UTF8, Unicode character set, except when user JL5534221 runs version JDE0001 in the PDEVCLA environment; then the program uses the CP1250, WIN-Latin2, Central Europe character set. The same program occasionally, but not currently, uses the character set CP1254, WIN-Latin5, Turkish for environment PDEVASD2.

This table presents the information for the encoding records that the example company needs in the flat file encoding table:

User/Role

Application Name

Application Version Name

Environment

Encoding Name

Status

All

All

All

All

CP1252

Active

All

P42101

All

All

UTF8

Active

JL5534221

P42101

JDE0001

PDEVCLA

CP1250

Active

All

P42101

All

PDEVASD2

CP1254

Inactive

These steps provide instructions on how to set up flat file encoding records for the previous example:

Access the Work With Flat File Encoding form. In Solution Explorer, select the System Administration Tools, System Administration Tools, User Management, User Management Advanced and Technical Operations, Unicode Flat File Encoding Configuration.

1. On the Work With Flat File Encoding form, click Add.

2. On the Flat File Encoding Revisions form, complete these fields, and then click OK:

- User / Role
*PUBLIC includes all users and roles.

- Environment
*ALL includes all environments.

- Program ID
*DEFAULT includes all programs.

- Version
*DEFAULT includes all program versions.

- Encoding Name
Enter the following value: CP1252.

3. Repeat the previous step to add the following records to the table:

User/Role

Environment

Program ID

Version

Encoding Name

*PUBLIC

*ALL

*DEFAULT

*DEFAULT

CP1252

*PUBLIC

*ALL

P42101

*DEFAULT

UTF8

JL5534221

PDEVCLA

P42101

JDE0001

CP1250

*PUBLIC

PDEVASD2

P42101

*DEFAULT

CP1254

4. Click Cancel to return to Work With Flat File Encoding.

5. Click Find to display all of the flat file encoding records.

6. Select the first record and from the Row menu, select Change Status to activate the recode.

7. Repeat the previous step to activate the currently active records.
This table displays the final configuration:

User/Role

Environment

Program ID

Version

Encoding Name

Status

*PUBLIC

*ALL

*DEFAULT

*DEFAULT

CP1252

AV

*PUBLIC

*ALL

P42101

*DEFAULT

UTF8

AV

JL5534221

PDEVCLA

P42101

JDE0001

CP1250

AV

*PUBLIC

PDEVASD2

P42101

*DEFAULT

CP1254

NA

19.2 Work with Flat File Encoding Records

This section discusses how to:

- Add a flat file encoding record.

- Activate a flat file encoding record.

19.2.1 Forms Used to Work with Flat File Encoding Records

Form Name

FormID

Navigation

Usage

Work With Flat File Encoding

W93081A

System Administration Tools (GH9011), Unicode Flat File Encoding Configuration.

Access the form to add a flat file encoding record. Locate the defined flat file encoding files.

Flat File Encoding Revisions

W93081B

On the Work With Flat File Encoding form, click Add.

Enter the information for a flat file encoding record.

19.2.2 Adding a Flat File Encoding Record

To define the character set that is applied to a flat file during the pre- or post-processing intercept, add a flat file encoding record. You can apply a flat file encoding file based on the user, the user role, the program ID, the program version, and the environment.

After you add the flat file encoding record, you must activate it.

Access the Work With Flat File Encoding form.

1. Click Add.

2. On the Flat File Encoding Revisions form, complete these fields, and then click OK:

- User / Role
The default user/role is *PUBLIC, which includes all users. By specifying a user or role, you can limit flat file encoding to only programs running under that user or role.

- Environment
The default environment is *ALL, which applies the character set encoding to all environments. By specifying an environment, you can limit the flat file encoding to only programs running under that environment.

- Program ID
The program ID identifies the batch or interactive application to which to apply the flat file encoding. The default value, *DEFAULT, applies flat file encoding to all programs.

- Version
A version is a set of user defined specifications that determines how a batch or interactive application runs. A program version identifies the batch or interactive application version to which to apply the flat file encoding. The default version, *DEFAULT, applies the flat file encoding file to all versions.

- Encoding Name
The encoding name identifies the character set used by the incoming or outgoing flat file. You must specify an encoding name.

19.2.3 Activating a Flat File Encoding Record

After adding a flat file encoding record, you must activate it before it will be applied to incoming and outgoing flat files.

Access the Work With Flat File Encoding form.

1. Click Find to display the defined flat file encoding files.

2. Select the flat file encoding file to activate or deactivate.

3. From the Row menu, select Change Status.
The status of the flat file encoding becomes active (AV) or inactive (NA).

20 Understanding Naming Conventions

This chapter contains the following topics:

- Section 20.1, "Path Codes"

- Section 20.2, "Data Sources"

- Section 20.3, "Package Names"

- Section 20.4, "Server Names"

- Section 20.5, "Workstation Names"

20.1 Path Codes

The naming conventions for a path code are as follows:

- Limited to 10 characters.

- Letters must be uppercase only.

20.2 Data Sources

The naming conventions for a data source are as follows:

- Limited to 30 characters.

- Case-sensitive.

Specific naming convention exceptions for the Client Access data source are as follows:

- Limited to 32 characters.

- Must begin with an alphabetic character.

- You cannot use the following characters:

- { }

- [ ]

- ( )

- ?

- *

- =

- !

- @

- ;

Note:
You must type the data source name before you can use the Client Access ODBC driver to access IBM i data.

20.2.1 Data Source Description

Limited to 80 characters.

20.3 Package Names

The naming conventions for a package are as follows:

- Limited to 8 characters.

- Uppercase only.

- You cannot use the following characters:

- /

- \

- :

- *

- ?

- <

- >

- |

20.4 Server Names

The naming conventions for a server depend on the specific platform. For example, an HP9000 and an IBM i allow you to enter different characters when you define the server name. JD Edwards EnterpriseOne limits the number of characters that you can use to name a server to 15, regardless of the platform.

20.5 Workstation Names

Use the following naming conventions for a workstation:

- Limited to 15 characters.

- Each workstation requires a unique name.
When you add a workstation to a Windows Server domain, you must use the name created for the computer by the network administrator.

If the workstation name does not have a computer account in the domain, you cannot sign in to the domain or access any domain user accounts.

Glossary

Accessor Methods/Assessors

Java methods to “get” and “set” the elements of a value object or other source file.

activity rule

The criteria by which an object progresses from one given point to the next in a flow.

add mode

A condition of a form that enables users to input data.

Advanced Planning Agent (APAg)

A JD Edwards EnterpriseOne tool that can be used to extract, transform, and load enterprise data. APAg supports access to data sources in the form of rational databases, flat file format, and other data or message encoding, such as XML.

application server

Software that provides the business logic for an application program in a distributed environment. The servers can be Oracle Application Server (OAS) or WebSphere Application Server (WAS).

Auto Commit Transaction

A database connection through which all database operations are immediately written to the database.

batch processing

A process of transferring records from a third-party system to JD Edwards EnterpriseOne.

In JD Edwards EnterpriseOne Financial Management, batch processing enables you to transfer invoices and vouchers that are entered in a system other than JD Edwards EnterpriseOne to JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Accounts Payable, respectively. In addition, you can transfer address book information, including customer and supplier records, to JD Edwards EnterpriseOne.

batch server

A server that is designated for running batch processing requests. A batch server typically does not contain a database nor does it run interactive applications.

batch-of-one

A transaction method that enables a client application to perform work on a client workstation, then submit the work all at once to a server application for further processing. As a batch process is running on the server, the client application can continue performing other tasks.

best practices

Non-mandatory guidelines that help the developer make better design decisions.

BPEL

Abbreviation for Business Process Execution Language, a standard web services orchestration language, which enables you to assemble discrete services into an end-to-end process flow.

BPEL PM

Abbreviation for Business Process Execution Language Process Manager, a comprehensive infrastructure for creating, deploying, and managing BPEL business processes.

Build Configuration File

Configurable settings in a text file that are used by a build program to generate ANT scripts. ANT is a software tool used for automating build processes. These scripts build published business services.

build engineer

An actor that is responsible for building, mastering, and packaging artifacts. Some build engineers are responsible for building application artifacts, and some are responsible for building foundation artifacts.

Build Program

A WIN32 executable that reads build configuration files and generates an ANT script for building published business services.

business analyst

An actor that determines if and why an EnterpriseOne business service needs to be developed.

business function

A named set of user-created, reusable business rules and logs that can be called through event rules. Business functions can run a transaction or a subset of a transaction (check inventory, issue work orders, and so on). Business functions also contain the application programming interfaces (APIs) that enable them to be called from a form, a database trigger, or a non-JD Edwards EnterpriseOne application. Business functions can be combined with other business functions, forms, event rules, and other components to make up an application. Business functions can be created through event rules or third-generation languages, such as C. Examples of business functions include Credit Check and Item Availability.

business function event rule

See named event rule (NER).

business service

EnterpriseOne business logic written in Java. A business service is a collection of one or more artifacts. Unless specified otherwise, a business service implies both a published business service and business service.

business service artifacts

Source files, descriptors, and so on that are managed for business service development and are needed for the business service build process.

business service class method

A method that accesses resources provided by the business service framework.

business service configuration files

Configuration files include, but are not limited to, interop.ini, JDBj.ini, and jdelog.properties.

business service cross reference

A key and value data pair used during orchestration. Collectively refers to both the code and the key cross reference in the WSG/XPI based system.

business service cross-reference utilities

Utility services installed in a BPEL/ESB environment that are used to access JD Edwards EnterpriseOne orchestration cross-reference data.

business service development environment

A framework needed by an integration developer to develop and manage business services.

business services development tool

Otherwise known as JDeveloper.

business service EnterpriseOne object

A collection of artifacts managed by EnterpriseOne LCM tools. Named and represented within EnterpriseOne LCM similarly to other EnterpriseOne objects like tables, views, forms, and so on.

business service framework

Parts of the business service foundation that are specifically for supporting business service development.

business service payload

An object that is passed between an enterprise server and a business services server. The business service payload contains the input to the business service when passed to the business services server. The business service payload contains the results from the business service when passed to the Enterprise Server. In the case of notifications, the return business service payload contains the acknowledgement.

business service property

Key value data pairs used to control the behavior or functionality of business services.

Business Service Property Admin Tool

An EnterpriseOne application for developers and administrators to manage business service property records.

business service property business service group

A classification for business service property at the business service level. This is generally a business service name. A business service level contains one or more business service property groups. Each business service property group may contain zero or more business service property records.

business service property key

A unique name that identifies the business service property globally in the system.

business service property utilities

A utility API used in business service development to access EnterpriseOne business service property data.

business service property value

A value for a business service property.

business service repository

A source management system, for example ClearCase, where business service artifacts and build files are stored. Or, a physical directory in network.

business services server

The physical machine where the business services are located. Business services are run on an application server instance.

business services source file or business service class

One type of business service artifact. A text file with the .java file type written to be compiled by a Java compiler.

business service value object template

The structural representation of a business service value object used in a C-business function.

Business Service Value Object Template Utility

A utility used to create a business service value object template from a business service value object.

business services server artifact

The object to be deployed to the business services server.

business view

A means for selecting specific columns from one or more JD Edwards EnterpriseOne application tables whose data is used in an application or report. A business view does not select specific rows, nor does it contain any actual data. It is strictly a view through which you can manipulate data.

central objects merge

A process that blends a customer's modifications to the objects in a current release with objects in a new release.

central server

A server that has been designated to contain the originally installed version of the software (central objects) for deployment to client computers. In a typical JD Edwards EnterpriseOne installation, the software is loaded on to one machine—the central server. Then, copies of the software are pushed out or downloaded to various workstations attached to it. That way, if the software is altered or corrupted through its use on workstations, an original set of objects (central objects) is always available on the central server.

charts

Tables of information in JD Edwards EnterpriseOne that appear on forms in the software.

check-in repository

A repository for developers to check in and check out business service artifacts. There are multiple check-in repositories. Each can be used for a different purpose (for example, development, production, testing, and so on).

checksum

A fixed-size datum computed from an arbitrary block of digital data for the purpose of detecting accidental errors that may have been introduced during its transmission or storage. JD Edwards EnterpriseOne uses the checksum to verify the integrity of packages that have been downloaded by recomputing the checksum of the downloaded package and comparing it with the checksum of the original package. The procedure that yields the checksum from the data is called a checksum function or checksum algorithm. JD Edwards EnterpriseOne uses the MD5 and STA-1 checksum algorithms.

connector

Component-based interoperability model that enables third-party applications and JD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOne connector architecture includes Java and COM connectors.

Control Table Workbench

An application that, during the Installation Workbench processing, runs the batch applications for the planned merges that update the data dictionary, user-defined codes, menus, and user override tables.

control tables merge

A process that blends a customer's modifications to the control tables with the data that accompanies a new release.

correlation data

The data used to tie HTTP responses with requests that consist of business service name and method.

credentials

A valid set of JD Edwards EnterpriseOne username/password/environment/role, EnterpriseOne session, or EnterpriseOne token.

cross-reference utility services

Utility services installed in a BPEL/ESB environment that access EnterpriseOne cross-reference data.

database credentials

A valid database username/password.

database server

A server in a local area network that maintains a database and performs searches for client computers.

Data Source Workbench

An application that, during the Installation Workbench process, copies all data sources that are defined in the installation plan from the Data Source Master and Table and Data Source Sizing tables in the Planner data source to the system-release number data source. It also updates the Data Source Plan detail record to reflect completion.

deployment artifacts

Artifacts that are needed for the deployment process, such as servers, ports, and such.

deployment server

A server that is used to install, maintain, and distribute software to one or more enterprise servers and client workstations.

direct connect

A transaction method in which a client application communicates interactively and directly with a server application.

See also batch-of-one and store-and-forward.

Do Not Translate (DNT)

A type of data source that must exist on the iSeries because of BLOB restrictions.

embedded application server instance

An OC4J instance started by and running wholly within JDeveloper.

edit code

A code that indicates how a specific value for a report or a form should appear or be formatted. The default edit codes that pertain to reporting require particular attention because they account for a substantial amount of information.

edit mode

A condition of a form that enables users to change data.

edit rule

A method used for formatting and validating user entries against a predefined rule or set of rules.

Electronic Data Interchange (EDI)

An interoperability model that enables paperless computer-to-computer exchange of business transactions between JD Edwards EnterpriseOne and third-party systems. Companies that use EDI must have translator software to convert data from the EDI standard format to the formats of their computer systems.

embedded event rule

An event rule that is specific to a particular table or application. Examples include form-to-form calls, hiding a field based on a processing option value, and calling a business function. Contrast with the business function event rule.

Employee Work Center

A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. Each user has a mailbox that contains workflow and other messages, including Active Messages.

enterprise server

A server that contains the database and the logic for JD Edwards EnterpriseOne.

Enterprise Service Bus (ESB)

Middleware infrastructure products or technologies based on web services standards that enable a service-oriented architecture using an event-driven and XML-based messaging framework (the bus).

EnterpriseOne administrator

An actor responsible for the EnterpriseOne administration system.

EnterpriseOne credentials

A user ID, password, environment, and role used to validate a user of EnterpriseOne.

EnterpriseOne development client

Historically called “fat client,” a collection of installed EnterpriseOne components required to develop EnterpriseOne artifacts, including the Microsoft Windows client and design tools.

EnterpriseOne extension

A JDeveloper component (plug-in) specific to EnterpriseOne. A JDeveloper wizard

is a specific example of an extension.

EnterpriseOne object

A reusable piece of code that is used to build applications. Object types include tables, forms, business functions, data dictionary items, batch processes, business views, event rules, versions, data structures, and media objects.

EnterpriseOne process

A software process that enables JD Edwards EnterpriseOne clients and servers to handle processing requests and run transactions. A client runs one process, and servers can have multiple instances of a process. JD Edwards EnterpriseOne processes can also be dedicated to specific tasks (for example, workflow messages and data replication) to ensure that critical processes don't have to wait if the server is particularly busy.

EnterpriseOne resource

Any EnterpriseOne table, metadata, business function, dictionary information, or other information restricted to authorized users.

Environment Workbench

An application that, during the Installation Workbench process, copies the environment information and Object Configuration Manager tables for each environment from the Planner data source to the system-release number data source. It also updates the Environment Plan detail record to reflect completion.

escalation monitor

A batch process that monitors pending requests or activities and restarts or forwards them to the next step or user after they have been inactive for a specified amount of time.

event rule

A logic statement that instructs the system to perform one or more operations based on an activity that can occur in a specific application, such as entering a form or exiting a field.

explicit transaction

Transaction used by a business service developer to explicitly control the type (auto or manual) and the scope of transaction boundaries within a business service.

exposed method or value object

Published business service source files or parts of published business service source files that are part of the published interface. These are part of the contract with the customer.

fast path

A command prompt that enables the user to move quickly among menus and applications by using specific commands.

file server

A server that stores files to be accessed by other computers on the network. Unlike a disk server, which appears to the user as a remote disk drive, a file server is a sophisticated device that not only stores files, but also manages them and maintains order as network users request files and make changes to these files.

final mode

The report processing mode of a processing mode of a program that updates or creates data records.

foundation

A framework that must be accessible for execution of business services at runtime. This includes, but is not limited to, the Java Connector and JDBj.

FTP server

A server that responds to requests for files via file transfer protocol.

HTTP Adapter

A generic set of services that are used to do the basic HTTP operations, such as GET, POST, PUT, DELETE, TRACE, HEAD, and OPTIONS with the provided URL.

instantiate

A Java term meaning “to create.” When a class is instantiated, a new instance

is created.

integration developer

The user of the system who develops, runs, and debugs the EnterpriseOne business services. The integration developer uses the EnterpriseOne business services to develop these components.

integration point (IP)

The business logic in previous implementations of EnterpriseOne that exposes a document level interface. This type of logic used to be called XBPs. In EnterpriseOne 8.11, IPs are implemented in Web Services Gateway powered by webMethods.

integration server

A server that facilitates interaction between diverse operating systems and applications across internal and external networked computer systems.

integrity test

A process used to supplement a company's internal balancing procedures by locating and reporting balancing problems and data inconsistencies.

interface table

See Z table.

internal method or value object

Business service source files or parts of business service source files that are not part of the published interface. These could be private or protected methods. These could be value objects not used in published methods.

interoperability model

A method for third-party systems to connect to or access JD Edwards EnterpriseOne.

in-your-face error

In JD Edwards EnterpriseOne, a form-level property which, when enabled, causes the text of application errors to appear on the form.

jargon

An alternative data dictionary item description that JD Edwards EnterpriseOne appears based on the product code of the current object.

Java application server

A component-based server that resides in the middle-tier of a server-centric architecture. This server provides middleware services for security and state maintenance, along with data access and persistence.

JDBNET

A database driver that enables heterogeneous servers to access each other's data.

JDEBASE Database Middleware

A JD Edwards EnterpriseOne proprietary database middleware package that provides platform-independent APIs, along with client-to-server access.

JDECallObject

An API used by business functions to invoke other business functions.

jde.ini

A JD Edwards EnterpriseOne file (or member for iSeries) that provides the runtime settings required for JD Edwards EnterpriseOne initialization. Specific versions of the file or member must reside on every machine running JD Edwards EnterpriseOne. This includes workstations and servers.

JDEIPC

Communications programming tools used by server code to regulate access to the same data in multiprocess environments, communicate and coordinate between processes, and create new processes.

jde.log

The main diagnostic log file of JD Edwards EnterpriseOne. This file is always located in the root directory on the primary drive and contains status and error messages from the startup and operation of JD Edwards EnterpriseOne.

JDENET

A JD Edwards EnterpriseOne proprietary communications middleware package. This package is a peer-to-peer, message-based, socket-based, multiprocess communications middleware solution. It handles client-to-server and server-to-server communications for all JD Edwards EnterpriseOne supported platforms.

JDeveloper Project

An artifact that JDeveloper uses to categorize and compile source files.

JDeveloper Workspace

An artifact that JDeveloper uses to organize project files. It contains one or more project files.

JMS Queue

A Java Messaging service queue used for point-to-point messaging.

listener service

A listener that listens for XML messages over HTTP.

local repository

A developer's local development environment that is used to store business service artifacts.

Location Workbench

An application that, during the Installation Workbench process, copies all locations that are defined in the installation plan from the Location Master table in the Planner data source to the system data source.

logic server

A server in a distributed network that provides the business logic for an application program. In a typical configuration, pristine objects are replicated on to the logic server from the central server. The logic server, in conjunction with workstations, actually performs the processing required when JD Edwards EnterpriseOne software runs.

MailMerge Workbench

An application that merges Microsoft Word 6.0 (or higher) word-processing documents with JD Edwards EnterpriseOne records to automatically print business documents. You can use MailMerge Workbench to print documents, such as form letters about verification of employment.

Manual Commit transaction

A database connection where all database operations delay writing to the database until a call to commit is made.

master business function (MBF)

An interactive master file that serves as a central location for adding, changing, and updating information in a database. Master business functions pass information between data entry forms and the appropriate tables. These master functions provide a common set of functions that contain all of the necessary default and editing rules for related programs. MBFs contain logic that ensures the integrity of adding, updating, and deleting information from databases.

master table

See published table.

media storage object

Files that use one of the following naming conventions that are not organized into table format: Gxxx, xxxGT, or GTxxx.

message center

A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user.

messaging adapter

An interoperability model that enables third-party systems to connect to JD Edwards EnterpriseOne to exchange information through the use of messaging queues.

messaging server

A server that handles messages that are sent for use by other programs using a messaging API. Messaging servers typically employ a middleware program to perform their functions.

Monitoring Application

An EnterpriseOne tool provided for an administrator to get statistical information for various EnterpriseOne servers, reset statistics, and set notifications.

named event rule (NER)

Encapsulated, reusable business logic created using event rules, rather that C programming. NERs are also called business function event rules. NERs can be reused in multiple places by multiple programs. This modularity lends itself to streamlining, reusability of code, and less work.

Object Configuration Manager (OCM)

In JD Edwards EnterpriseOne, the object request broker and control center for the runtime environment. OCM keeps track of the runtime locations for business functions, data, and batch applications. When one of these objects is called, OCM directs access to it using defaults and overrides for a given environment and user.

Object Librarian

A repository of all versions, applications, and business functions reusable in building applications. Object Librarian provides check-out and check-incapabilities for developers, and it controls the creation, modification, and use of JD Edwards EnterpriseOne objects. Object Librarian supports multiple environments (such as production and development) and enables objects to be easily moved from one environment to another.

Object Librarian merge

A process that blends any modifications to the Object Librarian in a previous release into the Object Librarian in a new release.

Open Data Access (ODA)

An interoperability model that enables you to use SQL statements to extract JD Edwards EnterpriseOne data for summarization and report generation.

Output Stream Access (OSA)

An interoperability model that enables you to set up an interface for JD Edwards EnterpriseOne to pass data to another software package, such as Microsoft Excel, for processing.

package

JD Edwards EnterpriseOne objects are installed to workstations in packages from the deployment server. A package can be compared to a bill of material or kit that indicates the necessary objects for that workstation and where on the deployment server the installation program can find them. It is point-in-time snapshot of the central objects on the deployment server.

package build

A software application that facilitates the deployment of software changes and new applications to existing users. Additionally, in JD Edwards EnterpriseOne, a package build can be a compiled version of the software. When you upgrade your version of the ERP software, for example, you are said to take a package build.

Consider the following context: “Also, do not transfer business functions into the production path code until you are ready to deploy, because a global build of business functions done during a package build will automatically include the new functions.” The process of creating a package build is often referred to, as it is in this example, simply as “a package build.”

package location

The directory structure location for the package and its set of replicated objects. This is usually \\deployment server\release\path_code\package\package name. The subdirectories under this path are where the replicated objects for the package are placed. This is also referred to as where the package is built or stored.

Package Workbench

An application that, during the Installation Workbench process, transfers the package information tables from the Planner data source to the system-release number data source. It also updates the Package Plan detail record to reflect completion.

Pathcode Directory

The specific portion of the file system on the EnterpriseOne development client where EnterpriseOne development artifacts are stored.

patterns

General repeatable solutions to a commonly occurring problem in software design. For business service development, the focus is on the object relationships and interactions. For orchestrations, the focus is on the integration patterns (for example, synchronous and asynchronous request/response, publish, notify, and receive/reply).

print server

The interface between a printer and a network that enables network clients to connect to the printer and send their print jobs to it. A print server can be a computer, separate hardware device, or even hardware that resides inside of the printer itself.

pristine environment

A JD Edwards EnterpriseOne environment used to test unaltered objects with JD Edwards EnterpriseOne demonstration data or for training classes. You must have this environment so that you can compare pristine objects that you modify.

processing option

A data structure that enables users to supply parameters that regulate the running of a batch program or report. For example, you can use processing options to specify default values for certain fields, to determine how information appears or is printed, to specify date ranges, to supply runtime values that regulate program execution, and so on.

production environment

A JD Edwards EnterpriseOne environment in which users operate EnterpriseOne software.

Production Published Business Services Web Service

Published business services web service deployed to a production application server.

program temporary fix (PTF)

A representation of changes to JD Edwards EnterpriseOne software that your organization receives on magnetic tapes or disks.

project

In JD Edwards EnterpriseOne, a virtual container for objects being developed in Object Management Workbench.

promotion path

The designated path for advancing objects or projects in a workflow. The following is the normal promotion cycle (path):

11>21>26>28>38>01

In this path, 11 equals new project pending review, 21 equals programming, 26 equals QA test/review, 28 equals QA test/review complete, 38 equals in production, 01 equals complete. During the normal project promotion cycle, developers check objects out of and into the development path code and then promote them to the prototype path code. The objects are then moved to the productions path code before declaring them complete.

proxy server

A server that acts as a barrier between a workstation and the internet so that the enterprise can ensure security, administrative control, and caching service.

published business service

EnterpriseOne service level logic and interface. A classification of a published business service indicating the intention to be exposed to external (non-EnterpriseOne) systems.

published business service identification information

Information about a published business service used to determine relevant authorization records. Published business services + method name, published business services, or *ALL.

published business service web service

Published business services components packaged as J2EE Web Service (namely, a J2EE EAR file that contains business service classes, business service foundation, configuration files, and web service artifacts).

published table

Also called a master table, this is the central copy to be replicated to other machines. Residing on the publisher machine, the F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.

publisher

The server that is responsible for the published table. The F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.

QBE

An abbreviation for query by example. In JD Edwards EnterpriseOne, the QBE line is the top line on a detail area that is used for filtering data.

real-time event

A message triggered from EnterpriseOne application logic that is intended for external systems to consume.

refresh

A function used to modify JD Edwards EnterpriseOne software, or subset of it, such as a table or business data, so that it functions at a new release or cumulative update level.

replication server

A server that is responsible for replicating central objects to client machines.

rules

Mandatory guidelines that are not enforced by tooling, but must be followed in order to accomplish the desired results and to meet specified standards.

secure by default

A security model that assumes that a user does not have permission to execute an object unless there is a specific record indicating such permissions.

Secure Socket Layer (SSL)

A security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery.

selection

Found on JD Edwards EnterpriseOne menus, a selection represents functions that you can access from a menu. To make a selection, type the associated number in the Selection field and press Enter.

serialize

The process of converting an object or data into a format for storage or transmission across a network connection link with the ability to reconstruct the original data or objects when needed.

Server Workbench

An application that, during the Installation Workbench process, copies the server configuration files from the Planner data source to the system-release number data source. The application also updates the Server Plan detail record to reflect completion.

SOA

Abbreviation for Service Oriented Architecture.

softcoding

A coding technique that enables an administrator to manipulate site-specific variables that affect the execution of a given process.

source repository

A repository for HTTP adapter and listener service development environment artifacts.

Specification merge

A merge that comprises three merges: Object Librarian merge, Versions List merge, and Central Objects merge. The merges blend customer modifications with data that accompanies a new release.

specification

A complete description of a JD Edwards EnterpriseOne object. Each object has its own specification, or name, which is used to build applications.

Specification Table Merge Workbench

An application that, during the Installation Workbench process, runs the batch applications that update the specification tables.

SSL Certificate

A special message signed by a certificate authority that contains the name of a user and that user's public key in such a way that anyone can "verify" that the message was signed by no one other than the certification authority and thereby develop trust in the user's public key.

store-and-forward

The mode of processing that enables users who are disconnected from a server to enter transactions and then later connect to the server to upload those transactions.

subscriber table

Table F98DRSUB, which is stored on the publisher server with the F98DRPUB table and identifies all of the subscriber machines for each published table.

super class

An inheritance concept of the Java language where a class is an instance of something, but is also more specific. “Tree” might be the super class of “Oak” and “Elm,” for example.

table access management (TAM)

The JD Edwards EnterpriseOne component that handles the storage and retrieval of use-defined data. TAM stores information, such as data dictionary definitions; application and report specifications; event rules; table definitions; business function input parameters and library information; and data structure definitions for running applications, reports, and business functions.

Table Conversion Workbench

An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.

table conversion

An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.

table event rules

Logic that is attached to database triggers that runs whenever the action specified by the trigger occurs against the table. Although JD Edwards EnterpriseOne enables event rules to be attached to application events, this functionality is application specific. Table event rules provide embedded logic at the table level.

terminal server

A server that enables terminals, microcomputers, and other devices to connect to a network or host computer or to devices attached to that particular computer.

transaction processing (TP) monitor

A monitor that controls data transfer between local and remote terminals and the applications that originated them. TP monitors also protect data integrity in the distributed environment and may include programs that validate data and format terminal screens.

transaction processing method

A method related to the management of a manual commit transaction boundary (for example, start, commit, rollback, and cancel).

transaction set

An electronic business transaction (electronic data interchange standard document) made up of segments.

trigger

One of several events specific to data dictionary items. You can attach logic to a data dictionary item that the system processes automatically when the event occurs.

triggering event

A specific workflow event that requires special action or has defined consequences or resulting actions.

user identification information

User ID, role, or *public.

User Overrides merge

Adds new user override records into a customer's user override table.

value object

A specific type of source file that holds input or output data, much like a data structure passes data. Value objects can be exposed (used in a published business service) or internal, and input or output. They are comprised of simple and complex elements and accessories to those elements.

versioning a published business service

Adding additional functionality/interfaces to the published business services without modifying the existing functionality/interfaces.

Versions List merge

The Versions List merge preserves any non-XJDE and non-ZJDE version specifications for objects that are valid in the new release, as well as their processing options data.

visual assist

Forms that can be invoked from a control via a trigger to assist the user in determining what data belongs in the control.

vocabulary override

An alternate description for a data dictionary item that appears on a specific JD Edwards EnterpriseOne form or report.

web application server

A web server that enables web applications to exchange data with the back-end systems and databases used in eBusiness transactions.

web server

A server that sends information as requested by a browser, using the TCP/IP set of protocols. A web server can do more than just coordination of requests from browsers; it can do anything a normal server can do, such as house applications or data. Any computer can be turned into a web server by installing server software and connecting the machine to the internet.

Web Service Description Language (WSDL)

An XML format for describing network services.

Web Service Inspection Language (WSIL)

An XML format for assisting in the inspection of a site for available services and a set of rules for how inspection-related information should be made.

web service softcoding record

An XML document that contains values that are used to configure a web service proxy. This document identifies the endpoint and conditionally includes security information.

web service softcoding template

An XML document that provides the structure for a soft coded record.

Where clause

The portion of a database operation that specifies which records the database operation will affect.

Windows terminal server

A multiuser server that enables terminals and minimally configured computers to display Windows applications even if they are not capable of running Windows software themselves. All client processing is performed centrally at the Windows terminal server and only display, keystroke, and mouse commands are transmitted over the network to the client terminal device.

wizard

A type of JDeveloper extension used to walk the user through a series of steps.

workbench

A program that enables users to access a group of related programs from a single entry point. Typically, the programs that you access from a workbench are used to complete a large business process. For example, you use the JD Edwards EnterpriseOne Payroll Cycle Workbench (P07210) to access all of the programs that the system uses to process payroll, print payments, create payroll reports, create journal entries, and update payroll history. Examples of JD Edwards EnterpriseOne workbenches include Service Management Workbench (P90CD020), Line Scheduling Workbench (P3153), Planning Workbench (P13700), Auditor's Workbench (P09E115), and Payroll Cycle Workbench.

workflow

The automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules.

workgroup server

A server that usually contains subsets of data replicated from a master network server. A workgroup server does not perform application or batch processing.

XAPI events

A service that uses system calls to capture JD Edwards EnterpriseOne transactions as they occur and then calls third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested notification when the specified transactions occur to return a response.

XML CallObject

An interoperability capability that enables you to call business functions.

XML Dispatch

An interoperability capability that provides a single point of entry for all XML documents coming into JD Edwards EnterpriseOne for responses.

XML List

An interoperability capability that enables you to request and receive JD Edwards EnterpriseOne database information in chunks.

XML Service

An interoperability capability that enables you to request events from one JD Edwards EnterpriseOne system and receive a response from another JD Edwards EnterpriseOne system.

XML Transaction

An interoperability capability that enables you to use a predefined transaction type to send information to or request information from JD Edwards EnterpriseOne. XML transaction uses interface table functionality.

XML Transaction Service (XTS)

Transforms an XML document that is not in the JD Edwards EnterpriseOne format into an XML document that can be processed by JD Edwards EnterpriseOne. XTS then transforms the response back to the request originator XML format.

Z event

A service that uses interface table functionality to capture JD Edwards EnterpriseOne transactions and provide notification to third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested to be notified when certain transactions occur.

Z table

A working table where non-JD Edwards EnterpriseOne information can be stored and then processed into JD Edwards EnterpriseOne. Z tables also can be used to retrieve JD Edwards EnterpriseOne data. Z tables are also known as interface tables.

Z transaction

Third-party data that is properly formatted in interface tables for updating to the JD Edwards EnterpriseOne database.

Index
A  B  C  D  E  F  I  J  L  M  N  O  P  Q  R  S  T  U  V  W

A

Application Failure Recovery program (P95400), 17.1

applications

granting access to failed application data, 17.3

interactive versions, 9.1

B

batch applications

overriding specifications with the Job Scheduler, 13.3.6

scheduling a jobJob Scheduler, 13.2.5

batch processes for vocabulary overrides, 12.2.5 business views, configuring for text search indexes, 16.2.3

C

cache, understanding cached override information, 11.1.1, 11.1.3

category codes, 10.1.1

control records, using with the Scheduler server, 13.5.1.1

D

data dictionary

administration, 2.1

updating display decimals, 2.2

Data Dictionary program (P92001), 2.1 data recovery

granting access to failed application data, 17.3

understanding, 17.1

data source naming conventions, 20.2 data, viewing in Universal Table Browser, 18.2.1 daylight savings rules

adding, 13.6.3

revising, 13.6.5

setting with Job Scheduler, 13.6

dispatch functions, using with the Scheduler server, 13.5.1.2 display decimals, updating, 2.2 Distributed Next Number Update UBE (R0002D1), 6.2.7 distributed next numbers

configuring for mobile clients, 6.1

enabling distributed next numbers for mobile clients, 6.2.3

mapping the JD Edwards EnterpriseOne user ID to the Distributed Next Numbers application, 6.2.5

scheduling updates to distributed next numbers applications, 6.2.7

setting up by application, 6.2.6

setting up by system for mobile clients, 6.2.4

E

environments, overriding with the Job Scheduler, 13.3.3

F

F00165 table, 14.1.1, 14.5, 15.1

F91300 table, 13.1, 13.5.1, 13.5.1.1

F91310 table, 13.1

F91320 table, 13.1, 13.5.1, 13.5.4

F98101 table, 14.4, 15.3.1.1

F98950 table, 11.1, 11.1.3

F98MOQUE table, 14.4

flat file encoding records

activating, 19.2.3

adding, 19.2.2

example of, 19.1.1

understanding, 19.1

Flat File Encoding Revisions form, 19.2.1

I

image media objects, 14.3.1

imaging

files, 14.1

setting up, 15, 15.3.1

typical process flow for, 15.3.1.1

understanding, 14.2

Imaging Constants Revisions form, 15.3.2 Imaging Constants table (F98101), 14.4, 15.3.1.1 Imaging process flow diagram, 15.3.1.1 Index Selection Tool program (P95150)

dropping a single index, 8.2.4

dropping indexes from a table, 8.1

dropping multiple indexes, 8.2.5

flagging indexes, 8.1.1

restoring indexes to a table, 8.2.6

selecting a data source, 8.2.3

understanding, 8.1

using, 8.2

viewing the index selection logs, 8.1.3, 8.2.7

interactive versions

copy an interactive version, 9.2.3

creating (adding) an interactive version, 9.2.4

understanding, 9.2.1

version detail, 9.2.2

interactive vocabulary overridesvocabulary overrides, 12.2.4

J

JDENET process, 13.5.1, 13.5.1.2

job launcher, activate or deactivate, 13.5.4

Job Maintenance form, 13.4.2, 13.4.5

job monitor loops, using with the Scheduler server, 13.5.1.4

job monitor, activate or deactivate, 13.5.4

Job Queue Maintenance program (P986130), 4.3.3

job queues

adding, 4.3.4

administering, 4.3.1.1

changing the status of, 4.3.6

copying, 4.3.5

managing, 4.3

overriding, 4.3.1.2, 4.3.7

understanding, 4.3.1

Job Schedule form, 13.4.2, 13.4.4, 13.4.5, 13.4.6 Job Scheduler

adding values to a report interconnect, 13.3.7

changing launch status, 13.4.4

defining resubmission time, 13.3.5

overriding batch application specifications, 13.3.6

overriding job expiration specifications, 13.3.4

overriding the environment, 13.3.3

resetting the job schedule, 13.4.7

reviewing all jobs or local jobs, 13.2.8

reviewing job schedules, 13.4.3

reviewing the job schedule, 13.4.1

revising a scheduled job, 13.2.7

running the Scheduled Jobs report, 13.7

scheduling a job, 13.2.5

scheduling a recurring job, 13.2.6

setting job status manually, 13.4.6

setting processing options, 13.2.4

understanding, 13.1

understanding the Scheduler server, 13.5.1

using advanced scheduling options, 13.3.1

viewing job details, 13.4.5

working with daylight savings rules, 13.6

working with job properties, 13.3.1

jobs

changing a printer, 4.2.5

changing the priority, 4.2.5

holding, 4.2.10

overriding printer location, 4.2.1.2

printing job reports

Purge Scheduled Jobs report, 13.7.1

Scheduled Jobs report, 13.7.1

printing jobs, 4.2.6 releasing, 4.2.10 reviewing all or local jobs, 13.2.8 reviewing online, 4.2.1.3 schedulingJob Scheduler, 13.2 status and priority, 4.2.1.1 terminating, 4.2.1.5, 4.2.9 viewing job logs, 4.2.1.4 viewing logs for a job, 4.2.8 working with job properties, 13.3.1 working with server jobs, 4.2.1

L

language-specific media object attachments, adding, 15.1.3

logs

viewing job logs, 4.2.8

M

Machine Search & Select form, 8.2.1, 8.2.2

Manually Set Job Status form, 13.4.2, 13.4.6

Media Object Queue Revisions form, 15.2.1, 15.2.2

media object queues

defining queue location, 15.2.3

deleting, 15.2.4

setting up, 15.2

understanding, 14.3

Media Object Queues table (F98MOQUE), 14.4 media objects

attaching language-specific media objects, 15.1.3

enabling JD Edwards EnterpriseOne to use media objects, 15.1

enabling media objects, 15.3.3

enabling use in JD Edwards EnterpriseOne, 15.1.2

for text search indexestext search indexes, 16.2.4

image media objects, 14.3.1

language considerations for, 14.5

media object tables, 14.4

OLE media objects, 14.3.2

setting up imagingimaging, 15.3.1

text items, 14.1.1

typical process flow for imaging, 15.3.1.1

URL media objects, 14.3.3

using standard processing, 15.1.2

Media Objects Storage (F00165), 14.1.1 Media Objects Storage table (F00165), 15.1 mobile clients

activating functionality, 6.2.1

distributed next numbers for, 6.1

setting up distributed next numbers by system, 6.2.4

N

naming conventions

data sources, 20.2

package names, 20.3

path codes, 20.1

servers, 20.4

workstations, 20.5

Next Number Revisions application (P0002), 6.2.2

O

Object Management Workbench ( OMW) administration, 3.1

OLE media objects, 14.3.2

OLE objects, 14.1

P

P0002 program, 6.2.2

P00023A program, 6.2.4

P0004A program, 10.3

P00098 program, 6.2.3

P91300 program, 13.1

P92001 program, 2.1

P9220 program, 12.1

P950411 programdistributed next numbers, 6.2.5

P95150 program

dropping a single index, 8.2.4

dropping multiple indexes, 8.2.5

flagging indexes, 8.1.1

restoring indexes to a table, 8.2.6

selecting a data source, 8.2.3

using, 8.2

viewing the index selection logs, 8.1.3, 8.2.7

P95190 program, 8.1 P95400 program, 17.1, 17.3 P986116 program

processing options, 4.2.3

understanding, 4.1

using, 4.2.2

P986130 program, 4.3.3 P98950 program, 11.1.3 packages, naming conventions, 20.3 path codes, naming conventions, 20.1 PIM synchronization

exporting PIM user records, 5.4

importing PIM synchronization files into Intellisync Server, 5.5

processing options, 5.2

setting up users for, 5.3

user defined codes for, 5.1.1

printing, viewing reports online, 4.2.7 properties, viewing column properties, 18.2.2 Purge Scheduled Jobs report, printing, 13.7.1

Q

queues

managing job queues, 4.3

media objectMedia Object Queues, 14.3

R

Recurring Scheduling Information Revisions form, 13.2.3, 13.2.6

reports

adding values to report interconnect, 13.3.7

checking status, 4.2.4

running the Scheduled Jobs report, 13.7

viewing online, 4.2.7

S

Schedule table (F91320), 13.1

Scheduled Job Master table (F91300), 13.1

Scheduled Job Parameters table (F91310), 13.1

Scheduled Jobs report, printing, 13.7.1

Scheduler, 13.7.1

Scheduler server

control records, 13.5.1.1

dispatch functions, 13.5.1.2

job monitor loops, 13.5.1.4

launch loops, 13.5.1.3

modifying the sleep time, 13.5.7

refreshing the settings, 13.5.6

resetting, 13.5.5

stopping or restarting, 13.5.3

using, 13.5.1

Scheduler Server Control form, 13.5.2, 13.5.4 Scheduling Advanced Options form, 13.2.3, 13.3.2, 13.3.3 Scheduling Information Add form, 13.2.3, 13.2.5 scheduling jobs

using the Job Schedulerjob scheduler, 13.2

search hierarchy, understanding, 11.1.2 servers

naming conventions, 20.4

understanding the Scheduler server, 13.5.1

shortcuts, for media objects, 14.1 stop words, defining for text search indexes, 16.4.4 subsystems

enabling, 4.4.1.2

locating subsystems running on a server, 4.4.3

logical sequence of events diagram, 4.4.1.1

stopping, 4.4.5

terminating, 4.4.1.4, 4.4.5

understanding JD Edwards EnterpriseOne subsystems, 4.4.1

viewing job records of, 4.4.4

synonyms, defining for text search indexes, 16.4.5

T

tables

viewing column properties, 18.2.2

viewing data in, 18.2.1

text items, 14.1.1 text search business view-data source pair, adding, 16.4.3 Text Search Index Language Revisions form, 16.2.2 Text Search Index Media Object Queue form, 16.2.2 Text Search Index Revisions form, 16.2.2 text search indexes

adding a text search business view-data source pair, 16.4.3

building, 16.3

defining, 16.2

defining languages for, 16.2.5

defining media objects for, 16.2.4

defining stop words for, 16.4.4

defining topics for, 16.4.6

designating data sources for business views, 16.2.3

properties of, 16.4.1

understanding, 16.2.1

Text Search Properties Revisions form, 16.4.2 topics, defining for text search indexes, 16.4.6

U

UDC lists, 10.1.1

UDC types

adding, 10.5.5

changing, 10.5.4

create and customize UDC types, 10.5

customizing, 10.2

deleting, 10.5.6

translate descriptions into alternate languages, 10.6.2

understanding, 10.1.1

UDCs, UDC types, and category codes, 10.1.1 Universal Table Browser

viewing column properties in a table, 18.2.2

viewing data in tables, 18.2.1

URL media objects, 14.3.3 user defined codes

adding, 10.4.2

blank as a valid value, 10.4.2

changing a user defined code, 10.4.1

consequences of customizing, 10.2.1

create and customize UDCs, 10.4

customizing, 10.2

deleting, 10.4.3

example of, 10.1.1.1

hard coded, 10.2

translate descriptions into alternate languages, 10.6.3

translating into different languages, 10.6

User Defined Codes program (P0004A), 10.3 user overrides

cached override information, 11.1.3

changing individual to group user overrides, 11.2.3

copying, 11.2.3

creating, 11.2.2

deleting, 11.2.4

fixing, 11.2.4

fixing after a form change, 11.2.4

search hierarchy, 11.1.2

understanding, 11.1

working with, 11.2

User Overrides Revision application (P98950), 11.1.3 User Overrides Table (F98950), 11.1.3 User Overrides table (F98950), 11.1

V

versions

differences between interactive and batch versions, 9.1.2

processing options, 9.1.1

vocabulary overrides

accessing, 12.2.2

accessing from OMW, 12.2.3

accessing the Interactive Vocabulary Overrides form, 12.2.3

creating a batch vocabulary override, 12.2.5

creating an interactive vocabulary override, 12.2.4

resetting, 12.2.7

resetting all overrides in an application (interactive and batch), 12.2.8

reviewing, 12.2.6

understanding, 12.1

Vocabulary Overrides program (P9220), 12.1

W

Work With All Job Schedule form, 13.4.2, 13.4.3

Work with Application Failure Records program (P95400), 17.3

Work With Flat File Encoding form, 19.2.1

Work With Job Queues form, 4.3.3

Work With Media Object Queues form, 15.2.1, 15.2.2, 15.2.4, 15.3.2

Work With Scheduled Jobs, 13.2.3

Work With Scheduled Jobs form, 13.2.5, 13.3.2, 13.4.2, 13.4.4

Work with Scheduled Jobs form, 13.5.2

Work with Server Jobs form, checking report status, 4.2.4

Work With Servers program (P986116)

processing options, 4.2.3

understanding, 4.1

using, 4.2.2

Work With Text Search Indices form, 16.2.2 Work with Text Search Properties form, 16.4.2 Work with Text Search Stop Words form, 16.4.2 Work with Text Search Synonyms form, 16.4.2 Work with Text Search Topics form, 16.4.2 workstations, naming conventions, 20.5

Oracle Legal Notices

Copyright Notice

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

Trademark Notice

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

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

License Restrictions Warranty/Consequential Damages Disclaimer

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

Warranty Disclaimer

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

Restricted Rights Notice

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

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

Hazardous Applications Notice

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

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

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