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'm trying to import a CM Package, but I got a "Distribution error creating item". Looking at the logs, it error-ed when trying to import a .sch file. I can always recreate the schedule, I just need to import the rest of my procedures.
Does anyone know how to remove a *.sch from a zipped CM Package? I removed it from the "root" folder and the "root_content", but when I import the CM Package, it is still trying to import the .sch file. I did see that the .sch was in the XML Document, but I didn't want to go there.
I have a case #200625042. Just seeing if anyone had any thoughts here, as I'm waiting for a response.
thanks!This message has been edited. Last edited by: FP Mod Chuck,
Posts: 18 | Location: Tacoma, WA | Registered: August 20, 2019
The package I created was intended to replace a good chunk of the legacy reports in Production. Prior to importing the CM Package to Production, I was planning to first un-publish and hide the Legacy content. So... I wanted to simulate this in Development, initially for documenting purposes. I created my CM Package with no issues and wiped out the changes in Development, so now my Development mirrors Production.
Posts: 18 | Location: Tacoma, WA | Registered: August 20, 2019