Salutation web service cannot run

I have only installed Sun One Studio 5 that came with Application Server 7.
Following the example on this link
http://developers.sun.com/tools/javatools/articles/buildingWS.html
I have managed to get these 4 examples to run
http://localhost:7778/servlet/HelloWorld Hello World!
http://localhost:7778/servlet/HelloWorld?m=0 Hello World!
http://localhost:7778/servlet/HelloWorld?m=1 Greetings, World!
http://localhost:7778/servlet/HelloWorld?m=2 Excuse me, I did not understand.
There is some difficulty however running the SalutationService there error message when I activate this link:
http://localhost:7778/SalutationService
HTTP 404 Not found.
I have changed the server instance to port 7779
but it is also giving the same not found message.
Any ideas why the web service is not running.
Also when I check the server instance for port 7779, under deployed applications there is nothing there. Should SalutationService be listed there?
Thanks.

Have you figured this one out yet?
The article has http://localhost/SalutationService/SalutationService as the endpoint URL (also called "SOAP RPC URL" in the IDE). What endpoint URL are you using? If the generated JSPs come up, the second line in the header says what the endpoing URL they're using is.
Also, you said you "changed the server instance to port 7779". If you changed the endpoint URL, you need to update it in the "SOAP RPC URL" property of the web service node, and then refresh it's client(s).

Similar Messages

Polycom CX 600 - Certificate web service cannot be found

