within Inetpub\wwroot\ wss\VirtualDirec tories\PortNo
Dont create a new application within IIS for
application. There is also no need to have your
application as Virtual Directory within the MOSS web
application. Then copy the web.config of _layouts
folder as the web.config for your application. You can
find layouts folder at $:\Program Files\Common
Files\Microsoft Shared\web server
extensions\12\ TEMPLATE\ LAYOUTS. Basically you can find
how to remove HTTPHanlders and HTTPModules added by
MOSS. Why we are removing these because they will try
to find your application within the database of MOSS.
So to avoid this, just remove them. Now you can add
any virtual directory level settings within the
web.config of your application. Other settings should
be placed within the web.config of MOSS.
Now after copying your application wihtin MOSS
application and restructuring your web.config, next
step is just copy dlls of your application within the
_app_bin folder of your MOSS web application. The bin
folder of your web application is of no use now:)
Similarly copy your resource files to
App_GlobalResources folder of your MOSS web
application.
Now just browse to your application as
http://servername: port/yourapplica tion/ and wulla it
will surely work. Since they are shareing same
application pool and application, user will remain
same for MOSS and your application. Similarly session,
cookies and other stuff will remain same means you
have same context.
BDC is for performing any action against your external
system or to fetch data from them. They dont provide
context sharing power.
Hope it will help u
Akif - akif.techie.ca 