Summary This article provides information regarding how to download AdminStudio. Discussion The AdminStudio product download is available at the Flexera Software Product and License Center. The  Product and License Center allows you to download products, as well as related product files. To access the AdminStudio product download via the Product and License Center: Log In to the Community. Click on "Product Access" and select "Product and License Center" From there, find the column with AdminStudio listed and select the “LET'S GO” button below that column Once you have been logged in to the Product and License Center, select "Product list" from the right-hand navigation list If applicable, select the AdminStudio product from the Product List. Select the applicable product version from the Product and File Downloads list. Note: If applicable, clicking the Release Archive tab will give you access to previous versions of AdminStudio.  Select the file you wish to download. Click the download hyperlink or select one of the Advanced Download Options. Click on the licenses link as shown in the below image to know the type of license information, Total number of licenses available, and corresponding Activation Code. More information can be found in the knowledge base article "How to Access the Product and License Center": https://community.flexera.com/t5/Downloading-Products/How-to-Access-the-Product-and-License-Center/ta-p/99340 Additional Information AdminStudio Product Serial Number Guidelines: -20 characters long -All characters are capitalized -Do not start with the letters ISMTK -Formatted as follows: (7-3-10): XXXXXXX-XXX-XXXXXXXXXX or (4-4-4-4): XXXX-XXXX-XXXX-XXXX for AdminStudio 2014 and later. -No letter "O"s are contained in the serial number, it's the number zero "0". -Make sure to include the dashes/hyphens (-) when entering. -There are no extra spaces either before or after the serial number.   Order Numbers typically are formatted as one of the following formats: SSF-XXXXXXXXXX Additional information about the Download and License Overview for AdminStudio 2016 and Later can be obtained from the following document: Download and Licensing Overview for AdminStudio   ... View more

Summary FLEXnet Connect is a solution that Flexera sells to software vendors that is designed to help you stay connected with your customers after they install your applications. Synopsis FLEXnet Connect is a solution that Flexera Software sells to software vendors that is designed to help you stay connected with your customers after they install your applications. Keeping software updated is one of the many benefits of FLEXnet Connect, but Flexera also recommends that software vendors build in an option to disable automatic update checking. If you are using an application that uses FLEXnet Connect, your application may have a configuration option to disable update checking. Please check your application's menu options. If your application does not have this option, Flexera has created a tool called the Software Manager that can disable automatic update checking. The Software Manager utility lists all applications currently using FLEXnet Connect on your computer and the FLEXnet Connect's status with that application. Discussion You may already have the Software Manager installed. If the Software Updates or Program Updates shortcut is listed in your Start menu, then the Software Manager is installed. If you do not have the Software Manager installed, follow these instructions to download and install it: To download and install the Software Manager: Download the latest FLEXnet Connect 6.1 Software Manager and save it to your Desktop. The latest FLEXnet Connect Software Manager can be downloaded here. Double-click on the FLEXnet Connect executable and follow the instructions to install the Software Manager. Once installed, you can run the Software Updates shortcut to start the Software Manager. We provide 3 options for disabling the Software Manager: Option #1: Download and Disable the Software Manager with the Uninstaller Perform the following steps to download and disable the Software Manager with the uninstaller. To download and disable the Software Manager with the uninstaller: Download the Software Manager uninstaller and save it to your Desktop. Double-click SoftwareManagerUninstall.exe and follow the instructions to disable the Software Manager. NOTE: The SoftwareManagerUninstall.exe only removes Windows Registry entries which are responsible for starting the common software manager after a reboot. No files are removed. Option #2: Disable the Software Manager Using Task Manager Perform the following steps to disable the Software Manager using Task Manager. To disable the Software Manager using Task Manager: Open the Task Manager by running Task Manager as an Administrator. Navigate to the Startup tab. Right-click Common Software Manager. Select Disable. Option #3: Disable the Software Manager Using the Registry Editor Perform the following steps to disable the Software Manager using the Registry Editor. To disable the Software Manager using the Registry Editor: Open the Windows Registry Editor (regedit.exe) by running the Windows Registry Editor as an Administrator. Navigate to the following Windows Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run Back up the Windows Registry entry by exporting it to a Windows Registry (.reg) file. Delete the ISUSPM Value Name along with its Value Data by right-clicking ISUSPM and selecting Delete. We suggest using the option, out of the 3 options, to disable the Software Manager that matches your preferences. Or if a particular option does not work for you, you can move on to the other options. ... View more

