Goverlan Integration


Caution: You should always perform a backup of the Service Manager database prior to running an integration. The EasyVista team will not resolve any issues related to the update or deletion of data and its impact on your platform.

Note: To set up this integration, the Goverlan agent must be deployed on workstations so that inventory data can be loaded. To find out more, please contact your EasyVista consultant.

Overview of the integration

Goverlan is a software that provides remote support and the automation of IT processes, inventory reports, etc.

This integration enables you to run Talend jobs and integration models to import technical inventory data relating to equipment, software and attributes from the Goverlan database into the Service Manager database.
The Equipment Catalog and Software Catalog will be updated in Service Manager once normalization processing has been run. The Attributes reference table will be updated in Service Manager once the data has been restructured.

  • You should download the relevant package to perform the integration.
  • Talend jobs can be run as standalone jobs.
  • Talend jobs and Goverlan integration models can be scheduled to run on a regular basis using a Windows or Linux scheduler.
  • Once you have scheduled the integration, you should check the data extracted by Goverlan regularly before integrating it in the Service Manager databases.
     

Note

  • The integration is based on the fundamentals of preimport processing. This includes storage, processing of external data in Service Manager tables and data normalization in order to standardize the data for the existing repository.
  • Talend is the third-party tool used to build this preimport processing via its jobs.
     
Integration Data Feed (direction) Authentication Type Integration Connector Options

Logo - EasyVista EV initials.png Goverlan

Down arrow.png

Logo - Talend.png

Down arrow.png

Logo - EasyVista EV initials.png Service Manager

N/A
Available versions
SaaS On Premise
Service Manager Check icon.png Check icon.png
Third-Party Product Check icon.png Check icon.png

Talend - definitions

Talend is an ETL (Extract Transform Load) tool used to extract information from a data source, modify it and reload it in a destination. The source and destination of the data can be a database, a Web service, a CSV file, etc.
    Open url.png See the Talend documentation

  • A job contains a set of interconnected components that are used by Talend to run data flow management processes.
  • The Talend Build Job function is used to create archives containing all of the files required to run jobs, such as BAT, PS1 and SH files as well as all context parameter files. 
  • The compiled jobs can be run as standalone jobs on any server, without using the Talend Open Studio console. You can schedule the jobs to be run from a batch file, PowerShell or Linux shell using Windows Task Scheduler or a Linux cron.

Notes

  • The Goverlan agent must be installed on the workstations where inventory reports are required.
  • Java Runtime Environment (JRE) must be installed on the workstation where the Goverlan integration is performed.
  • The configuration of Service Manager production databases required for the integration is now available in the standard version from version 2022 onwards.
    • For On-Premises customers whose Service Manager version is earlier than 2022, you must perform the configuration described in the procedure.
    • For SaaS-based customers whose Service Manager version is earlier than 2022, you must submit a request to the EasyVista CMC team.
  • The Talend jobs provided with the integration can be run as standalone jobs.
    • You do not need to acquire a Talend license.
    • You do not need to use the Talend Open Studio console.
  • In the procedure, you can see an example of how to schedule the dedicated Goverlan integration models using the smoIntegration tool.
    • This tool is only available for On-Premises customers.
    • For SaaS-based customers, you can schedule the integration models using scheduled tasks, i.e. using the Service Manager) smoScheduler tool, an external scheduler such as Windows Task Scheduler, or a third-party application.
          Open url.png See How to automate an integration.
  • Customers must specify the variables specific to their environment in a properties file listing the paths of the Excel files required for the integration and the parameters for accessing the Goverlan and Service Manager SQL servers.
  • Rules for mapping Goverlan data and Service Manager data:
    • Equipment: Mapped using the Type/Manufacturer/Model unique key.
    • Software: Mapped using the Software/Publisher unique key.
    • Attributes: Mapped using the Attribute unique key.
  • Data integration in Service Manager databases:
    • For security reasons, a specific GOVERLAN_READER user must be created in the Service Manager production databases. This user will only be granted the access rights required for performing the Goverlan integration. The access rights will be restricted to certain Service Manager tables in order to perform specific operations.
    • Customers can use a customer-specific exclusion list to monitor the relevant software references based on their organization's policy.
    • To ensure optimal performance of the platform and minimize normalization processing, only data that is new or modified since the previous processing will be extracted. References that do not exist in Service Manager will automatically be created.

