Release notes

The SSH library Mindterm used in TADDM has been replaced with Apache Mina SSHD library as Mindterm was EOL from January 2022. Apache Mina SSHD is a 100% pure java library to support the SSH protocols. This change is abstract to end user and requires no new configurations at their end.

TADDM Fixpack 11 will support ED25519 key based authentication. Earlier, key-based login was supported for RSA or DSA keys only.

Key-based authentication, also known as public key authentication, is a method used for securely authenticating users to a system, server, or application without the need for traditional passwords. It relies on cryptographic key pairs instead of passwords to establish identity and grant access. Refer to the link, Configuring for Discovery using the Secure Shell (SSH)

TADDM Fixpack 11 will support Future Crypto Policy using RSA keys enabled in RHEL8 and above versions for discovery and utilizing the Apache Mina SSHD library.

TADDM Fixpack 11 will support DB2 JDBC driver V 4.25.29.

If the property is set to true, then DB2 JDBC driver will be updated to the version 4.25.29.

If the property is set to false, then, the DB2 JDBC driver version will remain same (as previous version) after successful migration.

The TADDM ServiceNow Integration plugin has been extended to support the Utah release of ServiceNow. For more details on how to integrate TADDM with ServiceNow, see Integrating TADDM with ServiceNow.

TADDM has removed the dependency on 32-bit libgcc required to be present on RHEL operating systems to be used for TADDM installation.

Users can now install and use TADDM Fixpack-10 on the RHEL-9 operating system without the 32-bit libgcc library.

Also libXft.so.2 library is also not required on the RHEL-9 operating systems to be used as TADDM installation server.

For Log4j, an enhancement has been introduced to upgrade it from Log4j1 to Log4j 2.17.2 as it provides significant security improvements.

Log4j2 allows Lookup expressions in the data being logged exposing the JNDI vulnerability, as well as other problems, to be exploited by end users whose input is being logged.

When TADDM is upgraded to 7.3.0.10, a backup file, deploy-tomcat_7.3.0.x is left over which contains some unused references to the log4j version 1 JAR file. To remove unused references to log4j version 1, refer to https://www.ibm.com/support/pages/node/6986553.

The CheckDiskFailures module is now added with a filter option to skip the data based on duration and this helps to skip the data for a given year, date, and range of date and year.

For more details on CheckDiskFailures module, see Healthcheck Program topic in the Troubleshooting Guide.

The TADDM ServiceNow Integration plugin has been extended to support the San Diego version of ServiceNow. For more details on how to integrate TADDM with ServiceNow, see Integrating TADDM with ServiceNow.

• When extracting the fixpack .zip file on RHEL based system, using the native unzip command might give the following error:

  invalid zip file with overlapped components (possible zip bomb)

  If the above error occurs, extract the .zip file using one of the following ways:

  • Rerun the native unzip command after setting the environment variable UNZIP_DISABLE_ZIPBOMB_DETECTION=TRUE
  • If the above option is not supported in the native unzip, then use the jar executable present in the TADDM installation directory.

    <taddm_installation_directory>/dist/external/jdk-Linux-x86_64/bin/jar xf fixpack.zip

• Windows Discovery Server and Windows Anchor requires PowerShell 5.1 or later to be present on them.

For the Oracle Sensor to discover the Oracle database you must add the name of the compatible JDBC driver file to the Bundle-ClassPath entry in the MANIFEST.MF file. For more details, refer to Copying the JDBC driver.

In previous TADDM fix-packs, the Oracle sensor uses only the first JDBC driver, listed in the Bundle-ClassPath entry, for the discovery of the Oracle database but it was not using other listed JDBC drivers for the discovery of the Oracle database.

TADDM 7.3.0.9 enhances the Oracle sensor searching capabilities and now it uses all the JDBC drivers, listed in the Bundle-ClassPath entry, for the discovery of the Oracle database. If the first JDBC driver, listed in the Bundle-ClassPath entry, does not make a connection with the Oracle database, then searching will be done using other listed JDBC drivers automatically and the Oracle database gets discovered if it is compatible with any of the JDBC driver that is listed in the Bundle-ClassPath entry in the MANIFEST.MF file.

For more details on the collation properties, see Configuring the collation.properties file entries.

TADDM ServiceNow Integration plugin has been extended to support the Quebec version of ServiceNow. For more details on how to integrate TADDM with ServiceNow, see Integrating TADDM with ServiceNow.

Mapping RedHat Pacemaker cluster information to ServiceNow