Hi All,
I know, there are some same issues in the forum, bot those are not helpful for me. My problem is the same, via network cable (using just DHCP) the Polycom CX 600 Lync Phone are not able to sign in (however 1 month ago it was), returning the error message:
'Certificate web service cannot be found.'
I've double checked the DHCP options and all of them are OK! We are not using Windows DHCP, but the options are right, the 43 option containing the proper hexa value, the sub-options are also valid. From the DHCP log I can verify that the device got the
options, but the phone still not able to sign in.
From the browser I cannot open the device, by it's IP, just with FTP:\\'IP'. There I could find a .clg1 log file, but it not containing useful information for me.
This is the link of the log file: http://speedy.sh/XAgMT/system.clg1
If I run the DHCPUtil.exe -emulateclient on my workstation, I got the following:
Starting Discovery ...
Result: Failure = -2147014848
Or... sometimes it has a result:
Starting Discovery ...
Sending Packet (Size: 288, Network Adapter: 57.56.69.138, Attempt Type: Broadcas
t + Unicast)
--Begin Packet--
DHCP: INFORM (xid=5C1E8177)
DHCP: Op Code (op) = 1
DHCP: Hardware Type (htype) = 6
DHCP: Hops (hops) = 0
DHCP: Transaction ID (xid) = 1545503095
DHCP: Seconds (secs) = 0
DHCP: Flags (flags) = 0000
DHCP: Client IP Address (ciaddr) = 57.56.69.138
DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 0.0.0.0
DHCP: Client HW Address (chaddr) = E0DB55DE###--End Packet--
Received Packet
Sender:57.20.120.85:67, Size:408
--Begin Packet--
DHCP: ACK (xid=5C1E8177)
DHCP: Op Code (op) = 1
DHCP: Hardware Type (htype) = 6
DHCP: Hops (hops) = 0
DHCP: Transaction ID (xid) = 1545503095
DHCP: Seconds (secs) = 0
DHCP: Flags (flags) = 0000
DHCP: Client IP Address (ciaddr) = 57.56.69.138
DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 57.56.69.131
DHCP: Client HW Address (chaddr) = E0DB55DE8993
DHCP: Server Host Name (sname) =
DHCP: Boot File Name (file) =
DHCP: Magic Cookie = 99.130.83.99
DHCP: Option Field
DHCP: DHCP MESSAGE TYPE( 53) = (Length: 1) DHCP ACK
DHCP: Server Identifier( 54) = (Length: 4) 57.20.120.85
DHCP: Client Identifier( 61) = (Length: 0) ()
DHCP: SIP Server( 120) = (Length: 18) enc:0 lync2013.dlh.de (00086C79
6E633230313303646C6802646500)
DHCP: Host Name( 12) = (Length: 0)
DHCP: Vendor Identifier( 60) = (Length: 0)
DHCP: Param Req List( 55) = (Length: 0) 0 0
DHCP: Vendor Info( 43) = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
36463736324634333635373237343530373236463736363937333639364636453639364536373533
36353732373636393633363532453733373636335D)
DHCP: End of this option field
--End Packet--
Received Packet
Sender:57.20.120.85:67, Size:408
--Begin Packet--
DHCP: ACK (xid=5C1E8177)
DHCP: Op Code (op) = 1
DHCP: Hardware Type (htype) = 6
DHCP: Hops (hops) = 0
DHCP: Transaction ID (xid) = 1545503095
DHCP: Seconds (secs) = 0
DHCP: Flags (flags) = 0000
DHCP: Client IP Address (ciaddr) = 57.56.69.138
DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 57.56.69.130
DHCP: Client HW Address (chaddr) = E0DB55DE8993
DHCP: Server Host Name (sname) =
DHCP: Boot File Name (file) =
DHCP: Magic Cookie = 99.130.83.99
DHCP: Option Field
DHCP: DHCP MESSAGE TYPE( 53) = (Length: 1) DHCP ACK
DHCP: Server Identifier( 54) = (Length: 4) 57.20.120.85
DHCP: Client Identifier( 61) = (Length: 0) ()
DHCP: SIP Server( 120) = (Length: 18) enc:0 lync2013.dlh.de (00086C79
6E633230313303646C6802646500)
DHCP: Host Name( 12) = (Length: 0)
DHCP: Vendor Identifier( 60) = (Length: 0)
DHCP: Param Req List( 55) = (Length: 0) 0 0
DHCP: Vendor Info( 43) = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
36463736324634333635373237343530373236463736363937333639364636453639364536373533
36353732373636393633363532453733373636335D)
DHCP: End of this option field
--End Packet--
Received Packet
Sender:57.20.120.100:67, Size:408
--Begin Packet--
DHCP: ACK (xid=5C1E8177)
DHCP: Op Code (op) = 1
DHCP: Hardware Type (htype) = 6
DHCP: Hops (hops) = 0
DHCP: Transaction ID (xid) = 1545503095
DHCP: Seconds (secs) = 0
DHCP: Flags (flags) = 0000
DHCP: Client IP Address (ciaddr) = 57.56.69.138
DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 0.0.0.0
DHCP: Client HW Address (chaddr) = E0DB55DE8993
DHCP: Server Host Name (sname) =
DHCP: Boot File Name (file) =
DHCP: Magic Cookie = 99.130.83.99
DHCP: Option Field
DHCP: DHCP MESSAGE TYPE( 53) = (Length: 1) DHCP ACK
DHCP: Server Identifier( 54) = (Length: 4) 57.20.120.100
DHCP: Client Identifier( 61) = (Length: 0) ()
DHCP: SIP Server( 120) = (Length: 18) enc:0 lync2013.dlh.de (00086C79
6E633230313303646C6802646500)
DHCP: Host Name( 12) = (Length: 0)
DHCP: Vendor Identifier( 60) = (Length: 0)
DHCP: Param Req List( 55) = (Length: 0) 0 0
DHCP: Vendor Info( 43) = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
36463736324634333635373237343530373236463736363937333639364636453639364536373533
36353732373636393633363532453733373636335D)
DHCP: End of this option field
--End Packet--
Received Packet
Sender:57.20.120.100:67, Size:408
--Begin Packet--
DHCP: ACK (xid=5C1E8177)
DHCP: Op Code (op) = 1
DHCP: Hardware Type (htype) = 6
DHCP: Hops (hops) = 0
DHCP: Transaction ID (xid) = 1545503095
DHCP: Seconds (secs) = 0
DHCP: Flags (flags) = 0000
DHCP: Client IP Address (ciaddr) = 57.56.69.138
DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 57.56.69.131
DHCP: Client HW Address (chaddr) = E0DB55DE8993
DHCP: Server Host Name (sname) =
DHCP: Boot File Name (file) =
DHCP: Magic Cookie = 99.130.83.99
DHCP: Option Field
DHCP: DHCP MESSAGE TYPE( 53) = (Length: 1) DHCP ACK
DHCP: Server Identifier( 54) = (Length: 4) 57.20.120.100
DHCP: Client Identifier( 61) = (Length: 0) ()
DHCP: SIP Server( 120) = (Length: 18) enc:0 lync2013.dlh.de (00086C79
6E633230313303646C6802646500)
DHCP: Host Name( 12) = (Length: 0)
DHCP: Vendor Identifier( 60) = (Length: 0)
DHCP: Param Req List( 55) = (Length: 0) 0 0
DHCP: Vendor Info( 43) = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
36463736324634333635373237343530373236463736363937333639364636453639364536373533
36353732373636393633363532453733373636335D)
DHCP: End of this option field
--End Packet--
Received Packet
Sender:57.20.120.100:67, Size:408
--Begin Packet--
DHCP: ACK (xid=5C1E8177)
DHCP: Op Code (op) = 1
DHCP: Hardware Type (htype) = 6
DHCP: Hops (hops) = 0
DHCP: Transaction ID (xid) = 1545503095
DHCP: Seconds (secs) = 0
DHCP: Flags (flags) = 0000
DHCP: Client IP Address (ciaddr) = 57.56.69.138
DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 57.56.69.130
DHCP: Client HW Address (chaddr) = E0DB55DE8993
DHCP: Server Host Name (sname) =
DHCP: Boot File Name (file) =
DHCP: Magic Cookie = 99.130.83.99
DHCP: Option Field
DHCP: DHCP MESSAGE TYPE( 53) = (Length: 1) DHCP ACK
DHCP: Server Identifier( 54) = (Length: 4) 57.20.120.100
DHCP: Client Identifier( 61) = (Length: 0) ()
DHCP: SIP Server( 120) = (Length: 18) enc:0 lync2013.dlh.de (00086C79
6E633230313303646C6802646500)
DHCP: Host Name( 12) = (Length: 0)
DHCP: Vendor Identifier( 60) = (Length: 0)
DHCP: Param Req List( 55) = (Length: 0) 0 0
DHCP: Vendor Info( 43) = (Length: 130) ☺♀MS-UC-Client☻♣https♥☼lync201
3.dlh☻E6465040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536
572766963652E737663] (010C4D532D55432D436C69656E7402056874747073030F6C796E633230
31332E646C6802453634363530343033333433343333303532353246343336353732373435303732
36463736324634333635373237343530373236463736363937333639364636453639364536373533
36353732373636393633363532453733373636335D)
DHCP: End of this option field
--End Packet--
Result: Failure = 1
I don't know what is that Failure = 1
Has anybody an idea???
Many thanks,
Tamás

