Sample 1- Using scripts to generate an all-in-RapidCDMB schema

Table of Contents

Installation Instructions

  • Download Sample1
  • Unzip in RS_HOME

Running Sample1

The deployment and setup procedure is as follows:

  • Unzip the sample package in RS_HOME (..../RapidServer)
  • In RapidCMDBModeler UI, register and run the setup script (Sample1Setup.groovy), which will create the modeling meta-data (as if you have done the modeling through the RapidCMDBModeler UI).
  • After running the setup script, access the RapidCMDBModeler UI/Model Managed Classes view and browse the definitions for modeled classes and their relationships.
  • Generate the modeled classes by clicking on "Generate" in RapidCMDBModeler UI/Model Managed Classes view. All modeled classes will be generated.
  • In order for the model classes to be available from RapidCMDB Admin UI for consumption, reload the RapidCMDB application from RapidCMDB Admin UI / Application Management view.  
  • Use RapidCMDB Admin UI/Modeled Classes view to add more instances for each modeled class. 
  • As the last and most fun step, write new consuming scripts and/or setup script to modify the behavior. These scripts have to be registered and run in RapidCMDB Admin UI/Scripting page.

Sample Scenario 1

What is it:

This sample scenario uses several model classes some of which are inherited from a parent model class. For simplicity, all of the properties are assumed to be in RapidCMDB. However, once related files are downloaded, setup script can easily be modified to have federated data.

The relations between model classes are shown below:   
            
As it can be seen, this scenario represents a workplace where there are employees some of whom are developers, and they can work on many tasks, and participate many teams. On Employee model, we have defined a 1-1 relation on the Employee model to show that a relation to self can be defined on the same model. prevEmp keeps the instance of the previous employee who worked in the same position of the current employee. Similarly, nextEmp keeps the reverse relation between the current employee and its successor in the same position. Not all employees have nextEmp relation filled in.

Scripts provided:

  • Setup script (Sample1Setup.groovy): creates the model classes and relations between them

What is next: 

Once it is registered and run in RapidCMDBModeler UI/Scripting view, you can:

  • start populating the data from RapidCMDB Admin UI/Modeled Classes. Any model UI can also be directly accessed by forming a Url as follows:http://localhost:12222/RapidSuite/<modelName>
    Ex:http://localhost:12222/RapidSuite/employee
    Even though model names start with a capital letter while creating them, when used in Url, it should be in small letters.
  • modify the model classes at RapidCMDBModeler home page (Ex:http://localhost:12223/Modeler). Note that after any model changes, RapidCMDB Admin application has to be reloaded from RapidCMDB Admin UI/Application Management page.
  • write scripts to access, manipulate, and query the data.  These scripts have to be registered and run in RapidCMDB Admin UI/Scripting page. For more information on consuming scripts, visit this document.

Labels

sample sample Delete
tutorial tutorial Delete
cmdb cmdb Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.