Can XI handle RPC based web services ?

Is it possible with XI 3.0 to work with RPC based webservices rather than Document based services.
If it can, can some one send me sample configuration for SOAP Receiver and SOAP Sender.
I have successfully configured an SOAP Receiver to access external web service on internet which is a document based but I am having difficulty in accessing rpc based webservice on intranet.
We are on XI 3.0 SP 14. Appreciate your comments on this topic.
Thanks
Prasad

Hi John!
> Is using RPC style web services supported out of the
> box within XI? I have read some forums that suggest
> only document style are and would like a definitive
> answer.
I have opened an OSS message regarding this topic and I was told that RPC-style Web Services are not supported within the XI SOAP adapter. Our current workaround which adds the missing Web Service operation using an additional XSLT mapping is not sufficient. Instead we have to change our WSDL from RPC-style into document-literal style.
Regards, Tanja

Similar Messages

Another ESB issue in less than 24 hours!!!! (RPC based web service)

Ok, now I'm a little upset :-(
ESB does not support creating a SOAP service if the target service is RPC based and has its messages based on simple type.
OK, but, BPEL DOES!!!!
So, why ESB does not???
Below my target WSDL, which works nicely on BPEL, but I'm not able to configure in ESB:
<?xml version="1.0" encoding="UTF-8" ?>
- 
- <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.example.com/1182368010880/customerInputImpl/RetrieveServices" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns0="http://xmlns.POC.com/unique/default/namespace/customerInfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xmlns.example.com/1182368010880/customerInputImpl/RetrieveServices">
- <wsdl:types>
- <xs:schema xmlns="http://xmlns.POC.com/unique/default/namespace/customerInfo" targetNamespace="http://xmlns.POC.com/unique/default/namespace/customerInfo" elementFormDefault="qualified" attributeFormDefault="unqualified">
- <xs:complexType name="customertype">
- <xs:sequence>
<xs:element name="SEQUENTIAL" type="xs:string" minOccurs="0" />
<xs:element name="REFERENCE_TYPE" type="xs:string" minOccurs="0" />
<xs:element name="ACTION" type="xs:string" minOccurs="0" />
<xs:element name="COMPANY_CODE" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_STATUS" type="xs:string" minOccurs="0" />
<xs:element name="STATUS_ADDRESS" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_TYPE" type="xs:string" minOccurs="0" />
<xs:element name="LEGACY_CODE" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_NAME" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_NUMBER" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_NAME_PHONETIC" type="xs:string" minOccurs="0" />
<xs:element name="BRANCH" type="xs:string" minOccurs="0" />
<xs:element name="VERIFIER_DIGIT" type="xs:string" minOccurs="0" />
<xs:element name="STATE_REGISTRATION" type="xs:string" minOccurs="0" />
<xs:element name="MUNICIPAL_REGISTRATION" type="xs:string" minOccurs="0" />
<xs:element name="INDICATOR_CONTRIB_ICMS" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_CATEGORY" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_CLASS" type="xs:string" minOccurs="0" />
<xs:element name="ADDRESS_TYPE" type="xs:string" minOccurs="0" />
<xs:element name="ADDRESS1" type="xs:string" minOccurs="0" />
<xs:element name="DISTRICT" type="xs:string" minOccurs="0" />
<xs:element name="CITY" type="xs:string" minOccurs="0" />
<xs:element name="STATE" type="xs:string" minOccurs="0" />
<xs:element name="ADDRESS3" type="xs:string" minOccurs="0" />
<xs:element name="POSTAL_CODE" type="xs:string" minOccurs="0" />
<xs:element name="PHONE_COUNTRY_CODE" type="xs:string" minOccurs="0" />
<xs:element name="TELEPHONE_AREA_CODE" type="xs:string" minOccurs="0" />
<xs:element name="TELEPHONE_NUMBER" type="xs:string" minOccurs="0" />
<xs:element name="TELEPHONE_TYPE" type="xs:string" minOccurs="0" />
<xs:element name="TELEPHONE" type="xs:string" minOccurs="0" />
<xs:element name="TELEX" type="xs:string" minOccurs="0" />
<xs:element name="FAX" type="xs:string" minOccurs="0" />
<xs:element name="CONTACT_LAST_NAME" type="xs:string" minOccurs="0" />
<xs:element name="JOB" type="xs:string" minOccurs="0" />
<xs:element name="TELEPHONE_EXTENSION" type="xs:string" minOccurs="0" />
<xs:element name="CREATION_DATE" type="xs:string" minOccurs="0" />
<xs:element name="LAST_UPDATE_DATE" type="xs:string" minOccurs="0" />
<xs:element name="ERROR_MESSAGE" type="xs:string" minOccurs="0" />
<xs:element name="GL_ID_REC" type="xs:string" minOccurs="0" />
<xs:element name="GL_ID_REV" type="xs:string" minOccurs="0" />
<xs:element name="PAYMENT_METHOD_NAME" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_PROFILE_CLASS_NAME" type="xs:string" minOccurs="0" />
<xs:element name="CUSTOMER_ATTRIBUTE" type="xs:string" minOccurs="0" />
<xs:element name="ACCOUNT" type="xs:string" minOccurs="0" />
<xs:element name="TAX_BUREAU_ADDRESS" type="xs:string" minOccurs="0" />
<xs:element name="SALES_TERRITORY" type="xs:string" minOccurs="0" />
<xs:element name="REGISTRATION_TYPE" type="xs:string" minOccurs="0" />
<xs:element name="LAST_UPDATED_BY" type="xs:string" minOccurs="0" />
<xs:element name="CREATED_BY" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
- <xs:element name="customer">
- <xs:complexType>
- <xs:sequence>
- <xs:element ref="ns0:customerInfo" maxOccurs="unbounded">
- <xs:annotation>
<xs:documentation>Comment describing your root element</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
- <xs:element name="customerInfo" type="ns0:customertype">
- <xs:annotation>
<xs:documentation>Comment describing your root element</xs:documentation>
</xs:annotation>
</xs:element>
</xs:schema>
</wsdl:types>
- <wsdl:service name="customerInfo">
- <wsdl:port name="SOAPEventSource" binding="tns:SOAPEventSourceBinding">
<soap:address location="http://COMPANHI-F20AF2:8889/RetrieveServices/customerInfo" />
</wsdl:port>
</wsdl:service>
- <wsdl:portType name="customerInterface">
- <wsdl:operation name="customerInput">
<wsdl:input message="tns:customerRequest" />
<wsdl:output message="tns:customerResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SOAPEventSourceBinding" type="tns:customerInterface">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="customerInput">
<soap:operation style="rpc" soapAction="/RetrieveServices/customerInfo" />
- <wsdl:input>
<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://InputMessageNamespace" parts="customerRequestDATA" />
</wsdl:input>
- <wsdl:output>
<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://OutputMessageNamespace" parts="customerResponseDATA" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:message name="customerRequest">
<wsdl:part name="customerRequestDATA" type="ns0:customertype" />
</wsdl:message>
- <wsdl:message name="customerResponse">
<wsdl:part name="customerResponseDATA" type="xs:string" />
</wsdl:message>
</wsdl:definitions>
Now, I'm thinking about what to tell to the customer of my proof of concept :-(
Denis

