SOAP support in WLS6.0

I hear that SOAP support is "built in" to 6.0, but is not yet documented and
won't be documented until February. Does anyone know if this support is the
Apache implementation or something else?

FYI - quoted from the WLS 6.0 FAQ....
Does WebLogic Server 6.0 support SOAP?
WebLogic Server 6.0 does not support SOAP; however, BEA provides an
alpha-quality SOAP implementation at
http://developer.bea.com:80/techtracks/xml/index.jsp.
Alex Thomas <[email protected]> wrote in message
news:3a42444e$[email protected]..
>
Can't see anything in WL6 yet. I heard that a separate, probablyunsupported, SOAP
component would be made available. This is a non-trivial task if oneincludes UDDI,
WSDL etc etc.
cheers
alex
"Robert Cahn" <[email protected]> wrote:
I hear that SOAP support is "built in" to 6.0, but is not yet documented
and
won't be documented until February. Does anyone know if this support is
the
Apache implementation or something else?

Similar Messages

Is CSIv2 supported in WLS6.1SP2?

Is CSIv2 supported in WLS6.1SP2?

Thanks Andy.
I have some other (different) questions - but I think I should email them. I'll
send via Peter and Jim.
Cheers,
Nick
Andy Piper <[email protected]> wrote:
"Nick Minutello" <[email protected]>
writes:
Is CSIv2 supported in WLS6.1SP2?No. 7.0 only.
andy

SOAP Support

Hi,
its not clear for me... does PI only support document/literal soap messages for receiver (PI->3rd party) interfaces ?
It seems it handles WSDL in RPC (it can import them ! as stated in sap help) but I think it only handles document/literal messages. So it imports the WSDL, can call the operation but can't handle the results without custom programming by the client...
Here is what is in the help :
http://help.sap.com/saphelp_nw70/helpdata/EN/43/ce993b45cb0a85e10000000a1553f6/frameset.htm
In particular , this sentence has struck me :
The Integration Builder expects external messages in document-style format.
Does anyone have a clear , definite answer to this !
Thanks.
Edited by: Thierry Dagnino on Feb 24, 2009 11:58 AM
Edited by: Thierry Dagnino on Feb 24, 2009 11:59 AM

Thanks again for your reply,
this note also is not complete in its explanations :
Basicaly it says :
You can import RPC style wsdl but you must make sure your proxy sends out the right format soap message...
PI really works with document style wsdl internaly... but this does not affect the sending of soap messages.
For example : we we're able with the axis soap adapter to send a rpc style message out to the third party and we received the full rpc style response.
The problem seems to be ... the rest of PI : mapping etc... does not work with that format. Maybe if you are really really lucky.
Could SAP just write somewhere that PI just works with document/literal messages and if you use RPC style messages, there are high chances your stuff wont work.
Thanks.

JAX-RPC, JAXM, JAXR supported in WLS6.1?

Does wls6.1 support JAX API's? If not, when will they be supported? Thanks much.
Siming

Hi Siming,
The JAX Pack (i.e. JAX-RPC, JAXM, JAXB, JAXR, etc.) are still merely JSRs, with
no "real" consensus on whether they will ever be otherwise. This being the case,
it is unlikely that you will see support for them in WebLogic Server, in the near
future (3 to 6 months). You can always run the Sun RIs (Reference Implementations)
under WebLogic Server (I have done this with both JAXB and JAXM), if you would
like to experiment with these technologies.
Regards,
Mike Wooten
"Siming Mu" <[email protected]> wrote:
>
Does wls6.1 support JAX API's? If not, when will they be supported?
Thanks much.
Siming

JTA to TMS Support for WLS6

Will WLS 6 JTA be able to coordinate with the Tuxedo TMS in WLS6
          GA? CB


Hi Craig.
          Sorry, no, transactional integration between WLS and Tuxedo is planned for a future
          release after WLS 6.0.
          -- Ed Felt, BEA Systems, Inc.

Serialising data objects using XML

Does the support for XML in wl6.0 mean that java data objects can be serialized using xml entirely within weblogic (currently we use a 3rd party product, and are hoping to remove this if possible)?

