Empty list of events in Federated Details dialog

A first step to troubleshoot this issue is to disable the Ignore on Error check box on the interaction for the SCCDOMNIBUS provider.

1. Go to Integration > OSLC Providers.
2. Under More Actions, select Add/Modify Interaction Group.
3. Select SCCDCIGRP, the CI Interaction Group.
4. Expand the CCIEVENTS interaction on the Interactions tab.
5. Clear the Ignore on Error? check box.
6. Select OK.
7. Go back to the place where you selected View Federated Details and select it again. If the dialog still does not display events and no error occurs, continue to the next paragraph. If an error occurs, consult the other troubleshooting topics for information about the error.

There are several reasons why the Federated Details dialog does not display events for the CI:

• The Tivoli Netcool/OMNIbusendpoint is configured for basic authorization but the credentials for the endpoint are incorrect or empty.
• There is not enough data to satisfy any of the event queries for the particular CI. Each CI that you want to view events for must contain enough information to satisfy at least one of the event queries.
• You are requesting events for a CI whose classification is mapped to the EVENT resource type, but no events have been created for that CI.

Make sure the Tivoli Netcool/OMNIbus endpoint credentials are correct.

1. Go to Integration > OSLC Providers
2. Open SCCDOMNIBUS, the Tivoli Netcool/OMNIbus provider.
3. Open the endpoint by clicking the >> menu next to the End Point field, and selecting Go To End Points.
4. Enter the basic authorization credentials in the USERNAME and PASSWORD fields and save the endpoint.
5. Click Return with value.

If the endpoint credentials are correct or basic authorization credentials are not required, enable Debug for the logs:

• log4j.logger.maximo.oslc
• log4j.logger.maximo.application.ccmdb.pmcci
• log4j.logger.maximo.integration

The logs provide details on the queries that ran, their validations, and the values for each query parameter in each query. The logs aid in determining which queries failed, whether certain CI classifications were not mapped to EVENT resource types, and so on.

1. Go to System Administration > Platform Configuration > Logging.
2. Enable debug forlog4j.logger.maximo.oslc.
   1. Filter on oslc.
   2. Set the Log Level of log4j.logger.maximo.oslc to Debug.
   3. Make sure the Active check box is selected.
   4. Select the action, Apply Settings.
3. Enable debug for log4j.logger.maximo.application.ccmdb.pmcci.
   1. Filter on ccmdb.
   2. In the Loggers section, set the Log Level of log4j.logger.maximo.application.ccmdb.pmcci to Debug.
   3. Make sure Active is selected.
   4. Select the action, Apply Settings.
4. Enable debug for log4j.logger.maximo.integration.
   1. Filter on integration.
   2. In the Loggers section, set the Log Level of log4j.logger.maximo.integration to Debug.
   3. Make sure Active is selected.
   4. Select the action, Apply Settings.
5. Repeat the action that you took to view event details.
6. Check the server logs.
7. Search for the CCIOslcQueryClause canExecute and getResolvedWhere entries.
   Note: You can also search the log for a particular Configuration Item.
   • If a CI does not contain the needed information, the Tivoli Netcool/OMNIbus events will not be queried, and the canExecute entries explain why.
   • If a CI contains the needed information, the getResolvedWhere entries identify the query that was used to find matching events in Tivoli Netcool/OMNIbus.
8. Search for a result set dump file in the log, which is an XML file name that contains the results from Tivoli Netcool/OMNIbus. Open the XML file to view the data that was returned for the query that was run.