I do agree that we need to go through Oracle SR process to get any resolution instead of just relying on public forums. That helps you, Oracle and others facing similar issue.
Having said that I also can understand Heizard frustration because I felt the same way some times. Oracle needs to improve on their Support personnel skill set in SOA suite arena. The current support process makes you think twice/thrice...before you log a SR. In most of the cases you feel like training them with the tool set....:-(
Let me give you a real situation. I created a simple test case with file in and file out bound adapter for one of my issues and uploaded to SR. Guess what the analyst came up with....can I do OWC with you to understand the scenario..or SR is missing which file to use to test etc..and the SR goes to @CUS status.....you loose a day or two on this....
Once you were able to get through that first layer you will be impressed the kind of support you get. I am in same boat working aggressively on couple of critical SRs. Once those gets into development court I was able to resolve them in matter of weeks. It's only that getting there took me a while.
So it all depends on what your timelines are and what kind of relationship you have with Oracle (read how deep you are with Oracle products)
ESB is very lightweight and it does some trivial things very quickly. It also lot easier on developers who are new to whole web services world.
So far I have been trying only Doc/Lit services because that's what our standard is and assumed RPC/Lit just works. Now this thread started to worry me as well. So better give it a spin and start Oracle Support fun.....:-)
Regards,
Rajesh

Invoking a jax-rpc based web service from a jsp

hello
i'm trying to invoke a WS from a jsp page, working on tomcat + jwsdp
the ws i'd created and deployed on the server is named TestCNRPS, it contains the method: int exist(int ..)
i wrote this jsp page for testing :
<%@ page contentType="text/html;charset=windows-1252" import="cnrps.*" %>
<HTML>
<HEAD>
<TITLE>Appel service Web</TITLE>
</HEAD>
<BODY>
<%
int num_cin=45475645;
TestCNRPSIF_Stub stub = (TestCNRPSIF_Stub)(new TestCNRPSService_Impl().getTestCNRPSIFPort());
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY,System.getProperty("endpoint"));
out.println(stub.exist(num_cin));
%>
</BODY>
</HTML>
but i received this exception:
java.rmi.RemoteException: Erreur de transport HTTP : java.lang.NullPointerException; nested exception is:
Erreur de transport HTTP : java.lang.NullPointerException
cnrps.TestCNRPSIF_Stub.exist(TestCNRPSIF_Stub.java:87)
org.apache.jsp.invoqueWS_jsp._jspService(invoqueWS_jsp.java:58)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:268)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:258)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:205)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
Has someone an idea ??
thx
ps : i tested the WS from a client class and it worked fine

