Monthly Archive: April 2011

JMS Based Webservice on Weblogic Server

By default, client applications use HTTP/S as the connection protocol when invoking a WebLogic Web Service. You can, however, configure a WebLogic Web Service so that client applications can also use JMS as the transport when invoking the Web Service.When a WebLogic Web Service is configured to use JMS as the connection transport:The generated WSDL of the Web Service contains two port definitions: one with an HTTP/S binding and one with a JMS binding. When you invoke the Web Service in your client application, you can choose which port, and thus which type of transport, you want to use.Warning:     Non-WebLogic client applications, such as a .NET client, will not be able to invoke the Web Service using the JMS binding.The clientgen Ant task creates a Service implementation that contains two getPortXXX() methods, one for HTTP/S and one for JMS.Note:    You can configure any WebLogic Web Service to include a JMS binding in its WSDL. This feature is independent of JMS-implemented WebLogic Web Services.

Read more

Step1 :-

Create JMS Server and target it to the AdminServer running on http://localhost:7001Create a ConnectionFactory and a Queue targeted to the JMSServer.For Screenshots follow this article.
Step2 :- Create a JWS File

package demo;
import weblogic.jws.*;

import javax.jws.WebService;
import javax.jws.WebMethod;
import javax.jws.soap.SOAPBinding;

@WebService(name=”HelloWorldPortType”,serviceName=”HelloWorldService”,      targetNamespace=””)
@SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL,           parameterStyle=SOAPBinding.ParameterStyle.WRAPPED)

@WLJmsTransport(serviceUri=”HelloWorldService”,portName=”HelloWorldServicePort”,                    contextPath=”HelloWorldService”,connectionFactory=”ConnectionFactory-0″,queue=”Queue-0″)

