Business functions to use in services
You can work with services, customize and extend the business processing components, and make them usable in services.
A service typically consists of one or more messaging components (or components that define how messages to and from the service are handled), one or more utility components (such as email or alert handlers) and one or more business processing components. For information about the utility and messaging components available for services defined in the application, see the About organization modeling
The application is shipped with an extensive out-of-the-box business function library. Each function in this library is known as a standard API. For detailed information on the input, output, and behavior of each standard API, see the Javadoc.
You can also write your own business functions and use them in services. Each such function is known as an extended API.
While standard APIs can be aggregated and linked together to form more complex services, for most cases the API provides all the functionality that is required for a business transaction and is therefore not required to be linked together with other components or APIs. To ease working with this most common scenario, all of the standard APIs are automatically available for synchronous invocation without the need to model each one as a service using the Service Definition Framework. You can think of these APIs as "automatically defined" synchronous services. However, extended APIs and asynchronous invocation of these APIs requires that you explicitly model them as services first using the Service Definition Framework.