Tivoli Application Dependency Discovery Manager Version Release Notes IBM

Transcription

1 Tivoli Application Dependency Discovery Manager Version Release Notes IBM

2

3 Tivoli Application Dependency Discovery Manager Version Release Notes IBM

4 Note Before using this information and the product it supports, read the information in Notices on page 19. Edition notice This edition applies to version 7, release 3 of IBM Tivoli Application Dependency Discovery Manager (product number 5724-N55) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2007, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Release notes These release notes provide an overview of what is new or changed in IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.3.0, , , , and Contents v New features and enhancements in Fix Pack 5 v New features and enhancements in Fix Pack 4 on page 6 v New features and enhancements in Fix Pack 3 on page 9 v New features and enhancements in Fix Pack 2 on page 11 v New features and enhancements in Fix Pack 1 on page 12 v New features and enhancements in on page 13 v Features that are deprecated but still supported on page 14 v Significant changes from earlier releases on page 15 v Upgrade scenarios on page 16 v Key data modifications during the upgrade from earlier releases on page 16 v System requirements on page 16 v Known problems on page 16 v Moving TADDM from one operating system to another on page 16 Fix Pack 5 New features and enhancements in Fix Pack 5 TADDM includes the following new features and enhancements. For more information, follow the link, where provided. v AWS sensor AWS sensor supports discovery of public AWS cloud environment hosting EC2 and S3 services. It detects and retrieves information via URL (newly added). This is designed as a non-scripted sensor and is proposed to support 2 level discovery. During 1st level discovery, AWS management information is discovered: 1. VM instances and Details Memory OS details (name/family, version) VMs IPs (private, public IPs) Storage/volume, mount points related information Machine type Tags metadata 2. S3 buckets v SVC sensor support- 7.7 to 8.1 This enhancement caters to RFE As part of this enhancement, the following attributes shall be successfully discovered up till SVC version 8.1: 1. FC Ports 2. Storage Volume 3. Storage Pools Copyright IBM Corp. 2007,

