http://communities.bmc.com/communities/community/bmcdn/bmc_atrium_and_foundation_technologies/discovery

The January release includes 6 new products taking the total to 369 software products and over 29,000 software product configurations discoverable.

The release focuses on extending discovery coverage of BMC products and includes patterns for:

• BMC Atrium CMDB
• BMC BladeLogic Client Automation
• BMC CONTROL-M/CM for Advanced File Transfer
• BMC Patrol Enterprise Manager
• BMC ProactiveNet Analytics
• Remedy AR System

You can visit the In the Spotlight page on Configipedia to find out more about the release so you can confident in the discovered results returned.

The December release includes 8 new products taking the total to 364 software products and over 29,000 software product configurations discoverable.

The release focuses on extending discovery coverage of BMC products , particularly the CONTROL-M family.

You can visit the In the Spotlight page on Configipedia to find out more about the release so you can confident in the discovered results returned.

The November release includes 13 new products taking the total to 356 software products and over 29,000 software product configurations discoverable.

The release focuses on extending discovery coverage of IBM products specifically to support license audit initiatives and provides broad coverage across the all the major IBM software product brands such as:

• Cognos
• DB2
• FileNet
• Infosphere
• Rational
• Tivoli
• Websphere

To ensure quality, pattern developers leverage our relationship with IBM by either accessing product expertise or accessing products in IBM Innovation Center labs.

You can visit the In the Spotlight page on Configipedia to find out more about the release so you can confident in the discovered results returned.

Why is it important to track software going end of life? Here’s a few reasons Tideway customers tell us why they are using Foundation to track software nearing end of life.

• Identify operating systems and software that are exposed to security / stability risks as they are no longer supported by patch updates
• Identify operating systems and software that we may be paying a premium maintenance subscription for
• Identify operating systems and software that are no longer shipping may lead to increased costs and risks associated with variance

Products Reaching End Of Life In November 09

• HP Client Automation 4.2, 5.0
• HP DevInspect 4.0, 5.0, 5.1
• IBM Tivoli Netcool/OMNIbus 7.0

Products Reaching End Of Life In December 09

• Borland StarTeam v9.0
• CA Directory v8.1
• Ingres Ingres Database v2.6
• McAfee VirusScan Enterprise v8.0
• MySQL AB MySQL Database Server v5
• Oracle Berkeley DB v4.3
• Oracle Database Lite v10.2
• Sybase Adaptive Server Enterprise v12.5
• Sybase jConnect for JDBC v5.5
• Sybase Replication Server v12.6
• VMware Consolidated Backup v1.1
• VMware VirtualCenter v2.5
• VMware High Availability v2.5
• VMware VMotion v2.5

Go to Oracle October CPU web page

Oracle recommend that organizations “have a complete inventory of Oracle products across the IT enterprise, with full version numbers” however do not appear to have a solution for this. As a result we hear that many organizations are unable to apply the CPUs and as a result are exposing themselves to critical security vulnerabilities.

Follow these links to the find out more about how Tideway identifies Oracle Application Server , Oracle Database , E-Business Suite , Weblogic and JRockit inventories.

Or why not try out Tideway Foundation by downloading the Community Edition

Steve

The October release includes 14 new products taking the total to 343 software products and over 28,000 software product configurations discoverable.

The release particularly helps customers with the following:

• Symantec Veritas discovery for license audits – with enhancements to license key discovery and discovery of NetBackup Agents
• IBM discovery for license audits – with patterns for 7 additional products taking the total to 81 IBM products discoverable by Tideway
• Microsoft discovery for license audits – with patterns for 4 additional products taking the total to 30 Microsoft server products discoverable by Tideway
• Management of virtualized environments with the discovery of Oracle VM and Oracle VM Parallels Virtuzzo Containers

You can visit the In the Spotlight page on Configipedia to find out more about the release.

We’re going to start from the SAP Application Server, then explain the modeling of an SAP Suite instance, and finally go in-depth, into the Database queries that we employ, and how we interpret their results.

SAP Application Server

