Active Endpoints
Your SOA Needs BPEL for Orchestration
|
 |
 |
|
|
|
|
|
| | | | | | | | |
|
|
|
|
|
|
| | | | | | | | | | | | | | | | |
|
|
| SYS-CON MEDIA: | | | | |
| SYS-CON EVENTS: | | | | | |
| INTERNATIONAL SITES: | | | | | | | | | | |
 |
Terms of Use & Our Privacy Statement  About Newsfeeds / Video Feeds |
| Copyright ©1994-2008 SYS-CON Publications, Inc. All Rights Reserved. All marks are trademarks of SYS-CON Media. |
| Reproduction in whole or in part in any form or medium without express written permission of SYS-CON Publications, Inc. is prohibited. |
In the last part of this
three part series, we're
going to look at some
advanced topics and
further considerations
for running WebSphere
effectively under UNIX,
including monitoring,
security and resilience.
To administer WAS, you
have to connect to the
Administration Console on
the node using a Web
browser. The default URL
will be http://hostname:9
090/admin/. (Use the app
server hostname directly;
do not go via the Web
server.) 
This article describes
how to install and use
IBM WebSphere Application
Server (WAS) on Unix
systems (chiefly Sun
Solaris but most of the
information is generally
applicable). It's for
Unix system
administrators who must
support WebSphere in an
enterprise or production
context. 