What about SOAP?
Isn't that what SOAP does - marshals and unmarshals between objects and XML
You can use SOAP from Java, or C++ or whatever.
Contrary to a commonly held perception, SOAP doesn't require remote
transmission of the serialized XML datastream.
Where is the SOAP support for WLS6 ? I heard it was separately
downloadable?
"Alex Thomas" <[email protected]> wrote in message
news:3a532681$[email protected]..
>
With some limitations, yes, if you are starting from a DTD - see the docsfor the WebLogic DTD2Parser tool which generates a high-speed custom parser
for a given DTD.
>
This tool anticipates the JAXB standard (aka Data Binding, formerlyProject Adelard) - see http://java.sun.com/xml/ - which is due fairly
shortly AFAIK.
>
If you were wanting to start with arbitrary Java classes and serializethem to XML you'd have to wait longer unfortunately, though there are some
implementations around, e.g. http://www.wutka.com/jox.html. This would then
correspond to marshalling if the objects were parameters to an RPC of some
kind.
>
cheers
(another) alex
"alex" <[email protected]> wrote:
What I should have said is: can wl6 automatically populate java objects
from xml and vice versa? I believe this is called 'data marshalling and
unmarshalling', but I cannot find references to this in the doco.
>>
>

Does WLS6.1-sp2 support J2EE-1.3 spec by default?

hi All,
          Just installed WLS6.1-sp2 30-day evaluation. I tested on it with a simple
          Filter servlet, but it didn't work at all.
          I tried to find some docs related to J2EE spec compliance and they say the
          default is J2EE-1.3. Can anyone tell me the default J2EE spec supported by
          WLS6.1-sp2? And how can I check the currently-used J2EE spec in my running
          WLS? How can I switch between J2EE-1.2 and 1.3?
          Thanks
          Liu Yan


I think it is enabled by default. Note that javax.servlet.Filter which is
          shipped with WebLogic is different from one in final Servlet 2.3. Also you
          can search this newsgroup - there are lots of problems with Filters in 6.1.
          If you think that the problem is with your program, try to deploy it on Resin
          or Tomcat to see if it is actually the case.
          Liu Yan <[email protected]> wrote:
          > Thanks for your reply. I found that WLS6.1 DOES support so-called non-final
          > version of J2EE-1.3 spec. And my downloaded version is J2EE-1.3
          > feature-enabled by default. Seems the problem of my filter program.
          > But do you know how to configure J2EE compatibility in admin console? I mean
          > can I switch back and forth between J2EE-1.2 and 1.3?
          > Thanks
          > Liu Yan
          > "Dimitri Rakitine" <[email protected]> Ð´ÈëÏûÏ¢ÐÂÎÅ
          > :[email protected]...
          >> 6.1 does not support final Servlet 2.3 spec. You can see release notes
          >> for details: http://e-docs.bea.com/wls/docs61/notes/index.html
          >>
          >> Liu Yan <[email protected]> wrote:
          >> > hi All,
          >>
          >> > Just installed WLS6.1-sp2 30-day evaluation. I tested on it with a
          > simple
          >> > Filter servlet, but it didn't work at all.
          >>
          >> > I tried to find some docs related to J2EE spec compliance and they say
          > the
          >> > default is J2EE-1.3. Can anyone tell me the default J2EE spec supported
          > by
          >> > WLS6.1-sp2? And how can I check the currently-used J2EE spec in my
          > running
          >> > WLS? How can I switch between J2EE-1.2 and 1.3?
          >>
          >> > Thanks
          >>
          >> > Liu Yan
          >>
          >>
          >>
          >>
          >> --
          >> Dimitri
          Dimitri

B2B Support SOAP via SOAP Service and/or HTTP Posting?

I cannot find any documentation that points to the B2B product and it's support for SOAP. Can someone point me to this documentation if any?
If someone can answer the quick questions in the subject that would be great as well.

