JD Edwards EnterpriseOne Tools

Fundamentals Guide

Release 8.98 Update 4

E14712-02

March 2011

JD Edwards EnterpriseOne Tools Fundamentals Guide, Release 8.98 Update 4

E14712-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

- 1.1 JD Edwards EnterpriseOne Tools Overview

- 1.1.1 JD Edwards EnterpriseOne Tools Categories

- 1.1.2 Implementation Phases

- 1.1.3 Other Sources of Information

- 1.2 JD Edwards EnterpriseOne Tools Implementation

2 Understanding Development Tools

- 2.1 Understanding Development Tools

- 2.2 JD Edwards EnterpriseOne Report Design Aid

- 2.2.1 JD Edwards EnterpriseOne XML Publisher

- 2.3 Report Printing Administration

- 2.4 JD Edwards EnterpriseOne Tables and Business Views

- 2.5 JD Edwards EnterpriseOne Form Design Aid

- 2.6 JD Edwards EnterpriseOne Batch Versions

- 2.7 JD Edwards EnterpriseOne Business Services

- 2.8 Event Rules and System Functions

- 2.9 JD Edwards EnterpriseOne Object Management Workbench

- 2.10 JD Edwards EnterpriseOne Data Structure Design

- 2.11 APIs and Business Functions

3 Understanding Administration Tools

- 3.1 Understanding Administration Tools

- 3.2 JD Edwards EnterpriseOne Configurable Network Computing Implementation

- 3.3 System Administration

- 3.4 Auditing Administration

- 3.5 JD Edwards EnterpriseOne Delta Process

- 3.6 JD Edwards EnterpriseOne Solution Explorer

- 3.7 JD Edwards EnterpriseOne Workflow Tools

- 3.8 Server and Workstation Administration

- 3.9 JD Edwards EnterpriseOne Data Dictionary

4 Understanding Analytic Tools

- 4.1 Understanding Analytic Tools

- 4.2 JD Edwards EnterpriseOne Performance Monitor

- 4.3 JD Edwards EnterpriseOne AutoPilot

- 4.4 JD Edwards EnterpriseOne Virtual AutoPilot

5 Understanding Interoperability

- 5.1 Understanding Interoperability

- 5.2 JD Edwards EnterpriseOne Interoperability

- 5.3 JD Edwards EnterpriseOne Connectors

- 5.4 JD Edwards EnterpriseOne Business Services

- 5.5 JD Edwards EnterpriseOne Web Services Gateway

- 5.5.1 WSG Dispatcher

- 5.5.2 WSG Configuration Editor

- 5.5.3 WSG EnterpriseOne Adapter

- 5.5.4 WSG Order Promising Adapter

- 5.5.5 BPEL-PM

6 Viewing EnterpriseOne Tools Architecture and Implementation Phases

- 6.1 Understanding the Phases of Implementation

- 6.2 JD Edwards EnterpriseOne Architecture and Process Flow for Windows

- 6.3 Using JD Edwards EnterpriseOne Tools within Implementation Phases

Glossary

Index

List of Figures

- 6-1 JD Edwards EnterpriseOne Architecture and Process Flow for Windows

Preface

Welcome to the JD Edwards EnterpriseOne Tools Fundamentals Guide.

Audience

This guide is intended for anyone needing an understanding of the fundamentals of JD Edwards EnterpriseOne Tools technology.

This document is designed to introduce Oracle's JD Edwards EnterpriseOne Tools in a high-level manner and provide a structure for understanding the categories of and usage of the JD Edwards EnterpriseOne Tools technology.

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne minimum technical requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the cross-reference material in the Program Documentation at http://oracle.com/contracts/index.html for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.

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

This chapter contains the following topics:

- Section 1.1, "JD Edwards EnterpriseOne Tools Overview"

- Section 1.2, "JD Edwards EnterpriseOne Tools Implementation"

1.1 JD Edwards EnterpriseOne Tools Overview

JD Edwards EnterpriseOne Tools provides the underlying technology for Oracle's JD Edwards EnterpriseOne applications. All JD Edwards EnterpriseOne applications, such as Human Capital Management and Customer Relationship Management are built, deployed, and maintained using JD Edwards EnterpriseOne Tools.

With JD Edwards EnterpriseOne Tools you can:

- Develop new applications or customize existing applications.

- Administer applications that you have deployed within your organization.

- Provide decision support and reporting functionality to decision makers.

- Integrate JD Edwards applications with other JD Edwards applications or third-party applications.

The area of JD Edwards EnterpriseOne Tools contains over 40 tools, utilities, and technologies. This document provides two frameworks with which you can gain a better understanding of the delivered technology, how to categorize the tools, and when to use particular tools.

