USER GUIDE. Snow Integration Manager. Version 5.5. Release date Document date SNOWSOFTWARE.COM

Transcription

1 USER GUIDE Product Snow Integration Manager Version 5.5 Release date Document date

2 CONTENTS 1 Introduction Prerequisites Installation New installation Upgrade Configuration General Inventory File handling Connector options Logging Available integration connectors VMware AirWatch Symantec Altiris AWS Discovery Azure Discovery BMC Atrium Discovery and Dependency Mapping Citrix XenServer Dell KACE Discovery data from file FrontRange Discovery HEAT Discovery HP Discovery & Dependency Mapping Inventory HP Server Automation IBM BigFix Inventory IBM License Metric Tool (ILMT) IBM Tivoli Asset Discovery for Distributed Inventory File Forwarder iquate iqsonar LANDesk Microsoft Hyper-V Microsoft Office Microsoft SCCM MobileIron Red Hat Enterprise Virtualization ServiceNow Express Snow for ServiceNow Page 2 of 24

3 4.26 Snow Device Manager Snow Inventory Oracle Scanner Snow Xml VMware vsphere Import provider settings About Snow Integration Manager Page 3 of 24

4 1 INTRODUCTION This document describes how to install and configure Snow Integration Manager. 1.1 PREREQUISITES Very important! Read before beginning the installation. Verify that the server meets the system requirements for this product; see the document System Requirements for all Snow products, which is available for download at: For configuration of the Snow Integration Connectors, a user account with read-only access rights to the database or on the server is normally required. If additional access rights are required for a specific connector, these will be described in detail in the section of that particular connector. Configuration of Snow third party inventory connectors for IBM TAD4D and IBM ILMT require that IBM Data Server Driver Package is installed on the server where the Snow Integration Manager is installed. Configuration of the Microsoft Office 365 connector requires that the following is installed on the server where the Snow Integration Manager is installed. Microsoft Online Services Sign-In Assistant (64-bit version): Windows Azure Active Directory Module for Windows PowerShell (64-bit version): Download the latest version of Snow Integration Manager from: ftp://ftp.snowsoftware.com Page 4 of 24

5 2 INSTALLATION Make sure that the requirements listed in System Requirements for all Snow products are fulfilled before continuing with the installation. NOTE Run the installation as Administrator. 2.1 NEW INSTALLATION 1. To start the installation, double-click the SetupSIM.exe file. 2. The Snow Integration Manager Setup wizard is started. Click Next. 3. Read and accept the terms of the End User License Agreement. Click Next. 4. In the Custom setup step, select which connectors to install, and select Location for the installation files. Click Next. 5. In the Ready to install Snow Integration Manager step, click Install to start the installation. 6. After the installation has completed, click Finish to exit the Snow Integration Manager Setup wizard. 2.2 UPGRADE The settings of the active integration connectors are stored in the registry. They will be kept intact when SIM is uninstalled INSTALL NEW VERSION 1. Uninstall the existing version of Snow Integration Manager (or Snow External Data Provider) from Programs and Features in the Control Panel. 2. Install the new version of Snow Integration Manager. For details, see New installation. Page 5 of 24

6 2.2.2 TEST THE CONNECTORS After installation, start Snow Integration Manager to test settings and aggregation of the connectors. 1. Click the Inventory file handling tab. 2. Verify the settings for the incoming folders. For details, see Local Inventory server. 3. Click the Connector options tab. 4. To test the settings for each Active connector: a. Click the connector name, and then click Settings. b. In the Properties dialog box, click Test connection. c. If applicable, click Clear Last Aggregation date. d. Close the Properties dialog box. 5. To test aggregation for each Active connector: a. Click the connector name, and then click Aggregate selected. When the aggregation runs, the Aggregate selected button is blue. b. Wait until the aggregation is completed and the Aggregate selected button turns grey. 6. After aggregation is completed, check the logs for any errors or exceptions. (normally in C:\Program Files\Snow Software\Logs\Snow Integration Manager) 7. For each connector, verify that the correct Schedule is set TROUBLESHOOTING In case the connector fails to work, try to remove the connector, and then add and configure it once again. Do the following: 1. Click the connector in the Active connectors list, and then click Remove. 2. Click the connector in the Available connectors list, and then click Add. 3. In the Properties dialog box, configure the connector. 4. Test the connector settings. For details, see Test the connectors. 5. Test aggregation of the connector. For details, see Test the connectors. If the connector still fails to work, also try to remove the registry entries of the connector. Do this after the first step in the procedure described above. In case none of these actions makes the connector work, contact Snow support. Set Log level to ALL and send the result along with the defect description. For details, see Logging. Page 6 of 24

