The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Enabling a third-party JAX-WS application in WebSphere Application Server V6.1

Nikhil Thaker (nikhil.v.thaker@us.ibm.com), Advisory Software Engineer, IBM

Nikhil Thaker is an Advisory Software Engineer with IBM Software Group, and a member of the WebSphere Application Server team that developed the Web services JAX-WS implementation. He has more than nine years of experience in Enterprise Application Integration, and has focused on Web services for the past four years. He has worked with various IBM customers as an IT Specialist in Enterprise Application Integration in IBM Global Services. His industry experience includes automotive, health care, telecommunication and utilities.

You can reach Nikhil at nikhil.v.thaker@us.ibm.com.

Summary: This article describes how you can use a third-party Java API for XML Web services (JAX-WS) engine in WebSphere Application Server V6.1. It describes how to deploy an application using an external third-party JAX-WS engine, as well as limitations and potential issues when using such third-party applications.

Date: 13 Jan 2010
Level: Intermediate

Activity: 8017 views
Comments:

Get the downloads

This article describes how you can use a third-party Java™ API for XML Web services (JAX-WS) engine in WebSphere® Application Server V6.1. It describes how to deploy an application using an external third-party JAX-WS engine, as well as limitations and potential issues when using such third-party applications.

Overview

Some WebSphere Application Server (hereafter Application Server) users would like to leverage a third-party JAX-WS engine like Axis2 or Apache CXF by having these runtimes embedded in an application EAR file. There are several reasons you might want to do this, such as to use features specific to the third-party runtimes, to reuse code, or to achieve application consistency in a multi-vendor or multi-version environment.

Use of third-party JAX-WS runtimes has limitations and requires certain configuration changes. In some cases, it may also require manual intervention to resolve issues that occur during deployment and runtime. These limitations and issues vary based on the external runtime.

When such a third-party application is deployed on Application Server, the Application Server JAX-WS Web services engine must be disabled so it doesn’t conflict with the third-party implementation. Starting with WebSphere V6.1 Fixpack 29, configuration options were added to enable this on a per-application or per-server basis.

This article demonstrates how to use an application EAR with Axis2, Apache CXF, or Metro embedded in it with WebSphere Application Server V7.

Notes:

WebSphere does not claim support for any of the third-party JAX-WS runtimes. IBM ensures successful deployment of such applications only.
This document does not imply IBM is endorsing the use of any of the third-party runtimes mentioned in this document on WebSphere Application Server.

Downloads

Description	Name	Size	Download method
Article in PDF format	1001_thaker2.pdf	1.35MB	HTTP
Sample Axis2 application	axis2.zip	18.3MB	HTTP
Sample CXF application	CXFSampleOnWAS_Sample.ear	22.6MB	HTTP
Sample Metro application	MetroOnWAS_Sample.ear	14.8MB	HTTP