6 4. Disk Drive v Show console users and groups of script based discovery of WAS sensor In TADDM , console users and groups were not displayed. As part of this enhancement (RFE# 25909), TADDM can now show console users and groups of WAS on the Data Management Portal. It displays information related to the user like name, 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. v TPC sensor enhancement for supporting TADDM Best Practices In TADDM , TPC sensor used to truncate the number of rows returned by the query to 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 (RFE 72225), following properties has been added to collation.properties file with the default values:api.sh discover start. com.ibm.cdb.discover.app.srm.tpc.sensor.host_scsi_path.maxrows = com.ibm.cdb.discover.app.srm.tpc.sensor.host_scsi_agent_less.maxrows = v MSSQL server Sensor Support- Cluter Name In TADDM , MSSQL was not able to display SQL cluster name on the Data Management Portal. As part of this enhancement (RFE ), support has been added in TADDM 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. v TADDM-BigFix Integration 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 2 Application Dependency Discovery Manager: Release Notes

7 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 Table 1. Sensors -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: 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 Release notes 3

8 Table 1. (continued) Sensors 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: Limitations: 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 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: BigFix server OS: Linux (RHEL 6.8), Windows 2008 R2 BigFix target OS: Linux, Solaris, AIX, Windows v TADDM Integration with EMC ViPR SRM 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: Limitations: Host Discovery shall be enabled in EMC ViPR SRM Domain is configured for all the Hosts/Storage clients EMC ViPR SRM SSL mode is not currently supported Hosts to Storage mappings are not completely supported 4 Application Dependency Discovery Manager: Release Notes

9 Multi-path and relationships discovery is not supported EMC ViPR SRM version: 4.1 v TLSv1.2 support TADDM 7.3 FixPack 5 ensures that all communication from TADDM is covered under TLS. The following ports are used for Inter-server communication and covered under TLS: com.ibm.cdb.service.securitymanager.port=9540 com.ibm.cdb.service.topologymanager.port=9550 com.ibm.cdb.service.registriesurlprovider.port=9560 The following port is used for GUI (Web Portal and Data Management Portal) and covered under TLS: com.ibm.cdb.service.web.secure.port=9431 The following port is used for DMP-DS communication and covered under TLS: com.ibm.cdb.service.secureclientproxyserver.secure.port=9434 The following port is used for API Clients-DS communication and covered under TLS: com.ibm.cdb.service.secureapiserver.secure.port=9531 The following ports are used for registering the services (Proxy, Topology & EventsCore) to Service Registry which is available on Discovery Server. These ports are covered under TLS: com.ibm.cdb.service.registry.public.port=9433 com.ibm.cdb.service.registry.interserver.port=4160 com.ibm.cdb.service.registry.local.port=1099 v AES 256 Encryption algorithm support TADDM uses the property com.collation.security.algo.aes.keylength to decide which algorithm (AES-128 or AES-256) from the FIPS-compliant IBMJCEFIPS security provider to encrypt the following items: Passwords, including entries in the collation.properties and userdata.xml files Access list entries that are stored in the database TADDM 7.3 FixPack 5 ensures that AES-256 algorithm can be configured and applied for encryption of these items. v MSS Data cleanup 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: For deleting old data specific days old, set the below value to number of days. The default value is 365. com.collation.topobuilder.agent.mssobjlinkcleanupagent.previousold.olderthandays=365 To disable the agent, configure the following property to 'false'. By default it is 'true' which means that the agent is enabled: com.collation.topobuilder.agent.mssobjlinkcleanupagent.previousold.on=false To change the number of rows deleted in a batch, in a single deletion access to the database. The default 100 value of this property is 100. This property is also used in Orphan MSS Data Deletion in this Agent. Release notes 5

10 com.collation.topobuilder.agent.mssobjlinkcleanupagent.maxbatchrows=100 v New view for MSS Info data lookup A new view MSS_INFO_VIEW has been defined for the user to query the MSS Info details. User can write a query on this view to fetch the MSS Info specific data. To see the columns that are defined for this view, user can run the following SQL query: DESCRIBE TABLE MSS_INFO_VIEW v New supported discovery targets: 1. Lotus Domino RHEL DB v New severs supporting TADDM installation: 1. Windows RHEL 7.5 v New browsers supported by TADDM: 1. MS Edge Fix Pack 4 New features and enhancements in Fix Pack 4 TADDM includes the following new features and enhancements. For more information, follow the link, where provided. v Sensor and discovery enhancements - Collect Boot time with all SNMP Sensor 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. v IIS sensor redesign use appcmd.exe instead of Powershell IIS module 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. v Support discovery of Virtual Center System Appliance through web ports This enhancement can allow you to discover VCSA using web interfaces. There is a new configuration option in PortScan 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 PortScan 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 PortScanSensors `vcsalisteningportlist`. For successful discovery of VMware vcenter Server Appliance, Web Services communication must be defined. By default, ports 80 and 443 are defined in the VirtualCenterSensor. If your VMware vcenter Server Appliance uses non-standard ports, modify the value of the portlist property in the discovery profile. 6 Application Dependency Discovery Manager: Release Notes

11 Limitations: If port mentioned in `vcsalisteningportlist` is opened by some process other than VCSA, the VMware Virtual Center server sensor will show an error. v BIgIPSensor needs to be able to discover VIP IPv6 It is now possible to discover IPv6 VIP information of virtual and real server for Big IP devices. v Support of IBM Integration Bus(IIB) 10.0 IBM Websphere Message Broker has been renamed as IBM Integration Bus for newer releases. TADDM will be able to discover IBM Information Bus (IIB) WebSphere MQ is no longer a prerequisite for using IBM Integration Bus v Discovery of Citrix environments by Citrix 7 Server Sensor The Citrix 7 Server sensor discovers Citrix 7 XenApp environments. It is a script-based sensor. The sensor only supports Citrix version 7.6. Sensor Authorization The script-based sensor uses the same discovery user that is used for Windows logon. The Windows discovery user must have administrator read only permissions (defined in the Citrix console) for the Citrix configuration on any delivery controller for each site. Citrix requires that the discovery user be an active directory account and not a local account. Limitations Site names are assumed to be global. You cannot have two sites with the exact same name or this will cause over-merging. Discovery of VDAs Discovery of at least one delivery controller is required but discovery of the systems that run the VDAs is optional. The sensor will launch when it detects a VDA and the sensor will collect basic information about runtime processes and hostname. This will create a more complete picture of the Citrix environment. Nomenclature Citrix 7 introduces an architecture change from Citrix 6, but the TADDM data model is based on Citrix 6 architecture. In order to preserve backwards compatibility for business application mapping, the Citrix 7 architecture components are stored as Citrix 6 data model components. The table below shows the old and new concepts and how they map to the TADDM data model. Table 2. S No. Citrix 7 Citrix 6 Comments 1 Site CitrixFarm/ CitrixZone For each Citrix Site there will be a one-to-one Farm/Zone combination with the same name. 2 Admin Folder CitrixAppFolder Organizes the CitrixApplication components. 3 Desktop Catalog CitrixServerFolder NA 4 Desktop Group NA Desktop Groups are used to assign CitrixApplications to CitrixServers. Release notes 7

12 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. Table 3. S.No Model Object Attributes List 1 CitrixApplication Default encryption, Default sound type, Default windows type, Read only, PN Attribute, MF Attribute, Default window height, Default window scale, PN Folder, Default window width, Default window colour, Publishing flags. 2 CitrixFarm Discard Redundant Graphics, Alternate Caching method, Log Auto Reconnect Attempts, SNMP Disconnect trap, Notify Degradation, Legacy ICA Display Compatible, Video Buffer Size ICA, Enable Auto client reconnect, Use Client local time, Disable Client local time estimation, Enable SNMP Agent, Enable DNS Address resolution, RAS Response to client broadcast, SNMP Threshold Exceeded trap, SNMP Logoff trap, SNMP Threshold value, Log over limit denial, MultimediaAccelerationDefaultBufferSize, DS Driver, Legacy MF Server compatible mode, DC Respond to client broadcast, SNMP Logon trap, DSODB, Max Connection per user, Degradation Bias. 3 CitrixUser Account type 4 Citrix Group Account type 5 Citrix Account authority Authority Type 6 CitrixServer Is farm server, Zone ranking,feature release level,install Date v Discovery of Docker Sensors 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. v New supported discovery targets 8 Application Dependency Discovery Manager: Release Notes

13 TADDM can discover Windows 2016 Support for IBM Spectrum Control , , and 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 in release prevents grouping patterns from running in certain cases. TADDM has been tested with the Oracle patch for bug for versions and as the backend database. The grouping patterns work fine with the fix applied. Note: Java version 6.0 is no longer supported and has been removed from the Client software requirements documentation. Fix Pack 3 New features and enhancements in Fix Pack 3 TADDM includes the following new features and enhancements. For more information, see the appropriate topic, where provided. v Sensor and discovery enhancements: IBM Tivoli Storage Productivity Center sensor: discovery of Managed Disks for SVC (storage virtualization layer) with their relationships to the back-end storage: the Configuring the discovery profile topic in the Tivoli Storage Productivity Center sensor section in the TADDM Sensor Reference. DataPower sensor: discovery of domains and proxies: the DataPower sensor topic in the TADDM Sensor Reference. IBM BladeCenter SNMP sensor: discovery of IBM PureFlex System chassis: - The IBM BladeCenter SNMP sensor topic in the TADDM Sensor Reference. - The SVC Storage sensor topic in the TADDM Sensor Reference. Cisco UCS SNMP sensor: extended discovery capability: the Cisco UCS SNMP sensor topic in the TADDM Sensor Reference. Discovery schedule and scope synchronization enhancement: - The Adding a discovery schedule topic in the TADDM User's Guide. - The Discovery Schedule window topic in the TADDM User's Guide. - The Schedule Details window topic in the TADDM User's Guide. - The Loading a discovery scope from a file topic in the TADDM User's Guide. Dynamic setting of address space name from the api.sh discover start command: - The Discover command topic in the TADDM SDK Developer's Guide. - The Discovery management topic in the TADDM SDK Developer's Guide. - The Discovery service topic in the TADDM SDK Developer's Guide. Discovery of VMWare ESX hosts start time. PowerShell session enhancements: - The Automatic configuration topic in the Configuring for a non-admin Windows discovery section in the TADDM Sensor Reference. - The Configuring the collation.properties file entries topic in the Windows computer system sensor section in the TADDM Sensor Reference. New supported discovery targets: Release notes 9

14 - FreeBSD computer system sensor discovers FreeBSD 9.3, and 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. - Microsoft Exchange sensor supports Microsoft Exchange Server 2016 on Windows Microsoft SQL Server sensor supports Microsoft SQL Server 2014 on Windows 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. v Business applications enhancements: Generating business application topologies in the SVG format: the Actions for exporting topologies to the SVG format topic in the TADDM User's Guide. Grouping pattern traversal based on the hierarchydomain attribute: the Traversal configuration topic in the TADDM User's Guide. v Migration of missing values of the hierachytype and hierarchydomain attributes. v Placeholders creation: the Configuring for discovery of placeholders topic in the TADDM Administrator's Guide. v Cognos model new time stamp column and query items: The Building block views topic in the TADDM SDK Developer's Guide. The Data views in the TADDM model topic in the TADDM Administrator's Guide. v New length of column names in TADDM database views: the TADDM database schema and views topic in the TADDM SDK Developer's Guide. v Data type modification in the extended attributes views: the Extended attributes view topic in the TADDM SDK Developer's Guide. v Updated content of the TADDM Data Dictionary. v Secure connection between TADDM components. Significant changes from earlier releases v Important: The discovery of MAC addresses on switch trunk ports by using the BridgeSnmpSensor, or BridgeSnmpSensor2 is disabled by default in TADDM , and later. When it is enabled, the topology building performance is poor because of the excessive data that L2Agent is not able to process in time. As a result, too many temporary computer systems with type MACDevice are created. However, if you still want to discover the MAC addresses on switch trunk ports, you can add the following properties to the collation.properties file and set them to false: com.collation.discover.agent.net.bridgesnmpagent.filterextremetrunkport =false com.collation.discover.agent.net.bridgesnmpagent.filterciscotrunkport =false com.collation.discover.agent.net.bridgesnmpagent.filterlldptrunkport =false 10 Application Dependency Discovery Manager: Release Notes

15 For details, see the Configuring the collation.properties file entries topics in the Bridge SNMP sensor and Bridge SNMP 2 sensor sections in the TADDM Sensor Reference. v To display the Grouping Patterns pane in Data Management Portal, you must have the Update permission granted for the DefaultAccessCollection. v Placeholders created in TADDM are more advanced than the ones created in TADDM Therefore, migration is not supported. v Column names in TADDM database views can now have maximum 30 characters. v Data type in the extended attribute views has been modified. It might affect integration with products that use TADDM database views for extended attributes. For details, see the Extended attributes view topic in the TADDM SDK Developer's Guide. Fix Pack 2 New features and enhancements in Fix Pack 2 TADDM includes the following new features and enhancements. For more information, see the appropriate topic, where provided. v Sensor and discovery enhancements:.net 4.0 and 4.5 support: Configuring for discovery of Windows systems topic in the TADDM Administrator's Guide. Auto-defining extended attributes for sensors: Auto-defining extended attributes for sensors topic in the TADDM SDK Developer's Guide. Discovery of dependencies between MySAPJ2EEEngineInstances in pure J2EE clusters and database servers. Discovery of IIS module and database dependencies by using IISServerSensor: Microsoft IIS Web server sensor topic in the TADDM Sensor Reference. Discovery of IBM software - The Predefined templates topic in the TADDM User's Guide. - The Creating Level 3 application servers with no credentials topic in the TADDM Administrator's Guide. IBM WebSphere Application Server script-based discovery for Windows: The Sensors that support script-based and asynchronous discovery topic in the TADDM Sensor Reference. Load-balanced discovery: The Load-balanced discover command topic in the TADDM SDK Developer's Guide. Microsoft SQL Server script-based discovery: The Sensors that support script-based and asynchronous discovery topic in the TADDM Sensor Reference. New discovery targets of Linux computer system sensor: Ubuntu 14 and RedHat 7. New sensor: Cisco UCS SNMP sensor: The Cisco UCS SNMP sensor topic in the TADDM Sensor Reference. New sensor: Sun Sparc Virtualization sensor: The Sun Sparc Virtualization sensor topic in the TADDM Sensor Reference. New versions of Oracle JDBC drivers supported in TADDM: The Copying the JDBC driver topic in the TADDM Sensor Reference. PowerShell session in the discovery of the Windows target systems - The Configuring for discovery of Windows systems topic in the TADDM Administrator's Guide. Release notes 11

16 - The PowerShell session topic in the TADDM Administrator's Guide. - The Configuring the collation.properties file entries topic in the Windows computer system sensor section in the TADDM Sensor Reference. - The Setting up the PowerShell configuration topic in the TADDM Sensor Reference. - The Gateway problems topic in the TADDM Troubleshooting Guide. SAP HANA discovery: The Model objects with associated attributes topic in the SAP SLD server sensor section in the TADDM Sensor Reference. Support for password encryption for Sybase discovery: The Sybase sensor topic in the TADDM Sensor Reference. v Business applications enhancements Enhancement of Traversal configuration: The Traversal configuration topic in the TADDM User's Guide. Grouping patterns filtering: The Grouping Patterns pane topic in the TADDM User's Guide. Handling not discovered business applications components: The Topology builder properties topic in the TADDM Administrator's Guide. New bizappscli tool action analytics: The Actions for analyzing the content of business applications topic in the TADDM User's Guide. v Improved Cognos Model: The Data views in the TADDM model topic in the TADDM Administrator's Guide. Significant changes from earlier releases v The IBM Tivoli Monitoring Agent for TADDM Serviceability and Manageability which was incompatible with TADDM is supported again. You can use it with TADDM and However, the agent is not shipped with the product, you must download the files from Fix Central. For details, see the Planning for monitoring of TADDM servers topic in the TADDM Installation Guide. v The Grouping Patterns pane was moved from the Discovery section to the Analytics section of Data Management Portal. For details, see the Grouping Patterns pane topic in the TADDM User's Guide. Fix Pack 1 New features and enhancements in Fix Pack 1 TADDM includes the following new features and enhancements. For more information, see the appropriate topic, where provided. v Sensor enhancements: Discovery of RuntimeProcesses for WebSphereServers SSL communication enabled for SybaseSensor: - The Configuring the access list topic in the Sybase sensor section in the TADDM Sensor Reference. New sensor: SVC Storage sensor: - The SVC Storage sensor topic in the TADDM Sensor Reference New sensor: XIV storage sensor: - The XIV storage sensor topic in the TADDM Sensor Reference Migration of SoftwareModules deployed on JBoss. Migration of LPAR name. IBM WebSphere Message Broker 8 supported on Solaris Application Dependency Discovery Manager: Release Notes

17 Host storage sensor supported on HP-UX platform. v Enhancement of the Business application tiers function: The Business application tiers topic in the TADDM User's Guide. The Creating grouping patterns topic in the TADDM User's Guide. v Complete Cognos model: The Generating the TADDM model topic in the TADDM Administrator's Guide. The Data views in the TADDM model topic in the TADDM Administrator's Guide. The Extended attributes views topic in the TADDM SDK Developer's Guide. The Running the extended attributes view tool topic in the TADDM SDK Developer's Guide. v Support for Netcool /Omnibus 8: The Supported versions topic in the TADDM Administrator's Guide. v Support for Oracle Java runtime environment version 8.0: The Client software requirements topic in the TADDM Installation Guide. v Support for WAS Liberty Profile. v Show dependencies option available for all elements visible in topology view. v Additional changes in the documentation: The Business applications topic in the TADDM User's Guide. The Simplified Model topic in the TADDM SDK Developer's Guide. The Integrating TADDM with IBM Tivoli Monitoring via OSLC Automation topic in the TADDM Administrator's Guide. The Configuring TADDM communication topic in the TADDM Administrator's Guide. New features and enhancements in TADDM includes the following new features: v Completely new structure of business applications v New way of handling extended attributes v Simplified Data Model v Discovery over ITM by using KT1 protocol v Enhancement of delta books utility v Load balancing on anchors v Static script names v Scopes grouping v Credentials caching v Support for Apache Bean Scripting Framework 2.4 and Jython v Security: Tomcat 7 as platform FIPS compliant L2 discovery Tectia SSH support Support for TLSv1.2 Auditing of UI changes v Platform support: Support for Red Hat Enterprise Linux 7 x86_64 and Red Hat Enterprise Linux 7 for System z. Release notes 13

18 Support for new databases: DB and Oracle 11g Release 2 (11.2) Support for new browsers: Mozilla Firefox 24, 31 v New sensors and sensor enhancements: 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 Features that are deprecated but still supported The following features are deprecated but is still supported in TADDM 7.3.0: v Jython 2.1 support. v Synchronization server deployment, which is a TADDM deployment with a synchronization server (formerly known as an Enterprise Domain Server) and two or more domain server deployments, each of which has its own local database. In this type of deployment, the synchronization server copies discovery data from multiple domain servers one domain at a time in a batched synchronization process. Where more than one server is needed, the preferred deployment is the streaming server deployment. v Discovery Management Console (client UI that was formerly known as the Product Console). 14 Application Dependency Discovery Manager: Release Notes

19 v Discovery history feature in both user interfaces (Data Management Portal and Discovery Management Console). This has been replaced by new TADDM reports. v CMS/DIS integration. v Server Affinity report. v Utilization sensor. The component retrieves runtime properties for a discovery target. In this situation, change management is not applicable. To monitor resource usage, you can use IBM Tivoli Monitoring. v BIRT reporting engine and reports. v Discovery support for Windows v Use of the Secure Shell (SSH) v1 and v1.5 protocols for discovery. TADDM anchor servers require SSH v2 protocol support. v WebLogic JMX sensor. There is an equivalent WebLogic SSH sensor that discovers the same configuration. v WebSphere Application Server discovery using the JMX protocol. v Application infrastructure topology. v Physical infrastructure topology. v AppTemplate API. v The old Common Data Model classes (com.collation.platform.model.topology.simple and com.collation.platform.model.topology.customcollection packages are preferred from now on). v The lastmodifiedtime attribute, use the laststoretime attribute instead. v The setextendedattributes and getextendedattributes methods used on CI are compatible with earlier versions. They set the XA attribute that handles extended attributes from now on. v The setextendedattributes and getextendedattributes methods used on DataApi. Use setxa and getxa methods directly on CI instead of DataApi extra calls. Significant changes from earlier releases The following information describes significant behavioral changes from earlier TADDM releases: v Removal of NetFlow sensor. v Java API methods related to security (AuthorizationManager API methods) were modified to use only those custom collections that have hierarchy type set to "AccessCollection". During TADDM upgrade, all existing authorization policy entries and all Supports relationships between PersonRole and AccessCollection objects are automatically migrated to the corresponding custom collection objects with hierarchy type set to "AccessCollection". Java API methods related to collections (selected Compatibility API methods) are deprecated. Use equivalent methods operating on corresponding custom collections. For details, see Managing collections. v To integrate TADDM 7.3 with IBM Tivoli Business Service Manager (TBSM), you must use TBSM FP1, or later. v IBM DB2 9.5 for Linux, UNIX, and Windows is no longer supported as the TADDM back-end database. v 32-bit platforms are no longer supported as TADDM servers. v Sun Solaris is no longer supported as a TADDM server. Release notes 15

20 v Red Hat Enterprise Linux 5 is no longer supported as a TADDM server. v The Extended Attributes details pane separate tab was removed. Separate tabs are created only for non-default categories. You can view extended attributes for default category in a separate table in the General tab now. Upgrade scenarios Important: When you want to upgrade to TADDM 7.3.0, you must have TADDM installed. You cannot upgrade from TADDM 7.2.1, or earlier, to TADDM Key data modifications during the upgrade from earlier releases v When you upgrade from TADDM 7.2.2, all grouping entities are converted automatically into grouping patterns in accordance with a specific set of rules. A new grouping pattern is created for each entity. Later, the BizAppsAgent generates new custom collections from these grouping patterns. The new custom collections' content (a set of configuration items) is the same as the content of the corresponding original collections. For more information, see Automatic conversion of the old grouping entities. v During the upgrade procedure, extended attributes are modified in the following way: 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. System requirements For information about hardware and software compatibility, see the TADDM Installation Guide. Known problems Known problems are documented as technotes on the IBM Tivoli Application Dependency Discovery Manager Support site at sysmgmt/products/support/ IBMTivoliApplicationDependencyDiscoveryManager.html. This site also includes APARs (problem reports), downloads, and education materials. As problems are discovered and resolved, the IBM Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems. To search for TADDM technotes, enter in the Search support field. To find solutions to the problems that you might have, you can also go to the dw Answers site at Moving TADDM from one operating system to another If you want to move TADDM from one operating system to another, follow the procedure that is described in the following section of the TADDM Installation Guide: 16 Application Dependency Discovery Manager: Release Notes

21 com.ibm.taddm.doc_7.3/installguide/t_cmdb_moving_taddm_to_other_os.html Release notes 17

22 18 Application Dependency Discovery Manager: Release Notes

23 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Copyright IBM Corp. 2007,

24 IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at 20 Application Dependency Discovery Manager: Release Notes

25 Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. PostScript is either a registered trademark or a trademark of Adobe Systems Incorporated in the United States, and/or other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. Notices 21

26 22 Application Dependency Discovery Manager: Release Notes

27

28 IBM Printed in USA