Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, Liz McMillan, Yeshim Deniz, Carmen Gonzalez

Related Topics: Microservices Expo

Microservices Expo: Article

Developing J2EE 1.4 Web Services on the Fly

Developing J2EE 1.4 Web Services on the Fly

As Web services technology becomes pervasive, the beta release of Java 2 Enterprise Edition (J2EE) 1.4, which focuses primarily on Web services, flags a milestone in the Web services developer community. Sun's J2EE Reference Implementation (RI) helps developers to easily understand the technology through its robust implementation of the specification. The J2EE 1.4 specification (JSR-151) adds a lot of functionality to the platform. The core theme of J2EE 1.4 circumvents Web services. It has incorporated most of the Web services-related JSRs in its specification, including JSR-109 (Implementing Enterprise Web Services), JSR-101 (Java APIs for XML-based RPC), JSR-67 (Java APIs for XML Messaging 1.0), and JSR-93 (Java API for XML Registries 1.0).

Basically, a Web service client can access J2EE applications in two ways. First, the client can access a Web service created with JAX-RPC. Second, the client can access an EJB Web service (only stateless session beans) through its Web service endpoints. The bottom line is that JAX-RPC uses a servlet to implement the Web service. This helps in exposing the existing stateless session beans as Web services.

In this article, I'll deal with the development of a Web service using the J2EE 1.4 platform. I'll use the JAX-RPC APIs that form the basis for developing J2EE 1.4 Web services on the fly.

Creating a Web Service with JAX-RPC
Remote Procedure Call (RPC) is a mechanism through which you invoke procedures (or services) from a remote client. In the Java world, we have the Java API for XML-based RPC (JAX-RPC) in which service invocation takes place through an XML-based protocol called Simple Object Access Protocol (SOAP) over HTTP transport. Since the J2EE 1.4 platform uses standard technologies such as XML, SOAP, and HTTP, it is easy for developers to create Web services that are platform independent and interoperable.

The typical life cycle of a Web service has three stages: develop the Web service, deploy the Web service, and invoke the Web service. We'll follow this life cycle in developing our Web services using J2EE 1.4. We will consider the familiar stock quote application for our illustration. A stock quote service is deployed in the server. The client invokes the service by passing a stock symbol. Here, the service and the client are developed using the JAX-RPC APIs. Figure 1 shows the interactions between the Stock quote Web service and the stock quote client. Stubs are the client-side proxies used to communicate with the service. Ties are the classes the server needs to communicate with a remote client. Stubs and ties are low-level classes that perform similar functions, i.e, stubs on the client side and ties on the server side.

 

Building and Deploying the Service
The steps that are involved in building and deploying the service are:

  1. Define the interface class for the service.
  2. Implement the interface class.
  3. Compile the classes and generate WSDL.
  4. Package the classes as an EAR file.
  5. Deploy the service.
Service Interface
Our stock quote service has one method, getQuote, which takes the symbol as the argument and returns the value of the stock symbol. The interface definition for the stock quote service is shown in Listing 1.

Service Implementation
The service implementation StockQuoteImpl implements the interface StockQuote IF. This connects to an Axis stock quote service that is running on the www. xmethods.net server. The getQuote request made to this service returns an XML document that contains the value of the stock. If you are behind a firewall, you need to specify the proxyHost and proxyPort properties in order to access the service. The implementation for the stock quote service is shown in Listing 2.

Generating the WSDL File
J2EE 1.4 provides a tool called wscompile.bat, which generates the WSDL file for the service. The Ant target generate-wsdl does this for you and runs this tool as follows:

wscompile.bat -define -d build/server -nd build/server
-classpath build/server service-config.xml

The generated WSDL file MyStock QuoteService.wsdl is shown in Listing 3. The Ant target build-service compiles the service classes and the generation of the WSDL file for the service.

Packaging the Service
To package the service, use the ant target package-service, which packages the service and its dependent files in a stockquote.ear file. This EAR file bundles the stockquote-jaxrpc.war file in it. The contents of these WAR and EAR files are:

stockquote-jaxrpc.war
META-INF/
META-INF/MANIFEST.MF
WEB-INF/
WEB-INF/classes/
WEB-INF/classes/stockquote/
MyHelloService.wsdl
WEB-INF/classes/stockquote/StockQuoteIF.class
WEB-INF/classes/stockquote/StockQuoteImpl.class
WEB-INF/mapping.xml
WEB-INF/web.xml
WEB-INF/webservices.xml

stockquote.ear
META-INF/
META-INF/MANIFEST.MF
stockquote-jaxrpc.war
META-INF/application.xml
META-INF/sun-j2ee-ri.xml

Deploying the Service
J2EE 1.4 provides a tool called deploytool.bat for deploying Web applications. The developed EAR file is deployed in the server using this tool. This can be done with the help of the Ant target deploy-service. As a precondition, you need to start the database server from the command prompt by typing

