Monitoring/Viewing Web Service Messages in GlassFish

Hello,
I try to monitor the messages a Web Service produces in the admin GUI in GlassFish (v2 ur2): MyWebService -> Monitor -> Messages.
However, no messages are listed in spite of a successful activation of the Web Service.
The monitoring level in the configuration is set to 'HIGH'.
Any ideas ?
Thanks for your help.
Regards

Hi
it's me again.
OK, I made a significant progress, I used Perl's SOAP::Lite which apparently does not understand the document/literal wsdl style.
So, I'm using a Perl package which does support document/literal and now I get error messages.
The problem now is that the package is looking for xsd prefix in the wsdl+xsd files, and JAX-WS wsgen tool placed the prefix xs in these files.
I tried to manually fix this, but when deploying the war file to glassfish I get "new" wsdl+xsd file with the xs prefix again.
Can I somehow configure JAX-WS (or glassfish) to put a different prefix?
It's so frustrating to spend so much time on such problems.
Thanks
Sigal

Similar Messages

Message Monitoring and Web services Sequences .. SOAMANAGER

When can I use Mesage Monitoring and Sequence Monitoring .
We are making a proof a concept and we are the following.
1. A program which executes a proxy and with this proxy we are consuming a web services.
2. The proxy and web services were implemented in the same Abap Machine .
3. We execute the test and everything works very well and we consume the webservice and the program displays the expected result.
Now want to know How can we use the Message Monitoring and the Sequence Monitoring . Is this posible ? Do we have to make any previous configuration?
We don´t have any XI installation and for that we wonder if we can monitorize the webservices sequences ?
Any idea about if we can realize such king of actions ..
Many Thanks

Hi
I assumes u have dual stack.
You can do the sequence monitoring with or without PI. But without PI you would achieve that thing on the local machine.
You have to do those things at Java End using SAP NWA.
Please see this link
http://help.sap.com/saphelp_nwce10/helpdata/en/46/b00c2a99930764e10000000a1553f6/content.htm
http://help.sap.com/saphelp_nwce10/helpdata/en/46/9cb2b57ded371ae10000000a11466f/content.htm

Messages Monitoring and Web Services Sequences .... SOAMANAGER

When can I use Mesage Monitoring and Sequence Monitoring .
We are making a proof a concept and we are the following.
1. A program which executes a proxy and with this proxy we are consuming a web services.
2. The proxy and web services were implemented in the same Abap Machine .
3. We execute the test and everything works very well and we consume the webservice and the program displays the expected result.
Now want to know How can we use the Message Monitoring and the Sequence Monitoring . Is this posible ? Do we have to make any previous configuration?
We don´t have any XI installation and for that we wonder if we can monitorize the webservices sequences ?
Any idea about if we can realize such king of actions ..
Many Thanks

hi,
short answer: you can't. to my knowledge there is no such thing as message/sequence monitoring outside of PI/XI.
the only thing you can do is to enable debugging and access some debugging info from ST22. other than that you do not have access to the original (XML) message, the HTTP headers or the ST(simple transformation) info or anything else.
regards,
anton

Start an operation in web service with starting glassfish

Hi all,
I have a web service.it works with client style JAX-WS and glassfish v2 server. how can i define an operation in my web service that with starting of glass fish v2, this operation starts too?

