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.
New TIBCO Community Coming Soon
In early summer, TIBCO plans to launch a new community—with a new user experience, enhanced search, and expanded capabilities for member engagement with answers and discussions! In advance of that, the current myibi community will be retired on April 30. We will continue to provide updates here on both the retirement of myibi and the new community launch.
What You Need to Know about Our New Community
We value the wealth of knowledge and engagement shared by community members and hope the new community will continue cultivating networking, knowledge sharing, and discussion.
During the transition period, from April 20th until the new community is launched this summer, myibi users should access the TIBCO WebFOCUS page to engage.
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.