Planning and Designing Service Application Architecture – Part 2

In previous post, I introduced to the new capabilities and functions of Service Applications in SharePoint 2010. Planning Service application architecture is one of processes that SharePoint admins need to know in order to optimize Service Application architecture effectively.

Before planning Service application architecture, you should take the understanding of new capabilities of Service Applications as well as how to use Default and Custom group. Why didn’t I mention how to configure each Service application? Because each Service application has its individual settings that serve your business solution so you should reach out them by learning how to configure particular Service applications from other resources after reading my topic.

In MOSS 2007, you only have SSP, which was called monolithic stuff, for serving functions for your business solution so you, as a SharePoint administrator, will not think of the concept of dependencies. Because of diversification of Service application box, some Service applications will be dependent on the other. For example, you need to deploy Social networking solution including People Search in your organization. You need to import user information in order to create the best use of People Search. Also as Enterprise Search, you should utilize it for your Social networking solution. One resource about Service application dependencies you should know is this post.

Business functions planning worksheet

After learning Service application dependencies, you start identifying your business requirement as well as Service applications, which are responsible for business functions. The big challenge you need to know is that you must translate business functions into Service application. Simple reason is that business user or customer couldn’t know capabilities of Service applications, thus they just show requirement. For example, when you gain to business requirements from customers, they won’t say any technique words because they don’t know them, thus they will think of common functions in corporate and then say you by business language. In order to translate from business languages into Service applications, you must learn fully capabilities and functionalities of Service Applications. Writing down business requirement in the following worksheet is to define Service applications effectively.

This worksheet is an example that you need to refer. As you see, business user expects a document management system as well as Search system in order to meet their goal. Service functionality in worksheet is capabilities of particular service application that you should write down in order to configure later. Or business users specify that they want to use more social computing functions, such as My Sites sites, you should think of User Profile Service application.

Define number of instance depending on isolated requirement

After making business functions planning worksheet, you start considering required isolation depending on department policy in your organization. For example, the Finance department needs to use separate Excel service for their required performance as well as they expect the financial analysis to be secured. In this case, you should create new service instance in order to meet finance department’s requirement.

For high-availability perspective, you should document critical services that must be performed. It means you should use multiple instances to ensure increased availability, which is a part of business continuity plan for your organization. Remember I’m talking about Service application, not entirely the huge Business Continuity Management picture. If you want to learn it, please refer to this post.

As a business functions planning worksheet, I strongly recommend writing down required isolation.

In my example, I wrote down following factors:

  • Service application: after identifying service applications, you can put them into this worksheet.
  • Critical: you need to define critical level including High, Normal and Low.  High level service is what you need to consider performance and security policy that your organization actually needs,
  • Number of instance: this column allows you to know the number of instances for each Web application.
  • Isolation: considering required isolation is to meet performance or security policy in your organization.

Also, you need to list proxy group that needs to associated with Web application by configuring Custom group.

Service application security policy

As I mentioned earlier that what I’m taking at this topic is level 100 ITPro, thus you should improve deeply knowledge at other great resources from SharePoint expert. Because I’m not SharePoint expert so I just share basics of SharePoint for everyone who is approaching SharePoint 2010, which is huge product for developer, administrator as well as business user.

When it comes to business requirement, the security policy is indispensable as I think personally. Next post, I will continue to share my thinking on security policy for Service application.

16:00 GMT +7 July 7, 2011

2 comments

Leave a Reply