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.
As per TexasStingray's post it appears you are running the server as root - which is NOT a GOOD Idea.
However I don't think sticky bits[1] would help here as ROOT can create files anywhere and the sticky bit only stops others from deleting/changing your files in a particular directory.
I'd look at how the WF server is being started and try to ensure it's being started by iadmin.
If you are developing ANY applications under Projects in Developer Studio, the id that started the web application server is the id under which the files are created. We have WebSphere and it is always started under root. I worked with a different app server at my previous contract and it was root as well.
This has nothing to do with the id that starts the reporting server.
What you can try to do is, after creating the application directory from Projects or better yet create it from a Unix prompt or Data Servers (you can make it a project after), go to the Unix prompt and change the ownership to you and the permissions. To set the group sticky bit, do a chmod g+s on the directory.
I can't guarantee that will help but it can't hurt.