Caution

  • You must not modify any of the files in the package. If you do so, the integration will not run correctly. The EasyVista team will not resolve any issues related to the modification of files and its impact on your platform.
  • In the DefaultProperties.txt properties files, do not insert any spaces or tabs in the values. Do not enter quote marks.
  • You should always perform a backup of the Service Manager database prior to running an integration. The EasyVista team will not resolve any issues related to the update or deletion of data and its impact on your platform.
  • For SaaS-based customers, a VPN tunnel is required in order to ensure the connection between the Goverlan and Service Manager databases.

Best Practice

  • Schedule an inventory report to run on a regular basis on workstations using the Goverlan agent in order to load technical data relating to equipment, software and attributes regularly in the Goverlan database.
  • Schedule and define the run frequency of Talend jobs and integration models based on the frequency at which you plan to check the data extracted by Goverlan.
  • You should always perform a backup of the Excel normalization files prior to making any modifications. This enables you to revert back to the original version if required.

Operating principle

Display Steps
Goverlan integration - Operating principle.png

In Goverlan

  • (1) Connection to the Goverlan database via Talend. Extraction of equipment, software and attribute data via three specific Goverlan SQL views.

In Service Manager via Talend

  • Equipment and software data
    • (2) Storage of data in Service Manager E_GOVERLAN_..._VIEW tables.
    • (3) Normalization processing to standardize data for Service Manager catalogs via E_GOVERLAN_..._TRANSCO tables.
    • (4) Storage of normalized data in E_GOVERLAN_..._TO_EZV tables.
  • Attribute data
    • (5) Conversion of the data structure to normalize it for the Service Manager reference table and storage of the restructured data in an E_GOVERLAN_..._TO_EZV table.

In Service Manager via integration models

  • (6) Execution of six dedicated integration models to integrate processed data from the E_GOVERLAN_..._TO_EZV tables into the Service Manager production databases (AM_ASSET, AM_SOFTWARE, AM_CHARACTERISTICS tables).

Integration process

The integration between Goverlan and Service Manager comprises seven main steps.

Step 1 (Note: Only if your Service Manager version is earlier than version 2022): Create the dedicated Service Manager tables for the Goverlan integration

Step 2 (Note: Only if your Service Manager version is earlier than version 2022): Add the GOVERLAN_READER user to the Service Manager production databases

Step 3: Configure Talend jobs based on the customer's environment

Step 4: Run the initial integration between Goverlan and Service Manager

Step 5: Configure the Goverlan integration models

Step 6: Schedule the running of Talend jobs and Goverlan integration models

Step 7: Check the equipment and software data extracted by Goverlan

Prerequisites:

1. Install the Goverlan agent on the workstations where inventory reports are required.

2. Import the Goverlan package to your workstation and extract it.

         Download icon.png  Package Goverlan

         Package content.png

Step-by-Step Integration Process

Create the dedicated Service Manager tables for the Goverlan integration

Note:
  • Perform this step only if your Service Manager version is earlier than version 2022.
  • For SaaS-based customers, you must submit a request to the EasyVista CMC team.

Step 1: Create the Service Manager tables for equipment data

1. Access the Service Manager SQL server.

2. Run the three SQL scripts found in the folder called 1.create tables in evo_backoffice (sql). This folder is one of those in the Goverlan package you extracted. This will create the dedicated Service Manager tables for equipment in the EVO_BACKOFFICE database.