The first step is taken when the SAP Application Server is recognized as running on a given host. This is the case when Tideway discovers the sapstartsrv.exe or sapstartsrv process running. The pattern will then parse the process arguments, and will infer:

Instance Name: The instance of the running Application Server
System Name: The SAP SID, or name of the SAP system
Profile Directory: the directory containing the configuration profiles

This is an example of the process arguments: pf=C:\usr\sap\SBX\SYS\profile\START_DVEBMGS01_SALSA

This is the code that allows these attributes to be retrieved:

if “args” in process then
    instance_name := regex.extract(process.args, regex '(?i)pf=.*(?:/|\\)START_([^_]*)_',
                                   raw ‘\1’);


    system_name := regex.extract(process.args,
                                 regex “(?i)[/\\]([^/\\]+)[/\\]SYS[/\\]profile[/\\]”,
                                 raw “\1”);

    profile_dir := regex.extract(process.args,
                                 regex “(?i)pf=(.*[/\\])START_”,
                                 raw “\1”);
end if;

The pattern will then proceed to model an SAP Application Server Software Instance. Afterwards, it will retrieve 3 configuration profiles:

Default Profile: a profile common to all the SAP Application Servers belonging to the same System (SID). Example filename: DEFAULT.PFL
Instance Profile: a profile unique to the specific Application Server instance. Example filename: SID_INSTANCE_HOSTNAME
Startup Profile: a profile unique to the specific Application Server instance, containing Startup information. Example filename: START_INSTANCE_HOSTNAME

Each file is stored in a File Node, and linked directly to the relevant SAP Application Server Software Instance. The Default Profile is going to be especially useful in identifying which Database is supporting the SAP Suite instance. This is the Database that we’re going to query, and collect relevant data from.

The following is the code that allows the Instance Profile file to be retrieved, stored as a File Node, and linked to the SI. Note that system_name, instance_name and profile_dir, the key variables which allow us to retrieve the file location and name, were all retrieved from the process arguments, in the code section illustrated above.

if system_name then
    instance_profile_relative_path := “system_name_%instance_name%_%host.name%”;
    instance_profile_path := “profile_dir%instance_profile_relative_path%”;
    log.debug(“Going to extract the following file: instance_profile_path.”);


    instance_profile_file := discovery.fileGet(process,
                                               “instance_profile_path“);

    if not instance_profile_file then
        instance_profile_relative_path := text.upper(instance_profile_relative_path);
        instance_profile_path := “profile_dir%instance_profile_relative_path%”;
        log.debug(“Going to extract the following file: instance_profile_path.”);
        instance_profile_file := discovery.fileGet(process,
                                                   “instance_profile_path“);
    end if;

    if instance_profile_file and “content” in instance_profile_file then
        if_node := model.File(key := “instance_profile_path/%host.key%”,
                              type := “SAP Instance Profile”,
                              name := “File instance_profile_path on host.name“,
                              path := instance_profile_path,
                              size := instance_profile_file.size,
                              md5sum := instance_profile_file.md5sum,
                              last_modified := instance_profile_file.last_modified,
                              content := instance_profile_file.content);

        file_list := file_list + [if_node];
    end if;
end if;
[…]
if file_list then
    model.rel.RelatedFile(ElementUsingFile := app_si, File := file_list);
    log.debug(“Profile File(s) related to app_si.name.”);
end if;

Note: the 3 profile files are stored in a File Node, so that they are easily browsable and readable. Should you want to extract specific information from them, and store them in a specific attribute, please let us know.

Identifying the supporting Database

The pattern responsible for modeling the SAP Suite Software Instance triggers as soon as the SAP Application Server SI is modeled.

This pattern retrieves the Default Profile file – which was stored as a File node – and extracts DB location from it.

This is the code used to retrieve the Default Profile file from the SAP Application Server SI:

default_profile_files := search(in sap_app_si traverse ElementUsingFile:RelatedFile:File:File where type = “SAP Default Profile”);


	
for dpf in default_profile_files do
    if dpf and “content” in dpf then
        default_profile_file := dpf;
    end if;

end for;

These are the attributes that are extracted:

