In the Spotlight June 2012

In TKU June 2012 we have developed new pattern modules for certain products and enhanced existing ones. One such substantially enhanced pattern module in this release is for SAP.

Prior to TKU June, should ADDM encounter two or more distinct SAP systems sharing a common SAP System ID, such distinct SAP systems would have been merged together at the 2nd order SAP Suite Software Instance level. From TKU June, this is no longer the case as the host that the SAP Message Server is running on is now taken into account.

Every component within a distributed SAP system will have its own profile file containing entries such as 'rdisp/mshost' or 'SAPGLOBALHOST' whose value (be it a host name, IP address or SAP internal name) uniquely identifies the host where the SAP Message Server is running.

The two screenshots above clearly show that even though the two SAP systems share a SAP System ID of 'SI4', the SAP Message Server of the first is running on host 137.72.95.62 (tku1.bmc.com) and the second on host tku4 (137.72.95.63).

By storing both the SAP System ID and the message server host as attributes on each SAP component Software Instance, when ADDM comes to collate SAP components to include in a 2nd order SAP Suite Software Instance, it can simply ensure that the SAP System ID and the message server host of each SAP component match those of the SAP Message Server the SAP Suite pattern triggered off.

The two screenshots above show that the first 2nd order SAP Suite Software Instance is comprised of only those SAP components on hosts tku1 and tku2 and the second comprised only of those on tku3 and tku4.