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'v installed DS 767 and also got the PushOk plug-in for the SVN source code control system. When I try to configure PushOk in DS I get the following message:
The following evironments do not have the required variable SCC_NAME defined or set: localhost, therefore Source Control capabilities will not be available for these environments. If you intend to use Source Control with these environments, please contact your administrator and correct this problem.
Is SCC_NAME meant to be entered as an environment variable or is it something within DS? Any help appreciated.
Tia HåkanThis message has been edited. Last edited by: Håkan,
The problem looks like you are trying to use the source control against your local dev studio server and not against a webfocus server.
Unless you do the same as a lot of people and just reconfigure localhost instead of creating a new environment is dev studio.
I do not know the Source control package that you are using but the ones I do require that the target being protected is correctly defined.
Check the configuration and make sure that what you want to control is correctly defined.
If you are not actually trying to protect localhost but rather other environments that have been set up in DS then you should simply be able to ignore the error.