1.1.1 JD Edwards EnterpriseOne Tools Categories

This framework divides the JD Edwards EnterpriseOne Tools technologies, tools, and utilities into four categories:

- Development Tools.

- Administration Tools.

- Analytic Tools.

- Integration Tools.

1.1.2 Implementation Phases

This framework provides a sample set of implementation phases and lists the tools and technologies that are likely to be used or implemented within a particular phase. The implementation phases are:

- Installation.

- Application Configuration.

- System Configuration.

- Decision Support Configuration.

- Business Process Integration.

- Maintenance.

Note:
The implementation phases in this framework are intended to help you gain a better understanding of JD Edwards EnterpriseOne Tools. The implementation phases in no way imply strict dependencies between phases or tools. Every implementation is unique.

1.1.3 Other Sources of Information

This section provides information to consider before you begin to use JD Edwards EnterpriseOne Tools. In addition to implementation considerations presented in this section, take advantage of all JD Edwards sources of information, including the installation, release notes, documentation, and training courses.

In addition, 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.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Overview Guide.

- JD Edwards EnterpriseOne Tools System Administration Guide.

1.2 JD Edwards EnterpriseOne Tools Implementation

Implementing JD Edwards EnterpriseOne Tools requires the installation of the JD Edwards EnterpriseOne Tools CD within a supported environment as described in the JD Edwards EnterpriseOne Tools Installation.

2 Understanding Development Tools

This chapter contains the following topics:

- Section 2.1, "Understanding Development Tools"

- Section 2.2, "JD Edwards EnterpriseOne Report Design Aid"

- Section 2.3, "Report Printing Administration"

- Section 2.4, "JD Edwards EnterpriseOne Tables and Business Views"

- Section 2.5, "JD Edwards EnterpriseOne Form Design Aid"

- Section 2.6, "JD Edwards EnterpriseOne Batch Versions"

- Section 2.7, "JD Edwards EnterpriseOne Business Services"

- Section 2.8, "Event Rules and System Functions"

- Section 2.9, "JD Edwards EnterpriseOne Object Management Workbench"

- Section 2.10, "JD Edwards EnterpriseOne Data Structure Design"

- Section 2.11, "APIs and Business Functions"

2.1 Understanding Development Tools

The development tools that JD Edwards EnterpriseOne Tools provides offer a powerful application development environment in which you can build and customize JD Edwards applications to suit your specific enterprise needs quickly and easily. By using JD Edwards EnterpriseOne Tools development tools you can complete a variety of tasks including:

- Design and define application objects.

- Enable applications to serve different locations and languages while sharing the same data.

- Define end-to-end processes in a user-friendly, graphical design environment.

2.2 JD Edwards EnterpriseOne Report Design Aid

You can use JD Edwards EnterpriseOne Report Design Aid to create a variety of simple and complex reports. The interface is simple enough to use without programming expertise, yet powerful enough to create the most complex reports. You can also use JD Edwards EnterpriseOne Report Design Aid to create batch processes and reports.  JD Edwards EnterpriseOne Report Design Aid includes a director to you through the process of creating report templates. This Report Director presents multiple reporting options from which to choose. You can create custom Directors to aid in the creation of report templates. These Directors are configured to use report components to meet a specific reporting requirement. After using the director to create the initial report, you can enhance the report by:

- Inserting additional report sections

- Modifying properties

- Adding logic

- Further organizing the data

- Calculating totals

The design work space in JD Edwards EnterpriseOne Report Design Aid can be configured to compliment individual work preferences. You can:

- Modify the report view options.

- Select which toolbars and windows to display.

- Arrange windows.

You can use JD Edwards EnterpriseOne Report Design Aid with terminal server. Just like in a traditional client server configuration, a report template that is checked out using terminal server cannot be accessed by other users.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Report Design Aid Guide.

2.2.1 JD Edwards EnterpriseOne XML Publisher

JD Edwards EnterpriseOne XML Publisher automates the processing of XML output for the creation of pixel-perfect documents and reports. It reduces the high cost of producing, customizing, and maintaining business documents. Built on the open XSLFO standard, it provides a full range of reporting capabilities, including charts, formulas, watermarks, and graphics. Using a set of familiar desktop tools, users can create and maintain their own report formats based on data extracts from JD Edwards EnterpriseOne Reports.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Report Design Aid Guide.

2.3 Report Printing Administration

Report Printing Administration Technologies addresses the printing properties available in JD Edwards EnterpriseOne Report Design Aid, the printing properties presented at runtime, how to define printers for reporting, and the different output options available for JD Edwards EnterpriseOne reports.

