As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Hello all! This is my first post. We have had WebFOCUS for a about 3 months now, so I’m still getting used to this tool. We have just upgraded to version 7.1.4 from 7.1.1.
I have a question related to the IBIMR_user and Reportcaster. I have a fex that captures the users NT logon via the IBIMR_user variable and passed that down to a where clause in a SQL server database for filtering. We have a stored procedure that sits on the database that determines who can see what at the row level and puts their NT logon on a row in a table with a value for security. We then join this table in on all of the reports. In the fex I will use this statement: SET &MGR = &IBIMR_user; Then I have &MGR in the where clause
The problem that I’m running into is when I try to schedule the report in Reportcaster, it does not recognize IBIMR_User as a variable; thus I cannot hard code the IBIMR_User value.
The way tried to get around this was to use a –DEFAULT instead of a –SET for the &MGR variable. This worked in part. It did import into Reportcaster and show IBIMR_user as a variable, so I could hard code a NT logon in Reportcaster…… but it broke the fex when you tried to run it from the dashboard because it will pass “&IBIMR_user” down to the database in the where clause; not the user NT logon. I’ve tried several different ways to get around this (with and without quotes) to no avail. Here is an example:
In Caster, there are 2 slots for PreProcessing fexes, (and 2 slots for Post processing fexes); Use one of the 2 slots to name a fex that just sets your default &var The fex could have just 1 line in it, if you like, -SET &IBIMR_user='CASTER'; You can use this approach to do all sorts of other things, like check the time of day for a fex that you have scheduled to run every hour, and then set the &&KILL_RPC to Y if the current hour is during the night time. Handy feature, that Preprocessing fex thing. I'm sure someone will come along and give you a slicker, caster-ish answer, but this w/a should help.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
I just want to say that I found a solution for this problem a few months back. I used an insert statement on the Report Caster DB to get it to honor the 'IBIMR_user' variable. Below is the insert statement I used.
Art
insert into rptCaster.BOTPARMS values ('S11f6v3v0703','T11f6v29rv01','IBIMR_user','NTName','single',NULL,'04')This message has been edited. Last edited by: ETLProg,
Dev 7.1.4 WinNT SQL Server 2005 DB Prod 7.1.4 WinNT SQL Server 2000 DB