Hi,
The DHCP options are good.
Finally, I was able to run the test-csphonebootsrap cmdlet, and I got the following error:
Result : Failure
Latency : 00:00:01.2179659
Error Message : No response received for getting root certificate chain.
Inner Exception:The remote server returned an unexpected respon
se: (417) Expectation Failed.
Inner Exception:The remote server returned an error: (417) Expe
ctation Failed.
Diagnosis :
Inner Diagnosis:Mime-Version : 1.0
X-Squid-Error : ERR_INVALID_REQ 0
Vary : Accept-Language
Content-Language : en
X-Cache : MISS from proxy.lsy.bud.dlh.de
X-Cache-Lookup : NONE from proxy.lsy.bud.dlh.de:3128
Connection : close
Content-Length : 3944
Content-Type : text/html
Date : Thu, 09 Jan 2014 13:24:47 GMT
Server : squid/3.1.10
Via : 1.0 proxy.lsy.bud.dlh.de (squid/3.1.10)
VERBOSE: Workflow
'Microsoft.Rtc.SyntheticTransactions.Workflows.STPhoneBootstrapWorkflow'
started.
Workflow
'Microsoft.Rtc.SyntheticTransactions.Workflows.STPhoneBootstrapWorkflow'
completed in '0.0001508' seconds.
Target server Fqdn or web service Url not provided. Will have to do DHCP
Registrar Discovery.
An exception 'No response received for getting root certificate chain.'
occurred during Workflow
Microsoft.Rtc.SyntheticTransactions.Workflows.STPhoneBootstrapWorkflow
execution.
Exception Call Stack: at
Microsoft.Rtc.Admin.Authentication.WebServicesHelper.GetRootCertChains()
at
Microsoft.Rtc.SyntheticTransactions.Activities.GetRootCertChainsActivity.Intern
alExecute(ActivityExecutionContext executionContext)
at
Microsoft.Rtc.SyntheticTransactions.Activities.SyntheticTransactionsActivity.Ex
ecute(ActivityExecutionContext executionContext)
at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity,
ActivityExecutionContext executionContext)
at
System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRunti
me workflowCoreRuntime)
at System.Workflow.Runtime.Scheduler.Run()
Server stack trace:
at
System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(
HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory,
WebException responseException, ChannelBinding channelBinding)
at
System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChanne
lRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message,
TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean
oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan
timeout)
at
System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessa
ge methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage
message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)
at RootCertChainService.GetRootCertChains(GetRootCertChainsRequest request)
at Microsoft.Rtc.Admin.Authentication.WebServicesHelper.GetRootCertChains()
'DHCPDiscover' activity started.
Starting DHCP registrar discovery...
Constructing a DHCP packet.
Adding DHCP option PARAMETER_REQUEST_LIST.
Successfully added DHCP option.
Adding DHCP option VENDOR_CLASS_IDENTIFIER.
Successfully added DHCP option.
Successfully constructed DHCP packet.
Trying to open an udp connection.
Remote IP : 255.255.255.255.
Local IP : 10.150.7.33.
\tCreating a new UDP client.
Udp connection successfully created.
Sending packet.
Remote IP : 255.255.255.255.
Remote Port : 67.
Packet sent successfully.
DHCP discovery message send. Waiting for DHCP servers to respond.
Data received successfully.
Remote IP : 57.20.120.85.
Remote Port : 67.
Response received for the DHCP Discovery message.
Constructing a DHCP packet from received raw data.
Extracting DHCP Options.
Successfully constructed DHCP packet.
Return value for DHCP option : SIP_SERVER.
Found registrar Fqdn : lyncpool.dlh.de.
Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.1.
Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.1 - MS-UC-Client.
Successfully extracted sub option value.
Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.2.
Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.2 - https.
Successfully extracted sub option value.
Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.3.
Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.3 - lyncpool.dlh.de.
Successfully extracted sub option value.
Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.4.
Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.4 - 443.
Successfully extracted sub option value.
Searching for DHCP sub option : VENDOR_SPECIFIC_INFORMATION.5.
Return value for DHCP option : VENDOR_SPECIFIC_INFORMATION.
Found DHCP sub option : VENDOR_SPECIFIC_INFORMATION.5 -
/CertProv/CertProvisioningService.svc.
Successfully extracted sub option value.
Found web service Url :
https://lyncpool.dlh.de:443/CertProv/CertProvisioningService.svc.
Disconnecting.
DHCP registrar discovery activity completed successfully.
'DHCPDiscover' activity completed in '1.2179659' seconds.
'GetRootCertChains' activity started.
Trying to download a certificate chain from web service.
Web Service Url : http://lyncpool.dlh.de/CertProv/CertProvisioningService.svc
Could not download certificate chain from web service.
CHECK:
- Web service Url is valid and the web services are functional.
'UnRegister' activity started.
'UnRegister' activity completed in '3.78E-05' seconds.
VERBOSE: Workflow Instance ID 'a9313cfa-b82c-4bd2-9df6-81acca1bcbbc' completed.
VERBOSE: Workflow run-time (sec): 1.5083016.
It looks like the telephone are not able to download the root CA, but the webservice is available and reachable via port 80 and 443 too.... So, what is the reason? Why the Polycom CX600 is not able to download the root CA??