fahimeh wrote:
how can i define an operation in my web service that with starting of glass fish v2, this operation starts too?I am not sure that you can configure glass fish v2 server like this or not. But When ever glass fish v2 or any server starts, all successfully deployed web application, resources etc. gets initialized. In respect to this you can surely configure your web application such a way that whenever it get stated you want to perform any operation.
So, this will end up with your requirement isn't It?
Look at this thread: [how to start a thread in a web service when the web service is starting|http://forums.sun.com/thread.jspa?messageID=10915016#10915016]

BW 3.5 Query view web service

I am trying to activate the BW 3.5 Web Service for Accessing Query Data as per the link given below:
http://help.sap.com/saphelp_nw04/helpdata/en/d8/3bfc3f8fc2c542e10000000a1550b0/content.htm
I was able to release the service when I try to chk and save an error message is displayed 'No ICF service found (URL_NO_HANDLER)'. I went to SICF and checked the URL tree /sap/bw/xml/soap/queryview, and no service was created for queryview. Should I manually create the queryview service, is so which handler should be used for this service. Any suggestions??
Thanks.

Hi, Thanks for your response back.. I'm trying to "Consume" the queryview web service via non sap system. I'd like to access the query results via a web link and have XML Query results returned.
http://<BWserver>.domain.com:<port>/sap/bw/xml/soap/queryview?sap-client=142&wsdl=1.1
after adding
&infoprovider=<infoprovider>&query=<queryid> to the end of the template you provided I get some xml returned, but it doesn't contain any query results. Any idea what I have to do to get the xml results?
Here's the summarized XML
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:n0="urn:sap-com:document:sap:rfc:functions" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <wsdl:types>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions" elementFormDefault="unqualified" attributeFormDefault="qualified">
+ <xsd:simpleType name="char1">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char132">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="132" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char2">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char22">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="22" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char250">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="250" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char30">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="30" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char40">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char60">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="60" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char70">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="70" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="char8">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="8" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="cuky5">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="date">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:pattern value="\d\d\d\d-\d\d-\d\d" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="numeric1">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="numeric2">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="numeric3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="numeric6">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="6" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:simpleType name="unit3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" elementFormDefault="unqualified" attributeFormDefault="qualified" xmlns:n0="urn:sap-com:document:sap:rfc:functions">
<xsd:import namespace="urn:sap-com:document:sap:rfc:functions" />
+ <xsd:simpleType name="RfcException.Message.Number">
+ <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
+ <xsd:complexType name="W3query">
- <xsd:sequence>
<xsd:element name="Name" type="n0:char30" />
<xsd:element name="Value" type="n0:char250" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsSxAxisData">
- <xsd:sequence>
<xsd:element name="Axis" type="n0:numeric3" />
<xsd:element name="Set" type="tns:RrwsTxSet" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsSxTuple">
- <xsd:sequence>
<xsd:element name="TupleOrdinal" type="n0:numeric6" />
<xsd:element name="Chanm" type="n0:char30" />
<xsd:element name="Caption" type="n0:char60" />
<xsd:element name="Chavl" type="n0:char60" />
<xsd:element name="ChavlExt" type="n0:char70" />
<xsd:element name="Niobjnm" type="n0:char30" />
<xsd:element name="Tlevel" type="n0:numeric2" />
<xsd:element name="Drillstate" type="n0:char1" />
<xsd:element name="Opt" type="n0:char2" />
<xsd:element name="Sign" type="n0:char1" />
<xsd:element name="Attributes" type="tns:RrwsTAttributes" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsSAttributes">
- <xsd:sequence>
<xsd:element name="Attrinm" type="n0:char30" />
<xsd:element name="Caption" type="n0:char60" />
<xsd:element name="Attrivl" type="n0:char60" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsSxAxisInfo">
- <xsd:sequence>
<xsd:element name="Axis" type="n0:numeric3" />
<xsd:element name="Nchars" type="xsd:int" />
<xsd:element name="Ncoords" type="xsd:int" />
<xsd:element name="Chars" type="tns:RrwsThxAxisChars" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsSxAxisChars">
- <xsd:sequence>
<xsd:element name="Chanm" type="n0:char30" />
<xsd:element name="Hienm" type="n0:char30" />
<xsd:element name="Version" type="n0:char3" />
<xsd:element name="Dateto" type="n0:date" />
<xsd:element name="Caption" type="n0:char60" />
<xsd:element name="Chaprsnt" type="n0:char1" />
<xsd:element name="Chatyp" type="n0:numeric1" />
<xsd:element name="Attrinm" type="tns:RrwsTAttrinm" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsSAttrinm">
- <xsd:sequence>
<xsd:element name="Attrinm" type="n0:char30" />
<xsd:element name="Caption" type="n0:char60" />
<xsd:element name="Chaprsnt" type="n0:char1" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsSCell">
- <xsd:sequence>
<xsd:element name="CellOrdinal" type="n0:numeric6" />
<xsd:element name="Value" type="n0:char22" />
<xsd:element name="FormattedValue" type="n0:char40" />
<xsd:element name="ValueType" type="n0:char1" />
<xsd:element name="Currency" type="n0:cuky5" />
<xsd:element name="Unit" type="n0:unit3" />
<xsd:element name="Mwkz" type="n0:char1" />
<xsd:element name="NumScale" type="n0:char1" />
<xsd:element name="NumPrec" type="n0:char1" />
<xsd:element name="CellStatus" type="n0:char1" />
<xsd:element name="BackColor" type="n0:char8" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsSTextSymbols">
- <xsd:sequence>
<xsd:element name="SymType" type="n0:char1" />
<xsd:element name="SymTimedep" type="n0:char1" />
<xsd:element name="SymName" type="n0:char40" />
<xsd:element name="SymFs" type="n0:numeric2" />
<xsd:element name="SymBeginGroup" type="n0:char1" />
<xsd:element name="SymCaption" type="n0:char60" />
<xsd:element name="SymValueType" type="n0:char2" />
<xsd:element name="SymValue" type="n0:char132" />
<xsd:element name="SymOutputlen" type="n0:numeric6" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RfcException.Message">
- <xsd:sequence>
<xsd:element name="ID" type="xsd:string" />
<xsd:element name="Number" type="tns:RfcException.Message.Number" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="GetQueryViewData.RfcException">
- <xsd:sequence>
<xsd:element name="Name" type="tns:GetQueryViewData.RfcExceptions" />
<xsd:element name="Text" minOccurs="0" type="xsd:string" />
<xsd:element name="Message" minOccurs="0" type="tns:RfcException.Message" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="Rrxw3tquery">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:W3query" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsThxAxisData">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:RrwsSxAxisData" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsTxSet">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:RrwsSxTuple" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsTAttributes">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:RrwsSAttributes" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsThxAxisInfo">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:RrwsSxAxisInfo" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsThxAxisChars">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:RrwsSxAxisChars" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsTAttrinm">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:RrwsSAttrinm" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsTCell">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:RrwsSCell" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:complexType name="RrwsTTextSymbols">
- <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:RrwsSTextSymbols" />
</xsd:sequence>
</xsd:complexType>
+ <xsd:simpleType name="GetQueryViewData.RfcExceptions">
- <xsd:restriction base="xsd:string">
<xsd:enumeration value="Abort" />
<xsd:enumeration value="InvalidInput" />
<xsd:enumeration value="InvalidVariableValues" />
<xsd:enumeration value="InvalidView" />
<xsd:enumeration value="NoApplicableData" />
<xsd:enumeration value="NoAuthority" />
</xsd:restriction>
</xsd:simpleType>
<xsd:element name="GetQueryViewData.Exception" type="tns:GetQueryViewData.RfcException" />
+ <xsd:element name="GetQueryViewData">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="Infoprovider" minOccurs="0" type="n0:char30" />
<xsd:element name="Parameter" minOccurs="0" type="tns:Rrxw3tquery" />
<xsd:element name="Query" minOccurs="0" type="n0:char30" />
<xsd:element name="ViewId" minOccurs="0" type="n0:char30" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
+ <xsd:element name="GetQueryViewDataResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="AxisData" type="tns:RrwsThxAxisData" />
<xsd:element name="AxisInfo" type="tns:RrwsThxAxisInfo" />
<xsd:element name="CellData" type="tns:RrwsTCell" />
<xsd:element name="TextSymbols" type="tns:RrwsTTextSymbols" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
+ <wsdl:message name="GetQueryViewData">
<wsdl:part name="parameters" element="tns:GetQueryViewData" />
</wsdl:message>
+ <wsdl:message name="GetQueryViewDataResponse">
<wsdl:part name="parameters" element="tns:GetQueryViewDataResponse" />
</wsdl:message>
+ <wsdl:message name="exception00">
<wsdl:part name="exception00" element="tns:GetQueryViewData.Exception" />
</wsdl:message>
+ <wsdl:portType name="query_view_data">
+ <wsdl:operation name="GetQueryViewData">
<wsdl:input message="tns:GetQueryViewData" />
<wsdl:output message="tns:GetQueryViewDataResponse" />
<wsdl:fault name="exception00" message="tns:exception00" />
</wsdl:operation>
</wsdl:portType>
+ <wsdl:binding name="query_view_dataSoapBinding" type="tns:query_view_data">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="GetQueryViewData">
<soap:operation soapAction="" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
- <wsdl:fault name="exception00">
<soap:fault name="exception00" use="literal" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
+ <wsdl:service name="query_view_dataService">
- <wsdl:port name="query_view_dataSoapBinding" binding="tns:query_view_dataSoapBinding">
<soap:address location="http://sdhpbwa1.gdc.mycompany.com:8023/sap/bw/xml/soap/queryview?sap-client=100" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Suggestions for Chunking Large Outbound Web Service Messages from BPEL

We have a problem today when Oracle EBS sends a large amount of data to BPEL, BPEL processes that data and then attempts to pass that data as a web service via a partner link to the PeopleSoft integration broker. When the message is too large ( > 10,000 records or so) we are hitting some issues on the PeopleSoft web server side being unable to receive that large of a message.
"allocLargeObjectOrArray - Object size: 32768016, Num elements: 8192000"
We are considering adjusting the BPEL program to chunk the outbound data being sent to PeopleSoft. The idea would be to use some type of loop and just break after so many lines, transmit the current message and then start a new message.
The PeopleSoft integration broker has a setting, for outbound type integrations, that can enable an automated chunking feature called ‘Max App Message Size’. I was wondering, does BPEL have a similar configuration setting that might provide this feature? I’m dreaming up that this could be a property of the partner link object that could allow you to specify a certain ‘max size’ and then it would just know to start a new message at that threshold. That might avoid us having to make any additional BPEL code changes at this point.
Currently using version 11.1.1.1.
Any advice, much appreciated.
Regards,
Ken

I have found the following tutorial that implements something similiar to what I am trying to do: http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/10g/10135/odiscenario_bpelcallback/odiscenario_bpelcallback.htm#t3
Because of this, I am now confident that the conversation IDs can be used to achieve correlation. I have implemented the pattern by performing
an invoke activity on the web service, passing the result of ora:getConversationId() as part of the message. The conversation Id returned is of UUID-Form.
After the invoke activity, I have added a pick activity to receive the response message supplied by the web service through IDeliveryService.post(...). I can see that the message is received correctly by loooking at the contents of DLV_MESSAGE. However, the pick activity times out every time (after 10m). Looking at DLV_SUBSCRIPTION reveals that the conversation_id for the pick/receive activity is set to a value of the form bpel://localhost/default/MyBpelProcessName~1.0/7610001-BpInv0-BpSeq2.7-2. As far as I know, this should instead be set to the UUID that ora:getConversationId() returned before performing the invoke activity. What is going wrong here?
Thanks for your help!

Office 365 Reporting Web Service Message Trace - It says it can get the past 30 days but i can only get the past 7 days

It says Message Trace data is stored for 90 days here: http://technet.microsoft.com/library/jj723162(v=exchg.150).aspx
When running the MessageTrace report using the Office 365 Reporting Web Service it only returns the past
7 days, even though it says up to 30 days here: http://msdn.microsoft.com/en-us/library/office/jj984335(v=office.15).aspx.
PowerShell’s "Get-MessageTrace" cmdlet only returns the past 7 days as well. PowerShell also has
an alternative cmdlet called "Start-HistoricalSearch" which returns the MessageTrace results between 7 and 90 days old.
Is it supposed to return 30 days, or is the documentation wrong, or is their an alternative report (like
PowerShell) to get MessageTrace results for over 7 days using the Office 365 Reporting Web Service?
Note: I'm aware that the results are returned in batches of 2000 MessageTrace results.

That document is pretty old last modified March 2013 so I would say it's out of date. The reporting services are still pretty new in the current release I believe 7 days is limit for the Rest Endpoint and the Get-MessageTrace cmdlet (which is what
the more recent documentation around message tracking say) there is no REST endpoint for Start-HistoricalSearch you can see all the current endpoints by looking at the Metadata via
https://reports.office365.com/ecp/reportingwebservice/reporting.svc/$metadata
These services are evolving so new features and reports are added which is explained in
http://msdn.microsoft.com/EN-US/library/office/jj984346(v=office.15).aspx . But there is no public information on Timeframes and what reports and features are going to be added in future updates (that I know of). If you need data older then
7 days then Automating the HistoricalSearch cmdlets would be the way to do it for now.
Cheers
Glen

