Share This:

Hi Everyone,

 

Welcome to our new CMDB Blog for the month of November 2019. We mentioned about new features introduced in CMDB 19.08 in our last CMDB blog. Here is the link of last blog if you have missed it:

https://communities.bmc.com/community/bmcdn/bmc_it_service_support/cmdb/blog/2019/08/27/bmc-cmdb-1908-is-here

 

In this blog, we will provide detailed information about new interface for Class manager & additional capabilities added to the new user interface of Atrium Integrator. Below are the topics which we are going to cover:

 

  • Prerequisites
  • Class Manager Overview
  • Data Imports Console Overview
  • Navigating within Data Imports console
    • Listing, Filtering jobs
    • Executed Jobs
  • Manage Datastore
  • Create a Custom Job & Run it

 

 

Prerequisites

 

  • Accessing and navigating the new CMDB UI

https://docs.bmc.com/docs/ac1908/accessing-and-navigating-the-new-cmdb-user-interface-877695737.html

  • Configuring the URL to access the new CMDB UI

https://docs.bmc.com/docs/ac1908/configuring-the-url-to-access-the-new-cmdb-ui-in-a-single-server-server-group-and-load-balancer-environment-877695526.html

  • General queries about Configuration Management Dashboard UI

https://communities.bmc.com/community/bmcdn/bmc_it_service_support/cmdb/blog/2018/04/03/everything-that-you-need-to-know-about-accessing-new-cmdb-ui

 

 

Class Manager Overview

 

Class Manager has a new user interface that you can access quickly and easily. The Class Manager interface displays all the classes in your data model. You can create or edit a class or relationship.


How to launch Class Manager console?
Once you login to new CMDB Console, CMDB Dashboard is displayed. From this home page, you can open it using ‘Classes’ option under ‘Class Management’ menu.


1.png

2.png

 

Below is the layout of Class manager:

3.png

You can perform the following tasks related to the data model by using Class Manager:

 

1. Define the properties of the class    

 

- You can define the type of class, how it stores data, and (for relationship classes) the relationship.

- You can create new class or subclass by clicking on “Create” or “Add Subclass” button.

   “Create” button is located under navigation pane & “Add Subclass” button is available under Information pane.
4.png

  5.png

2. Configure instance auditing for the class

 

- Auditing enables you to track the changes made to instances of a class. You can select one of these options:-

      1. None - Select this to not perform an audit.
      2. Copy - Select this option to create a copy of each audited instance. Each form related to a class and its super class is duplicated to create audit forms that hold audited instances.
      3. Log - Select this option to create an entry in a log form that stores all attribute values from the audited instance in one field. If you select this option, you must also specify the name of the log form to use.

      6.png

3. Define one or more CI and relationship class attributes

 

- You can create new attribute or edit existing one from Class manager.
- To create new attribute, select the class on which you wanted to create an attribute & click on ‘Add’ button under ‘Attributes’ tab:

               7.png

                8.png

- To modify existing attribute, you can click on attribute name & click on Edit button:

                   9.png

               10.png

4. Specify permissions

- If you do not specify permissions for a class, BMC CMDB assigns default permissions.

               11.png

5. Specify indexes

 

- Indexing classes can reduce database query time. Index attributes that you expect users to query frequently,

   are used by discovery applications to identify Configuration Items (CIs), and are used in reconciliation identification rules.
- Specifying or modifying indexes in a class that already holds a large number of instances can take a significant

   amount of time and disk space. You must avoid creating indexes during normal production hours.

- You can create index from Class manager by clicking on ‘Add’ button in ‘Indexes’ tab :

12.png

                 13.png

Once you save it, you can see new index under “Indexes” tab:

              14.png

6. Propagate attributes in a weak relationship

 

- This step is necessary only if you have created a relationship class that has a weak relationship in which the attributes

  from one class should be propagated to another class.

               15.png

For more detailed information, you can go through below document:
https://docs.bmc.com/docs/ac1908/creating-or-modifying-classes-using-the-class-manager-877695663.html

 

Data Imports Console Overview

 

Data Import console is a home to creating and managing Atrium Integrator (AI) jobs.  For creating a complex Atrium Integrator jobs

which uses difficult logics and multiple data manipulation steps, Pentaho Spoon is still the choice though.

 

How to launch Data Imports console?

CMDB Dashboard is displayed after login to the new CMDB UI. From this home page, one can load ‘Data Imports’ console by clicking

Manage Atrium Integrator’ link available under ‘Job’ menu.

 

1.png

Upon clicking ‘Manage Atrium Integrator’ option, the ‘Data Imports’ console is loaded:

2.png

 

 

Navigating within Data Imports console

 

  • Listing jobs, Filtering jobs

          The console lists all the jobs under the tab 'Total' on its home page.

    3.png

Pagination - Pagination is applied to the list so they are visible in a small number per page. 

Filtering a Job - Jobs can be searched using a filter. For example, jobs that start with string 'SRM' or simply contains

that string in the job name can be searched by just typing 'SRM' (without quotes) in the Filter search box. 

4.png   

        NOTEPlease note that wildcards symbols like '*' or '?' can't be used while searching the jobs

 

  • Executed Jobs

The jobs that have finished execution (either successful or failed) are listed under the tab ‘Executed Jobs’ on Data Imports console

As the name suggests, this tab shows the list of executed jobs, their status and CI Record management information including errors if any.

5.png

If you want to see the Job Run details, please click on the down arrow just beside the 'Run History' column of that job.

6.png

'Run History' column shows the total count of times the job has run.  The count has a link that can be used to drill

down to fine details of the Job run history.

7.png

Job Run History can be further filtered to show latest Job runs by selecting 'Today' and recent Job runs by using option 'Last 7 days' or monthly.

8.png

From the screenshot, you will notice that there are Job status with 'Successful' and 'Failed' too.  You can use the Status drop down

to search only the 'Failed' jobs and then use the drop down inside the Job Run details in order to see the which transformation within the job that failed

9.png

10.png

 

Manage Datastore

 

Datastores are logical connections made to a physical container of the data.  It could be a CSV file, XML file, Database or AR server itself. 

The Target datastore is always an AR Server connection (datastore) as that is where we want to push the data to. 

The data is pushed to CMDB classes form within Remedy AR server. The source datastore can be various connections including CSV, XML or a database.

 

To Create or Manage a datastore, please click on 'Manage Datastore' button on 'Data Imports' console

11.png

 

Please see below the different datastores that you can create :

 

Creating a Datastore

 

12.png

 

Source Datastore using Database as type and MS SQL as a vendor database

 

13.png

 

Source Datastore using Database as type and Oracle as a vendor database

 

14.png

 

Source Datastore using CSV as type

 

15.png

 

Source Datastore using XML as type

 

16.png

 

Source Datastore using AR server as type

 

17.png

 

NOTEFor CSV and XML file connections, please create a store locally on the AR server where the AI job will run to ensure fast performance.

 

 

Create a custom job & Run it

 

The prerequisite for creating a custom job in ‘Data Imports’ console is to have source and target datastore created, as mentioned in the previous step of this document. 

Once the datastores are created, use the ‘Create Job’ command on the console, as seen below.

 

19.png

 

Fill out the new Job Details and also do the Field mapping between Source and Target dataset. 

In the example below, we have used external ‘Database’ as a source data.

 

20.png

 

Do the Field mappings, as seen in the below image

 

21.png

 

Save the Job

 

22.png

 

Click on job name then 'Start Job' button to run it

 

23.png

Thank you for reading this blog.