Hi Paul,
This sound familiar, but I cannot at the moment locate a reference to
the issue. I would encourage you to seek the help of our super support
team [1].
Regards,
Bruce
[1]
http://support.bea.com
[email protected]
Paul Merrigan wrote:
>
I'm trying to invoke a secure 8.1 web service from a 6.1 client application and keep getting rejected with the following message:
Security Violation: User: '<anonymous>' has insufficient permission to access EJB:
In the 6.1 client, I've established a WebServiceProxy and set the userName and password to the proper values, but I can't seem to get past the security.
If there something special I need to do on either the 8.1 securing side or on the 6.1 accessing side to make this work?
Any help would be GREATLY appreciated.

Message-based web service

We are using CF 7.01 and have been successful in consuming
web services in the past. We are unsuccessful however in consuming
a web service where the client says is using a message-based (aka
document style) web service. We are entering thier system but we
error out in our attempt to access thier web service.
In the cfcomponent I have even tried using style="document"
but we are still erroring out. The nature of the error message at
our end shows:
-- start of error message...
Message: Could not generate stub objects for web service
invocation.
Detail: Name:
https://integrationdev.peopleclick.com/soap/echo. WSDL:
https://integrationdev.peopleclick.com/soap/echo. WSDLException (at
/SOAP-ENV:Envelope): faultCode=INVALID_WSDL: Expected element '{
http://schemas.xmlsoap.org/wsdl/}definitions'.:
It is recommended that you use a web browser to retrieve and
examine the requested WSDL document for correctness. If the
requested WSDL document can't be retrieved or it is dynamically
generated, it is likely that the target web service has programming
errors.
-- ...end of error message.
The message insinuates a WSDL problem. I understand
message-based web services don't use a WSDL. Must I remove
something from our standard RPC-based web service configuration?
Thanks in advance.
Dev

hi all,
UPDATE:
i have some how managed to handle my error at both REQUEST MESSAGE peoplecode and at HANDLER peoplecode. Tested the webservice using SOAPUI tool. After passing all inputs required, the customer is not created and i am getting a blank response message which should contain the SETID and CUST_ID as response. Please help me out whether i am missing any Key part in creating a CUSTOMER. Note, i haven't written any Peoplecode for creation and i am also not aware how to do the same or where to write the logic for it.
Kindly bare with me and do help me out as i m struck with it for long. Thanks in advance

(261705413) Q RPCC-21 Can you compare a performance of "usual" RPC from EJB and RPC from Web Services?

Q<RPCC-21> Can you compare a performance of "usual" RPC from EJB and RPC from Web
Services?
A<RPCC-21> There are additional performance overheads for invoking a web service
when compared to straight EJB invocation. However, you should not think of web
services as a way to replace your EJBs instead you should be willing to accept
some performance decline for the massive gains in platform interoperability and
the ability to exposure your services outside of you firewall.
Additionally, performance decreases will be dependent on several factors. The
most significant of which is the XML-Java and Java-XML translation of the SOAP
message. This can be very fast if the XML structure is simple but if you web services
requires a parameter that has a complex XML format you may see a more significant
slow down.
Adam

Sorry if this sounds like I am new to this but I am.
So, the extended version is the format that would be used if you were not utilizing the files that the wsdl2java function creates?
And this is done to when you want more flexibiility for the user to call your service?
So, you would push to have the stub files used when you want to control how the web service is used?
thanks for the feedback.

RPC Style Web Service and SSL

Hi,
Has anyone tried (and maybe succeeded) in accessing an
RPC-style Web Service deployed on WebLogic Server 6.1 using
SSL? I have a Web Service deployed and am able to access it using JNDI and the
weblogic.soap.http.SoapInitialContextFactory
INITIAL_CONTEXT_FACTORY. However, when I try to set the
Context.SECURITY_PROTOCOL to "ssl" and access the secure port,
I get a "java.net.SocketException: Unexpected end of file from
the server" error message.
Does the weblogic.soap.http.SoapInitialContextFactory not
support SSL? Do I need to do the SOAP/XML messaging myself,
without being able to make use of the WebLogic convenience
classes? Thanks! Rob

