Summary How to move database location Synopsis 1. We are planning to replace Linux servers for our existing Windows servers. Can we still be able to continue use SQL database? 2. We need to move our SQL to a new server, how to configure both admin and reporting to point to database that will reside on new server? Discussion 1. We are planning to replace Linux servers for our existing Windows servers. Can we still be able to continue use SQL database? Ans: Yes you can use the same SQL database, as long as the only on instance is running. That is either Linux server instance must be running or Windows server instance must be running. 2. We need to move our SQL to a new server, how to configure both admin and reporting to point to database that will reside on new server? Ans: You can run flexnet site for both admin and reporting module click show advance setting in the configuration then Navigate to page 5 and point the installation to appropriate database server? ... View more

Summary How to install FlexNet agents 5 and above with GUI on Non-windows machine Discussion To run a GUI install please run the following command: ./.bin -i GUI Please replace with the name of the Linux installer. Please, remember to forward DISPLAY for a headless target. ... View more

Summary Error during upgradedb for 15.8 reporting server Symptoms While running the upgradedb for reporting server following error is observed in the upgradedb.log 2018-11-28 15:54:22,524 Starting actions going from remotereporting version 15.7.0.10 to 15.8.0 2018-11-28 15:54:22,529 UPDATE PLT_MODULE SET VERSION = '15.8.0' WHERE NAME = 'remotereporting' executed successfully. 2018-11-28 15:54:22,540 ERROR: Error execution: DELETE FROM PLT_MODULE WHERE NAME = 'products' 2018-11-28 15:54:22,540 ERROR: ORA-02292: integrity constraint (FLEXNETREPORTING.FK296D3A9649FE8C43) violated - child record found The update script exited with code 0. Cause The issue here is that for older version of FNMEA we had additional products module which is not required for newer release of FNMEA that is why the upgrade script tries to remove the pertaining row for that module in the table PLT_MODULE, however the table schema constraints for table PLT_MODULE was not updated appropriately so that this row could be deleted. Therefore, you see an error in the upgradedb.log. However, this error has no effect on functionality. Resolution The is an cosmetic issue which does not affect the functionality of the product. This issue was submitted to, reviewed by, and accepted by our Engineering Team as a valid bug for tracking under the Work Order with Issue #IOJ-1901706. ... View more

Summary This article discusses the issue with running Project Automation Java class with 64-bit JDK which results in the project failing to be saved by a node-locked licensed copy of InstallAnywhere. Symptoms Running the Project Automation Java class with a 64-bit JDK results in the project failing to be saved by a node-locked licensed copy of InstallAnywhere. Here is the error message that's generated: Trying to checkout IAEB version=17.0 Library for Native Hostid Couldn't Be Loaded (-521,7024) Trying to checkout IACB version=17.0 Library for Native Hostid Couldn't Be Loaded (-521,7024) Trying to checkout IAEE version=17.0 Library for Native Hostid Couldn't Be Loaded (-521,7024) Trying to checkout IACE version=17.0 Library for Native Hostid Couldn't Be Loaded (-521,7024) Trying to checkout IAEJ version=17.0 Library for Native Hostid Couldn't Be Loaded (-521,7024) Trying to checkout IACJ version=17.0 Library for Native Hostid Couldn't Be Loaded (-521,7024) Trying to checkout IAS version=17.0 Library for Native Hostid Couldn't Be Loaded (-521,7024) This copy of InstallAnywhere could not be registered using the node locked licensing file specified.Please check if the license file specified at (<path_to_lic_file>) is a valid license file for this node.If this was a subscription license, please verify if your license has expired. Cause InstallAnywhere is shipped as a 32-bit application, and the libraries which are used are only compatible with a 32-bit JVM. Steps To Reproduce 1. Create a project. 2. Implement a Project Automation Java class. For example: package com.zerog.ia.projectautomation; import com.zerog.ia.auto.project.Project; import com.zerog.ia.auto.project.ProjectAutomation; public class TestInstallAnywhereAutomation { public static void main(String[] args) { try { System.out.println("Test start..."); ProjectAutomation.setIALocation("C:\\Program Files (x86)\\InstallAnywhere 2015 Premier"); System.out.println("IALocation set"); Project myProject = ProjectAutomation.loadProject("C:\\Users\\UserName\\Desktop\\ProjectName\\ProjectName.iap_xml"); System.out.println("Project loaded"); System.out.println("java.library.path is : " + System.getProperty("java.library.path", "")); System.out.println("Test IA auto api"); System.out.println("IA project file to modify is " + "C:\\Users\\UserName\\Desktop\\ProjectName\\ProjectName.iap_xml"); ProjectAutomation.saveProject(myProject); System.out.println("Project saved"); System.out.println("Test done..."); } catch (Exception e) { e.printStackTrace(); System.exit(-1); } System.exit(0); } } 3. Compile the Java class. 4. Export the Java class in a JAR file. 5. Run the Project Automation Java class with a 64-bit JDK. The Project Automation Java class successfully loads the project but fails to save the project. ? Resolution Use a 32-bit JDK when running the Project Automation Java class. Additional Information An enhancement request for 64-bit support has been submitted to our Engineering team as Issue# IOJ-1748232. Our Engineering team is investigating this issue, but at this moment, there is no estimated time frame for when this feature will be implemented. ... View more