SQL script Table created in Service Manager Data stored Table structure
goverlan_asset_view.sql E_GOVERLAN_ASSET_VIEW Storage of data extracted from the Goverlan database via the specific Goverlan view, vSystemView E_GOVERLAN_ASSET_VIEW table structure.png
goverlan_asset_transco.sql E_GOVERLAN_ASSET_TRANSCO Storage of normalized data for updating the Equipment Catalog (Type, Manufacturer, Model) E_GOVERLAN_ASSET_TRANSCO table structure.png
goverlan_asset_to_ezv.sql E_GOVERLAN_ASSET_TO_EZV Storage of processed data ready to be integrated in the Service Manager production database E_GOVERLAN_ASSET_TO_EZV table structure.png

Step 2: Create the Service Manager tables for software data

1. Access the Service Manager SQL server.

2. Run the three SQL scripts found in the folder called 1.create tables in evo_backoffice (sql). This folder is one of those in the Goverlan package you extracted. This will create the dedicated Service Manager tables for software in the EVO_BACKOFFICE database.

SQL script Table created in Service Manager Data stored Table structure
goverlan_software_view.sql E_GOVERLAN_SOFTWARE_VIEW Storage of data extracted from the Goverlan database via the specific Goverlan view, vSoftwareInventory E_GOVERLAN_SOFTWARE_VIEW table structure.png
goverlan_software_transco.sql E_GOVERLAN_SOFTWARE_TRANSCO Storage of normalized data for updating the Software Catalog (Software Name, Publisher) E_GOVERLAN_SOFTWARE_TRANSCO table structure.png
goverlan_software_to_ezv.sql E_GOVERLAN_SOFTWARE_TO_EZV Storage of processed data ready to be integrated in the Service Manager production database E_GOVERLAN_SOFTWARE_TO_EZV table structure.png

Step 3: Create the Service Manager tables for attribute data

1. Access the Service Manager SQL server.

2. Run the SQL script found in the folder called 1.create tables in evo_backoffice (sql). This folder is one of those in the Goverlan package you extracted. This will create the dedicated Service Manager table for attributes in the EVO_BACKOFFICE database.

SQL script Table created in Service Manager Data stored Table structure
goverlan_attributes_to_ezv.sql E_GOVERLAN_ATTRIBUTES_TO_EZV
  • Storage of data extracted from the Goverlan database via the specific Goverlan view, vSystemAttributes
  • Storage of processed data ready to be integrated in the Service Manager database
E_GOVERLAN_ATTRIBUTES_TO_EZV table structure.png

Add the GOVERLAN_READER user to the Service Manager production databases

Note:
  • Perform this step only if your Service Manager version is earlier than version 2022.
  • For SaaS-based customers, you must submit a request to the $ProductName_logo_easyvista{{/velocity}} CMC team.

1. Access the Service Manager SQL server.

2. Open the folder by selecting Security > Users.

3. Run the create user 'goverlan_reader' (50004).sql query found in the folder called 2.create user goverlan_reader (sql). This folder is one of those in the Goverlan package you extracted.

The user will be added to Service Manager account 50004 in the EVO_DATA database.

4. Run the create user 'goverlan_reader' (50005).sql query found in the folder called 2.create user goverlan_reader (sql). This folder is one of those in the Goverlan package you extracted.

The user will be added to Service Manager account 50005 in the EVO_DATA database.

Configure Talend jobs based on the customer's environment

Prerequisites: Install Java Runtime Environment (JRE)

1. Download the latest version of the Java Runtime Environment setup (64-bit version) from the Java website to your workstation.

         Download icon.png  Java Runtime Environment (JRE) - Select the Windows Offline (64-bit) version

2. Run the executable file to install Java Runtime Environment (JRE) on your workstation.
 

Step 1: Configure the Talend job, GOVERLAN_GET_DATA_CATALOG

1. Go to the folder called 3.standalone jobs (engine)\goverlan_get_data_catalog_1.0\GOVERLAN_GET_DATA_CATALOG\local_project\goverlan_get_data_catalog_1_0\contexts. This folder is one of those in the Goverlan package you extracted.

2. Open the Default.properties file.
         File Default properties.png

3. Specify the parameters based on your environment.