j2ee/dbtype: the DB type. We are currently supporting MS SQL DB and Oracle DB. Work for IBM DB2 is under way
j2ee/dbhost: the Hostname where the DB is running
j2ee/dbname: the DB Name or SID, depending on the DB type.

These attributes are extracted using the following code:

db_type_short := regex.extract(default_profile_file.content,
                               regex “j2ee/dbtype *= *(\S+)”,
                               raw “\1”);

db_type := DBTypes[db_type_short];

log.debug(“DB Type: db_type.”);


	
if db_type = “MS SQL” then
    db_host := regex.extract(default_profile_file.content,
                             regex “j2ee/dbhost *= *(\S+)”,
                             raw “\1”);
    log.debug(“DB Host: db_host.”);

    db_name := regex.extract(default_profile_file.content,
                             regex “j2ee/dbname *= *(\S+)”,
                              raw “\1”);
[…]
elif db_type = “Oracle” then
    db_host := regex.extract(default_profile_file.content,
                             regex “j2ee/dbhost *= *(\S+)”,
                             raw “\1”);
    log.debug(“DB Host: db_host.”);
    db_sid := regex.extract(default_profile_file.content,
                            regex “j2ee/dbname *= *(\S+)”,
                            raw “\1”);
[…]
end if;

The pattern will then perform a search for Software Instances of a specific DB Type, with a specific Name/SID, and running on a specific Host, based on the retrieved attributes.

Querying the Database

Once the DB location is known, the pattern retrieves the port that the DB is listening on. The first place it looks in is the port attribute in the DB Software Instance. If that attribute isn’t present, the pattern looks for the value entered in the SAP Configuration Section for the pattern. The value in this section is defined by the user.

After the port is known, the pattern proceeds to run a set of queries. We’re reporting the 3 most relevant of them.

Versioning Query

select * from CVERS_TXT

This query returns the version of SAP Suite, and it also returns the application/system type that is running. Typical examples are: ERP, CRM, Netweaver…

Licensing Query

select * from MLICHECK

This query returns Licensing data for an SAP Suite instance. The attributes returned are:

• License Key
• Start Date
• Expiration Date
• Max Users allowed

This is an example of a Licensing Query call from the pattern:

if db_type = "MS SQL" then
    rows := MSSQLQueries.LicensingQuery(endpoint := remote_db_server,
                                        port := port,
                                        database := db_name);
elif db_type = "Oracle" then
    rows := OracleQueries.LicensingQuery(endpoint := remote_db_server,
                                         port := port,
                                         sid := db_name);
else
    rows := none;
end if;

All the resulting data is stored in a Licensing Detail, which is linked to and easily accessible from the SAP Suite Software Instance.

Components Query

select * from CVERS

This is a key query: it returns a list of all the installed components in an SAP Suite instance, such as EA-FINSERV (Financial Services) and EA-HR (Human Resources). This should make the purpose of an SAP Suite instance immediately clear to the user. The query is also going to return Release and Extended Release.

The attributes returned from the Components Query are initially stored in a list, using this code:

if rows then
    for row in rows do
        components := components + [["%row.component%", "%row.release%", "%row.extrelease%", ""]];
        log.debug("Component: %row.component%, Release: %row.release%, Ext Release: %row.extrelease%");
    end for;
end if;

Note: The empty string at the end of the list will be later filled in with the results from another query, which returns a description for each component.

Subsequently, each component is modeled into a Detail Node, using the following code:

for component in components do
    if component[0] then
        dt_name := component[0];
        dt_type := “Installed Software Component”;
        dt_key := “dt_name/%dt_type%/%sap_si.key%”;


        component_dt := model.Detail(key := dt_key,
                                     type := dt_type,
                                     name := dt_name,
                                     release := component[1],
                                     extended_release := component[2]);

        if component[3] then
            component_dt.description := component[3];
        end if;                         

        component_dt_list := component_dt_list + [component_dt];
    end if;
end for;

Finally, the modeled Detail Nodes are related to the SAP Suite Software Instance:

model.rel.Detail(ElementWithDetail := sap_si, Detail := component_dt_list);
log.debug("Components added as Details to %sap_si.type% SI.");