7 3 CONFIGURATION To configure the Snow Integration Manager, open the Snow Integration Manager Properties which is located in the start menu. 3.1 GENERAL Select global settings for Site id and aggregation scheduling. The global Site id setting can be overridden using the Site id setting in the connector specific options. NOTE The global setting for aggregation scheduling will affect all connectors. If connectors are to be scheduled separately, do not enable this setting. 1. In the Site id box, type the site name provided by the Service Provider (SPE platforms only), or the default site name used in the Snow Inventory installation (Enterprise). 2. In the Scheduling section, schedule an aggregation interval (or disable it). Page 7 of 24

8 3.2 INVENTORY FILE HANDLING Select method for handling of inventory data LOCAL INVENTORY SERVER When Snow Inventory Server is running on the same server as the Snow Integration Manager, do the following: 1. Click the Save to local inventory server check box. 2. In the Inventory incoming folder box, specify the folder where the integration connectors will put the inventory files. The default folder is C:\Program Files\Snow Software\Snow Inventory\Server\Incoming \data\processing. 3. In the Announcement incoming folder box, specify the folder where the Discovery data from file, the AWS Discovery, and the Azure Discovery connectors will put the discovery (announcement) files. The default folder is C:\Program Files\Snow Software\Snow Inventory\Server\Incoming \announcements\processing REMOTE INVENTORY SERVER When sending the inventory data to a remote inventory server (such as a Snow Inventory Master Server, a Snow Inventory Service Gateway, or a Snow Inventory Data Receiver), do the following: 1. Click the Save to remote inventory server check box. Page 8 of 24

9 2. Type the complete URL in the Url box. EXAMPLE 3. To activate and use proxy functionality, click Proxy. The Proxy settings dialog box appears. 4. Click the Use proxy check box. 5. In the Settings section, use the default proxy configured in Internet Explorer by clicking the Use default proxy check box, or configure manual proxy settings in the boxes SOFTWARE FILTERING The Software filtering section lists folder paths and file types, which by default are excluded from/included in the inventory. NOTE Software filtering is only applicable for the Microsoft SCCM 2007/2012 and LANDesk connectors. EXAMPLE Using the filter in the image below, all content of the folder _:\WINDOWS\* will be excluded except for the folder _:\WINDOWS\SYSTEM32\SPOOL\DRIVERS\*. Page 9 of 24

10 By default, only.exe and.dll file types will be included in the inventory, but more file types can be added. 1. To remove a filter, select filter in the list and then click Remove. 2. To create a new filter, click Add. The Add software filter dialog box appears. To exclude a folder, type a path in the Filter box, and the click the Excluding check box. Click Save. To include a folder in an already excluded path, type a path in the Filter box, and then leave the Excluding check box cleared. Click Save. To include a new file extension, type the extension in the Filter box, and then click the Is extension check box. Click Save. Page 10 of 24

11 3.3 CONNECTOR OPTIONS Select which connectors to configure. For details of the specific configuration options for each connector, see the sections that follow. 1. To add connectors, select connector in the Available connectors list and then click Add >>. 2. To remove connectors from the Active connectors list, select connector and then click << Remove. 3. To configure connector specific options, click Settings For each specific connector, see the sections that follow. 4. To configure a schedule for a selected Active connector, click Schedule. 5. To rename an Active connector, select connector and then click Rename. 6. To start an immediate aggregation for a selected connector, click Aggregate selected. This option is mostly used for test purposes. 7. In the Missing metadata reporting level list, select how to handle reporting of missing metadata. 8. To include software that lacks description, click the Include software with missing metadata check box. The filename will be used as placeholder for the description. Page 11 of 24

12 3.4 LOGGING On the Logging tab specifications can be made on what information to append to the log files, how the files are formatted, where they are located, and allowed number and size of the files (default settings are recommended). Page 12 of 24

13 4 AVAILABLE INTEGRATION CONNECTORS A number of integration connectors are available within the Snow Integration Manager. Information on how to configure each connector is either available in separate user guides, or described in the sections that follow. 4.1 VMWARE AIRWATCH The AirWatch connector uses an API connection. For a detailed description, see User guide, AirWatch connector. 4.2 SYMANTEC ALTIRIS The Symantec Altiris connector uses a database connection. For a detailed description, see User guide, Altiris connector. 4.3 AWS DISCOVERY The Amazon Web Service Discovery connector uses an API connection. For a detailed description, see User guide, AWS Discovery connector. 4.4 AZURE DISCOVERY The Azure Discovery connector uses an HTTPS connection. For a detailed description, see User guide, Azure Discovery connector. 4.5 BMC ATRIUM DISCOVERY AND DEPENDENCY MAPPING The BMC ADDM connector uses an API connection. For a detailed description, see User guide, BMC ADDM connector. 4.6 CITRIX XENSERVER The Citrix XenServer connector uses an API connection. For a detailed description, see User guide, Citrix XenServer connector 4.7 DELL KACE 1000 The Dell KACE 1000 connector uses a database connection. Page 13 of 24