How to view web service definition details using Netweaver ?

Hi,
I have installed Netweaver 7.01 trial version, and I have seen using the Web Service Browser, that all BAPI's are exposed as web services already. I would like to view the web service details for some of these BAPI's, in order to understand the authentication, authorization details for these as I plan to try and call these through java.
I basically want to understand whether they are using BASIC authentication by default or configured to use something else.
Any guidance on this is appreciated.
thx,
-Kev.

Did you try unpublishing it ...
HOW CAN I DELETE SERVICES IN THE SERVICES REGISTRY?
The concept of the Services Registry sees the content of the registry as a mirror of the various backend systems from which you publish into the registry. To ensure consistency, you should not manually delete service definitions from the registry, but instead it is recommended to use the publication rules functionality of SAP NetWeaver Administrator (Java) and SOA Manager (ABAP) to u2018unpublish' service definitions that are no longer required.
However, if you still need to delete service definitions, you can make use of the corresponding API and manually remove service definitions.
from the following link ...
/docs/DOC-8782#section172 [original link is broken]
Regards
M

Which Web Service message formats are supported?

Hi,
From the documentation it looks like only SOAP binding 1.1 is supported but nothing is mentioned about the supported message formats, e.g. Document literal (wrapped/bare), rpc-encoded, rpc-literal. etc. Does anybody know which are supported?
Regards Pete

