Hii im using wso2 enterprise service bus to connect to a OracleDataBase. I have succesfuly connected, but now i would like to set a request from a client that is connected to my service bus.
The problem is that i dont find any information on internet about my enterprise service bus, i can find information about other products of wso2 but not mine.
And the another question is what would be the url that my client should use to connect to my servicebus to my datasource.
Thankyou!!
Hi Hector as I understood your query you are trying to insert/update data to the oracle DB you have configured. To achieve this you will need the DB Report Mediator 1. After configuring this mediator you can call it using a proxy and your client can use the url of the proxy to send the payload. You can refer the example at 2 to get an over all idea.
DB Report Mediator
DB Report Mediator Example
Related
I need to set a MQ Transport provider to be able to use it in different services that there has been created previously.
The idea it's to migrate some services between version 11g to 12c Oracle Service Bus. I know that i could some of the same
by using the MQAdapter but isn't the idea that is required with these services.
By trying to upload these service without the setting it brings me an alert in the logs about 'There's no mq transport provider
set nor configured' something like that .
Error with mq Provider not found - Click to see it
Someone could help me or give me a hint with that? ,
For example, since our server is using TIBCO EMS, would I be able to connect to it using OpenJMS or WeblogicJMS?
JMS standardizes the API, but not the wire-protocol. So all JMS implementations are based on the same API interfaces, but you will require different implementation libraries/jar-files in your class-path that match the server you're connecting to. In the TIBCO EMS case, if you're connecting to a EMS, you'll need tibjms.jar and possibly other of this jars; you cannot use something from OpenJMS etc. instead since they use different wire-protocols.
JMS is pretty much the same as JDBC in this regard.
We have more than 5 corporate applications running on different servers with technologies like spring, struts communication between these application is point to point. We are planning to migrate this to ESB using Mule.
I didnt quite understand how mule works i have few doubts,
Mule is running in a different server do i need to deploy all my 5 aplications into the mule server.
I have spring application delployed on a tomcat server how this application is going to receive messages through mule or what are the configuration changes i need to do in my server or mule server.
Any advice or tutorials.
You need not deploy all you 5 applications in the Mule Server.
You said that all your application are currently point to point (which means that all are talking/communicating now through http protocol), similarly you can also use mule's http endpoints to communicate with all the 5 applications.
I.e. the spring application talking to another spring application can be modified to Spring application talking to Mule and Mule in turn talking to another Spring application .
You must learn the basics from the Documentation
http://www.mulesoft.org/documentation/display/current/Mule+Fundamentals --> browse through the navigation on the lefthand side.
Mule is an integration tool. you no need to change any of your existing applications. All you need is to develop an mule application which can do the mediation/orchestration.
For connecting with your spring application you no need to change any configuration you need to use http:outbound connector inside your mule flow
Just go through http://www.mulesoft.org/documentation/display/current/HTTP+Transport+Reference
So mule is based on SOA principle, so your 5 corporate service need not to be their in a single system. so if you want to consume the service/functionality of any of your 5 application, expose those service as web service, cloud be soap or rest. And you can call those service inside your mule. so in this case you have to create only 5 connection and where ever required you can refer to those connection inside mule configuration file.
#saravanan shanmugavel you need to use Mule ESB to orchestrate the communication between these application...ESB came into the picture to remove your point to point communication...you can create a proxy service for each of your service and one flow which will orchestrate communication between all...
All you need to do is change the application that is configurable according to mule server.
Please refer below link that will be helpful for understanding of mule that helps you better orchestrate communication between all.
https://docs.mulesoft.com/
I wonder is nservicebus pub/sub or other type of app can handle db client to msmq server.
For example I have a desktop client app. using db queue and i want to send message to server using msmq message queue.
Thanks
Take a look at this article about interop with SQL Server: http://andreasohlund.net/2010/09/03/event-based-interop-with-service-broker/. There exists an Oracle AQS transport as well if you are using Oracle.
The article describes how to setup a bridge between the DB queue and MSMQ.
In my application I need to push notifications of real time events from server to clients. The amount of data to pass is very small, mostly and Id. The number of clients listening simultaneously can be around 100 and I may have to publish one notification every 2 - 3 seconds. Both the server and client are built using .Net and WCF.
Given these requirements I have built a set of WCF services which will be run on a load balanced server cluster. The Instance context mode is Per Call and there is no need for sessions etc.
I am currently using BasicHttpBinding. Will TCP binding be better? Does it run on IIS 5 or 6? If not why?
What configuration for serialization can work best?
What are the things I need to do to make sure I get maximum performance?
Edit - Adding more information based on some of the responses -
I host a small WCF service in the client process using manual hosting. The server just calls this service on each client to push the data to all of them.
Firstly have you considered using messaging for what you are trying to achieve?
In answer to will TCP binding work better than BasicHttpBinding- almost certainly yes. If you want to use TCP, you can't use IIS- look into WAS with Windows Server 2008. If you're stuck with Windows Server 2003, then you'll have to host in a windows service instead.
You've made a good choice by choosing per call- this is the preferred instance management mode for creating scalable WCF services.
Edit:
Now you've update your question, I recommend you take a look at IDesign's Pub/Sub framework if you want to stick with WCF. I'd also look at Pub/Sub with MSMQ in WCF and also with "Vanilla" products such as Tibco RV.
If you need pushing data from service to clients you need sessions and you need duplex binding - NetTcpBinding or WSDualHttpBinding. It will not work with BasicHttpBinding because it allows only pulling data (client pools the service for changes). Push data means tha service sends data to clients when needed.
NetTcpBinding always crete session. It can't be hosted in IIS 6 or older. NetTcpBinding is allowed only in Windows Activation Service (WAS) which is extension of IIS 7.x. For older systems you need self hosting = windows service.
Edit:
Based on your description you need Publish-Subscribe message exchange pattern.