I have SAP BTP trial account in which Im trying to run a SAPUI5 application via the SAP Business Application Studio (BAS). I have added nothing fancy to it. Just created one from the one of the many UI5 templates and tried running it from the terminal via the command ui5 serve.
The command does execute without any problems and also provides me with the standard localhost:8080 URL. Im using Firefox since BAS doesn't seem to work with Edge as well as Chrome.
I even get a message popping on the right bottom corner telling me a service is listening to port 8080 with a button that says "open in New Tab" pressing it however does nothing.
Im new to SAP BTP and BAS. Are there more things to configure before running the application? Or perhaps I have to configurate the browser itself? The error message:
I have also had some experience with the Business Application Studio.
You don't work locally here like in VS Code, for example. That's why you can't access it via localhost:8080, but have to use the link that provides the BAS. In this case, something like
port8080-workspaces-....applicationstudio.cloud.sap.
The best thing you can do is to press "Open in new tab" on the screenshot with "A service is listening to port 8080", then you will be redirected to the working link.
Kind regards
Sebastian
Related
Context
I am trying to run a solution. I did not create it and I cannot contact its creator (because it is some kind of exercise).
This solution has a React front-end running on API through Axios.
I do not know this type of stack very well.
Running the API through npm start, I get a 404 error when the API is called.
I'm not sure if and how npm start is supposed to be able to start a C# webservice at the same time as the React application.
So, maybe I'm going in a completely wrong direction at this point but,
I guess that I should launch the API from Visual Studio in parallel.
I know that I'm supposed to use local CosmosDBService to reach some database.
In the service appsettings.json, CosmosDB.Account and CosmosDB.Key are empty.
'CosmosDB' also has a CosmosDB.Content property (which looks like a long encrypted string). I expect that this is the database content (it should not be very big) stored in the JSON file, but I don't find much info about this precise property.
What I am trying right now is to connect the solution to the DB in Visual Studio through [Solution] > Connected Services > Azure Cosmos DB > Right click > Connect then in the dialog, I try to select Azure Cosmos DB Emulator on container (local)
(The other option is Azure Cosmos DB but I think that I need an Azure account for this.)
Docker is required to go further.
I install Docker (I'm on Windows 10). Docker requires something called something like WSL 2 Linux Services. I install WSL 2 Linux Services, but Docker keeps requiring it even after rebooting the whole system.
I read that an alternative way is use Hyper-V. I enable Hyper-V through Powershell. Reboot system. I uncheck WSL 2 in Docker. Reboot everything again. Docker now starts successfully.
Back in Visual Studio [Solution] > Connected Services > Azure Cosmos DB > Right click > Connect then in the dialog, I try to select Azure Cosmos DB Emulator on container (local). The 'Finish' button is greyed out, but the 'Next' button is active.
When I click on the 'Next' button, nothing happens... No error, not other dialog box, just no info and no clue at this point. And the current Dialog is not closing. Clicking on 'Next' literally does nothing.
Edit: I noticed that first time clicking on 'Next' after relaunching Visual Studio, for a very brief moment, the cursor display "Loading" start and something appears at the bottom left of that dialog box (it just says "Waiting" and then disappears).
Question
By reading the previous paragraphs, you may understand that I'm trying to run an application stack completely out of my "comfort zone". So I'm no asking for complete solution about this whole situation. (Though suggestions are welcome.)
The scope of my question here is limited to:
Why clicking on 'Next' is doing nothing? What am I missing? How can I diagnose this?
So I'm trying to make a website for school and I've been following this guys tutorial on how to make a website. But for some reason when I get to lesson 32 and I enter the ec2-user:~/environment/blog $ rails server -b $IP -p $PORT command, the website doesnt run and it says " somenumbersandletters.vfs.cloud9.us-east-2.amazonaws.com refused to connect " with an error. I've followed all the steps correctly (Except for the directory he runs it from, I run it straight from blog instead of environment because it tells me I need to make a new app the other way). I've tried disabling my firewall, I've enabled Cookies and searched the internet for a solution. I am very new to Servers and Coding and any help would be greatly appreciated!
This is my Terminal Log
Answer from https://www.reddit.com/r/aws/comments/cwnbt1/aws_cloud9_server_refuses_to_connect/
Once you start the rails server, click the 'preview' button. When this tells you that it refuses to connect, find the button that looks like two overlapping squares with an arrow to "pop out into a new window." Once it was in a new tab, it worked like a charm.
Hope this helps!
I ran into this issue as well. I could view my rails application when viewing it from within a new tab, but not within the Cloud 9 IDE tab.
If you look in the browser console when viewing through the tab, you will see this error:
Refused to display 'https://xxxxxxxxxxxxxxxxxxxxxxx.vfs.cloud9.xxxxxxxxxxx.amazonaws.com/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.
This error is being caused because you are viewing the rails application through an iFrame via the Cloud 9 IDE. By default to add security and hinder Cross Site Scripting (XSS) attacks, Rails sets SAMEORIGIN for the X-Fram-Options header. This will not allow the rails app to be visible in the Cloud 9 IDE tab using the iFrame.
In order to bypass this, you will need to set this header to use ALLOWALL instead.
NOTE: Only do this within your development environment and never in a production environment. This could open your site up to XSS attacks.
Add the following configuration option to your config/environments/development.rb file:
config.action_dispatch.default_headers = {
'X-Frame-Options' => 'ALLOWALL'
}
After saving the changes, restart your rails server and the application should now be visible within the Cloud 9 IDE tab directly.
I tried to deploy a simple hello world application on Micro Cloud Foundry. I went through the process that mentioned in video and set up every thing (My IDE is STS eclipse and Windows 7). When I wanted to make a server on Micro Cloud Foundry: 1) I could not set my server host name to my domain for example "multisite.cloudfoundry.me" it said "The currently selected server type does not support remote hosts" and forced me to put "localhost" as the server name. 2) When I went through the process it started my Grails application and seemed it was running well but the url was broken "http://12431asd.multisite.cloudfoundry.me/" (It asked me for Grails app on this domain I choose "12431asd") and I got the message "VCAP ROUTER: 404 - DESTINATION NOT FOUND". when I tried this url "http://api.multisite.cloudfoundry.me/" I get the message "Welcome to VMware's Cloud Application Platform".
I appreciate any help and suggestions.
Reza
When you add a CloudFoundry server leave the first pane with the default settings and then on the second pane select the "Microcloud" url option setting the name to "multisite" in the popup dialog. Once the plugin has contacted your instance you can go ahead and put the email and the password in.
From there you should just be able to deploy by dragging the application to the server instance in your servers tab, setting the url in the dialog that follows. Once deployed you can double-click the application instance in the server tab and adjust its properties.
Can you verify that when you deployed the application, it's state was started? (it should say next to the application name under the server)
im trying to host my website developed in ASP.net4.0 in Ultidev's casini webserver 2.0.
bt when i try to host the same or click on http::/localhost:port, im getting following error.
Utidev webserver's windows service not running.
I dont hav clue on the windows service it's expecting.
Do i need to install any other dependencies ?
Please look at the error pic.
Please help me in this regard.
Thanks.
The host process for that application, DefaultSharedHostProcess, is having trouble starting. Look in the Windows Event Log, as well as "UWS.Installer.log.txt", "RegRepairTrace.txt" and "AppRegTrace.txt" files in the "%ProgramFiles%\UltiDev\Web Server" folder.
As there are a variety of circumstances which can lead to this error, you will need to edit your question and add in the relevant error details you discover from the logs, or go start a thread on UltiDev's support forum. For instance, I encountered this error because of a permissions issue to machine.config in a .NET 4 folder.
Ran into this today, and found if I recycle the host process, I was up and running.
In the UltiDev Web Server Explorer window on the left side, click on the Default Shared Host Process.
On the right side, you'll see a button named "Recycle Host Process". Click it, and answer Yes.
After this, the Windows Service started up, and I was able to communicate with my web app.
I'm working on a project that must connect to a asmx page.
But, it throws an exception 'Endpoint not found', but I configured all my app, set all the endpoints configurations in app.config. I've tried to connect to localhost and it works.
I've also tried something like disable firewall...
What could it be? Must it have something to port configuration?
Thanks!
Is this a deployed app, or are you running in debug mode from Visual Studio? In visual studio debug mode, you will have to set your endpoint addresses to include whatever port # the webservice starts on when you click "run" in VS (it should popup in your notifications tray). Then when you publish the project later, you will have to remember to change these endpoints back to not include the port #... That's the only thing I can think of that has tripped me up in the past. If that's not it- good luck.