Tag: sharepoint 2013

Manage Service Application with Windows PowerShell Commands

Windows PowerShell commands that you can use to manage service applications.

COMMAND
DESCRIPTION
Install-SPService
Installs the services in the farm. It runs once per farm.
Get-SPServiceInstance
Start-SPServiceInstance
Stop-SPServiceInstance
Operations related to managing the services instance for a specific server or the entire farm.
Get-SPServiceApplication
Publish-SPServiceApplication
Remove-SPServiceApplication
Set-SPServiceApplication
Unpublish-SPServiceApplication
Operations related to managing service applications deployed to a farm (such as sharing the specified local service application outside the farm).
Get-SPServiceApplicationProxy
Remove-SPServiceApplicationProxy
Add-SPServiceApplicationProxy
GroupMember
Operations related to managing service application proxies.
Get-SPServiceApplicationPool
New-SPServiceApplicationPool
Remove-SPServiceApplicationPool
Set-SPServiceApplicationPool
Operations related to managing the logical architecture of service applications.
Advertisements

SharePoint 2013 Admin Tips and Tricks

If you create the Service Application it creates virtual directories under the SharePoint Web Services in IIS. each Service application virtual directory is created by GUID (globally unique identifier).

VirualDirectory

NOTE An important point to remember is that a service application may have one or more databases. For example, the User Profile service application has profile, synchronization, and social tagging databases. Another example is the Search service application with crawl, link, analytics, and administration databases. The number of databases can quickly add up and be difficult to manage if you do not properly plan capacity.

One issue with confi guring service applications using the Confi guration Wizard is that the associated virtual directory databases can end up having a lot of GUIDs. For example, the name for one of the User Profi le databases could be User Profile Service Application_ProfileDB
_899fd696a54a4cbe965dc8b30560dd07.
Though this might be acceptable in some cases, generally, a more intuitive naming convention makes a more sense. One way to resolve this issue is to use the Manage Service Applications page in the Central Administration site to add service applications individually and then specify meaningful database names. The other alternative approach is to use Windows PowerShell to provision your service applications.
The following code snippet shows how you can provide a State Service service application using Windows PowerShell. Note how the SQL Server database and server name are specifi ed in the code.

New-SPStateServiceDatabase -Name “StateServiceDatabase” -DatabaseServer
“dhsqlsrv” | New-SPStateServiceApplication -Name “State Service Application”
| New-SPStateServiceApplicationProxy -Name ” State Service Application Proxy”
-DefaultProxyGroup > $null

Happy SharePointing …..!!! πŸ™‚ πŸ™‚ πŸ™‚

Variations in SharePoint 2013

SharePoint 2013 is packed with many outstanding features. Variations, which were introduced way back in SharePoint 2007, still find its existence in SharePoint 2013.

The upgraded or the new feature in SharePoint 2013 is the ability to translate via Microsoft Translator.

For this particular context, we will learn how to make use of variations in your site.

Prerequisites:

A SharePoint 2013 site with publishing feature

Machine Translation Service already activated.

Instructions on how to activate the Variations

When it comes to activating the variations, we will achieve our purpose by following steps:

  • Create a source site, which will be in English
  • Create a target site, which will be derived from Source site, which is in English.
  • For the purpose of the document, we are having target site in Hindi.
Verify the Variations Settings

Go to Site Settings.
Under Site Collection Administration, click Variations Settings.

img1

Variations Settings Page will show up.

Do the settings as per your need. For example, if you want to update the content on target site manually, you can set the options on this page accordingly.

Create the source variation

From the Site Collection Administration, click on Variation Labels

Following screen will be presented.

img2

We will start with Adding a label.

Click New Label.

Now, we are in process of creating a source variation from where the content will be derived. To do so, select the locale as English (United States). This will act as our default source language.

img3

Give any site location from where you want the source variation to be created. As already described on the page, you can also specify a top-level site by typing / in Variations home field.

img4

You can specify a label name and description for this particular label if needed.

img5

When the source variation is created, one can receive an e-mail notification (if configured) via the Label Contact field. You can enter any site member name here to direct the notification to the person.

img6

Click OK

One thing I liked more about SharePoint 2013, it makes the user comfortable from each of its notifications!! πŸ™‚

You will be comforted with following screen.

img7

The creation of the source variation will depend on the timer job settings. You can modify them under the Central Administration -> Monitoring -> Review Job Definitions

As a result, your source variation will be created.

img8

Creating target variations

Again, under Site Collection Administration, click on Variation Labels

Click New Label, you will be presented with following screen.

img9

In my case, I am going for a Hindi target variation. So, I’ve selected the same in Locale.

Click Continue.

Enter Label Name, description and display name, if needed.

Click Continue.

img10

It gives you an option to go for human translation, where you can create a XLIFF file and do the translation on the target site.

Click continue

img11

On this particular page, you can go for the page update settings as per your requirement.

Click continue

Review the label settings and click finish.

As a result, as soon as your timer job completes, you will be able to see the following screen.

img12

On the left pane, you are clearly able to see the two variations created.

For testing purpose, we will create a page on Source Site (English) and see if it is generated on Target Site (Hindi).

For the same, create a page on source site via the Gear menu.

img13

Check in and publish the page.

Go to Variation labels from Site Collection Administration.

Click on Create hierarchies.

From the ribbon menu,

Click Publish, under which click Update all targets.

img14

You will be able to see the above message.

As a result, you will be able to see a page in the target variation.

img15

That’s all! πŸ™‚