14 For a detailed description, see User guide, Dell KACE connector. 4.8 DISCOVERY DATA FROM FILE The Discovery data from file connector reads data from files in a folder, and then delivers the data to the Announcement incoming folder in Snow Integration Manager. 1. To add a source folder with discovery data files, click Add. 2. The Source File Folder dialog box appears with the two tabs Configuration and Field Mappings. 3. After settings have been made on the Configuration and Field Mapping tabs, click Preview to view the result of an import and to verify that the mappings are correct. 4. Optionally, type a site Id for this connector CONFIGURATION 1. Click the Configuration tab. 2. In the File folder box, type the folder where the connector will look for files. 3. If applicable for the file, select the Has headers checkbox. Page 14 of 24

15 4. Select file Type in the list. 5. Select data Delimiter in the list FIELD MAPPINGS 1. Click the Field Mappings tab. 2. Select one of the following: a. In the Mappings table, click to type the name of the Source file columns that corresponds to each Target field. b. Select the Map by index check box. In the Mappings table, click to type the index number of the Source file columns that corresponds to each Target field. c. Click Get headers from file to load the headers from a source file. In the Mappings table, select a header in the Source list for each Target field. NOTE If the Has headers check box is cleared on the Configuration tab, the Map by index check box is automatically selected and mandatory. 3. Click OK to save the changes and close the Source File Folder dialog box. Page 15 of 24

16 4.9 FRONTRANGE DISCOVERY The FrontRange Discovery connector uses a database connection. 1. In the Server box, type the SQL server name. 2. Select one of the following: Type user credentials for the FrontRange Discovery database in the User id and Password boxes. Click the Use integrated security check box. 3. In the Database list, select database. 4. To verify the connection, click Test connection. 5. In the Organizations that start with box, specify an organization filter which will be used to select computers that are connected to those organizations. Use % as a wildcard character. 6. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 7. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 8. Optionally, type a site Id for this connector. 9. To optimize handling of network adapter information, select the current version of Snow Inventory Server HEAT DISCOVERY The HEAT Discovery connector uses a database connection (SQL). For a detailed description, see User guide, HEAT Discovery connector. Page 16 of 24

17 4.11 HP DISCOVERY & DEPENDENCY MAPPING INVENTORY The HP DDMI connector reads data from files in a folder. The HP Discovery & Dependency Mapping Inventory (HP DDMI) connector opens each of the HP DDMI scan files (.xsf) and converts the inventory data to a standard Snow inventory file that can be integrated with the Snow database. 1. In the XSF scan file folder box, type the folder where the HP DDMI connector will look for HP DDMI XSF scan files. 2. Optionally, type a Site id for this connector. 3. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 4. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. NOTE Due to high CPU and memory usage the recommendation is to use a server with higher performance than the recommended minimum SIM server requirements, or there is a risk that the HP DDMI aggregation will underperform HP SERVER AUTOMATION The HP Server Automation connector uses an API connection. For a detailed description, see User guide, HP Server Automation connector IBM BIGFIX INVENTORY The IBM BigFix Inventory connector uses an API connection. For a detailed description, see User guide, IBM BigFix connector IBM LICENSE METRIC TOOL (ILMT) The ILMT connector can either use a database connection for ILMT version 7.x or import reports that have been exported from ILMT version 7.x or version 9.x. For a detailed description, see User guide, IBM License Metric Tool connector. Page 17 of 24

18 NOTE For integration with ILMT version 9.x, use the IBM BigFix Inventory connector IBM TIVOLI ASSET DISCOVERY FOR DISTRIBUTED The IBM TAD4D connector uses a database (DB2) connection. For a detailed description, see User guide, IBM TAD4D connector INVENTORY FILE FORWARDER The Inventory File Forwarder connector reads data from files in a folder. 1. In the Inventory file folder box, type the folder where the connector will look for inventory files. 2. In the Data receiver url box, type the complete URL to the Inventory Data Receiver. EXAMPLE 3. To verify the connection, click Test. 4. To activate the proxy functionality, click the Use proxy check box. 5. In the Settings section, use the default proxy configured in Internet Explorer by clicking the Use default proxy check box, or configure manual proxy settings by using the boxes. NOTE The Inventory File Forwarder does not support client-side certificates. If an Inventory 5 Server is configured to require client-side certificates, install an Inventory 5 Service Gateway on the same server where the Snow Integration Manager is installed. Configure the Inventory File Forwarder to deliver the data to the Service Gateway instead of the Inventory Data Receiver (IDR). The Service Gateway will then forward the data to the Inventory Master Server (or another Service Gateway). Page 18 of 24

