## JD Edwards EnterpriseOne Business Services Preface

This preface discusses:

- JD Edwards EnterpriseOne products.

- Additional sources of information.

- Common terms used in this guide.

### JD Edwards EnterpriseOne Products

This implementation guide refers to these JD Edwards EnterpriseOne products from Oracle:

- JD Edwards EnterpriseOne Accounts Payable

- JD Edwards EnterpriseOne Accounts Receivable

- JD Edwards EnterpriseOne Address Book

- JD Edwards EnterpriseOne Capital Asset Management

- JD Edwards EnterpriseOne Customer Relationship Management

- JD Edwards EnterpriseOne Expense Management

- JD Edwards EnterpriseOne Fixed Asset Management

- JD Edwards EnterpriseOne General Accounting

- JD Edwards EnterpriseOne Inventory Management

- JD Edwards EnterpriseOne Procurement

- JD Edwards EnterpriseOne Sales Order Management

- JD Edwards EnterpriseOne Service Management

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.

### Additional Sources of Information

Before you can run JD Edwards EnterpriseOne business services, you must be sure that the technical setup of your system and of your applications is correct. Additional, essential information about the technical system setup and application setup that is required to run JD Edwards EnterpriseOne business services appears in:

- JD Edwards EnterpriseOne 8.98 tools guides.

- JD Edwards EnterpriseOne 9.0 application implementation guides.

- Technical documents and presentations about business services and service-oriented architecture (SOA).

- JD Edwards EnterpriseOne 8.98 Business Services Documentation Map.

- JD Edwards EnterpriseOne 8.98 Reference Implementations Guide.

The steps that you need to take to configure your system are outlined in the JD Edwards EnterpriseOne 8.98 Business Services Documentation Map. This document includes each step that a user might need to complete, along with a reference to the documentation that describes each step. You should review all of the information that is included in the documentation map before attempting to set up and configure your system to use business services.

Reference implementations are complete beginning-to-end examples of implemented business services. Reference implementation business services are fully functional and can be used to test your business service environment.

Note. Standard tools and application guides are located on the documentation CD that accompanies your software. You can access all of the additional sources of information, including the technical presentations, the documentation map, reference implementation information, mapping spreadsheets, and additional documentation on Oracle's Customer Connection web site. From the main Customer Connection page, select Implement, Optimize and Upgrade. Then select Implementation Guide and then click on the Implementation Documentation and Software link. Scroll down the page and click on the Service Oriented Architecture (SOA) link.

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.

See Also

JD Edwards EnterpriseOne 8.98 Business Services Documentation Map

JD Edwards EnterpriseOne 8.98 Business Services Development Guide

JD Edwards EnterpriseOne 8.98 Business Services Development Methodology Guide

JD Edwards EnterpriseOne 8.98 Reference Implementations Guide

JD Edwards EnterpriseOne 8.98 Business Services Server Reference Guide

JD Edwards EnterpriseOne 8.98 Tools Interoperability Guide

JD Edwards EnterpriseOne Accounts Payable Preface

JD Edwards EnterpriseOne Accounts Receivable Preface

JD Edwards EnterpriseOne Address Book Preface

JD Edwards EnterpriseOne Capital Asset Management Preface

JD Edwards EnterpriseOne CRM Application Fundamentals Preface

JD Edwards EnterpriseOne Financial Management Application Fundamentals Preface

JD Edwards EnterpriseOne Fixed Assets Preface

JD Edwards EnterpriseOne Inventory Management Preface

JD Edwards EnterpriseOne Procurement Management Preface

JD Edwards EnterpriseOne Sales Order Management Preface

### About This Documentation

A companion Guide called About This Documentation contains general information, including:

- Related documentation, common page elements, and typographical conventions for guides.

- Information about using guides and managing the documentation library.

- Information on the International Organization for Standardization (ISO) country and currency codes used within documentation.

- A glossary of useful JD Edwards EnterpriseOne terms that are used in documentation.

See Also

About This Documentation Preface

Using Implementation Guides

Managing the Online Library and Implementation Guides

ISO Country and Currency Codes

Glossary of JD Edwards EnterpriseOne Terms

### Common Terms Used in this Guide

