I am quite new on web services and asp.net too. I created .net web service and deployed it on IIS. My web service takes some data from android and does some manipulation and store it in text files. Because I am working with localhost so there is no issue with storing data in text files. But now I am publishing this web service to azure portal now I am confused where my data will be stored? should I changed the path ? or what I have to do?
Local file system on azure cloud service may change so your data may be lost. Better to have the blob storage for storing file. https://www.simple-talk.com/cloud/cloud-data/an-introduction-to-windows-azure-blob-storage-/
Related
I was playing with google cloud just for the sake of learning cloud and web applications.
I made an application using
1)Front end (html,CSS, javascript)
2)Database( sqlite)
3)Middleware(Python Flask)
I have the application running on my local system .I have a flask service running to collect and write data to my DB, an API interface(using flask) to read from the DB and the web application that uses this API to display graphs.
Now I want to host this in google cloud. If i do that I will have the web application running on a port. But will i be able to access that from outside. Is there any way to do that?
That's definitely possible, looks like you should give Google App Engine a try
I have a list of ML experiments which I have created in Azure Machine Learning Studio. I have deployed them as web services (the new version, not classic).
How can I go into Azure Machine Learning Web Services, click on a web service (which was deployed from an experiment), then navigate back to the experiment / predictive model which feeds it?
The only link I can find between the two is by updating the web service from the predictive experiment, which then confirms what the web service is. I can see that the "ExperimentId" is a GUID in the URL when in the experiment and the web service, so hopefully this is possible.
My reasoning is that relying on matching naming conventions, etc., to select the appropriate model to update is subject to human error.
The new web service does not store any information about the experiment or workspace that was deployed (not all new web services are deployed from an experiment).
Here are the options available to track the relationship between the experiment and a new web service.
last deployment
However, the experiment keeps track of the last new web service that was deployed from the experiment. each deployment to a new web service overwrites this value.
The value is stored in the experiment graph. One way to get the graph is to use the powershell module amlps
Export-AmlExperimentGraph -ExperimentId <Experiment Id> -OutputFile e.json
e.json
{
"ExperimentId":"<Experiment Id>",
// . . .
"WebService":{
// . . .
"ArmWebServiceId":"<Arm Id>"
},
// . . .
}
azure resource tags
The tags feature for Azure resources is supported by the new web services. Setting a tag on the web service programmatically, with powershell or via the azure portal UX can be used to store a reference to the experiment on the new web service.
I have been working with Azure's web app service using Resource Manager to deploy a Django app. It has been working in fits and starts. I really like the auto-deployment from GitHub but I have been frustrated by the ability to work with the underlying machine. There is a "Console" tool through the Azure portal but it has limited functionality and when there is an internal server error on my app, I can't find the server output log.
Can someone share insight into how to view the server logs?
Azure web apps have a number of logs however, the applications logs provided out of the box only support Asp.Net applications. That being said there is an article about django on web apps and how to store and view its logs here.
What'll you'll have to do, as described in the link, is to setup the django application to store its logs on the azure file system. Another option is to setup the django application to email the devs but the better option is to store the logs on the file system properly.
I am using Axis2 (1.5.3 currently) and Tomcat (6.0.26 currently) and am running a web service. I would like to also host HTML pages for configuring the web service.
What is the best way to go about this? I assume keeping the same context is key, but perhaps it is not.
My current distribution is located under a folder structure similar to this:
Tomcat/webapps/mycompany
With the actual service code here:
Tomcat/webapps/mycompany/WEB-INF/services/myService
In a browser, I can hit my web service by going to here:
/mycompany/services/myService
I note that I can drop actual HTML files in this path and Tomcat will, indeed serve them up.
For instance, if I put "index.html" under Tomcat/webapps/mycompany, I can navigate to /mycompany/index.html and see my html.
What I want to do is have this HTML be attached to JAR/class files that can interact with the already-existing service class files in the same context as the service. Therefore, I can have the browser configure the web service directly.
Is this possible, and is there a tutorial or something out there that will help me with this? Note that I have been working with Tomcat and Axis2 for a while now for this particular web service, but I have never actually deployed a web application/html using Tomcat before.
Thanks.
First of all what do you mean by a configuring a service. Normally in SOA world services are analogous to interfaces. IMHO you can just change a service, since their are other users that rely on the services you are exposing.
If i want to change a service i would rather introduce a new version of the service after deprecating the existing one.
Are you talking about applying QoS to existing serviecs. Then that makes sense.
Anyway, If you want to have a web-app alongside with axis2 service engine, it is possible. If you look inside the axis2 war file you'll find the web.xml entry to Axis2Servlet. It is this servlet that serves the web services requests.
So, what you need is the Axis2Servlet mapping in your web-app along with your usual servlet-mappings. Number of possible ways to configure your services using web-app files. One options is to use web-services call itself to (with authentication) to configure it.
By "configure a service", take this example:
The service has a set of datasets.
Each dataset exists in a separate database.
The service can manage 0..n datasets.
The service must be configured to know about each dataset.
This is what I'm configuring. I'm not trying to configure Axis itself or redefine the service.
I would like to host the HTML using the same instance of Tomcat that I'm hosting the web service with. It needs to manage sessions, have login capability, an whatnot, and has to be able to configure the web service live.
From what I'm reading, it's probably best to make an interface to the web service that the web application module can call into from a different context.
Is there a better way?
I have created a Web Service in Net Beans 6.9 and deploy it locally. And I am using it via a java SE application by adding Web Service client in this application. How to obtain the link of the Web Serice so that it can be used from anywhere ?
2) From where to obtain WSDL file of Web Service ?
3) How to host a Web Service on the internet ?
Thank a ton in advance..!!!
You could create a new project of type web application in Netbeans.
In the web application, you will then create a web service (NOT a web service client).
For publishing and testing the web application, you will have to deploy it to a web server (e.g. GlassFish).
After publishing the web application, the WSDL file will be typically located at: http://localhost:<port>/<your web app>/<your service>?wsdl
For GlassFish, the default port is 8080.
If your current Netbeans installation doesn't support web projects or you don't have GlassFish installed, I suggest you download and install the latest version of Netbeans with Java EE support (bundled Apache Tomcat and GlassFish server in the same setup).
http://netbeans.org/downloads/index.html
Hosting SOAP web services on the internet at large has not been terribly successful. For example Google had SOAP based web services initially, and they switched to REST based services in the end. You may want to reconsider and deploy a REST based interface. If the bulk of your code is not embedded in the web service, then you should not have that difficult of a time switching the interface.
To deploy a SOAP or a REST web service, you would need to deploy a 'full' Java EE container (e.g. Glassfissh or JBoss) on a machine with access to the internet. You might virtual hosting e.g. Westhost, Amazon, or there are turnkey solutions like Heroku (note: I'm not endorsing any of the companies listed here; they're just examples). If you just want to deploy a REST based service, any web container will do e.g. Tomcat or Jetty. In addition to services mentioned above you could probably host a rest web service on any service that will let you upload a war file.