I have rceived a request that i need to communicate ti Oracle MQ through webservices. because i have other application will interact with webservice to post data to oracle MQ. because this applications is not MQ implemented app. In this how do i need to read and write data into MQ using webservice? What are the techniques are there to monitor whether the message arrived in Queue and make webservice to read it? Please guide me. i am more confused.i am new to this blindly.
this webservice application will be hosted in the demandware application. the webservice application reads the message in the Oracle MQ which is in the form of Xml file and places into the other Message queue which is also in the form of xml. Demandware application periodically invokes the request to webservice to get/ put the message from MQ queue.
Probably this is coming late, but still.
Demandware is not suitable for general purpose development, especially when proprietary protocols are involved.
My suggestion would be to use middleware component in cases like this.
Related
I am learning SMS application dev with RapidSMS Django. I came across rapidsms-twilio for backend. I am lost here and trying to make sense of overall architecture and technologies associated with each layer. It will help me in future research of better alternatives. Similar to web applications JS/Ajax/css/html are front end tech with java in app layer and db on backend how could i layout SMS application framework?
From my understanding Twilio will provide a number so whenever text is received on number it will receive it in SMMP format and convert it to HTTP and call app server URL mapped against it which could be in django. Where and what does rapidsms do here?
Twilio developer evangelist here.
I have never used RapidSMS, but as far as I can tell, it does the handling and sending of SMS via a chosen backend processor that receives and sends SMS messages. It comes with some built in backends, like Kannel which is an SMS gateway, but there are third party backends available too.
rapidsms-twilio is a third party backend that allows you to use RapidSMS as the dashboard/user interface and send and receive messages via Twilio
I am new to loadrunner and have read some tutorials. My application is invoked via a SOAP web service call from soap UI and I get a synchronous response immediately. Then my application starts processing request and makes many web service calls internally and some business logic processing as well. Based on the result of the web service calls, a table in my application is populated in GUI with the web services and their results. But everything happens internally. I have to keep refreshing the page to get the latest update in the table till all the services are completed.
How do I track such web services which are invoked internally from my application? In tutorials, I could see recording from browser. But this is different. The browser itself doesn't send any requests.
Use proxy recording and set your application to use the LoadRunner recording proxy for web. Don't forget to add the SOAP header afterward
With very little experience designing mobile or web based systems, I really have no idea idea what sort of methods are generally used for exchanging information from an application on a phone with a web service on a server. In my scenario, the app is on Blackberry 10, and I think the web service will be run on Heroku.
I want to periodically exchange small amount of information between client apps and the server's web service. I have tried searching for how this might be done, but I have had no success in finding anything helpful. Any sort of information on how I can or should do this would be appreciated.
To clarify a little: I am particularly interested in how small amount of data are typically stored for transfer, and then what mechanisms are generally used for actually sending and receiving the information.
Typically, this is handled via HTTP calls through the mobile device's SDK. I have no idea what the objects are on blackberry, but the typical workflow looks like this:
Write a web service that does something (e.g. calculation, retrieve data, store data).
Publish web service to a web server. This web service has a URL. If you are following RESTful approaches to web services, there would be unique URLs for resources available through the web. Each function that the web service performs uses one of the common HTTP verbs, e.g. GET and POST. You use "GET" to retrieve data from the web via the URL. You use "POST" when you also want to send data to the web.
From the client SDK (e.g. iOS, Android, Windows Mobile, Blackberry), build an HTTP request through the standard objects that are components of the SDK. Sometimes there are open-source libraries that provide wrapper classes that make this process easier. This HTTP request should either just use the URL (in the event you want to make a GET request), or you should build the request via the "body" of the request with the data that you want to send to the server, in the event of a POST request.
Both types of requests typically produce a response from the server, which you then handle and parse using objects and events that are typically components of the SDK.
You then do whatever you want with the parsed response in the context of the client.
Although the specifics of the implementation of this pattern can vary, the pattern is pretty consistent across all the major platforms; it's really the only way to do it.
Assume there are 2 web services A and B setup in SOA infrastructure.
Web services A depends on information that is available from the locally installed Desktop application (its a legacy application based on C++ programming and provides C++ API to give the information needed by web service A).
The scenario is this: Human actor (which can be considered as Consumer of web service B)logs into a website and clicks a button which requests the service provided by web service B. As part of this request, his ID is sent. Web service B sends request to web service A with this ID. Web service A uses this ID to somehow determine a way to talk to locally installed desktop application of the human actor who originated the request.
The main problem how can web service A connect to desktop application and get the information in a reliable way using SOA infrastructure.
Assume that everything in this SOA is Java based except the desktop application.
The desktop application is basically like a CRM application with its own internal database and not traditional database like MySQL. It provides just basic textual information about the human actor and about the customer(s) of that human actor in his installed CRM desktop application.
I do want to use SOA related technologies even though it may be more complicated.
Given above details:
How can I use JMS to solve this problem?
If JMS is not the right solution, what about ESB and how can I use ESB to solve this problem?
The communication with the desktop application will greatly be determined by what different methods the application is capable of performing. If the application has a database backend, an ESB can facilitate communication with predefined adapters for the specific database being used. If the application has an api that can be tapped programmatically, that is a method as well. I am not sure JMS would be the appropriate solution since given your use case you would want a synchronous reply. Putting JMS in the middle (somehow) will break that reply and rather return an asynchronous response.
I would recommend looking more into the functionality available in the desktop application and with your findings start with evaluating ESB functionality. An ESB may be overkill for this use case but if you plan to do more operations like this it may become valuable.
I think the problem boils down to a Java Web Service A, having a requirement to talk to a C++ desktop application to get user details.
If the Desktop application is able to use JMS using Stomp etc, ActiveMQ or HornetQ maybe used. This also allows you to scale A into multiple instances across many machines, and use JMS to request user information from the Desktop application.
Another option is to expose a simple API (REST, TCP etc) on the Desktop application and make the Web Service A talk to the Desktop application using that. Again, you could distribute the A into multiple instances for scalability.
You can use an ESB to convert a REST call to TCP, or a SOAP to JMS etc. Basically any-to-any conversion. The Free and Open Source ESB UltraESB [http://adroitlogic.org] contains many examples, and is lightweight (~35MB) so the 'overkill' will be minimal compared to > 300MB+ resource hungry ESBs
I'm developing an application that requires storing data on an internet database.
Because of WP7 doesn't support databases,I think if I send my variables-datas to the web services that i craated,i can do what i want.
I know how to write a webservice but how can i send my variables to the webservice from WP7?
You can have a look at http://www.sterlingdatabase.com/ which provides a nice and lightweight database. I'm also using this in my project and it works fine.