Focal Point
[SOLVED] Possible to change the EDATEMP location?

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/1547034806

August 16, 2011, 08:47 AM
ABT
[SOLVED] Possible to change the EDATEMP location?
How easy/Is it possible to change the location of EDATEMP? Right now it is on c:\ and I need it to be on D:\. I'd like to not have to reinstall the server/client.

- ABT

This message has been edited. Last edited by: ABT,


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
August 16, 2011, 09:51 AM
GamP
From the worksapce help file:
quote:

edatemp = operating system specific pathname
Internal default: edaconf
This defines the parent directory for edaprint.log and edatemp subdirectory.
Settable in the edastart.cfg file.


GamP

- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
August 16, 2011, 01:43 PM
ABT
Thanks GamP, found it in C:\ibi\srv76\wfs768\bin\edaserve.cfg as 'edatemp'. Does anyone know of any 'unintended side effects' of changing this?

- ABT


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
August 16, 2011, 02:25 PM
ABT
I've changed my edatemp setting in C:\ibi\srv76\wfs768\bin\edaserve.cfg to my D:\temp directory, restarted and it's still running in c:\temp. ideas?

EDASERVE.CFG
edahome = C:\ibi\srv76\home768p
edatemp = D:\temp
workspace_manager_name = "WebFOCUS 76 Server768p"
edaprfu = C:\ibi\profiles
approot = C:\ibi\apps
server_type = ffs
scaroot = C:\ibi\scale
cfg_date = 03/10/2009 11:22:53
crashed_cleanup = on
...


test.fex
-WINNT echo ========= WHERE AM I? ============
-WINNT cd
-WINNT dir /b


output
-----------------------------------------------
No HTML Output!
-----------------------------------------------

 ========= WHERE AM I? ============
 C:\temp\edatemp\ts000003
 stderr.log
 stdout.log
 sysh.tmp


Is there some other step I have not completed?

- ABT


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
August 17, 2011, 03:49 AM
GamP
This should be the only spot where you can set the temp dir.
And by the look of it, there does not seem to be anything wrong with the setting itself.
If I do the same thing, it changes the temp dir to that directory.
Mind you, the directory does have to exist, otherwise it will revert to the default.
But in this case it goes to the correct dir only on the c-disk iso the d-disk.
If this persists, I'd open a case with ib to check if something specific needs to be done for your release.


GamP

- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
August 17, 2011, 06:52 AM
ABT
thanks for the confirmation GamP. I think I am going to open a case. I have a second issue I need resolved too, might as well get them both done at the same time.

- ABT


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
August 22, 2011, 08:14 PM
ABT
simply have to set approot directive BEFORE edatemp directive. Thanks BJ!

- ABT


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
October 04, 2012, 04:06 PM
RRKen
I added the 'edatemp' line, restarted and now my log files go there but the temp files are still being generated in the old location. Any ideas?

edahome = /ibi/srv7703/home
jvm_rel = 15
license = 9999999999
edaprfu = /ibi/profiles
workspace_manager_name = "WebFOCUS 77 Server"
approot = /ibi/apps
edatemp = /edaserve/edatemp
server_type = ffs
scaroot = /ibi/scale
cfg_date = 07/16/2011 14:01:49


8.2.03 AIX Client Windows Tomcat
DB2, Terradata, SQL, Oracle
May 01, 2017, 11:55 AM
John_Edwards
Yep, me too. Does anyone know how to change where the actual process temporary files are housed mid-run? I'm on Data Migrator and WebFOCUS Versions 8.



May 01, 2017, 12:38 PM
eric.woerle
John,

Are you trying to define the foccache directory? There is a place to define this on the reporting server. Go to Workspace -> Settings-> Application Settings. there you can set the foccache_dir. This will require a server restart.

I'm hoping this is what you are looking for.


Eric Woerle
8.1.05M Gen 913- Reporting Server Unix
8.1.05 Client Unix
Oracle 11.2.0.2
May 01, 2017, 02:22 PM
John_Edwards
Another lead!

I changed it there and it isn't working, so I'm still missing something. An SE recommended a change to edatemp in edaenv.cfg. This is one of those things where there's some sticky issue that I need to find.

I've tried the C drive and an external drive, neither works. I'm still working it.

I'm on a virtual machine and it's out of space on the C drive sometimes, when I do very big runs.



May 01, 2017, 02:28 PM
John_Edwards
Now, when I say it isn't working, I mean that it isn't moving the tmp0000* directories. I see the logs move, but not the big stuff. The big stuff is what I need to move.

I know -- just make the C drive bigger. But the Ops guys aren't interested in making the change. If I can quote Valmont, "it's beyond my control."



May 02, 2017, 05:39 AM
Hank W.
You need to give the client a 'kick' too, not just the server. As in restart the tomcat service/ whatever your app server is on.

If it doesn't "bite" then you need to recheck what the environment variables are.


Cheers,
H.

WebFOCUS 8.1.05M
Oracle 11g - DB2
RedHat
May 02, 2017, 08:53 AM
John_Edwards
There's a trick to everything, eh Hank? You set me on the right path. I put my changes in and restarted Apache and it didn't take. But at that point I just said to heck with it, and bounced the entire machine. That did the trick. So, what I did for Version 8.1.0.4 on Windows Server 2012 was:

1. Proceeded to the C:\ibi\srv81\dm\bin folder and open the edaserve.cfg file. Note -- this is for Data Migrator, not WebFOCUS. To make the same change for WebFOCUS you would proceed to C:\ibi\srv81\wfs\bin.

2. Added the new edatemp directory line to the file. For me it was this line -- "edatemp = X:\edatemp" that I put right underneath the "scaroot = C:\ibi\scale" line, about 20 lines down the file.

3. Rebooted the entire box.

4. Ran the text.fex file from ABT's post above (fourth post in this thread) and got a response showing the use of the new directory for temporary files.

I haven't tested if using that external drive adversely affects execution speed very much. That is an interesting question that I'll need to look into. Some of these jobs are plenty big.

Thank you all Eric and Hank for contributing. As with most configuration issues, you just need to figure out what the magic step is to close the deal. In this case I needed to bounce the machine.