ebXML standard is typically supported by all available B2B Integration products. Oracle B2B is interoperability certified by Drummond group for ebXML. ebXML offers much richer security framework compared to basic SOAP and it will be a easy change for your partners - they need to configure their B2B to talk ebXML.
We are also planning on adding generic SOAP support in our next release. Please send me an e-mail and I can keep you posted.
Also if you need a demo of the product, we can arrange one as well.
Thanks - Sundar

Target URL in the Receiver SOAP channel in PI 7.11

Hi
I have designed integrated Configuration in PI 7.11 and i have SOAP sender and SOAP receiver. SOAP sender is fine but for SOAP receiver i have an issue with the target URL that i selected.
Initially the receiver was ABAP proxy with HTTP connection as we dont have ABAP related adapters in AAE i used SOAP. But i have used the same URL that is the Target host configured in the HTTP ABAP connection to the target system. Then i am getting the following error at the receiver comm channel
Message processing failed. Cause: com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme
I am sure i am doing a mistake, the URL i am using is wrong as it is not meant for SOAP calls. Please suggest me what needs to be done here.

..I am sure i am doing a mistake, the URL i am using is wrong as it is not meant for SOAP calls. Please suggest me what needs >>to be done here
You are using Integrated configuration with PI 7.1 EHP1 version. That means SOAP supports as PI native protocol (XI) for PROXY scenario. So, you have to create soap receiver adapter and choose message protocol as XI.
Integrated configuration occurs in java stack engine and XI adapter(proxy) not exists there. Only if you do classical processing (IE) then you can use XI adapter at the receiver side. Thats the reason you dont find XI adapter in the integrated configuration.
Hope I answered your question

How to install Soap on the (Apache) Oracle HTTP Server

Hi,
Does anyone know how to install SOAP on the Oracle HTTP Server? I downloaded a soap version (it seems that the standard version comes without SOAP) from the xml.apache.org site and followed the installation instructions as far as I could (only Tomcat is described). However, no 'soaping'!!! Maybe I'm overlooking something because I cannot imagine that it should be difficult.
Thanks in advance!
Hans

Hans, the SOAP implementation is part of OC4J. You get it out of the box. Check out how to use the out-of-the-box implementation in the tutorials on Web services with Oracle9i JDeveloper at:
http://otn.oracle.com/tech/webservices/htdocs/series/content.html
These tutorials/samples use the implementation of SOAP/WSDL that Oracle calls J2EE Web Services and this is the long term direction of Oracle's Web services implementation. This implementation is what Oracle will be evolving to Sun's Java Web Services Developer Pack as it finalizes into J2EE 1.4.
If you want to use Oracle/Apache SOAP, this too is included in OC4J but its support is being deprecated in future releases of Oracle9iAS in favour of the J2EE Web Services implementation. To find it, check out the OC4J/soap/webapps/ directory for the soap.ear file (it is in a slightly different spot if you are using the full Oracle9iAS R2 but still within the soap directory structure. Simply add <application name="soap" path="../../../soap/webapps/soap.ear" auto-start="true"/> to your OC4J server.xml and <web-app application="soap" name="soap" root="/soap" /> to your OC4J http-web-site.xml, re-start and away you go.
Finally, just to be sure, SOAP support in Oracle9iAS did not appear until 1.0.2.2.x and higher. If using 1.0.2.1 or less, you are correct, there is no SOAP support.
Mike.
Most folks that try out the J2EE Web Services find it is pretty easy to use so

SOAP and J2EE security

We have deployed several SOAP services (Apache SOAP) on a WLS6.1
server. Since there are more and more services are being deployed
people are getting worried about security. I was wondering what the
best solution was to to authentication and authorization on EJB and
method level for SOAP clients ? I was thinking about the following
solution: use the standard J2EE security by defining security
constrainst in the ejb-jar.xml file. Therefor every client needs to
provide credentials to use the EJB's (this should work for both
RMI/IIOP and SOAP clients).
What are your ideas and opinions about this solution ?
If you post a reply please CC to [email protected]

Hi,
Let me know if you find answer of your question.
thanks

Web Service Deployment error on WLS6.1

