how to access the application deployed in openshift3 (wildfly server) - docker

I have deployed the application in my local wildfly server and able to access my application through the url (http://127.0.0.1:8080/dhana/.
I have deployed the same application in openshift3 starter (new) and the build & deployment is successful.
It showing me the service url as ( http://dhanabalan-dhana.a3c1.starter-us-west-1.openshiftapps.com), But when I tried to hit this link it shows as below
Looks like server is up and running, Can anyone guide me to access the application?
Do I need to specify any port (8080) here?
Note: ROOT.war is the deployed file

Related

Rasa chat bot deployed on Heroku not responding to chat, only working on localhost 127.0.0.1:5000

I have created a rasa chat bot that is working properly on my system. chat response below
But when I deployed It on the Heroku the bot is not responding. chat responses below
Here is my code link GitHub code repository and Heroku deployed app link
Heroku link
Can anyone tell me what is problem with this?
I have used docker image to manage dependencies but I think my model is not properly deployed. I want to get an answer from the model.
Your project relies on 2 open ports. This is not possible with Heroku because your webbrowser clients make a connection with your flask app in the browser and have to send API calls to your rasa action server.
1 port is used for the rasa action server.
1 port is used for your flask app.
Your rasa action server declared in start_services.sh is never started.
Put your rasa action server in a separate Heroku app. Point the API endpoint calls of your flask app to that new Heroku app.

How do i deploy a blazor docker container application to multiple environments?

I've got a blazor server and client side application that is deployed into a docker container. I have multiple appsettings.json files. Each file should be deployed with its corresponding environment
I've seen some discussions which assert that the ASPNETCORE_ENVIRONMENT needs to be set for the server side application, which would automatically set the same value for the client side application. I've tried this. However, it seems that for the dev environment example, the appsettings.json file is still being used. I get a sign in error on the deployed dev environment which indicates that it's still using the appsettings.json file.
thanks
This was happening because we incorrectly set the ASPNETCORE_ENVIRONMENT correctly in the server application. Once we did that, it worked.

openshift wso2api manager redirect error

I am currently trying to setup wso2 api manager on openshift. The problem i am running into is that when i try to browse the url created by the openshift route, the application redirects me to the internally created IP address of the publisher app. However when i launch the container without openshift, the application directs me to it's intended API login page which is the Mgt console url.
I suspect this has to do with how the HAProxy embedded load balancer is behaving. I was able to hack around the configurations by changing the default ports to 443 however that created a new set of issues because changing the ports also required me hard coding container hostnames in the carbon.xml. Hardcoding settings in the configuration files prevents me from being able to scale up the containers.
Any assistance on this will be much appreciated.

Deployed application not showing up in websphere application server 8.5 after successful deployment using Jenkins

I am using websphere deployer plugin to deploy application to my local WAS server. Jenkins gives a success message after deployment but the deployed application is not present on the server.
Can anyone suggest how to deal with this. I did this deployment for tomcat and that works fine for me but on WAS server it seems like file not getting correct path. I am new to WAS server. Need suggestions.

ASP.NET MVC Deployment Referencing Development Environment

I am trying to deploy my ASP.NET MVC 3 application using Visual Studio 2010's "Publish Web" option (build/Publish App). This generates deployment/bin, deployment/scripts, deployment/views etc.
I loaded these resulting deployment files/folders to a web server running IIS 6. Afterwards, everything seemed to run just fine on this web server.
I then started to make new updates, just to my local environment. After doing that, the deployed version of the site stopped working. I looked at the stack trace and the web server seemed to be referencing controllers.cs from my local environment, as opposed to the dll's in the bin directory on the web server.
Is there something else I need to do before deployment to tell the web server to use it's own bin files as opposed to files on my development environment?
BTW both my development machine and the web server live on the same network.
Update:
Another thing that made me suspect that the web server was referencing my local dev environment was that when a new user tried to access the application she got an IOFileNotFoundException in regards to a reference to "Interop.ActiveDs.dll". The stack trace mentioned my_local_path/Interop.ActiveDs.dll. This file was in fact not on the web server so I added it and then her error went away. The Odd thing was that all other users before her did not recieve an error about this missing reference.

Resources