Service Integration 3-7
■
Section 3.2.2, Transformation Maps
■
Section 3.2.3, JARs
■
Section 3.2.4, WSDLs
■
Section 3.2.5, Proxy Services
■
Section 3.3.3, Service Accounts
■
Section 3.2.6, Service Key Providers
■
Section 3.2.7, Alert Destinations
■
Section 3.2.8, JNDI Providers
■
Section 3.2.9, SMTP Servers
3.2.1 Schemas and Data Types
Schemas describe types for primitive or structured data. XML Schemas are an XML vocabulary that describe the rules that XML business data must follow. XML Schemas
specify the structure of documents, and the data type of each element and attribute contained in the document. XML schemas can import or include other XML schemas.
For information on how to create schemas using the Oracle Service Bus Administration Console, see Adding XML Schemas in XML Schemas in the Oracle
Fusion Middleware Administrators Guide for Oracle Service Bus.
Oracle Service Bus uses a metadata language called Message Format Language MFL to describe the structure of typed non-XML data. The Oracle Format Builder tool
creates and maintains metadata as a data file called an MFL document. For information on how to create MFL documents, see the Oracle Fusion Middleware
Developers Guide for Oracle Service Bus.
3.2.1.1 Type System
Oracle Service Bus has a built-in type system that is available for use at design time. When creating an XQuery expression in a condition, in-place update action, or
transformation, the variable can be declared to be of a given type in an editor to assist in easily creating the XQuery. The types can be the following:
■
XML schema types or elements
■
WSDL types or elements
■
MFL types
3.2.2 Transformation Maps
Transformation maps describe the mapping between two disparate data types of different source and destination services. Oracle Service Bus supports data mapping
using either XQuery or the eXtensible Stylesheet Language Transformation XSLT standard. In addition, MFL described data is automatically converted to the equivalent
XML for transformation with XQuery or XSLT. The resulting XML is automatically converted to MFL if the target service requires it.
3.2.3 JARs
A JAR Java ARchive is a zipped file that contains a set of Java classes. It is used to store compiled Java classes and associated metadata that can constitute a program. A
JAR acts like a callable program library for Java code elements so that a single
3-8 Oracle Fusion Middleware Concepts and Architecture for Oracle Service Bus
compilation link provides access to multiple elements, rather than requiring bindings for each element individually.
JAR files can be registered as reusable Oracle Service Bus resources. They are used in Java callout actions that provide a Java exit mechanism, EJB-based business services,
and Tuxedo-based business services. For more information on JAR resources, see JARs in the Oracle Fusion Middleware Administrators Guide for Oracle Service Bus.
3.2.4 WSDLs