Summary This article explains how to suggest changes to the ARL, SKU Library, or PURL. Question How can I suggest changes to the FlexNet Manager Suite ARL, SKU Library, or PURL? Answer Flexera welcomes requests from our customers for updates to the Application Recognition Library (ARL), Stock Keeping Unit (SKU) Library and Product Use Rights Library (PURL). I have not purchased a maintenance plan or it has expired. Can I still suggest changes? Simple content requests which fulfill the criteria below can be submitted to the Content team. However, Flexera will not provide updates on the progress or completion of any request and they may be denied by the Content team. Where do I submit the content request? Content requests should be submitted through a support case in our Community at  https://community.flexera.com When will my request be completed? Requests will be qualified and prioritized at our discretion. As general guidelines: We accept all submissions sent through Support. Most requests we receive are completed within 1 to 2 weeks. For example, ARL updates are often available within 1 to 2 weeks; SKU and PURL requests are usually available monthly. Large or particularly complex requests will be assessed separately. For any request that we're unable to deliver in a reasonable time-frame, Flexera Services may be available. Why has my request not been added? Please keep in mind that some applications, SKUs, and PURLs can't be added to our published libraries, such as: Application evidence that has been modified due to customer repackaging or don't include valid publisher, product or version information. The provided SKU details are incomplete, ambiguous, or otherwise unverifiable. Product Use Rights that are only available to a single customer through a unique contractual term. What information do I need to provide for the request to be fulfilled? ARL Unassigned Evidence Customers may generate Evidence submissions and submit these to Flexera Support, which will be attached to a Support ticket and redirected to the Content Team. This can be done in one of two ways, depending upon the version of FlexNet Manager Suite for Enterprises installed. All versions allow export of evidence into a Microsoft Excel spreadsheet, or some versions of FlexNet Manager Suite include a Share button on the Applications views that will generate a submission file. This submission can be emailed directly from the Share button wizard when enabled or can be saved locally and attached or uploaded separately. Note: Detailed instructions for exporting uninstalled evidence can be found in the attachments section. Classifications If you believe that an application has the wrong classification e.g. that it's currently listed as commercial, but it should be freeware, this can be submitted to the Content Team as well.  If possible, please also provide the web link from the vendor which proves the correct classification. New Applications All new application submissions need to follow the recommendations in 'Guidelines for Submitting Evidence in FNMP 2014+.pdf' which is attached to this KB article. If no evidence is known to be associated with the applications, please attach a spreadsheet with the following column headers completed for each application: Publisher, Product, Version, and Edition. SKU Library SKUs can come in many different formats, including price lists, purchase orders or simply just SKU values. Customers are encouraged to submit SKUs for processing to Flexera Support. This can be done in one of two ways: 1. Provide the original SKU data source (e.g., price list or purchase order); or 2. Use the attached template to provide SKU details. While we are happy to accept all submissions, even if you only have the SKU number. Please note that the more information you can provide, the quicker we can add it to the library. The following information for SKUs and PURLs are very helpful in speeding up adding to the content libraries: SKU value Publisher and Description License Type e.g. Upgrade, maintenance, full license A template is attached to this article that can be used to provide information on missing SKUs. If you can't provide this information, please send us the SKU anyway but please be aware that these typically take a lot longer to process as extensive research must be carried out and in some cases, we may not find enough information to process some SKUs. Sending as much information as you have on SKUs is preferable. PURL We welcome PURL requests or updates for how we can improve the PURL. A 'PURL Request' template is attached to this article, which can be used to submit PURL use rights questions or adjustments. The following information will be required for a review to occur: Publisher Product Use Rights Question or Adjustment Requested Reference Documentation Once we receive the completed template, we will review the documentation and provide feedback. How is the accuracy of the content libraries maintained? We have a large team of experts in software licensing and application recognition dedicated to maintaining and enhancing our content libraries. We publish updates weekly for the ARL and Monthly updates for the SKU and PURL, averaging tens of thousands of updates each month across the ARL, SKU, and PURL.  Additional Information The attachment 'Submission Template and Guidelines.zip' includes: 1. SKU / PURL submission templates 2. Guidelines for Submitting ARL data 3. How to engage with our Technical support team to request the content library changes ... View more