19 4.17 IQUATE IQSONAR The iquate iqsonar connector uses a database connection. For a detailed description, see User guide, iquate iqsonar connector LANDESK The LANDesk connector uses a database connection. For a detailed description, see User guide, LANDesk connector MICROSOFT HYPER-V The Microsoft Hyper-V connector uses an API connection. For a detailed description, see User guide, Microsoft Hyper-V connector MICROSOFT OFFICE 365 The MS Office 365 connector uses an API connection. For a detailed description, see User guide, Microsoft Office 365 connector MICROSOFT SCCM The Microsoft SCCM connector uses a database connection. For a detailed description, see User guide, Microsoft SCCM connector MOBILEIRON The MobileIron connector uses an API connection. For a detailed description, see User guide, MobileIron connector. Page 19 of 24

20 4.23 RED HAT ENTERPRISE VIRTUALIZATION The Red Hat Enterprise Virtualization connector uses an API connection. 1. Type a Site name for this collection of Red Hat Enterprise Virtualization servers. This setting will override the Global site id. 2. To add one or more Red Hat Enterprise Virtualization Manager connections to scan for physical and virtual machines, click Add. The RHEV Server dialog box appears. 3. Type the Name of the data center. NOTE This name will only be used for reference in the Snow RHEV Scanner Configurator list. The actual data center name is collected via the API. 4. Type the Webservice url for the Red Hat Enterprise Virtualization Manager API. EXAMPLE 5. In the User and Password boxes, type user credentials for an account with access to the Red Hat Enterprise Virtualization Manager API. 6. To verify the connection, click Test. Page 20 of 24

21 4.24 SERVICENOW EXPRESS The ServiceNow Express connector uses an API connection. For a detailed description, see User guide, ServiceNow Express connector SNOW FOR SERVICENOW Snow for ServiceNow populates and maintains ServiceNow with information from Snow License Manager. The ServiceNow CMDB connector populates ServiceNow with information on all hardware and software assets, and relationships between hardware, software, and users whle the ServiceNow Catalog connector populates ServiceNow with hardware and software models. Both the ServiceNow CMDB connector and the ServiceNow Catalog connector use API connections. For detailed information, see User guide, Installation and configuration of Snow for ServiceNow SNOW DEVICE MANAGER The Snow Device Manager connector uses an API connection. 1. In the SDM Web API URL box, type the URL to the Snow Device Manager Web API. 2. In the Domain, User Name, and Password boxes, type credentials for a domain user account with administrative privileges in the Snow Device Manager platform. 3. To only include information on registered devices, click the Include only enrolled devices check box. 4. To verify the connection, click Test connection. 5. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 6. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 7. Optionally, type a site Id for this connector. Page 21 of 24

22 4.27 SNOW INVENTORY ORACLE SCANNER The Snow Inventory Oracle Scanner connector reads data from files in a folder. This connector is used for import of Snow Inventory Oracle Scanner 2.x output xml files. It is also used for processing of inventory result xml files generated by the Snow Inventory Client for Unix. 1. Add one or more folders where Snow Inventory Oracle Scanner will look for xml files. 2. Optionally, type a site Id for this connector SNOW XML The Snow XML connector reads data from files in a folder. Snow XML is an xml format that enables integration of data from any other hardware and/or software inventory system. The Snow XML connector reads data from a structured xml file and converts it to the standard Snow Inventory format. 1. Browse for a folder where Snow XML will look for xml files. 2. Optionally, type a site Id for this connector VMWARE VSPHERE The VMware vsphere connector uses an API connection. For a detailed description, see User guide, VMware vsphere connector. Page 22 of 24

23 5 IMPORT PROVIDER SETTINGS From Snow Integration Manager (named EDP when released) version 4.1 it is possible to import the active provider settings from an earlier External Data Provider 3.x installation, if installed on the same computer. All existing settings on the General tab (company name, site name, schedules) for the Snow Integration Manager will remain the same as in the earlier installation. The Snow Integration Manager Properties application presents the user with an option to import the settings the first time it starts. Note that this message will be displayed only once regardless of the answer being Yes or No. Page 23 of 24

24 6 ABOUT SNOW INTEGRATION MANAGER To check the version of the installed Snow Integration Manager: 1. In Snow Integration Manager Properties, press F1 on your keyboard. The About Snow Integration Manager dialog box appears. 2. Click OK to close the About Snow Integration Manager dialog box. Page 24 of 24