International Decision Systems has completed the changes of Solifi. Flexera is going to migrate all products/releases/mappings from the old manufacturer name ‘International Decision Systems’ to ‘Solifi’. https://www.solifi.com/news/leading-finance-technology-provider-ids-is-now-solifi/ This change will impact customers who rely on Technopedia Manufacturer ID/Product ID/Release ID & Names or previously discovered data mapped to the old manufacturer will be mapped to the new manufacturer. The change needs the customer to manage downstream processes and reporting in their organization. The spreadsheet “International Decision Systems Changed to Solifi Product list” provides the complete list of all the software products for which the publisher name will be renamed from Solifi from International Decision Systems. Customers should expect these changes to occur starting from October 31st to November 4 th , 2022. ... View more

  This work has now been completed   We are updating/changing the lifecycle dates for RedHat Enterprise Linux (Server) product Major and Minor releases in Technopedia (Full details attached). End of Life and Obsolete date Changes for major versions: We are going to consider the Maintenance Support or Maintenance Support 2 phase as EOL and Obsolete date for all Major versions i.e., RHEL 7, 8 and 9 Reference for lifecycle dates - https://access.redhat.com/support/policy/updates/errata   Example: For Major Version RHEL 7, EOL and Obsolete will be “6/30/2024” End of Life and Obsolete date Changes for Minor versions: We are going to consider the successive (Next) release GA date as the End of life of the current Release date and Obsolete will be the major version Obsolete date.   Example: For Minor Version 7.1, EOL will be “11/19/2015” (GA date of 7.2) as per      https://access.redhat.com/articles/3078  and  Obsolete will be “6/30/2024” as per https://access.redhat.com/support/policy/updates/errata Note: For the final minor release EOL and Obsolete will be the same i.e., OBS date of Major Release Example: For the final Minor Release 7.9 under Major version group 7, EOL and Obsolete will be “6/30/2024” which is the OBS date of Major Release RHEL 7.   Release with name (RHEL X) End of Life and Obsolete date Changes: We are going to consider the EOL and OBS dates of the RHEL X major version. Example: Release x.x (RHEL 7) EOL and Obsolete will be “6/30/2024” which is the EOL/OBS date of RHEL Major Release 7.   This change will impact customers who rely upon Technopedia Lifecycle dates from RHEL to manage their EOL and EOS/ Obsolete program and customers who rely on Technopedia Product ID/Release ID & Names and discovered previously mapped data to these packages. The main changes will be to the RHEL Release Lifecycle Date for Version Groups 7, 8, and 9 and the Release Lifecycle Date of Version x.x (RHEL X) in Technopedia.   Customers should expect these changes on OCT 13, 2022   Reference : https://access.redhat.com/articles/3078 https://access.redhat.com/articles/3078 https://access.redhat.com/support/policy/updates/errata  ... View more

UPDATES: (as of October 21, 2022 8:40pm Central Time): the changes have been implemented as part of ARL build #2710! Please refer to this ARL release announcement for additional details. **Note that ARL update on our cloud environments kicks off at Friday 6pm local time. The update will run on all customer instances throughout the weekend. (as of October 12, 2022 9:35am Central Time): due to the need to keep the stability of our UAT environment during the target date that we communicated earlier, we have decided to push out the changes for another week to October 21, 2022. This will give our teams additional time to ensure the deployment goes as smooth as possible. Thank you for your understanding! (as of September 29, 2022, 9am Central Time): We're still working on thoroughly testing the changes, therefore, the expectation for these changes to happen has been moved out a couple weeks to October 14, 2022. Slight changes on the list of applications that will get impacted (a few applications are no longer on the list). Please refer to the latest spreadsheet at the end of this post. As part of the efforts to align applications across the Application Recognition Library (ARL) and Technopedia, we discovered numerous ARL applications that have been historically curated without adhering to consistent standards. Various drivers, updates, patches, fixes, and other artifacts have been added to the ARL, while other similar items were correctly ruled ineligible for inclusion in Technopedia. This inconsistency makes coverage unpredictable and causes misalignment with normalization in other Flexera solutions. In order to provide consistent, curated, high-quality software coverage, Flexera is aligning coverage eligibility criteria between the ARL and Technopedia (see the unified eligibility criteria here). We plan to remove selected applications from the ARL that should not have been created as independent products under the unified eligibility criteria. This is a continuation of a similar exercise that we have done in the past (see here), where customers can expect: ARL applications listed in the spreadsheet attached to this post will be removed from the Public ARL. Evidence linked to these applications will be marked as "Ignored" in the ARL. Please note, None of the applications listed in this removal falls under any of the following criteria: Commercial applications. Applications linked to licensing content (SKU, PURL, Bundle). Vulnerable applications. If any of these applications has local evidence or is mapped to other applications in the customer environment, it will be retained as Local/Private. Similarly, if any of these applications are mapped to a license in the customer environment, it will also be retained as Local/Private, and the license position will be preserved As a reminder, we plan to begin the removal of these applications as part of the September 30 th  October 14 th , 2022 October 21, 2022 ARL release. Please reach out to us if you have any questions. You can reach our content support via raising a ticket through the customer community.  ... View more

