TeamSite Web Interface

I want to have a custom interface for our CMS server. I have created an ASP page that has links and documentation on it and I want my users to see that page when they access the server. The problem is when I go to the cms server, it redirects me to the login page. Is there anyway that I can get a page to come up when I go to the root of my server? Basically what is happening when I go to http://cmsserver I get redirected to http://cmsserver/iw/webdesk/login I would like for it to either throw up the default.asp from IIS or if that is not possible an index.html page from Apache. Any ideas?

Edited by keithleslie on 08/28/02 10:30 AM (server time).

Find more posts tagged with

Comments

akshathp

What I understand out of the question is that you are trying to make your deafult.asp/index.html page as a deafult page whenevr a person logs into the server. Is that right? Please correct me if I am wrong.

If this is correct, then I would suggest to rather have a small CGI script and add an item in the drop down menu of TS UI. That way user would be able to see your content each time they hit on that option. Or you could also make it part of your workflow.

But I am not sure you can change the deafult page of TS UI. If the default page ahs to be changed, then I am assuming it would require lot of customization and also the manner in which TeamSite engine invokes the start.html page.
Hope this helps.

Akshat Pramod Sharma
Interwoven Inc.

keithleslie

Not exactly. What I have done is built a page that has links to documentation, whitepapers, etc about interwoven, in addition to that, it has links to the login. I want the CMS server to serve this page, but when I try to put it so I can access by going to http://cmsserver/index.html IW converts that url to http://cmsserver/iw/webdesk/login/. I want to stop it from doing that, so I can serve index.html off of the root of the server.

akshathp

OK. Since, TeamSite would always authenticate any hit in the server, I am not sure if this is feasible or not. However, if you have a webserver running on your CMS server, you could always serve this and any other html/asp content using a different port. For example: http:cmsserver.domainname.com:81

Hope this helps.

Akshat Pramod Sharma
Interwoven Inc.