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.
I had created the synonym(master file and access file) to use the External SQL Script. I have multiple oracle adapter configured on the server. When I tried to run the report which was using synonym created above, it didn't work. When I traced this problem, I came to know that this synonym is not using CONNECTION(Adapter) specified in access file. Instead it was using the first adapter specified in "edasprof.prf" file.
Does anybody know why it is ignoring connection specified in access file and using the first connection configured on the server?This message has been edited. Last edited by: Kerry,
7.6.9/7.7 Windows/OS 390 HTML
Posts: 11 | Location: Pune | Registered: March 08, 2011
Sounds like you are using the SQL Pass Thru method to get to your data? This method does not need Meta Data and does not use the access file.
It does, however use the Adapter connection and requires that you're IBI_USER account have SELECT rights on the Object on the Oracle side.
There are hundreds of SQL Pass Thru posts here but in short, you invoke your SQL as so. ENGINE SQLORA SET DEFAULT_CONNECTION [adapt connection name here] SQL SQLORA PREPARE SQLOUT FOR
SELECT TO_CHAR(TO_DATE(SYSDATE,'DD-MON-RR'),'RRRRWI') FROM DUAL; -RUN
TABLE FILE SQLOUT PRINT * END -RUN
Look for the Adapt Connection Name in an Access file that uses the same tables from the database that you want to connect to.
Example Access File: -------------------------------------------------------------------------------- SEGNAME=DATABASENAME, TABLENAME=DATABASENAME, CONNECTION=youradaptname, KEYS=0, $
I never knew this but you can create metadata for s SQL script file, which is very intriguing.
Dhananjay, I would put the SQL file in one of your Application Folders, then use the WebFOCUS Reporting Server Create Synonym page to generate the metadata. My acx file looks like this:
Francis, Thanks for your suggestion. But it didn't work.
I changed
DATASET=/ibi/apps/sample/sample.sql
to
DATASET=sample/sample.sql
where "sample" is my application.
But no luck. It is still using the first connection specified in "edasprof.prf" and ignoring the CONNECTION attribute specified in access file. Even if I remove CONNECTION attribute from access file, still it works and use first connection specified.
7.6.9/7.7 Windows/OS 390 HTML
Posts: 11 | Location: Pune | Registered: March 08, 2011
After few days of testing what I seen is criticizing.
It is using randomly selected connection and not the only first one. Just the probability of selecting first connection is more.
To test this I have created synonym from the query(for Oracle database)- select * from user_users
When I ran report using synonym created for above query, it is giving me different user name every time. If it is using the connection that is specified in access file, it should give the same username every time.
Please help!
7.6.9/7.7 Windows/OS 390 HTML
Posts: 11 | Location: Pune | Registered: March 08, 2011
Thank You Francis. We were just thinking to use the same approach.
Even though there are few cons of this approach like we have to edit the report definition while migrating code from dev to qa or prod which otherwise could have been managed at metadata layer(access file). But we don't have other option.
I have also opened the case with IBI for the same.
7.6.9/7.7 Windows/OS 390 HTML
Posts: 11 | Location: Pune | Registered: March 08, 2011
Creating Joins with master files which describe .sql script is not supported. see case 81492516 as far as I know this is a NFR which might be implemented quite soon in new releases and will pass the join to the DB (join to SQL query "derived table") I would recommend you to open a case with IBI and also request this functionality