Re: InstallAnywhere details

You are absolutely correct, Execute Script returns the exit code for the action not of the underlying batch/script file. My experience with says that IA execute script does not work correctly in case of DOS batch files.
The reason being, execute run script uses Java Process.getRuntime.exec() thread to run the batch or command passed. Here Process.waitfor() method is used, if the underlying script uses @echo ON inside the script the behavior is very abrupt. Only the first script's 1 to 6th or 7th steps are run after that the script keeps on waiting thereby making the installation hang.

I would suggest to use your own plugin for executing command or batch specifically when the command or script calls another shell to execute the sequence of steps.

In the plugin spawn a thead and dont wait for the thread to complete. here the disadvantage is you will not get the complete the stderr, stdout till the theread completes but its a nice tradeoff done where you want to set gurentee for the underlying command to complete sucessfully.

I have developed a plugin which you can use if you want.

On Thu, Apr 16, 2009 at 6:46 PM, tony prabhu <ruban142003@yahoo.com> wrote:

Hi,   I am a beginner with IA and I want to know about the Execute Script/Batch action and how it works. I believe the exit code in this action is only for the action and not for the script or the commands it executes. So, how can i get an exit code for the executed script? Please explain to me in a detailed manner.   Thanks Tony

Re: Help

You are messing up two different things, earlier you said you want the user to input the architecture of the machine, now your requirement is going on the dev side.

Wait I will explain in detail

If your requirement is just to find the end users machine architecture

either run a custom java code or run a execute command utility in IA found under Add Action --> General Tab,

The command to run in uname -m, it will return u i386 which is 32 bit,

To find out more about various OS check out this link for determining the OS architecture, http://www.stata.com/support/faqs/win/64bit.html

Regarding running this write a Java class which would determine the OS version and subsiquently the OS architecture. Store the result in a IA variable

Code snippet

<>

class MyCustomCode(InstallerProxy ip) extends IACustomCode
{
   /* Run the logic to store the OS tye in a variable say MyOS */

   ip.substitute("OS_TYP", MyOS) // here the value of MyOS determined earlier is stored in a IA valiable $OS_TYP$
}

Inside the Install action under ur IDE you can add a compare installanywhere action to install any specific file or folder

e.g $OS_TYP$ equals 64bit then install else move ahead.

I do not have an IDE infront of me right now otherwise I would have sent you some screen shots.

If you are still face the issue I will create a sample project for you...for this logic

****************************************************************************************************

********************************************************************************************************

 

I am trying to download the enterprise version.

But there is still one doubt which is - the panel "get user input" is for the end user not for the developer (who is using InstallAnywhere for making installer e.g. me).

Can u throw some light on it please???

Actually I want InstallAnywehre to prompt me (developer) for taking the input as 32 bit or 64 bit at the time of building the project as shown below as per the requirement of the end user.

 

 

 

 

An issue with 32 bit and 64 machine

Problem :

 

Installerwhich build the application for multiple platforms (targeting Linux, AIX, HP-UX, Solaris and Windows).

My application has  binaries for above 5 platforms each of 32bit and 64bit (so kind of 10 platforms).

 

I have a directory structure like below

 

Application

|

|-----Linux

|              |-Linux32

|              |-Linux64

|

|-----AIX

|              |-AIX32

|              |-AIX64

|

|-----HP-UX

|              |-HP-UX32

|              |-HP-UX64

|

|-----Solaris

|              |-Solaris32

|              |-Solaris64

|

|-----Windows

|              |-Windows32

|              |-Windows64

|

 

Now what required is when I build as shown below my application and check the Linux box it should prompt  me to take input as "Linux32" or "Linux64" (user input) so that the  Linux installer of 32bit or 64bit is built.

 

 

 

 Solution :

Its quite easy to do that, installanywhere  has an inbuild functionality to check the OS architecture. You can store the OS architecture in the IA variable and implement your logic once you are known to end users OS architecture.

You will find this feature in Organization settings.

InstallAnywhere buildoutputs are independent to platform architecture, you can build your application for any desired platform with or without VM and run it. At the run time have a user input panel or at rutime decide the architecture of the user machine and cotinue with your installation logic.

Like this


Application ----
                      Folder 1 <Only if 32 bit>
                      Folder 2 <Only if 64 bit>

In the install section you can put a rule of compare installAnywhere variable so that it gets installed only when the rule is met.
 

Uninstaller Errors

Recently after changing the product name of one of the Merge modules in my suite I started getting errors while uninstallation.

When the uninstaller was called it threw a java exception saying target invocation exception stating



