General Information Server information and common files to collect

-
Most of the Information Server server components run under WebSphere Application Server and might use the DB2 database to store data and information. Also, many components share the same log files to log events. Therefore, there are several files and artifacts that contain information provided by multiple components. Some of these common files are described here, for easy collection. Others are described under the particular Information Server component area. Files that are only provided by an Information Server component are described under that component's area.
You must log in as an Administrator (in Windows) or root (in Linux, Solaris or AIX) before running the commands described in this document.
Directory listingIn order to diagnose permission issues to files and directories, collect the following directory listings, with owner and group permission settings:



Directory listing only
Description
<IS_HOME>\ASBServer\*      [only directory listing]Listing of all files under folder and subfolders, with owner and group permission settings
<IS_HOME>\ASBNode\*        [only directory listing]
<TEMP>\*                   [only directory listing]
Information Server 8.0.1 only
<TEMP>\WDISuite\*             [only directory listing]
<TEMP>\WDISuite\Reporting\*   [only directory listing]
Information Server 8.1 only
<IS_HOME>\ASBServer\apps\Reporting\* [dir listing only]
Files and Data to collect
Files and Data to collect
Description
<IS_HOME>\Version.xml
Provides information about Information Server components installed on machine, version, DB2 and WebSphere Application Server installation details
<IS_HOME>\buildinfo.txtProvides build version information
<IS_HOME>\ASBServer\etc\jacc.configJACC provider configuration file
<IS_HOME>\ASBServer\conf\*ASBServer installation configuration files, including SSL keys
<IS_HOME>\ASBServer\apps\lib\*.properties.Property files that are in the Application Server classpath
<IS_HOME>\ASBServer\apps\lib\ojb-conf.jarA central jar file for XMeta containing various details about deployed models as well as XMeta POJO connection parameters.
<IS_HOME>\ASBServer\bin\startMetadataServer.logContains trace entries from starting WAS during a system startup.
<IS_HOME>\ASBNode\*.logAll logs and error logs
<IS_HOME>\ASBNode\orbtrc*

<IS_HOME>\ASBNode\orbmsg*

<IS_HOME>\ASBNode\bin\orbtrc*

<IS_HOME>\ASBNode\bin\orbmsg*

<IS_HOME>\ASBNode\*.err

<IS_HOME>\ASBNode\*.out

<IS_HOME>\ASBNode\core*

<IS_HOME>\ASBNode\logging-agent-buffer.ser
Serialized log events
<IS_HOME>\ASBNode\bin\*.log

<IS_HOME>\ASBNode\bin\*.err

<IS_HOME>\ASBNode\bin\*.out

<IS_HOME>\ASBNode\bin\logging-agent-buffer.ser
Serialized log events
<IS_HOME>\ASBNode\javacore*<IS_HOME>\ASBNode\heapdump*<IS_HOME>\ASBNode\bin\javacore*<IS_HOME>\ASBNode\bin\heapdump*Java Core and heap dump files, created for OutOfMemoryErrors: there may be several, collect the most recent ones
Information Server 8.0.1 FP1/FP2 only 
<IS_HOME>\ASBNode\conf\registered-servers.xmlregistered-servers.xml file
Information Server 8.1 and 8.1.1 only 
<IS_HOME>\ASBNode\eclipse\plugins\ com.ibm.isf.client_configuration_8.1.0.0\registered-servers.xmlregistered-servers.xml file
Information Server 8.5 only 
<IS_HOME>\ASBNode\eclipse\plugins\ com.ibm.isf.client_8.5.0.0\registered-servers.xmlregistered-servers.xml file
Information Server 8.7 and above 
<IS_HOME>\ASBNode\eclipse\plugins\ com.ibm.isf.client\registered-servers.xmlregistered-servers.xml file
Agents' logs, Information Server 8.5 and above 
<IS_HOME>\ASBNode\logs\*.properties<IS_HOME>\ASBNode\logs\*\*.log<IS_HOME>\ASBNode\logs\*\*.log.pos<IS_HOME>\ASBNode\logs\*\*.log.errLog files from Logging Agent:
*.log* files only from subfolders under \logs
Migration logs, Information Server 8.5 and above 
<IS_HOME>\Migration\logs\*Migration log files
Windows registry
The following Windows registry keys are used by Information Server and its components:
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\InformationServerHKEY_LOCAL_MACHINE\SOFTWARE\Ascential Software
HKEY_LOCAL_MACHINE\SOFTWARE\Mortice Kern Systems
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Use the following commands to collect Windows registry entries specific to Information Server. Some of the keys might not exist, depending on the Information Server components that were installed.
Command
REG QUERY HKLM\SOFTWARE\IBM\InformationServer /S
REG QUERY "HKLM\SOFTWARE\IBM\Ascential Software" /S
REG QUERY "HKLM\SOFTWARE\Mortice Kern Systems" /S
REG QUERY "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems" /S
REG QUERY "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /S
REG QUERY HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters /S

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