Hi All,
I'm trying to deploy a dummy SOAP service on WLS6.1, build on a plain Java
class.
All the procedure works well on tomcat 3.2, and my SOAP client invokes all
the methods and gets expected response successfully.
When I even try to deploy it on WLS6.1 with the command line :
java org.apache.soap.server.ServiceManagerClient
http://server:port/soap/servlet/rpcrouter deploy myDeploymentDescriptor.xml
The following SOAP envelope is sent to WLS6.1 (tomcat finds it OK, as I
said)
POST /soap/servlet/rpcrouter HTTP/1.0
Host: 127.0.0.1
Content-Type: text/xml; charset=utf-8
Content-Length: 1860
SOAPAction: ""
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:deploy xmlns:ns1="urn:xml-soap-service-management-service"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<descriptor xmlns:ns2="http://xml.apache.org/xml-soap"
xsi:type="ns2:DeploymentDescriptor">
<faultListener xmlns:ns3="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns3:Array" ns3:arrayType="xsd:string[1]">
<item xsi:type="xsd:string">org.apache.soap.server.DOMFaultListener</item>
</faultListener>
<providerClass
xsi:type="xsd:string">aacom.ksl.catalog.CDCatalog</providerClass>
<serviceType xsi:type="xsd:int">0</serviceType>
<serviceClass xsi:type="xsd:string" xsi:null="true"/>
<methods xmlns:ns4="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns4:Array" ns4:arrayType="xsd:string[4]">
<item xsi:type="xsd:string">addCD</item>
<item xsi:type="xsd:string">getArtist</item>
<item xsi:type="xsd:string">list</item>
<item xsi:type="xsd:string">xmlList</item>
</methods>
<providerType xsi:type="xsd:byte">0</providerType>
<scriptLanguage xsi:type="xsd:string" xsi:null="true"/>
<mappings xmlns:ns5="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns5:Array" ns5:arrayType="ns2:TypeMapping[]" xsi:null="true"/>
<checkMustUnderstands xsi:type="xsd:boolean">false</checkMustUnderstands>
<defaultSMRClass xsi:type="xsd:string" xsi:null="true"/>
<ID xsi:type="xsd:string">urn:cd-catalog</ID>
<props xsi:type="ns2:Map" xsi:null="true"/>
<isStatic xsi:type="xsd:boolean">false</isStatic>
<scriptFilenameOrString xsi:type="xsd:string" xsi:null="true"/>
<scope xsi:type="xsd:int">2</scope>
</descriptor>
</ns1:deploy>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I get this very disappointing answer :
Ouch, the call failed:
Fault Code = SOAP-ENV:Client
Fault String = Unable to resolve namespace URI for 'ns2'.
Did somebody encountered this problem and know the fix or meaning of all
that ?
Regards
VLADAN.

Hi All,
I'm trying to deploy a dummy SOAP service on WLS6.1, build on a plain Java
class.
All the procedure works well on tomcat 3.2, and my SOAP client invokes all
the methods and gets expected response successfully.
When I even try to deploy it on WLS6.1 with the command line :
java org.apache.soap.server.ServiceManagerClient
http://server:port/soap/servlet/rpcrouter deploy myDeploymentDescriptor.xml
The following SOAP envelope is sent to WLS6.1 (tomcat finds it OK, as I
said)
POST /soap/servlet/rpcrouter HTTP/1.0
Host: 127.0.0.1
Content-Type: text/xml; charset=utf-8
Content-Length: 1860
SOAPAction: ""
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:deploy xmlns:ns1="urn:xml-soap-service-management-service"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<descriptor xmlns:ns2="http://xml.apache.org/xml-soap"
xsi:type="ns2:DeploymentDescriptor">
<faultListener xmlns:ns3="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns3:Array" ns3:arrayType="xsd:string[1]">
<item xsi:type="xsd:string">org.apache.soap.server.DOMFaultListener</item>
</faultListener>
<providerClass
xsi:type="xsd:string">aacom.ksl.catalog.CDCatalog</providerClass>
<serviceType xsi:type="xsd:int">0</serviceType>
<serviceClass xsi:type="xsd:string" xsi:null="true"/>
<methods xmlns:ns4="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns4:Array" ns4:arrayType="xsd:string[4]">
<item xsi:type="xsd:string">addCD</item>
<item xsi:type="xsd:string">getArtist</item>
<item xsi:type="xsd:string">list</item>
<item xsi:type="xsd:string">xmlList</item>
</methods>
<providerType xsi:type="xsd:byte">0</providerType>
<scriptLanguage xsi:type="xsd:string" xsi:null="true"/>
<mappings xmlns:ns5="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns5:Array" ns5:arrayType="ns2:TypeMapping[]" xsi:null="true"/>
<checkMustUnderstands xsi:type="xsd:boolean">false</checkMustUnderstands>
<defaultSMRClass xsi:type="xsd:string" xsi:null="true"/>
<ID xsi:type="xsd:string">urn:cd-catalog</ID>
<props xsi:type="ns2:Map" xsi:null="true"/>
<isStatic xsi:type="xsd:boolean">false</isStatic>
<scriptFilenameOrString xsi:type="xsd:string" xsi:null="true"/>
<scope xsi:type="xsd:int">2</scope>
</descriptor>
</ns1:deploy>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I get this very disappointing answer :
Ouch, the call failed:
Fault Code = SOAP-ENV:Client
Fault String = Unable to resolve namespace URI for 'ns2'.
Did somebody encountered this problem and know the fix or meaning of all
that ?
Regards
VLADAN.