SAP WebAS Supportability - cannot run Web Service

Hi Experts,
I found in the supported platform document, boe_xi_30_supported_platforms_windows.pdf.
It states that SAP Web Application Server 7 ... Not supported for Web Services.
Does this mean we cannot use Xcelius with Query as a web service on the top of SAP BW ?
Thanks and regards,
Manabu

Hi Manabu,
In the company I'm working for, we want to implement this solution (Business Object <-> SAP and Xcelsius with QAAWS in order to extract data from SAP Queries).
To do so, we got advises from SAP consultants. Apparently, there is a way to customise the WaS server with a special SDK, in order that it supports Web Services.
But the consultants did not recommand this solution (I didn't know why). The way we choosed is to use a Tomcat for the Web Services and a WaS for the rest of all the applications (You just have to interface the two server and to separate the tasks).
I can't tell you the result we've got, because we will try it next month...
Hope it helps...

Web service is running but Server Admin says "Not available"

Hello,
I cannot configure the web service using the Server Admin tool any more. The service is running and showing no error, but the "Web" icon in the "Computer & Services" panel of Server Admin is showing dark grey color. The Overview tab of the Web Service is stating: "Web Service is: Not available"
Any ideas what I can do to get it work again?
sudo apachectl configtest gave no errors or warnings.
Mac OS X (10.4.7)

You should not be logging in as root, despite what anyone has told you.
And the entire mechanism of OS X Server (and most other *nix OS-en), is meant for you to not be logged in as root.
Use sudo and/or authenticate in the GUI when/where needed.
Please try Wesley's advise here:
http://discussions.apple.com/thread.jspa?messageID=2862670
Try launching apache manually, and watch your logs
Ie:
in one terminal window, type:
tail -f /var/log/httpd/error_log
make a new Terminal window and type:
sudo apachectl start

Web Service - Cannot Deploy on Local OC4J

We get the following error when trying to deploy the following code as a web service to the local OC4J.
The parameter of domDoc of type oracle.xml.parser.v2.XMLDocument cannot be serialized into XML, and no custom serializer has been defined for it.
All we want to do with this service is connect to the database and return the results of the query in XML. We have tried a string, but it returns a string of XML and we need it to return the XML.
The code compiles, runs, and looks as though it is returning what it is suppose to if we write the return out, but the code will not deploy as a web service.
Thanx so much
Pam
This is the code:
package getuserform;
import java.io.IOException;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.SQLException;
import oracle.xml.parser.v2.XMLDocument;
import oracle.xml.sql.query.OracleXMLQuery;
public class getUserInfo {
public int GetUserInfo(XMLDocument domDoc){
try {
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
} catch (SQLException e) {
// TODO
return(-1);
String url = "jdbc:oracle:thin:@db:1521:v9it";
Connection myCon;
try {
myCon = DriverManager.getConnection(url,"user","password");
} catch (SQLException e) {
// TODO
return(-1);
OracleXMLQuery qry = new OracleXMLQuery (myCon,
"select upper(t.u_name_frst) || ' ' || upper(t.u_name_last) U_Name," +
" t.user_id, " +
" t.active Active, " +
" to_char(t.termination_dt, 'DD-MON-YYYY') Termination_DT, " +
" '(' || t.area_code || ') ' || t.phone_no Phone, " +
" t.email Email, " +
" t.city City, " +
" (select dpl_desc from schema.dept_pay_locations dpl where dpl.dpl_num = t.pay_location) Pay_Location, " +
" t.LOCATION Location " +
" from schema.users t " +
" where upper(t.user_id) like upper ('u227%')");
// xmlStr = qry.getXMLString(); works.
// return (qry.getXMLString()); works
// !work
domDoc = (XMLDocument)qry.getXMLDOM();
qry.close();
return(0);
}

Hi Pam,
It is using Element as the method return that is causing the problem. As you've seen this means that the Data Control has no concrete schema types to associate with the fields so it fails.
I have a couple of possible workarounds.
1. Is it a requirement to write your SQL query in the method? Perhaps they are to be dynamic?
If not, have you considered using the database to do the query and publishing that as the service. This would work around the problem. You can use JDeveloper to do all of this if you 'wrap' the query in a PL/SQL package in the database. Then use the 'Web Service from PL/SQL Package' wizard to generate the web service including wrapper Java classes for the package and DB connection/mgmt classes.
Or you can publish the actual Query as a service - using the command line (unfortunately you can't use JDEV to do this)
2. You mentioned the XSD for the query - if you have that then you can use a custom serializer and map your XSD to the return type of your method - the org.w3c.dom.Element class:
a. if your web service is already generated - open properties (Web Services Editor)
b. go to Custom Mappings page
c. click Add
d. for Java Class type in org.w3c.dom.Element
e. for XML Qualified Name add your XSD
f. add your serializer class - here is one I made earlier!
package project3;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPException;
import oracle.webservices.SOAPUtil;
import oracle.webservices.databinding.SOAPElementSerializer;
import org.w3c.dom.Element;
public class DummyElementSerialiser implements SOAPElementSerializer
public void init(Map map)
public SOAPElement serialize(QName qName, Object object)
try
return SOAPUtil.toSOAPElement((Element) object);
catch (SOAPException ex)
return null;
if you're generating the service from scratch this same mapping page comes up as part of the wizard
Now you should be able to create your data control
rgds
Susan

Why is the web service cannot be invoked?

Hi Experts,
Scenario: I have created a web service from a function module from SAP CRM using SOAMANAGER. I wish to invoke this web service from Data Services.
I have tried to invoke the web service using the 2 types of data store avaible in Data Services:
- One Web Service datastore
- One Adapter datastore
Both have the same WSDL URL and I see the defintion of the web service in both. Fine.
I created 2 dataflows:
- One invoking the function from the Web Service datastore
- One invoking the function from the Adapter datastore
When I execute the batch job, I get different errors in the 2 dataflows, but the root cause seems to be the same: it cannot access and execute the web service.
- In the dataflow using the function from the Web Service data store, I get the error RUN-248005 There is no response for thte web service. Ensure that the network, web server, and service are running properly. Also ensure that the service call time out is set properly
- In the dataflow using the function from the Adaptor data store, I get the error RUN-058110 Error calling function. Web Service client unable to invoke Web Service Server. Error: (0)null
I have checked the Data Integrator documentation and nothing is mentioned on what is a proper time out setting.
I have followed the white paper of Michael Eaton [Building Data Integrator Real Time Jobs and Calling Web Services|http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20bd5e60-11f9-2b10-2bbb-b5109cceff08?quicklink=index&overridelayout=true]. Nothing is mentioned in there in regards of special configuration. Yet, my scenario is a bit different here as I am using and external web service and not a published web service from Data Services.
Is there some Data Services configuration missing here? The web service is not secure: it as the lowest level of security, which is NONE! :).
What am I am missing :(?
Thanks a lot & Best Regards
Isabelle

Hi Manoj,
Thanks for the tip, unfortunately it still doesn't work.
I had posted a thread to the web service forum [Re: How to get the http.proxyHost and http.proxyPort?;. I was given the tip to invoke the web service using SOAP UI ([www.soapui.org]). I was able to invoke my web service and execute the service successfully! That's one win!
Yet, in DS it still doesn't work :(. I have:
- Added the Dhttp.proxyHost and Dhttp.proxyPort in the Additional Java Launcher Options in DS Management Console. I am not sure I have the right ones though. I think I might have the wrong values. I will recheck. Yet, when using SOAP UI, I don't need it so I am wondering why DS needs this.
- I have added the user/password in the adaptor datastore where the WSDL is specified.
I couldn't find any documentation related to the possible options for Additional Java Launcher Options. Where is this documented?
Thanks for your help & Best Regards
Isabelle

Web service: Cannot remove WSS security setting

Hi,
i have a problem about developing web service with jdeveloper 10.1.3.1
The problem is that ---> once i have add the security to the web service
(through the web service wizard .. i,e, right click the web service and
select "Secure Web Service'), i CANNOT REMOVE the security setting using
the web service wizard...
call the web service always say missing wsse:Security SOAP header..
do anybody have the solution?
thank you...

Hi,
the issue is still there in 10.1.3.3, and it must be somewhere on JDeveloper or OC4J side. Moreover, it's not limited to removing security settings, as the situation (old settings remembered) is the same when editing security settings.
lsp,
before regenerating a web service and its xml files (editing security properties), make sure you have cleaned the project and then you can try deleting the oracle-webservices.xml file from your project directory, because JDeveloper does not seem to be willing to overwrite it during regeneration.
If this does not help and you are using embedded OC4J, you can try the following steps before running the web service again:
- delete the embedded-oc4j/application-deployments/current-workspace-app directory, because it contains an oracle-webservices.xml file which may be outdated,
- empty the contents of embedded-oc4j/config/wsmgmt.xml, because it contains security settings for web services you have deployed so far, which also may be outdated,
- restart JDeveloper :)
Note that these are just guesses to solve the problem. Unfortunately doing all of these did not solve it for me.
So if anybody has some more ideas, we'll be happy to hear them.
Thanks,
Patrik

Invoking a web service - cannot resolve method parameter

I am getting a failure trying to invoking a method called sl_Access on a web service.
(Same code worked in Workshop 7.1, but fails in Workshop 8.0. The WDSL has not
changed.) WLW is not able to revolve a method parameter called piCustNo. The service
call works in WLW 7.1, but not 8.0.
Any insight on how to fix this problem?
The service call
private AnonType_sl_AccessResponse response = null;
nlastid = response.piLastId;
the service definition from wsdlControl.jcx ----
* @jc:protocol form-post="false" form-get="false" http-soap="true"
public AnonType_sl_AccessResponse sl_Access (int piCustno);
console error output -----
Submitted at Wednesday, October 8, 2003 2:15:22 PM EDT
Exception in sl_Access
com.bea.control.ServiceControlException:
SOAP-ENV:Client
An error was detected in the Web Service request. (10894)
Cannot resolve method sl_Access parameter ns:piCustno (10933)e91a6247e9b693c3:-1b6d127:f811fed2db:-8000#17
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:846)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:359)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:387)
at $Proxy11.sl_Access(Unknown Source)
at com.ovid.service.AccessService.getRepl(AccessService.java:93)
at com.ovid.service.AccessService.processBatch(AccessService.java:71)
at Controller.runAccess(Controller.jws:399)

see:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.workshop&item=1730
Joe Smith wrote:
>
I am getting a failure trying to invoking a method called sl_Access on a web service.
(Same code worked in Workshop 7.1, but fails in Workshop 8.0. The WDSL has not
changed.) WLW is not able to revolve a method parameter called piCustNo. The service
call works in WLW 7.1, but not 8.0.
Any insight on how to fix this problem?
The service call
private AnonType_sl_AccessResponse response = null;
nlastid = response.piLastId;
the service definition from wsdlControl.jcx ----
* @jc:protocol form-post="false" form-get="false" http-soap="true"
public AnonType_sl_AccessResponse sl_Access (int piCustno);
console error output -----
Submitted at Wednesday, October 8, 2003 2:15:22 PM EDT
Exception in sl_Access
com.bea.control.ServiceControlException:
SOAP-ENV:Client
An error was detected in the Web Service request. (10894)
Cannot resolve method sl_Access parameter ns:piCustno (10933)e91a6247e9b693c3:-1b6d127:f811fed2db:-8000#17
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:846)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:359)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:387)
at $Proxy11.sl_Access(Unknown Source)
at com.ovid.service.AccessService.getRepl(AccessService.java:93)
at com.ovid.service.AccessService.processBatch(AccessService.java:71)
at Controller.runAccess(Controller.jws:399)

