Configuring after upgrade

The post-upgrade activities that you might consider are the same as post-installation activities. If you have already performed these configuration steps, they are retained on upgrade and do not need to be repeated. 

Example post upgrade messages

Depending on the version and configuration of the system before upgrading, some of the following steps may be displayed:

Review patterns flagged by the upgrade

The upgrade flags any pattern modules that refer to the old (before BMC Discovery 11.0) data model and therefore need changes to continue to work correctly. Flagged TKU patterns are addressed by activating the new TKU. However, flagged custom patterns require manual review to decide what changes are required.

The Knowledge management page lists pattern modules flagged by the upgrade. If no modules are listed then no action is required. Any listed modules show the errors and/or warnings generated by the upgrade when patterns were compiled. Depending on the severity of the compile messages, pattern modules can be left enabled or disabled. However, all messages should be reviewed to avoid future issues with your patterns. Pattern modules and packages should be updated in the usual way for your environment; either by editing via the user interface or by uploading a new version.

Any pattern packages that you do not wish to update immediately can be deactivated and will no longer be listed. Alternatively, any pattern packages that are no longer required can be deleted.

CMDB sync mappings

The structure of the CMDB sync mappings changed in BMC Discovery 11.0 so you must consider any extensions to existing mappings. The mapping position they extend from may have changed. The syncmapping versions have been incremented and the knowledge management system will require that you review modules flagged by the upgrade before you can activate patterns.

Before you can activate patterns you must edit the syncmapping extensions. In most cases, you only need to update the version number of an import, but more complex extensions may require more rework because the underlying mappings are quite different.

Activate new TKU

The upgrade installs a new TKU package but does not activate it. You must activate the new TKU before performing discovery. Information on activating and deactivating TPL packages is available here.

CMDB sync filters 

The CMDB synchronization mechanism was changed in version 10.2 and most filters created using previous versions will no longer work. The filters may be in one of the following states:

For further information, see Recreating legacy filters.

CSV and XML web API access

The permission required to access the CSV and XML API has changed in BMC Discovery version 11.1. You must grant the new API access permission (api_access_group) to users who require access to the CSV and XML web APIs.

Export mapping sets

The upgrade checks whether there is a newer version of each of the installed mapping sets. If a mapping set has changed since the last version, either by the user modifying it or BMC releasing a newer version, then a warning is displayed to the user. The original mapping is renamed by the upgrade to append ".old" to the mapping set descriptor (the file ending with ".properties") and "_old" to the directory containing the mapping files. You can either:

  • Ignore the warning if the export framework is not being used.
  • Compare the old mapping set to the new one and keep the new one (that is, do nothing).
  • Compare the old mapping set to the new one and decide to keep the old one, in which case the user needs to manually delete the newer mapping descriptor and directory and rename the old ones (removing the .old and _old postfixes).
  • Compare the old mapping set to the new one and merge the changes. If the changes to the mapping set have been performed by BMC Software then these changes will be listed in the release notes and the user can apply these changes manually to their own copy of the mapping set.
Was this page helpful? Yes No Submitting... Thank you

Comments