This documentation supports the 9.1.04 version and its patches of BMC Atrium Core. The documentation for version 9.1 to 9.1 Service Pack 3 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Contents of the logs

Log entry details

Each entry in the log provides the following details:

  • Thread — The thread that the transaction used when the message was generated.
  • Timestamp — The date and time of the log entry.
  • Log Type — The type of log entry:
    • Error — Logs detailed messages for errors and warnings (default).
    • Info — Logs class-level details, such as dataset name and class name.
    • Debug — Logs trace messages, which are used for debugging errors.
      All these logging levels are inclusive of their preceding levels. For example, if you set the Logging Level at Debug, you receive log messages for Error, Info, and Debug types. You can specify the Logging Level for the log files from the Modify Server Configuration window of the Reconciliation Engine Console.
  • Message — The message for the log entry (classified into error, warning, and information categories).


The conversion pattern in a log file defines the order and types of information that are included in a log event.

For example, if the conversion pattern is:
%d %-5p [%t] %C (%F:%L) - %m%n

d stands for the date of the logging event.
p is the priority of the logging event.
t is the name of the thread the generated the logging event.
C stands for the fully qualified class name of the caller issuing the logging request.
F is the file name where the logging request was issued.
L is the line number from where the logging request was issued.
m is the application supplied message associated with the logging event.
n is the platform dependent line separator character or characters.

Log levels

You can set various log levels in BMC CMDB depending on the troubleshooting scenario. Log levels determine the types of messages that are logged for the calls. The following different types of log levels are available in BMC CMDB. 

All these logging levels are inclusive of their preceding levels. For example, if you set the Logging Level at Debug, you receive log messages for Error, Info, and Debug types. 

Level

Description

Fatal

Logs the events that may lead the application to abort.

Error

Logs the events in which application continues to run with some errors.

Warning

Logs the events that are potentially harmful situations.

Info

Logs events and calls that highlight the progress of the application at high level. This level includes results of the events and calls.

Debug

Logs the events and calls that are useful to debug an application. This level includes input and output values.

Trace

Logs the events without disturbing a running system. Trace-level logging can be useful in resolving issues in a production environment.

This level includes trace information.
ClearLogging is disabled.

Logs for core CMDB components


The logging for the core CMDB components such as the CMDB Engine, Normalization Engine, and Shared Plugins is enabled by default. Using this configuration, you can eliminate the downtime while enabling detailed logs.

You can access the logging settings in the Logging section of each core component at Configurations > Core Configurations.


Notes

  • No file system access is required for making any configuration changes.
  • For any change to logging configurations to take effect you do not need to restart the BMC Remedy AR System server.

The following is a sample CMDB Engine debug log file:

<ERROR > <TrID: 182hsvghTK62p5yZjAeLMg:0000026> <TID: 0000000345> <User: Remedy Application Service > /* Tue Jul 09 2019 11:01:48.076 */     [ com.bmc.arsys.domain.etc.ARException ] Error encountered during CMDB Get Dataset: ERROR (120121): Dataset is not found.; BMC.AE.SB.Demo.1
	at com.bmc.cmdb.server.service.impl.CacheServiceImpl.getDatasetById(CacheServiceImpl.java:1153)
	at com.bmc.cmdb.server.facade.impl.GenericFacadeImpl.getDataset_aroundBody16(GenericFacadeImpl.java:151)
	at com.bmc.cmdb.server.facade.impl.GenericFacadeImpl.getDataset_aroundBody17$advice(GenericFacadeImpl.java:42)
	at com.bmc.cmdb.server.facade.impl.GenericFacadeImpl.getDataset(GenericFacadeImpl.java:1)
	at com.bmc.cmdb.server.platform.internalapi.impl.ApiImpl.getDataset(ApiImpl.java:330)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
	at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
	at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:136)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
	at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
	at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
	at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:136)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
	at com.sun.proxy.$Proxy217.getDataset(Unknown Source)
	at com.bmc.cmdb.services.dataaccess.impl.RepositoryServiceImpl.getDataset(RepositoryServiceImpl.java:794)
	at com.bmc.cmdb.services.dataset.dataaccess.impl.DatasetDataAccessServiceImpl.getDataSet(DatasetDataAccessServiceImpl.java:191)
	at com.bmc.cmdb.services.dataset.impl.DatasetServiceImpl.getDataSet(DatasetServiceImpl.java:118)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)

The following is a sample CMDB client-side Java API log file:

