Handle Webservice Respons

Hello everybody,
Here my scenario: I want to send an IDOC from SAP to a third-party system via webservice. This is a synchronous scenario.
Now I want to achieve that the response and the original IDOC go into another IDOC and back to SAP.
How do I build this? I have problems to get my response message into the operation mapping. I have only one service interface with sychronous communication. And when I add this interface in the operation mapping, the request message of the webservice is chosen as original message and not the response.
I hope somebody can help me.
Best Regards
Martin

Hi Martin,
you need to insert those two beans in your module configuration to build the bridge:
RequestResponseBean
RequestOnewayBean
you may also check this:
http://help.sap.com/saphelp_nw04/helpdata/en/45/20d2b4c20a0732e10000000a155369/frameset.htm
best regards,
Markus

Similar Messages

How to handle Webservice

Hi Experts,
I want to know how to handle webservice in web Dynpro Application.
I need some documentation regarding this.
can any one help me.
Advance Thanks,
P.J.Balaji

Hi Balaji,
Check These links..
<a href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/wdjava/faq-Models-AdaptiveWebService&">Adaptive Webservices</a>
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/6bfb2c4e-0a01-0010-8eb4-f21a42d8f6ec [original link is broken] [original link is broken]
<a href="http://www.systinet.com/resources/tutorials">Webservice tutorials</a>
<a href="http://www.onjava.com/pub/a/onjava/2001/08/07/webservices.html">Java Webservices and Primer</a>
<a href="http://www.learningtree.com/courses/577.htm">Building XML webservices with Java</a>
[url=http://www.accelebrate.com/java_webservices_training/web_services.htm]Introduction[/url]
Urs GS

Handling WebService with more than one operation

Hi Everybody,
I have a hassle!
First of All, I'm Newbie, using Oracle Service Bus
I have to Implement a WS with aproximately 6 operations, in Service Bus.
I create my WSD and my XSD Artifacts, with no problem, the issue comes when I try to create My Proxy Service in OSB
Step 1 .- Create Proxy Service
Step 2 .- I make a Link from my Proxy Service to my Business Service wich contains the WSDL with the 6 operations
Step 3 .- I clic on edit the message flow in the actions panel to add route
Step 4 .- I edit the route looking for a Webservice and selecting the method (In this Case I select one method, because I don't know how to route many operations in one Proxy Service)
When I did that, my WS in OSB wasn't able to invoke one method. I got a timeout .. I don't know, if maybe I'm doing something wrong!!.
What I want is a way to route many methods in a same Web Service
I've done operational bifurcation in the Web Proxy.. With that component, I can choose methods like conditionals, and I can add a route destination for each method.. when I test it .. My OSB WS never reply me an asnwer, I got Timeout. Takes a lot of time
I also tried to do it with IF ELSE conditionals trying to know the name of the method from the WLS Headers and routing them to a specific webservice method. But I couldn't do it!
I check the WS out by itself and works in 2 seconds, so it's Working!
Any clues?, Well I hope you can help me!!
Thanks in Advance!
Edited by: user11334562 on 05-ago-2011 17:38

Pierluigi,
Thanks for your answer,
I had to rebuild my OSB project, and refact all my OSB artifacts,
My Proxy Service, I was trying to do it with my WSDL again, when I already had done in a Business Service,
So in my proxy I chose the BS instead WSDL and all Works Perfectly using SOAP Content.
Pretty Thanks!!
ABC

BPEL-- Urgent- Handling webservice call failures

Urgent-->We have to do a webservice call in our BPEL Process.If the webservice call fails it has to wait for 3 mins and retry again.Please suggets me some solution.I dont want to use WAIT BPEL Activity or JAVA thread.sleep.Any more ideas.Oracle Team help

Here is my composite.xml
<?xml version="1.0" encoding="UTF-8" ?>

<composite name="Call_ECM"
revision="930.0"
label="2009-08-24_22-32-06_694"
mode="active"
state="on"
xmlns="http://xmlns.oracle.com/sca/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:ui="http://xmlns.oracle.com/soa/designer/">
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/jms/SalesSupport/Call_ECM/InboundJMSConsume_PL%2F"
location="InboundJMSConsume_PL.wsdl" importType="wsdl"/>
<import namespace="ATVECMSRCREATE"
location="ATVECMSRCREATE_ATVECMSRCREATERef.wsdl" importType="wsdl"/>
<import namespace="http://xmlns.oracle.com/ias/pcbpel/NotificationService"
location="NotificationService.wsdl" importType="wsdl"/>
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/jms/SalesSupport/Call_ECM/OFMW_Logging_BAM_JMS_PRO%2F"
location="OFMW_Logging_BAM_JMS_PRO.wsdl" importType="wsdl"/>
<service name="InboundJMSConsume_PL"
ui:wsdlLocation="InboundJMSConsume_PL.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/jms/SalesSupport/Call_ECM/InboundJMSConsume_PL%2F#wsdl.interface(Consume_Message_ptt)"/>
<binding.jca config="InboundJMSConsume_PL_jms.jca"/>
</service>
<component name="SalesSupport___Siebel">
<implementation.bpel src="SalesSupport___Siebel.bpel"/>
<property name="activationAgent.InboundJMSConsume_PL.className"
type="xs:string" many="false">oracle.tip.adapter.fw.agent.jca.JCAActivationAgent</property>
<property name="activationAgent.InboundJMSConsume_PL.portType"
type="xs:string" many="false">Consume_Message_ptt</property>
<property name="configuration.transaction" type="xs:string"
many="false">requires</property>
</component>
<reference name="_OutboundWSSiebelInvoke_PL"
ui:wsdlLocation="ATVECMSRCREATE_ATVECMSRCREATERef.wsdl">
<interface.wsdl interface="ATVECMSRCREATE#wsdl.interface(ATVECMSRCREATEPORT)"/>
<binding.ws port="ATVECMSRCREATE#wsdl.endpoint(ATVECMSRCREATE/ATVECMSRCREATEPORT)"
location="ATVECMSRCREATE_ATVECMSRCREATERef.wsdl"/>
</reference>
<reference name="NotificationService"
ui:wsdlLocation="NotificationService.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/ias/pcbpel/NotificationService#wsdl.interface(NotificationService)"/>
<binding.wsif port="http://xmlns.oracle.com/ias/pcbpel/NotificationService#wsdl.endpoint(NotificationService/JavaPort)"
location="NotificationService.wsdl"/>
</reference>
<reference name="OFMW_Logging_BAM_JMS_PRO"
ui:wsdlLocation="OFMW_Logging_BAM_JMS_PRO.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/jms/SalesSupport/Call_ECM/OFMW_Logging_BAM_JMS_PRO%2F#wsdl.interface(Produce_Message_ptt)"/>
<binding.jca config="OFMW_Logging_BAM_JMS_PRO_jms.jca"/>
</reference>
<wire>
<source.uri>InboundJMSConsume_PL</source.uri>
<target.uri>SalesSupport_CallECM_ACom_Siebel/InboundJMSConsume_PL</target.uri>
</wire>
<wire>
<source.uri>SalesSupport_CallECM_ACom_Siebel/_OutboundWSSiebelInvoke_PL</source.uri>
<target.uri>OutboundWSSiebelInvokePL</target.uri>
</wire>
<wire>
<source.uri>SalesSupport_CallECM_ACom_Siebel/NotificationService</source.uri>
<target.uri>NotificationService</target.uri>
</wire>
<wire>
<source.uri>SalesSupport_CallECM_ACom_Siebel/OFMW_Logging_BAM_JMS_PRO</source.uri>
<target.uri>OFMW_Logging_BAM_JMS_PRO</target.uri>
</wire>
</composite>
Edited by: user11082822 on Nov 17, 2009 9:54 AM

PDF calling webservice - handling an incorrect authentication password

Hi All,
I have a PDF, connected to a webservice.
Connecting to this webservice requires authentication (username & password).
In the event that the user enters an incorrect password, how do I handle this on the PDF form?
I noticed in LC server logs, it logs that an incorrect password was attempted on a WSDL, however I dont seem to be getting anything back.
I have put a try catch around the connection in the PDF, but I recieve nothing.
Surely, I am missing something here about handling Webservice responses when calling from a PDF.
Thanks in advance.

Hi Gerben,
Thanks for hint. I created a new credential for SOAP. But there is a new issue. While calling the webservice, parameters are not passed properly. Service provider considers those values as null and returns an exception. Am I missing any other setting here?
I have checked Admin guide already. But not much of help.
Thanks
Arun Raghavan

Ignoring Http basic authentication header in wls 7.0.sp2 web service servlet (weblogic.webservice.server.servlet.WebServiceServlet)

Hi!
We need to implement authentication using our own methods, and the authentication
information is provided to the web service implementation in a basic authentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles web services
in
wls 7.0.sp2, always attempts to perform authentication, if the header is present.
Is there any way to circumvent this, because we want to implement authentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for our own
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet, which
would
remove the basic authentication header, and put the authentication info in custom
headers, such as x-auth: <user:password>, or smthng similar, and after successful
authentication, make a call to bea's servlet weblogic.webservice.server.servlet.WebServiceServlet.
But still, I'd like to know if there is any way to tell bea's servlet to ignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

Currently there is no option to turn off security check.
I think you can use a servlet filter mapped to the URL
of your service, instead of a proxy servlet?
Regards,
-manoj
http://manojc.com
"Toni Nykanen" <[email protected]> wrote in message
news:3ef1577b$[email protected]..
>
Hi!
We need to implement authentication using our own methods, and theauthentication
information is provided to the web service implementation in a basicauthentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
in
wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
Is there any way to circumvent this, because we want to implementauthentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for ourown
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet,which
would
remove the basic authentication header, and put the authentication info incustom
headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
>
But still, I'd like to know if there is any way to tell bea's servlet toignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

SOAP Webservice returns Array - how to setup Xcelsius?

Hello,
after a lot of tests I have recognized that Xcelsius is not able to handle Webservices which return arrays with an undefined size. So I edited the schema file in the way that the size is defined.
Here is an extract of the schema file:
<xsd:sequence>
            <xsd:element name="row0" type="tns:Row" maxOccurs="10" minOccurs="10" ></xsd:element>
</xsd:sequence>
With that configuration Xcelsius is able to import the wsdl. But the preview window is showing only one Row Folder, I have excpected "10". My question is, is my config the right way to handle arrays with Xcelsius and when it is, how I have to set up the range in the Excel Map to make the data avaiable???
Thank you in advance.
Best regards,
Conrad

Here is an example, you can compare what is different. From the look of it the recipient info is missing from yours. Does it say which INI option is missing when you get an error?
<doPublishRequest xsi:type="doPublishReq_Import" xmlns="http://webservices.docucorp.com/ewps/schema/2005-12-01">
        <LibraryId>CONFIGNAME</LibraryId>
        <DistributionOptions xsi:type="DistributionOptions_ADHOC" source="ADHOC">
          <Priority>REALTIME</Priority>
          <Channel xsi:type="Channel_IMMEDIATE">
            <PublishType>PDF</PublishType>
            <DistributionType>IMMEDIATE</DistributionType>
            <Disposition location="ATTACH" />
            <Recipient name="ORIGINAL">
              <Props>
                <Prop name="" />
              </Props>
              <Copies />
              <Story StoryName="" id="" alias="" />
            </Recipient>
          </Channel>
        </DistributionOptions>
        <SourceType>IMPORT</SourceType>
        <Import>
          <ImportFile xsi:type="ImportFile_ATTACH" d6p1:contentType="" location="ATTACH" xmlns:d6p1="http://www.w3.org/2005/05/xmlmime">O05hdXRpbH.......</ImportFile>
        </Import>
      </doPublishRequest>

Calling Amazon URL with XML response

Hello,
I would like to call a specific amazon-services via http://webservices.amazon.de/onca/xml?Service=AWSECommerceService&AWSAccessKeyId=myAC&AssociateTag=associateTag-21&ItemId=9783836212007&ResponseGroup=Large&Operation=ItemLookup but this is not a web service (I think).
Could someone tell me have to call the URL and how I can handle the response? With a web service or bapi it wouldnu2019t be a problem but I donu2019t know to handle thisu2026
I will try it out with CL_HTTP_CLIENT (hint of Thomas Jung). But did this someone before and how to handle the respone XML?
Can someone help me out with this?
Thx, Vanessa

you can consume this either using SOAP protocol of using REST approach (CL_HTTP_CLIENT)
on how to consume this using CL_HTTP_CLIENT, just do a where used list of this class in your system or search here in the forum, you will find lot of examples.
more on this how to construct the url for this can be found at
http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/index.html?rest-signature.html
once you consume this and get the xml result, you can either parse it using XSLT program or if you are not comfortable you can use FM SMUM_XML_PARSE to parse the XML
Hope this helps.
Regards
Raja

JBoss 4 to Sun Application Server...where to start

Hi there...
I'm charged with making sure my company's product, which has mostly been running on JBoss, works w/ Sun Application Server.
I've been trying to use the Migration Tool with poor results...I know some of it is because it's for JBoss 3 and not 4....
giving it the entire .EAR for our product tells me that it doesn't handle webservices...diving into the EAR's JAR containing our services and removing webservices.xml gives the same result of various permutations of putting in source code / xml leads , namely it runs and then freezes with
DefaultValidationEventHandler: [FATAL_ERROR]: Premature end of file.
Location:
DefaultValidationEventHandler: [ERROR]: Unexpected element {}:ejb-local-ref
Location:
back on the console I launched the UI from
To possibly oversimplify, I copied out some of the most relevant .xml we have,
ejb-jar.xml
jboss.xml
jbosscmp-jdbc.xml
jboss-web.xml
web.xml
and put them in a single directory...now the Migration tool runs, leaves most of the files unchanged, and for our ejb-jar.xml it fails, and says
Unknown error.
EjbJar is Null
Admittedly our ejb-jar.xml is handcrafted and maybe suspect, but still.
So I guess right now I'm not too optimistic about this tool.
Some of the problem is my understanding of what all goes in an EAR in terms of DD is weak. I'm trying to smarten up, but haven't found a good description of "these are the typical DD files for Sun Application Server", with examples or precise descriptions of the contents...and the migration tool doesn't get to the point where it's making some of the files i expected based on
http://java.sun.com/j2ee/tools/migration/doc/JBOSS3.0_S1AS7.html
(for example sun-cmp-mappings.xml doesn't appear anywhere in the AppServer\docs directory... )
Any pointers or advice appreciated...

There is an article, while it is for Application Server 7, it still could be useful:
http://developers.sun.com/prodtech/javatools/jsenterprise/reference/docs/jse7/jse7_jboss_plugin.html

Attachment in WLS 7 sp2 Web Service

Hi, I'm trying to send to a Web Service in WLS7 sp2 SOAP message with attachments. My problem: when I don't add any attachment to SOAP message all go OK, but when I add an attachment with the "href" attribute in an element of the message (I need do it because I use the MM7 protocol of 3GPP), WLS7 donÂ´t accept my message and tell me: "The ID referenced by ..... is unknow". The Content-ID of attachment is equal to value of the href attribute.
Please, I need help with this!! If anyone knows any URL or sample code that can help me, please, reply to this post.
Thanks and sorry, my english is not very well.

Currently there is no option to turn off security check.
I think you can use a servlet filter mapped to the URL
of your service, instead of a proxy servlet?
Regards,
-manoj
http://manojc.com
"Toni Nykanen" <[email protected]> wrote in message
news:3ef1577b$[email protected]..
>
Hi!
We need to implement authentication using our own methods, and theauthentication
information is provided to the web service implementation in a basicauthentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
in
wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
Is there any way to circumvent this, because we want to implementauthentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for ourown
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet,which
would
remove the basic authentication header, and put the authentication info incustom
headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
>
But still, I'd like to know if there is any way to tell bea's servlet toignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

Username token in SOAP message

Dear PI experts.
I am using SAP PI 7.1 and having a scenario where a message is sent from SAP (ECC 6.0) using Abap Proxy via PI to Java legacy system with Receiver SOAP Adapter.
I am supposed to send username token in the SOAP header. I have browsed quite an amount of SAP's Web service security material, but not yet been able to implement this behaviour. Mostly these documents are handling webservice scenarios between Abap systems using WS-RM.
Could you please advise me to right track.
Thank you, Jukka.

Hi,
you can use Principal Propagation to propagate your user from R/3 to PI to your target application.....you will have to ask your basis guys to enable Principal Propagation in your XI system by making your r/3 system and XI system as trusted systems to eachother.
Regards,
Rajeev Gupta

Best practices for apps integration with third party systems ?

Hi all
I would like to know if there is any document from oracle or from your own regarding best practices for apps integration with third party systems.
For example, in particular, let's say we need customization in a given module(ex:payables) need to provide data to a third party system, consider following:
outbound interface:
1)should third party system should be given with direct access to oracle database to access a particular payments data information table/view to look for data ?
2) should oracle create a file to third party system, so that it can read and do what it need to do?
inbound:
1) should third party should directly login and insert data into tables which holds response data?
2) again, should third party create file and oralce apps will pick up for further processing?
again, there could be lot of company specific scenarios like it has to be real time or not... etc...
How does companies make sure third party systems are not directly dipping into other systems (oracle apps/others), so that it will follow certain integration best practices.
how does enterprise architectute will play a role in this? can we apply SOA standards? should use request/reply using Tibco etc?
Many oracle apps implementations customizations are more or less directly interacting with third party systems by including code to login into respective third party systems and vice versa.
Let me your know if you have done differently and that would help oracle apps community.
thanks
rrb.