The code enables you to create programs using structured and object-oriented techniques. JD Edwards delivers numerous functions, classes, methods, and APIs.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Report Printing Administration Technologies Guide.

2.4 JD Edwards EnterpriseOne Tables and Business Views

Tables and Business Views addresses three tools from the JD Edwards EnterpriseOne toolset: JD Edwards EnterpriseOne Tables Design Aid is used to create and modify tables, JD Edwards EnterpriseOne Business View Design Aid is used to create and modify business views, and the JD Edwards EnterpriseOne Table Conversion tool is used to convert tables and copy data between tables.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

2.5 JD Edwards EnterpriseOne Form Design Aid

JD Edwards EnterpriseOne Form Design Aid is used to create or modify JD Edwards EnterpriseOne interactive applications. Interactive applications are composed of forms, and a form is the interface between a user and a table. This interface should present the data logically and contain the functions that are necessary to enter and manipulate data.

See Also:

- Getting Started with JD Edwards EnterpriseOne Tools: Form Design Aid.

2.6 JD Edwards EnterpriseOne Batch Versions

JD Edwards EnterpriseOne Batch Versions is a tool that you use to create and process versions of report templates. You can use JD Edwards EnterpriseOne Batch Versions to:

- Create batch versions.

- Define processing options, data selection and data sequencing, and review version detail.

- Check out batch versions, check in batch versions, erase the check out, and copy version specifications to the enterprise server.

- Modify batch versions without changing the report template specifications.

- Submit batch versions for processing and override processing options, data selection, and data sequencing at runtime.

- Review batch version processing by using Browser, the report cover page, and logs for reporting.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Batch Versions Guide.

2.7 JD Edwards EnterpriseOne Business Services

JD Edwards EnterpriseOne provides interoperability with other Oracle products and third-party products and systems by natively producing and consuming web services. As a web service provider, JD Edwards EnterpriseOne exposes web services for consumption by an external system. As a web service consumer, JD Edwards EnterpriseOne calls external web services from within the JD Edwards EnterpriseOne business logic layer. JD Edwards EnterpriseOne sends event notifications as JMS messages through JMS Queue and JMS Topic.

See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.

See JD Edwards EnterpriseOne Tools 8.98 Business Services Development Guide.

2.8 Event Rules and System Functions

Event Rules and System Functions are used to create or modify event rules (ER) in JD Edwards EnterpriseOne applications. Event rules are connected to certain runtime events and instruct runtime how to respond to the conditions you choose to define.

Event rules (ER) are logic statements that you can create and attach to events. ER is initiated when events occur at runtime. JD Edwards EnterpriseOne software supports two kinds of Event Rules: Named Event Rules and Embedded Event Rules. You can attach multiple event rules to one event. The various kinds of event rules include:

- Conditional statements, such as If/Else/End If.

- While loops.

- Assignments.

- Calls to business functions.

- Form or report interconnections.

- Calls to system functions.

- Table I/O operations.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Event Rules Guide.

2.9 JD Edwards EnterpriseOne Object Management Workbench

JD Edwards EnterpriseOne Object Management Workbench is the primary component of the change management system for JD Edwards EnterpriseOne development. A change management system is vital to a productive development environment because it helps organize a myriad of development activities and helps prevent problems, such as when a developer intermixes components from different releases or when multiple developers simultaneously change an object. JD Edwards EnterpriseOne Object Management Workbench automates many of these change management activities.

See Also:

- JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

2.10 JD Edwards EnterpriseOne Data Structure Design

JD Edwards EnterpriseOne Data Structure Design is used to create and modify JD Edwards EnterpriseOne data structures. Data structures are composed of data items defined in the data dictionary and are used to pass data to and from interactive and batch applications.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Data Structure Design Guide.

2.11 APIs and Business Functions

APIs and Business Functions is used to create complex, reusable routines in C. Business functions can call APIs directly, and can in turn be invoked from event rules (ER).

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: APIs and Business Functions Guide.

3 Understanding Administration Tools

This chapter contains the following topics:

- Section 3.1, "Understanding Administration Tools"

- Section 3.2, "JD Edwards EnterpriseOne Configurable Network Computing Implementation"

- Section 3.3, "System Administration"

- Section 3.4, "Auditing Administration"

- Section 3.5, "JD Edwards EnterpriseOne Delta Process"

- Section 3.6, "JD Edwards EnterpriseOne Solution Explorer"

- Section 3.7, "JD Edwards EnterpriseOne Workflow Tools"

- Section 3.8, "Server and Workstation Administration"

- Section 3.9, "JD Edwards EnterpriseOne Data Dictionary"

