If you are running, for example, IBM Connections as a "large deployment", you got at least 18 JVMs with their corresponding SystemOut.log files to monitor for errors, issues and the likes. Always stating them explicitly was – for me – too cumbersome. So I thought of an easier way. This is what I came up with.

According to the documentation, the WebSphere Application Server (WAS) log files are located in the following directories on each node in your WAS installation:

path/profiles/profilename/logs/servername/logs

where path is the WebSphere Application Server installation path. By default, path is the following:

/opt/IBM/WebSphere/AppServer

So in an IBM Connections 5.5 environment, there would be these log files:

/opt/ibm/WebSphere/AppServer/profiles/node01/logs/PushNotificationCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/NewsCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/HomepageCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/MetricsCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/FebCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/nodeagent/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/WidgetContainerCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/CommunitiesCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/WikisCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/MobileCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/DogearCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/BlogsCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/ModerationCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/CommonCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/SearchCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/RTECluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/ForumCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/ActivitiesCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/FilesCluster_server1/SystemOut.log
/opt/ibm/WebSphere/AppServer/profiles/node01/logs/ProfilesCluster_server1/SystemOut.log

So to get them all in one continuous log stream the following one-liner comes in handy:

find /opt/ibm/WebSphere/AppServer/profiles/node01/logs -name SystemOut.log -print0 | xargs --null tail -F

Of course, there are other solutions to this as well. One of them would be multitail, logcheck, Simple Log Watcher or lnav, but you would have to install them, which more often then not, isn't possible in a customer environment.

Tagged as: command line, commandline, linux, log, logs, systemout.log, tail, was, websphere | Author: Martin Leyrer
[Montag, 20190701, 15:31 | permanent link | 0 Kommentar(e)