Web App URL access

[Reginald_D_Souz]

Had a question regarding accessing archived mails using Web app URL. I have two EV servers in a single site. user1 is archived by evserver1; user2 is archived by evserver2. Users can search archived mails by accessing the http://evserver?/enterprisevault.

My question is can user1 and user2 search archived mails using a single url pointing to the evsite http://evsite/enterprisevault so that users need not remember which server their mails are archived by. Evsite is a site alias which points to evserver1. User1 can search archived mails when accessing the evsite url. But when user2 or any user whose mails are archived by evserver2 try searching using evsite url they get an error "Failed to perform the search request" .

Message Edited by Reginald D'Souza on 05-27-200704:02 AM

[andra_christie]

Why don't you set the webapp url to just  /enterprisevault  - this looks at the SiteEntryID in the hidden msg and takes the last part, which is the EV site alias, and uses that to connect to the Directory Service and then does an directory lookup to find out which Vault Server hosts the Vault Store in which the user's archive resides.  Then it uses THAT server in the full WebAPP URL in constructs.

[Reginald_D_Souz]

Andra,

Forgot to mention that we have already set the URL in the site properties to <https>/Enterprisevault. We are using SSL. Despite having that it is still failing. The users are connecting using a https session.

Reg

[lmulcahy]

I have a similar requirement, with 3 x EV2007 servers (in "building blocks:" config), and a requirement for HTTPS connections to the Web Access app.

The default "/EnterpriseVault" URL will resolve to the correct EV server using the process decribed above, but this is via HTTP. Is there any way to obtain this same functionality via HTTPS?

The documentation implies a server must be listed explicitly .. what then is the best way to ensure seamless user access (via HTTPS) in a multi-EV server environment ?

[TonySterling]

You will want to set it to <https>/Enterprisevault mentioned above.  I think the release notes have a blurb about how to specify a port if you want to do that as well.

regards,

~ts