ZeroGu5: c:\program files\OpenSource\InstallFrameWork\Uninstaller\resource\iawin32.dll not found

at ZeroGa2.b(DashoA10*..)

at ZeroGa2.b(DashoA10*..)

at com.zerog.ia.installer.LifeCycleManager.b(DashoA10*..)

at com.zerog.ia.installer.LifeCycleManager.a(DashoA10*..)

at com.zerog.ia.installer.Main.main(DashoA10*..)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.zerog.lax.LAX.launch(DashoA10*..)

at com.zerog.lax.LAX.main(DashoA10*..)

Upon inspection I found that the resource folder that contains platform specific dll's under the uninstall folder. Even the global registry file that contains the file/folder installation was also found to be missing, so practically the uninstaller cannot work without this file.

Scratching my head for hours I build the installer with high debug enabled (jvm parameters -Dlax.debug.level=3 -Dlax.debug.all=true) with stderr and stdout directed to a file, but could not trace out any specific problem.

The installer archive contained all the resources that are required inside the uninstall folder, so there was no question that its a build issue.

Then I started the the dry run of the program my normalizing the payload to zero, modifying the project information properties and found that the product name had a trailing space at the end

Once the trailing space was removed the installation and uninstallation started working properly.

Although a is a kind of cosmetic defect but took hell lot of time to dig it out. Probably the Install Anywhere team forgot to check the product name property for any trailing spaces that can disrupt their XML transformation logic.

Avinash Anand

An accomplished software engineer looking for a challenging opportunity with a globally respected organization that provides ample opportunities to showcase my expertise, enhance my knowledge and allows me to contribute as a positive factor in the progress of the company. Active contributor in open source world, currently working in Google appengine and Java based open source cross platform installer framework.


Professional Summary

* Over 42 months of Development experience in Java/J2EE (Core Java, JSP, Servlet, JDBC, XML).
* Responsible for System Analysis, Design, Coding, and Qualitative experience in managing project modules independently.
* Extensive exposure to: Waterfall and Agile Development approaches.
* Development processes like Analysis, Design, Coding, Testing and Maintenance.
* Client-Server Architecture and MVC Architecture.
* Object Oriented Analysis and Design (OOAD).
* Worked with protocols such as SNMP, TCP/IP, UDP, SIP, H.323.
* Well exposed to both Client/Server and Web environment.
* Experience in doing unit testing using JUnit. Created test plan for unit testing.
* Used Rational Purify Plus for analyzing code coverage, code optimization and memory management.
* Interactive team player and proactive personality.
* Experience in installation, configuration and maintenance of Operating Systems, Web Servers, Database Systems and Mail Servers.


Product Software Components :

Operating Systems : Windows 2000/2003, Sun Solaris, IBM AIX
Databases : SQL Server 2000, Oracle, DB2
Web Server : Microsoft Internet Information Server, Sun ONE Web Server, IBM HTTP Server, Tomcat
Application Server : IBM WebSphere Application Server

Work Profile includes :

* Involved in creating multi Installer for the product using ISMP 5.0 and InstallAnywhere over various platforms such as Windows AIX and Solaris.
* Worked in installer migration from ISMP to InstallAnywhere 2009.
* Written blog over InstallAnywhere http://installanywhere.blogspot.com
* Involved in writing Java Beans for integration with Install Shield, custom code and plugin development for InstallAnywhere
* Worked with Accresso support team bug reporting and getting timely fixes.
Integration of various modules created under the project.
* Addressed various bugs filled against the installer.
* Documented all the defects to be addressed against the product in concern with the current minor release
* Created Installer framework for the current service pack release over ISMP 5.0 for all the platforms supported by the product Windows, AIX and Solaris
* Worked on cumulative service project. Designed completely new architecture for the service pack layout.
* Preparing/Attending the Interim/Internal Audits.
* Project Status Reporting and other related Escalations to the Development Manager.



Skill Matrix

Languages : Java, C, C++, Junit, Python
Operating System : Windows, Linux, AIX, Solaris.
Database/RDBMS : Oracle, DB2, MS SQL Server 2000.
Application Server : IBM WebSphere Application Server, Tomcat
Web Server : Microsoft Internet Information Server, IBM HTTP Server
Scripting : JavaScript, XML
Knowledge of : VMware, LPAR and TDD



Contact me

avinash.anand007(at)gmail.com

Location : Pune, India

InstallAnywhere global registry

Unlike InstallShield InstallAnywhere maintains its product information in a xml file (.com.zerog.registry.xml) as compared to the vpd.properties file created by Install Shield.