%J2EE_HOME%/bin/cloudscape.bat -start

Start the J2EE server from the command prompt by typing

%J2EE_HOME%/bin/j2ee.bat -verbose

to start the server in verbose mode. The Ant target runs the deploy tool as follows:

deploytool.bat -id stockquote-jaxrpc
-deployModule stockquote.ear

This deploys the stock quote service in the server. To verify that the service has been successfully deployed, execute the Ant target "list", which lists all the applications that are deployed on the server. You can verify the successful service deployment by typing the following URL in your browser:

http://localhost:8000/stockquote-jaxrpc/mystockquote?WSDL

If you can see the WSDL file on your browser, the service is deployed successfully.

Building and Running the Client
The steps involved in building and running the client are:

  1. Generate the stubs.
  2. Code the client class.
  3. Compile the client class.
  4. Package the classes as a JAR file.
  5. Run the client.
Generate the Stubs
Stubs are the client-side proxies for the service. J2EE 1.4 provides a tool called wscompile.bat for generating these stubs. The Ant target generate-stubs, defined in our build.xml, does this task for you. This target runs the tool as follows:

wscompile.bat -gen:client -d build/client
-classpath build/server client-config.xml

The wscompile.bat tool generates files based on the information that it reads from the MyStockQuoteService.wsdl. The -gen: client option instructs the tool to generate the client-side classes called stubs. The -d option instructs the tool in which directory the generated stubs are to be placed. The -classpath option instructs the tool where to find the input classes. The tool reads the config file "client-config.xml" which has the information about the location of the WSDL file. The client configuration file client-config. xml is shown in Listing 4.

Service Client
Once the service is defined, implemented, and deployed, it is ready for access by the clients. The client uses the generated stubs to interact with the service. This is a static client as it was created before runtime. The client takes the service endpoint as the input argument, and invokes the getQuote method by passing the symbol "HPQ". The service returns the value of the symbol to the system console. This is the real-time quote of the symbol with a delay of 20 minutes. The client for accessing the stock quote service is shown in Listing 5.

Compiling and Packaging the Client
The Client sources along with the stubs are compiled and packaged as a JAR file by the Ant targets compile-client and package-client. This generates a file - client.jar that is used in invoking the stock quote service.

