WebSphere Application Server - How to print http ports with jacl(wsadmin) in was 6.X?

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > February 2007 > How to print http ports with jacl(wsadmin) in was 6.X?





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 How to print http ports with jacl(wsadmin) in was 6.X?

2007-02-15, 1:20 pm

Hello Everybody,

I am currently developing a general jacl script for printing useful information about every application running in a Websphere installation. The information consists of application name, virtual host, server name etc... So far I havent managed to figure o
ut how to display the
http ports. In WAS 5 printing the ports was easy:

>set server [$AdminConfig getid /Server:GetServicesSrv/]
>$AdminConfig list EndPoint $server


but it won`t work in Was 6.X. Could somebody give me a clue about how to do it?
I have tried to navigate across the element hierachy with the command

>$AdminConfig attributes XXX


beginning with

$AdminConfig attributes Server

in order to see what elements XXX has related to it(the first element to scan being 'Server' is supposed to be an obvious choice since the http ports are configured on server level).

I would appreciate any help, also hints about how to make more efficient searches with AdminConfig are welocme...

Regards,
Tom

2007-02-15, 1:20 pm

I just figured out that by executing the commands

>set server [$AdminConfig getid /Server:server1/]
>$AdminConfig showall $server


I can get most of the information, for example the bootstrap port, the soap connector port, the CSIV2_XXX ports and the ORB port but Im still missing the http and https ports... any hints? On which level/in which object are they configured?




2007-02-19, 7:16 pm

Hello,

Almost finished the scripting assignment, IŽll send everything programmed during the two last days as a file attachment in the case somebody finds the information useful. Note the procedure prueba, which is the main test method.

I arranged the information displayed by separating the information with tabs and carriage returns. This makes is easier to copy and paste the information into an Excel file.

Regards,
Tom

2007-02-19, 7:16 pm

...and now the attached file
Mark Lewis

2007-02-20, 1:18 pm

thomasisomaki@hotmail.com wrote:
> ..and now the attached file


Hi Tom,

Your attachment didn't make it through to my newsreader. It sounds like
you've solved your problem OK but perhaps this is useful for somebody
else anyway... Here is a bit of jacl that should interrogate the
endpoints for each server on WAS 6.x:

set nodes [$AdminConfig list Node]
foreach node $nodes {
set nodeName [$AdminConfig showAttribute $node "name"]

set serverEntries [$AdminConfig list ServerEntry $node]
foreach serverEntry $serverEntries {
set serverName [$AdminConfig showAttribute $serverEntry "serverName"]
puts ""
puts "Node:$nodeName/Server:$serverName"

set namedEndPoints [$AdminConfig list NamedEndPoint $serverEntry]
foreach namedEndPoint $namedEndPoints {
set endPointName [$AdminConfig showAttribute $namedEndPoint
"endPointName"]
set endPoint [$AdminConfig showAttribute $namedEndPoint "endPoint"]
set host [$AdminConfig showAttribute $endPoint "host"]
set port [$AdminConfig showAttribute $endPoint "port"]
puts "$endPointName: $host:$port"
}
}
}
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com