Java Reference
In-Depth Information
To create an SLA, you create an alert rule (indicating the conditions under which the bus
should signal an SLA violation for a message flow) and a destination.
This feature not only alerts you of failures, but it also allows you to prevent failures by identi-
fying when the system is starting to reach a performance limitation. Alerts can be specific to a
single operation within a service or to the entire service. OSB ships with a set of alerts to get
you started out of the box, and you can create your own custom alerts.
Reporting
OSB also allows you to generate graphical reports based on the status of SLAs within your
system. These reports are based on near-time data collected by the bus, and allow you to
search, sort, and filter based on service name, date ranges, and error codes, as you would ex-
pect.
Security
While the security available in OSB is robust, it is tightly integrated with the WebLogic ap-
plication server. It allows for message- and transport-level security. One nice feature of OSB
is that you are provided with a set of commonly used WS-Policy XML files that you can link
with your service using a single line of code. You can also link your security policy using an
arbitrary HTTP URL within your service bus project.
OSB steers you toward its proprietary security mechanisms. The Web Services Security Policy
(WSSP) specification is relatively new and is supported by WebLogic 10. However, OSB sup-
ports features from WSSP 1.2 only at the transport level, not at the message level.
Supported specifications
The Oracle SOA stack supports a variety of specifications and other standards, including the
following:
▪ WS-Policy
▪ WS-ReliableMessaging
▪ XACML
▪ WS-Addressing
▪ SCA
▪ XPDL
▪ SAML
▪ PKI