you want to send idoc to third party system (NONSAP).
what kind of system is it? can it handle http requests
or
can it handle webservice?
which version of R/3 you are using?
what is the mechanism the receiving system has, to receive data?
Regards
Raja

Integration with third party system....!

Hello All,
I want to integrate R/3 to Third Party system which can accept IDOCs. Can any body plz guide me in RFC destination part..? What type of connection should i use?
TCP/IP or HTTP???? and how to find the Gateway service for third party system?
Thanks in advance.
Regards,
Atul.

you want to send idoc to third party system (NONSAP).
what kind of system is it? can it handle http requests
or
can it handle webservice?
which version of R/3 you are using?
what is the mechanism the receiving system has, to receive data?
Regards
Raja

No Lock & Edit button in WLS 10 Console

I don't have the Lock & Edit button in the WLS 10 Console. I know that this could be turned on and off in previous versions of WebLogic in the config.xml file, but I didn't find this anywhere in the documentation anymore.
Can anybody tell me how to make the Lock & Edit buton visible again in WebLogic 10.3a?
Thanx
Peter

Here is my config.xml ( I guess I cannot just attach it):
<?xml version='1.0' encoding='UTF-8'?>
<domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/920/domain.xsd" xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml">
     <name>IOP5</name>
     <domain-version>10.3.0.0</domain-version>
     <security-configuration>
          <name>IOP5</name>
          <realm>
          
               <sec:auditor xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-auditorType">
                    <sec:name>CSRealmCSAuditor</sec:name>
                    <prov:audit-logger-name>@audit.WLSAuditChannel</prov:audit-logger-name>
                    <prov:use-wls-log-handler>false</prov:use-wls-log-handler>
                    <prov:providers-logs-enabled>false</prov:providers-logs-enabled>
               </sec:auditor>
               <sec:authentication-provider xsi:type="wls:saml-identity-asserter-v2Type">
                    <sec:name>SAMLIdentityAsserter</sec:name>
                    <wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
               </sec:authentication-provider>
               <sec:authentication-provider xsi:type="prov:cssaml-authenticatorType" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xmlns:dom="http://www.bea.com/ns/WebLogic/920/domain" xmlns:xsi1="xsi">
                    <sec:name>CS SAML Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
               </sec:authentication-provider>


               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-identity-asserterType">
                    <sec:name>CS Identity Asserter</sec:name>
                    <prov:credentials-validators>X.509=com.csg.cs.security.wls.authentication.pki.ext.CSPKICredentialValidator</prov:credentials-validators>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-principal-authenticatorType">
                    <sec:name>CS Principal Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                    <prov:credential-validator>com.csg.cs.security.wls.authentication.pki.ext.CSPrincipalCredentialValidator</prov:credential-validator>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:csb1-authenticatorType">
                    <sec:name>CS B1 Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                    
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authenticatorType">
                    <sec:name>CS Authentication Provider</sec:name>
                    <sec:control-flag>SUFFICIENT</sec:control-flag>
                    <prov:log-in-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:log-in-module-class-name>
                    <prov:assertion-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:assertion-module-class-name>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-internal-identity-asserterType">
                    <sec:name>CS Internal Identity Asserter</sec:name>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-data-layer-providerType">
                    <sec:name>CS Data Layer Security Provider</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                                   <prov:key-alias>SYSTEM</prov:key-alias>
                                   <prov:key-store-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-store-pass-phrase-encrypted>
                                   <prov:key-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-pass-phrase-encrypted>
               </sec:authentication-provider>
               <sec:role-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-role-mapperType">
                    <sec:name>CS Role Mapper</sec:name>
                    <sec:role-deployment-enabled>true</sec:role-deployment-enabled>
                    <prov:is-debug>false</prov:is-debug>
                    <prov:application-role-mapper-class-name></prov:application-role-mapper-class-name>
               </sec:role-mapper>
               <sec:authorizer xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authorizerType">
                    <sec:name>CS Authorization Provider</sec:name>
               </sec:authorizer>
               <sec:credential-mapper xsi:type="sam:saml2-credential-mapperType" xmlns:sam="http://www.bea.com/ns/weblogic/90/security/saml2">
                    <sec:name>SAML2CredentialMapper</sec:name>
                    <sam:issuer-uri>http://www.credit-suisse.com</sam:issuer-uri>
                    <sam:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</sam:name-qualifier>
                    <sam:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAML2NameMapperImpl</sam:name-mapper-class-name>
               </sec:credential-mapper>
               <sec:credential-mapper xsi:type="wls:saml-credential-mapper-v2Type" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers">
                    <sec:name>SAMLCredentialMapper</sec:name>
                    <wls:issuer-uri>http://www.credit-suisse.com</wls:issuer-uri>
                    <wls:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</wls:name-qualifier>
                    <wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
               </sec:credential-mapper>
               <sec:credential-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-credential-mapperType">
                    <sec:name>CSCredentialMapper</sec:name>
               </sec:credential-mapper>
               <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
               <sec:cert-path-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cert-path-providerType">
                    <sec:name>CS Certificate Path Provider</sec:name>
                    <prov:cert-path-validator-class-name>com.csg.cs.security.wls.authentication.cert.ext.CSPKICertPathValidator</prov:cert-path-validator-class-name>
               </sec:cert-path-provider>
               <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
               <sec:deploy-role-ignored>true</sec:deploy-role-ignored>
               <sec:deploy-policy-ignored>true</sec:deploy-policy-ignored>
               <sec:deploy-credential-mapping-ignored>false</sec:deploy-credential-mapping-ignored>
               <sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
               <sec:security-dd-model>Advanced</sec:security-dd-model>
               <sec:name>CSRealm</sec:name>
               <sec:delegate-m-bean-authorization>true</sec:delegate-m-bean-authorization>
          </realm>
          <default-realm>CSRealm</default-realm>
          <anonymous-admin-lookup-enabled>true</anonymous-admin-lookup-enabled>
          <credential-encrypted>{3DES}Zk0PFQd/y2JbBwcVCkoTVA==</credential-encrypted>
          <connection-filter>com.csg.cs.security.wls.net.ConnectionFilterImpl</connection-filter>
          <connection-logger-enabled>true</connection-logger-enabled>
     </security-configuration>
     <server>
          <name>IOPWLS5</name>
          <reverse-dns-allowed>true</reverse-dns-allowed>
          <ssl>
               <use-java>true</use-java>
               <enabled>true</enabled>
               
               <ciphersuite>TLS_RSA_WITH_RC4_128_SHA</ciphersuite>
               <ciphersuite>TLS_RSA_WITH_3DES_EDE_CBC_SHA</ciphersuite>
               <cert-authenticator></cert-authenticator>
               <hostname-verifier>com.csg.cs.security.wls.net.SSL.ext.CSPKIHostNameVerifier</hostname-verifier>
               <hostname-verification-ignored>false</hostname-verification-ignored>
               <export-key-lifespan>500</export-key-lifespan>
               <client-certificate-enforced>false</client-certificate-enforced>
               <listen-port>7002</listen-port>
               <two-way-ssl-enabled>true</two-way-ssl-enabled>
               <server-private-key-alias>tipd.csintra.net</server-private-key-alias>
               <server-private-key-pass-phrase-encrypted>{3DES}mQrgg0qTDHAhuU+2FACgZQ==</server-private-key-pass-phrase-encrypted>
               <ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
               <inbound-certificate-validation>BuiltinSSLValidationAndCertPathValidators</inbound-certificate-validation>
               <outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
          </ssl>
          <log>
               <rotate-log-on-startup>true</rotate-log-on-startup>
               <logger-severity>Notice</logger-severity>
               <stdout-severity>Notice</stdout-severity>
               <log-file-filter xsi:nil="true" />
               <stdout-filter xsi:nil="true" />
               <domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
               <domain-log-broadcast-filter xsi:nil="true" />
               <memory-buffer-filter xsi:nil="true" />
               <redirect-stdout-to-server-log-enabled>true</redirect-stdout-to-server-log-enabled>
               <redirect-stderr-to-server-log-enabled>true</redirect-stderr-to-server-log-enabled>
          </log>
          <machine xsi:nil="true"></machine>
          <listen-port>7001</listen-port>
          <listen-port-enabled>true</listen-port-enabled>
          <cluster xsi:nil="true"></cluster>
          <web-server>


               <send-server-header-enabled>false</send-server-header-enabled>
          </web-server>
          <iiop-enabled>false</iiop-enabled>
          <listen-address>127.0.0.1</listen-address>
          <staging-directory-name>./stage</staging-directory-name>
          <classpath-servlet-disabled>true</classpath-servlet-disabled>
          <key-stores>CustomIdentityAndCommandLineTrust</key-stores>
          <custom-identity-key-store-file-name>./keystores/identity.properties</custom-identity-key-store-file-name>
          <custom-identity-key-store-type>CS_PKI</custom-identity-key-store-type>
          <custom-identity-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-identity-key-store-pass-phrase-encrypted>
          <custom-trust-key-store-file-name>./keystores/trustedca.properties</custom-trust-key-store-file-name>
          <custom-trust-key-store-type>CS_PKI</custom-trust-key-store-type>
          <custom-trust-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-trust-key-store-pass-phrase-encrypted>
     </server>
     <embedded-ldap>
          <name>IOP5</name>
          <credential-encrypted>{3DES}nQpvTCkYlf4h4+8bAEI7JH8pg2Zo4uqNrVEu9bfYSr8=</credential-encrypted>
     </embedded-ldap>
     <administration-port-enabled>true</administration-port-enabled>
     <administration-port>9999</administration-port>
     <configuration-version>10.3.0.0</configuration-version>
     <app-deployment>
          <name>IOPA_root</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/root.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPD_prsysmgmt</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPD/prsysmgmt.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPC_prhelp</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPC/prhelp.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPA_prpc_j2ee14</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/prpc_j2ee14.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPB_prdbutil</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPB/prdbutil.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>



     <library>
          <name>CSWSPolicySAML11#[email protected]</name>
          <target>IOPWLS5</target>
          <source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\WSS11SAML1WSPolicy.jar</source-path>
          <deployment-order>1</deployment-order>
          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </library>
     <library>
          <name>CSWSPolicySAML20#[email protected]</name>
          <target>IOPWLS5</target>
          <source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\SAML2WSPolicy.jar</source-path>
          <deployment-order>1</deployment-order>
          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </library>






     
     <jms-server>
          <name>PRJMS_Server</name>
          <target>IOPWLS5</target>
     </jms-server>
     <jmx>
          <management-ejb-enabled>false</management-ejb-enabled>
     </jmx>
     <shutdown-class>
          <name>CSServerLifeCycleShutdown</name>
          <target>IOPWLS5</target>
          <class-name>com.csg.cs.security.wls.CSServerLifeCycleShutdown</class-name>
     </shutdown-class>
     <startup-class>
          <name>CSServerLifeCycle</name>
          <target>IOPWLS5</target>
          <class-name>com.csg.cs.security.wls.CSServerLifeCycle</class-name>
          <failure-is-fatal>true</failure-is-fatal>
          <load-before-app-deployments>true</load-before-app-deployments>
          <load-before-app-activation>false</load-before-app-activation>
     </startup-class>

     <jms-system-resource>
          <name>PRJMS_Module</name>
          <target>IOPWLS5</target>
          <sub-deployment>
               <name>PRJMS_Subdeployment</name>
               <target>PRJMS_Server</target>
          </sub-deployment>
          <sub-deployment>
               <name>PRJMS_Subdeployment_Topic</name>
               <target>PRJMS_Server</target>
          </sub-deployment>
          <descriptor-file-name>jms/prjms_module-jms.xml</descriptor-file-name>
     </jms-system-resource>
     <admin-server-name>IOPWLS5</admin-server-name>
     <jdbc-system-resource>
          <name>pega-rules</name>
          <target>IOPWLS5</target>
          <descriptor-file-name>jdbc/pega-rules-jdbc.xml</descriptor-file-name>
     </jdbc-system-resource>

     

     <webservice-security>
          <name>default_wss</name>
          <webservice-token-handler>
               <name>CSTokenHandler</name>
               <class-name>com.csg.cs.security.wls.authentication.wsee.TokenHandler</class-name>
               <token-type>ut</token-type>
               <handling-order>0</handling-order>
          </webservice-token-handler>
     </webservice-security>