public class HelloWorldImpl {
public String sayHello(String s) {
return “Hello ” + s;

Step 3:- Create a Client

package demo;
import demo.HelloWorldService;
import demo.HelloWorldService_Impl;
import demo.HelloWorldPortType;
import weblogic.wsee.jaxrpc.WLStub;
import java.util.ArrayList;
import java.util.List;
import javax.xml.rpc.Stub;

public class HelloWorldClient
public static void main(String[] args) throws Throwable {

String wsdl = args[0];
HelloWorldService service = new HelloWorldService_Impl(wsdl);
HelloWorldPortType port = service.getHelloWorldServicePort();
Stub stub = (Stub)port;
stub._setProperty(WLStub.JMS_TRANSPORT_JNDI_URL, “t3://localhost:7001”);
String response = port.sayHello(“World”);
System.out.println(“response = ” + response);

Step 4:- Create a build

<project name=”Sample JMS Webservice” default=”all” basedir=”.”>

<property name=”ws.file” value=”HelloWorldImpl” />
<property name=”ear.dir” value=”./ear” />
<property name=”client.dir” value=”./client” />

<path id=”client.class.path”>
<pathelement path=”${client.dir}”/>
<pathelement path=”${java.class.path}”/>

<taskdef name=”jwsc”
classname=”” />

<taskdef name=”clientgen”
classname=”” />

<target name=”all” depends=”clean,
deploy” />

<target name=”build” depends=”clean,
client” />

<target name=”clean”>
<delete dir=”${ear.dir}”/>
<delete dir=”${client.dir}”/>

<target name=”server”>
<mkdir dir=”${ear.dir}”/>
<jws file=”${ws.file}.java” explode=”true”/>

<target name=”deploy”>
<wldeploy action=”deploy”
source=”${ear.dir}” user=”weblogic”
password=”weblogic” verbose=”true”
targets=”AdminServer” />

<target name=”client”>
<mkdir dir=”${client.dir}”/>
srcdir=”${client.dir}” destdir=”${client.dir}”
srcdir=”${basedir}” destdir=”${client.dir}”

<target name=”run” >
<java fork=”true”
failonerror=”true” >
<classpath refid=”client.class.path”/>
<arg line=”http://localhost:7001/HelloWorldService/HelloWorldService?WSDL” />


Step 5:- Create a folder and keep the source files and the build.xml in that directory. Also copy the setWLSEnv.cmd from WL_HOME\bin to this folder. Create two folders in this folder, ear and client.

Step 6 :- Set the Environment


Step 7:- Create the Webservice Ear

D:\Replications\jmswebservice>ant server
Buildfile: build.xml

[jwsc] JWS: processing module /HelloWorldImpl
[jwsc] Parsing source files
[jwsc] Parsing source files
[jwsc] 1 JWS files being processed for module /HelloWorldImpl
[jwsc] JWS: D:\Replications\jmswebservice\ Validated.
[jwsc] Since compiler setting isn’t classic or modern,ignoring fork setting
[jwsc] Compiling 2 source files to C:\Users\khanf\AppData\Local\Temp\_bxr00
[jwsc] Since compiler setting isn’t classic or modern,ignoring fork setting
[jwsc] Copying 1 file to D:\Replications\jmswebservice\ear\HelloWorldImpl\W
[jwsc] Copying 22 files to D:\Replications\jmswebservice\ear\HelloWorldImpl
[jwsc] Copying 2 files to D:\Replications\jmswebservice\ear\HelloWorldImpl\
[jwsc] Copying 1 file to D:\Replications\jmswebservice\ear\HelloWorldImpl
[jwsc] [EarFile] Application File : D:\Replications\jmswebservice\ear\META-
[AntUtil.deleteDir] Deleting directory C:\Users\khanf\AppData\Local\Temp\_bxr00h

Total time: 16 seconds

Step 8:- Deploy the Ear

D:\Replications\jmswebservice>ant deploy
Buildfile: build.xml

[wldeploy] weblogic.Deployer -verbose -noexit -source D:\Replications\jmswebser
vice\ear -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -pass
word ******** -deploy
[wldeploy] weblogic.Deployer invoked with options: -verbose -noexit -source D:
\Replications\jmswebservice\ear -targets AdminServer -adminurl t3://localhost:70
01 -user weblogic -deploy
[wldeploy] <Apr 30, 2011 2:06:34 PM IST> <Info> <J2EE Deployment SPI> <BEA-2601
21> <Initiating deploy operation for application, ear [archive: D:\Replications\
jmswebservice\ear], to AdminServer .>
[wldeploy] Task 3 initiated: [Deployer:149026]deploy application ear on AdminSe
[wldeploy] Task 3 completed: [Deployer:149026]deploy application ear on AdminSe
[wldeploy] Target state: deploy completed on Server AdminServer
[wldeploy] Target Assignments:
[wldeploy] + ear AdminServer


Step 9 :- Compile the client

D:\Replications\jmswebservice>ant client
Buildfile: build.xml

[clientgen] Ignoring JAX-WS options – building a JAX-RPC client
[clientgen] *********** jax-rpc clientgen attribute settings ***************
[clientgen] wsdlURI: file:/D:/Replications/jmswebservice/ear/HelloWorldImpl/WEB-
[clientgen] serviceName : null
[clientgen] packageName : demo
[clientgen] destDir : D:\Replications\jmswebservice\client
[clientgen] handlerChainFile : null
[clientgen] generatePolicyMethods : false
[clientgen] autoDetectWrapped : true
[clientgen] jaxRPCWrappedArrayStyle : true
[clientgen] generateAsyncMethods : true
[clientgen] *********** jax-rpc clientgen attribute settings end ***************

[clientgen] Package name is demo
[clientgen] DestDir is D:\Replications\jmswebservice\client
[clientgen] class name is HelloWorldPortType_Stub
[clientgen] service class name is HelloWorldService
[clientgen] Porttype name is HelloWorldPortType
[clientgen] service impl name is HelloWorldService_Impl
[javac] Compiling 4 source files to D:\Replications\jmswebservice\client
[javac] Note: D:\Replications\jmswebservice\client\demo\HelloWorldPortType_S uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] Compiling 1 source file to D:\Replications\jmswebservice\client


Step 10:- Run the Client

D:\Replications\jmswebservice>ant run
Buildfile: build.xml

[java] response = Hello World

Total time: 10 seconds

If you have a look at the WSDL


The service will look like this.

<s0:service name=”HelloWorldService”>
<s0:port binding=”s1:HelloWorldServiceSoapBinding” name=”HelloWorldServicePort”>
<s2:address location=”jms://″ />

Let me know if you face any issues while running this sample.


Download the source here : jmswebservice

Changing default ports in Jboss

The Jboss port configuration is defined by the ServiceBindingManager service of JBoss.  There could be scenarios where you might want to change the default JBoss server ports. The Jboss Web Server by default runs on port 8080 and a set of other services run on a predefined set of ports which is specified in the server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml.

You can change the default ports in two ways.

1. Specifying as VM Parameter.

Start JBoss with the VM parameter jboss.service.binding.set set to either ports-defaultports-01,ports-02 etc. For example:

run -Djboss.service.binding.set=ports-01


2.Edit the ServiceBinding configuration file.

This requires to manually edit the server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml

Note: This file defines the default port bindings specified by “ports-default

<!– The name of the set of bindings to use for this server –>


You can change the default ports by any of the below values.

ports-01 : Has 100 as an offset port

ports-02 : Has 200 as an offset port

ports-03: Has 300 as an offset port.

A sample entry in the file would look like below.



<!-- The ports-default bindings are obtained by taking the base bindings and adding t0 to each port value  -->

<bean name="PortsDefaultBindings"  class="">


<!--  The name of the set -->


<!-- Default host name -->


<!-- The port offset -->


<!-- Set of bindings to which the "offset by X" approach can't be applied -->






Now if you want to change the default ports specify the below entry.




Changing the configuration manually is a tedious process and requires some other xml files to be changed. However it is recommended to follow the first approach.

For more on Service Binding Manager, refer below link.


Wonders Team. 🙂