Hi,
I opened a SR on Metalink and got this answer:
ApEx supports only RPC/literal style. The current support for Web services was designed to work with RPC style Web services nearly three years ago. We (
ApEx development/product management) are reviewing enhancement to more broadly support Web services and hope to have that support in a future release.
For the current support of Web services in Oracle Application Express, a design decision was made to support only WSDL’s that use the W3C XML Schema specification as it
is data type system. Just converting a Web service to RPC style is not all that is required to make it work properly with Application Express. It also must use the XML Schema specification as its data type system and prefix those type references, with the same prefix as the XML Schema reference in the definitions declaration in the WSDL.
Oracle Application Express expects type declarations to be fully qualified with the same prefix of the reference to the XML Schema specification as in the WSDL’s definitions declaration (http://www.w3.org/2001/XMLSchema). If the WSDL contains type references that are not qualified with the prefix of the XML Schema specification, then editing the WSDL to include these type references with the corresponding prefix will allow Oracle Application Express to properly parse the WSDL.
Support for more loosely defined types is planned for a future release of Oracle Application Express.
Regards Pete

Is it possible to use TCP/IP Monitor with web services?

Hi!
I have created a web service in workshop 10 and deployed it on a WLS10 inside workshop. I have turned on TCP/IP monitoring and in this case it uses port 13458. I have also generated a test client using the clientgen ANT task.
Now I'm using the generated client classes in the following way:
TestWSXSDService service = new TestWSXSDService_Impl ("http://localhost:13458/TestWSXSD/TestWSXSD?WSDL");
TestWSXSD port = service.getTestWSXSDSoapPort();
Apparently the classes retrieves the WSDL file from the server and this request show up on the TCP/IP Monitor.
However, when I finally executes my request:
port.hello(in);
it's apparently using the endpoint information from the retrieved WSDL file and the request goes to port 7001.
This is the request I want to monitor! Is there a way to make this work with the client classes generated by clientgen or must I make my client in some other way in order to keep a fixed end point against the TCP/IP Monitor?
Thank you.
/John
Edited by johnlindgreen at 08/10/2007 4:51 AM

Hi!
I tried to set the suggested properties both on the client and server side, but as far as I can tell they don't wotk with WLS 10. Maybe I'm doing something wrong?
I tried to serach the documentation and found weblogic.webservice.verbose documented for WLS 8 and weblogic.webservice.client.verbose documented for WLS 9. I couldn't find anything for WLS 10.
But then I re-found something about using a proxy server from a client [url http://edocs.bea.com/wls/docs100/webserv/client.html#proxy_server]. This actually does the trick. So now my code looks like this:
               TestWSXSDService service = new TestWSXSDService_Impl ();
               TestWSXSD port = service.getTestWSXSDSoapPort();
          Proxy p = new Proxy(Proxy.Type.HTTP, new InetSocketAddress("localhost", 13458));
          HttpTransportInfo info = new HttpTransportInfo();
          info.setProxy(p);
          ((Stub)port)._setProperty("weblogic.wsee.connection.transportinfo",info);
This keeps the client use my TCP/IP Monitor as endpoint.
/John

Complete web service message not showing next operation

Hi,
When sending Xchange complete message, the response shows the next operation. But when using web service for complete the response shows the next queue operation as the same as I have done complete for. Have anybody seen this before and know a solution? I have tested both in 5.2 and 6.0
<PRODUCTION_REQUEST>
   <COMPLETE>
      <SFC_LIST>
         <SFC>
            <SITE>KRHALL</SITE>
            <ID>SE11410000</ID>
            <RESOURCE>X-LINE</RESOURCE>
            <OPERATION>SM2</OPERATION>
            <USER>JONORD</USER>
         </SFC>
      </SFC_LIST>
   </COMPLETE>
</PRODUCTION_REQUEST>
<PRODUCTION_RESPONSE>
<COMPLETE>
    <SFC_LIST>
      <SFC>
        <ID>SE11410000</ID>
        <ITEM>3EST000215-9384</ITEM>
        <ROUTER>3EST000215-9384</ROUTER>
       <STEP_ID>021</STEP_ID>
       <REWORK>false</REWORK>
       <QTY>1</QTY>
       <TIMES_PROCESSED>1</TIMES_PROCESSED>
       <STEP_COMPLETED>true</STEP_COMPLETED>
       <DONE>false</DONE>
       <DATE_TIME>2012-02-22T14:59:19.320Z</DATE_TIME>
      <QUEUED_STEPS>
         <QUEUED_STEP>
           <ROUTER>3EST000215-9384</ROUTER>
           <STEP_ID>030</STEP_ID>
           <OPERATION>AOI</OPERATION>
        </QUEUED_STEP>
     </QUEUED_STEPS>
   </SFC>
</SFC_LIST>
</COMPLETE>
</PRODUCTION_RESPONSE>
     <me:CompleteRequest_sync>
         <me:CompleteRequest>
            <me:SiteRef>
               <me:Site>KRHALL</me:Site>
            </me:SiteRef>
            <!1 or more repetitions:>
            <me:SfcRequest>
               <me:SfcRef>
                  <!You may enter the following 2 items in any order>
                  <me:Sfc>SE1141000A</me:Sfc>
               </me:SfcRef>
               <me:ResourceRef>
                  <!You may enter the following 2 items in any order>
                  <me:Resource>X-LINE</me:Resource>
               </me:ResourceRef>
               <me:OperationRef>
                  <!You may enter the following 3 items in any order>
                   <me:Operation>SM2</me:Operation>
                  <me:Revision>#</me:Revision>
               </me:OperationRef>
               <me:UserRef>
                  <!You may enter the following 2 items in any order>
                  <me:UserId>JONORD</me:UserId>
               </me:UserRef>
            </me:SfcRequest>
         </me:CompleteRequest>
      </me:CompleteRequest_sync>
         <ns2:CompleteResponse>
            <ns2:SfcResponse>
               <ns2:DateTime>2012-02-22T16:45:22.319+01:00</ns2:DateTime>
               <ns2:Done>false</ns2:Done>
               <ns2:ItemRef>
                  <ns2:Item>3EST000215-9384</ns2:Item>
                  <ns2:Revision>03</ns2:Revision>
                  <ns2:SiteRef>
                     <ns2:Site>KRHALL</ns2:Site>
                  </ns2:SiteRef>
               </ns2:ItemRef>
               <ns2:Quantity>1</ns2:Quantity>
               <ns2:QueuedStep>
                  <ns2:OperationRef>
                     <ns2:SiteRef>
                        <ns2:Site>KRHALL</ns2:Site>
                     </ns2:SiteRef>
                     <ns2:Operation>SM2</ns2:Operation>
                     <ns2:Revision>1</ns2:Revision>
                  </ns2:OperationRef>
                  <ns2:RouterRef>
                     <ns2:SiteRef>
                        <ns2:Site>KRHALL</ns2:Site>
                     </ns2:SiteRef>
                     <ns2:Router>3EST000215-9384</ns2:Router>
                     <ns2:Revision>03-02</ns2:Revision>
                     <ns2:RouterType>U</ns2:RouterType>
                  </ns2:RouterRef>
                  <ns2:StepId>021</ns2:StepId>
               </ns2:QueuedStep>
               <ns2:Rework>false</ns2:Rework>
               <ns2:RouterRef>
                  <ns2:SiteRef>
                     <ns2:Site>KRHALL</ns2:Site>
                  </ns2:SiteRef>
                  <ns2:Router>3EST000215-9384</ns2:Router>
                  <ns2:Revision>03-02</ns2:Revision>
                  <ns2:RouterType>U</ns2:RouterType>
               </ns2:RouterRef>
               <ns2:SfcRef>
                  <ns2:Sfc>SE1141000A</ns2:Sfc>
                  <ns2:SiteRef>
                     <ns2:Site>KRHALL</ns2:Site>
                  </ns2:SiteRef>
               </ns2:SfcRef>
               <ns2:StepCompleted>true</ns2:StepCompleted>
               <ns2:StepId>021</ns2:StepId>
               <ns2:TimesProcessed>1</ns2:TimesProcessed>
            </ns2:SfcResponse>
         </ns2:CompleteResponse>

Hi,
I have now raised a ticket for this issue.
Br,
Johan

Problem viewing web service in wsnavigator

I have a portal project with a working portal service and component (for testing the portal service). I've followed the documentation <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/d6/f9bc3d52f39d33e10000000a11405a/frameset.htm">Creating a Web Service from a Portal Service</a> to create a web service and deploy it. The problem I'm having is that I can't find any indication that my web service exists on the portal. It doesn't appear in wsnavigator and I can't access the WSDL via URL. Any ideas on what I might be missing?

I have a portal project with a working portal service and component (for testing the portal service). I've followed the documentation <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/d6/f9bc3d52f39d33e10000000a11405a/frameset.htm">Creating a Web Service from a Portal Service</a> to create a web service and deploy it. The problem I'm having is that I can't find any indication that my web service exists on the portal. It doesn't appear in wsnavigator and I can't access the WSDL via URL. Any ideas on what I might be missing?

Double precision formatting in web service messages

I currently have a value passed in the response of a web service that represents a currency value. Right now I have it defined as a double type in xsd. Every time I return a value such as 12.00 the value gets truncated to 12.0. And if I have a value of 12.01, the entire number is returned. What is the best way to make sure the value is always two decimal places for the returned value?
Or does the client side have to know if the number is 12.0, then the second decimal is 0 etc?

I think its working i redefined the web service call and was able to use it with no problems - except when I try to substitute a form variable into the call. The webservice actuals does not substitute the variable.
So this is the webservice call that I set up - and what ends up in the database is "#P72_NAME#" instead of what is in the field
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://com.remp.web.sas.dataimport.type">
<soapenv:Header/>
<soapenv:Body>
<com:registerCompound>
<String_1>#P72_NAME#</String_1>
<Double_2></Double_2>
<String_3></String_3>
</com:registerCompound>
</soapenv:Body>
</soapenv:Envelope>

EWPS - web-service messaging queue

Hi,
We have deployed EWPS webservice and tested through SOAP-UI interface. This is tested successfully.
But the issue that we are facing is whenever we go into the iDocumaker web page ; the SOAP UI is getting error out with the following message
"Native Library C:\docclnt\MSMQLIB.DLL already loaded in another classloader"
Is it that we can use only the "message-queues" only for one application ? Or, we need to define a different message queue for EWPS ?
Thanks..

Hi Pradip,
The message queues provide a decoupled integration between your applications (e.g. iDocumaker and EWPS) and the back-end services, brokered by Docupresentment (IDS). Even though iDocumaker runs on the backend servers, it is still treated as a client to Docupresentment much like EWPS - both use IDS client communication APIs to interact with the message queues. The idea is that many applications (think multiple users of a web application, or multiple users of a thick-client application) are able to interact with the back-end services using the queues without causing overload on the back-end servers.
So, the short answer is that using queues is a way to provide scalable infrastructure that allows many applications to interact with the back-end services. In general, the products (iDocumaker, EWPS, IDS) are configured in such a way as to prevent users from accessing items that are in-use by other users.
If this doesn't adequately answer your question, we'll probably need additional details.
Thanks!
-Andy

How to create Web Service based on PI WSDL message

Hi all,
we have following scenario:
Within PI (version 7.1) we set up a message type and inbound service interface. This service interface should send the PI message to a web service running on a SAP J2EE (version 7.01). As the PI message is sent as WSDL I thought it should be easy to build a web service on the SAP J2EE based on this WSDL from PI.
Unfortunately, I have problems creating the Web Service.
For my current project we integrated the NWDI to the SAP NetWeaver Developer Studio and I'm required to add the Web Service to an existing DC (Development Component) within the NWDI.
What I tried so far is:
- I created a Deployable Proxy Project and within this I created a Client Proxy Definition based on the WSDL from the PI. But I can't add this Proxy to the DCs of the NWDI and I don't know how to implement my own coding here in order execute specific functions.
- I created a new class within the NWDI DC and a public method. Based on this I created a Virtual Interface and a Web Service Definition (WSD). Then I added this to a Web Service Deployment Descriptor. I uploaded this to the SAP J2EE. But I'm not able to access this and I don't know hoe to assign the WSDL here.
I also tried here to create a client proxy based on this WSD as I thought I might assign the WSDL here. But I don't see the WSD in the list of Web Services uploaded to the SAP J2EE...
Can you please advice me how to create a Web Service in such an environment?
regards
René Jurmann

Hi Tahir,
sorry that you needed to wait this long - but this is how I created the web service:
The steps on how to create the web service in NetWeaver Developer studio are nearly the same as described in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5838. [original link is broken] [original link is broken] [original link is broken]
Some steps I just skipped and some others I added. Some of the steps I did the way I described it as I needed to connect the web service with the SAP PI.
Prerequisites:
Add Java Perspective and J2EE Development Perspective to the open perspectives.
Within "Window - Preferences - Web Services" check "Soap extensions visible in the virtual interface editor"
The SDM of the corresponding SAP J2EE is configured within "Window - Preferences"
Create a Development Component (DC) with type "J2EE -> EJB Module"
The business logic of the web service will be implemented in an Enterprise Java Bean (EJB). So first the EJB component must be created:
     Choose "File -> New -> Other"
     In opening PopUp choose "Development Component -> Development Component Project"
     Select the Software Component for which you want to add the DC (e.g. "Local Development -> MyComponents")
     Choose now vendor, name and type:
          vendor is an alpha-numeric string of 20 characters starting with a letter - all in lower case
          name is an alpha-numeric string starting with a letter - all in lower case
          vendor and name concatenated must not be longer then 40 characters
          the name can be separated into different part using "/" as separator
          each part of the name must not be longer than 8 characters
          the type is "J2EE - EJB Module"
          you can specify a Caption as general description for the web service
Create new EJB
To create the EJB itself:
     In J2EE DC Explorer of J2EE Development Perspective expand new DC and right-click on folder "ejbModule"
     Choose "New - EJB" with following details:
          EJB Name: <name as for PI service Interface to be created - starting in upper case>
          EJB Project: <pre selected>
          Bean Type: Stateless Session Bean
          Default EJB Package: <corresponds to namespace in PI>
          generate default interfaces: Checked
Regarding the "Default EJB Package" this should be created according the namespace in PI for which all PI objects will be created. This only applies if you have some naming conventions here.
Example:
Namespace in PI is: http://company.net/pi/SOFTWARE_COMP/Application
The corresponding package then is: net.company.pi.software_comp.application
Implement coding for web service
As the web service will be called via PI some transfer variables will be submitted. Most likely, those variables will not be standard type (e.g. String) but a complex type. Those types must be generated as Java classes. Below an example of a complex type I needed:
Data Type
net.company.pi.software_comp.application.types.MessageProcessingInformation
Structure:
     Element name          Element type
     sendingSystemID          String
     interfaceID               String
     businessProcessVariantCode     String
     testIndicator               Boolean
For every element described a public "get", "set" and "has" method must be created in the corresponding Java class:
package net.company.pi.software_comp.application.types;
import java.io.Serializable;
public class MessageProcessingInformation implements Serializable {
     protected String sendingSystemID;
     protected String interfaceID;
     protected String businessProcessVariantCode;
     protected Boolean testIndicator;
     public String getSendingSystemID() {
          return sendingSystemID;
     public void setSendingSystemID(String value) {
          this.sendingSystemID = value;
     public boolean hasSendingSystemID() {
          if(sendingSystemID != null && !sendingSystemID.equals("")){
               return true;
          return false;
All Java classes representing complex types and all classes referenced here (used for sub-types) must implement java.io.Serializable. Java standard types which do not implement this class must not be used as sub-types.
As soon as all data types are declared the real business logic can be implemented:
     In J2EE DC Explorer of J2EE Development Perspective expand DC - "ejb-jar.xml" - <Name> and double click on "ejbCreate"
     In detail view select folder "Business Methods" and click "Add"
     choose name of business method - this should be the same as the PI message type used for the service interface - starting lower case
     return type should be "void"
     add needed parameters fully qualified - including package (as specified in PI and created previously in DC)
     you can mark certain parameters as array if necessary
Remark:
It might be that after saving you get an error. This might be as the package name of one component is copied to the corresponding Java class at the very beginning (before the package declaration within the Java class). Simply delete the string here.
It also might be, that the new business method is only defined in the remote interface class but not in the bean class. Just create an according method in the bean class.
Within the newly created business method within the bean class you can now implement the business logic.
Create a DC with type "J2EE -> Enterprise Application"
In order to create the "real" web service and deploy it to the J2EE an Enterprise Application project has to be created. So create a new DC as for the EJB Module but choose as type "J2EE -> Enterprise Application".
After the DC is created right click on the EJB DC and choose "Add to EAR Project". Choose the new DC.
Create web service for EJB
As soon as you implemented the business logic you can create the "real" web service. Therefore:
     Right click on the EJB name below "ejb-jar.xml"
     Choose "New - Web Service"
     Choose proper "Web Service Name" and "Configuration Name" (probably oriented at the EJB name)
     Copy the URL of the web service - you'll need it later for PI configuration
     on the second next screen use the same name for "Virtual Interface" and "Web Service Definition" (the name should be the name of the "Endpoint")
     the "EAR Project" should be preselected
Unfortunately, the web service can't be used in its current configuration to be accessed by PI. Therefore the Virtual Interface must be changed. To do so, expand folder "Virtual Interfaces" and double click the virtual interface created.
Within the detail view expand in tabs "Mapping" and "Types" the complete folder structure. For any "SOAP Extension" where a namespace can be defined use as namespace the corresponding namespace in PI (e.g. http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/BillerDirect) but do not change any "Soap Extension" of a standard Java type. (if you don't have any naming convetions for namespaces in PI you can leave the SOAP Extension here. But then the namespace in PI should be set accordingly.)
Probably it can be necessary on top level "Soap Extensions" in tab "Mapping" to leave "Use Namespaces for Parameters" unchecked. For some of my web services this parameter must be checked for others not - just try.
If you can define a "New Name", "Local Name" or "Item Label" for a Soap Extension then use a name with starting upper case letter. (For Java Naming conventions most of the data type names will start with lower case letters.) Especially the method name must be renamed this way in order to stick to the PI namings.
As a last point to change here check in tab "Mapping" all "Incoming Parameters" which you specified as array. Use for those as "New Name" a different name - do not just simply change from lower case to upper case. This is necessary as on PI we need to create two levels although here only one is specified.
For any own sub-type declared as array the name within the coding should also differ from the corresponding Java Class name the type refers to.
If all this is done you can deploy the web service to the J2EE:
     right click on "Enterprise Application" DC and choose "Development Component - Build..." and build all corresponding components
     right click on "Enterprise Application" DC and choose "Development Component - Deploy"
Test the new web service via <J2EE URL>/wsnavigator/enterwsdl.html
Create PI interface
After the web service is created successfully the PI integration can be started.
Therefore, within the Enterprise Services Builder create a data type according to the web service definition. All components defined on top-level for this data type should be declared as incoming parameter for the web service business method. Therefore it could be necessary to create some sub data types on PI first and add those to the "master" data type.
Ensure that the names of the components correspond to the names defined in the web service (see virtual interface here). Those names must exactly be the same - including lower/upper case. Also take care for the ordering of the components.
In case you need to include arrays following applies:
The upper level is of occurrence "1:1". This has only one sub-entry with occurrence "1:n". The names for upper and sub-level must not equal.
Based on the data type a message type is created. The name of the message type must be exactly the same as the name of the web service business method. (Hint: the name of the web service business method was most likely changed in the virtual interface. Then this name must correspond to the message type name.) Based on the message type an asynchronous inbound interface is to be created (which will be referred in the Integration Directory). The operation name for this interface (left panel) should be the same as the name for the web service business method.
Create PI mappings and routings
How to map (message mapping and operation mapping) from source to the web service message I wont explain here as this depends on the source message. The only important things here are:
     When creating the SOAP communication channel within the Integration Builder the "Target URL" is:
          <J2EE URL>/<Access URL as specified in web service creation>?wsdl&style=document
     The soap action is the name of the web service business method.
     Most likely the web service needs authentication to be executed.

Monitoring/Viewing Web Service Messages in GlassFish

Similar Messages

Maybe you are looking for