InstallAnywhere StandAlone Build with Docker Build your own Docker Image with InstallAnywhere SAB  On an machine where Docker is installed, create Folder (eg: IADockerBuild). Copy InstallAnywhere installer (eg: InstallAnywhere2020.bin for Ubuntu docker) to the above created folder (i.e IADockerBuild) and ensure the file has execute permissions. Create a file called DockerFile (no extension) inside the above created folder (i.e IADockerBuild) with the following content [Dockerfile] # Base Ubuntu Image FROM ubuntu:latest # Change to Root Dir WORKDIR / # Copy InstallAnywhere installer to root ADD InstallAnywhere2020.bin / # InstallAnywhere installation RUN ./InstallAnywhere2020.bin -i silent Launch Terminal and navigate to the above created folder (i.e IADockerBuild) Run the following command as 'sudo' or root user to build the Docker image with InstallAnywhere installed: docker build -t installanywhere2020 --no-cache=true . Wait for the build to complete. Once the build is complete run the following command to list the newly created image docker images   License InstallAnywhere SAB  Activate a Node Locked License For activating SAB using a node locked license, you need to manually copy the license file (license.lic) to InstallAnywhere [INSTALLDIR] location. It is also mandatory to create the container with --mac-address option, else the MAC/Physical address will be dynamic each time you create a new container. Open the license file that you want to use for activating InstallAnywhere SAB and copy the MAC address.           Use the same/copied MAC/Physical address to create the container using --mac-address docker run --mac-address <MAC-ADDRESS> -it <IMAGE> (Optional) In case if you want to create container, mount folder and assign MAC address at the same time run the following command: docker run --mac-address <MAC-ADDRESS> -v "<HOST-DIR>:<CONTAINER-DIR>" -it <IMAGE> Where: MAC-ADDRESS : is separated by colon( : ), eg: 00:16:7F:51:03:7D HOST-DIR : folder present in Physical machine/VM CONTAINER-DIR : folder inside the container;  if the folder does not exist it will automatically create it. The license file need to be copied to the installation folder. The container should be in Exited state in order to copy files to a container. Run the following command to Stop the container: docker stop <CONTAINER-ID/CONTAINER-NAME>         4. After the container is stopped, run the following command to copy the license file (i.e license.lic) to docker container. "docker cp license.lic <CONTAINER-ID/CONTAINER-NAME>:root         5. After the license file copy is done, run the following command to Restart the container: docker start <CONTAINER-ID/CONTAINER-NAME>          6. Navigate to the install directory cd /root/InstallAnywhere\ 2020          7. Register the Nodelocked license to the SAB build using the following command ./build -registerNodeLocked [path_of_license_file] Activate a Concurrent License Run the command as sudo or root user docker run -it <IMAGE>        2. Navigate to the InstallAnywhere location cd /root/InstallAnywhere\ 2020        3. Register the SAB build with concurrent License Server    ./build ls <License Server Port>@<License Server IP Address>   Note:  Please refer the following for addition details on the commands used: docker build: https://docs.docker.com/engine/reference/commandline/build/ docker images: https://docs.docker.com/engine/reference/commandline/images/ docker start : https://docs.docker.com/engine/reference/commandline/start/ docker stop : https://docs.docker.com/engine/reference/commandline/stop/ docker cp: https://docs.docker.com/engine/reference/commandline/cp/ docker run: https://docs.docker.com/engine/reference/run/ ... View more

Symptoms: InstallAnywhere digital signing feature uses a timestamp URL from Symantec which is being decommissioned (more details here) and migrated to Digicert. Signing with new Digicert URL causes a breakage in Digital Signing Diagnosis: When signing an installer with SHA-256 digest, using the new Digicert server (http://timestamp.digicert.com), the resulting installer is signed by SHA-256 digest, but the counter signatures are signed with SHA1 due to an incorrect order in which InstallAnywhere calls the signing APIs Affected InstallAnywhere Versions InstallAnywhere 2015 InstallAnywhere 2017 InstallAnywhere 2018 InstallAnywhere 2020 All minor releases of the above releases included Resolution The issue is resolved in a hotfix that can be downloaded from here. Please note that the hotfix is applicable on the latest service packs of above affected versions. Download and extract the contents of the file. Copy x86/IAWinDigiSign.exe to <IA_Install_Location>/resource/nativetools/windows Copy x64/IAWinDigiSign.exe to <IA_Install_Location>/resource/nativetools/windows64 After replacing the above files, in your InstallAnywhere project, navigate to Project à Platforms à Windows à Digital Signing and update the Timestamp server field to http://timestamp.digicert.com Additional Information If there are any additional issues, please contact our  Technical Support team   ... View more