Caution: Do not insert any spaces or tabs in the values. Do not enter quote marks.

  • filePath: Path to the Excel files and software exclusion file.
  • EZV_sql...: IP address, port, login and password of the SQL server in your Service Manager environment.
  • GOVERLAN_sql...: IP address, port, login and password of the SQL server in your Goverlan environment.

4. Save the file.
 

Step 2: Configure the Talend job, GOVERLAN_LOAD_DATA_TO_EZV

1. Go to the folder called 3.standalone jobs (engine)\goverlan_get_data_catalog_1.0\GOVERLAN_LOAD_DATA_CATALOG\local_project\goverlan_load_data_catalog_1_0\contexts. This folder is one of those in the Goverlan package you extracted.

2. Open the Default.properties file.

3. Specify the parameters based on your environment.

4. Save the file.

Run the initial integration between Goverlan and Service Manager

Step 1 (optional): Define the list of software that should not be extracted from the Goverlan database

Aim: In this step, you can specify the software whose licenses you do not monitor, such as plugins, runtimes, sdk, etc. This software data will not be loaded in the Excel normalization files. You can adapt the default list based on the software monitoring policy adopted by your organization.

1. Go to the folder called 3.standalone jobs (engine). This folder is one of those in the Goverlan package you extracted. 

2. Open the text file, software_exclusion_list.txt. This contains the software exclusion list.

3. Add one row for each software to be excluded.

         Software - Exclusion list.png

4. Save the file.

Step 2: Extract data from the Goverlan database

1. Run the GOVERLAN_GET_DATA_CATALOG_run.xx script found in the folder called 3.standalone jobs (engine)/goverlan_get_data_to_ezv_1.0\GOVERLAN_GET_DATA_TO_EZV. This folder is one of those in the Goverlan package you extracted. Depending on your OS, the script may be a batch file (BAT), PowerShell (PS1) or Linux shell (SH).

  • The GOVERLAN_GET_DATA_CATALOG job will run.
  • The Excel normalization files with the equipment and software data extracted from the Goverlan database will be created.
  • Attribute data extracted from the Goverlan database will be restructured and normalized for the Service Manager reference table and then stored in an E_GOVERLAN_..._TO_EZV table.

Step 3: Normalize equipment and software data

Aim: The normalization steps enable you to standardize equipment and software data extracted from the Goverlan database for your Service Manager equipment and software repositories.

Note: No normalization processing is required for attribute data.

Normalize equipment data

1. Go to the folder containing the Excel files. This is the folder specified in the DefaultProperties.txt file in the filePath variable.

2. Open the Excel file, catalog_asset.xls.
         Asset - Before Excel file.png

3. Complete the three columns, CATEGORY_TRANSCODED, MAKE_TRANSCODED and MODEL_TRANSCODED. Enter the type, manufacturer and model of the equipment as required by your equipment repository in Service Manager.
         Asset - After Excel file.png

4. Save the file.

Normalize software data

1. Go to the folder containing the Excel files. This is the folder specified in the DefaultProperties.txt file in the filePath variable.

2. Open the Excel file, catalog_software.xls.
         Software - Before Excel file.png

3. Complete the two columns, SOFTWARE_NAME_TRANSCODED and SOFTWARE_PUBLISHER_TRANSCODED. Enter the software name and publisher as required by your software repository.
         Software - After Excel file.png

4. In the FOLLOW_SOFTWARE column, indicate if you want to monitor this software in your repository (value 1) or not (value0).

Note: This column is used to specify the list of software to be excluded if you did not define it in the exclusion list described above in step 1.a.

5. Save the file.

Step 4: Integrate the normalized equipment and software data in the E_GOVERLAN_..._TO_EZV tables in Service Manager