Summary If you use a proxy server in your environment you would often configure this in Internet Explorer and mgsimportrecognition.exe would use the IE settings however in some cases you might not be able to use the proxy in Internet Explorer e.g. another application won't work through the proxy. Synopsis If you use a proxy server in your environment you would often configure this in Internet Explorer and mgsimportrecognition.exe would use the IE settings however in some cases you might not be able to use the proxy in Internet Explorer e.g. another application won't work through the proxy. Discussion If this is the case you will need to manually enter the proxy server using the -ps switch in mgsimportrecognition e.g. mgsimportrecognition.exe -ps <ProxyServer>:<ProxyPort> -pu <ProxyUsername> -pp <ProxyPassword>   The proxy username and password may not be required, it all depends on your configuration.   Additional Information Once the command has been run once with the -ps -pu -pp switches it should save the configuration so that next time it works by just running the executable. The configuration settings are saved in the following registry key: KEY_LOCAL_MACHINE\SOFTWARE\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion If you are running a 64bit version of windows the registry key is: KEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion If you are unsure about or need to know the proxy username or port previously configured in IE for the content libraries, you can use the following short script below in an administrative PowerShell netsh winhttp show proxy $client = new-object System.Net.WebClient $client.Proxy.GetProxy("https:// ... View more

Summary If you find that it will be necessary to move your license to a new machine, the license must first be returned or deactivated from the previous machine before it can be activated on the new machine. Synopsis AdminStudio and WiseScript Editor node-locked licenses are single-machine, single-user licenses according to the End-User License Agreement (EULA). This means that they can be activated on one machine and accessed by one user. If moving a license to a new machine is required, the license must be returned or deactivated from the machine on which it is currently activated, before attempting to activate the license on a new machine. Please note that there is a return limit for each type of licence: Node Locked Licence If your licence is a node locked licence, then you are allowed to return/deactivate/transfer your licence up to a maximum of four times per year. Concurrent Licence If your licence is a concurrent licence and you would like to return/transfer it from the current licence server to a new/another licence server, then please note that there is a return/transfer limit of 2 returns/transfers per year. Discussion This section included steps for both online and offline activation methods of deactivation. Online Deactivation: 1) Reinstall the software on the previous machine (if it has been uninstalled). 2) From the command-line change directories to the appropriate default path: Version Default Path AdminStudio 8.5 C:\Program Files\Macrovision\AdminStudio\Common AdminStudio 8.6 C:\Program Files\Macrovision\AdminStudio\Common AdminStudio 9 C:\Program Files\AdminStudio\9.0\Common AdminStudio 9.01 C:\Program Files\AdminStudio\9.01\Common AdminStudio 9.5 C:\Program Files\AdminStudio\9.5\Common AdminStudio 10 C:\Program Files\AdminStudio\10.0\Common AdminStudio 11 C:\Program Files\AdminStudio\11.0\Common AdminStudio 11.5 C:\Program Files\AdminStudio\11.5\Common AdminStudio 2013 C:\Program Files\AdminStudio\2013\Common AdminStudio 2014 C:\Program Files\AdminStudio\2014\Common AdminStudio 2015 C:\Program Files\AdminStudio\2015\Common AdminStudio 2016 C:\Program Files\AdminStudio\2016\Common AdminStudio 2018 C:\Program Files\AdminStudio\2018\Common AdminStudio 2019 C:\Program Files\AdminStudio\2019\Common AdminStudio 2020 C:\Program Files\AdminStudio\2020\Common WiseScript Editor C:\Program Files\WiseScript Package Editor\WiseScript Package Editor Note: For 64 bit machines, the default location will be under the (x86) Directory. For example: AdminStudio 11.0 on a 64-bit machine will be located at C:\Program Files (x86)\AdminStudio\11.0\Common WiseScript Editor on a 64-bit machine will be located at C:\Program Files (x86)\WiseScript Package Editor\WiseScript Package Editor 3) Based on the product installed, execute the following Command: For AdminStudio use TPSconfig /return For WiseScript Editor use TSWconfig /return Activation Server URL: activationservice.installshield.com Note: We suggest allowing incoming and outgoing traffic to and from *.flexerasoftware.com and *.installshield.com as well as making sure that ports 80, 443 & 8443 are open. Offline Deactivation: 1) Reinstall the software on the previous machine (if it has been uninstalled) 2) Open up a Command Prompt and CD to the appropriate default path. 3) Execute the following command which will generate a request code: For AdminStudio use TPSconfig /return /no_internet For WiseScript Editor use TSWconfig /return /no_internet 4) For AdminStudio 2014 and later, process the request code at our Product and License Center self-service web page. ... View more

FlexNet Manager Suite is licensed per device. Devices require a license regardless of how they’re imported, whether it’s via FlexNet Manager Suite’s inventory manager, Windows SMS (or SCCM), or any other inventory source. Ignored and discarded devices do not count towards license consumption. Those with administrator roles can view FlexNet Manager Suite license utilization in the system menu . 1. From the system menu select FlexNet Manager Suite License.       2. This view will allow you to see the number of devices and servers that are licensed, active, and the available licenses remaining.       What happens if I exceed the license limit? If you exceed the number of active devices for which FlexNet Manager Suite is licensed, a warning is displayed each time you log in for the next 30 days. If the license breach is not resolved within 30 days, FlexNet Manager Suite will not allow the addition of any new devices, as follows: The inventory importer won’t import new devices. Devices already in FlexNet Manager Suite are updated as normal. The administration console won’t allow manual creation of a new device. Ways to correct license overutilization Contact a Flexera Sales representative to purchase more licenses. Delete unwanted inventory devices and ensure they don’t get imported again. Mark unwanted devices as “ignored” and ensure they don’t get imported again. ... View more

