This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
acurry
Flexera Alumni
- Revenera Community
- :
- About acurry
Sep 18, 2020
01:24 PM
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
- Tags:
- Q111006
Aug 17, 2020
05:39 PM
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
Labels:
Feb 06, 2019
09:23 PM
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
- Tags:
- japanese
Dec 21, 2018
05:45 PM
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
Labels:
Dec 21, 2018
05:38 PM
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
Labels:
Dec 20, 2018
07:01 PM
Summary This script will validate the MD5 checksums of the Compliance Library files. Synopsis This script will validate the MD5 checksums of the Compliance Library files. Discussion Compliance Library Upgrade Guide for instructions on installing a new Compliance Library.
Download validateSigMD5s.sh for CL 2.34 and later
Download validateSigMD5s-old.sh for CL 2.33 and earlier
Usage
validateSigMD5s.sh /path/to/CL/x.xx
... View more
Labels:
Nov 15, 2018
06:27 PM
1 Kudo
Summary What functionality will remain the same and will change in the FlexNet Operations Cloud ALM Reporter? Question What functionality will remain the same and will change in the FlexNet Operations Cloud ALM Reporter? Answer Many of the core capabilities of the ALM reporter will remain the same:
Data refresh schedule Configuration user flow to create and schedule reports Universes for Product Set-up and Download History will remain the same
There are changes to treatment of data results in 2018 R1:
Previous Data Field New Data Field/Treatment Description "Organization" Field renamed to "Account" Field name change introduced in 2017 R4 with full changes to UI and web services in 2018 R1 "Created Date/Time" Rounded "Created Date/Time" Field results round down to the hour Time zone presented in Pacific Time zone presents in GMT Affects New Universes: Entitlements + Fulfillments + Account/Users Legacy universes will remain using Pacific Time such as Download History and Product Set-Up Some custom attributes were searchable All custom attributes are searchable During the initial creation for the custom attribute, need to set "synch to Reporter" in the custom attribute set up in order to include it in searches Wildcard was * asterisk Wildcard is % percentage symbol - New Universes introduced in 2018 R1 - Legacy universes will continue to use *asterisk for wildcard searches such as Download History and Product Setup Custom attributes not available in all data universes Default 30 custom attributes included per level If a custom attribute field is not needed for reporting, then choose only the fields necessary. Should a field be needed at later date, it will require Flexera assistance, submit a Support Case
... View more
Nov 15, 2018
06:26 PM
Summary Concurrent License Server Error EXITING DUE TO SIGNAL 37 Exit reason 5: Vendor daemon can't talk to lmgrd. Symptoms EXITING DUE TO SIGNAL 37 Exit reason 5: Vendor daemon can't talk to lmgrd Cause This error is known to occur on Linux due to a permissions issue if lmadmin was installed as root. Resolution Move the installation to a non-root user path and log in as a non-root user Restart the license server
... View more
Labels:
Nov 15, 2018
06:26 PM
Summary Concurrent License Server Error EXITING DUE TO SIGNAL 37 Exit reason 5: Vendor daemon can't talk to lmgrd. Symptoms EXITING DUE TO SIGNAL 37 Exit reason 5: Vendor daemon can't talk to lmgrd Cause This error is known to occur on Linux due to a permissions issue if lmadmin was installed as root. Resolution Move the installation to a non-root user path and log in as a non-root user Restart the license server
... View more
Labels:
Nov 15, 2018
05:12 PM
Summary This articles discusses how to configure claimed copyrights. Synopsis Claimed copyright settings can be used to have Palamida designate a selection of copyrights to be ignored when the software scans for third-party indicators. Only "unparseable" copyrights can be ignored. An unparseable copyright is one that is not strong enough to match a pattern but still appears to be copyright statement. Files containing copyrights put into the "claimed bucket" will not be flagged for third-party indicators if the customer's claimed copyright is the only indicator.This behavior ensures that real copyright matches are still detected. Ignored copyrights are not accessible in the scan results. (For more information on how to control the sensitivity of copyright detection, please refer to the section, "Tuning Copyright Detection" in the Enterprise Installation and System Administration Guide.) Discussion Edit the file $palamida/config/scanEngine/claimedCopyrights.txt
##############################################################################
# This file may be used to force detected copyrights into the -claimed- bucket.
# The purpose of this is to move all copyrights that belong to the user into a
# separate bucket (-claimed-) so that they do not cause the scanned file to be
# flagged as having third-party indicators if the only evidence is the customer's
# copyright.
##############################################################################
##############################################################################
# The case-sensitive strings or regular expression patterns below will cause a
# detected copyright to be moved into the -claimed- bucket.
##############################################################################
#[P|p]alamida
Defining copyright patterns for which to take ownership and move to the -claimed- bucket:
Do not use commas (,) while defining copyright, date or owner patterns. Since commas are used as delimiters, they will end up tokenizing your patterns into multiple values. For example: Palamida, Inc. should be defined as Palamida Inc. (Note that there is no comma in the owner pattern.) Do not use any of the following reserved characters: \n \r | # ! % : ; , / * " space. If you use these reserved characters, they will be replaced by a whitespace (' ') character. If Java special characters are part of the defined copyright pattern, ensure that double slashes are used to escape both the properties file parsing as well as the Java interpretation. An example of this is Copyright 2008 would be defined as Copyright \[C\] 2008.
... View more
Labels:
Nov 15, 2018
05:11 PM
Summary This article discusses how to use the new code search feature in Detector 6.8. Synopsis For the new code search feature, scanned code is indexed so that a search may be performed at anytime. This eliminates the need for a text/grepping tool outside of the product. This feature can be combined with Palamida Groups, tags and custom filters. The tree is filtered to files containing results such that these files can be Marked as Reviewed, Added to Group or tagged. Discussion If you click the search button, the following options are offered:
Search for File Name
You can now search for a file name across the code base using this new feature menu and seeing the results as a new highlighting feature in the Source matches:
Search for Selected Text
You can also search for any selected string or text in files across the scanned codebase. You can find this in a new menu when you select and right-click on text in the Partial Matches Pane.
... View more
Labels:
Nov 15, 2018
05:11 PM
Summary You are unable to launch Tomcat or Detector and receive an error in $palamida/tomcat/logs/catalina.out . Symptoms You are unable to launch Tomcat or Detector and receive the following or similar errors in $palamida/tomcat/logs/catalina.out:
WARNING: Due to a permissions issue accessing the log files, the status of the database has been changed to read only.
java.io.FileNotFoundException: /home/palamida/workspaces/ePortal/workspace/log/log3.dat (Permission denied) Cause This and similar permissions errors can be caused by launching Tomcat with root permissions. The result of this is that any data created during that Tomcat session (such as scanning a workspace) will be written with root ownership; subsequent attempts to access data created during these sessions will thus be denied for having insufficient privileges.
NOTE: Tomcat should never be run with root user privileges Resolution There are two main approaches to this issue:
1)
Re-launch Tomcat with your desired user. Create a new Workspace. Re-scan the materials from the inaccessible workspace in your new workspace.
2)
Determine the name of your Palamida database.
You can find the name of your database on the db.url line of $palamida/config/core/core.db.properties. For example:
db.url=jdbc:mysql://<HOST>:<PORT>/<YOUR_DATABASE_NAME>?autoReconnect=true
Within your workspaces/ directory, run the ls -al command to list the workspace directories along with their owner username and group.
For any workspaces with root ownership, run the following command, using the username you intend to use to launch the Palamida server, for example:
chown -R palamida:palamida /opt/palamida/workspaces
... View more
Labels:
Nov 15, 2018
05:11 PM
Summary This article provides a resolution for the message: You are not authorized to access workspaces for the current project. Symptoms When launching Detector, you see this message:
NOTE: If you are on Palamida 6.1.0 or earlier, you must have JRE 7u40 or earlier on the client machine to launch Detector.
Resolution Log out of the WebUI, log in again, and relaunch Detector from a new JNLP file.
Clear temporary files from Java control panel:
Clear all Palamida code-signing certificates from the Java Control Panel. Clear all browser cache and restart your browser.
... View more
Labels:
Nov 15, 2018
05:11 PM
Synopsis Almost always, the first step in error resolution is log analysis. This document shows how to fully shut down the Palamida Tomcat servers, kill any hanging Java processes, and generate a new set of logs without historical data. This helps the Support team isolate an error as it occurs. Discussion
Please STOP all Palamida by running $palamida/tomcat/bin/shutdown.sh.
After shutdown of the Tomcat servers, ensure that there are no hanging Java processes.
You can ensure there are no Java processes by the following commands:
i. jps
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. Kill the Java process if necessary by the kill -9 command:
Next, delete all the logs in $palamida/logs and $palamida/tomcat/logs
Start the Palamida Tomcat servers ? this will generate a set of new logs to help isolate the error
Attempt the action that caused the error before.
If you experience the error again, please zip and email the new logs with the error.
Please include all logs in $palamida/logs and $palamida/tomcat/logs Please also include the following configuration files:
$palamida/config/core/core.properties $palamida/config/core/core.db.properties $palamida/config/scanEngine/scan.properties $palamida/config/scanEngine/scanEngine.properties $palamida/tomcat/bin/catalina.sh (For Windows, use catalina.bat instead) NOTE: Please rename this file, as e-mail clients such as Outlook will block it to be quarantined.) $palamida/tomcat/conf/server.xml
Additional Information If you are experiencing Detector related issues, we may suggest for you to send us the logs. Please refer to Enable Java Console Logging for enabling Java Console Logs.
... View more
Labels:
Nov 15, 2018
05:11 PM
Summary On opening Detector you receive the error: Unable to launch the application. Symptoms On opening Detector you receive the error:
And the following error:
JAR resources in JNLP file are not signed by the same certifica
Cause There are cached expired certificates or JAR files from an earlier version. Resolution Delete all Palamida code-signing certificates from the Java Control Panel.? Clear your Java cache from the Java Control Panel:
Clear all browser cache and restart your browser.
... View more
Labels:
Latest posts by acurry
Subject | Views | Posted |
---|---|---|
43845 | Sep 18, 2020 01:24 PM | |
712 | Aug 17, 2020 05:39 PM | |
1937 | Feb 06, 2019 09:23 PM | |
906 | Dec 21, 2018 05:45 PM | |
1167 | Dec 21, 2018 05:38 PM | |
618 | Dec 20, 2018 07:01 PM | |
1030 | Nov 15, 2018 06:27 PM | |
2179 | Nov 15, 2018 06:26 PM | |
1375 | Nov 15, 2018 06:26 PM | |
1350 | Nov 15, 2018 05:12 PM |
Activity Feed
- Posted How Do I Install or Uninstall the Software Manager? on InstallShield Knowledge Base. Sep 18, 2020 01:24 PM
- Posted Generating FlexNet Code Insight Thread Dumps for Support on Code Insight Knowledge Base. Aug 17, 2020 05:39 PM
- Posted InstallShield 同時接続ライセンスの借用 on InstallShield Knowledge Base. Feb 06, 2019 09:23 PM
- Posted FlexNet Code Insight Group Builder Script - Add-On on Code Insight Knowledge Base. Dec 21, 2018 05:45 PM
- Posted FlexNet Code Insight (Palamida) 6.11.3 Upgrade Guide on Code Insight Knowledge Base. Dec 21, 2018 05:38 PM
- Posted Validate CL Signatures Script on Code Insight Knowledge Base. Dec 20, 2018 07:01 PM
- Posted What functionality will remain the same and will change in the FlexNet Operations Cloud ALM Reporter? on FlexNet Operations Knowledge Base. Nov 15, 2018 06:27 PM
- Posted Concurrent License Server Error EXITING DUE TO SIGNAL 37 Exit reason 5: Vendor daemon can't talk to lmgrd on InstallShield Knowledge Base. Nov 15, 2018 06:26 PM
- Posted Concurrent License Server Error EXITING DUE TO SIGNAL 37 Exit reason 5: Vendor daemon can't talk to lmgrd on InstallAnywhere Knowledge Base. Nov 15, 2018 06:26 PM
- Posted Configuring Claimed Copyrights on Code Insight Knowledge Base. Nov 15, 2018 05:12 PM
- Posted Detector Code Search in 6.8 on Code Insight Knowledge Base. Nov 15, 2018 05:11 PM
- Posted Permission Denied Exception on Code Insight Knowledge Base. Nov 15, 2018 05:11 PM
- Posted You are not authorized to access workspaces for the current project on Code Insight Knowledge Base. Nov 15, 2018 05:11 PM
- Posted Collecting Logs for Support on Code Insight Knowledge Base. Nov 15, 2018 05:11 PM
- Posted Unable to launch the application: JAR resources in JNLP file are not signed by the same certificate on Code Insight Knowledge Base. Nov 15, 2018 05:11 PM
- Posted Enable Java Console Logging on Code Insight Knowledge Base. Nov 15, 2018 05:11 PM
- Posted What does the Match Slider in Workspace Settings do? on Code Insight Knowledge Base. Nov 15, 2018 05:10 PM
- Posted An SQL data change is not permitted for a read-only connection, user, or database on Code Insight Knowledge Base. Nov 15, 2018 05:10 PM
- Posted Unable to start the License deamon with error "/lib64/libc.so.6: version `GLIBC_2.14' not found " Due to Older Version Installed on FlexNet Publisher Knowledge Base. Nov 13, 2018 10:34 PM
- Posted "This copy of InstallAnywhere could not be registered using the node locked licensing file specified." Error Occurs Due to the license.lic file Not Being Found in the Expected Location on InstallAnywhere Knowledge Base. Nov 12, 2018 07:15 PM
Contact Me
Online Status |
Offline
|
Date Last Visited |
Aug 15, 2019
02:38 PM
|