Your task is to develop a client-server solution using web services (SOAP and RE
ID: 3734759 • Letter: Y
Question
Your task is to develop a client-server solution using web services (SOAP and REST) that allows people to retrieve posted messages and to post new messages. To ensure reliable storage of messages a database (e.g. MySQL) must be used.
This assignment consists of client and server components.
a) For the server side, you must develop SOAP and REST web services in the language Java using Glassfish or Tomcat.
SOAP:
Develop a SOAP web service for retrieving posted messages from the database and develop a SOAP web service for storing messages in the database.
REST:
Develop a REST web service for retrieving posted messages from the database and develop a REST web service for storing messages in the database.
b) For the client side, you must develop in Java 2 standalone applications.
SOAP:
Develop a standalone application that connects to the SOAP web services and allows a user to add new posts and to retrieve existing posts.
REST:
Develop a standalone application that connects to the REST web services and allows a user to add new posts and to retrieve existing posts.
To obtain additional bonus marks (up to 50%) develop a web page that allows users to add new posts and to retrieve existing posts using the web services developed in part a.
a) (20% bonus) The web page connects to the REST web services developed in part a.
b) (30% bonus) The web page connects to the SOAP web services developed in part a.
There is no more info for this question.
Explanation / Answer
XML is a common, flexible format that allows web service processes to easily manage HTTP and SOAP requests (and REST requests if you are using web service components). AtomSphere strips away the SOAP envelope and HTTP header so you can work solely with the raw data fields when constructing processes at the profile level. It is the most common document type for the start and end of a web service process. Below are some considerations when building these profiles for your integrations.
The root tag and web service object name do not need to match.
Build one XML profile for each object that you want to integrate. For example, if you want to launch one web service process for updating customer information and another web service process for creating new customers, then manage both actions in one simple XML profile that contains the standard customer fields. Simply assign the UPDATE action for one web service server operation and the CREATE action for the other.
NOTE: The default SOAP API configuration specifies that the WSDL includes AtomSphere-specific operation name wrapper elements. You can modify the configuration to remove the wrapper elements to accommodate clients requiring pure SOAP pass-through
Synchronous communication refers to an open session that returns response data to the client application upon initial request. It is best suited for integrations where there is less data being processed and a quick response is required to be sent to the client. A Return Documents step is required for this communication type. Asynchronous communication refers to a closed session where the client application sends an initial request, receives a 200 OK response and no structured response is returned, or there is no Return Documents step in the process.
In synchronous communication, in the event there are no response documents forwarded to the Return Documents step to return data to the client for an execution scenario, AtomSphere will return an empty “Response” or “ResponseList” message to the client application if you have a Single or Multiple XML Object output type defined.
If you prefer to send response data asynchronously, depending on the nature of the web service process or the client application you are using, you may want to build another AtomSphere process that sends response data. For instance, you could build a standalone process that is scheduled to run hourly, queries recently created data and sends responses via the Web Services SOAP or HTTP Client connectors.
If you have an expected input type defined in your Web Services Server operation, you need to understand that it will be the source document format for your process flow. For example, if XML data is sent in through a SOAP request, then the XML profile must be defined as the source profile in a map if you would like to translate the data directly into a database.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.