|
What should I set $IBM_DAV_PATH to?
|
|
Replies:
1
-
Pages:
1
-
Last Post:
Oct 30, 2009 8:15 AM
Last Post By: robtie
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
19
Registered:
Oct 05, 2009 12:53:35 PM
|
|
|
|
What should I set $IBM_DAV_PATH to?
Posted:
Oct 21, 2009 10:32:24 AM
|
|
|
|
I have the server, client and virtualizer installed on my linux.
When I try to virtualize an app, there's a reference to $IBM_DAV_PATH/lib in the scripts (ex. in davGen/SDK/compilers/gcc.sh). This implies that this variable should point to /usr/ibmdav/client or /usr/ibmdav/virtualizer.
On the other hand, when I launch the server (or service broker), it prompts me to set IBM_DAV_PATH and the only setting that works is /usr/ibmdav/server.
Those two options are conflicting and it forces me to export IBM_DAV_PATH differently when I want to virtualize an app and when I want to run it.
Is that how it's supposed to work or did I mess something up? Why aren't the relative paths set so that IBM_DAV_PATH could simply point to /usr/ibmdav?
Regards
|
|
Posts:
19
Registered:
May 13, 2008 12:49:42 PM
|
|
|
|
Re: What should I set $IBM_DAV_PATH to?
Posted:
Oct 30, 2009 08:15:05 AM
in response to: _Big_Mac_'s post
|
|
|
|
Hi,
when running the virtualizer and when running the DAV-enabled client the IBM_DAV_PATH
should point to the DAV client install. The default on Linux is IBM_DAV_PATH=/usr/ibmdav/client
On the server side (including the DAV broker) the default on Linux is IBM_DAV_PATH=/usr/ibmdav/server
Generally the client and server are on different machines so there is no conflict.
If running on the same machine one window could be used for the client and another
for the server. Alternatively to run in the same window/console the environment could be set e.g.
by sourcing a script to set the server-side environment and starting the service(s)/broker followed by sourcing a script to set the client-side environment and running the client.
Regards,
-Robert
|
|
|
|
|
