.net barcode reader free Configuring the Application Discovery and Load Balancing Service Application in .NET

Painting Quick Response Code in .NET Configuring the Application Discovery and Load Balancing Service Application

Granting the consumer farm permissions to the Application Discovery and Load Balancing Service Application establishes a relationship between the farms and allows you to set permissions to other service applications as well You can manage the security for a service application using the SetSPServiceApplicationSecurity cmdlet In the next example, we retrieve a claims provider that provides claim information that relates to the server farm

PS >> >> >> > $claimsPrincipal = New-SPClaimsPrincipal -ClaimType ` "http://schemasmicrosoftcom/sharepoint/2009/08/claims/farmid" ` -ClaimProvider $claimprovider ` -ClaimValue "27ea4ca4-9a17-4a3a-b862-75dbe5a0f424"

In this example, we use the ClaimType parameter and specify a URI used for the farm identifier claim type We use the ClaimProvider parameter and specify the claims provider reference stored in the claimProvider variable Finally, we use the ClaimValue parameter and specify the consumer farm s GUID NOTE You can find the consumer farm s GUID by running the following command on the consumer farm: (Get-SPFarm)Id You can add the claims principal to a SPObjectSecurity object using the GrantSPObjectSecurity cmdlet In the following example, we add a new security principal containing a claims principal and grant the principal Full Control rights, which is the only permission level supported by the Topology Service Application

PS >> PS >> > $security = Get-SPTopologyServiceApplication | Get-SPServiceApplicationSecurity > Grant-SPObjectSecurity -Identity $security ` -Principal $claimsPrincipal -Rights "Full Control"

Finally, we update the Topology Service Application with the security principal using the Set-SPServiceApplicationSecurity cmdlet

PS > Get-SPTopologyServiceApplication | >> Set-SPServiceApplicationSecurity -ObjectSecurity $security

Once the Application Discovery and Load Balancing Service Application is configured, you can publish a service application

You can use the Publish-SPServiceApplication cmdlet to publish a service application In this example, we will publish the metadata service application, which will enable content types and terms to be accessible on the consuming farm

PS > Publish-SPServiceApplication ` >> -Identity (Get-SPServiceApplication -Name "MetadataServiceApp")

Next, we need to create a new metadata service application proxy on the consuming farm that connects to the published service application on the publishing

18:

farm Adding a remote connection requires the URI of the published metadata service First, we retrieve the URL of the Topology Service by typing the following command on the publishing farm:

PS > (Get-SPTopologyServiceApplication)LoadBalancerUrlAbsoluteUri https://rig8c3:32844/Topology/topologysvc

Then we use the Receive-SPServiceApplicationConnectionInfo cmdlet on the consumer farm to retrieve the URI of the published managed metadata service applications This example returns an object of type SystemUri

PS > $uri = (Receive-SPServiceApplicationConnectionInfo ` >> -FarmUrl https://rig8c3:32844/Topology/topologysvc | >> Where-Object {$_Name -eq "MetadataServiceApp"})Uri

Next, we create a new metadata service application proxy using the SystemUri object stored in the uri variable as value for the Uri parameter and add the new proxy to the default proxy group

PS > New-SPMetadataServiceApplicationProxy -Name "Metadata Service App Proxy" ` >> -URI $uri -DefaultProxyGroup

Finally, we grant permissions to the published managed metadata service application to allow the consumer farm to connect to it The metadata service application supports three different types of permissions: Read Access to Term Store, Read and Restricted Write Access to Term Store, and Full Access to Term Store The following example demonstrates how to set up the metadata service application permissions

PS PS >> >> >> PS >> >> PS >> PS >> > $claimProvider = (Get-SPClaimProvider -Identity System)ClaimProvider > $claimsPrincipal = New-SPClaimsPrincipal -ClaimType ` "http://schemasmicrosoftcom/sharepoint/2009/08/claims/farmid" ` -ClaimProvider $claimprovider ` -ClaimValue "27ea4ca4-9a17-4a3a-b862-75dbe5a0f424" > $security = Get-SPMetadataServiceApplication -Identity MetadataServiceApp | Get-SPServiceApplicationSecurity > Grant-SPObjectSecurity -Identity $security ` -Principal $claimsPrincipal -Rights "Read Access to Term Store" > Get-SPTopologyServiceApplication | Set-SPServiceApplicationSecurity -ObjectSecurity $security

We have now gone through the steps that are necessary to publish a service application from one farm to another, allowing the consuming farm to pull data from the managed metadata service application