3.1 Understanding Administration Tools

With Information Technology infrastructure becoming more complex, JD Edwards EnterpriseOne Tools offers the state-of-the-art tools to make maintenance easy and cost-effective. The JD Edwards EnterpriseOne Tools administration tools enable system administrators to manage the applications you have deployed within your organization. The administration tools enable you to perform numerous administrative tasks, such as configure security, monitor performance, troubleshoot, upgrade to new versions, apply patches, and transfer data from target to source systems. Most of the tasks can be completed using the same browser interface used for completing business transactions in JD Edwards applications.

3.2 JD Edwards EnterpriseOne Configurable Network Computing Implementation

JD Edwards EnterpriseOne Configurable Network Computing is an application architecture that enables interactive and batch applications, composed of a single code base, to run across a TCP/IP network of multiple server platforms and SQL databases. The applications consist of reusable business functions and associated data that can be configured across the network dynamically. The overall objective for businesses to provide a future-proof environment that enables them to change organizational structures, business processes and technologies independently of each other.

3.3 System Administration

System Administration provides the tools necessary to administer a JD Edwards EnterpriseOne configuration and the information necessary to troubleshoot different types of error conditions. System Administration also enables administrators to perform system maintenance and use logs to resolve common system and application issues.

See Also:

- JD Edwards EnterpriseOne Tools System Administration Guide.

3.4 Auditing Administration

The JD Edwards EnterpriseOne auditing and electronic signature tools provide a solution to the Food and Drug Administration's (FDA) acceptance of electronic signature and audit records for FDA-required records such as product submissions, batch records, and complaints. These tools enable you to comply with the FDA 21 CFR Part 11 regulation for submitting electronic records.

You can configure JD Edwards EnterpriseOne to generate an audit table when table records are inserted, updated, or deleted. The audit records contain data such as:

- Before and after values.

- Time and date of the transaction.

- The user that made the modification.

In addition, you can configure JD Edwards EnterpriseOne interactive and batch applications to require an electronic signature approval when a user tries to change the data on an application or submit a report. A record of the approval is recorded in the Signature table (F9500005). The table records this information:

- Approver of the change.

- Reason for the approval.

- Approver's user ID.

- User's role.

- Date and time of the approval.

The information in the audit and electronic signature tables can be viewed using the View Audit/Signature Information application (P9500005) or by generating reports (R9500004, R9500005, R9600006). The reports display all the audit and signature information in an easy to read Adobe Acrobat (PDF) file that can be printed to hard copy or saved in digital format.

See Also:

- JD Edwards EnterpriseOne Tools Auditing Administration Including 21 CFR Part 11 Administration Guide.

3.5 JD Edwards EnterpriseOne Delta Process

JD Edwards EnterpriseOne Delta Process is used to determine the development changes that have occurred in translation tables.

See Also:

- JD Edwards EnterpriseOne Tools Delta Process Guide.

3.6 JD Edwards EnterpriseOne Solution Explorer

JD Edwards EnterpriseOne Solution Explorer provides you with a convenient method for accessing Windows-based JD Edwards EnterpriseOne applications, and creating/maintaining JD Edwards EnterpriseOne task views for Web or Windows. Solution Explorer is comprised of the following three modes:

- Menu Design Mode
Use the Menu Design Mode to set up menus, tasks, task views, and task view roles.

- Menu Filtering Mode
Use the Menu Filter Mode to enable and disable tasks users assigned a certain role can perform.

- Task Launching Mode
Use the Task Launching Mode to navigate to development and administrative applications in JD Edwards EnterpriseOne using the Fast Path, or using the menu.

See Also:

- JD Edwards EnterpriseOne Tools Solution Explorer Guide.

3.7 JD Edwards EnterpriseOne Workflow Tools

JD Edwards EnterpriseOne Tools Workflow Tools enables you to automate the high-volume, formerly paper-based process into an email-based process flow across a network. Documents, information, and tasks pass from one participant to another for action based on a set of procedural rules. The result is an automated and efficient process with minimal user involvement, which enables you to streamline the existing business processes, increase efficiency, and reduce process time.

See Also:

- JD Edwards EnterpriseOne Tools Workflow Tools Guide.

3.8 Server and Workstation Administration

Server and Workstation Administration is used to extend an initial installation prototype environment to meet practical requirements and recognizes, addresses, and solves daily issues that arise in a dynamic enterprise. Server and Workstation Administration uses the flexibility of the Configurable Network Computing architecture to optimize the JD Edwards EnterpriseOne installation for the enterprise.

See Also:

- JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide.

3.9 JD Edwards EnterpriseOne Data Dictionary

