aspose file tools*
The moose likes Websphere and the fly likes starting new managed server Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "starting new managed server " Watch "starting new managed server " New topic
Author

starting new managed server

kala subramanyam
Greenhorn

Joined: Jan 13, 2004
Posts: 4
Hi,
I am trying to create & run a new server on IBM's Websphere application server 5.1 .
I am able to create it and start it. I am not able to open the admin console and install applications.
1. Is there a way to start the admin console other than starting it along with the default server from first steps.
Thanks
Kala
chandubcs
Ranch Hand

Joined: Jun 03, 2001
Posts: 47
I am also facing same problem, you can see my thread at http://www.coderanch.com/t/74397/Websphere/start-or-run-application-newly
I tried many ways, but no solution. If I get the solution I will update you and if you come to know the solution please update me, whichever comes first.
Thanks,
Chandra
Scott Duncan
Ranch Hand

Joined: Nov 01, 2002
Posts: 363
OK, here is the deal. The admin console in WAS 5 basically sux. The admin console that comes with the install by default is installed on the server1 instance. This console can only install/edit/manage applications on the server1 instance. You can set up and configure new server instances via the console but do not think you will be able to start them. The reason for all of this? Well the support guys tell me it is because each server instance runs on it's own, dedicated JVM and therefore, an application (such as the admin console) running on the server1 instance, cannot manage applications running on a different instance (e.g. server2). In fact you cannot do much of anything with the other instances you create other than create and config them. Do not be misled by the documentation in the info center like I was. By looking at the documentation, it seems that this should be possible. In fact, this should be a very normal way of doing things as every other quality app server on the market does this without a hitch. Your options are this...
1.) Create a new virtual host for each server instance you create with a different port number than 9090 (admin_host) and then use wsadmin to install the adminconsole.ear file on each server instance using the appropriate, newly created port. Now you will have an admin console for each server instance. Not a clean solution I know but it works.
2.) Install WebSphere Network Deployment to manage all of your server nodes. Incorporate each node into the ND cell. This is an administrative nightmare but once it is set up it is pretty cool. (And this is what it all boils down to. IBM has found yet another way to extort money from their customers by basically forcing ND on us. I find it funny that ND can manage multiple nodes with multiple server instances with multiple apps on each but they will tell you it is impossible to manage seperate server instances from the admin console that comes with the product.)
3.) You can do what I did. I uninstalled all adminconsoles on every machine we have and manage them with the wsadmin tool. This has a pretty high learning curve but in the end, your environment will be more stable and you will be glad you did it. Of course doing this begs the question 'Why use WebSphere if I have to use the command line to administer it?'
IBM should have stuck with their fat admin client. At least it worked...


No more rhymes! I mean it!<br /> <br />Does anybody want a peanut?
kala subramanyam
Greenhorn

Joined: Jan 13, 2004
Posts: 4
Thank you for the reply.
Can you please tell me how to use wsadmin to install the application or atleast forward a link where I can find the information.
I am looking at IBM's document, it looks like I will have to use jacl scripts to do it. Cant I just say something like
wsadmin -c install my_application.ear
and then say
wsadmin -c start application my_application
Thanks for all the help
Kala
Rufus BugleWeed
Ranch Hand

Joined: Feb 22, 2002
Posts: 1551
1. get command prompt
wsadmin<CR>
2. issue help command
wsadmin>$AdminApp help install
You need the admin console. You should focus on why you are not getting it. http://localhost:9090/admin works on my machine after I issue start the server.
Have you reviewed ../logs/startServer.log and ../logs/SystemOut.log?
[ January 15, 2004: Message edited by: Rufus BugleWeed ]
Scott Duncan
Ranch Hand

Joined: Nov 01, 2002
Posts: 363
You do not need jacl scripts to do anything with wsadmin. However, they make like easier on you. I do not use one for install but I do use one for the update.
To install open wsadmin.
$AdminApp installInteractive C:/apps/myapp.ear
or to use the defaults on the install:
$AdminApp install C:/apps/myapp.ear
To uninstall:
$AdminApp uninstall app_name
To update, use the -update option on the install
chandubcs
Ranch Hand

Joined: Jun 03, 2001
Posts: 47
I tried this with wsadmin tool, its working properly and we can install the applications, but I am wondering how to install applications on newly created server "server2". When I use "..installInteractive myApp.ear -server server2" its giving me some error. And how to make that application start on "server2".
Thanks much,
Chandra
kala subramanyam
Greenhorn

Joined: Jan 13, 2004
Posts: 4
1. Start server1. Open admin console
2.create new server. Server2
3. Go to server2 -> web container -> HTTP Transport -> note the port nos
4. Environment -> Virtual hosts -> Add the port nos to the default host
5. Install the application to the server2 (step : Map modules to application servers)
6. Go to command prompt and start the server2. This step will start both server2 and the application.
Tony Chen
Ranch Hand

Joined: Jan 29, 2001
Posts: 286
Re: William
I don't know where you get the WAS support for Admin Console. But there are three ways to get an admin console for server2 (or whatever new app server).
1. install ND (you already know this one) and use the admin console on the dmgr;
2. install another admin console to server2;
3. map the installed admin console on server1 to both server1 and server2;
Also, to let you know, with only admin console on server1, you can also do a lot of stuff with server2, such as install applications onto server2, etc.
Tony


SCJP Java 2 - IBM Certified Enterprise Developer - WebSphere V4.0 & V5.0 - IBM Certified System Administrator - WebSphere Network Deployment V6.0 - Canadian Securities Course (CSC) Certification
Rickey Mooney
Greenhorn

Joined: Aug 11, 2002
Posts: 4
Tony had some interesting ideass; however
1. if you use admin console installed on server1 when you install a application it has a lot of problems communicating with server2;
2. IBM documentation is mis-leading but in line with what William Duncan says if you read the documentation about the base system it is a single application server so it will not support two application servers - you need the Deployment Manager (you really need node agent which only works with the Deployment Manager).
3. Setting up two admin consoles is very involved/complex.
4. You might look into wsinstance software (setting up multiple standalone versions of WSA 5.x Application Server).
5. I would really like to know how one would map the admin console on server1 to server2 ?
Tony Chen
Ranch Hand

Joined: Jan 29, 2001
Posts: 286
Originally posted by Rickey H Mooney:
Tony had some interesting ideass; however
5. I would really like to know how one would map the admin console on server1 to server2 ?

Installing a new application
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/trun_app_instwiz.html
11. On the Step: Map modules to application servers panel, for every module select a target server or a cluster from the Clusters and Servers list. Place a checkmark in the check box beside Module to select all of the application modules or select individual modules.
(you can select both server1 and server2 and more... and you can perform this on existing applications as well such as admin console.)
Tony Chen
Ranch Hand

Joined: Jan 29, 2001
Posts: 286
Originally posted by Rickey H Mooney:
Tony had some interesting ideass; however
1. if you use admin console installed on server1 when you install a application it has a lot of problems communicating with server2;
3. Setting up two admin consoles is very involved/complex.

Not really true!
You can install the "adminconsole" application to server2 from within the admin console running on server1. Once it's installed. Start server2 using command "startServer server2", and access "http://localhost:9091/admin"
A few additional steps you might need to perform:
1. add *:9081 to default host alias list (9081 is the http port of server2);
2. add *:9091 to admin host alias list (9091 is also the http port of server2);
3. regenerate the web server plugin;
Good luck!
Tony
 
wood burning stoves
 
subject: starting new managed server