SharePoint [architecture series]-SharePoint services and service application framework 02

In the previous article, we clarified some concepts of the SharePoint service through Q & A. Here we focus on two aspects:

Sharepoint Server Architecture Object ModelAndSome topology structures of SharePoint service applications

I. Sharepoint Server Architecture Object Model

 

Ii. Some topology structures of SharePoint service applications

The object model of the SharePoint service application supports different server farm environments. Here we will discuss some of the situations:

1. Single-Application Server structure (Single Application Server )

The service application instance in this structure runs on a server, and the client connects to the service application instance through the service application proxy. For example:

This structure has the smallest hardware requirement, but the disadvantage is that there is no redundancy. If only this server breaks down or stops working, the corresponding service will stop.

In a single server structure, this server is both a front-end web server and an application server. Therefore, the service is running both in the web server environment and in the application server environment.

2. Multiple application servers

In this topology, the server farm is expanded to have three application servers, but we only select two of them to run our service application ), the remaining server is used for other purposes, such as running another different service application.

This topology structure provides redundancy to some extent. If an application server is stopped, the service instances running on other servers can continue to process incoming service requests. Therefore, this topology structure is much more efficient than a single server structure.

Of course, if the remaining server does not have sufficient processing capabilities to respond to the customer's service requests, the user will feel the decline in service efficiency, but even so, it is always better than the shutdown.

For the purpose of expansion or maintenance, the server farm administrator can use the SharePoint management center or powershell to start and stop service instances on a server at any time.

It should be noted that this topology still uses only one service application logically, but this service application runs in a field environment with three servers.

3. Multiple web applications

This topology is characterized by several Web applications sharing the same service application.

When you want to share different Web applications, such as taxonomy or user profile) you need to use a common service application as a bridge to share data.

Note that the Web applications in this topology use the same service application proxy.

4. Multiple Service Application)

This topology is characterized by the fact that two service applications (A and B) of the same type run in the same phase server farm. The Web application in this server farm may establish a connection with any one of A or B. The establishment of this connection is determined by the server farm administrator.

The two service applications can be isolated to some extent. For example, they can use different databases to store related data of the application.

This topology is suitable for scenarios where data is not shared. For example, if a company has personnel departments and sales departments, the data between them must be kept confidential to each other, the sales department cannot retrieve the Personnel Archive information, but the Personnel Department cannot check the company's sales information. Therefore, when you need to create a search service application for these two departments) you need to use this topology. Each of these databases provides data support for each service application instance.

The corresponding web application in this topology uses different service application proxies to interact with their respective service applications.

Note that two different service applications run on the same server (same service instance.

 

5. federated Service Application)

This topology is used when a remote client calls a service application, that is, cross-field (Cross farm) Call.

 

For example, a large enterprise needs to establish enterprise-level search services. Such services cannot be solved by a single server, and require a high investment, therefore, the IT department will choose to centralize such enterprise-level search services, establish a separate service center, and provide enterprise-level search services to other departments or organizations. In this way, a server farm is dedicated to service bearer, so as to create highly intensive services (such as Web Analysis and Business Intelligence) for centralized sharing. This not only saves hardware investment and manpower investment, but also improves search efficiency and maintenance efficiency.

Note that this topology structure requires two-way mutual trust between the "field" that provides the search service and the customer "field.

Summary:

The SharePoint service still has many other topologies, such:

Multiple Service applications and multiple servers exist in multiple SharePoint farms ), one or more servers run one or more service application instances (service instances ). Service applications can also provide services, that is, a service application can call services provided by other service applications through the service application proxies ), in addition, this call can span different server farms. The SharePoint service application architecture provides great flexibility and scalability to meet different "service" needs of users.

Reprinted: http://www.cnblogs.com/wsdj-ITtech/archive/2012/12/06/2558938.html