JD Edwards EnterpriseOne Data Dictionary is used to create or modify Data Dictionary items for use in JD Edwards EnterpriseOne applications. JD Edwards EnterpriseOne Data Dictionary items not only define and describe data, but they also can trigger the runtime engine to react or process in certain ways by nature of their types. Furthermore, online help, error messages, term substitutions for different industries, and translations are all tied to Data Dictionary items.

See Also:

- JD Edwards EnterpriseOne Tools Development Tools: Data Dictionary Guide.

4 Understanding Analytic Tools

This chapter contains the following topics:

- Section 4.1, "Understanding Analytic Tools"

- Section 4.2, "JD Edwards EnterpriseOne Performance Monitor"

- Section 4.3, "JD Edwards EnterpriseOne AutoPilot"

- Section 4.4, "JD Edwards EnterpriseOne Virtual AutoPilot"

4.1 Understanding Analytic Tools

JD Edwards applications offer a wide range of query and reporting possibilities. These include the standard reports we deliver, as well as the reporting tools you can use to customize reports or create new ones. JD Edwards EnterpriseOne Tools reporting and decision support capabilities enable you to perform numerous tasks, such as create queries, create reports, and create online analytical processing (OLAP) cubes.

Your database contains a wealth of information that you've carefully entered, maintained, and secured for the ultimate purpose of generating timely, meaningful, presentation-quality reports as well as provide online analytical options. Our reporting and decision support capabilities enable you to access the data you need and present it in the form that is most useful for the decision makers in your organization.

4.2 JD Edwards EnterpriseOne Performance Monitor

JD Edwards EnterpriseOne Performance Monitor enables you to view realtime and historical performance data of your JD Edwards systems. JD Edwards EnterpriseOne Performance Monitor provides the information that you need to solve immediate performance issues and analyze trends in system performance. By default, JD Edwards EnterpriseOne Performance Monitor is disabled on a new JD Edwards EnterpriseOne installation. When you have a JD Edwards application environment running and you have set up the Performance Monitor, you can begin to capture and analyze JD Edwards EnterpriseOne performance data.

See Also:

- JD Edwards EnterpriseOne Tools Performance Monitor Guide.

4.3 JD Edwards EnterpriseOne AutoPilot

JD Edwards EnterpriseOne AutoPilot is an automated testing tool that you can use to create scripts to test the execution of JD Edwards EnterpriseOne applications and to perform repetitive tasks, such as loading data, entering sales orders, or creating screen shots.

See Also:

- JD Edwards EnterpriseOne Tools Autopilot Guide.

4.4 JD Edwards EnterpriseOne Virtual AutoPilot

JD Edwards EnterpriseOne Virtual Autopilot is an automated testing tool that is used to capture data and provide users with the raw material to build a virtual script that will accurately simulate JD Edwards software processes.

See Also:

- JD Edwards EnterpriseOne Tools Virtual Autopilot Guide.

5 Understanding Interoperability

This chapter contains the following topics:

- Section 5.1, "Understanding Interoperability"

- Section 5.2, "JD Edwards EnterpriseOne Interoperability"

- Section 5.3, "JD Edwards EnterpriseOne Connectors"

- Section 5.4, "JD Edwards EnterpriseOne Business Services"

- Section 5.5, "JD Edwards EnterpriseOne Web Services Gateway"

5.1 Understanding Interoperability

Interoperability is most often associated with software as a way to enable disparate software applications to work together. Interoperability makes it possible for third-party applications and JD Edwards EnterpriseOne to exchange information. Two approaches are used to achieve interoperability:

- Disparate systems adhere to published interface standards.

- Disparate systems use services that convert one product's interface into another product's interface "on the fly."

5.2 JD Edwards EnterpriseOne Interoperability

JD Edwards EnterpriseOne Interoperability discusses the interoperability models that third-party systems can use to exchange information with JD Edwards EnterpriseOne. A model is a way for third-party systems to connect to or access JD Edwards EnterpriseOne. JD Edwards EnterpriseOne supports four basic interoperability models:

- Web Services Gateway

- Connectors

- Messaging Adapters

- Batch Interfaces

These interoperability models are further categorized by model type. For example, the COM Connector and Java Connector are model types within the Connectors model.

Each model type is supported by one or more capabilities. Capabilities are ways to send information into or retrieve information from JD Edwards EnterpriseOne. For example, a third-party system can use the realtime events capability with the WSG, connectors, or message adapters models to retrieve information from JD Edwards EnterpriseOne. Capabilities supported by JD Edwards EnterpriseOne include:

- Synchronous request and reply

- Asynchronous outbound notification

- Asynchronous outbound request and reply

