JBoss 7 in Eclipse - eclipse

I installed Jboss7 into my Eclipse Oxygen.
When I write into my browser: http://localhost:8080/jbossws I cannot reach the page:
When I write http://localhost:8080 I have the following result
What is missing into my installation?

The url does not exist in JBoss AS 7.x or above. You should add a JBoss Admin user (with the add_user.sh/bat) With the url http://localhost:9990 (If you have not changed the port.) you can reach the admin console. Under Deployment are the web services.

Related

Liferay/jboss : no response after hot deploying a war

When I start jboss server with liferay (6.2), everything works. I can access the portal, access the administration section of liferay, even war deployed outside of liferay (activiti-explorer,...)
But when I hot deploy a war with portlets, jboss is still running but I can't access anything, even war deployed outside of liferay.
In chrome, i get a ERR_EMPTY_RESPONSE for any url pointing to the jboss server.
In the jboss console, there is nothing showing up after liferay telling the war has been deployed.
Could you help or indicate me leads to resolve my problem?
Thanks in advance

How do I deploy to Websphere developer server 8.5 via Eclipse Mars?

How does one deploy a web app from Eclipse Mars to a local install of IBM Websphere Application Server Developer 8.5 ?
I installed the app server from IBM's Installation Manager, upon completion it says its location is:
C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv01
I tested the app itself using the "First Steps" window which popped up after install, and it looks like it is running fine.
Now, I want to test creating a simple hello world web application in Eclipse Mars, and be able to deploy it to this installed Websphere instance and be able to debug (stop at breakpoints). However, I can't seem to figure this part out.
When I go to my Servers tab in Eclipse and attempt to add a Websphere server, I didn't have any options. So I started downloading some IBM Websphere Developer Tools that I could find. I managed to now have these options for adding server:
"WebSphere Application Server Liberty"
"WebSphere Application Server traditional V8.5"
I tried using both, but they don't seem to be compatible with my installed version of WebSphere, because I keep getting the error of "The WebSphere Application Server traditional installation directory is not correct." when I try to plug in the Installation directory.
I suspect I should have a separate option for
"WebSphere Application Server developer V8.5"
or such, however no matter what I search for online, in the Eclipse marketplace, in the Eclipse sites, I can't find anything to install that gives me that option.
You have to use "WebSphere Application Server traditional V8.5" and point it to the installation root not the profile root - so to C:\Program Files (x86)\IBM\WebSphere\AppServer in your case.
For the future, it is not recommended to install WebSphere in the Program Files (x86) folder, I'd suggest something simpler like c:\IBM.
I used the below link Eclipse Mars WAS Plugin . Not sure it still works. For Oxygen working version use Eclipse Oxygen WAS Plugin

Eclipse STS connecting to Tomcat

In Spring Tool Suite IDE, have added Tomcat server and started it. Console output says : INFO: Server startup in 19182 ms
But on trying url http://localhost:8080/, gives HTTP error 404
STS version - 3.6.2.
If server is started outside Eclipse, Tomcat homepage is accessible as usual.
Try http://localhost:9087/ and see if that works. You may need to check your configurations for other port numbers, but 9087 should work.
Got it working!
Wile running tomcat in eclipse, not all files are copied in the new deployment location in the eclipse workspace. But after manually copying index.jsp and related images, the home page came.

Apache Tomcat 7 and Eclipse Juno EE integration (Ubuntu 12.04)

I am currently setting up a Web Service environment for developing SOAP Web services in a linux box (Ubuntu 12.04). I want to use Eclipse EE Juno with Apache Tomcat 7. I successfully install tomcat (using the sudo apt-get install) and configure it as a Server runtime environment in Eclipse. When, I deploy a web service in order to test it, everything works fine. However, when I type the URL to my browser, nothing works. It seems that Apache tomcat is up and running, but no web services are deployed (in fact i receive an HTTP Status 404 from tomcat). Being curious, I go to "/var/lib/tomcat7/webapps/" directory in order to check if any web application is deployed, and there are no web applications.
What may be the matter? How can I configure correctly my tomcat in order to work with Eclipse and be able to deploy and test my web applications through the IDE?
Thank you.
Problem solved by configuring to IDE to have all the pribileges on the server.

Deploying portlet on liferay with weblogic 10.3

Currently I have set up liferay 6.1 to weblogic server 10.3.5.
Now I can use liferay portal from weblogic server.
After that, I am trying to deploy the other sample portlet to liferay on weblogic server.
I would like to know how to deploy that sample portlet?
Another problem is that I want to develop portlet applicatin that use JSF 2.0 for view and EJB 3.0 for business layer. Can I deploy that portlet applicatin on liferay with weblogic server. Is that possible. If possible, Please guide me.
Keep in mind that Weblogic only supports hot deploy for the admin server. There are 2 import settings that liferay needs for hot deployment on weblogic. You need a setting for the weblogic dest dir and a liferay home setting that refers to the root folder of the Weblogic domain. The env.DOMAIN_HOME doesn't work in WLS 10.3.6, that's why you need to set the home location with the full path.
Normally Liferay has a "deploy" folder that it monitors for .war files. You just copy your portlet .war file to that folder, and Liferay deploys it. You can change location of that folder by configuring "auto.deploy.dest.dir" setting in portal-ext.properties.
According to documentation, on WebLogic by default it has this value:
auto.deploy.weblogic.dest.dir=${env.DOMAIN_HOME}/autodeploy
Also another part of documentation mentions that on some containers portlets hot deployment may not work or be problematic. But I think this is not about WebLogic.