As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Googling this question returns lots of results with marketing jargon.
What I am looking for is a summary of what it does, more along these lines What is Maven?
This is the closest I could get.
"WebSphere" in the most abstract sense is a brand encompassing various products, so "a brand" is about as good an answer as you can get.
What one usually refers to when saying "WebSphere", though, is the WebSphere Application Server, which (as the name implies) is an application server - something that runs EJBs and other server-side Java technologies like servlets, JMS, etc. An example of another important player in this space is JBoss AS.
Finally, another possible definition of "WebSphere" is "its creator's biggest technology mistake" ;)
Unlike a regular web server which simply provides clients acces to html-documents, which their browser then displays as websites, an application server allows for programms/scripts to be invoked by requesting websites, which dynamically generate the websites.
In this case the scripts are written in Java. This allows for a lot of the apis provieded in Java to be utilised by your web-application (the website itself is simply the frontend of your webapplication)
So web sphere is an application server from IBM. Simple as that. This tells you what it can do.
Hope that helps.
WebSphere is an application server which supports a lot of advanced functions including load balancing, database connection managing, advanced logging options and many more.
On the other hand it introduces severe overhead, is difficult to administrate and one has to learn a lot to use it effectively. And more often than on other servers you find yourself in JAR hell. Been there.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have a web application which needs to interact with all the major CRM and ERP systems in order to send and receive data.
What according to you will be a better approach.
Design this whole logic inside the web application,maybe a component for each interface
Use a ESB.
Please suggest what will be the best approach to implement this, any other workarounds,designs are also welcome.
Web services were pretty much tailor-made to address the issue of communication and integration among many disparate systems, so it seems like that would be the most logical solution.
If you require ordered messaging, guaranteed message delivery, etc then an ESB is probably your best bet. Otherwise your web application should be able to integrate directly with the other systems via web services.
Finally, you will probably want to create components in your web application anyway to encapsulate the logic of each system (doing this now will help to ensure minimal changes are necessary if/when you replace one of the external systems). For example, for a recent integration with an accounting system I created interfaces and abstract classes to generalize the functions inherent to all accounting systems, and then created concrete classes that implemented that functionality for the specific accounting system I was integrating with at the time. The benefit to this is that if my client ever changes accounting systems in the future all I will need to do is create another concrete implementation - I will not need to rewrite the code in my client application.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Good day. I'm developing a website with the database which is going to be hosted in the cloud using Spring/Hibernate bundle. I also need to develop a desktop application that would be able to manage the remote database. I'm stuck choosing the appropriate method of implementing remote access. JAX-WS, RMI, Spring HttpInvoker or any other method? Which should I choose and why?
I'd choose JAX-WS/SOAP for this particular task.
Unlike binary protocols such as RMI, it goes easily over corporate proxies and firewalls. It has security mechanisms (WS-Security), transaction and session support which I believe is important for database remote management.
It also has better tooling/IDE support than any other remote access method/API/framework.
Create a service layer above dao layer and make it WS. Call WS from your web application and desktop application for using your db actions.
Despite valuable answers of my predecessors, I would like you to analyze how complex system you are bulding and how many environmentally different clients such system would have. I mean, if there would be other applications, written in different technologies than Java involved in it. If it is so, the best solution is JAX-WS. Web services are standarized and can be used among various evironments, not only Java EE. But if you are going to build some very specific system used only by your applications, RMI should be enough.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I want to code a server daemon application that provides some backend functionality. I'd like to stick to Java since I'm pretty familiar with this language and I figure it'd be much easier to just dig into a new framework and not a new language in parallel.
So far I found many promising frameworks, but all of them resemble somehow a webserver. Thing is, I don't want to code a web-application in terms of web-sites so I doubt that I'll need all the webserver-functionality such as templates and this stuff.
What would be a good suggestion for this purpose or would using a regular web-framework such as "play" without the template-stuff be the best choice?
JAX-WS is a standard for creating SOAP web services. Wikipedia link to see what it is about.
For RESTful you would need to make http requests, usually get and post and this type of service works best if you develop a website. From what I understand you don't want this, but still if ever just check the spring framework.
Raw TCP/IP is so much harder and unless you know exactly what you want (performance and optimization wise) you`re better off using a framework.
A webserver is used to implement webservices. A webserver may serve more than html to clients.
I have a personal "stack" using for a long time that is Jetty + RESTEasy and it serves no html at all (only XML and Json).
Javascript + Rest (Glassfish + Jersey for rest). Glassfish – Java EE Full profile certified reference application server (server will used for REST host).
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
There are lots of applications are moving towards osgi. And there are lots of material on the internet talk about benefits of using OSGi. But I fail to see the problems the current way of building/distributing a large java web application using non-OSGi(old way). Could someone
first outline the non-OSGi and OSGi way of developing,packing,distributing a large java web application.
Secondly point out the the problem associated with non-OSGi way?
Thirdly, how moving to OSGi would solve these problems. Maybe also give concrete examples and reference resources.
The "current" way is WAR files, which are share-nothing. If you have three web applications and they all use commons-lang, you have to deploy three copies of the same jar file
(you might be right in that this is not a real problem for most people).
In addition to that, OSGi deploys bundles, not applications. This allows individual pieces of the application to be upgraded or activated at run-time. Not sure if that is important for many people, though. In fact, the missing "application granularity" leads to a great number of "movable parts" being visible in the form of all the bundles that make up an application. That confuses deployment people. OSGi is working on fixing that.
Finally, in OSGi the "container" functionality is also often part of the "application's" set of bundles (as opposed to a black box like JBoss that is clearly separate from application code). Bring your own container in a way. Very flexible, but again confusing for deployment people.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have an idea for a smartphone application.the idea involves communicating with a web server in a specific protocol that I wish to design. what is the best architecture for the web server that fits this scenario, If I want to use DB pesistance, client server communication, and it should be in a language I'm farmiliar with, such as Java or c++?
I'm sorry if it's a noob question, I never dealt with this kind of development (I'm a RT embedded engineer)
thanks a lot.
I would pick a technology that is easy to deploy and manage. I'm not a C++ guy, but I think Java fits the bill. There are a number of easy ways to deploy java these days:
Google App Engine: http://code.google.com/appengine/
Heroku: http://devcenter.heroku.com/articles/java
Amazon ec2 beanstalk: http://aws.amazon.com/elasticbeanstalk/
Each of these will provision the servers and databases for you. Google, and I think Heroku, have free plans for getting started.
-Dave
I think your question is too broad.
I would go for what I'm most confident with, Unix server with Java and MySQL, but since you intend to create the protocol, anything would do, like Windows with SQL Server and IIS and .Net 4...
The fundamental idea is, since you intend to create the protocol, what you interface with is irrelevant. If you were going to use SOAP on a WinPhone, it would make sense to go for a .Net platform, whatever people might say about compatibility and SOAP. Similarly, Android would be better interfaced with Axis and Java, imho. The iPhone anyway requires third party tools or hand-coding of XML, so anything goes.
As it is, your initial idea is right: go for what you master best, because the field has enough learning requirements as it is that you don't need more hurdles :D