See Also:

- JD Edwards EnterpriseOne Tools Interoperability Guide.

5.3 JD Edwards EnterpriseOne Connectors

Connectors are point-to-point, component-based interoperability models that enable third-party systems and JD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOne connector architecture includes Java and COM connectors. The connectors accept inbound XML requests and expose business functions for reuse. Output from the connectors is in the form of an XML document. The connectors include:

- Java
The JD Edwards EnterpriseOne dynamic Java and Java connectors support realtime event processing. Java is a portable language, so you can easily tie JD Edwards EnterpriseOne functionality to Java applications.

- COM
The JD Edwards EnterpriseOne COM connector solution is fully compliant with the Microsoft component object model. You can easily tie JD Edwards EnterpriseOne functionality to Visual Basic and VC++ applications. The COM connector also supports realtime event processing.

See Also:

- JD Edwards EnterpriseOne Tools Connectors Guide.

5.4 JD Edwards EnterpriseOne Business Services

Business services are JD Edwards EnterpriseOne business function objects that are used for interoperability between JD Edwards EnterpriseOne and other applications or systems. Business services are written in the Java programming language and provide business service operations that access the business logic in JD Edwards EnterpriseOne for many supported business transactions, such as journal entries, exchange rates, accounts payable vouchers, inventory look-ups, pricing, sales orders, and so on. You use Oracle's JDeveloper tool and the Java programming language to create a business service. The JD Edwards EnterpriseOne web services framework provides a set of foundation packages that helps you create a business service. Each foundation package contains a set of interfaces and related classes. All business service classes extend from ServiceBusinessFunction.

See "Web Services Gateway Dispatcher Overview" in the JD Edwards EnterpriseOne Tools Web Services Gateway: Dispatcher Guide.

SeeJD Edwards EnterpriseOne Tools Business Services Development Methodology Guide for more information about developing business services.

5.5 JD Edwards EnterpriseOne Web Services Gateway

Oracle's JD Edwards EnterpriseOne Web Services Gateway (WSG) toolset provides an infrastructure that enables JD Edwards EnterpriseOne to natively produce and consume web services. This allows for basic point-to-point integration capability between JD Edwards EnterpriseOne and non-EnterpriseOne systems. WSG installs are consistent with the JD Edwards EnterpriseOne install processes. You can choose to install WSG when you install JD Edwards EnterpriseOne Tools 8.95 and later Tools releases. WSG provides components that include the following:

- Dispatcher

- Configuration Editor

- EnterpriseOne Adapter

- Order Promising Adapter

- Business Process Execution Language Process Manager (BPEL-PM)

5.5.1 WSG Dispatcher

The WSG Dispatcher package enables inbound and outbound communication with JD Edwards Enterprise Integration Gateway. The WSG Dispatcher package separates the integration business logic from the transport that is used for the communication, which enables other transports to be supported in the future without any change to the integration services.

See "Web Services Gateway Dispatcher Overview" in the JD Edwards EnterpriseOne Tools Web Services Gateway: Dispatcher Guide.

5.5.2 WSG Configuration Editor

The WSG Configuration Editor provides a user interface to manage information specific to individual integration production. To accomplish this, the Configuration Editor enables you to create integration options instead of using literal values in integrations. The Configuration Editor also enables you to maintain code and key cross-reference information.

See JD Edwards EnterpriseOne Tools Web Services Gateway: Configuration Editor Guide.

5.5.3 WSG EnterpriseOne Adapter

The WSG EnterpriseOne Adapter enables the exchange of information between JD Edwards EnterpriseOne applications and other heterogeneous systems. This adapter provides a flexible, easy-to-use mechanism for WSG-enabled applications to interface with JD Edwards EnterpriseOne. The EnterpriseOne Adapter, which must be installed on the WSG Integration Server, exposes business logic, realtime event generation and database access within J.D. Edwards EnterpriseOne.

See JD Edwards EnterpriseOne Tools Web Services Gateway: EnterpriseOne Adapter Programmer's Guide.

5.5.4 WSG Order Promising Adapter

The WSG Order Promising Adapter enables the exchange of information between the JD Edwards EnterpriseOne Order Promising application and other heterogeneous systems. This adapter provides a flexible, easy-to-use mechanism for WSG-enabled applications to interface with the JD Edwards EnterpriseOne Order Promising application. The Order Promising Adapter provides an entry point into the Order Promising application. The adapter sends notifications to Order Promising and handles request and response message types.

See JD Edwards EnterpriseOne Tools Web Services Gateway: Order Promising Adapter Programmer's Guide.

5.5.5 BPEL-PM

