IntroductionConnections to UCMDB databases are preferably based on MS linked server connections. However also direct connections to UCMDB databases are supported. The reason is that DM-ETL+ will have to use openrowset queries to collect data when using direct UCMDB database connections as the data source. Whenever an SQL server performs an openrowset query, the SQL server needs to allow adhoc queries. For adhoc queries either the system admin server role needs to be enabled or an additional registry key that allows adhoc queries has to be set. Both resolutions will degrade the security of the SQL server itself. Therefor it is recommended to use MS linked server connections instead. Never the less, technically and functionally MS SQL Server connections are supported.
- Accessible UCMDB Application layer and accessible physical UCMDB database(server). Can be two seperate servers.
- UCMDB application - Username/password with sufficient rights (fully enabled through webservices) to meet endgoals intended with use of this connector-definition.
- Physical database - Username/password with sufficient rights to meet endgoals intended with use of this connector-definition.
- DM-ETL+ and the UCMDB application need to be installed on the same server. If DM-ETL+ is not primarily intended for UCMDB related tasks then it is recommended to have a main DM-ETL+ Server install and a secondary "satellite" DM-ETL+ install next to the UCMDB application that only handles UCMDB related jobs. This is needed for optimal performance and datatransfer stability based on webservices.
Important InformationOn the use of the UCMDB connector the following important notes apply:
- Direct Connections: Reading also relies on the connector because of meta constructions that need to be translated. Reading directly on DB level can be done but will not make much sense and cannot be used (correctly) as a consolidation compare source.
- Resource CI is not supported in UCMDB 7.0 but is supported in 7.5 and higher
Figure 1: The Connector Properties
Creating the connectorTo create the connector, leave open solutions and select:
- Tools > Settings > Connector [TAB] > Add.
- Select: "Application - HP uCMDB"
- Click Ok
The Connector properties
|Datasource name||Textbox||Fill in the desired data source name as it is represented within DM-ETL+.|
|Physical Datasource||Dropdown||Use the dropdown list to select the appropriate logical data source.|
|Default owner||Textbox||Here you can set the default owner of the source. In most cases the value must be: dbo|
|Server||Textbox||Server hostname or IP (needs to resolve to UCMDB application server)|
|Port||Textbox||UCMDB webservices port (default 8080). Consult your UCMDB implementation documentation if this has been set to another port.|
|Caller Application||Textbox||This is important when consolidating to UCMDB. CI's have owners and a behavior can be in place to restrict updates/deletes if not the original Caller Application. By using UCMDB in capital letters (default) this protection can be circumvented.|
|Namespace||Textbox||Set default to
|User||Textbox||Fill in username with sufficient rights for writing and reading data to and from the UCMDB.|
|Password||Textbox||Fill in the corresponding password.|
|Datasource name||HP uCMDB Connector|
|Physical Datasource||HP uCMDB Source|
- Test the datasource connection by pressing Test datasource
- Test the webservice connection by pressing Test webservice
- Click OK to close and save the connector screen
Importing data to DM-ETL+This chapter assumes that a UCMDB connector is already configured as described in the previous chapter. See Figure 3.
- First add a diagram to the solution and select the UCMDB connector as datasource.
- Then double click the title of the diagram to open the diagram main window.
- Select the table that contains the data to be imported.
- The table will now open in the diagram window.
- Check the Visible checkbox for the columns that contains the data required.
- Press Import And View Last to import and view the data.
- When the required data is selected and imported, click save to save the diagram and go back to the solution.
Consolidate data to UCMDB
Important Notes on Usage
- Inserting: Before you are able to use consolidation functionality (inserts), you will have to know which fields define the key for a given dataset. Additionally you will need to refer to the proper item type (which is different from the displayname!). See the "How to check attribute properties" section (on the Working with DM-ETL+ and UCMDB page) to learn how you can find this.
- Updating: UCMDB Keyfields are not allowed to be updated! This inhibits items to be recreated with another identity and incurs unexpected behaviour.
- Before being able to work with relations (creating and deleting), you will need to explicitly allow this operation. See the "How to (dis)allow relationship types" section (Working with DM-ETL+ and UCMDB) to learn how you can achieve this.
- Actual name is needed for reference (not Display Name) and is casesensitive!
- Relationships are not consolidated automatically. You can however easily have consolidation functionality built into your solutions. With the Relationships Tab you can either attempt to Create or Delete a number of relationships, defined by the fields your input diagram delivers.
- When using the relationships Create/Delete functionality you will always need to know the CI End1, CI End2 and the CI Relation ID (with deleting). This information can be found in ClassesLinks in the .link 'table'. Note: Because of the raw format of this entity you cannot use the table preview functionality as you would expect. Instead you will have to actually Import>View Last to see a correct representation of the contained data.
DetailsThe HP U-CMDB Consolidation Task resembles the Database Consolidation Task for the greater part. It is recommended to browse through the Database and SD Consolidation guidelines. Here we will expand on what is HP UCMDB specific.
Creating a HP U-CMDB Consolidation Task
- First make sure you have set up a working target UCMDB Connector (if you are using information from the same UCMDB as source then be sure to have a source UCMDB Connector configured as well).
- Then in the Left Pane click Consolidation>HP UCMDB.
- In the newly created Task select the UCMDB Datasource Connector in the dropdown list.
- Double click the Task to open the UCMDB Consolidation Task.
Figure 5As with most Consolidation types, the Mapping need to be set up in order to know which data fields need to be compared/updated with eachother. This Task is similar to setting up mappings in the Database or SD Consolidation Task. Please refer to these chapters for more information on setting up mappings. After setting up mappings, you will find that the functionality is identical in regards to Updated, Insert, Delete Items and Exceptions. The UCMDB Consolidation Task specific functionality can be found under the Link Class tab. Within the UCMDB structures of linked CI Types/CI's make up CMDB models. These links are relationships between CI Types/CI's. The DM-ETL+ UCMDB Consolidation Task is capable of creating and/or deleting these relationships through the Link Class tab. Creating Links Use the top left pane in the UCMDB Consolidation Task. See Figure 6.
- UCMDB Datasource; where the links need to be created.
- END1 ID Column and END2 ID Column; From a relationship or link perspective, it always needs 2 endpoints to be a valid link. Within the UCMDB this is called Endpoint1 and Endpoint2 represented by columnnames. Also consider that the direction of the relationship is always from END1 ID to END2 ID. If you would want to create a relationship in the other direction you would need to swap the column names from the dropdown list.
- Relation type column; Specify the name of the relationship (make sure that this relationship type is allowed for the targeted CI Types). See the "How to (dis)allow relationship types" section (in the Working with DM-ETL+ and UCMDB page).
- Click Create Links to Push the changes,
Figure 7Five different criteria need to be configured to delete a link or relationship:
- UCMDB Datasource; where the links need to be deleted.
- END1 ID Column and END2 ID Column; From a relationship or link perspective, it always needs 2 endpoints to be a valid link. Within the UCMDB this is called Endpoint1 and Endpoint2 represented by columnnames.
- Relation ID column; It is necessary to specify the Relation ID when deleting relationships, therefor a Relation ID column needs to be provided.
- Relation type column; Specify the name of the relationship type (make sure that this relationship type is allowed for the targeted CI Types). See the "How to (dis)allow relationshiptypes" section (Working with DM-ETL+ and UCMDB)
- Click Delete Links to Push the changes.