WebSphere Application Server information and files to collect

-
The commands presented in this section invoke the standard IBM WebSphere Application Server collector tool that creates a zip file containing the following information:
  • WebSphere Application Server release information
  • WebSphere Application Server Installation Logs
  • Directory listing of WebSphere Application Server folders
  • Files under AppServer\logs
  • AppServer\bin\*
  • AppServer\properties\*
  • AppServer\profiles\<folder> used by the Information Server installation [with selected files from all folders under the profile]



Make a copy of the profile data from each server in the node, from the profile where Information Server was installed, which includes the following artifacts where Information Server data and logs are found.
Files and Data to collectDescription
<WAS_IS_PROFILE>/logs/*
All files contained in the /logs folder and its subfolders
<WAS_IS_PROFILE>/properties/portdef.props<WAS_IS_PROFILE>/logs/portdef.props 
<WAS_IS_PROFILE>/classes/*.properties<WAS_IS_PROFILE>/classes/ojb-conf.jar

<WAS_IS_PROFILE>/javacore*<WAS_IS_PROFILE>/heapdump*
Java Core and Heap dump files created by OutOfMemoryErrors. There may be several but collect the most recent ones
Non Clustered WAS environmentDescription
<WAS_IS_PROFILE>/config/cells/<hostname>Cell01/security.xml<WAS_IS_PROFILE>/config/cells/<hostname>Cell01/
     nodes/<hostname>Node01/serverindex.xml <WAS_IS_PROFILE>/config/cells/<hostname>Cell01/
     nodes/<hostname>Node01/servers/
     <servername>/server.xml		 
Clustered WAS environment (IS 8.5 and above)Description
Gather from every <PROFILE> folder: both the <WAS_DMGR_PROFILE> and every <WAS_NODE_PROFILE> in cluster:

<PROFILE>/config/cells/<hostname>Cell01/security.xml
<PROFILE>/config/cells/<anyFolder>/*.xml
<PROFILE>/config/cells/<anyFolder>/jacc.config
<PROFILE>/config/cells/<anyFolder>/clusters/<anyFolder>/*.xml
<PROFILE>/config/cells/<anyFolder>/nodes/<anyFolder>*/*.xml
<PROFILE>/config/cells/<anyFolder>/nodes/<anyFolder>/servers/<anyFolder>/*.xml
<PROFILE>/config/cells/<anyFolder>/wim/<anyFolderAndSubFolders>/*.xml		On the DMgr node and also on every node in the cluster, as well for each Server in the Node
IBM WebSphere Application Server version 8 and aboveDescription
<WAS_IS_PROFILE>/logs/server1/TextLog_xxxxxx.log <WAS_IS_PROFILE>/logs/server1/logdata/*.*<WAS_IS_PROFILE>/logs/server1/tracedata/*.*WAS version 8 High Performance Extensible Logging (HPEL) logs
IBM WebSphere Application Server LibertyDescription
<WAS_IS_PROFILE>/mis/logs/*.log <WAS_IS_PROFILE>/mis/server.xml<WAS_IS_PROFILE>/mis/bootstrap.propertiesWAS Liberty log and configuration files
Collect all WebSphere Application Server artifacts as shown in the following tables:
AIX, Solarix, Linux, or HP-UX
Command
Collects
  • Verify that the path contains the following system directories:
    /bin
    /sbin
    /usr/bin
    /usr/sbin
  • Run the following command from inside a temporary directory (outside of the WAS_HOME folder)
<WAS_HOME>/bin/collector.sh -verbosity 5 -JarOut CRMxxxxx_Collection_<timestamp>.jar
add the parameter -profileName profile_name

Standard WebSphere Application Server data, profiles, and log collector. ProducesCRMxxxxx_Collection_<timestamp>.jar file
Collects artifacts under the specified WebSphere Application Server profileName rather than the default profile
Windows
Command
Collects
  • Include regedit in the path
  • Run the following command from inside a temporary directory (outside of the WAS_HOME folder)
<WAS_HOME>\bin\collector.bat -verbosity 5 -JarOut CRMxxxxx_Collection_<timestamp>.jar
add the parameter -profileName profile_name		 Standard WebSphere Application Server data, profiles, and log collector. ProducesCRMxxxxx_Collection_<timestamp>.jar file
Collects artifacts under the specified WebSphere Application Server profileName rather than the default profile
WebSphere thread dump
Procedure
To generate a WebSphere thread dump, go to <WAS_IS_PROFILE>\bin folder (e.g.C:\IBM\WebSphere\AppServer\profiles\default\bin) in a command window and invoke the following commands:
wsadmin
set objectName [$AdminControl queryNames WebSphere:type=JVM,process=server1,*]
$AdminControl invoke $objectName dumpThreads
quit
The thread dump file will be in the WebSphere profile directory <WAS_IS_PROFILE> and will have a name like javacore.xxxxxxxx.xxxxxx.xxxx.txt

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more