1. Run the GOVERLAN_LOAD_DATA_CATALOG_run.xx script found in the folder called 3.standalone jobs (engine)/goverlan_load_data_to_ezv_1.0\GOVERLAN_LOAD_DATA_TO_EZV. This folder is one of those in the Goverlan package you extracted. Depending on your OS, the script may be a batch file (BAT), PowerShell (PS1) or Linux shell (SH).

  • The GOVERLAN_LOAD_DATA_CATALOG job will run.
  • The Excel files containing the normalized equipment and software data will be integrated in the E_GOVERLAN_..._TO_EZV tables in Service Manager.
  • Excel control files will be generated.

Step 5: Check the integrated data in the E_GOVERLAN_..._TO_EZV tables in Service Manager

Aim: This step enables you to check the integrity of the data integrated in the E_GOVERLAN_..._TO_EZV tables and to correct it if required.

1. Go to the folder containing the Excel files. This is the folder specified in the DefaultProperties.txt file in the filePath variable.

Check equipment data

1. Check the contents of the Excel file, output_asset_to_ezv.xls.

2. If you see any normalization errors:

  • Open the Excel file, catalog_asset.xls containing the references you normalized earlier in step 3.

    Best Practice icon.png  Perform a backup of the file before making any corrections. This enables you to revert back to the original version if required.

  • Modify the CATEGORY_TRANSCODED, MAKE_TRANSCODED and MODEL_TRANSCODED columns to correct errors in equipment references.
  • Save the file.
  • Run data integration again using the GOVERLAN_LOAD_DATA_CATALOG_run.xx script.

Check software data

1. Check the contents of the Excel file, output_software_to_ezv.xls.

2. If you see any normalization errors:

  • Open the Excel file, catalog_software.xls containing the references you normalized earlier in step 3.

    Best Practice icon.png  Perform a backup of the file before making any corrections. This enables you to revert back to the original version if required.

  • Modify the SOFTWARE_NAME_TRANSCODED, SOFTWARE_PUBLISHER_TRANSCODED and FOLLOW_SOFTWARE columns to correct errors in software references.
  • Save the file.
  • Run data integration again using the GOVERLAN_LOAD_DATA_CATALOG_run.xx script.

Check attribute data

1. Open the Excel file, output_software_to_ezv.xls containing the attribute data that was integrated.

2. If you see any errors, please contact the EasyVista Support team.

Configure Goverlan integration models

Step 1: Import the dedicated integration models for integrating Goverlan data in Service Manager

Note: Perform this step only if your Service Manager version is earlier than version 2022.

1. Select Administration > Import / Export > Import in the menu.

2. Import the six EXP files found in the folder called 4.integration models for service manager (exp). This folder is one of those in the Goverlan package you extracted.
 

Step 2: Find the integration models for integrating Goverlan data

1. Select Administration > Integration > Integration Models in the menu.

  • The names of the integration models contain the prefix Goverlan.
  • They are used to integrate processed data from the E_GOVERLAN_..._TO_EZV tables into the Service Manager production databases (AM_ASSET, AM_SOFTWARE, AM_CHARACTERISTICS tables).

         Integration model - Goverlan model list.png
 

Step 2: Integrate equipment data

Update the Equipment Catalog

1. Find the integration model called 01.Goverlan / Create equipment catalog that will update the Equipment Catalog.

2. Click Edit icon.png next to the integration model.

3. Select the language of the data to be integrated.

4. Configure the connection to the Service Manager database.

  • Select the datasource data type.
  • Click Define.
             Integration model - General configuration.png
  • Specify the password in the connection string for accessing the EVO_BACKOFFICE database.
             Integration model - General configuration - Connection string.png

Specify the SQL query that will search for the data to be integrated in the Query field.
         Integration model - Equipment create catalog query.png

5. Proceed to step 2 of the integration model and define the mapping of fields as shown below.
         Integration model - Equipment create catalog mapping.png

Update the Equipment Inventory

1. Find the integration model called 02.Goverlan / Import equipment that will update the Equipment Inventory.

2. Click Edit icon.png next to the integration model.

3. Select the language of the data to be integrated.

