Starting from beacon version 14.2.0, Data Platform standalone extractors can be executed on the beacon to collect data using specific loader configurations (refer to the table below). The data will be imported into IT Visibility.
Existing custom Data Platform extractors can be used with IT Visibility as long as they use loader configurations listed below. If you need to create a new custom extractor for IT Visibility, contact Flexera Services.
NOTE: BDNA_Normalize_Extractor_5.5.76_3002 supports the new security/encryption features. See the section, "Use Extractor Version 5.5.76 for Greater Security," below, for details.
C:\DPV5\EXTRACTION\Extractor.exe -X "C:\DPV5\orion(11.5.1).extractor(MSS).config" -O "C:\ProgramData\Flexera Software\Beacon\IntermediateData\DataPlatformExtractor" -H localhost -PT 1433 -C SolarWindsOrion -U sa -P Admin123456789 -I false -F SolarWindsOrion_US.zip
Extractor Command Options and Example Values
[-X] <Xml Config file full path> ; C:\DPV5\orion(11.5.1).extractor(MSS).config
[-O] <Output file path> ; C:\ProgramData\Flexera Software\Beacon\IntermediateData\DataPlatformExtractor
[-F] <Output file name> ; SolarWindsOrion_US.zip
[-H] <Database host name> ; localhost
[-PT] <Database port> ; 1433
[-C] <Database Catalog name> ; SolarWindsOrion
[-U] <Database user name> ; sa
[-P] <Database user password> ; Admin123456789
[-I] <Database Windows Authentication> ; true or false
For the other Extractor options, run the command Extractor.exe -?.
Extractor
|
Extractor Config File
|
---|---|
Solarwinds Orion (11.5.1,12.0,12.1) (MSS) | orion(11.5.1).extractor(MSS).config |
Solarwinds Orion (12.1) (MSS) | orion(12.1.0).extractor(MSS).config |
JAMF Casper (earlier than version 9) | casper.extractor(mysql).config |
JAMF Casper 9 | casper9.extractor(mysql).config |
JAMF Casper 10 | casper10.extractor(mysql).config |
ASG Trackbird |
trackbird.extractor(MSS).config, |
BDNA Discover |
discover.extractor(ORA).config |
BMC BladeLogic |
bladelogic(8.8).extractor(ORA).config, |
CA IT Client Manager (ITCM) |
itcm.extractor(MSS).config |
CiscoWorks LAN Management Solution (LMS) |
ciscoworks.extractor(SQA).config |
HP Network Automation |
hpna.extractor(ORA).config |
LANDesk |
landesk.extractor(MSS).config, |
Lansweeper |
lansweeper.extractor(MSS).config, |
Novell ZENworks |
zenworks.extractor(MSS).config |
OCS |
ocs.full.extractor(mysql).config |
Scalable |
scalable.extractor.config |
HP Discovery and Dependency Mapping Advanced (DDMa) |
hpddma.extractor(MSSQL).config, |
IBM TCM |
tivoli.tcm.extractor(MSS).config, |
IBM Tivoli Application Dependency Discovery Manager |
taddm.extractor(DB2)(9.5)(L2INTRFC).config, |
IBM Tivoli Asset Discovery for Distributed |
tad4d.extractor(DB2)(7.5).config, |
IBM Tivoli Asset Discovery for z/OS |
tad4z.extractor(DB2).config |
Microsoft Assessment and Planning Toolkit (MAP) 7 |
map.full.extractor.config |
Microsoft Assessment and Planning Toolkit (MAP) 8 |
map8.extractor(MSS).config |
Radia Client Automation Enterprise |
radia.extractor(MSSQL).config |
Lakeside SysTrack |
systrack.extractor(MSS).config |
If the same file already exists in folder C:\ProgramData\Flexera Software\Beacon\IntermediateData\DataPlatformExtractor, it will overwrite it next time when generating the new one.
If you cannot see the generated zip file, please review the command options you used or see more details in the log folder. e.g. C:\DPV5\log\normalize.txt.
On the Action tab, specify the full path of Extractor.exe for Program/script. For Add arguments (optional), enter the command options you used in step five.
NOTE: If you have multiple connections to several data sources, create a scheduled task for each connection. Leave enough time between them for one to finish before the next one starts to run.
Any error during the upload of the file will be moved to the Error folder C:\ProgramData\Flexera Software\Beacon\IntermediateData\DataPlatformExtractor\Error.
It will only keep the latest error zip file per connection. Upload third-party inventory data is defaulted to run every ten minutes. If the Data Platform extractor is scheduled to run more often than ten minutes, only the latest zip file within the ten minutes will be uploaded.
Version 5.5.76 of the standalone extractor includes new security and encryption functionality. Formerly, the command-line tool required all the configuration options to be included as command-line options. Some of these options could potentially include sensitive data. With this release, customers have the option to create an encrypted config file that includes the configuration settings to use with the extractor. This config file can be passed as the lone command-line argument keeping all the data that would formerly have appeared on the command line secure.
-S Saves a secure (encrypted) copy of the configuration filename you specify with the -X command-line option. The secure config file will have .edf appended to the filename. For example, if you pass a config filename of sccm.extractor.config, the resulting secure config file's filename will be sccm.extractor.config.edf.
To use the extractor to create a secure config file, invoke the extractor from the command line using the -S option along with all the other command-line options you would typically use to obtain data from your selected data source. The -S option captures all other command-line options, as well as the chosen schema file content, and saves it to an encrypted config file.
Example: Entering the following on the command line...
Extractor.exe -S -X "sccm.extractor.config" -O "MyOutDir" -H qslserver\sqlinstance -PT 1433 -C schemaname -U username -P password -I false -F MyOutFile.zip
...creates a new file named sccm.extractor.config.edf.
To use an encrypted config file you previously created with the -S option, simply invoke the extractor on the command line and pass it the name of the encrypted config file you want to use.
Example: Extractor.exe "sccm.extractor.config.edf"
on Jan 04, 2021 12:48 PM - edited on Aug 28, 2024 11:31 AM by jlockard1
I found that running FLEXERA_Normalize_Extractor_5.5.35_3003.exe as described in step 2 did not create the EXTRACTION folder. It only displayed the BDNA Normalize Extractor dialog. The FLEXERA_Normalize_XXX.zip file is a 7-Zip self-extracting file, so you can use the 7-Zip File Manager to extract the files and manually put them in the EXTRACTION folder.
Hi - SCCM is missing from the list of extractor configs listed in this article - is that deliberate, i.e. does that mean that the SCCM extractors that always worked with Data Platform will *not* work in with this process?
I think the list above describes this method as a workaround for not having these data sources directly supported by IT Visibility at the time. Please refer to Inventory Data Sources Supported for IT Visibility for the current list.
That doesn't mean that it wouldn't work, but Flexera would obviously point at the supported approach instead as the preferred and supported method.
Thanks John,
I get that, but the data imported by sharing of SCCM data via a "supported" ITAM connected SCCM source is not equivalent to what is/was brought in by an SCCM extractor (Data Platform style) connection.
For example:
* Usage data is not imported from the ITAM (supported) method, so if that's required in ITV then you would need the extractor
* If you have pass-thru query requirements, that is only possible when extractor based connections
Whilst I used SCCM as an example the question I'm really asking is whether the extractor method is really limited to what's listed in the documentation, or whether it would work for any properly developed/tested extractor that would have worked with Data Platform on prem.
Of course, there are design considerations such as any extractor based import will only be processed in ITV and not flow into ITAM. On the other hand - an ITAM connected inventory source such as SCCM will automatically flow into ITV (as of Feb 2023). However if I build an ITAM inventory import for Solarwinds, the Solarwinds data won't flow into ITV and if I need it in ITV as well I need to build/setup an ITAM based connector as well as an extractor based connector.
Overall I've found it challenging to properly understand what does/doesn't flow automatically and what needs additional customisation, so we are totally dependent on the list of supported apps in the documentation being kept up to date.
Thanks for the feedback.
regards,
Murray
I understand. The good news is that it will work, and that Flexera will continue to add more data sources to the supported list.
Please be aware that passthru isn't supported with ITV though. (It's in the roadmap backlog...)
Thanks,
Under supported data sources that require configuration I see Altiris Client Management Suite is listed, but when I download the extractor, I don't see an extractor config for Altiris. Can you point me in the right direction? I need to add Altiris as an external connection. Thanks!