Data partitioning for Configuration Item types is set up in a slightly different way, using the Configuration Item Type Reference object, rather than on the CI type itself. Instead of setting the partitioning attribute on the Configuration Item type in Object Designer, you set it on the Configuration Item Type Reference object, and then on the required related attribute on that object.
You may need to create a window for the Configuration Item Type Reference object to be able to set the partitioning attributes for the different CI Type References.
Using the procedures described in Setting the partitioning attribute to set a partitioning attribute on the Configuration Item Type Reference object, you enable data partitioning for CI Types in:
the Configuration Management component
when adding CIs to a change
To enable the data partitioning of CI Types on process windows such as the Incident and Problem windows, you need to complete a few more steps. The procedure below describes how to re-design the Incident window to also use CI Type partitioning.
To re-design the Incident window for CI Type data partitioning:
Open the Incident window in Window Manager.
Delete the existing CI Type list box.
From the Attributes tree, add Configuration Item Type Reference, and rename its label to match that which was used by the CI Type control. This replaces the unpartitioned CI Type list with the new partitioned CI Type list. However, we need the existing CI Type functionality to continue working, so we now need to copy the value from the CI Type Reference into the CI Type field whenever it changes. The CI Type field still exists in the database, but is no longer displayed on the screen. By copying the CI Type Reference into the CI Type, all of the existing filters, queries, and reports will continue to work as before.
Repeat this design work for any other Incident windows in your system.
Display the Business Objects tree and select the Incident object.
In the Actions list, click Business Object Copy Rules. The Copy Rules Configuration dialog appears.
Expand the Copy Rules tree and right-click the Incident object, then click New Rule. A new rule is added to the Copy Rules tree, and the Rule Editor changes to enable you to edit the new rule.
Type a Description for the rule, then set the following values: Event – Value Changed Target – Configuration Item Type Sources – Configuration Item Type Reference/Class
Select the Always execute rule check box, the Overwrite option button, and the Clear target if source is empty check box, then click OK.
For more information about configuring copy rules, see the Designer Guide.
Whenever a new Configuration Item subclass (a CI type) is created, a new record is added to the Configuration Item Type Reference object, which then manages the partitioning of CI types. However, if you want to partition CI types, you will need to populate the Configuration Item Type References for the existing CI types before switching on the partitioning. You populate the Configuration Item Type References for the existing CI types using the Run TPS Tools utility on the Web server.
To populate the Configuration Item Type References for the existing CI types:
From Program Files (x86)\LANDesk\Framework\bin, start Touchpaper.Tools.RunTPSTools.exe. The Run TPS Tools utility starts.
Under Provider, select SQL Server.
Type the name of the Database Server, the Database Name, the User name, and the Password for your database.
Click Test to confirm that the connection details are correct.
In the Tools list, select Populate CI Type References, then click Run. The Progress list indicates the success or failure of the tool.