Deploying web application in SUP2.0 - sup

I have deployed my web application in the folder
C:\Sybase\UnwiredPlatform\Servers\UnwiredServer\deploy\webapps
of SUP server. I have stoped and restarted the server. But it is not working.
i have also checked the server error log file it is not showing any error.
I have tested the same in tomcat server 6.0 it is working fine.
I am new in SUP2.0 environment. Please help me in deploying web application also let me know if i am following the right procedure..
thanks in advance
Pratap Kumar Panda

The suggested way to deploy a webapp is though Eclipse. (with the sybase plugin installed)
See these series of tutorials
http://www.youtube.com/watch?v=ls-swn433g0

Related

How to host a Blazor ServerSide app on a VPS

I'm experimenting with the Blazor Server App and want to host it on my own VPS. I followed about every official documentation there is, but I can't get it to work.
VPS info:
Runs on Hostinger -> Ubuntu 18.04 64bit with Webmin
Installed all required dotnet versions on VPS:
When creating a test index.html and place it inside var\www\html\ it can be accessed through a browser and the content is shown
Blazor Server App info:
Start a new project > Blazor Server App > Publish > Local folder
Copy files from bin\release\netcoreapp3.1\publish* into VPS\var\www\html\
The files can be seen when browsing, but nothing executes
What am I missing here? How can what I want to do be done?
I was expecting the application to run, just like it did when executing it in Visual Studio.
I followed this tutorial based on a similar question
https://www.jeremymorgan.com/blog/linux/blazor-in-linux/, but I'm not using CentOS so it did not help much.

ASP.NET Core 6 site work with kestrel not with IIS or IIS Express (503)

I'm working on an ASP.NET Core 6 site and I usually use kestrel to run and debug the application. Today I've deployed the app to IIS but after one or two requests IIS stop responding and only return
HTTP Error 503.0 - Server has been shutdown
Same behaviour with IIS Express. Everything works fine with kestrel.
I don't know how to debug the problem, I've attached the debug but with no luck. I've also looked at stdout log but nothing appears.
Does anybody have any suggestions on how to debug the issue ?
Please follow my step to collect the dump files. And if want analyze the dump files you can create a new post and ask for help. This answer just tell you how to debug issue.
First Way
Remote debug with visual studio 2022
Deploy your app to IIS.
Run your VS2022 with administrator and attach the process.
Reproduce the issue to check the issue.
Second Way:
Collect dump files
If the first method can't reproduce or debug the issue.
You can follow below steps to collect the dump.
Download and install Debug Diagnostic Tool v2 Update 3.1
Deploy your webapp in IIS
Set rules to collect dumps by using DebugDiag or Collect dumps manually

Azure App Service Application Insights Not showing sql command text in dependency

I have a web app (.Net 4.6.2) running on an Azure App Service with Application Insights. I'm using SQL Azure as a back end. When Application Insights logs sql dependencies, the command text isn't included, just the server name and the database name shows up under 'Command'
I've uninstalled and reinstalled the extension and seem to have exhausted online sources. Can anybody suggest where else I look for a solution?
Is this how you install the extension? (Just double checking) And you tried removing/adding back the extension?
Also - does you application refer to SDK in source code already? (via nuget)

Re: Enterprise edition of our iPad app not downloading

We have created an enterprise edition of our iPad app. and we were using it since last 15 days. but url suddenly stopped working. we are not able to install application now.
Error: "There is no application set to open the URL itms-services://?action=download-manifest&url=index.php%3Fplist%3DMyApp".
Earlier it was working fine, i din't change anything to my side.
Please help me out guys.
Thanks in advanced.
One thing to check is that the app is hosted on a server that gives the .ipa the correct MIME type, which should be "application/octet-stream." Any changes in your hosting server?
I've been in a situation where a Microsoft IIS server was not set properly and was screwing me up.

WCF Azure 403 error when running locally

I'm stumped. There are several threads out there that reference a similar problem, but not the same one. I'm trying to get a simple WCF service up and running in Azure, but my problem is happening before I even deploy. I'm following this article:
https://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-create-deploy/
Which says to create your project, build the "Hello World" service interface and class, and then start your project locally. I get a 403 error when I try to start my project.
The only step I'm not following exactly is that I don't have a "Start Without Debugging" option (I'm using Visual Studio Express Web Developer), so I just push "Start Debugging."
Why would I get a 403 error on my own machine? I am running Visual Studio as Administrator.
On the WebRole project right click on your .svc (Service1.svc) and choose "Set As Start Page" And then run the project. Make sure to do this on the WebRole project not the Azure Cloude Project.
Is the Azure project the default project or is the WCF Web Role? If it's the role itself, that may be your issue - it's trying to access the root of virtual directory containing the web service versus running the cloud app in the local emulator. If you browse to http://127.0.0.1:81/Service1.svc in a new browser window do you still get the 403?
It seems VS has lost the its project settings. Bring up "Properties" page on the web service in VS. Go to the "Debug" tab. Under Servers/Virtual Path: my configuration was set to just "/". Put the name of your server back in there "/Service1.svc" and it should work from the debugger now. This fixed the problem for me.
The problem went away when I upgraded to VS 2010 Pro. I never fixed it on Express, but after upgrading the problem was gone ... I had the "Start without Debugging" option in the Pro edition, so I suspect that the problem may have been specific to Express.