Metadata Workbench (MDWB) information and files to collect

-
All platform users



Files and Data to collect
Description
<IS_HOME>/Updates/modpack_811v1_MWB_all_8110/ISInstall*.logPatch installer logs
<WAS_IS_PROFILE>/workbench*.log 
<WAS_IS_PROFILE>/logs/workbench*.logInclude files such as workbench-aspect.log, workbench-web-activity.log, and workbench.log
<WAS_IS_PROFILE>/matching*.logWorkbench stitching log
Information Server 8.0.x only

<IS_HOME>/MDW_log.txtWorkbench installer and application logs
<IS_HOME>/InstallerEventsLog.log 

 Collecting Metadata Workbench specific information

All platform users
Command
Collects
Information Server 8.0.1 and 8.1

<IS_HOME>/ASBServer/bin/WebAdmin.bat[/.sh] -list -user <username> -password <password>Web applications that are currently deployed in WebSphere Application Server. Use Websphere Administrator user credentials
<IS_HOME>/ASBServer/bin/ServiceAdmin.bat[/.sh] -listapp -user <username> -password <password>Services that are currently deployed in WebSphere Application Server. Use Websphere Administrator user credentials
Information Server 8.1 only

<IS_HOME>/ASBServer/bin/model_status.sh] -lModels that are registered and their status

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