BPEL PM (Business Process Execution Language Process Manager | A plug-and-play, standard-based infrastructure for integrating systems, services and activities into process flows that are easy to change. BPEL PM can deliver both composite applications, such as web service orchestration or J2EE process flows, and data integration applications such as file-to-DB, DB-to-DB, or OracleApps-to-X.
Business Service | Business services are JD Edwards EnterpriseOne OMW objects that contains one or more java classes that expose public methods. The methods access logic in EnterpriseOne and support a specific step in a business process, such as adding a sales order or updating an address book record. A business service contains internal value object classes, which make up the signature for the public methods. Business services are managed by published business services, which are exposed to the user as a web service. Note. In the JD Edwards EnterpriseOne system, business services are managed by published business services. These published business services are exposed to the user as web services. Therefore, in the context of web services, business services are called web service operations. This documentation uses the terms business service and web service operation interchangeably.
Business Service Property | Business service properties are key value pairs that are referenced in the business service code. The properties enable users to change the functionality of a business service without changing the internal code of the business service. Properties also enable users to expose values to an end user of the business service. For example, a customer can use business service properties to specify a particular version of a program to use when processing data that is associated with the business service. Business service properties enable users to easily enter or change the version without having to change the code of the associated business service.
Class | See Java Class.
Component | Components are the extensible building blocks of a value object, and are comprised of compounds and fields, or fields alone.
Compounds | Compounds are collections of related fields within a value object. An example of a compound is Entity, which is made up of fields entityID, entityLongId, and entityTaxId.
ESB (Enterprise Service Bus) | A component of the BPEL PM product. An ESB provides integration infrastructure that combines SOA and event-driven architecture (EDA) functionality to enable organizations to respond to business changes quickly and easily. The integration of ESB with enterprise applications, BPEL PM, BAM, and web services managers enables organizations to leverage their existing technology investments.
Fields | Fields are the lowest-level elements in a value object. Fields store business data.
Interface | An interface defines the communication boundary between the consumer and provider of a business service. The interface is the consumer’s only exposure to the business service. It exposes the operation name and the defined messages that are sent back and forth. Both input and output data associated with a business service is considered part of the interface.
Java Class | A java class is a programming construct that is used to group related variables and methods. The class determines the type of object. For example, AddressBookProcessor.java is a type of business service which is a class.
Javadoc | Javadoc is a computer software tool that enables users to generate application programming interface (API) documentation in HTML format from Java source code. Javadoc is the industry standard for documenting Java classes.
Method | Methods are pieces of code that perform a specific function. A public method is available to be exposed. Some public methods are exposed as web service operations. Other public methods are not exposed, and are internal business services.
Payload | The payload is the business data that is sent by a web service. The payload for an EnterpriseOne business service is the value object.
Published Business Service | A published business service is a JD Edwards EnterpriseOne OMW object that contains or consists of one Java class, which publishes multiple methods. The published business service gives exposure to one or more business services by providing an interface that is available to the public as a consumable web service. Published business services contain value objects that contain data that is passed in and out of the related business services. Note. In the context of JD Edwards EnterpriseOne, published business services are exposed to consumers as web services. Therefore, in many cases, you will see the terms business service and web service used interchangeably. See Business Services
SOA (Service Oriented Architecture) | A technical architecture that enables organizations to extend the use of their business data beyond their native software systems. SOA enables users to expose native EnterpriseOne business services through web service standards.
Transport | The communication method that a business service uses. The transport defines how and where data is sent.
Value Object | Value objects are the payload, or input and output data, for a business service. Value objects provide the interface for a published business service or business service. Published business services use published value objects and business services use internal value objects. Value objects can contain both business data and warning messages that are produced during data processing. Value objects are comprised of components, compounds and fields.
Web Service | Web services enable software applications that are written in various programming languages and are running on various platforms to exchange data over computer networks. A web service is prescribed by its interface. The public interface of a specific web service is described by Web Services Description Language (WSDL). Web service communication consists of transport and payload. Early web service implementation used HTTP as a transport and SOAP to describe the payload. Current web service standards have adopted Web Service Invocation Framework (WSIF), allowing SOAP/HTTP, java, and other transport and payload types. Note. In the context of JD Edwards EnterpriseOne, published business services are exposed as web services. Therefore, in many cases, you will see the terms used interchangeably. See Published Business Service
Web Service Operation | See Business Service.
WSDL (Web Service Description Language) | An XML format for describing network services. WSDL describes the public interface of a web service.