Jul 25 2019 21:10:08.613 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.initialization() :: initialization() - Begin 
Jul 25 2019 21:10:08.614 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getServerCharSetName() :: getServerCharSetName()
Jul 25 2019 21:10:08.614 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getServerCharSetName() :: 1 :: getArRpcCallContext() return ArRpcCallContext
Jul 25 2019 21:10:08.614 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - Begin getRpcClient()
Jul 25 2019 21:10:08.614 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - End getRpcClient()
Jul 25 2019 21:10:08.615 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.initialization() :: initialization() - End 
Jul 25 2019 21:10:08.615 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - initialization() - Done
Jul 25 2019 21:10:08.615 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - End getRpcClient()
Jul 25 2019 21:10:08.615 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getServerCharSetName() :: getServerCharSetName()
Jul 25 2019 21:10:08.615 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getServerCharSetName() :: 1 :: getArRpcCallContext() return ArRpcCallContext
Jul 25 2019 21:10:08.615 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - Begin getRpcClient()
Jul 25 2019 21:10:08.615 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - End getRpcClient()
Jul 25 2019 21:10:08.625 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - Begin getRpcClient()
Jul 25 2019 21:10:08.625 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - End getRpcClient()
Jul 25 2019 21:10:08.625 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - Begin getRpcClient()
Jul 25 2019 21:10:08.626 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - End getRpcClient()
Jul 25 2019 21:10:08.626 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - Begin getRpcClient()
Jul 25 2019 21:10:08.626 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - End getRpcClient()
Jul 25 2019 21:10:08.626 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - Begin getRpcClient()
Jul 25 2019 21:10:08.626 DEBUG [Thread-4] (                          ?:?    ) - <TrID: 1Y5lJA9sSKqAsuwON4ftQQ:0000002> CMDBProxyJRpcBase.getRpcClient() - End getRpcClient()

You can perform all the Atrium CMDB configurations by using Centralized Configuration System (CCS). For more information, see  Centralized configuration


Reconciliation job log


The Reconciliation Engine logs all activities that it performs: Identification, Compare, Merge, Delete, and Purge. A log file for a job is created each time the Reconciliation Engine runs that job. The Reconciliation job logging is enabled by default.


The Reconciliation job logging topic provides information about log details, naming conventions, viewing events, and interpreting log entries.

Log file naming convention

The Reconciliation job log files use the following naming convention: 
jobName_ctr.log 

jobName is the name of the job that you created in the Reconciliation Manager (for example, BMCAsset - Identification and Purge). 

ctr is a numeric value that starts from 1 and is incremented when a new log file is created for the job run. The Reconciliation Engine continues to log errors in a new log file when an existing log reaches its size limit. 

For example, if multiple files are created for the BMCAsset - Identification and Purge job run, the job log files will be named as:

  • BMCAsset - Identification and Purge_1.log
  • BMCAsset - Identification and Purge_2.log

BMC Atrium Core Console server-side logging

The BMC Atrium Core Console server-side processing is recorded in the mid tier and application server logs. The mid tier log file location depends on the application sever that you have installed.

For example, for an Apache Tomcat application server installed on the mid tier, the log is stored in the BMC Remedy Action Request System serverInstallation/tomcat/logs/stdout_currentDate.log file. Mid tier logs are located in the AR System serverInstallation/mid tier/logs subdirectory of the AR System installation.

For more information about mid tier logging, see BMC Remedy Mid Tier logging in the BMC Remedy AR System online documentation.

For more information about application server logging, see BMC Atrium Core web services deployment logs.

BMC Atrium Core Console client-side logging

BMC Atrium Core logs the BMC Atrium Core Console client-side processing in the flashlog.txt file, which helps you to debug user interface errors. To log the client-side processing, install and configure the 7, 0, 14, 112 or newer version of Adobe Flash Player Debugger. The BMC Atrium Core Console requires a minimum of Adobe Flash Player version 9 to run.

Note

The Adobe Flash Player log combines messages from all its instances running on your computer. For example, if you were running two instances of Adobe Flash Player with CNN.com and BMC Atrium Core each on the same computer, you might find intermixed log messages from both these instances.

To determine your Adobe Flash Player Debugger version

Use the following methods to determine the version of the Adobe Flash Player Debugger that you have installed. If the version you determined using each method differs, the debug logging might encounter issues. In such a case, uninstall all versions of the Adobe Flash Player Debugger and install again. 

Determining Adobe Flash Player Debugger version

Using this component

Perform these steps

BMC Atrium Core Console

Right-click inside the BMC Atrium Core Console and select About Adobe Flash Player version.
The version of the Adobe Flash Player installed is displayed, but this will not distinguish between the release and debug player.|

Adobe website

  1. Go to http://helpx.adobe.com/flash-player/kb/find-version-flash-player.html. Follow the steps give on this page to install the Flash player, if you do not have one.
  2. http://helpx.adobe.com/flash-player/kb/configure-debugger-version-flash-player.html Follow the steps given on this page to install the download the debugger version of Flash Player.

Note: Adobe moves this content occasionally. You can usually find the new location by searching for "debug flash player" with Google or equivalent search engine.  

To configure your Adobe Debug Flash Player Debugger

When you install BMC Atrium Core, the following files are copied to the webapps directory of your installation for the client-side logging:

  • Readme.txt — Contains information about downloading, installing, and configuring the Adobe Flash debugger.
  • mm.cfg — Contains the configuration information to enable logging on the client side. Copy this file to the location specified in the readme.txt file for your operating system.
    The location of the flashlog.txt log file depends on your operating system, as listed in the following table. 

    Log file location by operating systems

    Operating system

    Log file location

    Windows 95, Windows 98, Windows ME, Windows 2000, Windows XP

    C:\Documents and Settings\<userName>\Application Data\Macromedia\Flash Player\Logs

    Windows Vista

    C:\Users\<userName>\AppData\Roaming\Macromedia\Flash Player\Logs

    Apple Macintosh OS X

    /Users/<userName>/Library/Preferences/Macromedia/Flash Player/Logs/

    Linux

    /home/<userName>/.macromedia/Flash_Player/Logs/


Was this page helpful? Yes No Submitting... Thank you

Comments