Alright!
Glad you got it working ;-)
Actually, the problem with the protocol being hardcoded to http in the wsdl.jsp,
is a bit strange. It's unusual that the BEA engineers that coded the wsgen component
and support classes, didn't use something like the following:
<soap:address location="<%= request.getScheme() + "://" + request.getServerName()
+ ":" + request.getServerPort() %>/security/examples/webservices/security/PhoneBookService"/>
I don't use wsgen too much, because I need to have more control over the J2EE
packaging. It (wsgen) is great for spitting out stuff, but not really setup for
doing Web service packaging that use classes (i.e. helper files, frameworks, etc.)
that it doesn't generate. I think they (BEA) might be looking into integrating
the Web Services assembly process with other tools like WebGain, Forte, etc. to
alleviate these types of issues.
Anyway, glad you got it working, so now you can help somebody else (time permitting,
of course) with this topic in the future!
Regards,
Mike Wooten
"Rob Nelson" <[email protected]> wrote:
>
Mike,
Thank you very much for your response! The next to
last sentence did it for me (when you mentioned checking
that the location attribute of the soap:address element
was set properly)! I noticed that when I viewed the WSDL
file via the browser (by clicking on the link in the
index.html page), I saw http://host:<unsecure_port> when
I requested it over the unsecure port, but I saw
http://host:<secure_port> when I requested the WSDL over
the secure port. Notice it did not say https!
So, I unjarred the EAR file that was generated by my
wsgen task, and then unjarred the generated WAR file
contained therein. When I looked at wsdl.jsp, I noticed
that "http" was hard-coded in the location attribute, but
that the host name and port number were dynamically
generated. So I added a scriplet to dynamically place an
"s" after "http" (if request.isSecure()) and rejarred up
the WAR and EAR files.
Now when I deployed the EAR file, I see "https" when
I request the WSDL over the secure port, and my client
(actually your client;) works! Awesome! I really appreciate
your help! Now my only issue is why did the wsdl.jsp have
"http" hard-coded, not accounting for secure requests.
These files were generated by the WSGEN task in ANT.
I figure it's either: I have a configuration problem,
I have a problem with my ANT build script, my version of
WebLogic Server (6.1 w/SP1 built 9/18/2001) has a bug, or
maybe you just have to manually go in and modify the wsdl.jsp
file if you want to use https :(. Please let me know if
you have any insight on this, and I will also follow up
with WebLogic support. Thanks again! Rob
"Michael Wooten" <[email protected]> wrote:
Hi Rob,
I am absolutely sure the code I posted works, so we need to approach
this from
a different angle ;-)
First, I know why the Context.SECURITY_PROTOCOL approach doesn't works.
It's because
the namespace in the Web Services code examples is not the same oneas
the one
used for RMI objects, EJBs, JDBC Data Sources, etc. For those objects,
the Context.PROVIDER_URL
is something like "t3://localhost:7001", and the INITIAL_CONTEXT_FACTORY
is "weblogic.jndi.WLInitialContextFactory".
The one being used with WebLogic Web Services, is mainly just functioning
as a
mechanism for manufacturing WebServiceProxy objects, because it is a
non-instanciable!
It does this by using a subclass of javax.naming.Context called SOAPContext,
which
is completely hidden from you, but also doesn't do much except implement
the lookup()
method. The implementation of this method ignores the Context.SECURITY_URL
property,
but it does pay attention to the "java.naming.security.principal" and
"java.naming.security.credentials"
properties. You don't need these properties for SSL, just Basic Authentication.
Enough about that, though. The service end-point is a servlet right?
So this means
it has a URL that begins with http or https, which in turn means the
WebLogic
servlet engine gets the SOAP request and sends it to the StatelessSessionAdapter
servlet. To WLS, this is just like any other HTTP/HTTPS request sent
to it ;-)
There is no special "SOAP-related" HTTP/HTTPS handler in WLS, but the
SSL challenge
dance still happens. So my first question is, are you sure you havethe
HTTPS
attributes set properly in the WebLogic console. SSL/HTTPS should be
enabled and
the "Hostname Verification Ignored" checkbox should be checked. Next,
are you
sure the URL assigned to the location attribute of the <service> element
in the
WSDL is correct (i.e. https://localhost:7002)? Are you using the "dynamic
client"
approach?
Regards,
Mike Wooten
"Rob Nelson" <[email protected]> wrote:
Mike,
Thanks for your response. I downloaded the code example that
you
posted
last week, as well as the code example that you posted in October for
a similar
request (BEA Support pointed me towards that). Unfortunately, I still
can't get
the Web Service to respond to the client request when the client uses
the HTTPS
port for the WebLogic Server.
I tried two different client approaches. The first uses the client
code
that you posted in October, the WebServiceProxy approach. The second
approach
is based on the example in the WebLogic documentation, which uses the
weblogic.soap.SoapInitialContextFactory
class with the javax.naming.Context object to perform a lookup on the
service
(which closely resembles rmi without the narrowing).
Both client classes fail to invoke the the service itself viaHTTPS
(although
they both work when making HTTP requests to the unsecure port). However,
when
I run the client based on the client class that you posted in October
and make
an HTTPS request, I can see in the output where it is able to download
the WSDL
file and use it (via the WebServiceProxy) to describe the availablemethods
for
the associated Web Service. It is only when the actual invoke() method
is called
on the SoapMethod object (which in turn sends the XML request to the
Web Service
Servlet), that the server doesn't respond, and the client fails with
an UnexpectedEndOfFileException
(i.e. no response).
So, do you know why the servlet that the RPC-style Web Serviceuses
to handle
requests would not respond to HTTPS requests, when it processes HTTP
requests
without a problem (using the same client code that fails with the HTTPS
request)?
I am using WebLogic Server 6.1 w/SP1 on a Solaris 8 platform. Thanks
for any
advice you can give me! Rob
"Michael Wooten" <[email protected]> wrote:
Hi Rob,
Check out the attached zip for "insights" into how to do this. It
contains
the
code for two Web service "consumers" (that the new fangled word fora
"client")
and the web.xml and weblogic.xml for the RPC-style Web Service, that
they consume.
Hope this helps,
Mike Wooten
"Rob Nelson" <[email protected]> wrote:
Hi,
Has anyone tried (and maybe succeeded) in accessing an
RPC-style Web Service deployed on WebLogic Server 6.1 using
SSL? I have a Web Service deployed and am able to access it using
JNDI
and the
weblogic.soap.http.SoapInitialContextFactory
INITIAL_CONTEXT_FACTORY. However, when I try to set the
Context.SECURITY_PROTOCOL to "ssl" and access the secure port,
I get a "java.net.SocketException: Unexpected end of file from
the server" error message.
Does the weblogic.soap.http.SoapInitialContextFactory not
support SSL? Do I need to do the SOAP/XML messaging myself,
without being able to make use of the WebLogic convenience
classes? Thanks! Rob

How to call an ABAP based web service from a web page (form)

Hi,
I am trying to figure out how I can call my own developed ABAP based web service. I was able to successfully test it in the WS navigator and am now wondering what I need to do to embed the service call in a plain simply web page (form). Basically I'd like to create a web form allowing to specify the parameters and with a 'Submit' button pass the parameters to the web service and launch it.
Is this possible or do I need some kind of SDK to accomplish this?
Thanks for any hints and tips.
Wolfgang

Hi,
refer the following link and this is for cosuming the web service form Web dynpro Java
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50d70a19-45a3-2b10-bba0-807d819daf46&overridelayout=true
and please go throught the following link if you want to cosume it through web dynpro abap and find the answer given by the Moderator Thomas Jung
regards
Manohar

Retrieving client ip from RPC-style web service

Hi,
I've got an rpc-style web service and I would like to log the incoming client
ip address (i.e. I need to get at the HTTPRequest object). Can this be done by
passing some kind of SOAP context parameter in the argument list of my exposed
methods? If this is not doable, is implementing SOAP message handlers the way
to to go? I would rather not do the latter, as the web service is working well
and don't want to play with my code too much.
Thanks

I tried this, following the example in http://e-docs.bea.com/wls/docs70/webapp/filters.html,
but I still can't get it to work. The init() method gets called, but doFilter(ServletRequest
req, ServletResponse resp, FilterChain fc) does not. The "filter" part of my
web.xml looks like:
<filter>
<filter-name>serviceFilter</filter-name>
<filter-class>webservices.ServiceFilterImpl</filter-class>
</filter>
<filter-mapping>
<filter-name>serviceFilter</filter-name>
<url-pattern>/myPattern/myWebService</url-pattern>
</filter-mapping>
The only thing I could thing of is that maybe my url-pattern is wrong, although
this seems unlikely as my web service is able to process requests sent using
http://myWLSMachine:7001/myPattern/myWebService.
In fact, in the the WLS access.log file, I have:
[07/Oct/2002:11:51:01 -0400] "POST /myPattern/myWebService HTTP/1.0" 200 3011.
Do you know if there's something in the JAX-RPC API that I could use to get at
the client ip address? I dug through the documentation and came across something
called "ServletEndpointContext", but I'm not sure if this will do the trick.
Thanks for your time,
Danielle
"manoj cheenath" <[email protected]> wrote:
One way to do this may be to write a servlet filter
and map the filter to the URL of your service.
regards,
-manoj
"Danielle Vella" <[email protected]> wrote in message
news:[email protected]..
Hi,
I've got an rpc-style web service and I would like to log the incomingclient
ip address (i.e. I need to get at the HTTPRequest object). Can thisbe
done by
passing some kind of SOAP context parameter in the argument list ofmy
exposed
methods? If this is not doable, is implementing SOAP message handlersthe
way
to to go? I would rather not do the latter, as the web service isworking
well
and don't want to play with my code too much.
Thanks