TADDM ServiceNow integration plugin has been enhanced and configured to map the pacemaker cluster objects with ServiceNow.

For more details on the supported CI list, see Appendix D: Supported CI list.

For the Microsoft IISServerSensor, an enhancement has been introduced to discover Application Pool details of the Microsoft IIS Web servers.

Discovered application pools will be displayed under a new Application Pool tab in the Details panel view of the IIsWebService component. A relationship between web sites and the Application Pool is also maintained.

For more details on the Microsoft IIS Web server sensor and Inventory Summary pane, refer to Microsoft IIS Web server sensor and Inventory Summary pane: Inventory tab.

Taddm 7.3.0.8 provides the ability to define password policy with password strength rules that are used to determine whether a new password is valid.

For more details on the password policy, refer to Password Policy.

A new sensor “Pacemaker Cluster Sensor” has been added to support the discovery of RedHat Pacemaker Cluster (created using the High Availability-AddOn packages on RHEL) on Red Hat Enterprise Linux 7.8. The sensor discovers the cluster nodes, resources, resource groups, resource clones, multi-state resources, their meta attributes, resource attributes, cluster properties on the cluster. The relationship of cluster nodes with the Linux Computer Systems is also maintained.

This sensor is a script-based sensor. For more details, refer to Pacemaker Cluster sensor.

Documentation on Custom template sensor (CTS), Custom Server Template (CST), and Custom Server Extensions (CSX) has been enhanced to give a better understanding of these topics.

In addition, a topic CTS vs CST vs CSX has been added that demarcates the differences (sensor run, usage, creation, limitations, etc.) between the three customization methods in TADDM.

In DAP phase II, the dashboard window is introduced. In this window, you can find a pie chart and a search field. Using this chart, you can now view all the available configuration items in your TADDM CMDB. Interactive features of the chart enable you to explore CI details easily.

In the previous release, only two similar (Type) components were compared. Now you can compare up to five components. Even in the comparison result pane, instead of two components, you can now view comparison results of five components. Comparison result can be downloaded in three different formats, XML format is newly added along with the existing PDF and CSV formats.

DAP phase II also provides enhanced capability to explore details of the five configuration items. In the previous version, analysis of only three CIs was possible.

Now ServiceNow Integration plugin extends support for Madrid version of ServiceNow.

In FP7, the ServiceNow plugin provides enhanced support for all TLS versions. Prior to this release, only the preconfigured value of TLS was supported. A new customizable property, securityProtocol=TLSv1.2, has been introduced in the plugin.properties.

Additionally, a new attribute, depth, is introduced in the mapping.xml file. You can customize this attribute according to how deep you want the details of data that you fetch. This customization in turn increases or decreases execution time.

For load balance discovery, now you can abort a discovery at scope set level. Previously, if you initiated an abort for LBD, all the scope sets associated to the discovery aborted.

Now more flexibility has been introduced to the command so you can abort either at the pool level using old command or at the scope set level using the new command.

api.sh -u <user> -p <password> discoverloadbalanced abort --poolName <pool name> --scopeSet <scope set name>.

Previously, the abort command was restricted to the pool name, but with this change, discovery can be aborted at the scope set level.

Dap now supports user authentication from an external LDAP directory server. In the previous version, only file-based user authentication was supported. Following this release, an LDAP user with the appropriate role (viewer) can access DAP.

TADDM 7.3 Fixpack 6 adds support of an Integration Plugin to migrate TADDM discovery data to ServiceNow CMDB. This integration of TADDM discovery data with ServiceNow CMDB supports initial bulk migration and any subsequent Configuration Item (CI) dynamic updates using push data mechanism. The plugin can be executed on TADDM discovery server, or, some other server and is managed (start, stop, status) as a separate tool via its command line interface.

Supported CIs: The scope of Integration Plugin will be limited to set of basic configuration items comprising of Networking, Compute and Storage (ComputerSystem, IpAddress, IpInterface, L2Interface, AppServer, AppServerCluster, Database Server, Storage SubSystem, Storage Volume, FileSystem).

The TADDM Data Access Portal is the IBM® Tivoli Application Dependency Discovery Manager (TADDM) web-based user interface for viewing the data in a TADDM database. This user interface is applicable to a domain server deployment, to a synchronization server deployment, and to each storage server in a streaming server deployment.

TADDM Data Access Portal provides the following services that can be used to perform analytics:

Login- To Access TADDM Data Access Portal, user can login into TADDM Data Access Portal using TADDM login credentials having "dapuser" role assigned to them.