Synopsis:   This article discusses the eligibility of file evidence submitted by customers that can be accepted into the ARL for processing. With huge submissions of file evidence, it has necessitated a discussion of filtering evidence of most value while maintaining a high level of quality expected in the ARL.     Discussion :     Adding large volumes of file evidence to the ARL does not contribute to enhancing the quality of the data, unless the file confirms the recognition of important applications (commercial) or allows you to track usage.   Unfortunately, we are not able to manage large batches of unrecognized file evidence exported from the ‘unrecognized file evidence’ tab. These requests create intensive work and are not conducive to the ARL quality and inventory import performance.   The main objective with unrecognized file evidence is not in clearing them from the unrecognized tab, but in filtering out the evidence of most value to your environment and adding those to our library. The remaining evidence in the unrecognized tab will not impact consumption or recognition on the device. This streamlines our file evidence list and facilitates better usage calculation and recognition.     We are interested in working with ‘qualified’ file evidence that is filtered and vetted by you and your team to be useful in tracking usage (along with the commercial application the file allows to recognize).We would also consider the ‘proven to useless’ file evidence that can be validated as ignored by Flexera. A similar approach has recently been adapted for the Unix distribution (unlicensed) files. Overall, we wish to pursue the file evidence submissions on a more focused target with you.   To better focus on file evidence of most value, we would suggest you filter and then export your unrecognized evidence on two basic conditions:    Evidence data that contains all basic attribute details like file Name, Publisher/Company, Product, Version, File path, Type, Matches.     Important file evidence that you know to be used in calculating usage or in some cases enable recognition for applications ( Ex: Java .exe files, UNIX files that have no extension). Some of the file evidence that we classify as ‘Qualified’ evidence contain the following file paths -   exe, .sys, .sys2, .cmptag, .swtag, .swidtag, dtag and .msi.      Any significant changes to these criteria will be communicated in advance through Content notifications in the Flexera Community. Once we cover the most important file evidence, we can analyse the remaining evidence you have in your environment and determine the importance in processing and adding them to the ARL.   We work to continually improve the quality of evidence in FlexNet Manager, and a large part of that is the importance of the Flexera community. We have thousands of customers participating regularly in discussions that involve updates and changes to Flexera product and content.   This helps other customers new to the environment or working on similar topics to better understand our process. This also helps us update our content libraries based on customer input. We strongly recommend leveraging the Flexera community to better understand the scale of file evidence that will be of consequence to your environment.    For further details on this issue and a larger context to the task of managing evidence in Flexera, we have an important seminar conducted by our Product Manager Nicolas Rousseau that you can find below -    https://community.flexera.com/t5/Search/bd-p/global-search?searchString=Managing+unrecognized+evidence&from=0&sortby=_score&orderBy=desc&pageNo=1&aggregations=%5B%5D&uid=df0591ff-0aa6-11ea-b1e8-02d8a83e9456&resultsPerPage=10&exactPhrase=&withOneOrMore=&withoutTheWords=&pageSize=10&language=en&state=5&suCaseCreate=false       Going Forward:   While we aim to reduce the task of processing large batches of evidence, we are simultaneously focusing on qualitative methods to reduce the impact and presence of unrecognized evidence in the Flexera UI. One method of pursuing this is for us to work on specific scripts that will only filter on evidence of most prevalence in your environment and look to publish a list of file evidence that is required for usage/recognition on that device. This is currently a project in its early stages of development and will be worked on as we expand our evidence quality capabilities.    ... View more

