|
|
6. Connecting Server Farms
In some circumstances SharePoint is deployed within an enterprise organization in separate server farms or on separate servers. Usually, the reason is to increase performance and avoid geographical latency. However, more often the real reason is the political makeup of organizations. Different divisions may have their own SharePoint instances/farms or separate subsidiaries. Or, some organizations may have a server for each office.
Alternatively, we have seen where organizations may want to bridge SharePoint 2007 farms with legacy SharePoint 2003 farms, or separate MOSS servers from WSS servers, or simply put confidential information on separate servers.
Leveraging the CorasWorks Data Integration Toolset you can integrate separate server farms. This is done by putting our external data adapters on the remote servers. These provide the information based upon their configuration. Then, in your local environment, your applications consume the information and work with it as if it was local.
In the Breeze environment, we have a separate server farm supporting the CorasWorks Sandbox. This is used for the external servers.
Confidential HR Documents
In this scenario, the HR department wants to keep its official HR documents very secure and under different records management policies. Thus, they process the documents within the Intranet. When they are finalized or they have fax or image copies they serve them on a separate secure and managed server.
The display below shows the information coming from the remote server (with Breeze our Sandbox). The display that we are seeing is within the HR Administrators dashboard. The ACL’s of the workspace secure access to this view. In addition, the consuming data connection is modular and actually resides within this workspace and thus cannot be accessed by anyone else except the authorized HR Administrators.
Click here to see this display.
|
|