Now that you have a working
knowledge of the fundamentals, it is time to put that knowledge to
work. In this section, you will learn how to operate all the knobs and
switches that enable you, as a SharePoint administrator, to do your
job. Your job encompasses everything from actually creating service
applications to managing their security and properties with the GUI or
PowerShell. Sounds like a grand time.
Creating a New Instance of a Service Application
You set up your farm and
included all the service applications needed to get it off the ground.
That was a great way to quickly get up and running; but now you are
ready for prime time, and HR is screaming for its own instance of the
Managed Metadata service application. They would like to name it
HR-Only Metadata. The following steps describe how you would create it
for them:
1. Open Central Administration.
2. In the Application Management section of the home page, click the link to Manage service applications.
3. Here you
can see all the service applications currently available in your farm.
In the Ribbon, click the New button and select Managed Metadata
Service, as shown in Figure 1.
4. For Name, enter HR-Only Metadata.
5. Confirm you have the correct database server listed.
6. For
Database Name, choose something that will help you identify it, like
HR_Only_Metadata_DB. (Remember that it is best to avoid spaces in a
database name.)
WHEN EVERYONE WANTS THEIR OWN MANAGED METADATA SERVICE
If other divisions in the company also request their own Managed Metadata service, you can use what Microsoft terms a partitioned service application,
which keeps data and processing separate despite being in a single
process and database. This is discussed in greater detail later in the
“Multi-Tenancy in SharePoint 2013” section.
NOTE If
you want to host this database, or any other database, on a different
SQL Server, you merely need to ensure that permissions are set up. Once
that is done, you can just enter the new server’s name. Typically, the
permissions you need are found in your farm administrator account. This
is the account you specified when you ran the SharePoint Products and
Technologies Configuration Wizard (the gray one) when the farm was
first configured. The SQL Server rights this account needs include
dbcreator and securityadmin on the existing or new SQL Server that you
are trying to use. In addition, the SQL Server needs to meet the
minimum SharePoint requirements for SQL Server.
7. Most of the
time you will choose the “Use existing application pool” radio button.
From the drop-down menu, select your default app pool, as shown in Figure 2.
NOTE For
optimal performance, the current best practice is to keep all your
service applications in one application pool. This may change as the
product evolves, but it makes the most sense for now. Application pools
consume a great deal of resources, and performance testing has shown
that you get the best results when all your service applications are in
one application pool.
8. At the
bottom of this dialog are two options regarding the content type hub
and reporting syndication errors. Leave these two options alone for
now.
9. The last
check box, “Add this service application to the farm’s default list,”
is checked by default. For clarity’s sake, they mean Default Proxy
Group. Leave it as is. Later in the “Managing Service Application
Groups” section you will learn how to change this setting after the
fact, if necessary.
10.
Leave all the other settings at their default and click OK. After the
service application is created, you will be returned to the Manage
service applications page.