JAX-WS web service - "Cannot find dispatch method"

I'm getting the same error response every time I send a request to my JAX-WS web service:
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
   <faultcode>ns2:Client</faultcode>
   <faultstring>Cannot find dispatch method for {http://www.w3.org/2003/05/soap-envelope}Envelope</faultstring>
</ns2:Fault>I've tried using JAX-WS RI 2.1.7 and 2.2 on my Tomcat server, but both return the same error response. It will return the WSDL just fine (when "?wsdl" is appended to the endpoint URL). I used "wsimport" to generate the necessary Java classes from my WSDL--it used JAX-WS RI 2.1.6 (the one included with the JDK I guess) to generate the Java source files.
Other people online have had similar problems, but never with the SOAP element "{http://www.w3.org/2003/05/soap-envelope}Envelope", always with things specific to their WSDLs like "{}reqParams" or "{http://www.telekom.at/eai/WSToCramerCSIRead}CSIRead". I set a debug breakpoint at the start of my SIB method and it doesn't even get that far.
Any ideas? Thanks for your help.
WSDL:
<?xml version="1.0" encoding="utf-8"?>

<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ihe="urn:ihe:iti:xds-b:2007" xmlns:iherad="urn:ihe:rad:xdsi-b:2009" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
targetNamespace="urn:ihe:rad:xdsi-b:2009" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" name="ImagingDocumentSource">
<documentation>IHE XDS-I.b Imaging Document Source</documentation>
<types>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:ihe:iti:xds-b:2007"
      xmlns:ihe="urn:ihe:iti:xds-b:2007">
      
      <xsd:include schemaLocation="../schema/IHE/XDS.b_DocumentRepository.xsd"/>
    </xsd:schema>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:ihe:rad:xdsi-b:2009"
      xmlns:ihe="urn:ihe:iti:xds-b:2007"
      xmlns:iherad="urn:ihe:rad:xdsi-b:2009">
      
      <xsd:include schemaLocation="../schema/IHE/XDSI.b_ImagingDocumentSource.xsd"/>
    </xsd:schema>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
      xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/rs.xsd"/>
    </xsd:schema>
    
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
      xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/lcm.xsd"/>
    </xsd:schema>
   <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
      xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/rim.xsd"/>
    </xsd:schema>
</types>
<message name="RetrieveImagingDocumentSetRequest_Message">
    <documentation>Retrieve Imaging Document Set</documentation>
    <part name="body" element="iherad:RetrieveImagingDocumentSetRequest"/>
</message>
<message name="RetrieveDocumentSetResponse_Message">
    <documentation>Retrieve Document Set Response</documentation>
    <part name="body" element="ihe:RetrieveDocumentSetResponse"/>
</message>
<portType name="ImagingDocumentSource_PortType">
    <operation name="ImagingDocumentSource_RetrieveImagingDocumentSet">
      <input message="iherad:RetrieveImagingDocumentSetRequest_Message"
        wsaw:Action="urn:ihe:rad:xdsi-b:2009:RetrieveImagingDocumentSet"/>
      <output message="iherad:RetrieveDocumentSetResponse_Message"
        wsaw:Action="urn:ihe:iti:2007:RetrieveDocumentSetResponse"/>
    </operation>
</portType>
<binding name="ImagingDocumentSource_Binding" type="iherad:ImagingDocumentSource_PortType">
    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="ImagingDocumentSource_RetrieveImagingDocumentSet">
      <soap12:operation soapAction="urn:ihe:rad:xdsi-b:2009:RetrieveImagingDocumentSet"/>
      <input>
        <soap12:body use="literal"/>
      </input>
      <output>
        <soap12:body use="literal"/>
      </output>
    </operation>
</binding>
<service name="ImagingDocumentSource_Service">
    <port name="ImagingDocumentSource_Port_Soap12" binding="iherad:ImagingDocumentSource_Binding">
      <soap12:address location="http://localhost:8080/webservice-test/ridsService"/>
    </port>
</service>
</definitions>
Request:
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:urn="urn:ihe:rad:xdsi-b:2009"
xmlns:urn1="urn:ihe:iti:xds-b:2007"
xmlns:a="http://www.w3.org/2005/08/addressing">
   <soap:Header>
     <a:Action soap:mustUnderstand="1">urn:ihe:rad:2009:RetrieveImagingDocumentSet</a:Action>
     <a:MessageID>urn:uuid:0fbfdced-6c01-4d09-a110-2201afedaa02</a:MessageID>
     <a:ReplyTo soap:mustUnderstand="1">
          <a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
     </a:ReplyTo>
     <a:To>http://localhost:8080/webservice-test/ridsServer</a:To>
   </soap:Header>
   <soap:Body>
      <urn:RetrieveImagingDocumentSetRequest>
         
         <urn:StudyRequest studyInstanceUID="test1">
            
            <urn:SeriesRequest seriesInstanceUID="test2">
               
               <urn1:DocumentRequest>
                  
                  <urn1:HomeCommunityId>test3</urn1:HomeCommunityId>
                  <urn1:RepositoryUniqueId>test4</urn1:RepositoryUniqueId>
                  <urn1:DocumentUniqueId>test5</urn1:DocumentUniqueId>
               </urn1:DocumentRequest>
            </urn:SeriesRequest>
         </urn:StudyRequest>
         <urn:TransferSyntaxUIDList>
            
            <urn:TransferSyntaxUID>?</urn:TransferSyntaxUID>
         </urn:TransferSyntaxUIDList>
      </urn:RetrieveImagingDocumentSetRequest>
   </soap:Body>
</soap:Envelope>
Response (HTTP 500):
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
   <faultcode>ns2:Client</faultcode>
   <faultstring>Cannot find dispatch method for {http://www.w3.org/2003/05/soap-envelope}Envelope</faultstring>
</ns2:Fault>

I posted here to benefit anybody who is looking for a solution.
The solution is to use WebServiceContext to get ServletContext, then use ServletContext to get parameters defined in web.xml.
@Resource private WebServiceContext m_wsCxt;
Then in method
SOAPMessageContext soapCxt = (SOAPMessageContext) m_wsCxt.getMessageContext();
ServletContext servletCxt = (ServletContext) soapCxt.get(javax.xml.ws.handler.MessageContext.SERVLET_CONTEXT);
}

Web Service client running on Tomcat behind Apache-ModJk

Hi all.
I've realized a web service, which have been deployed on a Tomcat 5.5 instance running behind a firewall.
The Web Service is published through an Apache 2.0 Web Server, which is in the DMZ and which is connected to Tomcat via modjk.
Everything is working fine (as apache forwards to tomcat clients' calls), except from one thing: one of the web-methods needs to connect to a remote server to validate some data... that is, this web-method implements a "web service client" piece of code, by which a remote validating method must be called.
So, the problem is that this remote method must be accessed from something running behind the firewall...
One way could be to open a hole in the firewall, allowing only calls to that remote address, but I'd rather avoid this.
Do someone have other suggestions?
Is there perhaps any way to use mod_jk also for "exiting" and not only for "entering"?
Any help will be very appreciated!!

Could you not use a proxy server. The web service client would go through the proxy server to the internet

Accessing web service in run-time

Hello,
In the project I am currently working we have a component (Device Monitor) that needs to access other web services which contain the same interface (MonitorRemote). The webservices wit the MonitorRemote interface register in run-time giving their end-point, wsdl url and any other information that we may need.
My problem is to access these webservices in run-time. I have tried many approaches and nothing seems to work.
Currently I am creating 2 webservices with the same MonitorRemote remote interface but different name, service name and portName.
I try to execute the following:
1)String serviceName = method.getMethodName();
2)String portName= method.getPortName();
3)URL wsdlURL = new URL(method.getURL());
4)String namespaceURI = method.getNamespaceURI();
5)QName serviceQName = new QName(namespaceURI, serviceName);
6)QName portQName = new QName(namespaceURI, portName);
7)TimeoutMonitorService mtService = new TimeoutMonitorService(wsdlURL, serviceQName);
8)MonitorRemote monitoringRemote = mtService.getPort(portQName, MonitorRemote.class);
9)monitoringRemote.stopMonitoringFeature(0, 0);
Before the execution I test my TimeoutMonitorService with the webservice navigator and it works fine. After I execute line 9) the TimeoutMonitorService crashes giving the following message:
System exception
[EXCEPTION]
javax.ejb.EJBException: Exception raised from invocation of public void com.sap.sii.devicemonitor.DeviceMonitorBean.stopMonitoringFeature(com.sap.sii.devicemonitor.entities.ResourceMonitoringSettings) throws com.sap.sii.dataStructures.exceptions.IncorrectParameterException method on bean instance com.sap.sii.devicemonitor.DeviceMonitorBean@92f4d2 for bean sap.com/SII_device_monitor_EARannotation|SII_device_monitor_ejb.jarannotation|DeviceMonitorBean; nested exception is: javax.xml.ws.soap.SOAPFaultException: com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException
javax.xml.ws.soap.SOAPFaultException: com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException
at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.processFault(JAXWSUtil.java:341)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:984)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:700)
Afer the first time I receive this error I start getting many warining messages in the log files with the following message:
Exception occurred during open of configuration [apps/sap.com/SII_device_monitor_EAR/TimeoutMonitoringTaskService].
[EXCEPTION]
com.sap.engine.frame.core.configuration.ConfigurationLockedException: Can not lock Configuration "apps/sap.com/SII_device_monitor_EAR/TimeoutMonitoringTaskService" because it is already locked.
at com.sap.engine.core.configuration.impl.ServerEnvironment.lockConfiguration(ServerEnvironment.java:664)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:879)
I tried to remove and re-deploy but the webservice only returns this error message once I execute my code. The only work around is to create a new project with different interface names.
I am using:
SAP NetWeaver Developer Studio
SAP NetWeaver 7.1 SP05 PAT0000
Build id: 200802021401
Any help would be really appreciated.

