|
Home > Archive > WebSphere Application Server > February 2007 > New to Websphere 6.1, new server question
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 |
New to Websphere 6.1, new server question
|
|
|
| Hi All
Running WebSphere 6.1 on Solaris and wanting to create a new server. I have found out that I have to do this by way of creating a new profile (if I have understood this correctly), but no matter what I do the server name stays as server1. How can I change
this so that when I stop/start a server I can specify the one I want. Or am I missing something here?
Many thanks
Farren Minns
| |
| Stephen Cocks 2007-02-12, 1:19 pm |
| In most respects each profile is a separate workspace. Amongst other things
the profile contains product configuration, such as the definition of an
application server, and this is collectively called a "Node". All the
command line tools operate on a profile and one of the profiles you've
created is identified as the "default" when no other profile is specified.
You can elect that a new profile becomes the default profile when you create
it, or you can change the default profile using the manageprofiles.sh
command.
So if you run the startServer.sh script to start a server, and you run this
from the $WAS_HOME/profiles/myprofile/bin directory then it will start a
server in profile "myprofile". If you run the script from $WAS_HOME/bin then
it will start a server in the default profile. Thus the fact that both
servers have the name "server1" isn't important. Similarly if you run admin
scripts using the wsadmin shell you should run the version from the required
profile directory. You can also specify "-profileName myprofile" on most
commands.
If you have the Network Deployment version of a WebSphere platform product,
then you can manage configuration across multiple Nodes from a central
Deployment Manager server. The collection of Nodes, and all their related
configuration, managed by a Deployment Manager is called a "Cell". In a Cell
the names of servers are qualified by the name of their Node. Each Node in a
Cell must have a unique name, and that provides a namespace for the servers.
Hence NodeA/server1 and NodeB/server1 are different entities. Nodes in a
Cell can also support multiple application servers. When constructing a
Network Deployment topology it is common to use the "Custom" profile type
which initially has no servers configured, and to configure one or more
servers on that Node from the Deployment Manager - in which case you can
provide your own server names and don't have to stick with "server1".
(The above rules are neither 100% accurate, nor 100% complete, but they will
suffice for most practical purposes)
--
Stephen Cocks
WESB/WPS System Administration
<fminns@wiley.co.uk> wrote in message
news:343277444.1171278593576.JavaMail.wassrvr@ltsgwas009.sby.ibm.com...
> Hi All
>
> Running WebSphere 6.1 on Solaris and wanting to create a new server. I
> have found out that I have to do this by way of creating a new profile (if
> I have understood this correctly), but no matter what I do the server name
> stays as server1. How can I change this so that when I stop/start a server
> I can specify the one I want. Or am I missing something here?
>
> Many thanks
>
> Farren Minns
| |
|
|
|
|
|