XMeta Metabrokers and Bridges

-
All platform users
Files and Data to collect
Description
Services (Domain) machine

<IS_HOME>\ASBServer\install\logs\xmeta-install.log
xmeta installation log
<IS_HOME>\ASBServer\install\etc\history\xmeta-install-status.hist
xmeta installation history file
<IS_HOME>\ASBServer\install\bin\install.properties
xmeta installation configuration file
Server (ie ds engine) machine

<IS_HOME>\ASBNode\install\logs\xmeta-install.log
xmeta installation log
<IS_HOME>\ASBNode\install\etc\history\xmeta-install-status.hist
xmeta installation history file
<IS_HOME>\ASBNode\install\bin\install.properties
xmeta installation configuration file
Client machine

<IS_HOME>\ASBNode\install\logs\xmeta-install.log
xmeta installation log
<IS_HOME>\ASBNode\install\etc\history\xmeta-install-status.hist
xmeta installation history file
<IS_HOME>\ASBNode\install\bin\install.properties
xmeta installation configuration file

 Windows

 Set environment variable MIR_LOG_LEVEL to 6. All the debug information for Bridges will be captured in the log files as described below:
Files and Data to collect
Description
Client Machine

<USER_HOME>\dstage_wrapper_trace*.logDatastage logs.  <USER_HOME> is typically C:\Documents and Settings\<username>
<USER_HOME>\dstage_wrapper_spy*.logDatastage logs
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM WebSphere Metadata Server MetaBroker\IBMWDISPostprocessor.logMetabrokers and Bridges post processor Log File
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM WebSphere Metadata Server MetaBroker\IBMWDISPreprocessor.logMetabrokers and Bridges pre processor Log File
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM WebSphere Metadata Server MetaBroker\IBMWDISDecoderParamValues.xml

<IS_HOME>\Clients\MetaBrokersAndBridges\IBM WebSphere Metadata Server MetaBroker\IBMWDISEncoderParamValues.xml		Metabrokers and Bridges parameter values files
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM Rational Data Architect MetaBroker\IBMRDADecoderParamValues.xmlMetabrokers and Bridges parameter values file
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM Rational Data Architect MetaBroker\*.logMetabrokers and Bridges Log File
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM Rational Data Architect MetaBroker\Installation directoryMetabrokers and Bridges Log File
Client Machine, Information Server 8.7 and above

<IS_HOME>\Clients\MetaBrokersAndBridges\IBM InfoSphere Data Architect MetaBroker\IBMIDADecoderParametersEnu.xmlMetabrokers and Bridges parameter values file
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM InfoSphere Data Architect MetaBroker\*.logMetabrokers and Bridges Log File
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM WebSphere Metadata Server MetaBroker\ IBMWDISDecoderParametersEnu.xmlMetabrokers and Bridges parameter values file
<IS_HOME>\Clients\MetaBrokersAndBridges\IBM WebSphere Metadata Server MetaBroker\ IBMWDISEncoderParametersEnu.xmlMetabrokers and Bridges parameter values file
Client Machine, Information Server 11.3 and above

<IS_HOME>\Clients\MetaBrokersAndBridges\mis.logMetabrokers and Bridges Log File
<IS_HOME>\Clients\MetaBrokersAndBridges\Bridges*\conf\ MIRSetup.xmlMetabrokers and Bridges Setup File
<IS_HOME>\Clients\MetaBrokersAndBridges\Bridges*\conf\ MIRModelBridges.xmlMetabrokers and Bridges parameter values file
<IS_HOME>\Clients\MetaBrokersAndBridges\bin\mis.cfgMetabrokers and Bridges Configuration File
<TEMP>\*.xmlMetabrokers and Bridges Configuration Files
<TEMP>\imam\**\*.xmlMetabrokers and Bridges Configuration Files
To turn on additional debugging information in Metabrokers and Bridges, set the environment variable DEBUG_IBMWDIS to a user-defined string value that will be used as prefix in the filename of the output log files and then reproduce the problem. Additional debugging information will be produced in the following artifacts:
Files and Data to collect
Description
<TEMP>\<DEBUG_IBMWDIS>MIMB.logMetabrokers and Bridges Log File
<TEMP>\<DEBUG_IBMWDIS>XML_Decoder.xml_Dump.xml 
<TEMP>\<DEBUG_IBMWDIS>XML_Decoder.xml 
<TEMP>\<DEBUG_IBMWDIS>Filterhub* 
<TEMP>\<DEBUG_IBMWDIS>TempHub.hub 

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