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.
So, throughout this week we've been attempting to troubleshoot why a particular app domain within our 8104 repo isn't able to recognize dimensions that are joined successfully to a fact table within a fact table synonym on the data server side when (back on the Content side again) we either have a piece of the app trying to request a particular field from one of the joined dims or we create a brand new report based off that fact synonym that has the dims joined to it and none of the dims show up in the obj inspector once the report canvas populates.
So, I had a remote session with tech support from IBI yesterday to figure out what was going on. Eventually we were able to contain the issue to the specific app domain we were trying to get to work. This particular app domain we used CM with and imported it from an 8009 repo into our new 8104 repo. I guess that was not what we were supposed to do until we ran a .bat that converts portals, etc. to the 8.1 architecture. We found the instructions on how to manually run the conversion, but the .bat file we were supposed to run wasn't present in the WebFOCUS80 directory location for it. It does exist in the WebFOCUS81 directory location for it though. We go to enter our admin credentials to run the utility but it throws an error saying "no dice" more or less.
Has ANYONE here had to go through upgrading to 8.1.0x from an 8.0.xx version and successfully got their older 8.0 repos, portals, etc. to work without issue in 8.1?
Any insights and experience(s) would be much appreciated!
Thanks!
UPDATE: I figured out we weren't in need of converting our content and portals after all. We had 2 of the same master files created in different app directories, and we didn't configure custom settings for the new environment yet. Deleted the offending master file, rechecked app paths, configured custom settings, and everything is working now!This message has been edited. Last edited by: CoolGuy,
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015