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.
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.
Source files, descriptors, and so on that are managed for business service development and are needed for the business service build process.
A method that accesses resources provided by the business service framework.
Configuration files include, but are not limited to, interop.ini, JDBj.ini, and jdelog.properties.
Utility services installed in a BPEL/ESB environment that are used to access JD Edwards EnterpriseOne orchestration cross-reference data.
A framework needed by an integration developer to develop and manage business services.
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.
Parts of the business service foundation that are specifically for supporting business service development.
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.
Key value data pairs used to control the behavior or functionality of business services.
An EnterpriseOne application for developers and administrators to manage business service property records.
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.
A unique name that identifies the business service property globally in the system.
A utility API used in business service development to access EnterpriseOne business service property data.
A source management system, for example ClearCase, where business service artifacts and build files are stored. Or, a physical directory in network.
The physical machine where the business services are located. Business services are run on an application server instance.
One type of business service artifact. A text file with the .java file type written to be compiled by a Java compiler.
The structural representation of a business service value object used in a C-business function.
A utility used to create a business service value object template from a business service value object.
The data used to tie HTTP responses with requests that consist of business service name and method.
A WLS instance started by and running wholly within JDeveloper.
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).
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.
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.
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.
An artifact that JDeveloper uses to organize project files. It contains one or more project files.
Published business services web service deployed to a production application server.
EnterpriseOne service level logic and interface. A classification of a published business service indicating the intention to be exposed to external (non-EnterpriseOne) systems.
Information about a published business service used to determine relevant authorization records. Published business services + method name, published business services, or *ALL.
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).
A coding technique that enables an administrator to manipulate site-specific variables that affect the execution of a given process.
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.
An XML document that provides the structure for a soft coded record.