Change Title Red Hat Package Lifecycle Date Changes and Naming convention of Releases Class 1 Customers should be aware and be prepared Change Summary UPDATE: This work has now been completed (as of September 16, 2022). For full details, please see attachment  Red Hat Release Info.xlsx This notification is a continuation of the work which we announced in  March 2022. We are going to differentiate Red Hat base package releases lifecycle dates in release tables in Technopedia. We will be implementing below changes in Technopedia:  Base Packages:  We are going to identify the base packages based on the discovered evidence by keeping their product names without any prefix.  We are going to classify them as base package and will update their EOL dates as follows: Examples:    ruby-2.0.0.648-38.el7.x86_64  ruby-1.8.7.352-3.el6.x86_64    There are two scenarios: a.      Package versions are shared across RHEL versions (i.e., certain package versions are supported on multiple RHEL versions). The versions and EOL for these base packages will be captured in Technopedia as follows: Manufacturer Product Name Version EOL Notes Red Hat ruby 2.3 (RHEL 6) 11/30/2020 Following EOL for RHEL 6 Red Hat ruby 2.3 (RHEL 7) 6/30/2024 Following EOL for RHEL 7   b.      If we cannot identify the underlying RHEL version, we will just leave the EOL empty: Manufacturer Product Name Version EOL Notes Red Hat ruby 2.3 (null) EOL undefined since RHEL version is unknown Red Hat ruby 2.4 (null) EOL undefined since RHEL version is unknown Red Hat ruby 2.6 (null) EOL undefined since RHEL version is unknown   Discovered evidence data will be mapped based on above scenarios. Impact This change will impact customers who rely upon Technopedia Lifecycle dates from RHEL to manage their EOL and EOS/OBS program and customers who rely on Technopedia Product ID/Release ID & Names and discovered previously mapped data to these packages.  The main changes will be to the Red Hat Base Package Lifecycle Date.  Obsolete dates for RHEL 5, 6, 7 and 8 will remain the same as currently recorded in Technopedia. When Customers should expect these changes on Sep 16, 2022 Reference https://community.flexera.com/t5/Technopedia-Blog/Red-Hat-components-from-Base-Package-vs-Software-Collection-to/ba-p/225890 ... View more

As per the ActiveState announcement, they are changing how they distribute, license, and price their products and services. The changes are having impacts on licensing and pricing for few ActiveState products. One of the changes includes retiring the community editions and making few versions as no longer free of change.   The details of the impact can be found here: https://www.activestate.com/blog/important-changes-to-activestate-licensing-and-pricing-model-in-2021/     Impacted products and versions: ActivePerl 5.14.0 and later releases (e.g. 5.16.x, 5.18.x, …) 5.12.2.1203 and later releases in the 5.12 series 5.10.1.1008 and later releases in the 5.10 series 5.8.9.828 and later releases in the 5.8 series ActivePython 3.2.0 and all later releases (e.g. 3.3.x, 3.5.x, …) 3.1.3.5 and later releases in the 3.1 series 2.7.1.3 and later releases in the 2.7 series ActiveTcl 8.6.0 and all later releases (e.g. 8.6.x, …) 8.5.9.1_RC2 and later releases in the 8.5 series 8.4.19.5_RC1 and later releases in the 8.4 series To accommodate the above changes, Flexera is going to update the ActiveState products as below: We are going to create the new products with the ‘Free’ moniker. These free releases will be migrated to the newly created products. ActivePerl (Free) ActivePython (Free) ActiveTcl (Free) The existing products ‘ActivePerl’,’ ActivePython’ and ‘ActiveTcl’ will be represented as restricted based on the version update details. This change will impact customers who rely on Technopedia Product ID/Release ID & Names and discovered previously mapped to ActivePerl, ActivePython and ActiveTcl products. They will be mapped to the new products and specific update releases. The attached spreadsheet provides the full list of all releases in scope for this review which will be created, removed or reserved. Customers should expect these changes to be completed within 4 weeks from the publication date of this notification. ... View more

Technopedia is making changes for evidence recognition for the release Apache Software Foundation Tomcat 9.0 to address a reported problem with false positives. Common file evidence with display name ‘Tomcat9.exe’ has been causing false recognition for Apache Software Foundation Tomcat 9.0 which is not correct.  We will be ignoring this file evidence in Technopedia. This change will impact customers who have relied upon discovered data that was previously recognizing Apache Software Foundation Tomcat based on exe data. We have research on this discovered exe file and there would be no impacts as it shouldn’t be used for recognition. The complete list of changes is in the attachment. An ETA for completion of these changes will be communicated shortly. ... View more