Synopsis Sometimes, the FlexNet Code Insight application can appear to hang or become unresponsive. The initial approach to debugging this situation is usually to generate a thread dump to see where the process currently is in the Java call stack. Discussion Process on Linux Option 1: jstack The jstack utility comes with the JDK and is located in the bin folder inside the JDK home directory. We recommend using the JDK with the same version as the Java process running Tomcat for compatibility. The JDK archive downloads can be found here. Find the Process ID (PID) of the Java process running FNCI using one of the following methods i. jps (this can be run from $JAVA_HOME/bin/ if it is not in your path) This might return a process called "Bootstrap" with an associated process ID. ii. ps aucx | grep java This might return a process called "java" with an associated process ID. iii. ps -ef | grep palamida This is useful if you have multiple Java processes running and need to verify which one is the FNCI process. Check for the path of your FNCI installation in the output. Use jstack to generate the Java stack trace to an outfile. i. Run the command: $JAVA_HOME/bin/jstack , pass it the Java process ID, and direct it to an outfile: Take three of these thread dumps, about a minute or two apart each, so that the outputs can be compared for differences. Alternatively, you can use the kill -3 command with the process ID to send the thread dump to the $FNCI/tomcat/logs/catalina.out file instead. Process on Windows The process on Windows, when running Tomcat interactively (i.e., not as a Windows service) is very similar to the above. Find Tomcat's Java process ID using Task Manager, then from the CMD line, run %JAVA_HOME%\bin\jstack with the process ID as the argument and redirecting to an outfile (same as Linux). However, if running Tomcat on Windows as a service, the process is a bit more involved, so please contact support for the full set of instructions. ... View more

Symptoms Please consider the following scenario: - Select an existing Purchase Order ? or even create a new one - Select an Purchase Order Line that is not linked to an Entitlement ? or create a new PO Line and assign a license directly by the ?Licenses? tab, click ok and close the PO Line - Select ?Edit/View?? for the PO Line and go to the ?Licenses? tab to assign an Entitlement and click ok (applies only for existing PO) - Now, the focus is back on the PO Line Manager with the recently linked PO Line, but the Icon did not change from green to red o I understand that this will remain unchanged unless the ?Apply? button was selected ? from my point of view that?s not an defect - If the customer want?s to review the PO Line by selecting ?Edit/View?? again, the assigned Entitlement is gone. - After confirming all changes by using ?Apply? the linked Entitlement is shown as well as the icon of the PO Line has changed. Resolution This issue has been addressed. ... View more

AMS sending multiple identical emails when user clicks Edit Data button on Data Entry Tab . Steps To Reproduce 1. Logon as a customer company user and create a new application request. 2. After submitting the request an email is then sent to all relevant users notifying them of the new request. 3. Click the Edit Data button, enter a reason for editing the step then click Continue Edit. Resolution Result: Multiple emails are sent from AMS notifying all relevant users of a Change of Data even though the user has not made any changes yet. Expected: No email is expected until the user actually changes something and only one email is necessary showing updates made by the user. ... View more