Web services enable the exchange of information between Oracle BPEL-PM and JD Edwards EnterpriseOne WSG. Interoperability between Oracle BPEL-PM and JD Edwards EnterpriseOne consists of web services that are created in EnterpriseOne WSG and consumed by Oracle BPEL PM as well as web services that are provided by Oracle BPEL PM and consumed by EnterpriseOne WSG. This certification document explains how to prepare adapter services, integration points, and notifications from WSG for consumption by Oracle BPEL. It also explains how WSG consumes Oracle BPEL service flows.

See Oracle Business Process Execution Language Process Manager (BPEL-PM) Integrations with JD Edwards EnterpriseOne WSG on the Oracle | JD Edwards Download web page

6 Viewing EnterpriseOne Tools Architecture and Implementation Phases

This chapter contains the following topics:

- Section 6.1, "Understanding the Phases of Implementation"

- Section 6.2, "JD Edwards EnterpriseOne Architecture and Process Flow for Windows"

- Section 6.3, "Using JD Edwards EnterpriseOne Tools within Implementation Phases"

This chapter provides overview information related to using JD Edwards EnterpriseOne Tools within a sample implementation framework.

Note:
The implementation phases in this framework are intended to help you gain a better understanding of JD Edwards EnterpriseOne Tools regarding how and when they may be used. The implementation phases in no way imply strict dependencies between phases. Every implementation is unique.

6.1 Understanding the Phases of Implementation

Although few implementations follow exactly the phases of a system development life cycle (SDLC) or implementation plan, the following implementation phases are provided as a framework through which you can gain an understanding of how specific JD Edwards EnterpriseOne Tools are intended to be used. This framework should be viewed as a high-level educational rather than a strict, implementation model.

Note:
Some JD Edwards EnterpriseOne Tools may be used in multiple phases of an implementation.

6.2 JD Edwards EnterpriseOne Architecture and Process Flow for Windows

These host server processes perform the indicated actions:

Figure 6-1 JD Edwards EnterpriseOne Architecture and Process Flow for Windows

All communications between the client and the host server occur using sockets. The communications between jdenet_n and jdenet_k occur with shared memory. jdenet_n and queue kernel communicate using the Job Control Status Master database table (F986110).

This text explains the process flow:

- During Windows system startup, jdesnet runs automatically, provided that it is installed to start automatically. Otherwise, it must be started manually.

- This information applies to the JD Edwards network service:

- The program is system\bin32\jdesnet.exe.

- Each time that a new server or workstation connects to this server, jdesnet might start another jdenet_n until the number of jdesnet and jdenet_n jobs equals the value in the maxNetProcesses field in the [JDENET] section of the JDE.INI file.

- Each time that a new request, such as a batch application or CallObj is submitted, jdesnet (and any jdenet_n processes) might start another jdenet_k process until the number of jdenet_k jobs equals value in the maxKernelProcesses field in the [JDENET] section of the JDE.INI file.

- Jdenet_n can be run manually by running system\bin32\jdenet_n.

- This information applies to the JD Edwards queue service:

- The program is system\bin32\jdesque.exe.

- The service runs the number of instances of queue kernels specified in the UBEQueues, PackageQueues, and SpecInstallQueues fields in the [NETWORK QUEUE SETTINGS] section of the JDE.INI.

- When a user submits a batch application, jdesnet or jdenet_n (as part of the host server) communicates with the client as follows:

- The host server programs are system\bin32\jdesnet.exe and system\bin32\jdenet_n.exe.

- The client environment is initialized.

- The client tells the host server (using a socket) to initialize its environment.

- The host server (for example, jdenet_n) initializes its environment and gets environment and user handles.

- The host server passes the environment and user handles to the client (using a socket).

- The client launches the batch application and then sends data to the host server (using a socket).

- If the maximum number of kernel (for example, jdenet_k; the k stands for kernel) processes has not been met, jdesnet or jdenet_n might start a new jdenet_k process.

- If the maximum number of jdenet_k processes has been met, jdesnet or jdenet_n puts the message in a queue for a jdenet_k process.

- The client frees the user environment.

- The client tells the host server (using a socket) to free the user environment for the server.

- The host server frees its user environment.

- The client tells the host server (using a socket) to free the environment for the server.

- The host server frees its environment.

- When the UBE Jdenet_k (the kernel) writes to the database (batch application only), this occurs:

1. The program is system\bin32\jdenet_k.exe.

2. Jdenet_k adds a record in the F986110 database table. The record has a status of W (Waiting).

- The Queue Kernel periodically checks the contents of table F986110 and launches a runbatch process.

- When runbatch processes the batch application, this occurs:

- The program is system\bin32\runbatch.exe.