</domain>
Regards
Peter

Soap message context doesnt contain operation name

I deployed a simple web service to convert Fahrenheit to Celsius and vice versa and generated the client artifacts with wsimport. I have two handlers set up, one for the client that I created and one for the server. When I invoke a method the client handler fires but does not contain the key for wsdl_operation. The server side does however. Below is the code for the web service, client, and handler
WebService:
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService(name="Converter")
public class Converter
     @WebMethod(operationName="fahrenheitToCelsius")
     public double fahrenheitToCelsius(double f)
          return (f-32)*(5/9.0);
     @WebMethod(operationName="celsiusToFahrenheit")
     public double celsiusToFahrenheit(double c)
          return (9/5.0)*c+32;
}Client:
public class Client {
     public static void main(String args[])
          ConverterService cs = new ConverterService();
          Converter converter = cs.getConverterPort();
          //create service
          List<Handler> handlerChain =
             ((BindingProvider)converter).getBinding().getHandlerChain();
         ClientHandler sh = new ClientHandler();
         List<Handler> new_handlerChain = new ArrayList<Handler>();
         new_handlerChain.add(sh);
            ((BindingProvider)converter).getBinding().setHandlerChain(new_handlerChain);
            System.out.println(converter.celsiusToFahrenheit(32.0));
}Handler.handleMessage():
public boolean handleMessage(SOAPMessageContext arg0) {
          for (String a:arg0.keySet())
               System.out.println(a + " : " + arg0.get(a));
          return true;
     }Any idea why the client handler's message context does not contain an operation name? I have been passing it to the handler as i attach it to different services but its not really viable to have a different handler for each method in a service.

Not sure but you can give it a try.
you can set the log configuration level to TRACE 32 on your managed server where you have deployed your webserivce e.g soa_server1
Follow the steps to configure.
1. Right click your managed server in enterprise manager and choose Log > Log Configuration
2. Search for Webservices and View as Runtime Loggers Press the Play button
3. Set the level from NOTIFICATIONS (INFO) to TRACE32.
4. Stop your servers rename the log files and restart your managed servers to create new fresh logs.
Hope it helps,
Zeeshan

Handle Webservice Respons

Similar Messages

Maybe you are looking for