Prerequisites
To populate the SAM Core user interface with data on users, applications, computers, and usage, you need to install the following inventory sources locally:
| Inventory source | Description |
|---|---|
| Snow Inventory Agents for Linux, Unix, macOS, and Windows | The agents inventory computers and servers in your IT environment. |
| Snow Integration Manager and Connectors | The connectors integrate with third-party inventory solutions and virtualization technologies to collect inventory data. |
For more information, see SAM Core technical overview.
Some sections of SAM Core require specific prerequisites in addition to these general prerequisites, as described in the following sections.
Adobe Creative Cloud
To populate the Adobe Creative Cloud pages with data on licenses, users, applications, and activity, you need the following inventory sources:
| Inventory source | Description |
|---|---|
| Snow Inventory Agents for macOS and Windows | The agents inventory devices and Adobe Creative Cloud on-premises applications as well as user activity in those applications. Note: For proper recognition of Adobe Acrobat edition by the agent, you may require an Adobe Acrobat Registry Scan script from the Data Intelligence Service. Contact Flexera Support for access to and help with the script. |
| Snow Integration Connector for Adobe Creative Cloud | The connector imports information on license plans and users from one or several Adobe Creative Cloud portals. For more information, see Adobe Creative Cloud Connector. Note: You are recommended to schedule data aggregations for the Adobe Creative Cloud connector every 24 hours. Aggregations more often than on a daily basis adds minimal benefit, since the Snow Inventory Agent is scanned on a daily basis in most cases. Manual aggregations should only be done when necessary, for example, due to changes within the portal itself. |
Generic SaaS
To populate the Generic SaaS pages with data on subscriptions, applications, and activity, you need the following inventory source:
| Inventory source | Description |
|---|---|
| Snow Integration Connector for SaaS | The connector imports information on subscriptions, application use, and user activity from the respective service provider. Not all connectors can provide activity data. For more information and configuration, see SaaS Connector. Note: You are recommended to schedule data aggregations for the SaaS connector every 24 hours. Aggregations more often than on a daily basis adds minimal benefit. Manual aggregations should only be done when necessary. |
Microsoft 365
To populate the Microsoft 365 pages with data on subscriptions, users, applications, and activity, you need the following inventory sources:
| Inventory source | Description |
|---|---|
| Snow Inventory Agents for macOS and Windows | The agents inventory devices and Microsoft 365 on-premises applications as well as user activity in those applications. |
| Cloud application metering | The cloud application metering browser extensions collect cloud application use and user activity. For more information, see Cloud application metering. |
| Snow Integration Connector for Microsoft 365 | The connector imports information on subscription plans and some user activity from the Microsoft 365 portal. For more information, see Microsoft 365 Connector. Note: You are recommended to schedule data aggregations for the Microsoft 365 connector every 24 hours, to get the latest activity data from the Microsoft 365 portal. Aggregations more often than on a daily basis adds minimal benefit, since the Snow Inventory Agent, which also provides activity from on-premises inventory sources, is scanned on a daily basis in most cases. Manual aggregations should only be done when necessary, for example, due to changes within the portal itself. |
Oracle
To populate the Oracle pages with inventory data, you need the following inventory sources. It is recommended to deploy all Oracle Scanners to all environments.
| Inventory source | Description |
|---|---|
| Snow Inventory Agents | Gather the inventory data collected by the Oracle Scanners and transport it to the Snow Extender, for further transport to Snow Atlas. Note: You must enable the Oracle scan by configuring the Oracle element in the agent configuration file, snowagent.config. For more information, see Agent configuration file. |
| Snow Inventory Oracle Scanner (SIOS) | Inventories your Oracle Databases, Database Options, Management Packs and E-Business Suite products. For more information, see Snow Inventory Oracle Scanner. |
| Snow Inventory Oracle Middleware Scanner (SIOMS) | Inventories your Oracle Fusion Middleware products. For more information, see Snow Inventory Oracle Middleware Scanner |
| Snow Inventory Java Scanner (SIJS) | Inventories your Java products. For more information, see Snow Inventory Java Scanner |
Oracle verified data
To populate the Oracle verified data tab with inventory data, additional inventory sources must be installed, as shown in the table below.
| Inventory source | Description |
|---|---|
| Snow Inventory Oracle Hardware Scanner (SIOHWS) | Collects hardware-related data on environments that contain Oracle Database and Middleware products. For more information, see Snow Inventory Oracle Hardware Scanner |
| VMware vSphere Connector | Gathers data from a VMware infrastructure according to the configuration of the VMware vSphere Connector. For more information, see VMware vSphere Connector. |
The version requirements per inventory source for the Oracle verified data feature is listed below. It is recommended to always use the latest versions of the inventory sources.
- SIOS: version 7.0 or later. To gather E-Business Suite data, version 8.4 or later is required.
- SIOMS: version 3.0 or later.
- SIJS: version 3.2 or later.
- SIOHWS: version 1.0 or later.
- SIM: version 5.39 or later
- Snow Inventory Agents: version 6.0 or later.
The inventory sources must be installed on all Oracle environments.
If the following virtualization technologies are used, you must install the inventory sources on all environments, as follows:
- Oracle Solaris Zones on the Global Zone
- Oracle VM Server for SPARC on the Control Domain
- Oracle VM Server for x86 on the Dom0
Permission requirements
To view and manage Oracle data in SAM Core, the user must have one or more Snow Atlas permissions enabled, as listed in the table below. All permissions are enabled by default for the Administrator role. For more information on roles in Snow Atlas, see Roles.
| Permission | Description |
|---|---|
| omo.oracle.general.r | Gives the user access to the main menu of the Oracle section in SAM Core. The user can view the information, but cannot import, update, or edit any data. Note: Additional permissions as listed below must be enabled for the user to get access to some additional functions. |
| omo.oracle.crud | Gives the user permission to view, import, update, and edit the data in the Oracle section of SAM Core. Note: Additional permissions as listed below must be enabled for the user to get access to some additional functions. |
| omo.oracle.reports.r | Gives the user permission to see SAM Core reports that are specific to Oracle. It gives the user access to the Reports tab in the Oracle section of SAM Core. |
| omo.oracle.compliance.crud | Gives the user permission to manage Oracle license assignments. It gives the user access to the License assignments and Auto-assignments sections on the Entitlements tab in the Oracle section of SAM Core. |
| omo.oracle.mapping.crud | Gives the user permission to enter information on the physical processor socket capacity into SAM Core, to be used in Oracle licensing calculations for Oracle Databases standard editions. It gives the user access to the Oracle computer model mapping function on the Home > Administration page. |
| omo.oracle.audit.crud | Gives the user permission to manage and download data that is accepted by Oracle as verified data. It gives the user access to the Oracle verified data tab in the Oracle section of SAM Core. Note: The E-Business Suite product category is excluded from the permission by default. To enable a user to view and manage E-Business Suite data, contact Flexera Support. |
Datacenters and clusters
To automatically populate the Datacenters and clusters pages with data, you need the following inventory sources:
| Inventory source | Description |
|---|---|
| Citrix Hypervisor Tools | Must be installed on each virtual machine hosted on Citrix Hypervisor. |
| VMware Tools | Must be installed on virtual machines to automatically identify host/guest relations. Host names and IP addresses are used for mapping. |
| VMware vSphere Web Services SDK | Must be installed on ESX servers. |
| Snow Integration Connector for Citrix Hypervisor | Gathers data from a Citrix infrastructure. For more information, see Citrix Hypervisor Connector. |
| Snow Integration Connector for Microsoft Hyper-V | Gathers data from a Microsoft Hyper-V infrastructure. For more information, see Microsoft Hyper-V Connector. |
| Snow Integration Connector for Red Hat Enterprise Virtualization | Gathers data from a Red Hat Enterprise infrastructure. For more information, see Red Hat Enterprise Virtualization Connector. |
| Snow Integration Connector for VMware vSphere | Gathers data from a VMware vSphere infrastructure. For more information, see VMware vSphere Connector. |
Note that if you do not have Snow Integration Manager and Connectors installed, you can add datacenters and clusters manually in SAM Core instead, based on the inventoried computers in your IT environment.