RPC style web service client

hi,
i am new to web service technology. i want to create dynamic web service client for a "rpc" style web service in Netbeans.
please, can anybody guide me for this?
thanks in advance.

Hi,
To avoid creating new topic I will put my question here.
I try to create new web service (rpc-style) client in netbeans. I have rpc plugin installed. In ejb module node I right click > new > web service client >
I fill all filds, chose rpc-style and > after clicking finish - error occur:java.lang.LinkageError: com/sun/xml/rpc/processor/generator/Names
     at org.netbeans.modules.websvc.registry.util.Util.getParameterType(Util.java:856)
     at org.netbeans.modules.websvc.registry.jaxrpc.WrapperClientWriter.printOperations(WrapperClientWriter.java:275)
     at org.netbeans.modules.websvc.registry.jaxrpc.WrapperClientWriter.writeClass(WrapperClientWriter.java:219)
     at org.netbeans.modules.websvc.registry.jaxrpc.Wsdl2Java.createWrapperClients(Wsdl2Java.java:305)
     at org.netbeans.modules.websvc.registry.jaxrpc.Wsdl2Java.execute(Wsdl2Java.java:229)
     at org.netbeans.modules.websvc.registry.util.Util.createWSJar(Util.java:493)
     at org.netbeans.modules.websvc.registry.RegistryViewImpl.registerService(RegistryViewImpl.java:221)
     at org.netbeans.modules.websvc.registry.RegistryViewImpl.registerService(RegistryViewImpl.java:159)
     at org.netbeans.modules.websvc.registry.netbeans.RegisterViewImplNetBeansSide.registerService(RegisterViewImplNetBeansSide.java:91)
     at org.netbeans.modules.websvc.jaxrpc.client.wizard.ClientBuilder.generate(ClientBuilder.java:330)
     at org.netbeans.modules.websvc.jaxrpc.client.wizard.JaxRpcClientCreator$2.run(JaxRpcClientCreator.java:319)
     at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)
