Claudine,
Cloud computing, the cool environment where R:BASE applications rock!
Exactly 19 years ago, who would have thought that we would be talking
about consolidating our business applications and running them on the
cloud, where every authorized user can access your secure R:BASE
applications from anywhere using any device. How about 2017 and beyond ...
And, we the dreamers at R:BASE Technologies kept up with everything,
including the first R:BASE cloud server and the first R:BASE
application deployed on Microsoft Windows Server 2012 R2 and now on
Windows Server 2016. It is really exciting to see how R:BASE
applications and custom R:BASE Web Portals (using Oterro, Node.js,
and Java) are helping our R:BASE clients.
Now to your cloud specific questions ...
When users are successfully logged in on the cloud server, using the
web browser, such as RDWeb on (Windows Server 2012R2, Windows Server
2016), they are actually running everything on the server itself.
Based on the user account and user environment configuration, you may
or may not allow to share and/or access local resources. The cloud
environment (User and Windows) on the cloud server is also configured
to use the C:\Temp
In our R:BASE cloud server (RDWeb) setup and guidelines ....
Define Environment Variables (Administrator and all Remote Desktop Login Users)
Start > This PC > Properties > System > Advanced system settings >
Environment Variables ...
User variables for Administrator
TEMP: C:\Temp
TMP: C:\Temp
System variables
TEMP: C:\Temp
TMP: C:\Temp
See attached screen shots.
Since the compiled application runs on cloud server along with
corresponding DLLs and CFG files, based on the SCRATCH C:\Temp
settings, all R:BASE temporary SCRATCH (.$$$) files will be stored
under C:\Temp.
FYI, each new session of R:BASE (either as RDP or RDWeb, WebPortal)
creates its own unique 32-digits temporary scratch (.$$$) files.
Using this approach, there is only one place to monitor, as well as
one place to maintain/clean all scratch files, etc.
Yes, it is very safe to delete all (*.$$$) files found in C:\Temp
directory or wherever they live. You will get the -ERROR- message if
those .$$$ files belong to active R:BASE or OTERRO session(s).
To answer your last question, in my personal experience as well as my
clients', who are running very complex multi-user business
applications on the cloud, C:\Temp been the best configuration. Of
course, I always speak of myself, my experience, and the way I make
my R:BASE work in all these environments.
I hope that answers your question.
Very Best R:egards,
Razzak
At 04:31 PM 1/28/2017, Claudine Robbins wrote:
With cloud computing comes a question on C:\TEMP.
Each user has a local user setting and a local system setting.
And as an RD user, a cloud user account setting and a system setting.
Since the compiled application runs on the cloud server, are
R:BASE's temp files written to the cloud server C:\TEMP or the local C:\TEMP?
AND most importantly, is it safe to delete all files found in
C:\TEMP directories wherever they live?
A corollary to this question is, has best usage for setting
environment variables to C:\TEMP changed?
--
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
