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. I seem to be experiencing some issues trying to create hold files and write them to a writable server application folder, as detailed in The instructions here. I seem to be able to at rare times, succesfully create a hold file, but not consistently, and am running into issues trying to replace them with updates.
I don't actually get any errors when creating an initial hold file in Infoassist -- everything seems to run fine, until I need to actually see that hold file to use it:
1. Many times the hold file does not show up in the data join section in InfoAssist, or in the application folder in webfocus (at least the way i view the application folder, which is by expanding our reporting server node and navigating to it).
2. Even though I cannot see this hold file, when i go to attempt to recreate it by saving as the same-named sql hold file in infoassist, I get a prompt that the file already exists, and to choose another name. This message appears while at the same time, the conflicting file name does not show up in the application folder in the file dialog box that is prompting the message. I can provide screenshots of this.
Its like there are phantom files there, or files I cannot see even though I am the one who has created them. There are times when I notice i have to restart the webfocus browser and infoassist to get stuff to show up in the server app folders, but I've waited days to see these files show up and they are not.
The instructions seem to indicate that if the hold file you are saving already exists, it will automatically be overwritten, but the opposite seems to happening for me.
Any Ideas?
I'm wondering if I'm just not using the correct method to create hold files using InfoAssist, but I'm not finding any instructions as to how to basically just encapsulate a few table joins into a single hold file, to eliminate the need for some end users to have to mess with joins. I think the first portion of the subquery hold file instructions would be how to do it, but maybe someone can point me to a better reference?
Please note we are experiencing a bug verified by support to my knowledge with this version that involves being unable to consistently upload data to server application folders without getting errors. I am wondering if it is related?
We are running Edition: WebFOCUS Product Release: 8.0 Service Pack: 10 Build Version: branch8010 Build/GEN Number: 73 Build/GEN Date: Tue Jul 07 17:55:14 MST 2015 Application Server: Apache Tomcat/7.0.33This message has been edited. Last edited by: <Kathryn Henning>,
While we wait for other members to provide any comments regarding your questions. These issues / questions may be best handled with opening a case with IBI Tech Support so that you can discuss this with the support person and possibly show them what you are trying to do and what happens. There are trace files that can be captured to get an idea of what is happening in the underlying processes.