How do I properly import an association between Software Licenses and Software Purchases in Asset Control / Contract Management 6.2 or Asset Management 6.5

Article:HOWTO3685  |  Created: 2006-05-26  |  Updated: 2008-12-16  |  Article URL http://www.symantec.com/docs/HOWTO3685
Article Type
How To



Question

How do I properly import an association between Software Licenses and Software Purchases in Asset Control / Contract Management 6.2 using Connector Solution 6.1 or in Asset Management 6.5 using Connector Solution 6.5

Answer

To import an association between a Software License and Software Purchase(s) using Altiris Connector Solution 6.1 and 6.5, you have to decide what the final desired results are and then how to set up the Connector import rule to achieve those results.

There are four main areas on the Software Purchase tab of a Software License:

  • Software Purchase Search Rule
  • Excluded Software Purchases
  • Other Software Purchases
  • All Software Purchases

  

 

 

Software Purchase Search Rule

This is where you place search rules that automatically associates Software Purchases to a Software License whenever the ‘NS.Update Software Purchases’ schedule runs.  For example: If 'Adobe Photoshop 7%' exists as a search rule, any Software Purchase that has a name beginning with 'Adobe Photoshop 7' will be associated to the Software License.

Under Column Mappings of the Connector Import Rule:

Data Class Name: Software Purchase Search Rule (multi rowed)
Data Class Column: Product Name

Data Class Column: Product Version

Data Class Column: Exclude


Note: The Product Name and/or Product Version mappings are for the Search Rule(s) that you would like. The Exclude column mapping is either a 0 to include the Search Rule in the Software License or a 1 for to exclude the Search Rule.

 


Excluded Software Purchases

 

This is where you may list any specific Software Purchase you would like excluded from being associated to the Software License.

 


Under Column Mappings of the Connector Import Rule:

Data Class Name: Software Purchase Tied (multi rowed)

Data Class Column: SoftwarePurchase

Data Class Column: Exclude


Note: For a Connector 6.1 Import Rule, the Data Source will need a column that contains the bit value, which is 1, for each Software License line item.  This column name would be referenced in the Foreign Source Column Name for the Exclude Data Class Column.  For a Connector 6.5 Import Rule, this same process can be used or by having a Source <value> of 1 instead.

 


Other Software Purchases

This is where you may list any specific Software Purchase you would like associated to the Software License regardless of if the Software Purchase may belong to a search rule.

Under Column Mappings of the Connector Import Rule:

Data Class Name: Software Purchase Tied (multi rowed)

Data Class Column: SoftwarePurchase

Data Class Column: Exclude


Note: For a Connector 6.1 Import Rule, the Data Source will need a column that contains the bit value, which is 0, for each Software License line item.  This column name would be referenced in the Foreign Source Column Name for the Exclude Data Class Column.  For a Connector 6.5 Import Rule, this same process can be used or by having a Source <value> of 0 instead.

 

 

All Software Purchases

Once the ‘NS.Update Software Purchases’ schedule runs, these are the combined results of Software Purchase Search Rules and Other Software Purchases for the Software License.  This list is updated when clicking the Apply or Done button when editing the Software License.

Under Association Mappings of the Connector Import Rule:

Association Name: Software Purchases



Important: If you associate Software Purchases only using this Association Mapping, the association will be removed once the ‘NS.Update Software Purchases’ schedule runs or by clicking the Apply or Done button when editing the Software License. For the association to stay, use either Software Purchase Search Rules or Other Software Purchases when importing Software Purchases using Connector Solution.

 


Legacy ID



22991


Article URL http://www.symantec.com/docs/HOWTO3685


Terms of use for this information are found in Legal Notices