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
- :
- Re: Running directory
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
‎Dec 13, 2007
07:31 AM
Running directory
Hi
I have an IA installation setup at mounted network location /nw/jomon
I am running the installation from a location /local/dir1/dir2 as /nw/jomon/Solaris/Disk1/InstData/VM/install.bin
Is there any IA Variable or some other workaround to find out the location from where it is launched(i.e. /local/dir1/dir2)?
something like a `pwd` from a shellscript 🙂
Regards
I have an IA installation setup at mounted network location /nw/jomon
I am running the installation from a location /local/dir1/dir2 as /nw/jomon/Solaris/Disk1/InstData/VM/install.bin
Is there any IA Variable or some other workaround to find out the location from where it is launched(i.e. /local/dir1/dir2)?
something like a `pwd` from a shellscript 🙂
Regards
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 09, 2008
07:43 PM
i want to know if we can do this too!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 10, 2008
02:39 AM
After a lot of searching, finally I could find out that there is an environment variable 'PWD' set for the current directory in UNIX. So I used $lax.nl.env.PWD$ in InstallAnywhere for the same.
It is working for me in whatever scenarios I tested till now.
It is working for me in whatever scenarios I tested till now.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 10, 2008
04:19 AM
Quoting from the IA manual, as it seems that there is an builtin IA variable for this:
"$INSTALLER_LAUNCH_DIR$ This is a full path to the installer's self-extractor. This variable is read-only"
"$INSTALLER_LAUNCH_DIR$ This is a full path to the installer's self-extractor. This variable is read-only"
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 10, 2008
04:32 AM
yes, $INSTALLER_LAUNCH_DIR$ will give you the location of the self extractor. But my requirement was like this... I have kept the installer in Dir1 and I go to Dir2 and run Dir1/Disk1/InstData/Solaris/VM/install.bin.
$INSTALLER_LAUNCH_DIR$ will give you the path Dir1/Disk1/InstData/Solaris/VM where I wanted the path Dir2.
$INSTALLER_LAUNCH_DIR$ will give you the path Dir1/Disk1/InstData/Solaris/VM where I wanted the path Dir2.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 10, 2008
06:43 AM
You're running the JVM installation separately?!?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 10, 2008
08:17 AM
no. I have just selected the "with VM" build option. if I am at /home directory and running /tmp/Solaris/InstData/VM/install.bin, the value of lax.nl.env.PWD is /home and the value of $INSTALLER_LAUNCH_DIR$ is /tmp/Solaris/InstData/VM. That is what I have observed.