need bit more info. from where you are trying to access this webservice? what is the wsdl you are using

Web services: cannot fint "Create a Web Reference Manually"

what's up guys,
I'm using Application Express 2.2.1.00.04 ..
I'm trying to manually create a web service reference. I read the manual and found this:
To create a manual Web reference:
* On the Application home page, click Shared Components.
* Under Logic, click Web Service References.
* Click Create.
* For Search UDDI, select No and click Next.
* From the Tasks list on the right, click the Create Web Reference Manually link.
* The Create/Edit Web Service page appears.
but I can't find "Create Web Reference Manually" in the tasks list..
please help me..
thanks in advance..

Thanks Jason,
you don't know how much time you saved me! :)
I guess I'll have to upload it somwhere then use the URL.
thanks again,
Abdullah

Web Service cannot be Started when we deploy war file in Tomcat

Hello every one,
We made a webservice in Netbeans 6. and we created the war file
and ist is workign fine with netbeans. when we tried to deploy to tomcat
it is showing error as given below:
**FAIL - Application at context path /WebApplication3 could not be started**
please help me to sort out this problem as early as possible.
Thanks in advance
Vishnu

Any one has any idea on this. I am stuck up with this. Help!
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by pragashj:
OS : Windows NT 4.0 SP 5
OAS : 4.0.8.2
Issue : Listner failed to start asking me to start OAS service first. But the OAS service is already started. When I tried starting the Listner service from Windows - Services (In control panel) still it failed. OAS Service though active does not show as active in the Service Control(This issue is listed in the Release note). The svwww.err gives oracle_adp_init returned ADI_FATALINIT.
Any one had the same issue? How do I work around to get my Web Listner started?
Thanks<HR></BLOCKQUOTE>
null