4. Configure the connection to the Service Manager database.

  • Select the datasource data type.
  • Click Define.
  • Specify the account and password in the connection string for accessing the EVO_BACKOFFICE database.
  • Specify the SQL query that will search for the data to be integrated in the Query field. Replace the values indicated in yellow below with the production database account.
    Note: You can use the WHERE clause to import only equipment with inventory dates modified since the previous integration.
             Integration model - Equipment import query.png

5. Proceed to step 2 of the integration model and define the mapping of fields as shown below.

  • In the Source column, select the relevant STATUS_ value corresponding to the language you selected earlier in step 1. By default, the value is English, i.e. STATUS_EN.
             Integration model - Equipment import mapping.png

Step 3: Integrate software data

Update the Software Catalog

1. Find the integration model called 03.Goverlan / Create software catalog that will update the Software Catalog.

2. Click Edit icon.png next to the integration model.

3. Select the language of the data to be integrated.

4. Configure the connection to the Service Manager database.

  • Select the datasource data type.
  • Click Define.
  • Specify the password in the connection string for accessing the EVO_BACKOFFICE database.

Specify the SQL query that will search for the data to be integrated in the Query field.

Note: You can use the WHERE clause to import only monitored software. The value in the Source column of the Excel file is FOLLOW_SOFTWARE = 1.

         Integration model - Software create catalog query.png

5. Proceed to step 2 of the integration model and define the mapping of fields as shown below.
         Integration model - Software create catalog mapping.png

Update the License Inventory

1. Find the integration model called 04.Goverlan / Add software to equipment that will update the License Inventory.

2. Click Edit icon.png next to the integration model.

3. Select the language of the data to be integrated.

4. Configure the connection to the Service Manager database.

  • Select the datasource data type.
  • Click Define.
  • Specify the account and password in the connection string for accessing the EVO_BACKOFFICE database.
  • Specify the SQL query that will search for the data to be integrated in the Query field. Replace the values indicated in yellow below with the production database account.
    Note: You can use the EXCEPT clause to import only software that is new or modified since the previous integration, e.g. change in version, new software detected.
             Integration model - Software add to equipment query.png

5. Proceed to step 2 of the integration model and define the mapping of fields as shown below
         Integration model - Software add to equipment mapping.png

Step 4: Integrate attribute data

Update the Attributes reference table

1. Find the integration model called 05.Goverlan / Create attributes that will update the Attributes reference table.

2. Click Edit icon.png next to the integration model.

3. Select the language of the data to be integrated.

4. Configure the connection to the Service Manager database.

  • Select the datasource data type.
  • Click Define.
  • Specify the account and password in the connection string for accessing the EVO_BACKOFFICE database.
  • Specify the SQL query that will search for the data to be integrated in the Query field. Specify the relevant value for the ATTRIBUTE_ field corresponding to the language you selected earlier in step 1. By default, the value is English, i.e. ATTRIBUTE_EN.
             Integration model - Attributes create query.png

5. Proceed to step 2 of the integration model and define the mapping of fields as shown below.

  • In the Source column, select the relevant ATTRIBUTE_ and TYPE_ values corresponding to the language you selected earlier in step 1. By default, the value is English, i.e. ATTRIBUTE_EN and TYPE_EN.
             Integration model - Attributes create mapping.png

Update attributes in the Equipment Inventory

1. Find the integration model called 06.Goverlan / Add attributes to equipment that will update attributes in the Equipment Inventory.

2. Click Edit icon.png next to the integration model.

3. Select the language of the data to be integrated.

4. Configure the connection to the Service Manager database.

  • Select the datasource data type.
  • Click Define.
  • Specify the account and password in the connection string for accessing the EVO_BACKOFFICE database.
  • Specify the SQL query that will search for the data to be integrated in the Query field.
             Integration model - Attributes add to equipment query.png

5. Proceed to step 2 of the integration model and define the mapping of fields as shown below.

  • In the Source column, select the relevant ATTRIBUTE_ value corresponding to the language you selected earlier in step 1. By default, the value is English, i.e. ATTRIBUTE_EN.
             Integration model - Attributes add to equipment mapping.png

Schedule the running of Talend jobs and Goverlan integration models