Some times it becomes tough for the end user or project author to get rid of a corrupt installation or uninstallation.

.com.zerog.regostry.xml file contains product name, version, UUID and description apart from the components and DIM registration information. This is typically useful if you have to identify a IA installation from a different framework say Install Shield.

This file is stored in /var directory or user on the UNIX machine if the installation is done by the root user else the file is stored in the home folder of the user.

In case of windows the file gets created under windows home drive (c: or d:)

A case study and its remedy

Q My installer/uninstaller did not run successfully! Can not proceed with a fresh installation

Ans- Remove/rename the global registry file and try running the installer/uninstaller

Q Needs to identify the components installed by the installer or need to find which components were removed by the uninstaller

Ans- Check the xml file it will contain the component information, the file in itself is self explanatory in nature.

Q. By mistake I have removed the global registry file but installation is intact, will by uninstallation work properly?

Ans- Yes absolutely, if the uninstaller does not find the global registry file it will look for the file at $USER_INSTALL_DIR$/Uninstall_$PRODUCT_NAME$/.com.zerog.registry.xml file it contains all the information about that individual installation.

So conclude with the global registry file can help the user to manipulate the installation or uninstallation in a desired manner and is sometimes very helpful in recovering the product instance after a corrupt installation

Developer Installation Manifest

Developers of the InstallAnywhere community would be very much familiar with the terminology "Developer Installation Manifest" commonly refereed as DIM.

InstallAnywhere provides the installation developer add addition pay load to their projects without adding any rework or hassle. The use of DIM proves to be of great importance if the application is developed by a large team across multiple sites. The process of packaging and requirement gathering proves to be very tedious and error prone. Due to lack of communication or insufficient knowledge many a times small bugs are introduced to the application package in the form of extra files/files missing/non registration of OCX etc.

Now imagine if theres a way the application developers who are writing the actual software do not require to communicate the list of file to be shipped in the required directory structure :) , imagine if the developer can test his standalone package while debugging or testing his application in stand alone mode. That to the developer does not require to this into an xml with any common text editor, all he/she has to do is to use his frequently used dev IDE eclipse or .NET editor! Seems cool ..... But how????

InstallAnyewhere allows to install plugins to commonly used development IDE's currently Eclipse and .NET IDE, these plugins allow the application software engineer to author to create DIM's which contain source and target locations of the file needed to run his component . All he needs to do is to identify the files and folder source location and needs to provide the target location on the end machine where it is going to be installed. This DIM can be plugged into the main project owned by the installation author or the Build/Release engineer. This gives the development team the sense of ownership of the application files owned by them and reduces the cost of maintenance and authoring to a large extent.

If will be asked to rate features and benefits of DIM over the traditional benefit of adding the files and folder into the main project I would give it a 10 on 10.

I am listing down some of the key benefits of the DIM below

1. DIM's allows the flexibility to be updated and owned by individual developers
2. It creates sufficient data encapsulation to the rest of members of the project
3. Developers can add files and folders inside the DIM
4. They will have option to register the ocx and dll if required wihin the DIM
5. Environment variables can be created inside the DIM
6. Group functions can be assigned inside the DIM
7. DIM's can be build and tested in a stand alone mode there by reducing the build time and ease for the developer to test his/her application

Above all features are definitely a great boon for the developer and build engineers of distributed and gigantic applications

I have also observers some of the major issues with InstallAnyhwere collaboration plugin in Eclipse. They are big issues but still can be lived with, here are some of them.

1. If the folder addition feature in the DIM is given some filters to add the contents of the DIM, it cannot be build and gives some weired exception. The possible workaround for this issue is to add the folder as a speed folder inside the main project and then give constraints or filters
2. Files need to be physically present at the source location if you are trying it to add in the DIM. The possible work around for this issue is to create a dummy file at the specified source location using touch utility or its equivalent on any OS
3. The installer output of the DIM can not be used in a stand alone mode for the customer purpose as it shows a warning message that "This installer has been built using a collaboration tool and hence should not be used to production"
4. The most big issue is that all the plugins that are installed and used has to be compulsorily have a valid license for its use(i.e if you have a team of 100 people who will be writing DIM's for their small software piece you need to actually have 100 licenses). The only available workaround for this problem is to install IA collaboration tool on a common machine where all the developers are going to have access and each of them will be authoring their individual DIM at different point of time :(

All of the above pros and cons have taken me to the conclusion that DIM's are of great use if used efficiently and with proper planning.