Comparison -This feature allows user to compare attributes between two CI of same component types. User can see the difference and similarities between two CI attributes.

Relationship- Relationship associations between two resource instances, showing how resource instances are related to each other. To show relationship between classes of the same or different types. Each relationship has a definition, or type.

These different relationship types carry a certain semantic that pertains to the kind of association between the resource instances.

All Oracle databases before Oracle Database 12c were non-CDBs. i.e., Oracle 12C supports both non-CDB architecture and multi-tenant architecture based on configuration option.

Prerequisites

A privileged common user shall be used to discover Oracle12c multitenant architecture.

There have been many updates in “EMC ViPR SRM Sensor”, which is used to discover storage resources that are related to storage area network (SAN) by obtaining the requisite data from EMC ViPR SRM. This sensor discovers such storage resources as storage arrays (VMAX only), hosts and switches (Brocade only), i.e. discovery of fabrics, zones, zonesets, storage volumes, switches, switch ports, hosts, HBAs, etc. only.

Host storage sensor utilizes 32-bit collection-engine binary to discover the HBAs and FC Volumes that are configured on the host system. As a result, there is a pre-requisite of installing 32-bit glibc library.

This enhancement has been done to remove pre-requisite of installing 32-bit glibc library on 64-bit RHEL/AIX targets.

A configuration option (collectionEngineBuild_64_Bit) has been provided for utilizing 64-bit collection-engine binary and is applicable for RHEL/AIX platforms.

InstallAnywhere is a Java-based software tool for creating installers or software packages, for multiple platforms. It creates reliable installations for on-premises platforms – Windows, Linux, Apple, Solaris, AIX, HP-UX, and IBM etc.

TADDM was using InstallAnywhere 2012 for creating build packages until last fixpack 5. However, in TADDM 7.3 Fixpack 6, TADDM installers have now been built using InstallAnywhere 2017.

Though, nothing changes from end-user perspective.

Support for SLM (Software License Metric) tags have now been added in current TADDM fix pack to support ILMT.

Now, TADDM resource usage can be monitored and captured using a script and its based on below metrics:

SLM tags are based on the ISO/IEC 19770-4 standard draft for Resource Utilization Measurement. SLM tags provide a standardized capability to report the consumption of the product license metrics (resources related to the use of a software asset). It’s an XML file generated by a product in runtime to self-report its license usage. An SLM tag file has a .slmtag file name extension.

IBM License Metric Tool (ILMT) is a product that identifies which software assets you have installed and their license usage. IBM License Metric Tool provides a simple way to track IBM software that you are using.

