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
Related
I don't understand why I get the error in the title of this post.
I have a Website running its own Application Pool in .NET V4.0.
Under the Website I have an Application running on its own Application Pool in "No Managed Code" as its a C# .NET 5.0 REST Web API. The Application points to a different physical location on the Server than the Website.
Why am I getting the following error when I navigate to the desired URL:
403.18 - Forbidden The specified request cannot be processed in the application pool that is configured for this resource on the Web server.
When I try to call my REST service from POSTMAN using the correct URL I receive the following response from my server:
<TITLE>403 Forbidden</TITLE>
<BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![endif]-->
</HEAD>
<BODY>
<H1>Forbidden</H1>
You do not have permission to access this document.
I have set the folder permissions correctly however, I'm still receiving this error.
There are many reasons for 403.18 error:
An ISAPI filter or custom module changed the URL to run in a
different application pool than the original URL.
An ISAPI extension (or custom module) used ExecuteURL (or
ExecuteRequest) to run in a different application pool than the
original URL.
You have a custom error page that is located in one application pool
but is referenced by a Web site in another application pool. When the
URL is processed, it is determined by IIS that that it should have
been processed in the first application pool, not the other pool.
The Web site has multiple applications configured. The application
this request is configured to run in is set to run in an application
pool that does not exist.
Things you can try:
If you have an application that is trying to process a URL in another
application pool (such as trying to process a custom error), ensure
that they both run in the same application pool if appropriate.
If you are trying to process a custom error URL that is located in
another application pool, enable the custom errors Redirect feature.
Verify that the application pool for the application exists.
Create a tracing rule to track failed requests for this HTTP status
code and see if ExecuteURL is being called.
For me a folder on my one virtual app was missing the dot net standard DLL. If the answer above doesn't resolve things it might be a good idea to beyond compare directories between the busted ENV and a working one.
I am using WebSphere Developer Tools for Eclipse on Mars SR1. I am trying to republish my application on a remote WebSphere 8.5 server. I am running into a SSLHandshakeException error when I try to do an incremental publish.
A "Problem Occurred" dialog pops up with the following details:
The publish encountered some problems and the application may not have
been installed or it may have been successfully installed but was
unable to start. Removal of the following application is completed:
WebAppEAR Removal of the following application is completed:
WebAppEAR Failure uploading archive to server: Upload retry limit
exceeded for file
C:\Users\Administrator\workspace.metadata.plugins\com.ibm.etools.wrd.websphere.core\tmp1455916474993\TestEAR.ear.
Exception: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h:
PKIX path building failed:
java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl
could not build a valid CertPath.;
The only way I can republish my application is to remove it from the server and re-add it.
This is currently a known problem with using WebSphere Application Server on Eclipse Mars with WebSphere Developer Tools. The technote below explains what's causing this problem and a few ways work around it.
IBM Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21976357
Essentially, in Mars SR1 an EPP logging plugin was added, which conflicts with WebSphere Developer Tools. This affects the republishing on WAS V7, V8 and V85 using a secure profile with non-loose configuration (Run server with resources on Server). This includes remote servers, which always run with non-loose configuration and local servers that have that option enabled.
If you choose to disable the EPP logging plugin, please refer to the link below for the latest updates. Also, for those who are using Mars v2 now, please be aware the VM argument has changed slightly after Aeri v2 was introduced.
https://wiki.eclipse.org/EPP/Logging
Also, if you are using an existing workspace and the plugin wasn't disabled, you will have to delete the plugin directory manually. The folder is called "org.eclipse.epp.logging.aeri.ide.server" and it is located here: "workspace/.metadata/.plugins/".
It happens to me whenever I use add or remove projects option to remove the projects and add it back again. When we remove the project from server using eclipse sometimes it won't get remove from actual server. So when we add back again we get this exception. So make sure the project is uninstalled from server admin console when you remove it from server. If it is not, then uninstall forcefully from admin console.
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?
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
i've got one issue with Websphere Portal application. The situation is when we removed one uploaded image file of Portal application from WAS intsalledApps folder path directly, that file would be regenerated by itself after we restart Websphere Portal application server. It seems that image file has been sync from somewhere else. But that websphere portal has been deployed within websphere standalone server, no dmgr node but just one application server profile. So i don't understand why that file would come out again? where is it from?
Thanks in advance
there should be a couple of directory where installation keeps their file
D:\IBM\WebSphere\wp_profile\config\cells\nodename\applications
and the second one
D:\IBM\WebSphere\wp_profile\installedApps
check both of them, if you confirm that there is no deployment manager in this configuration.