Setup Instructions for Running the Web Service
Required Software:

  • Download Ant 1.5.3 from http://ant.apache.org
  • Download J2SE 1.4.1 from http://java.sun.com/j2se/1.4.1/download.html
  • Download J2EE 1.4 Beta from http://java.sun.com/j2ee/1.4/download.html#sdk

    Setting Up Environment Variables
    To run the StockQuote application, you need to set the following environment variables:

  • J2EE_HOME=C:\j2sdkee1.4
  • JAVA_HOME=C:\j2sdk1.4.1_02
  • ANT_HOME=H:\apache-ant-1.5.3
  • PATH=%JAVA_HOME%/bin;%J2EE_HOME%\bin;%ANT_HOME%\bin;%PATH%

    Invoke the Service Using the Web Service Client
    Download the source code of the developed Web service. Extract this under "J2EE_HOME\doc\samples". The "build. xml" file bundled with this application defines all of the tasks discussed above as Ant targets. Before proceeding further, you need to change the proxy-related information in the StockQuoteImpl.java class.

    As a precondition, you need to start the database and J2EE servers by using the following commands:

    %J2EE_HOME%/bin/cloudscape.bat -start
    "%J2EE_HOME%/bin/j2ee.bat -verbose

    This starts the server in verbose mode. Wait until the command window displays "J2EE server startup complete." Now you are ready to execute the Ant targets that will help you build, deploy, and invoke the Web service.

    Execute the following targets:

  • Ant build-service: Compiles the service sources.
  • Ant package-service: Packages the service classes and related files in an EAR file.
  • Ant deploy-service: Deploys the service in the server.
  • Ant list: Lists the deployed service.
  • Ant build-client: Compiles the client sources.
  • Ant package-client: Packages the client classes as a JAR file.
  • Ant run: Invokes the service. Figure 2 shows the output of the client after invoking the service. It returns the value of the symbol with a delay of 20 minutes.
  • Ant undeploy: Undeploys the service from the server.

     

    Conclusion
    Tools always ease the development of application software. With the help of robust tools, developers can spend more time designing the applications than developing the applications. The current release of the J2EE 1.4 platform provides some basic tools that ease the development of Web services. The J2EE 1.4 final release plans to have support for Web Services - Interoperability (WS-I) basic profiles. Developing and deploying Web services on the fly is a reality with the arrival of the J2EE 1.4 platform.

    References

  • J2EE 1.4 Platform Home: http://java.sun.com/j2ee/
  • J2EE 1.4 Specification: http://java.sun.com/j2ee/j2ee-1_4-pfd2-spec.pdf
  • JSR 151: www.jcp.org/en/jsr/detail?id=151
  • The J2EE Tutorial Addendum: http://java.sun.com/j2ee/1.4/docs/tutorial/index.html
  • More Stories By Arulazi Dhesiaseelan

    Arulazi Dhesiaseelan holds Master of Computer Applications degree from PSG College of Technology, India. He has been involved in designing and building Java based applications and SDK for more than three years. He was also involved in the API development of UDDI4j project hosted at http://uddi4j.org. He's working with Hewlett Packard Company (India Software Operations), Bangalore. Currently he is involved in the development of an open service framework for mobile infrastructures. He can be reached at [email protected]

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


    @MicroservicesExpo Stories
    The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin, ...
    By now, every company in the world is on the lookout for the digital disruption that will threaten their existence. In study after study, executives believe that technology has either already disrupted their industry, is in the process of disrupting it or will disrupt it in the near future. As a result, every organization is taking steps to prepare for or mitigate unforeseen disruptions. Yet in almost every industry, the disruption trend continues unabated.
    SYS-CON Events announced today that HTBase will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. HTBase (Gartner 2016 Cool Vendor) delivers a Composable IT infrastructure solution architected for agility and increased efficiency. It turns compute, storage, and fabric into fluid pools of resources that are easily composed and re-composed to meet each application’s needs. With HTBase, companies can quickly prov...
    Building custom add-ons does not need to be limited to the ideas you see on a marketplace. In his session at 20th Cloud Expo, Sukhbir Dhillon, CEO and founder of Addteq, will go over some adventures they faced in developing integrations using Atlassian SDK and other technologies/platforms and how it has enabled development teams to experiment with newer paradigms like Serverless and newer features of Atlassian SDKs. In this presentation, you will be taken on a journey of Add-On and Integration ...
    Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership abi...
    The essence of cloud computing is that all consumable IT resources are delivered as services. In his session at 15th Cloud Expo, Yung Chou, Technology Evangelist at Microsoft, demonstrated the concepts and implementations of two important cloud computing deliveries: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). He discussed from business and technical viewpoints what exactly they are, why we care, how they are different and in what ways, and the strategies for IT to transi...
    Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
    All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
    DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm.
    As software becomes more and more complex, we, as software developers, have been splitting up our code into smaller and smaller components. This is also true for the environment in which we run our code: going from bare metal, to VMs to the modern-day Cloud Native world of containers, schedulers and micro services. While we have figured out how to run containerized applications in the cloud using schedulers, we've yet to come up with a good solution to bridge the gap between getting your contain...
    As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningf...
    DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In his Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, will explore t...
    DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, explored HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
    With major technology companies and startups seriously embracing Cloud strategies, now is the perfect time to attend @CloudExpo | @ThingsExpo, June 6-8, 2017, at the Javits Center in New York City, NY and October 31 - November 2, 2017, Santa Clara Convention Center, CA. Learn what is going on, contribute to the discussions, and ensure that your enterprise is on the right path to Digital Transformation.
    Everyone wants to use containers, but monitoring containers is hard. New ephemeral architecture introduces new challenges in how monitoring tools need to monitor and visualize containers, so your team can make sense of everything. In his session at @DevOpsSummit, David Gildeh, co-founder and CEO of Outlyer, will go through the challenges and show there is light at the end of the tunnel if you use the right tools and understand what you need to be monitoring to successfully use containers in your...
    What if you could build a web application that could support true web-scale traffic without having to ever provision or manage a single server? Sounds magical, and it is! In his session at 20th Cloud Expo, Chris Munns, Senior Developer Advocate for Serverless Applications at Amazon Web Services, will show how to build a serverless website that scales automatically using services like AWS Lambda, Amazon API Gateway, and Amazon S3. We will review several frameworks that can help you build serverle...
    The IT industry is undergoing a significant evolution to keep up with cloud application demand. We see this happening as a mindset shift, from traditional IT teams to more well-rounded, cloud-focused job roles. The IT industry has become so cloud-minded that Gartner predicts that by 2020, this cloud shift will impact more than $1 trillion of global IT spending. This shift, however, has left some IT professionals feeling a little anxious about what lies ahead. The good news is that cloud computin...
    An overall theme of Cloud computing and the specific practices within it is fundamentally one of automation. The core value of technology is to continually automate low level procedures to free up people to work on more value add activities, ultimately leading to the utopian goal of full Autonomic Computing. For example a great way to define your plan for DevOps tool chain adoption is through this lens. In this TechTarget article they outline a simple maturity model for planning this.
    While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations might...
    The rise of containers and microservices has skyrocketed the rate at which new applications are moved into production environments today. While developers have been deploying containers to speed up the development processes for some time, there still remain challenges with running microservices efficiently. Most existing IT monitoring tools don’t actually maintain visibility into the containers that make up microservices. As those container applications move into production, some IT operations t...