Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Custom Menu Items
Kay
We are trying to using custom menu items outside of iw-bin with symbolic links. Setup Symbolic Link /iw-home/httpd/iw-bin/custom -> /iw-home/httpd/custom/iw-bin We have our scripts in the /iw-home/httpd/custom/iw-bin directory. We can get the webserver configured so that when we directly hit a script under that directory it runs, but will not run if called from teamsite as a custom menu item. We are using Apache & Teamsite 5.5.2 and we are running on Sun Microsystems Inc. SunOS 5.8 Question: Will this work? If so, How do we configure TeamSite to work?
Find more posts tagged with
Comments
tvaughan
Custom menu items, when executed from the TeamSite GUI, are wrapped in a cgi wrapper and passed a number of TeamSite environment variables (like vpath, user, role, etc).
If you can get your custom menu item to work from the TeamSite GUI, you should be able to get it to work from some other access point -- providing that you configure your other access point to provide your custom cgi with all the same cgi parameters it is depending on. In otherwords, you should be able to trick your custom menu item.
On the other hand, I think it would be much harder to get a cgi to work from some outside access point, and then try to "bring it in to the fold" by configuring it as a TeamSite custom menu item and expecting it to work.
Tom
james1
I thought that custom menu item CGI's have to be in the iw-bin directory itself, not in a sub-directory. So you could symlink the individual CGI's into the /iw-home/httpd/iw-bin directory, but you couldn't symlink an entire directory into it.
You should try symlinking an individual CGI file and see if that works.
Hope this helps.
-- James
--
James H Koh
Interwoven Engineering
Migrateduser
Just another thought... if you are having problems getting cgi's to work from symlinks it could be because iw-webd is set up to not allow following of symlinks from the <iw-home>/httpd directory:
from httpd.con.template:
<Directory "__IW_TS_HOME__/httpd/">
Order allow,deny
Allow from all
</Directory>
I have not tried this myself and modifying the httpd.conf.template is not supported, so be careful if you plan to change anything here.
I believe that the change needed would be:
<Directory "__IW_TS_HOME__/httpd/">
Options FollowSymlinks
Order allow,deny
Allow from all
</Directory>
After this change is made you would need to do an iwreset -ui to make the change take effect.
This will have the iw-webd server follow symlinks from anywhere under <iw-home>/httpd (which includes the iw-bin directory). Be aware that this introduces potential security problems if you are not carefule. I am also not sure that this will work however due to the fact that the iw_cgi_wrapper. cgi may be the limiting factor.
Please see the apache documentation for more info about FollowSymlinks and other directives:
http://httpd.apache.org/docs/mod/core.html#options