Summary This article discuss about the build parameters for the InstallAnywhere Ant task. Synopsis This article discuss about the build parameters for the InstallAnywhere Ant task. Discussion InstallAnywhere includes an Ant task to build installers from Ant. The InstallAnywhere Ant task (iaant.jar) is located in your InstallAnywhere application folder: IA_HOME\resource\build\iaant.jar where IA_HOME is the InstallAnywhere installation directory. Tip: To integrate the InstallAnywhere Ant task in an Ant project, set the classpath of the InstallAnywhere Ant task to the location of iaant.jar. Note: The use of iaant.jar requires Java 1.4 or later. The following Ant task parameters are available: Build Parameters Platform Options Build Options Installer Options However, this article provides information only on the Build Parameters. For more information on the other parameters please refer the additional information section. Build Parameters Use the following parameters to control the build process for the InstallAnywhere Ant task. Attribute Description IAProjectFile The location of the InstallAnywhere project that you want to build. This is a required parameter. IALocation The location where InstallAnywhere is installed. This is an optional parameter. Note ? If IALocation is not specified, the task searches for a copy of InstallAnywhere to run against. If InstallAnywhere is not installed in one of the default locations, the task checks the InstallAnywhere product registry for a valid location. i5OSLogin The host name, user name and password of an iSeries machine in the following format: hostname_or_ip/userName/password For example: <buildinstaller IAProjectFile="Project_File" IALocation="IA_HOME" i5OSLogin="hostname_or_ip/userName/password"> After the project successfully builds, an asterisk-masked i5OSLogin parameter (password portion) prints to the console. This is an optional parameter. propertiesfile The location of a BuildProperties.xml file. If this parameter is used, all other attributes are ignored. This is an optional parameter failOnError Stop the build process if the command exits with a return code other than 0. Defaults to false. This is an optional parameter. Additional Information To get more information on Platform Options, Build Options and Installer Options, click here. ... View more

Summary This article discusses why IAClasses.zip should not to be in the dependencies of a project. Synopsis This article discusses why IAClasses.zip should not to be in the dependencies of a project. Discussion All of the elements which are present in IAClasses.zip are already added to the classpath by InstallAnywhere and are not required to be added explicitly by the installation author while designing the project file. The following reasons further illustrate why this should not be done: Each version of InstallAnywhere has its own mapping of classes and resources in IAClasses.zip. Therefore, if IAClasses.zip is explicitly added for a project in InstallAnywhere 2015 and then the project is upgraded to InstallAnywhere 2017, this will cause build-time errors. Adding IAClasses.zip to the dependencies would unnecessarily increase the size of the installer. This might result in more overhead time for the extraction process. ... View more

