Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)

Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.

Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)

Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.

Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional

A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.

Slide 2
Master the art of DevOps
Master in DevOps Engineering (MDE)

Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.

Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert

Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.

Slide 3
Learn and get certified
AWS Certified DevOps Professional

Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.

previous arrow
next arrow

Troubleshooting Installers in InstallAnywhere

Spread the Knowledge

deployexpert created the topic: Troubleshooting Installers in InstallAnywhere
There are several methods available to debug InstallAnywhere installers. Deciding
upon which method to use depends in part on the installer development cycle—during
installer development or later if an end-user has a problem with the installer.
Most InstallAnywhere installers utilize Macrovision’s LaunchAnywhere technology.
Along with many convenient features for end-users (double clickable launchers,
native-like user experience) LaunchAnywhere launchers provide a host of built in
debugging features.

During Installer Development
InstallAnywhere can output debug information to a file.
In the Installer Debug Output Section of Project | Config are fields which define what
file locations to send stdout and stderr. The options for the text fields are to leave
blank which discards the information, enter “console” which sends the information to
a live console, or to type the file paths. Both entries should point to the same file.
These paths should be absolute, and can be managed using Java paths, rather than the
system specific paths. This feature allows developers use one entry for multiple
platforms.
For example:
Send stderr to: /tmp/outputfile.text.
Send stdout to: /tmp/outputfile.text
These settings will direct the output to /tmp/outputfile.txt on a Unix or derivative
system, and to C:\tmp\outputfile.txt on a Windows system. The file itself (in this
example outputfile.text) will contain most, if not all information needed to debug
InstallAnywhere installations.
Because these files will not be uninstalled, we recommend that this feature be
deactivated prior to the final build of the product installer. However, some developers
have chosen to leave the output intact to make debugging any issue that arise post
development easier.

Facebook Notice for EU! You need to login to view and post FB Comments!
Rajesh Kumar