- The system changes the status stored in table F986110 to P (Processing).

- The system starts the batch application.

- If the batch application completes successfully, it changes the status in table F986110 to D (Done).

- If the batch application does not complete successfully, it changes the status in table F986110 to E (Error).

- Unlike the many processes that execute when a batch application is submitted, jdenet_k performs the processing when a user submits a CallObject and these actions occur:

- Cannot start the service name service on the enterprise server.

- Error 1069: The service did not start due to a logon failure.

6.3 Using JD Edwards EnterpriseOne Tools within Implementation Phases

The following table describes the implementation phases.

Phase

Description

Installation

This phase covers the activities involved in installing the JD Edwards CDs and setting up your demonstration JD Edwards environment. A demonstration environment includes application servers, Process Scheduler servers, web servers, and a JD Edwards database.

Application Configuration

This phase covers the activities involved in configuring the JD Edwards applications you have purchased to fit the business processes of your organization. This phase includes setting up security access, customizing pages, creating custom batch programs, and so on.

System Configuration

This phase covers the activities involved in setting up and configuring the infrastructure that supports the deployment of your application configuration. For example, in this phase you would set up the servers, the security, and processes required to be in place for your end users to use the JD Edwards system to complete business transactions with a browser or other device.

Decision Support Configuration

This phase covers the activities involved with setting up the reporting and decision support systems that decision makers will use to gather business information. This includes developing predefined queries and reports, setting up a system to generate reports at scheduled times, set up access to OLAP cubes, and so on.

Business Process Integration

This phase covers the activities involved in setting up systems that enable your business processes to span multiple business areas, such as HR and Finance, within your organization. This phase includes setting up our XML-driven integration technology that enables disparate systems to exchange data seamlessly, and it also includes setting up JD Edwards Workflow to enable multiple users within a business process to easily route data and notifications to each other.

Maintenance

This phase covers the activities that are involved in maintaining your JD Edwards system once you have rolled out the system to your end users. This phase includes monitoring system performance, upgrading to new releases, applying patches, and so on.

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  G  I  J  M  O  P  R  S  T  V  W

A

administration tools

Auditing Administration, 3.4

Configurable Network Computing Implementation, 3.2

Data Dictionary, 3.9

Delta Process, 3.5

Internet technology, 3.3

Server and Workstation Administration, 3.8

Solution Explorer, 3.6

understanding, 3.1

Workflow Tools, 3.7

analytic tools

AutoPilot, 4.3

Performance Monitor, 4.2

understanding, 4.1

Virtual AutoPilot, 4.4

APIs and Business Functions, 2.11 application configuration, 6.3 architecture

enterprise servers

Windows, 6.2

Auditing Administration, 3.4 AutoPilot, 4.3

B

Batch Versions, 2.6

business process integration, 6.3

C

Configurable Network Computing Implementation, 3.2

Connectors, 5.3

D

Data Dictionary, 3.9

Data Structure Design, 2.10

decision support configuration, 6.3

Delta Process, 3.5

development tools

APIs and Business Functions, 2.11

Batch Versions, 2.6

Data Structure Design, 2.10

Event Rules and System Functions, 2.8

Form Design Aid, 2.5

Object Management Workbench, 2.9

Report Design Aid, 2.2

Report Printing Administration, 2.3

Tables and Business Views, 2.4

understanding, 2.1

E

Event Rules and System Functions, 2.8

F

Form Design Aid, 2.5

G

globalization, 2.5

I

implementation phases, 1.1.2

application configuration, 6.3

business process integration, 6.3

decision support configuration, 6.3

installation, 6.3

maintenance, 6.3

system configuration, 6.3

understanding, 6.1

installation, 1.2, 6.3 Internet technology, 3.3 interoperability

Connectors, 5.3

understanding, 5.1

Web Services Gateway, 5.5

J

JD Edwards EnterpriseOne Tools

category, 1.1.1

installation, 1.2

overview, 1.1

JD Edwards Pure Internet Architecture, 3.3

M

maintenance, 6.3

O

Object Management Workbench, 2.9

P

Performance Monitor, 4.2

phases of implementationimplementation phases, 6.1

R

Report Design Aid, 2.2

Report Printing Administration, 2.3

reporting toolsdecisionsupport tools, 4.1

S

Server and Workstation Administration, 3.8

Solution Explorer, 3.6

system configuration, 6.3

T

Tables and Business Views, 2.4

troubleshooting

Windows enterprise server, 6.2

V

Virtual AutoPilot, 4.4

W

Web Services Gateway, 5.5

Windows

enterprise server, 6.2

Workflow Tools, 3.7

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.