Best Practice icon.png  Schedule and define the run frequency of Talend jobs and integration models based on the frequency at which you plan to check the data extracted by Goverlan.

Schedule the running of Talend jobs

Use a scheduler such as Windows Task Scheduler to automate the running of jobs.

Step 1: Schedule the GOVERLAN_GET_DATA_TO_EZV job

1. Go to the folder called 3.standalone jobs (engine)\goverlan_get_data_catalog_1.0\GOVERLAN_GET_DATA_CATALOG. This folder is one of those in the Goverlan package you extracted.

2. Schedule the GOVERLAN_GET_DATA_CATALOG_run.xx script to run. Depending on your OS, the script may be a batch file (BAT), PowerShell (PS1) or Linux shell (SH).

The GOVERLAN_GET_DATA_TO_EZV job will run based on the frequency defined.

  • New or modified equipment and software data will be extracted from the Goverlan database. This data will be added to the existing Excel normalization files.
  • New or modified attribute data will be extracted from the Goverlan database. This data will be restructured and normalized for the Service Manager reference table and then stored in an E_GOVERLAN_..._TO_EZV table.

Step 2: Schedule the GOVERLAN_LOAD_DATA_TO_EZV job

1. Go to the folder called 3.standalone jobs (engine)\goverlan_get_data_catalog_1.0\GOVERLAN_LOAD_DATA_CATALOG. This folder is one of those in the Goverlan package you extracted.

2. Schedule the GOVERLAN_LOAD_DATA_CATALOG_run.xx script to run. Depending on your OS, the script may be a batch file (BAT), PowerShell (PS1) or Linux shell (SH).

The GOVERLAN_LOAD_DATA_TO_EZV job will run based on the frequency defined.

  • The Excel files containing the normalized equipment and software data will be integrated in the E_GOVERLAN_..._TO_EZV tables.
  • Excel control files will be generated.

Schedule the running of Goverlan

 integration models

You can define a scheduled task using the Service Manager smoScheduler scheduler. You can also use an external scheduler such as Windows Task Scheduler, or a third-party application.
    Open url.png See How to automate an integration.

  • The six Goverlan integration models will run based on the frequency defined.
  • Processed data from the E_GOVERLAN_..._TO_EZV tables will be integrated into the Service Manager production databases (AM_ASSET, AM_SOFTWARE, AM_CHARACTERISTICS tables).

Schedule the integration using the smoIntegration tool

  • Note: The smoIntegration tool is only available for On-Premises customers.
  • It is used to run integration models not defined as scheduled tasks instead of using the Service Manager) smoScheduler scheduler.
  • You can download the smoIntegration.exe file found in the folder called 5.run smo_integration on-prem (bat). This folder is one of those in the Goverlan package you extracted.
     

Step 1: Disable the running of Goverlan integration models by the Service Manager smoScheduler scheduler

1. Select Administration > Integration > Integration Models in the menu.

2. Click Edit icon.png to edit each  Goverlan integration model.

3. Unselect the Enabled box in the window for scheduling the task.

Step 2: Create the script for running the six Goverlan integration models automatically in the production databases

1. Open the run_smoIntegration (50004) file found in the folder called 5.run smo_integration on-prem (bat). This folder is one of those in the Goverlan package you extracted.

2. Replace the values highlighted in yellow with the values of your environment.

  • smoIntegration: Path to the smoIntegration executable on your hard disk.
  • portSmoServer variable: Port of the smoServer service.
  • ipSmoServer variable: IP address of the smoServer service.
  • accountEZV variable: Service Manager database account, e.g. 50004, 50005.

Caution: You must not modify the modelname variables found between double quotes because they are the English names of the models.

@echo off

set smoIntegration=C:\talend\smo_integration
set accountEZV=50004
set portSmoServer=xx.xx.xx.xx
set ipSmoServer=xx.xx.xx.xx

del /q %smoIntegration%\log\*.*

echo Integration is running... Please wait...

