Database Reference
In-Depth Information
sume as a resource will reside on WLS. An exception could be Secure Gateway (the
Oracle API Gateway), which for good reasons we will touch upon in the
Securing service
interactions - Security Gateway
section, is not based on WLS.
As we mentioned previously, we will focus only on some core features enabled with the
SOA functionality, rather than on the WLS administration aspects. Firstly, we have to
mention that WebLogic 11
g
supports JEE 5 and JAX-WS 2.1 for the web service develop-
ment when the newest 12
c
release supports JEE6 and JAX-WS 2.2.
In the context of the SOA infrastructure, what is the most interesting for us is which re-
sources can be securely provided for utilization and how they can be managed on runtime.
Needless to say that resources such as JMS for asynchronous communications usually do
not belong to the particular application (if the application that encapsulates the communic-
ation channel is down, we can hardly rely on that channel anymore), so we need the JMS
server to handle our JMS messaging.
All these resources, and some more, are securely provided by WLS:
• EJB resources
•
Enterprise Information Systems
(
EIS
) resources
•
Java DB Connectivity
(
JDBC
) resources
•
Java Messaging Service
(
JMS
) resources
•
Java Naming and Directory Interface
(
JNDI
) resources
• Web service resources
• Work context resources
As WLS is compliant to JSR-255 JMX management extension standards, there are many
ways to manage shared recourses. For instance, the standard sequence to create JMS
Queue—
Creating a JMS Server -> Creating a Module -> Creating
Queue ->
—can be fulfilled using the WLS console or the WLS scripting tool. The basic
resources (such as JMS) can be combined to expose shared WLS services, which are also
known as managed WLS resources. Among others, we would like to mention one man-
aged service responsible for establishing a reliable messaging infrastructure—Oracle's
Store and Forward
(
SAF
) service.
The SAF service enables WebLogic Server to distribute messages reliably between applic-
ations that are spread across the WebLogic Server instances; effectively, the implementa-
tion of the Reliable Messaging SOA pattern. For example, with the SAF service, an ap-
plication that runs on or connects to a local WebLogic Server instance can reliably send
messages to an endpoint that resides on a remote server. If the destination is not available
Search WWH ::
Custom Search