quote:
The server is NOT in the "ibi" path
For the WebFOCUS server to access a file (text or any other supported format) the latter has to be accessible via the operating system. If the file is not in the same "box" where the WF server is running then you need to share that location so both the OS and WebFOCUS can access it. Mapping a drive (E:, F:, etc.) to the exact location would be helpful. From there, all you need to do is MAP that location in WebFOCUS and get to the file.
For instance, this scenario:
datasrv -> Repository of data files located in D:\shared_resources and shared as windows SMB resource (let's say "shared"). Within it you have a folder called "data" with a set of data files you need access to (e.g. mydata.txt)
wfsrv -> Box where the WebFOCUS reporting runs. From this box, via Windows, you should be able to access
\\datasrv\shared\data\myfile.txt or for simplicity, you could map \\dataserv\shared as F: and then the file could be accessed as
F:\data\myfile.txt. This is just OS stuff, not still related to WF.
Accessing the file from WebFOCUS should be very easy as the OS can now see it.
APP MAP DATA F:\data
FILEDEF MYFILE DISK DATA/myfile.txt
-RUN
Al you need now is to create a masterfile for MYFILE (myfile.mas) describing your text file and then issue a regular TABLE FILE MYFILE to use it.
Take a look at "Describing Data with WebFOCUS Language" for details on how to create the master file, and "Creating Reporting Applications" for details about APP MAP, FILEDEF and other user APP statements.
Sorry, I'm not able to access IBI's tech support right now so cannot provide actual document names and/or DN#.
Prod/Dev: WF Server 8008/Win 2008 - WF Client 8008/Win 2008 - Dev. Studio: 8008/Windows 7 - DBMS: Oracle 11g Rel 2
Test: Dev. Studio 8008 /Windows 7 (Local) Output:HTML, EXL2K.