Installing web service handler

is there a way of programmatically deploying a handler onto a web
service operation?
i looked at jax-rpc HandlerRegistry but when i set a handler chain, it
did not do anything. is this aupposed to set the handler chain on the
server so all future calls will use the handler?
i would like to do this instead of defining everything at deploy time in
the web-services.xml file.

I think you can use oracle web services manager for this. I can't speak from personal experience but from what I've heard I think this is the preferred approach for dealing with secured web services.

Similar Messages

How Can I install Web Service on Oracle 11g r1?

How Can I install Web Service on Oracle 11g r1?

Hi,
Is necesary install XDB?
Because i have executed;
select * from dba_registry
where COMP_ID = 'XDB'
Oracle XML Database
Regards

Errors installing web service to use dreamweaver extension

Portal Version: 10g
OS/Vers. Where Portal is Installed:: Linux AS 2.1
Errors installing web service to use dreamweaver extension
Recently I download the dreamweaver extension for portal, but when I try to install it several errors are raised... in the installation guide the next message appear:
This installation for this feature is an easy 3 step procedure.
1. Installing the Portal web service
2. Configuring the web service to work with your portal (one time administrative process)
3. Installing the PortalTemplates extension for Dreamweaver MX
well but when I try to run the 1 step everything goes wrong...
in the guide say:
# Transfer this file to the OC4J_HOME/j2ee/home directory of the OC4J
(please make sure that the OC4J is up and running)
# Use the following command to install the web service
java -jar admin.jar ormi://<oc4j_host>:<oc4j_ormi_port>
<username> <password>
-deploy -file portalTemplate.ear -deploymentName portalTemplate
here it's where I have some questions,
1. the ormi referers to the rmi ok (I think that), well then I go tho the iasconsole and search for the ports and is show:
home RMI 3202
OC4J_Portal RMI 3203
OC4J_BI_Forms RMI 3204
then I use the home-> port 3202
java -jar admin.jar ormi://myhost.midtierinstall.com:3202
ias_admin ias_midtier_admin_password -deploy -file portalTemplate.ear -deploymentName portalTemplate
but the following messages appear :
Error: Unable to find java:ServerAdministrator : lookup error:javax.naming.AuthenticationException invalid username/passwod for default (ias_admin).... and the error continue... but the problem is that the password works when I use the enterprise manager in that midtier console...
I want to know if I'm doing something wrong or how I should use this command to install that web service

The ormi is the rmi port in the OC4J. This coold be found in oc4j_home/j2ee/home/config/rmi.xml file. The default port is 23791.
Hope this helps,
Ramya

Cannot acces usernametoken in web service handler

I am using wsse usernametoken security standard. I cannot access the usernametoken infomarion in the web services handler. The whole header is blank. Anyone have this situation ?

I am using wsse usernametoken security standard. I cannot access the usernametoken infomarion in the web services handler. The whole header is blank. Anyone have this situation ?

Web service handler could not called in client web service

