After applying the 5.5.20 patch, the User Console UI is not accessible through IE/Edge browser.
There is no error message on the User Interface, but it appears as though the user was logged in for just a second and the page refreshed back again showing the same Login prompt.
This is caused by a security enhancement in 5.5.20 to store the JSESSIONID in Cookies instead.
This change will require the browser to support Cookies.
Engineering is working on a permanent solution.
1. Login via any browsers other than IE or Edge. Tested with Chrome and it works fine.
2. Using HTTPS protocol instead of HTTP.
IBM’s x86 Server Business has been acquired by Lenovo.
Please refer to the following link: https://news.lenovo.com/pressroom/press-releases/lenovo-set-to-close-acquisition-ibms-x86-server-business/
Technopedia has made these changes accordingly. Related products and mappings under IBM (manufacturer ID: 6517) have been migrated to Lenovo Group (manufacturer ID: 7053).
IBM will be retaining its System z mainframes, Power Systems, Storage Systems, Power-based Flex servers, PureApplication and PureData appliances. Therefore IBM (manufacturer ID: 6517) will stay active.
We have compiled a complete list of the hardware products displaying lineage and relationships affected by this acquisition. Please refer to the list attached to this article.
The 5.5.* Normalize Mapping cube, Unmatched Package report, and Unmatched Files report are disabled by default. This is due to the MatchAddremove and MatchExe configuration settings being disabled in order to improve performance. Please see below if you want to re-enable them.
To enable these, you need to change the following parameters and make them true in Norm.configuration.config (This file can be found under ..\BDNA\Data Platform\Conf)
By default the above values are set to false.
After you change the parameters, you need to rerun the Normalize tasks and then you should see the Normalize Mapping cube with both the Unmatched Package and Unmatched Files report showing up.
If you need to force a full Technopedia catalog sync please follow the steps below:
In the BDNA database run the following:
update BDNA.dbo.TECHNOPEDIA_VERSIONS set PKG_ID=-1 where '_src' = 'TECHNOPEDIA';
The next time you run a Technopedia catalog sync the full catalog will be downloaded and synced with your system.
Please note as this is a full catalog sync this will take some time to complete.
Customers receive an error " Specific user account has no candidate group for the Management Group" when configuring User Console v5.5.13
This issue has been reported in the following scenario:
1)LDAP Authentication is used.
2)Customer license key does not contain Analyze.
Fix : This issue has been fixed in v 5.5.17
For customers performing a fresh v 5.5.13 install:
Download and unzip the attachment: BDNA -31044 Patch for 5.5.13.zip
Install 5.5.13 User Console
Backup and replace the Configure User Console.exe in the User Console/Bin directory with the one provided in the attached zip.
Run User Console Config Wizard.
When using LDAP authentication you may experience the below ("Connection Reset") error when attempting to log in to the User Console:
This issue is caused by using HTTPS binding in IIS with the 'Require Server Name Indication' option selected.
To resolve this issue:
Close the User Console and launch IIS
Go to ‘Sites’ then click on the site being used for Data Platform
Then click on ‘Bindings’
Select the ‘HTTPS’ binding and click ‘Edit’
Uncheck the option for ‘Require Server Name Indication’
Click ‘OK’ then ‘Close’
Launch the User Console and attempt login
Enabling additional logging for Analyze reports can be useful to gather the queries that Analyze runs against the BDNA_PUBLISH database. These queries can then be run against the BDNA_PUBLISH database directly.
The steps below allow the additional logging to be enabled:
On the User Console install machine open File Explorer and go to " C:\Program Files\BDNA\User Console\Tools\Tomcat\webapps\bdna\WEB-INF\classes" or the equivalent location if your installation is not on the C drive.
Open the 'Log4j.xml 'in Notepad ++ or any other editor
Scroll to the bottom of the page and uncomment out the following section by removing the <!-- & --> <appender name="SQLLOG" class="org.apache.log4j.RollingFileAppender"> <param name="File" value="C:/Program Files/BDNA/User Console/Logs/mondrian_sql.log" /> <param name="Append" value="false" /> <param name="MaxFileSize" value="500KB" /> <param name="MaxBackupIndex" value="1" /> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p [%c] %m%n" /> </layout> </appender> <category name="mondrian.sql"> <priority value="DEBUG" /> <appender-ref ref="SQLLOG" /> </category>
Now restart the Data Platform User Console service for the changes to take affect.
Once restarted reopen the User Console and create a simple report and wait for the results to populate.
Now in File Explorer go to ' C:\Program Files\BDNA\User Console\log' you should see a new log called 'mondrian_sql'
Scroll to the bottom of the log file to find the latest sql query that was run. You can then take this query to run on database directly. If you do not see the 'mondrian_sql' log in the logs folder try restarting your machine and try again. After you have gathered the necessary sql queries you may want to comment out the above code in step 3 to disable the additional logging. The log file may grow quiet large over time so you may want to disable the option again or manually clear the 'mondrian_sql' log out now and again.
This article answers some common questions about Technopedia fields in the Software Product Hierarchy.
This answers some common questions about Technopedia fields in the Software Product Hierarchy.
Suite Information: Indicates if a product is part of a suite 'True' or 'False'.
Release: A release is a combination of Manufacturer + Product + Version + (optional Edition) + Release Date (GA).
Licensable: A flag that indicates whether the Software Release is licensable or not.
Version: A Version is different from a Release and does not contain Edition or Release Date. A Version can translate into multiple Releases if it has multiple Editions.
Technopedia tracks to the Minor Version. For example: 11.1.2, 11.1.3, and 11.1.6 are all shown as 11.1 in the Technopedia catalog.
Edition : Software Product Edition name (if Applicable), such as "Enterprise"
Version Group: The name of Version Group (label is Market Version in BDNA Analyze) of the software product. A sample is Version "15" with a Market Version of "2016".
Family: Software Product Brand/Family (if applicable), such as "Office" .
1)Can we disable http options method for IIS?
Ans : Yes, in IIS under 'Request Filtering' --> HTTP Verbs --> OPTIONS Verb may be denied. This will not affect application functionality.
2)Can IIS default welcome page be removed?
Ans : Yes, you can delete this IIS default welcome page: C:\inetpub\wwwroot\iisstart.htm
3)Can we disable weak ciphers on application server?
Ans : Our application uses TLS 1.2 which is a secure protocol currently.
Yes, you can disable other weak ciphers after consulting with your IT/security team.
This support tool is to make it as simple as possible to collect necessary log and configuration files in relation to Data Platform Admin Console
The tool gathers the requested log\conf files and downloads as a zip file in your web browser. This removes the need for you to access the Data Platform server to gather these files.
The Support Tool was introduced in version 5.5.16
Only accounts in Admin Console management role can access to this page and download the relevant files and data.
There are 3 options you can select to download the specific files:
All Logs and Conf: Includs Admin Console configuration files, Admin Console logs and IIS logs.
Logs: Only Includs Admin Console logs.
Conf: Only Includs Admin Console configuration files.
The text box will display the files list that is to be downloaded and it is not editable. The files are collected and compressed in zip format. It takes more time if the logs are large. i.e. 10 minutes for 1GB logs.
Accessing the tool
1) In the Admin Console click the help icon to the right of the screen. 2) In the pop up window select 'Support tool - Data Platform' from the list. (Last option)
3) Scroll down the window until you see the following:
4) Select the necessary dropdown option and click 'Download Diagnostic Data'. The download will then begin and once completed you will see the completed download in your web browser or downloads folder. **This may take some time depending on the total size of the log files, approx 10mins per 1GB of data)
This Support Tool is to make it as simple as possible to collect relevant files and data that are used by support to review, analyze, and provide support feedback. The support tool retrieves files and data from the backend and provides the download in your browser so that users do not need to log in to the server to collect these files
The Support Tool was introduced in version 5.5.16
Only accounts that have the User Console management role can access this page and download the relevant files and data. A limited set of file extensions and SQL statements are allowed.
There are 2 options you can select Standard & Advanced.
By default, the support tool collects the User Console logs, IIS logs, and User Console configuration files. The files are collected and compressed in archive (.zip) format. Large logs take more time; for example, it takes about 10 minutes for 1GB logs.
Collects User Console configuration files, User Console logs and IIS logs.
You can specify which files and data is collected. Things to note:
Supports directory and file paths, one file/directory in one line
The relevant path is base on the installation of User Console. (base on %NORMALIZE_BI_HOME%)
The path must start with one of the followings
The path must start with one of the followings
The default paths are already in the text box.
Only supports SELECT statement
Multiple statements are supported, one statement per line
TOP or ROWNUM is not allowed
Only the first 100 rows are returned and collected
The default statements are already in the text box
Accessing the tool
1) In the User Console click the 'Administrator' drop-down and select 'User Console Help'.
2) In the pop out window select 'Download Diagnostic Data'.
3) A new window will open where you can access the Support Tool. You can then choose if you want to use the 'Standard' or 'Advanced' option.
Microsoft Features on Demand
Features on Demand (FODs) are Windows feature packages that can be added at any time to Windows 10 or Windows Server 2019. They are distributed as .cab files on the Feature on Demand ISO and you can use Deployment Image Servicing & Management (DISM) to add a FOD to a Windows image. There are 2 types of Features on Demand
FOD's without satellite packages: Comprise features with all language resources packaged into the same package. These FODs are distributed as a single .cab file.
FODs with satellite packages: Language-neutral FODs that have language and/or architecture resources in separate packages (satellites). These FODs are distributed as a set of several .cab files, but are installed by specifying a single 'capability name'.
Some FODs come preinstalled with Windows 10 or Windows Server 2019. You can also add additional FODs to support additional hardware features or enable certain use cases. The following Features on Demand come preinstalled, and have no satellite packages
Internet Explorer 11
The following FODs are not preinstalled but are recommended to be preinstalled to enable certain scenarios
Retail Demo Experience RDX
Server Core App Compatibility
The following FODs are not preinstalled
OneCore Developer Mode
MSIX Packaging Tool Driver
RAS Connection Manager Administration Kit (CMAK)
Enterprise Cloud Print / Mopria Cloud Service
Remote server administration tools (RSAT)
Windows Storage Management
Discovery and Normalization of FOD
FOD Products will still continue to be captured into Technopedia along with Support Policies and Lifecycle dates as long as Microsoft still allows the Products to be downloaded separately. For example RSAT can be downloaded separately from the official website here https://www.microsoft.com/en-au/download/details.aspx?id=45520 and will show up in ‘Uninstall or change a program’. Note from the screenshot below this is where we could see the ‘Publisher’, ‘Name’ and ‘Version’ data which is typical for what we discover for Add/Remove evidences.
However, if the Product is downloaded as a FOD and installed using DISM then it only shows up in the ‘Turn Windows Features On or Off’ list. In this scenario, currently it is not possible to discover the ‘Publisher’, ‘Name’ and ‘Version’ data evidence, since DSIM requires Administrator privileges, and extractors do not have the capability to run Command line arguments since the versioning of RSAT is not available for Discovery when installed and activated as a FOD, it is not possible to capture lifecycle EOL/Obsolete dates.
We continue to investigate to determine if our Discovery tools can use other evidences (e.g. Registry, WMI, File exe) to identify instances of when Windows packages have been installed using FOD, rather than through direct download.
When normalizing a data Mashup using a SCCM database, the process completes successfully but the mashup fields do not appear in Flexera Data Platform Analyze Report.
Mashup normalize process works fine with .zip or .csv data source type. The below is a workaround and we will do a permanent fix in further release.
1. Zip the mashup data source from data source database: a. Open "..\BDNA\Data Platform\Bin\Extractor.exe" b. Upload the mashup extract config file. c. Complete the sccm connection fields d. Click "Test" button to make sure SCCM database is connected, then click execute button to zip the mashup data source
2. Then normalize the .zip file instead as a mashup data source.
While running the user console config wizard , on the "Connect to BDNA Data Platform" screen the error message received is : Connect attempt to BDNA Data Platform service failed
Things to check:
1. Ensure your data platform and user console server can communicate with each other over the specified port (http/https).
2. Try using hostname/IP in the User Console config wizard.
3. If the network/port connectivity between the servers is fine but you still cannot get through this page, validate the user console logs.
If you see the below error in setup.log
ERROR UI: System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.
below error in UX.log
The remote server returned an error: (500) Internal Server Error.
you can use below workaround:
In <Data Platform Install directory>/Conf/Norm.configuration.config file:
Update the value of <BI_CONFIG_NORMALIZE_BI_SERVER_URL> to the IP of the User Console server.
Restart Data Platform service and then try to re run the User Console config wizard. This should work.
This article discusses common questions in relation to where on the Data Platform servers are account credentials (i.e. user, password and server details) held or stored for connections to existing data sources and how they're encrypted.
Q: Where in the BDNA or on the Data Platform servers are server details and service account credentials for data sources stored?
A: %BMS_HOME%\Conf\Norm.configuration.config file
Q: When connecting a data source we are prompted for server, user and password details. Where are these stored?
A: In BDNA database, NBF_JOB_PROCESS table, PROCESS_DATA field, USER_PASSWORD node
Q: What algorithm is used to encrypt or hash these credentials?
A: Combination of Data Encryption Standard(DES) and Base64 is used for encryption/hashing.
Hewlett Packard Enterprise Completes Acquisition of SGI
Hewlett Packard Enterprise announced that it has completed its acquisition of SGI on November 1, 2016 . https://www.hpe.com/us/en/newsroom/press-release/2017/03/hewlett-packard-enterprise-completes-acquisition-of-sgi.html
Technopedia has made changes accordingly. Products, releases and mappings under Silicon Graphics International (mfr id: 8615 ) have been migrated to Hewlett Packard Enterprise (mfr id: 213050000 ).
Silicon Graphics International (mfr id: 8615 ) is now marked as 'inactive'.
We have compiled a complete list of both software and hardware products displaying lineage and relationships affected by this acquisition. Please refer to the list attached to this article.
This article discusses Technopedia Software Eligibility.
In general, Technopedia customers can expect to see or request to capture any software products from various categories and sources in Technopedia. There are only a handful of items that Technopedia will not capture, unless there are valid and/or compelling reasons otherwise.
The following is the list of items that Technopedia generally avoids collecting:
Service packs that do not have defined lifecycle dates, are not supported or are not licensable (incl. language packs, security packs, hot packs, compatibility packs, hot fixes, patches, update-sets, knowledge-base).
Software Development Kits (SDK), Toolkits, and API's that are available for free, or those that h ave insufficient information about mandatory attributes that need to be captured in Technopedia.
Add-ins, plug-ins, miscellaneous extras and options that are available to a main software product but are not mandatory or provide new capabilities that is functionally independent from the main product that have no monetary value. Note that certain plug-ins that need to be licensed, come with support and have monetary value, would be regarded as eligible.
Products, add-ins, APIs, JAR files, Libraries and extensions that do not run as applications in their own right, do not come with any support agreements and/or are free to download use and modify. Typically, these can be identified if they have a 'free to use' license type such as MIT, Apache 2.0, GPL, CLL, MPL, CDDL, Eclipse, ISC etc., and are provided by an individual contributor rather than a corporation. However, when a product we would not regard as eligible has already been added to Technopedia in the past, we should endeavor to continue to keep that current should the customer request us to update.
Open Source Software (OSS) applications are eligible to be captured in Technopedia if they are standalone applications that can run independently without requiring other (main) applications to function properly.
Open Source Software (OSS) components are hugely diverse and their eligibility will be subject to good judgement calls. OSS components that we generally add to Technopedia will answer 'Yes' to the following questions:
Does it have any practical use, other than serving as the building blocks for a larger component?
Is it a complex component that provides complete functionality and is installable and ready to use independently?
Does it have version control and support?
Is the component subject to a CVE vulnerability as recorded on the National Vulnerability Database https://nvd.nist.gov /
Is the component captured in nexB DejaCode catalogue https://enterprise.dejacode.com/home /
Technopedia avoids capturing software that is not listed on its manufacturer's official website. This includes non-public information that users obtain through discovery inside the operating systems? management console; software titles used as internal/unofficial references, etc.
Helper applications (including installers/uninstallers, setup files, help files, help applications, wizards, MSI installers, etc).
Portlets, servlets, applets, Java web-starts (JavaWS), and most java-related components such as Java applets and scripts with extensions .java, .jar, .js, .jsp, .json
Portals that serve as the single point of access for information. Technopedia will, however, capture the portal server (the software application that runs the portal). Note that some portals serve as the user interface for the underlying SaaS piece in the back-end, and are eligible to be captured in Technopedia. Typically, these portals provide a branded look and feel for organizations and enter prises, and also provide customized access control and entitlement procedures.
Websites, web pages, and any other web interfaces that simply serve as a front end to a public service. Technopedia does capture software as a service (SaaS), including client applications of cloud-based software offerings. Specifically, for SaaS, there are distinctive advanced criteria that set them apart from simple websites/web pages such as:
The application and data are hosted centrally by the provider where patches and upgrades are deployed transparently
Accessible via web browser and/or custom-built apps installed on Internet connected devices such as desktops, mobile phones
Capability to manage how data is stored in a cloud/cloud-like infrastructure as well as cached locally (offline mode)
Support for different advanced requirements such as data compression, security, backup schedule
Multitenancy where the application layer and sometimes the application itself is different for each tenant based on the varying levels of tenancy
Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) virtualized/containerized solutions that can be deployed either on public cloud instances (Amazon, Azure, etc.) or private cloud (VMWare, OpenStack, etc.) are not eligible for our regular S/W capture in Technopedia. These types of 'Cloud' assets are more suited to be captured in the Cloud Content Pack
Hardware d rivers and/or hardware-specific firmware. Note that Technopedia does capture 'embedded operating systems' that are widely used in multiple variation of devices.
Modules that are simply distinguished from each other on the interface level. Modules that are distinct and are functionally independent will be considered case by case.
Software features or capabilities that are marketed as part of the main software title will not be captured on its own, especially when said features or capabilities are only discernible via license-level identification.
Mobile applications. Note that there are software applications that are available on both mobile as well as traditional platforms, in which case will be captured in Technopedia.
Customer's internal, home-grown software applications
Software and/or releases that are still in development, and not yet in GA
Database backup files and code / scripts that serve only as examples
Software titles in non-Latin alphabets (e.g. software titles in Chinese, Japanese, Arabic, etc.)
Well-known malware, especially the ones that will generally be identified as such in widely used anti-malware applications
Software that are used for illegal activities
Technopedia avoid s capturing gaming software and other related entertainment-oriented software
Technopedia avoid s capturing miscellaneous tools and utilities that are usually bundled with a new PC or other software package that the user is not fully aware that they are installing (also known as bundleware, shovelware, or bloatware)
Technopedia avoids capturing Hardware devices under the Software catalog with the exception for a few security related virtual technologies (i.e. Firewalls, Vulnerability Shield Server, Intrusion Prevention Devices, etc.).
This article discusses how Technopedia product version EOL dates are captured.
This article discusses how Technopedia product version EOL dates are captured.
The Flexera Content process captures the EOL date for a Minor Version only if it is different from the Major Version. This is indicated by the IS_MAJOR attribute on the Software Release table. If IS_MAJOR indicates ?yes?, it a Major Version.
If the EOL date is the same for Versions indicated as Major and Minor, Technopedia only shows EOL Date for the Major Version. In those cases, t his decision was made based on customer demand to only capture the Major Version. There may be some historical entries where Technopedia captured the EOL for a Minor Version even if it is the same as the Major Version, but this is not a cause for concern.
If some EOL data look different for the same product this is probably because a Service Pack or Subversion exists that has different EOL dates. To check the differences, add the PATCHLEVEL attribute from the Software Release table and VERSION and SUBVERSION attributes from the Software Version table to your query to review and compare the detail.
Synopsis How does Technopedia calculate Is_Supported and Desupported Lifecycle Flags? Discussion The Is_Supported and Desupported are flags that are available in the Technopedia Lifecycle and Support Content Pack.
Desupported is a flag that is set in Technopedia and is maintained by the daily update of Technopedia content.
Is_Supported is a flag that is calculated and updated on the Customer Data Platform instance at the time of Technopedia Synch based on parameters. It can be either 'yes or 'no'. The defaults for Lifecycle calculation can be viewed in the Technopedia Settings. They default to an Industry Average Number of Months and Version Increments, but can be changed to a custom setting if needed.
REASON_IS_SUPPORTED is an additional attribute that refers to the IS_SUPPORTED value and provides a reason why the object is or is not supported.
Here is the logic and order of how Flexera calculates and sets the values for the Is_Supported flag. Rules below are followed from 1 to 4, and the first rule to be met is applied.
In any case, when Technopedia finds DISCONTINUEDFLAG or DESUPFLAG =?yes?, then Is_Supported = ?no?. REASON_IS_SUPPORTED = ?Technopedia flagged this as Discontinued/De-supported'.
If the SW Product has END_OF_LIFE or OBSOLETE dates that are NOT NULL, they are used to calculate the IS_Supported Flags.
If END_OF_LIFE (or OBSOLETE if END_OF_LIFE is NULL) is in the future, then Is_Supported = ?yes?. REASON_IS_SUPPORTED = ?Technopedia EOL Date not met yet?. If END_OF_LIFE (or OBSOLETE if END_OF_LIFE is NULL) is in the past, then Is_Supported = ?no?.REASON_IS_SUPPORTED = ?Technopedia EOL Date?.
If the SW Product END_OF_LIFE and OBSOLETE Dates are NULL, and the GENERAL_AVAILABILTY date is NOT NULL, then the GENERAL_AVAILABILTY Date is used to calculate the EOL of the product based on the Industry Averages (available in Technopedia Settings).
If the CALC_EOL is in the future, then Is_Supported = ?yes?. REASON_IS_SUPPORTED = ?Product is less than GA + x months?? If the CALC_EOL is in the past, then Is_Supported = ?no?. REASON_IS_SUPPORTED = ?Product is GA + x months??
If the END_OF_LIFE, OBSOLETE and GENERAL_AVAILABILTY dates are NULL, then the SW MAX_VERSION_ORDER and VERSION_ORDER are used to determine if the VERSION is supported based on the Industry Averages of Supported Versions. (Available in Technopedia Settings).
If the delta of the SW MAX_VERSION_ORDER - VERSION_ORDER is greater than the Industry Average of Supported Versions, then Is_Supported = ?no?. REASON_IS_SUPPORTED = ?More than X versions apart?. If the delta of the SW MAX_VERSION_ORDER - VERSION_ORDER is less than the Industry Average of Supported Versions, Is Supported = ?yes?. REASON_IS_SUPPORTED = ?Less than X versions apart?.