Need Suggestion on the below implementation in SiebelOpenUI - siebel

In our implementation Siebel has been listening to the signalR hub and getting the values whenever it is posted in the server.
But now as the Dotnet SignalR Server is running on JSON supporting files, Siebel is also in need to refer the JSON files to receive the values from server.
Please suggest how we can refer a JSON file from Siebel.
Below are the js files Siebel is referring as of now.
jquery.signalR-2.0.3.min.js
jquery-1.6.4.min.js
we have the following Json files that SignalServer is referring to in dotnet:
Microsoft.AspNet.SignalR.Core.dll
Microsoft.AspNet.SignalR.Core.xml
Newtonsoft.Json.dll
Newtonsoft.Json.xml
My question is can we use the same Xml files mentioned above in Siebel to refer or is there any other approach to achieve the referring part.

I came to know from Siebel team here that it's not doable right now for some reason i don't know why. excuse me I'm not a Siebel resource.
And I called the send method in the SignalR server i created in c# Asp.net from my SignalR VB Client.
Siebel is listening to the Asp.net SignalR server and successfully receiving the input values now from the SignalR Client.

Related

Creating a New Web Service Consumer Domino

I am trying to import a WSDL in to my Domino Designer 9.0.1 client. I have downloaded the WSDL file and specify it in the Local File part of the wizard.
I click OK and get the error
"The requested operation failed. Server redirected too many times (20)"
I have imported other WSDL's without a problem and the only difference with the one I now need, is that I need to login to see the WSDL.
Does this stop the wizard?
If so, is the only option writing the java agent from scratch to access the data?
Obviously I cannot provide the actual wsdl I am trying to attach to as it is a paid service, so not sure what other information I can provide to help find a solution.
Thanks
Graeme

Does the existence of a .wsdl file mean files must be generated?

When I'm tasked with dealing with connecting to web services, I've always found the appropriate .wsdl file, ran WSDL2Java.bat, and incorporated those Java files into my Java project. Then I've successfully completed my project that needs to access data via web services.
My question is, are there other ways to use the .wsdl file to access web services? ( I'm not talking about creating classes for different languages ). For example, I have documentation describing one company's web services. The examples it shows in it's documentation are essentially dumps of HTTP Post requests. Is this "web services"? It looks to me that the .wsdl file is merely used as a reference to make the correct Post requests. I could just make text templates and plug in the right values, and send them out, right? I really feel like I'm missing something here.
Am I a web-services illiterati?
To call a SOAP web service over HTTP you just need to send it a properly formatted XML with a POST request. That's it! How you build the request is irrelevant as long as it conforms to the SOAP protocol and the payload corresponds to a proper web service operation that exists on the particular web service you are calling.
But how do you know how to build the proper payload?
The web service needs to have some sort of documentation otherwise you don't know what to put inside the XML. The documentation can be whatever you like as long as people can use it to build valid requests. WSDL fits this criteria but has an extra advantage: you can feed it to a tool that generates code. That code knows how to handle all the SOAP details and exposes objects and methods to your application.
What would you prefer? Generating code from the WSDL in a few minutes and be able to call whatever operation on the web service or, build the requests and parse the responses by hand and spend hours or days doing so. What would your boss or company prefer? :)
It looks to me that the .wsdl file is merely used as a reference to make the correct Post requests. I could just make text templates and plug in the right values, and send them out, right?
Right! But you also have to consider your productivity as an employee in one case as opposed to the other.

SOAP Web Service basics

am new on WS.
some simple questions in my mind, please try to solve it.
i did a demo WS for Calculator on calculator(), where it has one UI where i enter values for it, internally pass it to WS. Ok i got answer/output. but if i want to create only webservice which take/give xml data or just give xml data. how can i create it.
i found some WS URL's about some fame company. is it used by using by opening Connection. how they define this URL? am using MyEclipse10 when i went to create new WS, needed to use Java Bean class for create it. ok, if i create myWS url then how it ll get call? because it is JavaBean?
and if just want to create WS then i need not required to create New WS client?
i dont know it is simple or may be foolish question, when i walk on WS i stop here. i feel like , without basic knowledge started to build it.
please, clear it.
Thanx.
MyEclipse (as well as Eclipse, IBM D Developer, etc) let you create a Java Web service server in one of two ways:
Bottom up Java Bean: you supply a bean, it turns it into a WSDL (and generates the corresponding stub code)
Top down WSDL: you supply a WSDL, and it generates the corresponding stub code
When a company creates a web page, they set up a web server and publish some HTML pages on it.
When a company publishes a WSDL, they also set up a web server ... and publish an XML WSDL on it.
The URL you go to in order to read a WSDL is just an ordinary HTTP web server, that happens to be serving an XML WSDL at that location.
The WSDL specifies where the service can be found, and what operations and data types the service uses. A WSDL you create, or a WSDL that's published by some other company.
'Hope that helps

WebServices client in java?

I would like have a solution for creating a WebServices client and it needs to consume the Services which already existed.
I have code this from Netbeans ide but my requirement is the wsdl url must be a dynamic one and more specific it needs to fetch from .xml,please suggest me to do that dynamic..cheers
If you are building a Java EE application you can create a web service client in Netbeans. Otherwise you need to code it on your own or use a external tool or library.
You need to parse the XML and read the WSDL URL from it, you can find in the net for how to read the data from the XML
Once done,using the URL you got from the XML you can call the service endpoint (The code you have already)

How to deploy an Axis-generated soap service to an embedded Tomcat instance

I generated a Soap Service from a WSDL and now I need to deploy it to my existing application which uses embedded tomcat (I.E. I have a class which extends TomcatServeletContainer and a main class which instantiates that class and starts the server).
I see many examples for how to deploy an axis service to a standalone tomcat using a WAR, or a WSDD, but I don't see how to wire it together myself. I assume I have to define a servelet in the web.xml and provide some other glue. Any assistance or pointers to appropriate documentation would be most appreciated.
Thanks!
-Carl
Have you been able to get this to work?
I've been trying to build a webservice (in a standalone war-file containing the axis jars (w/dependencies)+server-config.wsdd) using maven. I really don't want to make any calls to the AdminClient at all (meaning not to install Axis).
I've generated the server side sources from a WSDL using the axistools-maven-plugin, and everything seems to work ok until I have deployed the service. http://localhost:8080/myApp/services gives me the name of the service and two exposed methods. But clicking the wsdl link displays an Axis error message telling me "Could not generate WSDL! There is no SOAP service at this location".
Is it at all possible to build a standalone Axis webservice this way using maven?
Yes, you will need build your application the same way you would for a WAR but programmatically inform tomcat where you exploded war lives.
Everything else should be the same as the standard servlet spec.