Database Reference
In-Depth Information
WebLogic as the integral component of all infrastructures, abstracting, sharing and monit-
oring resources, is the key contributor to Service Autonomy. Using the WLS Administra-
tion console or scripting tools, Work Manager can assign or revoke computing power to
the installed application and components, thus increasing or decreasing their runtime
autonomy. The clustered implementation controlled by WLS node manager(s) increases
SOA applications' resiliency and high availability. Consequently, because of high availab-
ility, abstraction, and visibility, all the servers' resources are highly reusable in a very con-
trollable manner (thanks to Work Managers), and as a result, are composable. The unifica-
tion of the resource types and the ways of resource discovery and management open the
door for the implementation of the Canonical Resource SOA pattern; this helps to present
all components of the underlying technical infrastructure as unified blocks, easily shared
and consumed by different services. Elastic resource provisioning based on the simplified
replication model, specific for Cloud (mostly for 12
c
, but 11
g
also has some support),
helps to avoid the decreasing of service autonomy during the implementation of the Ca-
nonical Resource pattern.
Again, we have to stress the fact that WLS cannot guarantee the employment of all of
these principles and characteristics alone in your architecture. Only basic SOA patterns,
such as Reliable Messaging and Canonical Resources for some elements, can be provided
out of the box. We have to architect our components right from the start to achieve a desir-
able level of Composability.
There are some more things on the technical side related to SOA, which are not supported
by WLS (11
g
and 12
c
):
• No OSGi support. Even though it was said that WebLogic 12
c
uses OSGi for in-
ternal modularization and to deliver products such as Oracle's
Complex Event
Processor
(
CEP
), there is no direct support for this standard. For instance, if you
are developing components for unmanaged devices, and you need to implement
the dynamic component model managed remotely, Fuse/ServiceMix ESBs could
be a better choice.
• Limited JBI support. Same as previous.
• No OAUTH 2.0 support for RESTful services. You should rely on a secure peri-
meter solution.
The GlassFish application server could be the alternative for WLS, but we must remember
that it isn't a strategic product; not all OFM products will be supported and some enter-
prise features will not be available.
Search WWH ::
Custom Search