Technopedia is making changes for evidence recognition for Oracle Database to address a reported problem with false positives. Common file evidence with display name 'Oracle.exe' has been causing false recognition for Oracle Database which is not correct.  We will be ignoring this file evidence in Technopedia. This change will impact customers who have relied upon discovered data that was previously recognizing Oracle database based on exe data. We have research on this discovered exe file and there would be no impact as it shouldn’t be used for recognition. The complete list of changes is in the attachment. An ETA for completion of these changes will be communicated shortly. ... View more

Flexera is going to migrate all software products/releases/mappings from current data to proposed data. (See attachment) IBM SDK Java Technology Edition has been renamed to be IBM Semeru Runtime Certified Edition. [1] Reference URL(s): [1] https://www.ibm.com/support/pages/java-sdk-downloads-version-110 [2] https://www.ibm.com/support/pages/node/6512838 [3] https://www.ibm.com/support/pages/semeru-runtimes-support This change will impact customers who rely on not only Technopedia Manufacturer ID/Software Product ID/Release ID and names, but also discovered data that was previously mapped to the current Data will be mapped to the proposed Data. The change needs the customer to manage downstream processes and report in their organization. The spreadsheet Software Product & Release Name Change 12212021.xlsx provides the full list of all the software products and releases for which the manufacturer/product will be renamed from IBM SDK Java Technology Edition to IBM Semeru Runtime Certified Edition. Customers should expect these changes to begin no earlier than January 4th.   ... View more

Java platform 8 Standard was the only version recognized as a Suite (through the Java executable, the JDK and the JRE applications). This inconsistency will be fixed by removing the components for the suite recognition. This will enhance the visibility on the components that were "hidden" by the suite. There should be no impact on the Java license consumptions as the three products are normally covered as primary products.   ETA: 07th January 2021         ... View more

IBM Business Process Manager has been renamed to Business Automation Workflow. This product change will be updated in the ARL. This is to facilitate better management of Business Automation Workflow applications in the Upgrade/Downgrade tab. The Business Automation Workflow products in scope for changes are in the attachment. These changes are expected to take place on 31 st December 2021 ARL release. ... View more

Change Title Manufacturer Name changes in Technopedia Class 2 Customers should be aware and be prepared Change Summary Flexera is unifying Manufacturer names to be consistent across our internal repositories. The Manufacturer names in the attached file "Manufacturer Name Changes" are being changed in Technopedia. Impact This change will impact customers who rely on Technopedia Manufacturer ID’s and Names to manage downstream processes and reporting in their organization.  The impact is expected to be low. The attached list of Manufacturers is in scope to be renamed. When Customers should expect these changes to have been completed starting from July 9 to July 15. ... View more

Change Title SDL to RWS Holdings Product Migration Class 2 Customers should be prepared and take actions Change Summary Flexera is going to migrate all products/releases/mappings from old manufacturer name ‘SDL’ to ‘RWS Holdings’. As RWS Holdings has completed the acquisition of SDL. We will migrate SDL’s products to RWS Holdings. http://www.sdl.com/ https://www.rws.com/about/news/2020/acquisition-of-sdl-by-rws-enhances-capabilities-in-language-services-and-technology/ Impact This change will impact customers who rely on not only Technopedia Manufacturer ID/Product ID/Release ID & Names but also discovered data that was previously mapped to the old manufacturer will be mapped to the new manufacturer. The change needs the customer to manage downstream processes and reporting in their organization. The spreadsheet Migration from SDL to RWS Holdings.xlsx provides the full list of all the Technopedia products for which the manufacturer name will be renamed from SDL to RWS Holdings. ... View more

Change Title EMS Database Management Solutions to EMS Software Development Class 2 Customers should be prepared and take actions Change Summary Flexera is going to migrate all products/releases/mappings from EMS Database Management Solutions to EMS Software Development. As EMS Database Management Solutions renamed as EMS Software Development, all products/releases/mappings will be migrated to EMS Software Development. https://web.archive.org/web/20120126082628/https://www.sqlmanager.net/, https://www.sqlmanager.net/ Impact This change will impact customers who rely on not only Technopedia Manufacturer ID/Product ID/Release ID & Names but also discovered data that was previously mapped to the old manufacturer will be mapped to the new manufacturer. The change needs the customer to manage downstream processes and reporting in their organization. The spreadsheet EMS Database Management Solutions Migrated to EMS Software Development Product list provides the full list of all the software products for which the publisher name has been renamed from EMS Database Management Solutions to EMS Software Development.   Update: The migration has been completed and available as part of the Technopedia version of 2021.07.07. See the attached Excel file that shows the change.        ... View more