Previous Topic: Scalability Server ConsiderationsNext Topic: Import of Expressions Not Using IN and NOT IN Operators


Importing Unicenter Software Delivery 4.0 Query Strings

This section contains the following topics:

Overview

Query Import Limitations

Import of Expressions Containing OS Security or Directory Lookups

Import of Expressions Using IN and NOT IN Operators

Import of Expressions Not Using IN and NOT IN Operators

Import of Expressions Not Using IN and NOT IN Operators

Overview

CA ITCM uses Unicenter Software Delivery 4.0 formatted query strings in the following areas to support backward-compatibility:

Command Line Interface

The command to create computer groups accepts Unicenter Software Delivery 4.0 formatted query string to create a dynamic group.

Software Packages

Importing software packages containing procedure prerequisites created in Unicenter Software Delivery 4.0 accepts formatted query strings.

Software Packager

The CA ITCM Software Packager uses Unicenter Software Delivery 4.0 formatted query strings to create procedure prerequisites for software packages it creates.

Note: All the above areas create custom queries in the CA ITCM query subsystem because of certain query import limitations. In addition, queries that have been migrated from version 4.0 to Unicenter DSM r11.x using the migration tools are imported as custom queries.

Query Import Limitations

Software Delivery uses queries in a number of places to automate the management of assets. Starting with Unicenter DSM release 11, a new query mechanism that is common to all the DSM components replaces the 4.0 query sub system. The new SQL-based query mechanism gives performance improvements over the code-based legacy evaluation mechanism. Also, starting with Unicenter DSM r11, a new basic hardware inventory mechanism that is common to all of DSM replaces the inventory module of Unicenter Software Delivery 4.0. The new basic hardware inventory module offers more accurate inventory. However, some of the Unicenter Software Delivery version 4.0 attributes are not collected by the CA ITCM inventory module.

These changes have the following high-level impact on the query import:

Query Attributes

When you import a 4.0 formatted query string into CA ITCM, it is not possible to map all the query attributes to equivalent CA ITCM attributes. CA ITCM will import invalid queries with empty expressions marked as invalid for informational purposes. You must modify these queries before performing an import.

Computer Users

The CA ITCM query subsystem recognizes computers and user profiles as individual target types for queries. This means that a query can return either a set of computers or a set of user profiles but not both. In version 4.0, computers and user profiles were represented by one target type allowing a query to return both computers and user profiles. When you import a version 4.0 formatted query string into CA ITCM, the ability to return both computers and user profiles is maintained through the creation of a custom query. Custom queries are pure SQL statements that are not directly compatible with the query building functionality of the Query Designer. Therefore, you need to modify the custom queries using the Edit SQL feature of the Query Designer rather than using the Insert Argument feature.

Wildcard Characters

CA ITCM uses SQL wildcards; the LIKE operator replaces the MATCH operator in Unicenter Software Delivery 4.0 and all other wildcard characters are mapped to the SQL equivalents where possible. However, some of the wildcard characters such as '?', '+' and '|' have no equivalent in SQL; the 'set negation' [^ ….] is not supported and produces an invalid query.

Attribute Values

Some attribute values have changed in CA ITCM. In many cases, a simple mapping is possible to convert the version 4.0 values embedded in queries to the new values. In other cases, this is not possible because the number of values used in CA ITCM and version 4.0 may not match; in some cases an '=' or '<>' operator can be replaced with LIKE and some wildcards added to the literal. In this case, operators other than '=' or '<>' produce an invalid query.

This limitation specifically applies to the Target attribute group with the attribute values such as Machine, Staging Server, Domain, and UserId. It also applies to the Name attribute of attribute groups SDAttr_OS2, SDAttr_WinNT, SDAttr_WinCE, SDAttr_unix, SDAttr_Win9X, SDAttr_Netware, and SDAttr_VMS.

In the case of the attribute Type (in the Target attribute group) with the values 'Machine' and 'Staging Server', queries behave differently in Unicenter Software Delivery version 4.0 and CA ITCM. The reason for this is, in version 4.0 the agent on the Local Server was of the type 'Machine' whereas in CA ITCM the agent on the domain manager is of type 'Staging Server'.

Query Results

In Unicenter Software Delivery 4.0, a query "Target.Type='Machine'" returns all agents (no Staging Servers) including the Local Server's agent. When this query is imported to CA ITCM, it returns only standalone agents (agents that have no scalability server or domain manager on the same machine).

In Unicenter Software Delivery 4.0, a query "Target.Type='Staging Server'" returns all Staging Servers. When this query is imported to CA ITCM, it also returns the domain manager, as its agent is considered to be a Staging Server.

Import of Expressions Containing OS Security or Directory Lookups

When you import a Unicenter Software Delivery version 4.0 formatted query string that contains NTGroup source or the Directory source, authorities are added to the URI strings. These are machines names for the local authorities used with NTGroup and directory authorities used with Directory. These authorities may be incorrect in the new environment where you are using the Manager. In this case, you can edit the query after import and change the authority name.

To change the authority name, open the Properties dialog of the query, right-click the SQL fragment, and select Edit SQL. Replace the authority name with the correct one.

Import of Expressions Using IN and NOT IN Operators

The IN/NOT IN operations of Unicenter Software Delivery version 4.0 involve using a plug-in to provide a set of values instead of the single literal used for the other operations. The Unicenter Software Delivery version 4.0 plug-in sources and their equivalent functionalities in CA ITCM are as follows:

The SDGroup plug-in functionality is provided by standard CA ITCM queries that use computer group definitions.

NTGroup is implemented using the Directory services feature of CA ITCM queries. The allowed attribute group is Target and the allowed attributes in that group are User and UserId.

For IN/NOT IN tests against sets produced by Directory Services enquiries, the allowed attribute group is Target and the allowed attributes in that group are User, UserId, Name, Server, and Machine.

For IN/NOT IN tests against sets produced using the Unicenter Software Delivery version 4.0 query integration with Asset Management, the allowed attribute group is Target and the allowed attributes in that group are User, UserId, Name, Server, and Machine.

Import of Expressions Not Using IN and NOT IN Operators

The following table lists the supported and unsupported attributes in each attribute group that do not contain expressions using IN or NOT IN operators; the unsupported attributes will not be imported successfully: