Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Simon

 
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From the other thread, you said:
"I am really having trouble to understand which problem is resolved to you, and what's the remaining. It will be nice if you can open a new thread.
In WAS, there are 2 http server. One is called embedded server, which listens to port 9080. And supposedly it resides in Servlet engine, so it uses FileServlet to serve static content. This is equivalent to BEA WLS default installation.
WAS can have external http server connected to WAS servlet engine, so you can easily load balancing your http server. You don't need it for testing purpose, but for production you definitely will go with it. IHS/Apache can be installed along with AEs/AE, they usually listen to port 80.
So it totally depends on how your application is installed, you can access it via port 80(if external http server is active and your plugin config has it) or port 9080(if WAS is the only running instance).
WAS 4.0 Handbook is about WAS AE, it is for administrator different from Dev book. It is sg246176 on redbooks site."

I'm clear about the two http servers now. I've shut down the external http server, so all questions are now about the embedded http server.
You stated that the embedded server listens on port 9080. When I type in the url //localhost:9080 I get nothing. In the previous thread you will note that both Prashanth and I do not get the sample applications to run at the url //localhost:9080/WSsamples/index.html. That seems like that should work with the embedded server, since the external server does bring up the sample applications from //localhost/WSsamples/index.html.
I'm probably misunderstanding virtual hosts, but the default_host is set to 9080 and the admin_host is set to 9090. Again, I am successful with the embedded server and the url //localhost:9090/admin (so the embedded server must be working, right?).
In trying to install the ear file from the WAS 4.0 Development Handbook, they suggested I would need to disable or uninstall the sample application, because both are pointed to the / (root) context. As an alternative, they suggested I could set up an alternative virtual host, which is what I did. I setup a pigbank_host assigned to port 9081. During the piggy_bank ear installation, I selected the pigbank_host as the virtual host.
So I would expect //localhost:9081 to bring up the index.html file. I've also tried //localhost:9081/index.html without success.
Prashanth suggested that the problem may be because of the server-cfg file generated for the external server. I tried temporarily renaming it, and restarting the server without success.
The server-cfg file would just be for the external server, right? Nothing to do with the embedded server??
I'm very interested to reading any appropriate documentation. Thanks to your suggestion, I read all of the WAS 4.0 Development Handbook, other than the JUnit chapter. I'm going to come back to that. That was very good advice and an excellent read. I will go look at the WAS 4.0 AE Handbook as you suggest. I am running AEs, but hopefully the information will still apply. Does the AE version also have an embedded server?
Appreciate the continued help. I need to solve this one before I can walk thru the example code.
Mike
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think prashanth may be a bit confused:
server-cfg.xml contains the configuration for the app server. The embedded HTML server certainly needs it.
plugin-cfg.xml contains the routing information for the external HTTP server. It is generated from the information in the server-cfg.xml file by the GenPluginCfg tool.
Kyle
 
Looky! I'm being abducted by space aliens! Me and this tiny ad!
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic