AIXThis forum is for the discussion of IBM AIX.
eserver and other IBM related questions are also on topic.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
It's a general philosophy problem. If you use your AIX system as a server, you never need a graphic console. If you use it as a workstation, you need a graphic console.
Personnally, I use wsm remotely, so I have no graphic display on most of my systems.
Some people hate sending infos like passwords through the network, so for database administration and system administration purposes, they prefer having the graphical console directly attached to the system, nothing goes to the network.
I very rarely use AIX servers with directly attached graphics displays. I use SSH with X11 tunnelling turned on. As long as I have an X11 server running on the client side (e.g. I run Linux or have Windows with something like Exceed), just typing "wsm" will bring it up on my screen.
There are also a Windows and a Linux client for wsm which should make it run a lot faster (since it runs like a dog otherwise). If you've got wsm installed on your server, you should find the files on there already; just copy them over to your PC and install them.
Finally, you can set the whole thing up to work over a web browser, though I haven't done it for a while and I can't remember exactly how.
Yes, that is exactly what I would like to do. I have installed the windows client on my pc. However, I cannot connect to the box. I started the wsm server from the cmd line, but no go. I have changed the port to a port that I know is open and it still does not connect. Apparently the server is not starting when i run the command.
It seems that because I changed the port to the non-default, the pc-client doesn't see the server. However, if the server is listening for the client shouldn't it pick it up regardless of what port it is on?
Quick question - are you running the WebSphere Application Server and are using its admin consoile on the same box? Both try to make use of port 9090 by default, which is why you have to do a "wsmserver -disable" to install WAS with the defaults.
Just be aware! IBM document this sort of behaviour in the WAS RedBooks rather than the WSM RedBooks....