In TADDM 7.3.0.4, console users and groups were not displayed. As part of this enhancement (RFE# 25909), TADDM 7.3.0.5 can now show console users and groups of WAS on the Data Management Portal. It displays information related to the user like name, email address, associated group and assigned roles on the “User” tab. Group related information like name, associated users and assigned roles is displayed on the “Group” tab.

WebSphereScriptSensor discovers three components - WebSphere Server, WebSphere Cell and WebSphere Node. As WebSphere cell is an administrative domain that enables common administrative activities in a WebSphere Application Server distributed environment.

User and group related configuration files are stored in WebSphere Cell. So, TADDM displays users and groups tab in WebSphere cell inventory details section.

In TADDM 7.3.0.4, TPC sensor used to truncate the number of rows returned by the query to 20000. This number can be increased, but in order to do so, you need to edit a file called tpc.properties in a deep directory under osgi.

In TADDM 7.3.0.5 (RFE 72225), following properties have been added to collation.properties file with the default values:

com.ibm.cdb.discover.app.srm.tpc.sensor.HOST_SCSI_PATH.maxrows = 20000

com.ibm.cdb.discover.app.srm.tpc.sensor.HOST_SCSI_AGENT_LESS.maxrows = 20000

In TADDM 7.3.0.4, MSSQL was not able to display SQL cluster name on the Data Management Portal.

As part of this enhancement (RFE 115737), support has been added in TADDM 7.3.0.5 to display the SQL cluster name in regular discovery, script based discovery and ASD discovery.

Also for RFE 99129, a new property com.collation.discover.agent.sqlserver.skipSqlAuthentication has been added with the default value as True.

If the value of this property is set to True, it will allow Windows authentication first.

If the value of this property is set to False, it will allow SQL authentication first.

TADDM can use and leverage the BigFix architecture (BigFix Server and BigFix Agents) to automatically deploy, execute and capture TADDM Asynchronous Scripted Discoveries.

Basically, Asynchronous Script Discovery (ASD) requires manual intervention from TADDM administrator. “TADDM-BigFix Integration” feature utilizes the connectivity that BigFix infrastructure provides to the fire walled zone machines for running the discovery through the TADDM script packages it and is mainly based on automation of standard ASD approach.

Need for TADDM – BigFix Integration

-To discover the Enterprise infrastructure behind firewall, TADDM currently utilizes:

• Manual ASD (Asynchronous Scripted Discovery)
• Anchors and Gateways
• IBM Netcool Monitoring tools (ITM)

-Customers are not willing to deploy Anchors/Gateways for fire walled zones

-Manual ASD is cumbersome and labour intensive and not feasible/preferred option

-Integration of TADDM and BigFix can fill this gap

Key Advantages

-Ability to discover fire walled zones without anchors

-Ability to reuse the BigFix Infrastructure (e.g. open secure ports) to access endpoints

• "saving time" = this means the security team don't need to open ports on endpoints, configure SSH

-Automated way of ASD based discovery (termed AutoASD) behind firewalls - Minimal intervention required from TADDM administrator

Note: This BigFix integration feature is not same or similar to “BigFix Inventory”.

This integration needs below access(es):

• Read-Only access to BigFix Database – to be able to retrieve the encryption keys
• BigFix Server credentials – to be able to invoke BigFix APIs

It supports BigFix SSL mode as well.

Point to note is that TADDM-BigFix Integration supports similar set of sensors as supported by standard ASD mechanism.

Here’s list of sensors supported by this feature:

Table 1.

Sensors
Citrix XenServer sensor
Generic server sensor
IBM AIX computer system sensor
IBM DB2 sensor
IBM Lotus Domino server sensor
IBM Tivoli Utilization sensor
IBM WebSphere MQ Server sensor
IBM WebSphere sensor
JBoss Application Server 7 sensor
Kernel-based virtual machine sensor
Linux computer system sensor
Microsoft Exchange sensor
Microsoft IIS Web server sensor
Oracle sensor
Solaris computer system sensor
WebLogic SSH sensor
Windows computer system sensor

All the pre-requisites that are applicable for these sensors to support ASD mode of discovery will apply here as well.

Assumption:

• Sufficient disk space, processing capacity and memory should be available to cater to the request and result packages that gets processed on TADDM server, BigFix Root Server and Discovery tar-gets
• Only “taddmusr” will be allowed for running the BigFix discovery on TADDM discovery server, and root user won’t be permitted
• Any discovery targets specified during discovery and not reachable from BigFix root server won’t be visible in Discovery History
• StartTime in the Discovery History will reflect the start time when bunch of script package execu-tion results are available on the TADDM Discovery server and its processing is triggered
• CompletionTime in the Discovery History will reflect the end time when a given bunch of results are successfully processed

Limitations:

• “Custom Servers” Discovery is not supported
• Due to asynchronous nature of discovery, multiple discovery history entries might get created for a single TADDM-BigFix discovery
• Rediscovery is supported from same Discovery server that was used for original discovery

Here are the supported version details:

• BigFix server version: 9.5.4
• BigFix server OS: Linux (RHEL 6.8), Windows 2008 R2
• BigFix target OS: Linux, Solaris, AIX, Windows

A new sensor termed “EMC ViPR SRM Sensor” will discover storage resources that are related to storage area network (SAN) by obtaining the requisite data from EMC ViPR SRM.

This sensor discovers such storage resources as storage arrays (VMAX only), hosts and switches (Brocade only), i.e. discovery of fabrics, zones, zonesets, storage volumes, switches, switch ports, hosts, HBAs, etc. only.

Assumption:

• Host Discovery shall be enabled in EMC ViPR SRM
• “Domain” is configured for all the Hosts/Storage clients

Limitations:

• EMC ViPR SRM SSL mode is not currently supported
• Hosts to Storage mappings are not completely supported
• Multi-path and relationships discovery is not supported

EMC ViPR SRM version: 4.1

TADDM 7.3 FixPack 5 ensures that all communication from TADDM is covered under TLS.

com.ibm.cdb.service.SecurityManager.port=9540

com.ibm.cdb.service.TopologyManager.port=9550

com.ibm.cdb.service.RegistriesURLProvider.port=9560

com.ibm.cdb.service.web.secure.port=9431

com.ibm.cdb.service.SecureClientProxyServer.secure.port=9434

com.ibm.cdb.service.SecureApiServer.secure.port=9531

com.ibm.cdb.service.registry.public.port=9433

TADDM 7.3 FixPack 5 ensures that AES-256 algorithm can be configured and applied for encryption of these items.

The only limitation of TADDM in Fixpack 5 is the inability to discover SNMP devices with AES-256 being the only encryption algorithm configured at the target. For supporting discovery of SNMP devices with AES-256 enabled, an upgrade is required in the version of the AdventNet SNMP library used by TADDM. This is a planned work and shall be made available to the users post the release of TADDM 7.3.0.5.

The “MssObjLinkCleanupAgent” has been added in TADDM 7.3 Fixpack 5. This clean-up agent will perform additional clean-up of MSS Data.

By default, the agent will delete maximum 100K rows daily which are more than 365 days old. This number of days can be configured. User can set this to a lower value like 30 days to delete rows which are more than 30 days old. This will lead to better performance of MSS related queries and UI.

Following properties can be configured in collation.properties:

com.collation.topobuilder.agent.MssObjLinkCleanupAgent.previousOld.olderThanDays=365  

com.collation.topobuilder.agent.MssObjLinkCleanupAgent.previousOld.on=false

com.collation.topobuilder.agent.MssObjLinkCleanupAgent.maxBatchRows=100

• Boot time is a common attribute on the default OID for an SNMP device and helps in knowing for how long a SNMP device is up.
• User can collect boot time and store in TADDM database for all SNMP devices i.e. blade chassis, routers, switches, firewalls, load balancer, etc.

Prior to this enhancement, IIS sensor required UAC to be disabled if using a domain account. This was due to PowerShell requirements. Now, with this enhancement, you can discover IIS without UAC disabled as IIS sensor will use appcmd.exe instead of PowerShell.

This enhancement can allow you to discover VCSA using web interfaces. There is a new configuration option in Port sensor to allow the specification of VCSA listening ports (vcsaListeningPortList) to be used to trigger seeding of VirtualCenterSensor.

By default, `vcsaListeningPortList` is empty in the Port sensor. Ports 80, 443 are ubiquitous ports and may appear a bad choice for seeding the VirtualCenterSensor, since they can cause many false positives for sensor invocations. It is recommended to provision a more unique port, or, lists of that port's possible values in a customer deployment (e.g. 514, 902) should be used in PortSensors `vcsaListeningPortList`.

It is now possible to discover IPv6 VIP information of virtual and real server for Big IP devices.

IBM Websphere Message Broker has been renamed as IBM Integration Bus for newer releases. TADDM will be able to discover IBM Information Bus (IIB) 10.0. WebSphere MQ is no longer a prerequisite for using IBM Integration Bus 10.0.

Some of the attributes in Citrix model objects are not relevant or not used in Citrix XenApp 7.6 architecture and hence they will not get populated and thus may get displayed with no value (“Blank”) in TADDM Data Management Portal, since TADDM Data model is based on Citrix 6 architecture.

The Docker sensors detect and discover Docker clusters, hosts, host attributes, containers and overlay networking stacks from the deployed Docker clusters or individual Docker hosts. A Docker system consists of following:

1. Containers containing virtual NICs, storage and running applications.
2. Docker hosts running multiple containers and a Docker daemon to manage containers.
3. Docker cluster consisting of several Docker hosts, and a cluster controller.

A Docker cluster can be achieved through Docker provided Swarm. The APIs called are Docker APIs over HTTP from a client to the Host or Swarm Manager to discover the objects within them. These sensors will discover the hosts and through existing means would be able to access the host.

1. DockerHostSensor – Sensor for a single Docker Host

The DockerHostSensor (DHS) uses Docker APIs through SDKs and discovers the elements from the Docker Host environment comprising – Containers, Images, Networks, Volumes, etc.

2. SwarmClusterSensor – Sensor for a single Swarm Cluster

The DockerSwarmCluster Sensor uses Docker APIs through SDKs and discover the elements from the Docker Swarm manager environment comprising - Detect Swarm Manager, list of Docker hosts (nodes) in the cluster, network information involving Overlay networks, docker_gwbridge, etc.

• TADDM can discover Windows 2016
• Support for IBM Spectrum Control 5.2.11, 5.2.12, 5.2.13 and 5.2.14
• ApacheServer Sensor discovers IBM HTTP Server (IHS) and Oracle HTTP Server (OHS) on Windows 2008, Windows 2008 R2, Windows 2012, Windows 2012 R2 and RHEL 7
• TADDM can discover IBM i5/OS versions 7.2 and 7.3
• TADDM can discover WebSphere 9.0
• Oracle bug 22256560 in release 12.1.0.2 prevents grouping patterns from running in certain cases. TADDM has been tested with the Oracle patch for bug 22256560 for versions 12.1.0.2 and 12.2.0.1 as the backend database. The grouping patterns work fine with the fix applied.

• IBM Tivoli Storage Productivity Center sensor: discovery of Managed Disks for SVC (storage virtualization layer) with their relationships to the back-end storage: Configuring the discovery profile.
• DataPower® sensor: discovery of domains and proxies: DataPower sensor.
• IBM BladeCenter SNMP sensor: discovery of IBM PureFlex® System chassis:
  • IBM BladeCenter SNMP sensor
  • SVC Storage sensor
• Cisco UCS SNMP sensor: extended discovery capability: Cisco UCS SNMP sensor.
• Discovery schedule and scope synchronization enhancement:
  • Adding a discovery schedule
  • Discovery Schedule window
  • Schedule Details window
  • Loading a discovery scope from a file
• Dynamic setting of address space name from the api.sh discover start command:
  • Discover command
  • Discovery management
  • Discovery service
• Discovery of VMWare ESX hosts start time.
• PowerShell session enhancements:
  • Automatic configuration
  • Configuring the collation.properties file entries
• New supported discovery targets:
  • FreeBSD computer system sensor discovers FreeBSD 9.3, and 10.2.
  • JBoss Application Server 7 sensor discovers WildFly 8, and 9 on Windows Server 2012, and Red Hat Enterprise Linux® 7.
  • Linux computer system sensor discovers SUSE Linux Enterprise Server 12, CentOS Linux 5, 6, and 7.
  • VMware ESXi computer system sensor discovers VMware ESXi 6.
  • VMware Virtual Center server sensor discovers VMware vCenter Server 6.0 on Windows, and VMware vCenter Server Appliance 6.0 on SUSE Linux Enterprise Server 11.
  • Microsoft Exchange sensor supports Microsoft Exchange Server 2016 on Windows 2012.
  • Microsoft SQL Server sensor supports Microsoft SQL Server 2014 on Windows 2012.

• Generating business application topologies in the SVG format: Actions for exporting topologies to the SVG format
• Grouping pattern traversal based on the hierarchyDomain attribute: Traversal configuration

• Building block views
• Data views in the TADDM model

• Tomcat 7 as platform
• FIPS compliant L2 discovery
• Tectia SSH support
• Support for TLSv1.2
• Auditing of UI changes

• Support for Red Hat Enterprise Linux 7 x86_64 and Red Hat Enterprise Linux 7 for System z®.
• Support for new databases: DB2® 10.5 and Oracle 11g Release 2 (11.2)
• Support for new browsers: Mozilla Firefox 24, 31

• Configuration for non-admin discovery on the Windows operating system
• Discovery of Citrix XenServer
• Discovery of DataPower
• Discovery of dependencies between WAS Cluster, Cell, Node and Databases
• Discovery of ESXi
• Discovery of HP NonStop through SSH
• Discovery of IIS WebDirectory
• Discovery of JBoss 6
• Discovery of JBoss 7
• Discovery of Microsoft Exchange 2013
• Discovery of MQ 7.1 and 7.5 and multiversion support for Unix and Windows
• Discovery of MySQL (custom script for discovery included into FP3)
• For MaxDB, a new access list entry type has been added
• Discovery of MySQL to create modules for each database
• Discovery of NetApp
• Discovery of new attributes for vCenter
• Enhanced NFS Dependency Agent to create relationship based on mounted share
• Level 3 discovery on WPARs
• New auth attributes in Windows and Linux scripts.
• Removal of LSOF prerequisite for AIX® discovery
• Script based and asynchronous discovery for Windows operating system
• Script based discovery for AIX operating system: Increased parity
• Script based discovery of Microsoft Internet Information Services (IIS)
• Secure discovery of LDAP services
• Support of HyperV 2012
• Support for Virtual Center Server Appliance (vCSA)
• Unification of FCPort WWN format
• VIOS connectivity to Storage SubSystem without agents

• Extended attributes are stored along with the CIs in the XA attribute of a new custom type ExtendedAttributesData. The data that is kept in separate objects of the UserData type is migrated into the XA attribute.
• Extended attributes now have categories. If no category is selected, an attribute is stored in the default global category. All extended attributes present in the old data model were moved into the default global category.