In a windows server environment, are these setting correct if the server application is running on the server only (WEB application).
lh3srvc.ini
Shares
C:\Revsoft\web\OIWeb7.0=C:\Revsoft\web\OIWeb7.0
C:\Revsoft\web\WEBData=C:\Revsoft\web\WEBData
and in each REVPARAM at the root of these directories:
Revparam 1
ShareName=C:\Revsoft\web\OIWeb7.0
Revparam 2
ShareName=C:\Revsoft\web\WEBData
Pascal Landry
Pascal,
I would recommend using a simpler share name, I am concerned that the special characters in your share names might create parsing problems. So make your settings something like this:
lh3srvc.ini
Shares
OIWeb7=C:\Revsoft\web\OIWeb7.0
WEBData=C:\Revsoft\web\WEBData
Revparam 1
ShareName=OIWeb7
Revparam 2
ShareName=WEBData
Pat
Pascal,
If this is a Windows Server, then there is no need for a .ini file and paths in the revparam files. Treat the UD on a Windows Server just like you would the 2.1 Service. On the surface, the only difference is the need for only one revparam.
If you are trying to "hide" the data files, well, that is another matter.
Kevin
Pat, Kevin,
Thanks for the response.
Pat the special characters, I imagine you refering to the $ in my share, is to signify that it's a hidden share within the windows server environment. When you create the share, if you specify the $ sign at the end, you will not see the share when browsing through network neighborhood.
As for the ini file. I am trying to hide every thing. I guess in my little insecure world it makes me feel more secure;)
I guess my point would be that if I have a system running locally (web) and have a seperate environment for users through WAN do I have specify share for all, only those that are not running locally or none and what would be the correct syntax if I do chose to use the ini in a windows environment.
Pascal Landry
Pat the special characters, I imagine you refering to the $ in my share, is to signify that it's a hidden share within the windows server environment. When you create the share, if you specify the $ sign at the end, you will not see the share when browsing through network neighborhood.
No.
I was referring to the ':' and '\' characters in the share names in your lh3srvc.ini file and in your revparam files. My suggested alternatives eliminated these.
Pat
Ok,
I've written in the full path as the share and it works quite well. But as mentionned by Kevin, I could probably eliminate completly the share reference for a local server operation.
Pascal