Showing posts with label OSB. Show all posts
Showing posts with label OSB. Show all posts

Monday, February 2, 2026

How to create JMS Queue / Topic in Weblogic 12c / 11g

In this post I have tried to listed down all required steps to create JMS Queue which can be utilized for reliably transfer the data between two systems. Here is the steps by step process on how to create a JMS Queue in Weblogic 12c / 11g.

In order to complete below steps you must have created your JMS Server and JMSModule. If this is not done please go through the previous post on How to create JMS Server and JMS Module to complete the require steps.

  • Go to weblogic console and login to the domain
  • Go to domain Structure ->Services -> Messaging ->JMS Module
  • It will show you the list of all available module on the right pane of the window. Select "UserJMSModule" from the JMS Modules table.
  • This will land up in "Configuration" tab  under "UserJMSModule"
  • Click New in Summary of resource table and select Queue and click next
  • Enter the name of the queue as UserQ and JNDI name as eis/UserQ. and leave the template as none. This can be any values you want. Click on Next

  • Now Select the subDeployment as "UserSubDeployment" which we created in previous steps.and click on finish
  • You should be getting a Message JMS Queue is created successfully.
Now you are ready to use this queue for storing the messages.

Thursday, August 6, 2015

How to Create / Configure / Maintain JMS Server & Module in Weblogic 11g / 12c

In this post here i have tried to put across step by step process to create JMS Server , JMS Module etc to complete required full configuration for Weblogic JMS server for 12c. Steps will remain same for weblogic 11g as well.


  • Login to Weblogic console and go to Domain Structure -> Services -> Messaging
  • Select JMS Server
  • Create a new JMS Server page will open, enter below details
  • Click Next
  • On the next screen select Target. It should be the server where you want to create this JMS Server.
  • Click Finish 
  • Now we have JMS Server and we need to add JMS Module 
  • Go to Domain Structure -> Services -> Messaging -> Select JMS Module
  • Click on New button to create new JMS Module
  • Enter required information in create new JMS page
    • Name : UserJMSModule
    • Descriptor : UserJMSModule
    • Location in Domain : leave it blank to create it at default location and click Next
  •  On the next page select appropriate target server where you want to deploy this JMS Module and select Next
  • In the next window leave the check box "Would you like to add resources to this JMS system module?" unchecked and click finish
  • Message should be displayed as "The JMS module was created successfully". 
  • Under settings for UserJMSModule go to subdeployment tab and click New
  • Provide the name of subdeployment as "UserSubDeployment" and click next
  • Select the previously created "UserJMSServer" and click on finish and message should be displayed as "Subdeployment created successfully"
  • Click on Activate the changes to make the changes available for use in the domain.









Thursday, October 6, 2011

Why Oracle Service Bus 11g ? Key Benefits and Advantages

This blog covers key benefits and advantages we can achieve with the implementation of Oracle Service Bus 11g. Actually I have been asked by Client to list down the capabilities they will get with the Oracle Service Bus 11g Implementation and this is what they got from me and lead to this blog finally.

1. Service Virtualization :

                      A core principle of SOA is to ensure that any service consumer can access any service provider - and from any platform. This has been considered as key principle in OSB and it provides robust way of Vitalizing the Service. It’s a great value add in SOA Architecture.

2. Loose Coupling

                     OSB provides loose coupling by mediating between Service provided and Consumer. Without mediation Service consumer and provider will create dependency to each other. A change in single side provider/consumer will lead to the change dependent consumer/provider respectively. OSB bridges the gap of transport, message format, security technology etc.

3. Location Transparency

                     It’s a strategy to hide physical location of actual physical location of service endpoints from the Service Consumer. All Service consumers should know only single logical machine & port name for each service. This allows for greater flexibility when managing your services. You can add, move, prioritize and remove service endpoints as needed without needing to recompile your service consumer again.

4. Seamless Connectivity

                     While newer applications may expose services over standard, easily consumable interfaces such as SOAP, an overwhelming majority of the services available in enterprises are still locked in legacy systems, from mainframes to custom applications. The first task of an OSB is to ensure that all these existing assets can be easily accessed and integrated. An OSB offers rich and comprehensive connectivity options to standard interfaces (SOAP, messaging, etc.) and also to packaged applications and legacy systems via adapters such Siebel Adapter, Peoplesoft Adapter etc.

5. Routing

                     After having a seamless connectivity next task is that data and messages need to flow reliably. OSB offers efficient, secure and reliable transport options. OSB also provides advance routing facilities to determine where the data needs to go. Such routing can be done based on headers, content or other external rules.

