Introduction and Features of Oracle Service Bus

Hi Friends,

I have started some hands on OSB i.e . (Oracle Service Bus) for my new project.so have found some intro and features of OSB.

So today we will talk about introduction of Oracle Service Bus and itz features...

Oracle Service Bus (OSB) :

Oracle Service Bus is at the heart of Oracle’s comprehensive business integration solution and belongs to the Oracle Messaging product line.

Oracle Service Bus is primarily targeted for managing different types of services, and providing traditional message brokering across heterogeneous IT environments.

Oracle Service Bus is a proven market-leading Enterprise Service Bus (ESB) built from the ground up for SOA lifecycle management that provides foundation capabilities for service discovery and intermediation, rapid service provisioning and deployment, and governance.

Oracle Service Bus is a proven, lightweight and scalable SOA integration platform that delivers low-cost, standards-based integration for high-volume, mission critical SOA environments.

It is designed to connect, mediate, and manage interactions between heterogeneous services, legacy applications, packaged applications and multiple enterprise service bus (ESB) instances across an enterprise-wide service network.

Oracle Service Bus provides built-in management and monitoring capabilities and supports out-of-the-box integration with SOA Governance products.

Functional Features of OSB :

The functional features of Oracle Service Bus can be categorized into the following functional layers:

• Messaging Layer: that reliably connects any service by leveraging standards web service transports, traditional messaging protocols and configuration of enterprise-specific custom transports.
• Security Layer: a rapid service configuration and integration environment that abstracts policies associated with routing rules, security, and service end-point access.
• Composition Layer: a meta-data driven feature-rich configuration interface for service discovery and validation capabilities for automatic import and synchronization of services with UDDI registries, allows message flow modeling, transformations, third-party service callouts and a test console.
• Management Layer: a service management environment that includes dynamic service and policy configuration, centralized usage and performance monitoring, and management of services - not just Web services, but also Java, .Net, messaging services, and legacy end points.

Feature Benefits (OSB):

Oracle Service Bus Features and Benefits :

Functionality	Functional Feature	Business Benefit
Message Routing	Configuration-driven intelligent, content-based and identity-based routing	Rapidly respond to business needs by quickly configuring routing rules based on changes to business rules or existing IT systems, without coding
Message Transformation	Dynamic message transformation based on XQuery or XSLT, supporting multiple message formats	Flexibly adapt to evolving SOA and integration project scenarios through the ability to dynamically transform and route services using simple and/or complex routing rules and/or message payloads
Service Registry	Automated or administrator-driven interoperability with UDDI V3 registries for service publishing and reuse	Increase ease of re-use by automatically discovering existing services and exporting new services to the service registry
Service Provisioning	Simplified service provisioning	Increase ease of managing multiple versions of services, simplify and speed deployments by eliminating build-test development cycles
Message Security	Optimized, pluggable, policy-driven transport and message level security	Leverage existing investments in security infrastructure and seamlessly broker between multiple security frameworks
Service End-point Interoperability	Extensibility and expanded service end-point support	Extend solution to accommodate unique IT requirements using infrastructure with certified interoperability with multiple standards, protocols, and vendors
Service Level Agreements	Rules-driven, configurable Service Level Agreement (SLA) enforcement	Gain visibility and control by enabling users to set SLAs based on a number of factors and alerts when the SLAs are not met
Message Transport	Extensible support for heterogeneous transports between service end points including custom transports via the Custom Transport SDK	Provides flexibility to leverage existing investments in disparate systems and/or ensure smooth transition from older to newer systems
Message Brokering	WS-I compliant Intelligent messaging brokering with support for multiple transport types, message formats	Ensure investment protection and leverage existing infrastructure through the ability to orchestrate services from existing IT systems with disparate messaging protocols without needing to change the systems and styles
Service Availability	Proactive infrastructure health and availability monitoring with JMX and SNMP	Maintain health and availability of the SOA through easy configuration of support of performance metrics and SLAs using a built-in, feature-rich dashboard OR 3rd party performance management systems.
Service Monitoring Dashboard	Flexible, graphical, and embedded management and monitoring dashboard	Automatically monitor and manage status of performance metrics and SLAs using a built-in, feature-rich dashboard or 3rd party performance management systems. Proactively take corrective action based on alerts.
Service Deployment	Easy, customizable programmatic or console-driven deployment	Ability to enforce governance and speed deployments

It's just an introduction for Oracle Service Bus. I hope it helps you in understanding OSB.



Regards,
Ajinkya Vichare

Configure log4j in weblogic server

Hello Everyone,

Today we will discuss about Configure log4j in weblogic server :

Step 1. Copy log4j-1.2.9.jar & wllog4j.jar under domain_root/lib folder.

Step 2. Create log4j.xml and drop it under domain_root folder. If you have log4j.xml inside the application(EAR/WAR), I would recommend to move outside EAR/WAR as
changing severity (log level) would require re-deployment. To avoid this, we can move log4j.xml into domain root folder but again the server needs to be bounced.
But there is a fix.

Step 3. Login to weblogic server console. Go to Servers -> Admin Server-> Logging.
Click on advanced mode. Change the logging implementation from JDK to Log4J. 

Click save.

Step 4. Activate changes. Re-start the admin server.

This should enable log4j and should write logging into log file mentioned in log4j.xml or properties file.

Hang on! There is a catch here. Say now I want to change the log level from DEBUG into WARN or ERROR. 

How do i do? 

We go to log4j.xml and change the level.
Now how does this change take into effect? It needs bouncing of the server.
I have given below sample log4j.xml for your reference...

log4j.xml:

 <?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE log4j:configuration SYSTEM

"log4j.dtd">
<log4j:configuration>
 <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
   <layout class="org.apache.log4j.PatternLayout">
     <param name="ConversionPattern"
            value="%d [%t] %-5p %c - %m%n"/>
   </layout>
 </appender>
<appender name="FILE" class="org.apache.log4j.RollingFileAppender">
   <param name="File" value="/log/myApp.log"/>
   <param name="Append" value="true"/>
   <layout class="org.apache.log4j.PatternLayout">
     <param name="ConversionPattern" value="%d{ISO8601} %t %-5p %c{2} - %m%n"/>
   </layout>
 </appender>
 <logger name="org.apache">
   <level value="WARN"/>
 </logger>
 <logger name="org.springframework">
   <level value="WARN"/>
 </logger>
 <root>
   <level value="DEBUG"/>
   <appender-ref ref="FILE"/>
<!--   <appender-ref ref="CONSOLE"/> -->
 </root>
</log4j:configuration>

I have disabled log4j to write into weblogic console by commenting out. If you want it enable den you can do it by uncommenting

I hope it will help you in configuring log4j in weblogic server. And would also like to thank google and peoples who shares their views on the same.

Enjoy working in Middleware.....

Regards,
Ajinkya Vichare

ajinkya-vichare.blogspot.com