echo 01.Goverlan / Create equipment catalog
%smoIntegration%\smoIntegration.exe -port=%portSmoServer% -ip=%ipSmoServer% -account=%accountEZV% -modelname="01.Goverlan / Create equipment catalog"

echo 02.Goverlan / Import equipment
%smoIntegration%\smoIntegration.exe -port=%portSmoServer% -ip=%ipSmoServer% -account=%accountEZV% -modelname="02.Goverlan / Import equipment"

echo 03.Goverlan / Create software catalog
%smoIntegration%\smoIntegration.exe -port=%portSmoServer% -ip=%ipSmoServer% -account=%accountEZV% -modelname="03.Goverlan / Create software catalog"

echo 04.Goverlan / Add software to equipment
%smoIntegration%\smoIntegration.exe -port=%portSmoServer% -ip=%ipSmoServer% -account=%accountEZV% -modelname="04.Goverlan / Add software to equipment"

echo 05.Goverlan / Create attributes
%smoIntegration%\smoIntegration.exe -port=%portSmoServer% -ip=%ipSmoServer% -account=%accountEZV% -modelname="05.Goverlan / Create attributes"

echo 06.Goverlan / Add attributes to equipment
%smoIntegration%\smoIntegration.exe -port=%portSmoServer% -ip=%ipSmoServer% -account=%accountEZV% -modelname="06.Goverlan / Add attributes to equipment"

3. Save the file.

4. Repeat the procedure to configure the run_smoIntegration (50005) file found in the folder called 5.run smo_integration on-prem (bat). This folder is one of those in the Goverlan package you extracted.

Check the equipment and software data extracted by Goverlan

Aim:

  • When Talend jobs are run regularly, all equipment and software data that is new or modified will be extracted from the Goverlan database and added to the Excel normalization files on a regular basis.
  • You must then normalize these new or modified references before they can be integrated in the Service Manager databases.
     

Step 1: Check equipment data

1. Go to the folder containing the Excel files. This is the folder specified in the DefaultProperties.txt file in the filePath variable.

2. Open the Excel normalization file called catalog_asset.xls.

3. Complete the three columns, CATEGORY_TRANSCODED, MAKE_TRANSCODED and MODEL_TRANSCODED. Enter the new and modified references.

Modifications made to equipment data will be integrated in the Service Manager repository when the Goverlan integration models are next run.
 

Step 2: Check software data

1. Open the Excel normalization file called catalog_software.xls.

2. Complete the columns, SOFTWARE_NAME_TRANSCODED, SOFTWARE_PUBLISHER_TRANSCODED and FOLLOW_SOFTWARE. Enter the new and modified references.

Modifications made to software data will be integrated in the Service Manager repository when the Goverlan integration models are next run.

Description of Talend jobs

GOVERLAN_GET_DATA_CATALOG

         Talend - Job GOVERLAN_GET_DATA_CATALOG.png

This job is used to:

  • Extract equipment, software and attribute data from the Goverlan database using specific Goverlan SQL views.
  • Clean and normalize the equipment and software data extracted to ensure standardized equipment and software repositories in Service Manager.
  • Modify the structure of the attribute data extracted to adapt it to the structure of the Service Manager Attributes reference table.
  • Ensure that the job was correctly run.

GOVERLAN_LOAD_DATA_TO_EZV

         Talend - Job GOVERLAN_LOAD_DATA_TO_EZV.png

This job is used to:

  • Store only the most recent version of a given software.
  • In the Service Manager software repository, delete all software no longer detected by Goverlan (cleanup step).
  • Generate Excel control files containing the data that is ready to be integrated in Service Manager.
  • Ensure that the job was correctly run.

List of files to download

Note: To find out how to use them, see the integration process.

         Download icon.png  Package Goverlan

Tags:
Last modified by Unknown User on 2022/04/21 14:37
Created by Administrator XWiki on 2022/04/21 14:32

Shortcuts

Recent changes
•  EV Service Manager
•  Service Apps
•  EV Self Help
•  Service Bots

Powered by XWiki ©, EasyVista 2021