|
|
4. Across Web Applications
Web Applications are the highest level of entity in a SharePoint deployment. When you deploy SharePoint you create a Web Application. This entity contains one or more site collections. Each web application has its own Web.Config file and host header definitions. Often Web Applications are used to separate major uses of SharePoint. Thus, an organization may have separate Web Applications for its Internet, Intranet, Extranet, and its Portal.
CorasWorks also crosses the barrier of Web Applications. The Breeze demonstration environment uses 4 different web applications for its Portal, Intranet, Extranet, and Workplace Administration. In this environment we have implemented a Single Sign–On system to make it work as one work environment. Yet, usually these four areas represent distinct barriers that aren’t easily crossed.
Below we’ll talk about an example of how you can see and publish information across these web application zones.
Publishing Approved Documents
In this scenario, the product team is working with documents in a review and approve process within the Intranet. The documents go through their internal process with appropriate approvals. The view below shows the user selecting the action to Publish the selected document. A copy of the document will then be published
to a Partner Extranet. The extranet is in a separate web application. You can
also see the documents that are published on the Extranet from within the Intranet. A similar scenario would be to publish documents from the Intranet to the Portal, perhaps with a separate review process for the group that controls that portal.
Click here to see the Product Working Document solution in Breeze.
|
|