Summary この記事では、InstallShield の同時接続ライセンスの借用についての解説と、ライセンスの借用を行う前に確認すべき留意事項が挙げられています。 Synopsis この記事では、InstallShield の同時接続ライセンスの借用についての解説と、ライセンスの借用を行う前に確認すべき留意事項が挙げられています。   ナレッジベース記事の英語版は、KB Q213787 を参照してください。 [To see an English version of this KB article, see KB Q213787.]   Discussion 借用とは、FlexNet Licensing Server が配置されているネットワークへの接続を切断して、同時接続ライセンスの使用を可能にできる機能を意味します。       「 InstallShield の同時接続ライセンス用のライセンス サーバーを設定する 」 の解説にある手順を実行すると、ライセンスサーバー マネージャー (lmadmin) によって、チェックアウト可能なライセンスが表示されます。「Activatable」 アイコンをクリックして、利用可能なライセンスの数を確認してください。次の lmadmin のスクリーン ショットでは、InstallShield 2013 Premier Edition (IS2013-PREM-CC) の同時接続ライセンスが 2 つチェックアウト可能になっています。また、現在、借用状態になっている、または解除 (Detached) されているライセンスが 0 であることも分かります。また、このスクリーンショットでは、InstallShield 2013 Standalone Build (IS2013-SAB-CC) が 1 つチェックアウト可能になっていて、借用状態になっているライセンスがないことも分かります。         チェックアウトされたライセンスが、借用中でない場合、[Concurrent] アイコンをクリックした時、ライセンスはチェックアウト状態、もしくは使用中であることが示されます。次のスクリーン ショットでは、InstallShield (IS2.win.prem) が 1 つチェックアウトされていることが示されています。         ライセンスが借用された場合、[Activatable] アイコンをクリックすると、ライセンスが借用中、または切断状態であることが示されます。下のスクリーンショットでは、2 つある InstallShield 2013 Premier (IS2013-PREM-CC) の同時接続ライセンスのうち 1 つが現在、借用中であることが分かります。Standalone Build (IS2013-SAB-CC) の同時接続ライセンスは、1 つだけ借用が可能になっています。       ライセンスの借入方法についてのステップバイ ステップ ガイドについては、「 ライセンス サーバーから InstallShield または InstallShield Collaboration ライセンスを借用する 」をご覧ください。ライセンスを借用する場合、ライセンス の借用ウィザードで、借用期間 (ライセンスを借用する日数) を入力する必要があります。いったん借用期間が過ぎると、借用されたライセンスはクライアント側で無効になり、再度、ライセンス サーバーでチェックアウトが可能な状態になります。       指定可能な日数の値は、1 から 60 です。FlexNet Licensing Server では、借用期間が過ぎるまで、借用されたライセンスをキャンセルできませんので注意してください。借用期間が過ぎる前にライセンスを再度利用可能な状態に戻す必要が発生した場合、クライアントからライセンスを返還します。       借用期間が過ぎる前にライセンスを返還するには、以下の手順に従います:       FlexNet Licensing Server と同じネットワークに接続している状態で、InstallShield を起動します。   [ヘルプ] メニューで、[バージョン情報] をクリックします。[バージョン情報] ダイアログ ボックスが開きます。ダイアログ ボックスで、借用期間の残り日数が表示されます。   [ライセンスの返還] ボタンをクリックします。       返還が成功すると、ライセンスは FlexNet Licensing Server に戻され、再度チェックアウト可能な状態になります。       クライアントから、FlexNet Licensing Serve に接続できなかった場合、エラーダイアログが表示されます。 Additional Information 一旦ライセンスが借用されると、FlexNet Licensing Server では、借用されたライセンスをキャンセルすることができません。つまり、借用期間が終了するまで、FlexNet Licensing Server から強制的にライセンスを返還することは不可能になります。 ライセンスは、ユーザーによって返還されるか、または借用期間が完全に終了するまで使用できません。 借用期間が終了する前にライセンスを返還するには、クライアントが、ライセンスが借用された FlexNet Licensing Server に接続されている必要があります。 クライアントのハードウェアで障害が生じた場合、ライセンスは、借用期間が終了するまでチェックアウトは不可能になります。 限られた数のライセンスを使用しているユーザーは、ライセンスを借用すべきかどうか、および借用期間の長さを決定するとき、これらの条件を念頭に置いておく必要があります。 クライアント側におけるハードウェア障害を懸念するユーザーは、借用されたライセンスにアクセスできなくても問題が発生しないとあらかじめ分かっている日数に、借用期間を制限するようにしてください。 ... View more

Summary This article provides the steps for manually creating a Customer Community User in Salesforce. Synopsis When a contact is added as an entitlement contact, a customer community login is automatically created for the user, but there may be some scenarios in which a contact does not need to be an entitlement contact but still needs access to the Customer Community. This article provides the steps for manually creating a Customer Community User in Salesforce. Discussion In order to create a Customer Community User, a Contact must exist in Salesforce. These steps assume that a Contact already exists. While there are various methods that can be used to find a contact in Salesforce this method searches for the Contact email. Within the Salesforce global search bar (at the top of Salesforce), search for the contact email. If a contact exists with that email, the record will be displayed within the Contacts section of the search results. Click on the Contact Name. On the Contact Detail page, click on the Manage External User button towards the top of the page. Click on the Enable Customer User option. (If you do not see this option, the customer already has a Customer Community User) This will take you to the Customer Community User profile page. By default the users name will be the email address of the contact. (User Name must be unique) Also select Customer Portal User - SLO in the Profile field. Click Save. The customer will be sent an email automatically with the username and a temporary password for the account. The customer must change the password before logging in. ... View more

This article provides information regarding how to resolve the activation error: "The quantity specified exceeds maximum quantity allowed (0)". Symptoms Your attempt to activate your license is denied, and the following message is displayed: The quantity specified exceeds maximum quantity allowed (0). Cause This activation error indicates that the license you are attempting to activate has already been activated on another machine. Resolution To resolve this error, it will be necessary to return the license to the account on the activation server. This process is sometimes referred to as a deactivation. You can return the license by uninstalling the application or by clicking the Return License button (available in AdminStudio 11.x and up). The Return License button is located in the About dialog box (which is displayed when you click About AdminStudio on the Help menu). Starting with AdminStudio 8.5, you can also return the license from the command line, by executing the return command as follows. 1. From the command-line change directories to the appropriate default path: AdminStudio Default Path AdminStudio versions 8.5 and 8.6 C:\Program Files\Macrovision\AdminStudio\Common AdminStudio versions 9.x and up C:\Program Files\AdminStudio\<VERSION NUMBER>\Common Note: For 64 bit machines, the default location will be located in the Program Files (x86) Directory. 2. Execute the following command: AdminStudio: TPSconfig /return ... View more