Flex and SOAP 1.2 ?

Hello,
I know that Flex Builder 3 is not compatible with SOAP 1.2 (only 1.1).
Can someone from Adobe please respond if you plan to make at least Flash Builder 4 compatible with SOAP 1.2 ?
For the record, SOAP 1.2 was officialy approuved in 2003 by W3C (W3C recommendation on June 24, 2003).
Thank you in advance for your response,
and thank you for all great software
Adnan

Hi,
Unfortunately we're not going to be updating the SOAP support in Flex 4. We continue to look for folks in the community who might be interested in assisting here.
Matt

Integration Web Service Support?

Does the new Integration 7.0 BPM have web service/SOAP support?
In particular, I would like to start my workflow from a web service call, or be
able to call web services directly from tasks in my workflow. Can this be done?
Please advise,
Dave

No it does not. You have two choices. There is a alpha plug-in available to call
web services from a node task. It is for Integration 2.0. I have not been able
to run it against 7.0. The other option is to utilize workshop. There is a sample
on dev2dev. Search for integration interoperability.
"David Mrozek" <[email protected]> wrote:
>
Does the new Integration 7.0 BPM have web service/SOAP support?
In particular, I would like to start my workflow from a web service call,
or be
able to call web services directly from tasks in my workflow. Can this
be done?
Please advise,
Dave

Does iPlanet proxy3.6 support dayofweek and timeofday in ACLs

I tried using dayofweek and timeof day in ACLs so as to allow some users access to Internet during particular time of a day. But when I start the proxy server I get an error stating syntax is not proper. Can anyone tell me if these can be used in ACLs for proxy server. I tried adding the ACLs to generated*.acl. If these can be used can anyone let me know the proper syntax and also if I have to create a separate acl and refer to it in magnus.conf?
OS Solaris7
Proxy: iPlanet Web Proxy Server 3.6

Hi,
NES3.6 is supported under WLS6.0. Could you please put the part of obj.conf
file to proxy request here?
Thanks
Yu Tian
"Benjamin Hyatt" <[email protected]> wrote in message
news:[email protected]..
>
Having a problem getting libproxy to function properly on nes 3.6
Added the proper entries for the plugin in obj.conf; reloaded.
Nes instance starts up fine. If I attempt to access the url (i've definedby
ppath) the app server never get's hit. It's as if the plugin is beingcompletely
ignored.
I've set Debug="ON" hoping to see wlproxy.log in /tmp.... nothing.
I've done this very easily before with wl 5.1.0 and iplanet.
Does the 6.0 sp2 proxy plugin support nes 3.6?
Platform
Solaris 2.6
Any info is greatly appreciated.
Thanks,
/Ben

SOAP support in WLS6.0

Similar Messages

Maybe you are looking for