Hi All,
I have two web service ServiceA & ServiceB and both implemented in weblogic.
The ServiceA is SSL enable and protocol is https which is not published by me.
The ServieB is my web service(wls8.1) and act as client for ServiceA.
My problem is when i hit my service, its not able set the handler when it call ServiceA but it is invoking the service and giving application exception like authentication error.
My service file:
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.HandlerRegistry;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import weblogic.webservice.client.SSLAdapterFactory;
import weblogic.webservice.client.WLSSLAdapter;
public class HelloService {
String wsdl = "https://188.122.123.23/RemoetService?WSDL";
static {
SSLAdapterFactory factory = SSLAdapterFactory.getDefaultFactory();
WLSSLAdapter adapter = (WLSSLAdapter) factory.getSSLAdapter();
adapter.setTrustedCertificatesFile("D:\\lib\\certs
cacerts");
factory.setDefaultAdapter(adapter);
System.setProperty("weblogic.xml.encryption.verbose","true");
System.setProperty("weblogic.xml.signature.verbose","true");
System.setProperty("weblogic.webservice.verbose","true");
public String sayHello(String user) {
RemoteService_Impl service = new RemoteService_Impl(wsdl);
RemotePortType port = service.getRemoteServicePort1();
String namespace = service.getServiceName()
.getNamespaceURI();
QName portName = new QName(namespace,
"RemoteServicePortType");
HandlerRegistry reg = service.getHandlerRegistry();
List handlerList = new ArrayList();
Map map = new HashMap();
map.put("Username", "user1");
map.put("Password", "pwd1");
HandlerInfo info = new HandlerInfo();
info.setHandlerClass(WSClientHandler .class);
info.setHandlerConfig(map);
handlerList.add(info);
reg.setHandlerChain(portName,(List)handlerList);
RemoteServiceResponse = port.callMe(name);
My Handler file:
package com.test;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.Handler;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.Name;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPHeader;
import javax.xml.soap.SOAPHeaderElement;
public class WSClientHandler implements Handler {
private HandlerInfo handlerInfo;
public WSClientAuthenticateHandler(){}
public void init(HandlerInfo hi) {
System.out.println("Handler init");
handlerInfo = hi;
public void destroy() {
System.out.println("Handler destroy method called");
handlerInfo = null;
public QName[] getHeaders() {
System.out.println("Handler Header method called");
try {
Map map = handlerInfo.getHandlerConfig();
QName[] headers = handlerInfo.getHeaders();
System.out.println(" Config :"+map);
for(int i=0;i<headers.length;i++) {
System.out.println(headers.getLocalPart()+" "+
headers.toString()+" "+headers.getNamespaceURI());
}catch(Exception e) {
e.printStackTrace();
return handlerInfo.getHeaders();
public boolean handleRequest(MessageContext mc) {
SOAPMessageContext smc = (SOAPMessageContext) mc;
System.out.println("Calling handler class.....................");
try {
SOAPEnvelope se = smc.getMessage().getSOAPPart().getEnvelope();
System.out.println("Calling handler class.....................");
SOAPHeader soapHeader = se.getHeader();
Name headerName = se.createName("Security","wsse","http://schemas.xmlsoap.org/ws/2002/07/secext");
SOAPHeaderElement headerElement = soapHeader.addHeaderElement(headerName);
SOAPElement element = headerElement.addChildElement(se.createName("UsernameToken", "wsse", "http://schemas.xmlsoap.org/ws/2002/07/secext"));
element.addChildElement(se.createName("Username", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testuser");
element.addChildElement(se.createName("Password", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testpwd");
System.out.println("Calling handler class.....................");
System.out.println("** Request: \n "se.toString()"\n");
}catch(SOAPException e) {
e.printStackTrace();
return true;
/** * Specifies that the SOAP response message be logged to a
* log file before the
* * message is sent back to the client application
* that invoked the Web service.
public boolean handleResponse(MessageContext mc) {
System.out.println("Handler Response method called");
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
System.out.println("** Response: \n"messageContext.getMessage().toString()"\n");
return true;
/** * Specifies that a message be logged to the log file if a SOAP fault is
* * thrown by the Handler instance.
public boolean handleFault(MessageContext mc) {
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
System.out.println("** Fault: \n"messageContext.getMessage().toString()"\n");
return true;
Please need help here.
Thanks in Advance,
pps

I have tested static client calling using handler simple above service and found the issues.
QName portName = new QName(namespace,
"*RemoteServicePortType*");
The above line code has created the issues,becuase in wsdl file ( given similar wsdl file).
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="SayHelloRequest">
<part name="firstName" type="xsd:string"/>
</message>
<message name="SayHelloResponse">
<part name="greeting" type="xsd:string"/>
</message>
*<portType name="RemoteServicePortType">*
<operation name="sayHello">
<input message="tns:SayHelloRequest"/>
<output message="tns:SayHelloResponse"/>
</operation>
</portType>
<binding name="Hello_Binding" type="tns:*RemoteServicePortType*">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sayHello">
<soap:operation soapAction="sayHello"/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</output>
</operation>
</binding>
<service name="Hello_Service">
<port binding="tns:Hello_Binding" name="*RemoteServicePortType1*">
<soap:address
location="http://host1:8080/soap/servlet/rpcrouter"/>
</port>
<port binding="tns:Hello_Binding" name="*RemoteServicePortType2*">
<soap:address
location="http://host2:8080/soap/servlet/rpcrouter"/>
</port>
<port binding="tns:Hello_Binding" name="*RemoteServicePortType3*">
<soap:address
location="http://host3:8080/soap/servlet/rpcrouter"/>
</port>
<port binding="tns:Hello_Binding" name="*RemoteServicePortType4*">
<soap:address
location="http://host4:8080/soap/servlet/rpcrouter"/>
</port>
</service>
</definitions>
From the above WSDL, I have four port name (port binding="tns:Hello_Binding" name="*RemoteServicePortType1*) which is not matching with PortType (portType name="*RemoteServicePortType*")
even i have iterated from getPorts() method and used to invoke the service.But handler was not calling when i invoke.
Please guide me here how i specify correct portname which can call Handler class also.
Thanks in advance,
pps

Web service handler could not registered/called in client web service

Hi Expert,
I have two web service ServiceA & ServiceB and both implemented in weblogic.
The ServiceA is SSL enable and protocol is https which is not published by me.
The ServieB is my web service(wls8.1) and act as client for ServiceA.
My problem is when i hit my service, its not able set the handler when it call ServiceA but it is invoking the service and giving application exception like authentication error.
My service file:
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.HandlerRegistry;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import weblogic.webservice.client.SSLAdapterFactory;
import weblogic.webservice.client.WLSSLAdapter;
public class HelloService {
String wsdl = "https://188.122.123.23/RemoetService?WSDL";
static     {
          SSLAdapterFactory factory =                SSLAdapterFactory.getDefaultFactory();
          WLSSLAdapter adapter = (WLSSLAdapter)     factory.getSSLAdapter();
          adapter.setTrustedCertificatesFile("D:\\lib\\certs\\cacerts");
          factory.setDefaultAdapter(adapter);
          System.setProperty("weblogic.xml.encryption.verbose","true");
          System.setProperty("weblogic.xml.signature.verbose","true");
          System.setProperty("weblogic.webservice.verbose","true");
     public String sayHello(String user) {
          RemoteService_Impl service = new RemoteService_Impl(wsdl);
          RemotePortType port = service.getRemoteServicePort1();
          String namespace = service.getServiceName()
                    .getNamespaceURI();
          QName portName = new QName(namespace,
                    "RemoteServicePortType");
          HandlerRegistry reg = service.getHandlerRegistry();
          List handlerList = new ArrayList();
          Map map = new HashMap();
          map.put("Username", "user1");
          map.put("Password", "pwd1");
          HandlerInfo info = new HandlerInfo();
          info.setHandlerClass(WSClientHandler .class);
          info.setHandlerConfig(map);
          handlerList.add(info);
          reg.setHandlerChain(portName,(List)handlerList);
          RemoteServiceResponse = port.callMe(name);
My Handler Class:
package com.test;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.Handler;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.Name;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPHeader;
import javax.xml.soap.SOAPHeaderElement;
public class WSClientHandler implements Handler {
     private HandlerInfo handlerInfo;
     public WSClientAuthenticateHandler(){}
     public void init(HandlerInfo hi) {
          System.out.println("Handler init");
          handlerInfo = hi;
     public void destroy() {
          System.out.println("Handler destroy method called");
          handlerInfo = null;
     public QName[] getHeaders() {
          System.out.println("Handler Header method called");
          try     {
               Map map = handlerInfo.getHandlerConfig();
               QName[] headers = handlerInfo.getHeaders();
               System.out.println(" Config :"+map);
               for(int i=0;i<headers.length;i++)     {
                    System.out.println(headers.getLocalPart()+" "+
                    headers[i].toString()+" "+headers[i].getNamespaceURI());
          }catch(Exception e)     {
               e.printStackTrace();
          return handlerInfo.getHeaders();
     public boolean handleRequest(MessageContext mc) {
          SOAPMessageContext smc = (SOAPMessageContext) mc;
          System.out.println("Calling handler class.....................");
          try     {
          SOAPEnvelope se =      smc.getMessage().getSOAPPart().getEnvelope();
          System.out.println("Calling handler class.....................");
     SOAPHeader soapHeader = se.getHeader();
     Name headerName = se.createName("Security","wsse","http://schemas.xmlsoap.org/ws/2002/07/secext");
     SOAPHeaderElement headerElement = soapHeader.addHeaderElement(headerName);
     SOAPElement element = headerElement.addChildElement(se.createName("UsernameToken", "wsse", "http://schemas.xmlsoap.org/ws/2002/07/secext"));
     element.addChildElement(se.createName("Username", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testuser");
     element.addChildElement(se.createName("Password", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testpwd");
     System.out.println("Calling handler class.....................");
               System.out.println("** Request: \n "+se.toString()+"\n");
          }catch(SOAPException e)     {
               e.printStackTrace();
          return true;
     /** * Specifies that the SOAP response message be logged to a
     * log file before the
     * * message is sent back to the client application
     * that invoked the Web service.
     public boolean handleResponse(MessageContext mc) {
          System.out.println("Handler Response method called");
          SOAPMessageContext messageContext = (SOAPMessageContext) mc;
          System.out.println("** Response: \n"+messageContext.getMessage().toString()+"\n");
          return true;
     /** * Specifies that a message be logged to the log file if a SOAP fault is
     * * thrown by the Handler instance.
     public boolean handleFault(MessageContext mc) {
          SOAPMessageContext messageContext = (SOAPMessageContext) mc;
          System.out.println("** Fault: \n"+messageContext.getMessage().toString()+"\n");
          return true;
Please need help here.
Thanks in Advance,
pps

I have tested static client calling using handler simple above service and found the issues.
QName portName = new QName(namespace,
*"RemoteServicePortType");*
The above line code has created the issues,becuase in wsdl file ( given similar wsdl file).
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="SayHelloRequest">
<part name="firstName" type="xsd:string"/>
</message>
<message name="SayHelloResponse">
<part name="greeting" type="xsd:string"/>
</message>
<portType name="*RemoteServicePortType*">
<operation name="sayHello">
<input message="tns:SayHelloRequest"/>
<output message="tns:SayHelloResponse"/>
</operation>
</portType>
<binding name="Hello_Binding" type="tns:*RemoteServicePortType*">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sayHello">
<soap:operation soapAction="sayHello"/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</output>
</operation>
</binding>
<service name="Hello_Service">
+<port binding="tns:Hello_Binding" name="*RemoteServicePortType1*">+
+<soap:address+
location="http://host1:8080/soap/servlet/rpcrouter"/>
+</port>+
+<port binding="tns:Hello_Binding" name="*RemoteServicePortType2*">+
+<soap:address+
location="http://host2:8080/soap/servlet/rpcrouter"/>
+</port>+
+<port binding="tns:Hello_Binding" name="*RemoteServicePortType3*">+
+<soap:address+
location="http://host3:8080/soap/servlet/rpcrouter"/>
+</port>+
+<port binding="tns:Hello_Binding" name="*RemoteServicePortType4*">+
+<soap:address+
location="http://host4:8080/soap/servlet/rpcrouter"/>
+</port>+
</service>
</definitions>
From the above WSDL, I have four port name (port binding="tns:Hello_Binding" name="*RemoteServicePortType1*) which is not matching with PortType (portType name="*RemoteServicePortType*")
even i have iterated from getPorts() method and used to invoke the service.But handler was not calling when i invoke.
Please guide me here how i specify correct portname which can call Handler class also.
Thanks in advance,
pps

How to write a Web service Handler without modifying the Web service code

Hi,
How can I write a SOAPHandler without modifying the Web service code. I want to add a generic handler which will take care of SOAPHeader for all the webmethods. To add a handler is it necessary to modify the web service code?

You will find answer in [implementing_handlers_using_jaxws_2|http://blogs.sun.com/sdimilla/entry/implementing_handlers_using_jaxws_2]

Installing Web services

Is it possible to install Labview Web Services on a server with no full Labview installed, just run-time engine and Apache?
I created an installer for a compiled Web service, but it seems to work only on my development machine, and only when Labview IDE is open

Dear Snamprogetti,
You can find and easy to use guide that explains you how to use Web Services in RTE at the following link:
http://digital.ni.com/public.nsf/allkb/62B9C2D5C91EE8B28625778800609FF2?OpenDocument
have a great day!
MarcoMar
National Instruments Italy

Install web services manager

Can anyone provide some pointers on how to install oracle web services manager? Do we need oracle AS 10.1.2 or can we use an embedded oc4j. Any pointers really appreciated.
thanks

Hello,
You can use both. If you are not installing OWSM on 10.1.2 AS then OWSM comes bundled with OC4J and Orale-Lite. Please review the install guide here:
http://download-west.oracle.com/docs/cd/B14099_18/idmanage.htm
Hope this helps.
Deepak

Problem Installing: Web Services Developer Pack 1.3

I am trying to setup an environment to develop and deploy a web application with jsp & servlets. When i tried to install the web services developed pack i got the following error found in the log file. I also just installed the j2sdk 1.4.2_03 and i have set my class path to the new java folder.
Any help would be great.
-Chris
(Feb 7, 2004 5:16:21 PM), Install.product.install, com.installshield.product.service.product.PureJavaProductServiceImpl, wrn, Parent Component with UID = a8182b517735a528d4f8baa8438a8985 of installed Component with displayName = JAXP Version 1.2.4 (Java API for XML Processing) was not found in the VPD.
(Feb 7, 2004 6:01:11 PM), Install.product.install, com.installshield.product.service.product.PureJavaProductServiceImpl$DiskSpaceCheck, wrn, String index out of range: -1
(Feb 7, 2004 6:01:30 PM), Install.product.install, com.sun.jwsdp.installer.SaveEnvironmentVariablesAction, err, An error occurred and product installation failed. Look at the log file /usr/jwsdp-1.3/log.txt for details.
(Feb 7, 2004 6:01:30 PM), Install.product.install, com.sun.jwsdp.installer.SaveEnvironmentVariablesAction, err, java.lang.NoClassDefFoundError
STACK_TRACE: 13
java.lang.NoClassDefFoundError
     at com.sun.jwsdp.installer.SelectJVMPanel.<init>(SelectJVMPanel.java:85)
     at com.sun.jwsdp.installer.SaveEnvironmentVariablesAction.install(SaveEnvironmentVariablesAction.java:177)
     at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(PureJavaProductServiceImpl.java:1916)
     at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(PureJavaProductServiceImpl.java:5149)
     at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(InstallableObjectVisitor.java:369)
     at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(InstallableObjectVisitor.java:333)
     at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(InstallableObjectVisitor.java:133)
     at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(PureJavaProductServiceImpl.java:4532)
     at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(PureJavaProductServiceImpl.java:3727)
     at com.installshield.wizard.service.AsynchronousOperation.run(AsynchronousOperation.java:40)
     at java.lang.Thread.run(Thread.java:534)
(Feb 7, 2004 6:01:31 PM), Install.product.install, com.installshield.product.service.product.PureJavaProductServiceImpl, wrn, Parent Component with UID = a8182b517735a528d4f8baa8438a8985 of installed Component with displayName = JAXP Version 1.2.4 (Java API for XML Processing) was not found in the VPD.
My screen output when i got the error
Installing Java(TM) Web Services Developer Pack 1.3. Please wait...
|-----------|-----------|-----------|------------|
0% 25% 50% 75% 100%
|||||||||||||||
Errors occurred during the installation.
- An error occurred and product installation failed. Look at the log file
/root/jwsdp-1.3/log.txt for details.

Look at the log file /usr/jwsdp-1.3/log.txt for details.Doesn't the log file tell you what's wrong? From the error messages, the installer (InstallShield?) couldn't find some class. Review all of the install instructions, paying particular attention to the setting of environment variables like PATH and CLASSPATH, etc. You might want to check at the Installshield site for further information, also.

Trouble installing web service on linux verson of appserver

Hi.
I've created a test web-service using sun studio enterprice 7, and deployed it to the windows appserver. It works there.
Then I've deployed it to my linux version of the appserver 7, the exact same way. But there I get errors that I don't understand. Can someone please help me?
From error log:
[20/Jan/2005:13:19:56] SEVERE (14838): StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
javax.servlet.ServletException: com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.<init>(Ljavax/xml/namespace/QName;ZLjava/lang/String;Z)V
at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:478)
at _jasper._convertDollarToYen_TAGLIB_jsp._jspService(_convertDollarToYen_TAGLIB_jsp.java:195)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:552)
at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:368)
at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:287)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)
----- Root Cause -----
java.lang.NoSuchMethodError: com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.<init>(Ljavax/xml/namespace/QName;ZLjava/lang/String;Z)V
at ConvertorPack.wsTestClientGenClient.ConvertDollarToYenResponse_LiteralSerializer.<init>(ConvertDollarToYenResponse_LiteralSerializer.java:30)
at ConvertorPack.wsTestClientGenClient.WsTest_SerializerRegistry.getRegistry(WsTest_SerializerRegistry.java:30)
at ConvertorPack.wsTestClientGenClient.WsTest_Impl.<init>(WsTest_Impl.java:24)
at ConvertorPack.wsTestClientGenClient.convertDollarToYen_handler.doAfterBody(convertDollarToYen_handler.java:76)
at _jasper._convertDollarToYen_TAGLIB_jsp._jspService(_convertDollarToYen_TAGLIB_jsp.java:120)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:552)
at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:368)
at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:287)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
[20/Jan/2005:13:19:56] SEVERE (14838): a:505)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598) Best regards
Kristian Gr�nli

Hi;
Please see below doc which could be helpful for your issue:
Where can I find documentation on Web Services Installation? [ID 911492.1]
How To configure OWSM In A RAC Environment? [ID 605404.1]
How To Reconfigure an Existing Oracle Web Services Manager (OWSM) Instance To Use a RAC [ID 602152.1]
Regard
Helios

OBIEE web services: Handling saved filters

I was trying to call obiee web services to get report data. And I used ReportParams to pass the prompt values. But this was not working in case of saved filters in the report.
Plz advice .....

searching.gif is referred through CSS files, thus replace the searching.gif (under res\sk_oracle10\b_mozilla_4) with another custom created blank gif and name it as searching.gif....rename the original searching.gif to searching_original.gif for reference.
caveat: This will affect your enterprise wide display.
mark answers promptly.
J
-bifacts
http://www.obinotes.com

Creating a Web Service to handle flow between BPEL process and XML Gateway

I am new to Web Services. I have never created one, yet I have the task of designing the following for a project.
Any help as to what steps I need to take would be very very helpful. There is a lot of information on XML, SOA and WSDL out there that it can get very confusing, and sometimes you just need someone to point the way
What I need to do is create a Custom Send and a Custom Receive Program (both web services) handle the message flow between an Enterprise BPEL processes and a Deployed XML Gateway.
BPEL compresses this XML business object document (for faster transmission), and sends remotely to this Custom Receive web service, which in turn calls a decompress java program and then send the document to the XML gateway inbound web service.
The Custom Send web service does just the opposite. It needs to take the business object document from XML gateway, call the compress java program and then send to the Enterprise BPEL.
In a nutshell...these Custom Send/Receive Web services handle the message flow between the Enterprise BPEL process and the Deployed XML Gateway.
What I need help on...
-Creating this in JDeveloper- where do I get started?
-How does a web service receive a compressed file sent to me via BPEL? Does it just sit there waiting for it?
-Is this a synchronous or asynchronous design?
-Will this be 2 web services (Send and Receive) or do I make 1 with 2 functionalities
-How do I call the java compress/decompress program within the web service? (this java function is already created and ready to be called)
-Is this decompressed business object file an XML schema and an XML message? Or just a message?
-I need to send this to the XML Gateway Web Service to load. How does that work?
-I have a Generic XML Gateway WSDL file...I assume I need to take all the info I get and map it to this template? Is this true? How do I do that?
Like I said, any help would be appreciated. Links answers to my many questions would be fabulous.
-Jason

If you are talking about simple XML transformation of the SOAP payload between the client calling your service and the final destination of the message you are routing, the ESB approach may be a better fit.
If you have more complex transformation in mind, with major processing and rework of the message in the intermediary, you may be better of with using the POJO approach. Write your service and embed a callout to the other service in your implementation. If the two services share the same Java Model, you may even be able to re-use the same Java Bean.
To get SOAP Element instead of Java bean, you just need to use the noDataBinding option with either genProxy and topDownAssemble (or assemble). See the WS-Guide [1] for details. Chapter 18 will give you all the details about the different WSA command line parameters.
Hope this helps,
-Eric
[1] http://download-west.oracle.com/docs/cd/B31017_01/web.1013/b28974/toc.htm

Installing collab 4.1 sp2 - Web services enhancement

All,
I have been reading through the install guide for collab and one of the pre install steps is to install Web services enhancement 2.0. But if I do a search on www.microsoft.com for Web Services Enhancement all I find is Web Services Enhancement 3.0. Can I install 3 instead of 2? Has anybody done this? I will be doing this install on Monday. Any help would be appreciated.
Thanks,
Berney

Hi Dave,
Please check the below link,
How to create Xcelsius Dashboard based of BI Web Service ( BIWS )
Using Webservice in Dashboard
Webservices in Dashboard - Issue
Also change your original link here and try to load
(sample link)
From:
http://BOE:8080/dswsbobje/qaawsservice/bisw?def=1&cuid=xxxxxxxxxx
To:
http://BOE:8080/dswsbobje/qaawsservice/bisw?wsdl=1&cuid=xxxxxxxxxx
or else can you post your url here.
Hope this helps.
--SumanT

Connection Reset while making http web service call to remote server

Hello guys,
Our environment details are as follows:
WebLogic version: 10.3.3
Cluster: yes
Database: Oracle
Web service server: Remote application
When our WebLogic server makes a http Web service call to another remote application which runs on IIS server for creating a record. The record gets created in remote application but WebLogic server log says java.net.SocketException: Connection reset and the same record doesn't get created in WebLogic application. We have confirmed that remote application is running and it is behaving as expected. Also, we installed web service client on our WebLogic machine just to isolate any network related issues, when we make a same request through this client it works fine and we get answer. At this point in time, it looks like it could be WebLogic or application which is behaving goofy. we are running out of ideas, it would be nice if someone have any thoughts on it like turning on any flags or any other troubleshooting steps. Please, let me know.
Here is the stack trace:
####<Sep 18, 2011 12:31:40 AM MDT> <Info> <com.blah.blah> <server1> <WLSserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defaul
t (self-tuning)'> <user> <BEA1-69D606DA85BDB1A0A7D5> <> <1316327500388> <BEA-000000> <ERROR com.blah.blah - Error during creating a order remoteappja
va.net.SocketException: Connection reset
com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: Connection reset
at com.sun.jersey.api.client.Client.handle(Client.java:569)
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:556)
at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:69)
at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:451)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:173)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at weblogic.net.http.MessageHeader.isHTTP(MessageHeader.java:220)
at weblogic.net.http.MessageHeader.parseHeader(MessageHeader.java:143)
at weblogic.net.http.HttpClient.parseHTTP(HttpClient.java:462)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:364)
at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
at weblogic.net.http.HttpURLConnection.getResponseCode(HttpURLConnection.java:952)
at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:215)
at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)
... 58 more
>
thanks a lot for your help in advance
Regards,

Here's what the issue was for us:
When the web service was initializing, Weblogic? was trying to retrieve the WSDL first before initializing the service.
Though the web service URL was proper, the WSDL itself was unresolvable. This led to this strange connection reset error.
So, if you're experiencing this consistently, check your WSDL URL.
We used "strace" to discover this problem by running it for a brief time while the web service initialization was attempted - and it very clearly showed that the code was attempting to laod something from a bogus address / IP

Installing web service handler

Similar Messages

Maybe you are looking for