SOAP Responce cannot be decoded after during a long web service exection

I have an AIR application.
I am using the spark web service and i have set up a fualt handler and set the requestTimeout to 0.
I call an opertaion that calls a .Net web service.
Inside that .Net web service i run a very heafty SQL using ADO and then i take the results from the SQL statment and I use those results to make an excel spreadseeht and saved on the machine running the webservice.
This web service ran by itself can easily take up to two minutes to run (which is very acceptable given the nature of the query), and I would like the AIR application to just continue to sit there and wait for it to complete (also acceptable).
Even with the request timeout set 0 i receive a "SOAP Responce cannot be decoded" fault from the webservice before the web service is even done running. Why is this happening?
I've run several debuggers to make sure the info to the .Net web service is correct, I've stepped through the entire web service piece by piece and no exceptions are thrown during its execution. It just takes a long time to perform and the fault occurs right in the middle of the execution of web service.
I've also had this happen when i'm debugging some of my other web serivces. If a breakpoint is hit in visual studio in my webservice and i do my thing and step through stuff blah blah blah standard debugging stuff, the same thing will happen a fault will be hit before the webservice is done executing.
Please help.

I'm not sure what the deal is between Flex/AIR and Visusal Studios, but i descided to publish my webservices and point the wsdl there instead of using the visual studio generated one.
AND BEHOLD
I't worked and worked much much faster than i was anticipating.
So i'll just chalk it up to poor communication between FLEX and VS. But if anybody knows a more complete answer I would still love to hear it.

What about "write once, run everywhere" with web services ?

Hi all,
I'm very new to web services in Java (but not new at all in Java and not really new in web services).
I'm amazed of not finding a specification API for web services. It doesn't seem that I can write a web service (or a web service client) and run it under several "web services containers" (like we can do for servlets, JDO and pretty all java technologies). It seems - according to the tutorials I found yet - that if I want to make a web service that runs under Apache Axis, I must use org.apache.axis.* classes, and so on with WebLogic and other web services container...
It doesn't look like java style and I'm kind of confused...
could someone give me details ? am I wrong or something ?
TIA

I think is not that bad.
You have two APIs in the jwsdp tool just for web services (JAXRPC and JAXM) and you can construct your web services and your clientes wit that. Once you compile with the tool and you get the WSDL and the model I think that you can deploy it in any container (I think)
hope it hepls

Salutation web service cannot run

Similar Messages

Maybe you are looking for