Conclusions

This approach models an instance of SAP Suite, comprising its supporting Application Servers and Database, its license key, and installed software components. It encloses them in an organic model, which is easily browsable from the Tideway UI.

For a more comprehensive description and outline of the pattern, please refer to the SAP Business Suite Configipedia page.

For a more problem oriented view, please refer to the SAP Business Suite Discovery Capabilities from Tideway Foundation blog.

Edoardo L’Astorina

Why is it important to track software going end of life? Here’s a few reasons Tideway customers tell us why they are using Foundation to track software nearing end of life.

• Identify operating systems and software that are exposed to security / stability risks as they are no longer supported by patch updates
• Identify operating systems and software that we may be paying a premium maintenance subscription for
• Identify operating systems and software that are no longer shipping may lead to increased costs and risks associated with variance

Products Reaching End Of Life In October 09

• HP Data Protector Cell Server Database Service 5.5
• HP Data Protector Cell Manager Service 5.5
• HP Data Protector Media Management Server 5.5
• HP Data Protector Backup Session Manager 5.5
• HP Data Protector Restore Session Manager 5.5
• HP Data Protector Client Backup Service 5.5
• HP Data Protector Backup Media Agent 5.5
• HP Data Protector Restore Media Agent 5.5
• HP Data Protector Backup Disk Agent 5.5
• HP Data Protector Restore Disk Agent 5.5
• Red Hat JBoss Rules 4.0

Products Reaching End Of Life In November 09

• HP Client Automation 4.2, 5.0
• HP DevInspect 4.0, 5.0, 5.1
• IBM Tivoli Netcool/OMNIbus 7.0

This new functionality allows Tideway to address critical SAP related problems such as Change Impact produced by a Data Center Move and License Management.

Approach to Understanding the Product
Following our previous work with Oracle E-Business Suite, we continued to expand our coverage of business applications by working on SAP Business Suite.

The approach that we employed was very similar: a combination of Tideway internal expertise, and external Subject Matter Experts. In this particular case, we worked side by side with QuestAM, who provided us with invaluable data, guidelines, and a test lab for the development and final testing of our work.

Tideway Capabilities for SAP Business Suite Mapping
Tideway is able to identify an instance of SAP spread across multiple hosts in your estate, and supported by multiple Application Servers. Tideway will also indicate the location of the supporting Database for each SAP instance. Currently supported DBs are: Microsoft SQL Server & Oracle Database Server. Support for IBM DB2 is under development.

The functionality described above are performed by Tideway in a normal Discovery, where only host credentials are supplied. Once the supporting Databases are singled out, a user can provide Tideway Foundation with Credentials for those DBs, thus allowing for a much deeper Discovery to take place.

After logging into the Database, Tideway will execute a set of DB Queries, which will return valuable data. It will return version-related data, like SAP Version, Release, and Type (ie. ERP, CRM, Netweaver…).

The DB Queries will also return Licensing Data, like License Key, License Expiry Date & Maximum Users allowed. This data is particularly interesting in view of a License Audit.

Finally, the DB Queries will return a list of Installed Components, which can clearly identify the use which a given SAP Instance is intended for (ie, EA-FINSERV for Financial Services, EA-HR for Human Resources…). The ability to distinguish among different Components of SAP is a great advantage in a Data Center Move/Upgrade, as it allows to understand which Applications are going to be affected by shutting specific hosts down.

In conclusion, whether your goal is preparing for a License Audit, preventing outages caused by change, or performing a discovery & software mapping of your Data Center, Tideway Foundation is an excellent tool that will make you aware, in just a few steps, of your SAP deployment across your estate.

For a visual explanation, please refer to the In the Spotlight page on Configipedia. For a more detailed technical explanation, please refer to the SAP Business Suite product page.

Tideway is always interested in understanding where the highest demand for product mapping lies. Would you be interested in seeing more Business Applications mapped like SAP Business Suite? Is your main focus on PeopleSoft? Or Siebel? Or something else? Please do not hesitate and let us know.

Edoardo L’Astorina