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.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- How to change VM packs path vie Variable
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
02:12 AM
How to change VM packs path vie Variable
Hi All,
I need to pick the VM packs from different location (say /opt/VM) instead of/resource/installer_vms.
I plan to move all VM packs from IA_DIR>/resource/installer_vms directory.
So I added my VM path location (/opt/VM) in Edit/Preferences/ Resources/ VM Pack Resource Paths dialog.
It Build configuration panel it lists all the VMS available under /opt/VM/.
This preference changes are stored in my home directory.
I need to save these preference settings permanently in .xml file. Since the InstallAnywhere will be launched by different users.
Is there any InstallAnywhere variable that updates the installer_vms directory from default location to another location?
Please help me in this.
Regards
Kalai
I need to pick the VM packs from different location (say /opt/VM) instead of
I plan to move all VM packs from IA_DIR>/resource/installer_vms directory.
So I added my VM path location (/opt/VM) in Edit/Preferences/ Resources/ VM Pack Resource Paths dialog.
It Build configuration panel it lists all the VMS available under /opt/VM/.
This preference changes are stored in my home directory.
I need to save these preference settings permanently in .xml file. Since the InstallAnywhere will be launched by different users.
Is there any InstallAnywhere variable that updates the installer_vms directory from default location to another location?
Please help me in this.
Regards
Kalai
(9) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
02:50 AM
In build command line, you can define a build properties file in which you can define vm path.
something like: com.zerog.ia.build.vmpack.XXX.path where XXX is platform specific.
Refer to the documentation for more details.
--Jerome
something like: com.zerog.ia.build.vmpack.XXX.path where XXX is platform specific.
Refer to the documentation for more details.
--Jerome
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
03:47 AM
I created build.properties files and placed in the same location where my project file(iab.xml) is available.
cat build.properties
com.zerog.ia.build.vmpack.solaris.path=/opt/VM
com.zerog.ia.build.platform.solaris.vm=SunJRE160_24SolarisSPARC.vm
But still I am not able to see the SunJRE160_24SolarisSPARC.vm pack in InstallAnywhere under Build->Build configurationïƒ Build targets
Correct me if I have misunderstood.
cat build.properties
com.zerog.ia.build.vmpack.solaris.path=/opt/VM
com.zerog.ia.build.platform.solaris.vm=SunJRE160_24SolarisSPARC.vm
But still I am not able to see the SunJRE160_24SolarisSPARC.vm pack in InstallAnywhere under Build->Build configurationïƒ Build targets
Correct me if I have misunderstood.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
06:19 AM
kalpeer wrote:
I created build.properties files and placed in the same location where my project file(iab.xml) is available.
cat build.properties
com.zerog.ia.build.vmpack.solaris.path=/opt/VM
com.zerog.ia.build.platform.solaris.vm=SunJRE160_24SolarisSPARC.vm
But still I am not able to see the SunJRE160_24SolarisSPARC.vm pack in InstallAnywhere under Build->Build configurationïƒ Build targets
Correct me if I have misunderstood.
You won't see it in the GUI/build targets, the build.properties file will overwrite it at build time.
But if you do a build, then this /opt/VM/SunJRE160_24SolarisSPARC.vm
should be used.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
09:05 AM
Thanks a lot Jerome..
It worked fine.
It worked fine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
10:39 AM
To build.properties I added the below statement for Windows build
com.zerog.ia.build.vmpack.windows.path=/opt/VM/SunJRE160_07Win32.vm
com.zerog.ia.build.platform.windows.vm=true
com.zerog.ia.build.platform.windows.novm=false
During the command line build VM is getting picked up from/resource/installer_vms only.
For Solaris and Linux VM pack is picked from /opt/VM/ directory but for Windows its getting picked from default location.
If I remove the Windows VM pack from/resource/installer_vms directory build is getting failed.
Please help me to solve this problem. I am doing the build in Solaris platform.
com.zerog.ia.build.vmpack.windows.path=/opt/VM/SunJRE160_07Win32.vm
com.zerog.ia.build.platform.windows.vm=true
com.zerog.ia.build.platform.windows.novm=false
During the command line build VM is getting picked up from
For Solaris and Linux VM pack is picked from /opt/VM/ directory but for Windows its getting picked from default location.
If I remove the Windows VM pack from
Please help me to solve this problem. I am doing the build in Solaris platform.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
11:12 AM
I don't know if there is a misconfiguration or an issue there ... I'm not using this setting.
anyway in documentation, it refer:
config.1.com.zerog.ia.build.vmpack.windows.path=
where "config" seems to be the name of your build configuration (in case you have more than one. (named 'Migrated Configuration' if not renamed).
Try tuning this, otherwise maybe ask some help from support.
--Jerome
anyway in documentation, it refer:
config.1.com.zerog.ia.build.vmpack.windows.path=
where "config" seems to be the name of your build configuration (in case you have more than one. (named 'Migrated Configuration' if not renamed).
Try tuning this, otherwise maybe ask some help from support.
--Jerome
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
11:37 AM
It remind me an old issue from the time I was using this build properties file, and I had opened an incident to support for a similar reason.
As they didn't fixed this in a timely fashion, I get rid of this properties file.
So I went to my old incident cases, and found that they were suggesting me to use xml properties file instead of text.
You can find template under\resource\build. The file is named "BuildProperties.xml"
Have a nice try .... and keep us informed
--Jerome
As they didn't fixed this in a timely fashion, I get rid of this properties file.
So I went to my old incident cases, and found that they were suggesting me to use xml properties file instead of text.
You can find template under
Have a nice try .... and keep us informed
--Jerome
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 20, 2011
01:54 PM
Thanks Jerome, i will try with properties.xml file and will update .
Today i got the below error when i try to use the VM from different location via build.properties file.
InstallResources/>
Error Generating the Solaris with VM
Installer.
Today i got the below error when i try to use the VM from different location via build.properties file.
InstallResources/>
Installer.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 21, 2011
01:45 AM
I created the BuildProperties.xml file under where my project was available.
Below is the BuildProperties.xml file contents
InstallAnywhere fails to generate the installer for Solaris platform.
InstallAnywhere projext.xml –p BuildProperties.xml
Please help me in this.
If there is any link for the documentation please provide me.
Regards,
Kalai
Below is the BuildProperties.xml file contents
InstallAnywhere fails to generate the installer for Solaris platform.
InstallAnywhere projext.xml –p BuildProperties.xml
Please help me in this.
If there is any link for the documentation please provide me.
Regards,
Kalai