Web application is seemingly not running when deployed in websphere - websphere

I have a war file which I deployed and ran in tomcat. Then I deployed it in websphere from admin console. The status of the webapplication is seen as started along with the built-in web applications such as "ivtApp", "query", etc. Now from this link:
Heading
http://pic.dhe.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Finfo%2Fae%2Fae%2Frins_portnumber.html
It looks like the port number for web application is 9080 for http. I tried to run the application using the link:
http://{localhost}:9080/spring3HibernateMaven/index
(I am using "{" because this website didn't allow typing localhost)
the context root being spring3HibernateMaven. And I get page not found error in the browser. So I thought there must be something wrong with my web application. Hence I tried to run their web application:
http://{localhost}:9080/ivtApp
Which gives the same error. Even
http://{localhost}:9080/
gives the same error. I assume it should show something for this url as is shown from tomcat.
So how can I run the/any web application in websphere? FYI, I downloaded the latest version of websphere from their website.
Thanks

ivtApp has context path "ivt", so you need to use host:9080/ivt
Btw, you can find context path setting in websphere\application control panel

Related

IIS Express Web API and multiple projects

-My Web API project running in its own project is fine.
-Trying to run my Web API project from within a solution which contains another web project I get the following suggestion given its 'forbidden'
1. Go to the IIS Express install directory.
2. Run appcmd set config /section:system.webServer/directoryBrowse /enabled:true to enable directory browsing at the server level.
3. Run appcmd set config ["SITE_NAME"] /section:system.webServer/directoryBrowse /enabled:true to enable directory browsing at the site level.
The first appcmd suggestion works fine, the second does not. I believe the reason is because my site name does not exist in iis Express until it runs or I am doing something else wrong.
This leads to the last question.
-Can I even have a Web API project running while another web project in the same solution consumes its methods. I assume the answer is no.
In fact I assume that if I want to have a web application consume the methods of this Web API application I am going to have to install a proper IIS stand alone.

JDeveloper - change the target URL when running with the internal OC4J container

I'm trying to set up JDeveloper for development on an internal terminal server. When I run a newly created webpage using the internal OC4J container, my browser opens looking at page http://hostname.domain:8988/OA_HTML/runregion.jsp.
For reasons out of my control, the DNS server won't resolve hostname.domain for me. In production, this won't be an issue, but for testing, having to deploy and test on the full dev instance every time is a problem.
Is there a way to tell Jdeveloper to use 127.0.0.1 for the testing URL rather than hostname.domain?
you can change it in the "properties" of the "IntegratedWebLogic"

Websphere Application Server 7 - Redirecting HTTPS request to HTTP

I'm facing some problems with my WAS setup. The HTTPS link is redirecting to an HTTP. I am sure this is not an application issue since I tested the same application on other environments and it is working.
I had copied the virtual host configuration from the environment that is working, but still not getting it to work. I checked the other environments's Web Container Customer Properties and it does not have any.
Any thing that needs to be checked?
Update :
I saw below the virtual host there is a link called "Update global Web server plug-in configuration". Do I need to click this and copy the generated file to all nodes?

Service in Silverlight application does not work when deployed

I've created a Silverlight application that uses a service. The service is defined in the web project in that solution. The silverlight application references it and uses it.
Everything works locally on my dev machine when I run the application in Visual Studio.
I note that the url im given from VS is: http://localhost:50453/Default.htm
But when I deploy this (by filesystem copy deploy option) the web page starts and it looks okey except that it seems to have a problem using the service.
In the Silverlight application, if I look at the reference settings the url to the service is: http://localhost:50453/SilverlightService.svc and thats probably whats wrong, as the server that Im deploying to does not have a clue whats on port 50453.
So Im trying to change this port to 80 on my dev machine but Im out of luck. My web project does not have any property where I can change the port. Opened URL and URL is locked at http://localhost:50453 :-/
How can I change the my dev environment to match the production environment with port 80?
For sure you can change the web project's URL in project properties, but this is not a good solution because you'll get the same problems when accessing the SL application from a remote computer.
You need to set the service URL programmatically, like above:
ServiceReference1.Service1Client svc = new ServiceReference1.Service1Client();
Uri serviceUri = new Uri(System.Windows.Browser.HtmlPage.Document.DocumentUri, "Service1.svc");
svc.Endpoint.Address = new System.ServiceModel.EndpointAddress(serviceUri);
This solution uses the same URL that you are using to access the Silverlight Application.

IBM Worklight - Can't open localhost:8080/console in browser

I want to preview my Worklight app in my browser, but when I open localhost:8080/console in the browser this error appears:
HTTP Status 404 - /console
type Status report
message /console
description The requested resource (/console) is not available.
Apache Tomcat/7.0.21
You are missing the context root in the URL. It should be: http://localhost:8080/your-context-root/console.
The value of the context root is usually the name of the .war file - the name of your project. Try that.
Tip: also make sure you have set it in both worklight.properties and application-descriptor.xml, otherwise your application will fail to connect to the server, now that you have moved from Eclipse to an application server.
Some topics of worth from the IBM Worklight Information Center:
Transporting Worklight applications to test and production environments
Deploying a customization .war file to an application server

Resources