6. Performance

                      OSB is stateless & light weight; hence provide the excellent performance result under stress conditions as well.

7. Transformation

                       Oracle Service Bus provides run time transformation capability and support industry standard for middleware :XML, XSLT, XQuery & XPath.

8. Support for Event Driven Architecture

                       Oracle Service Bus support Oracle’s latest Event Driven Architecture.

9. Security & Policy

                        OSB provides centralized way of implementing the Security for Integration which results into highest level of standardization and control on security issues. Security is best enforced using policy driven framework because it allows to implement security details outside of the Application & easy to maintain. This makes it complete pluggable component & highly Agile which can be changed without modifying the actual application as per the organization policy’s and compliance.

10. Service Polling

                       Oracle Service Bus supports service polling. This allows to OSB to automatically detect live service and remove others from the list. This has a significant impact in performance.

11. Load balancing & Failover

                       Oracle Service Bus supports multiple load balancing algorithms to load balance between endpoints. It automatically detects a failover and removes it from Load balanced urls.

12. Service Throttling

                       Service throttling is a new feature in Oracle Service Bus which allows to restrict the load for particular service. This has great value when it comes to Service up time.

13. Monitoring

                       Oracle Service Bus provides two way monitoring.
Proactive Monitoring: Here Integrator can monitor the dashboard and check the performance of the service bus which can help to tune the server effectively. Tracking the server performance over time can help to plan capacity planning well in advance.

Reactive Monitoring: Here OSB will monitor the Server and look for specific conditions to occur and it will automatically sends the Alert to users, Admin etc. Alert can be in the form of Email, JMS, SMS etc.

14. Message Validation

                       Oracle Service Bus support normal data level value check validation as well as Schematron Validation.

15. Value Added Feature

                  a. Support for Domain Value Map

                  b. Support for Cross Reference

                  c. Support for Package application Adapters

                  d. Support for Advance message formats such as SWIFT and FIX in financial Service Domain.

Friday, November 26, 2010

Difference & New features in Oracle Service Bus 11g

  1. Service Result Cache with Coherence :
    • Oracle Coherence 3.5
    • Oracle Service Bus now supports service result caching for business services with Coherence. Oracle Coherence is an in-memory data grid solution that lets organizations predictably scale mission-critical applications by providing fast access to frequently used data.
      Service result caching allows caching the response from a business service. This can dramatically improve performance if the response from the business service is relatively static. Oracle Service Bus uses a single cache for all business services. Only valid/correct results from business services are cached.
       
  2. Transaction :
    • With Oracle Service Bus, you can configure a proxy service to start and execute its message flow in the context of a JTA global transaction for non-transactional inbound transports (such as HTTP and JMS with a non-XA connection factory). In prior releases, the proxy service message flow executed in the context of a JTA global transaction only when the inbound transport started/propagated a global transaction (such as JMS/XA or SB with the transaction propagated).
    • With Oracle Service Bus, it is possible to execute both the request and the response pipelines in the context of the same JTA global transaction for non-synchronous inbound endpoints as well. 
  3. JMS Object Message :
    • In Oracle Service Bus, the JMS transport is enhanced to receive and send Java Objects to and from JMS queues/topics. The support is enabled by configuring a proxy or business service to have the Service Type Messaging:Java.
  4. JCA Adapters :
    • Oracle Service Bus provides support for Oracle SOA Suite 11g Release1 Patch Set 2 (11.1.1.3.0) JCA adapter artifacts. New Oracle Service Bus resource types for JCA Bindings and TopLink/EclipseLink mapping XML files are now available, as is support for normalized message properties in the transport headers. Upgrade for Oracle Service Bus 10g Release 3 JCA artifacts is seamless.
      Certification for File and BAM adapters has also been added. Automatic upgrade of Oracle Service Bus 10g Release 3 services using JCA adapter artifacts based on Oracle SOA Suite/JDeveloper 10g Release 3 is provided.
  5. New Transport : 
    •  Newly introduced JEJB transport for invoking EJB 3.0. 
    • It also support exposing proxy service as EJB 3.0 stateless session bean.
  6. Split Join Enhancements :
    • Transaction Support : can execute within context of JTA transaction
    • Wait : can halt execution of branch for specified duration
  7. Transport Enhancements :
    1. JMS Failover For Request/Response Pair : For both Correlation ID and Message patterns, Oracle Service bus provides enhanced high availability by letting you specify a response URI  ( any service account ) for each request URI in request/response JMS Business Service.
    2. Email Load Balancing : Oracle Service Bus 11g lets you specify multiple endpoint URLs for load balancing.