I use netbeans 6.5. In my project I choose java ee 5 as in 1.4 there is no web service client option
Any ideas?
I found some rpc tutorils for netbeans 4.0 but I wonder why it couldn't be done in netbean 6.5
Regards,
Lech

[Integrated SOA Gateway] Publish Java based web service

Welcome!
Lately I have been trying to publish Java based web service through Integrated SOA Gateway. The documentation states that:
+"Custom interface definitions can be created for various interface types including custom interface definitions for XML Gateway Map, Business Event, PL/SQL, Concurrent Program, Business Service Object, Java (except for Java APIs for Forms subtype) and Composite Service for BPEL type."+ (Integrated SOA Gateway Developer's Guide Release 12.1, "Creating and Using Custom Integration Interfaces")
After familiarizing myself with $FND_TOP/bin/irep_parser.pl and $FND_TOP/bin/FNDLOAD tools, I have started coding my POJOs. Initially I have come up with three classes - request/response objects and service implementation. Service implementation has been annotated with "@rep:X" descriptors according to "Java Annotations" section of the documentation. While invoking $FND_TOP/bin/irep_parser.pl I have received errors about class resolution. My solution was to transform request and response types to static inner classes. This way I ended up with one *.java source file (see below).
* Sample ISG Service.
* @rep:scope public
* @rep:product AP
* @rep:displayname My Custom ISG Service.
public class MyService {
public static class Request {
private String id;
public void setId(String id) {
this.id = id;
public String getId() {
return id;
public static class Response {
private String data;
public void setData(String data) {
this.data = data;
public String getData() {
return data;
* Sample operation.
* @param request Request Object.
* @return Return Object.
* @rep:displayname Test operation.
* @rep:category BUSINESS_ENTITY SAMPLE_SERVICE
public MyService.Response testOperation(MyService.Request request) {
MyService.Response response = new MyService.Response();
response.setData("Some Data");
return response;
ILDT file has been successfully created and uploaded. However, I could not see the "Generate WSDL" button on Integrated Repository website. Is there any particular interface or superclass that my service implementation should extend? I have reviewed "PurchaseOrderSDO" example posted in the developer's guide (page 407), but I couldn't come up with a working solution. Could you provide me with more detailed tutorial/example? Which documentation sections should I read again?
After searching through forum, I have spotted $FND_TOP/bin/soagenerate.sh script, and thought that lack of "Generate WSDL" button was an EBS defect. After running the script, I have received an error:
Error in Service Generation.
ServiceGenerationError: Interface Type (JAVA) Interface SubType (null) is not supported.
oracle.apps.fnd.soa.util.SOAException: ServiceGenerationError: Interface Type (JAVA) Interface SubType (null) is not supported.
     at oracle.apps.fnd.soa.provider.wsdl.ArtifactsFactory.getArtifactsGenerator(ArtifactsFactory.java:55)
     at oracle.apps.fnd.soa.provider.wsdl.WSDLGenerator.generateServiceWSDL(WSDLGenerator.java:128)
     at oracle.apps.fnd.soa.provider.wsdl.ServiceGenerator.generateSOAService(ServiceGenerator.java:75)
     at oracle.apps.fnd.soa.provider.wsdl.ServiceGenerator.generateSingleService(ServiceGenerator.java:88)
     at oracle.apps.fnd.soa.provider.wsdl.ServiceGenerator.main(ServiceGenerator.java:419)
I would be grateful for any suggestions. Has anyone published Java based web service through ISG?
Best regards,
Lukasz

I tried the following as per Oracle support and able to generate the wsdl though, but not invoke the webservices.
1. Applied the patch 8607523
2. Took the translator.jar file from the patch 8857799 and replaced the current translator.jar file
3. Deploy the adapters.
$FND_TOP/bin/txkrun.pl -script=CfgOC4JApp -applicationname=pcapps
-oc4jpass=welcome -runautoconfig=No

Hi all: Change language Code in CI based web services.

I am developing CI based soap web services in peoplesoft. i want response in different in languages. I need that language is selected at request time. mean need to change Language Code in CI based web services.
Can anybody help me?
thanks

You posted a duplicated thread here :
Hi all: Change language Code in CI based web services.
-- mod. action: locking this one --
Nicolas.

Handling sessions in Web Services

Hi all,
I am quite new to Web Services. I am facing problems in handling sessions in Web Services.
I am using Apache Axis as SOAP engine. I have different Web Services like AuthenticationService, DataService and ReportService.
The problem is in handling authentication. I need to authenticate only once using AuthenticationService and maintain the
session for rest of the calls to different web services like DataService, ReportService.
Has anyone faced similar situation?
Please help.
Thanks,
Prashanth

a bit unspecific, anyway, here a solution for a plain JAX-RPC implementation
in a JAX-RPC client, use
((javax.xml.rpc.Stub)myProxy)._setProperty(javax.xml.rpc.Stub.SESSION_MAINTAIN_PROPERTY, Boolean.TRUE);
to let the client maintain session state
in JAX-RPC server, implement ServiceLifecycle and call getHttpSession() on the servlet endpoint context
Merten

Can IREP can be utlized to "DEPLOY" web services in 11.5.10

Hi
IREP is a wonderful repository of all service endpoints or say compilation of all integrations for Ebiz suite.
From R12 onwards it even helps deploy web services.
But I can't seem to understand how in R11.5.10 could IREP help to deploy a web service. If the idea is to access IREP from Jdeveloper within a BPEL or ESB project then that is a separate thing and is recommended.
In 11.5.10 it appears otherwise IREP just provides a generic WSDL that is not specific to a particular Application instance since irep in 11.5.10 doesn't ship with the install.
How can one deploy a web service in 11.5.10 from IREP?

Hi
You have to read XML gateway documentation to get an idea for this. R11.5.10 gives you a generic WSDL for you to supply to your web service subscribers. I was able to enqueue a message successfully through BPEL by utilizing the WSDL supplied by R11.5.10 instead of using an AQ or Oracle Adapter.
The functionality of IREP is much more exploited in R12 compared to 11.5.10 and my personal beleif is that from R12 onwards it is of much use. Look at R12 IREP documentation. You will need to log in as sysadmin or with integration repository admin priveledge to deploy the web service but you can see it through other users as long as the resp is assigned to you and you can deploy XML Gateway and Service Beans based web services from with in R12.
Good Luck

2-java clients communicate with java based web-service

I'm new 2 web-services.
I need to create 2-java clients(a game like chess) & communicate them through a java based web-service.
I can create the web service.(using Netbeans getting started tutorial.only the basic stuff)
when we create the 2-clients are those should be web-clients or are they should be normal java
applications.
(clients should be GUI based)
??

I'm new 2 web-services.
I need to create 2-java clients(a game like chess) & communicate them through a java based web-service.
I can create the web service.(using Netbeans getting started tutorial.only the basic stuff)
when we create the 2-clients are those should be web-clients or are they should be normal java
applications.
(clients should be GUI based)
??

Document-based web services - WebLogic 8.1

Hi all, 
I'm exposing a stateless session bean method as a web service. The in/out parameters are XML documents so my method signature looks as follows:
 
public Document collectMessages( Document request )
 
Accordingly I want to use document-based web services. I use servicegen to create all server-side classes required for the web service.
 
I'm testing the service from the WebLogic provided test page. For document-based services, the text-area is initially populated with the following content
 
<pre>
<['http://www.revenue.ie/webservices/ris/rcm/webservices']:RcmCollectRequest/></pre>
 
When I invoke the service I get the following error:
 
<pre>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Body>
<env:Fault>
<faultcode>Client</faultcode>
<faultstring>Unable to find a matching Operation for this remote invocation <RcmCollectRequest>
</RcmCollectRequest>. Please check your operation name. </faultstring>
</env:Fault>
</env:Body>
</env:Envelope></pre>
 
I've searched for this error and seen it in the forum only a number of times. It seems as though some manual manipulation of the web-services.xml document can solve it. Does anyone have an example? My web-services.xml document looks as follows:
 
<pre><?xml version="1.0" encoding="UTF-8"?>
<web-services>
 <web-service useSOAP12="false" targetNamespace="http://www.revenue.ie/webservices/ris/rcm/webservices" name="rcmmessageservices" style="document" uri="/">
 <types>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="http://www.revenue.ie/webservices/ris/rcm/webservices" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="http://www.revenue.ie/webservices/ris/rcm/webservices">
 <xsd:element type="xsd:anyType" name="RcmCollectRequest" nillable="true">
</xsd:element>
 <xsd:element type="xsd:anyType" name="RcmCollectResponse" nillable="true">
</xsd:element>
 </xsd:schema>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:ie.revenue.rcm.ejb.session" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:ie.revenue.rcm.ejb.session">
 <xsd:element type="stns:InvalidRequestException" name="InvalidRequestException">
</xsd:element>
 <xsd:element type="stns:SystemUnavailableException" name="SystemUnavailableException">
</xsd:element>
 <xsd:complexType name="InvalidRequestException">
</xsd:complexType>
 <xsd:complexType name="SystemUnavailableException">
</xsd:complexType>
 </xsd:schema>
 </types>
 <type-mapping>
 <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:p2="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p2:RcmCollectResponse" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
 <type-mapping-entry deserializer="ie.revenue.rcm.ejb.session.SystemUnavailableExceptionCodec" xmlns:p3="java:ie.revenue.rcm.ejb.session" type="p3:SystemUnavailableException" serializer="ie.revenue.rcm.ejb.session.SystemUnavailableExceptionCodec" class-name="ie.revenue.rcm.ejb.session.SystemUnavailableException">
</type-mapping-entry>
 <type-mapping-entry deserializer="ie.revenue.rcm.ejb.session.InvalidRequestExceptionCodec" xmlns:p4="java:ie.revenue.rcm.ejb.session" type="p4:InvalidRequestException" serializer="ie.revenue.rcm.ejb.session.InvalidRequestExceptionCodec" class-name="ie.revenue.rcm.ejb.session.InvalidRequestException">
</type-mapping-entry>
 <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:anyType" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
 <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:p1="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p1:RcmCollectRequest" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
 </type-mapping>
 <components>
 <stateless-ejb name="ejbcomp0">
 <ejb-link path="rcm-ejb-1.0.jar#CustomerMessageController">
</ejb-link>
 </stateless-ejb>
 </components>
 <operations>
 <operation name="collectMessages" method="collectMessages(org.w3c.dom.Document)" component="ejbcomp0">
 <params>
 <param style="in" xmlns:p1="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p1:RcmCollectRequest" location="body" name="document" class-name="org.w3c.dom.Document">
</param>
 <return-param xmlns:p2="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p2:RcmCollectResponse" location="body" name="result" class-name="org.w3c.dom.Document">
</return-param>
 <fault xmlns:p3="java:ie.revenue.rcm.ejb.session" type="p3:SystemUnavailableException" class-name="ie.revenue.rcm.ejb.session.SystemUnavailableException" name="SystemUnavailableException">
</fault>
 <fault xmlns:p4="java:ie.revenue.rcm.ejb.session" type="p4:InvalidRequestException" class-name="ie.revenue.rcm.ejb.session.InvalidRequestException" name="InvalidRequestException">
</fault>
 </params>
 </operation>
 </operations>
 </web-service>
</web-services>
</pre>
 
Thanks in advance, 
Eoin

Hi Eoin,
I had the exact problem. Struggled a lot and still couldn't figure out. I think its a problem in 8.1. Not sure. Might want to check with the support guys. If you are struck with 8.1 and still couldn't figure out, AXIS would be a option for you. Just an FYI. Thats what we are doing now.
Luckily for us we are migrating to 9.1 and I just completed a POC for doc oriented webservices in 9.1. It works like a charm.
Thanks and good luck
- Aspert

Can XI handle RPC based web services ?

Similar Messages

Maybe you are looking for