Summary This article discusses about using the Project Automation API InstallDirectory Synopsis This article discusses using the Project Automation API InstallDirectory Java class. Discussion The InstallDirectory Java class adds the given directory to the installer project to be later installed by the installer. It is similar to adding a directory using the Add File... or adding a Create Folder action button via InstallAnywhere IDE. It also allows the definition of some file attributes, like UNIX permissions and destination name. Constructor for Install Directory public InstallDirectory() Method Summary for InstallDirectory Modifier and Type Method and Description Vector<OSHostable> getChildren() The children files to be installed. boolean getRemoveRecursively() Whether to recursively delete all contents of this folder during uninstall. void setRemoveRecursively(boolean removeRecursively) Whether to recursively delete all contents of this folder during uninstall. Methods inherited from class com.zerog.ia.auto.project.actions.FileAction getDestinationName, getFileOverwriteBehavior, getOverrideUnixPermissions, getShouldUninstall, getSourceFile, getUnixPermissions, setDestinationName, setFileOverwriteBehavior, setOverrideUnixPermissions, setShouldUninstall, setSourceFile, setUnixPermissions Methods inherited from class com.zerog.ia.auto.project.InstallableObject getBelongsToUninstallPhase, getRollbackEnabledCancel, getRollbackEnabledError, getRuleExpression, getRules, getRulesLogicalOperation, getTagsInInstallPiece, setBelongsToUninstallPhase, setRollbackEnabledCancel, setRollbackEnabledError, setRuleExpression, setRulesLogicalOperation, setTagsInInstallPiece Methods inherited from class com.zerog.ia.auto.project.ProjectObject equals, getReferenceID, hashCode, setReferenceID Methods inherited from class java.lang.Object getClass, notify, notifyAll, toString, wait, wait, wait Sample custom code The following is an example of Java code that adds an install directory to the first directory in the Install Sequence. When this sample code is executed on the attached sample project a new folder is created under User Install Folder in the Install Sequence. package com.company.ProjectAuto; import com.zerog.ia.auto.project.actions.InstallDirectory; import com.zerog.ia.auto.project.*; public class ProjectInstallAuto { public static void main(String[] args ) { ProjectAutomation.setIALocation("Path it InstallAnywhere installation directory"); // change to point to your project file Project iap = ProjectAutomation.loadProject("Path to project file"); //Get the First Installation Folder in the tree in install-sequence OSHostDestinationFolder destinationFolder = iap.getOSHost().getFolders().get(0); //Add a new directory to the Installation Folder InstallDirectory InstDirect = new InstallDirectory(); destinationFolder.getChildren().add(InstDirect); //save and close the project ProjectAutomation.saveProject(iap); System.exit(0); } } Additional Information For more information on the Project Automation API, click here. ... View more

Summary This article discusses about Windows SmartScreen Error when installer is launched and how to prevent it. Synopsis This article discusses about Windows SmartScreen Error when installer is launched and how to prevent it. Discussion When launching a code signed installer on Windows 8.1 or higher version following error screen is encountered: This error screen is because of SmartScreen filter technology which was initially designed for Internet to protect users from malicious websites and web applications. SmartScreen filter requires Extended Validation (EV) code signing Certificates to accept the installer as a certified application. Therefore, if the user digitally signs the installer with EV code signed certificates then the user would not encounter this error. Additional Information For More information about Microsoft SmartScreen & Extended Validation (EV) Code Signing Certificates click here. ... View more

Summary This article provides steps about how to create a VM pack from a JDK Synopsis This article provides steps about how to create a VM pack from a JDK. InstallAnywhere Supports VM pack with one level of nesting of JRE folders. Discussion To manually create a VM from JDK. Please refer the following steps: Download and install the JDK on the desired platform. Copy the JDK directory to your personal directory and rename it to jre. Create an archive of the JRE directory. For Windows, create a vm.zip archive. Do not use compression and do not retain full path info For Linux and Unix like platform, create a vm.tar.Z archive. Create a compressed tarball. For example, tar -czvf vm.tar.Z jre. Create a vm.properties file. For more information about creating VM.properties file click here. Create a ZIP archive consisting of the VM archive (vm.zip or vm.tar.Z) and the vm.properties file. For best results, use maximum compression on this archive. Rename the resulting ZIP archive: <CustomVMPack>.vm. Copy the .vm file to IA_HOME\resource\installer_vms where IA_HOME is InstallAnywhere installation directory. Additional Information For more information about Creating a VM Pack for InstallAnywhere click here. To know more about VM pack structures click here. ... View more

Summary This article provides information about the options in the Execute Ant Script Action. Synopsis This article provides information about the options in the Execute Ant Script action. Discussion Execute Ant Script allows developers to execute scripts designed for the Apache Jakarta Project?s Ant application. If this action is selected, InstallAnywhere bundles Ant with the application. To set up an Execute Ant Script action, set the following options on the customizer: Options Description Ant Build Script Identify the Ant build script you want to execute by choosing one of the following options: Specify Build Script?Click Choose File to identify the script file you want to use. Navigate to the build script file and click Open. To examine the build script you selected, click View Script. Use Existing/Installed Build Script?Type the path and filename for an Ant build script file that either exists already or will be installed on the target system. Specify Build Properties To optionally identify a build properties file to use with the build script, select this option and then click Choose File to identify the properties file to use. Substitute IA Variables in Build Properties Select this option to resolve any InstallAnywhere variables in the build properties file you selected. Ant Target To specify an Ant target, choose one of the following options: Use Default Target?Select this option to use the target defined in the build script as the default target. Use Specified Target?Select this option to use the target you specify in the text box. This option allows you to execute the build script with a target other than the default target. Show Indeterminate Dialog Choose this option to show a message dialog while the Ant script is running. In the text box, enter the message that you want the indeterminate dialog box to show when the installer runs this action. Dependencies Ant supports a number of additional tasks. These tasks typically require an external library separate from the core Ant tasks. To include an external library, click Add jar or zip and select the external library that you want to include in this action. Click Remove to remove an archive listed in the text box. Note ? InstallAnywhere automatically adds dependencies required by the Execute Ant Script action. Additional Information The Execute Ant Script action is only for developers familiar with Ant. For more information, visit the Apache Ant site. ... View more

Summary This article talks about how to configure the Upgrade Configurations Dialog Box. Synopsis This article talks about how to configure the Manage Upgrade Configurations Dialog Box. Discussion The Manage Upgrade Configurations dialog box is where you define how your upgrade should detect earlier versions of the product that need to be updated. To access the Manage Upgrade Configurations dialog box: In the Advanced Designer, on the Project page, click Upgrades. The Upgrades view opens. Find the Upgrade Configuration setting. In the Upgrade Configuration setting, click the Manage Upgrade Configurations button. The following settings are available on the Manage Upgrade Configurations dialog box. Setting Description List of Upgrade Configurations Use this list to define one or more configurations that specify how your upgrade should detect earlier versions of the product that need to be updated. By default, this list shows a Default Upgrade Configuration item. To manage the items in this list: To add a new configuration, click the Add button next to the list. To view or edit the settings for a particular configuration, select the configuration and then review and modify the settings below the list as needed. To remove an existing configuration, select it in the list, and then click the Delete button. Criterion for Detecting Which Products to Upgrade Select the code that you want the current upgrade configuration to target. Available options are: Products that Share My Upgrade Code?The installer searches target systems for the presence of a product that has the same upgrade code. Products that Share My Product Code?The installer searches target systems for the presence of a product that has the same product code. ?If the product code option is selected, the following check box is available: Product Code for Earlier Version Does Not Match that of the Current Project?The installer searches target systems for the presence of a product that has a different product code that you specify. If you select this option, ensure that you use the Product Code of the Earlier Version box to indicate the product code for which you want the installer to search. ? The upgrade code is listed in the Upgrades view on the Project page of a project. The product code is listed in the General Settings view on the Project page of a project. To learn more about selecting an option for this setting, see Detecting Installed Earlier Versions that Need to Be Updated. Range of Product Versions to Upgrade Enter a range of version numbers that you want the current upgrade configuration to target. The range of version numbers for the upgrade configuration must be lower than the version number of the upgrade. That is, the range of version numbers must be less than the version number that you specify in the General Settings view on the Project page of the current project. Additional Information In the .com.zerog.registry.xml registry file, the Product Code is referred to as product _id and Upgrade Code is referred to as upgrade_id. For more information on upgrades, click here. ... View more