Sonic MQ 8.0 with Websphere Integration Developer 6.2

SonicMQ, is a Java Message Standard (JMS) - based messaging server. JMS provides a common set of interfaces, messaging concepts, and programming strategies, and makes it easy to write business applications that asynchronously send and receive critical business data and events.

Steps to Connect Sonic MQ with WID :

1. Place the Required jar files into lib\ext of WID62 :
 Get the Following Jar files from Sonic MQ lib Directory and Place them into following folder " IBM\WID62\runtimes\bi_v62\lib\ext ".
              * jndi.jar
              * mfcontext.jar
              * sonic_Client.jar
              * sonic_Crypto.jar
              * sonic_XA.jar
              * broker.jar
              * sonic_mgmt_client.jar

2. Create Topic in Sonic MQ :
            Name : SONIC_SAMPLE
3.  Create LookUp Name for the Topic in JMS Administered Objects in Sonic MQ :

Lookup Name is the Topic Alias name to which it is specified and we need to create JNDI for this Lookup name in ed in Admin Console of WAS.
Destination Name is the Topic Name in the Sonic MQ.
Normally we create JNDI for the Queue or Topic for the Websphere MQ but when we work with Third Party MQ Providers like Sonic MQ  we need to Create JNDI for the Alias name of the Topic which is specified in the JMS Administered Objects.

4. Creating Connection Factory Names and specifications :

Create a Connection Factory as mentioned below
Lookup Name : " Sonic_ConnectionFactory"
Factory Type : " TopicConnectionFactory"
Connection URL : " tcp://localhost:2506"
Default Username : " Administrator"
Password : "Administrator"

5. Create JMS Provider in Admin Console of WAS.

 Name of the JMS Provider : " Sonic MQ Provider "
Class Path of the jar files : " path of the jar files where we placed "
External initial context factory  : " com.sonicsw.jndi.mfcontext.MFContextFactory "
External provider URL  : " tcp://localhost:2506 " ( Give host name where the sonic mq is installed ).

6. Create JNDI for TopicConnection Factory in Admin Console :

Name : "Sonic_ConnectionFactory"
Type : Topic
JNDI Name : " jms/Sonic_ConnectionFactory"
External JNDI Name : "Sonic_ConnectionFactoryb"
Component Managed Authentication Alias : Give some name which contains :  username / password ( Administrator/Administrator )

7. Create JNDI for Topic in Admin Console :
Here we need to create JNDI for Topic which is already created in Sonic MQ. Here we need to observe that we should create JNDI for Topic Look up name of specified Topic i.e to this " SONIC_SAMPLE_LOOKUP " we need to create JNDI.

7. Specify the Bindings of Import and Export in the Assembly Diagram :
7.1 Import :
Now Take an Import into Assembly Diagram. and Give an Interface to it.
then Specify Binding as " GenericJMSBinding ". Specify JMS messaging domain " Publish-Subscribe",  and Provide JNDI names for Both Topic Connection Factory and Topic.

7.2 Export :
Now take a Export in Assembly Diagram.and Give an Interface to it.then Specify Binding as " GenericJMSBinding ". Specify JMS messaging domain " Publish-Subscribe",  and Provide JNDI names for Both Topic Connection Factory and Topic. In additional that we need to specify the Listener Port. and this listener Port also to be created by us.  

9.The Import in the Assembly Diagram as shown below.

10.Creating Listener Port for Export :

Open Admin Console -> Application Servers -> server1->Message Listener Service ->  Listener Ports. and then Create Listener port specified in the Export in Assembly diagram with the Appropriate JNDI Names of Topic Connection Factory and Topic.

Now save all the changes and Deploy it into Websphere Process Server. To Test this flow Right Click on Import and choose Test Component. then Run the Flow.

The Result of this flow is the data goes to the Sonic MQ when we run the flow  and the Through the Export the flow will get the same data From Sonic MQ and It prints in the Java Component.

Thank You.

Products From Websphere to Choosing

             You can use WebSphere to build and monitor an infrastructure to support your on demand business, and to build and extend applications that run on that infrastructure. Choosing the product depends on the business requirements. These are divided into various interaction types.
1.People Integration :
        People Integration capabilities enable customers, employees, and business partners to interact with business information, applications, and business processes, at any time from anywhere.
       Example : Using these capabilities, you could automate your call center functions, and then authorize selected employees, customers, and business partners to access these functions from their personal computers, cell phones, and PDAs.
       Products from Websphere : WebSphere Portal, WebSphere Voice.

2.Process integration :
       Businesses can use the Process integration capabilities to model, choreograph, monitor, and optimize business processes to keep them in line with strategic business goals.
       Example : You could model a key business process, then simulate it, refine it, enable people to interact with it in convenient ways, put it into production, monitor it, fine-tune it, and then quickly and intelligently adapt it, when your business needs change.
       Products from Websphere : WebSphere Business Modeler, WebSphere Business Monitor, WebSphere Process Server, WebSphere Integration Developer, WebSphere DataPower SOA Appliances.

3.Information integration :
       Information integration capabilities let you create a consistent, unified view of structured and unstructured information from disparate sources, and to manage and synchronize product reference information.
       Example : You could create a free-form search across all your information assets, including Web sites, relational databases, file systems, newsgroups, portals, collaboration systems, and content management systems.
        Products from Websphere : IBM Information Integration, WebSphere Commerce.

4.Application integration :
        The application integration capabilities provide a wide variety of services to support reliable and flexible flow of information across applications, which could be running in different enterprises.
        Example : You could simply exchange messages between two applications, or, if your business needs are more involved, you could create a flexible, service oriented architecture to support systematic information exchange across a wide variety of applications running on different company servers, platforms, and in multiple languages.
        Products from Websphere : WebSphere Message Broker, WebSphere Enterprise Service Bus, WebSphere Partner Gateway, WebSphere Transformation Extender.

5.Application and transaction infrastructure :
        The WebSphere application infrastructure enables you to build, deploy, integrate, and enhance new and existing applications.
        Example : You can Web-enable and extend legacy applications, and enable them to run in a Java environment.
        Products from Websphere : CICS Transaction Server, WebSphere application servers.

Thank You.

What is WebSphere ?

                 WebSphere is IBM's integration software platform. It includes the entire middleware infrastructure such as servers, services, and tools needed to write, run, and monitor 24x7 industrial-strength, on demand Web applications and cross-platform, cross-product.WebSphere is a modular platform based on industry supported open standards. You can plug your existing assets into WebSphere using trusted and enduring interfaces, and you can continue to extend your environment as your needs grow. WebSphere runs on many platforms including AIX, HP Unix, i5/OS, Linux, Sun Solaris, Windows, and z/OS.                                                                                                WebSphere Application Server is the base for the infrastructure, everything else runs on top of it. It supports SOA and non-SOA Environments. WebSphere Process Server, which is based on WebSphere Application Server, and WebSphere Enterprise Service Bus, provide the foundation for service-oriented architecture (SOA). Collectively, they support the use of business rules to drive applications that support business processes. High performance environments also use WebSphere Extended Deployment as part of their base infrastructure.
                    IBM provides extensive tools and facilities to help you build, run, manage, and optimize your WebSphere applications. WebSphere tooling is based on industry open standards such J2EE and Eclipse, and they use common installation, administration, security, and programming models.  

Thank You.