|
Home > Archive > WebSphere Portal Server > November 2004 > Websphere Application Server and Portal Server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Websphere Application Server and Portal Server
|
|
|
| Instead of starting the Application Server first and then start the Portal
Server, I start the Portal Server only, and my portlets work fine, is it ok
if I don't start the Application Server?
| |
| Mattias Abrahamsson 2004-10-25, 2:48 am |
| Hello,
You don't need to have server1 started in order to run your portal.
"server1" is used for administrative purposes (during installs and fixpacks)
as far as I can tell.
//Matt
"Ho" <h.lui@environs.com.hk> wrote in message
news:clhra3$8bl2$1@news.boulder.ibm.com...
> Instead of starting the Application Server first and then start the Portal
> Server, I start the Portal Server only, and my portlets work fine, is it
> ok if I don't start the Application Server?
>
| |
| Scott A. Roehrig 2004-10-27, 5:53 pm |
| WAS supports the notion of multiple servers or nodes. WPS is installed as a
completely separate node
within the WAS cell. Therefore server1 is not required to be running to for
WPS to work.
Server1 is typically used for administration purposes since the WAS admin
console Web application
is installed to that node, although the application can be installed to the
WPS node as well.
Scott
"Mattias Abrahamsson" <none@nowhere.com> wrote in message
news:cli6k3$8grs$1@news.boulder.ibm.com...
> Hello,
>
> You don't need to have server1 started in order to run your portal.
> "server1" is used for administrative purposes (during installs and
> fixpacks) as far as I can tell.
>
> //Matt
>
> "Ho" <h.lui@environs.com.hk> wrote in message
> news:clhra3$8bl2$1@news.boulder.ibm.com...
>
>
| |
| Munish 2004-11-11, 2:48 am |
| Hi
You are absolutely right in saying that server1 is not required to be running for WPS to work.
But WebSphere_Portal is not a node as per my understandings. It is an Application Server under a node(Node name is usualy host name of machine where WebSphere is installed). server1 and WebSphere_Portal are application servers installed under that node.
In WAS 5.0 the name space for a cell is distributed among the various servers. The Deployment Manager, node agent and application server processes all host a name server. In previous releases, there was only a single name server for an entire administrative domain.
In WebSphere releases prior to 5.0, all servers shared the same default initial context, and everything was bound relative to that initial context.
In WebSphere Application Server V5, the default initial context for a server is its server root. System artifacts, such as EJB homes and resources, are bound
to the server root of the server they are associated with.
This is the reason why we don't need to start server1 for running WebSphere_Portal server.
Please correct me if I am wrong.
Regards,
Munish Pandhi
"Scott A. Roehrig" <saroehr@hotmail.com> wrote in message news:clorfo$3g1s$1@news.boulder.ibm.com...
> WAS supports the notion of multiple servers or nodes. WPS is installed as a
> completely separate node
> within the WAS cell. Therefore server1 is not required to be running to for
> WPS to work.
>
> Server1 is typically used for administration purposes since the WAS admin
> console Web application
> is installed to that node, although the application can be installed to the
> WPS node as well.
>
> Scott
>
> "Mattias Abrahamsson" <none@nowhere.com> wrote in message
> news:cli6k3$8grs$1@news.boulder.ibm.com...
>
>
|
|
|
|
|