I've created a generic logger. this logger captures the path of the calling fex, but it only works if the caller is on the client side, even though the logger.fex is on the reporting server.

In logger I use &IBIMR_fullpath to get the path of the fex, but this is empty if the calling fex is on the reporting server. Anyone tell me how to capture the path for a reporting server fex file?

This message has been edited. Last edited by: <Emily McAllister>,

Gavin, if &IBIMR_fullpath is blank, then the fex exists on the reporting server or is an adhoc fex. If &FOCFEXNAME is equal to 'ADHOCRQ' then it's an adhoc request. For reporting server fexes, a combination of &APPROOT (or &APPPRIV, whatever that is) and &FOCFEXNAME should provide the full path (though you have to append '.fex'). Unfortunately, one parameter uses slashes, the other back slashes. Meanwhile, we have two reporting servers in a cluster - the code must be on both servers, so we would have to include the server name, which I don't know how to do.

I can't use APPROOT as that isn't setup in our linux version in PROD. Plus, when I use it in Dev, I get this, which isn't what I'm looking for.

APPROOT = E:\Webfocus\ibi\apps;

&APPPRIV gives me the following:

A VALUE IS MISSING FOR: &APPPRIV

And FOCFEXNAME is ADHOCRQ.

What I'm attempting to do is get the APPLICATION Name of which the fex is running under, so I need the full path as it is on the report server/client side. Example, if the path is IBFS:/WFC/Repository/MyApplication/ I want really want "MyApplication", which I'm parsing out at the moment. If there is an easier way, client side AND reporting server, I'm all ears.

Well, I thought I found an answer. Seems WebFOCUS has an internal DB, that keeps track of all these things.

Table Name: wf_reposobj
Has many columns, here are a few:
LASTACCESSON
LASTACCESSBY
PRT_PATH
OBJNAME

However, it doesn't capture Reporting Server access, only client side. No breaks.

If you're not using approot, how are reporting server application folders defined?

I've not considered MyApplication in IBFS:/WFC/Repository/MyApplication/ to be an application, I thought it was just a folder in the repository.

We're on WF8.0.08 on Windows, so I imagine we have a different set of system variables.

quote:

If you're not using approot, how are reporting server application folders defined?

Sorry, I got confused, thinking of the usage, "/approot/myapp/myfile.fex", we can't use that as it's not defined in our Linux environment. Your speaking about the &APPROOT, which is always there, but that doesn't tell me what application within that approot folder I'm currently executing from, which is what I'm looking for.

My mistake - when I run the fex from Dev Studio, I get the proper App folder name:

&FOCFEXNAME   = baseapp/fml1

In our Windows environment, when I run a fex in a reporting server application folder, I get this:

&APPPRIV      = D:\ibi\apps80
&APPROOT      = D:\ibi\apps80
&FOCFEXNAME   = FML1
&FOCFOCEXEC   = _fml1

No app folder name .

I should never run anything from within Dev Studi - things behave quite differently.

There's some chatter here: Application Name Inside a FEX file

It appears to me pretty ridiculous that this isn't simple to do...

Code tweaked slightly since originally posted

-* Determine which application folder a fex resides in

-SET &ECHO=ALL;

-DEFAULT &FOCFEXNAME = 'NCRR004';

-SET &PROGRAM1 = LOCASE(&FOCFEXNAME.LENGTH, &FOCFEXNAME, 'A&FOCFEXNAME.LENGTH');
-SET &PROGRAM1 = TRUNCATE(&PROGRAM1);


SQL FMI SET SYSFILES FOCEXEC
-RUN

DEFINE FILE SYSFILES
FILENAME1/A64 = LOCASE(64, FILENAME, 'A64');
END
-RUN

TABLE FILE SYSFILES
PRINT
PHNAME
WHERE FILENAME1 EQ '&PROGRAM1';
ON TABLE HOLD AS H001 FORMAT ALPHA
END
-RUN

-READ H001 &PHNAME.A80.

-TYPE PROGRAM LOCATION: &PHNAME

This message has been edited. Last edited by: Francis Mariani,

Well, I made the same mistake and found a crazy discovery.. I was running the fex from appstudio, which means I never got what I was looking for. Then I ran it from the console, but via reporting server and it came back with just the name without the extension. Now get this.

If I'm in a fex that is doing an include on the logger fex, the &FOCFEXNAME has the FULL path and the extension of the calling fex, which is what I'm looking for.

I'm having one of those:

Welcome To FOCUS moments.

The two top fexes sit on the reporting server. Ran from the console, under the report server tree.

Logger.fex

-DEFAULTH &INFO = _FOC_NULL;
-DEFAULTH &CURRENTPATH = _FOC_NULL;
-DEFAULTH &FOCFEXNAME = _FOC_NULL;
-SET &CURRENTPATH = IF &IBIMR_fullpath.LENGTH GT 1 THEN &IBIMR_fullpath ELSE &FOCFEXNAME;
-TYPE CURRENTPATH = &CURRENTPATH;
-TYPE INFO = &INFO;

Caller.fex:

-SET &INFO = 'This is my info and add variables to it, so we know what is being passed in.';
-INCLUDE cc/log/logger.fex

This on sits on the client side.
CallerFromClient.fex:

-SET &INFO = 'This is my info and add variables to it, so we know what is being passed in.';
-INCLUDE IBFS:/EDA/WFCL/cc/log/logger.fex

ok, take it all back, I saw a path and was too excited. &FOCFEXNAME is returning cc/log/logger.fex, no matter who the caller is from the reporting server. Being called from the content server, gives me the caller, since I'm doing an INCLUDE.

No consistency in this product.

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