Summary This service pack fixes various issues which have been identified with the FlexNet Manager Platform and Flexera Inventory Manager 9.2 releases. For full details of the issues resolved please see the attached release notes documents. Symptoms This service pack fixes various issues which have been identified with the FlexNet Manager Platform 9.2 and Flexera Inventory Manager 9.2 releases. This service pack is only applicable to FlexNet Manager Platform and Flexera Inventory Manager version 9.2. This service pack supersedes the hotfixes supplied in knowledge base articles Q210771, Q211314 and Q211574. Resolution To apply the service pack, follow the steps outlined in the attached release notes documents (within the attached zip file). Click to Download the Service Pack For full details of the issues resolved please see the attached release notes documents. Additional Information If you ran the migration scripts to upgrade FNMP after 4th June 2013 then the SQL scripts for this patch will already have been installed on your database and you will only need to run the executables in the attachment below. If you upgraded before this date you will need to run both SQL scripts and executables from the attachment below. ... View more

Summary A python project to gather component/license information from various package managers (e.g., npm, rubygems, rpms, etc.) and parse into groups that are importable via the import workspace XML data script. Synopsis A python project to gather component/license information from various package managers (e.g., npm, rubygems, rpms, etc.) and parse into groups that are importable via the import workspace XML data script for FlexNet Code Insight. Download: Contact Technical Support Password: 000022428 Switch to checking for "repository" field for npm urls first (for Github component matching). Fix bug for .gem files. Fix typo in gemsource documentation. Usage ./GroupBuilder.py [options] Run with -h for options. Discussion Input For Node Modules: A text file with a list of files paths containing Node Modules (run with -f <file> ). Or a text file with a list of Node Modules (run with -p <file> ). For Ruby Gems: A text file with a list of files paths containing .GEM files (run with -f <file> -t gems ). Or a text file (such as a gemfile) with a list of gems (run with -p <file> -t gems ). For Ruby Gems source code, use like npm with a text file of file paths (run with -f <file> -t gemsource ) For RPMs: A text file with a list of file paths containing RPMs (run with -f <file> -t rpms ). For Composer (PHP) packages: A text file with a list of files paths containing composer.json files (run with -f <file> -t php ). A composer.lock file with package JSON data. (run with -f <composer.lock> -t php ). For BitBake (bb) files: A text file with a list of files paths containing .bb files (run with -f <file> -t bitbake ). For CSV file: A csv (comma-separated) file with a list of groups having data in the following order: Group/Package Type, Name, Version, License, Description, URL, filepath, Component ID, and ComponentVersion ID Requirements For Node Modules: An installation of npm from NodeJS (http://nodejs.org/). Or local access to the package.json files. For Ruby Gems: Internet access. The Requests python package. For RPMs: The rpm command (via Cygwin or your Linux package manager) And local access to the rpm files. For Composer (PHP) packages: A composer.lock file with package information in JSON format. Or local access to composer.json files. For BitBake: Local access to .bb files. For CSV: All groups must have a name, at least. For associating groups to components, either the components.txt file (which contains component information for the core database) or a JSON with credentials to use a Palamida MySQL database. Using a MySQL connection will require the mysql.connector package (https://dev.mysql.com/downloads/connector/python/2.1.html). Please take care when using database connections. Always make a verified backup before making direct database connections. This script only queries and does not write to the Palamida database. For all: Python 2.7.x. The lxml package is necessary to pretty-print the XML output. Output An XML file that's importable by the Palamida import/export script For versions of the import/export script 3.2 and AFTER: scriptRunner.bat <PATH_TO>importWorkspaceData.groovy --server <your core server url> --scan_server <your scan server url> --input groups.xml --workspace foo-workspace For versions of the import/export script BEFORE 3.2: scriptRunner.bat <PATH_TO>importWorkspaceData.groovy -input workspaceData.xml -workspace foo-workspace -check_md5_hash If you give the script file paths, then it will try to associate the resulting groups to files and build that into the XML file. If you do not have file paths, you have the option to associate all of the resulting groups to a single file, otherwise when you import the groups they will not be attached to any files. Caveats Please bear in mind the following caveats: The information is not necessarily perfect. The developer might have been lazy or stupid and incorrectly filled out the metadata in the file (or wherever). We recommend doing a quick check against the actual licenses. The information is not necessarily complete. Some node modules will have ?Unknown License? given because the information was not available in the metadata. These projects likely have licenses in their source repositories (Github, etc) or other places. I recommend looking at each of these manually. The information does not give you P1 bundle issues. Each of these files must be checked for P1 issues as usual before being marked as reviewed (P1 search terms and P1 license matches). A major benefit of these scripts is that we have more time to be thorough looking for P1 stuff. This is an alpha release that is completely independent of the main Palamida product and is provided 'as is' as an add-on for convenience. It likely contains bugs and likely won't handle every special case. We welcome feedback and suggestions (fscott@palamida.com). If you see any P6 groups with obvious know licenses, please let us know what the license text was so I can add it. License priorities can be adjusted in the Group.py file. Additional Information The current version is 1.9 (5-17-2016) Switch to checking for "repository" field for npm urls first (for Github component matching) Fix bug for .gem files. Fix typo in gemsource documentation. Version 1.8 (5-13-2016) Better component matching. Attempts to find Github component first given a Github URL before doing a broader URL search. (Thanks Ed!) Groups will still be created when you don't have access to the npm registry. Clearer logging when checking npm registry. Version 1.7 (4-6-2016) Now compatible with import/export scripts v3.2 (for Palamida 6.8). NOTE CHANGE IN OUTPUT ABOVE. Support for gem source writeups. Some day will read gemspecs directly. Version 1.6 (3-6-2016) New components based on latest electronic update. CID and CVID for csv groupbuilding. Gem source code is now supported. Fixed typo in Ruby Gem group write-up (Thanks Ed!) Group.py will now try to associate a group to a component by an exact name match as a last gasp attempt. Warning that this may lead to more false postives. Feedback is welcome here. RPM bug fixes and improvements. Version 1.5 (1-4-2016) Various bug fixes and improvements. Version 1.4 (12-21-2015). The lxml is now an optional dependency. It's primarily used to pretty-print XML. Version 1.3 (12-06-2015). Faster node module processing and better console info. Option to use connection to Palamida MySQL database. Selects available version ID as well as component, if available (requires DB connection) Now supports BitBake and CSV files. Future Work More documentation Options for formatting output. Handling more special cases. Copyright Copyright (C) 2015-2016 Palamida Inc. All rights reserved. This software is the confidential and proprietary information of Palamida Inc. and shall not be used, disclosed or reproduced, in whole or in part, for any purpose, without the prior written consent of Palamida Inc. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ... View more

Summary This article provides the requirements and instructions to upgrade FlexNet Code Insight (Palamida) to 6.10.3. Synopsis This guide is for upgrading the FlexNet Code Insight (Palamida) application. For Compliance Library upgrades, Compliance Library Upgrade Guide. This guide is for upgrading to FlexNet Code Insight (Palamida) 6.11.3 only. For new installations, see the Install SysAdmin Guide include with the product. IMPORTANT: Do NOT perform an upgrade on a production server unless you are an experienced FlexNet Code Insight administrator. It is highly recommended that you contact Flexera Software Support to assist you with the upgrade. It is your responsibility to ensure the integrity and reliability of backups. Always test and verify backups, and maintain redundant offsite copies. Flexera Software is not responsible for data loss due to corrupt or missing backups. Discussion Requirements You must have one of these previous versions to use this guide: 6.11.1, 6.11.2, 6.10.0, 6.8.1, 6.8.0, 6.6.2, 6.6.1, 6.1.4, 6.1.3, 6.1.2, 6.1.1, 6.1.0, 6.0.5, 6.0.2, 5.2.4, 5.2.2 You will need the following to perform the upgrade: The plain text database password for the user and database defined in core.db.properties. You will need to run an Electronic Update as the final step in the upgrade. The core server must have outgoing Internet access on port 22, otherwise you will need to run the Electronic Update manually. You will need enough free disk space to perform backups. Check the size of your workspaces directory, which may be large. The FlexNet Code Insight 6.11.3 distribution zip file. Contact your Flexera representative if you do not have a copy. The migrationImport.groovy script, located in /scriptRunner/scripts/ of your 6.11.3 application directory. This script copies the properties and configurations from your existing application directory (OLD_DIR) to the new application directory (NEW_DIR) and notifies you of any additional steps needed The migrate.sh / migrate.bat script, located in /scriptRunner/bin/ of your 6.11.3 application directory. This script migrates your existing database schema from the existing version of FNCI to the new version. If you have any custom core reports, you will need to re-run the custom SQL scripts that you initially used to install them. Prepare Environment NOTE: The commands in this guide are written for Linux. Windows users may choose to perform the steps with a mouse. Be sure to replace the sample values below with those of your installation. This guide makes reference to the following variables. You can set these variables on the server in order to paste the commands in this guide. # Current installed version OLD_VER="6.11.1" # Current app directory. OLD_DIR=" /opt/CodeInsight/6.11.1 " # New app directory, which will be created. NEW_DIR="/opt/ CodeInsight /6.10.3" # Base directory for backups (a 6.11.3 subdirectory will be created) BACK_DIR="/opt/ CodeInsight /backup" # Core server only - MySQL Database info. DB_HOST="localhost" DB_NAME=" CodeInsight " DB_USER="myUser" DB_PASS="myDbPassword" # Scan servers only - Workspaces directory. WS_DIR="/opt/ CodeInsight /workspaces" You can paste the above into a file on the server (for example /tmp/code_insight_env) and edit the values. Then you can run source /tmp/code_insight_env to set the variables used in this guide. After the upgrade is complete, be sure to rm /tmp/code_insight_env , if it contains the database password. Upgrade FlexNet Code Insight Shutdown FlexNet Code Insight. For multi-server installs, shutdown all servers. cd $OLD_DIR/tomcat/bin ./shutdown.sh Backup the database. This step applies to CORE only. NOTE: These commands are for MySQL. If you are using Oracle, obtain a fresh backup from your DBA before proceeding. Make sure your DBA is available to restore the backup promptly, in case it is needed. mkdir -p $BACK_DIR/6.11.2 cd $BACK_DIR/6.11.2 mysqldump -h $DB_HOST -u "$DB_USER" --password="$DB_PASS" -r migration_db.sql $DB_NAME Backup workspaces directory. This step applies to all SCAN servers. NOTE: This may take a long time depending on the size of your workspaces directory. cd $WS_DIR tar cf $BACK_DIR/6.10.3/migration_ws.tar . Backup the installation directory. cd $OLD_DIR # clear the tomcat temp files rm -r tomcat/temp/* tar czf $BACK_DIR/6.10.3/migration_app.tgz . Extract the 6.11.3 distribution zip file (CodeInsight-6.11.3.zip) and move it to the new directory. unzip -q CodeInsight-6.11.3.zip -d /tmp mv /tmp/CodeInsight-6.11.3.zip $NEW_DIR Place the migration import script in the new directory, and run the script. cd $NEW_DIR/scriptRunner/bin ./scriptRunner.sh -n ../scripts/migrationImport.groovy $OLD_DIR Check the TODO log for any additional steps needed. Complete any necessary steps before continuing. cat $NEW_DIR/scriptRunner/log/migration.TODO.log Run the database schema migration. This step applies to CORE only. cd $NEW_DIR/scriptRunner/bin ./migrate.sh $OLD_VER If database errors are seen, please re-run the database schema migration after resolving the error. Run the new reports.sql to install new reports. Use the appropriate file according to your database vendor (MySQL in this example). This step applies to CORE only. Note: The reports.sql file will overwrite any modifications to the report tables in the database. If you have custom reports, you will need to re-run the custom SQL to install them after you have run the new reports.sql file. Make sure you have your custom SQL scripts before you run this. mysql -h $DB_HOST -u "$DB_USER" --password="$DB_PASS" -D $DB_NAME \ -e "source $NEW_DIR/dbScripts/mysql/reports.sql" NOTE: FlexNet Code Insight 6.11.3 has features which requires a new Data Services Enabled key. You can continue to start and use the application with your existing key, but there will be errors seen with the features that require this key. Start the new FlexNet Code Insight application. For multi-server installs, do this after you have completed the previous steps on all servers. cd $NEW_DIR/tomcat/bin ./startup.sh && tail -f ../logs/catalina.out Check the log for any errors, and resolve them before continuing. Log into the WebUI and run the Electronic Update. This step applies to CORE only. NOTE: DO NOT SKIP THIS STEP. In most cases, the electronic update will be scheduled automatically. Check the Scheduler tab in the WebUI. If the update is not running, you can trigger it through Administration > Updates, and clicking Check for Electronic Update. If your installation does not have outgoing Internet access on port 22, you will need to run the update manually. If you face certificate errors on startup of the scan server or if you are unable to see your scan server from the application UI, then you will need to import the certificate being served by Tomcat on the scan server into the JDK of the core server. Verify Upgrade Log into the WebUI and go to Help > About to verify the version. Create a test project and workspace. Ensure that the Detector client launches for the workspace. Close Detector and schedule a scan. Revert to Previous Version Ensure the FlexNet Code Insight server is stopped. For multi-server installs, ensure all servers are stopped. Restore the database. This step applies to CORE only. NOTE: These commands are for MySQL. If you are using Oracle, have your DBA restore the backup. cd $BACK_DIR/6.10.0 mysql -h "$DB_HOST" -u "$DB_USER" --password="$DB_PASS" -D "$DB_NAME" < db_migration.sql Restore workspaces backup. This step applies to all SCAN servers. NOTE: If you did not open, create, or scan any workspaces while the new version was running, you can skip this step. cd $WS_DIR tar xf $BACK_DIR/6.11.2/ws_migration.tar Start the previous installation. For multi-server installs, do this after you have completed the previous steps on all servers. cd $OLD_DIR/tomcat/bin ./startup.sh && tail -f ../logs/catalina.out ... View more