K2 Blackpearl 4.6.10 Installation and Configuration with SharePoint 2013

1 Installation of K2

K2 Blackpearl Installation

-          Run K2 package Installer.

K2 Installation

Make sure MSMQ Feature from Server Features and Roles are installed as below.

-          Run K2 Blackpearl Setup Manager from the Path K2 Installation Package 4.6.10 -> k2 Blackpearl 4.6.10 (4.0…..) -> installation.

K2 blackpearl Setup Manager

-          Next -> Custom Installation

-          Please make sure that all are checked expect visual studio features

Check features

-          Set dB creator permission for the service account

-          Set administrator permission for the service account in SQL server configuration wizard and for the folder too.

-          Change smpt server settings.

          Now the configuration wizard will be running

g

-          Create new web application and a root site collection to activate k2 features on

                      -      Go to Central administration -> Apps -> manager app catalog -> create new app catalog site

Smart Forms Installation

Go to K2 Installation package 4.6.10 -> K2 SmartForms 4.6.10 -> Intallation -> setup.exe

-          Next -> next -> next -> finish

-          The configuration wizard will be running automatically

Control Pack Installation

-          Complete the same steps of configuration wizard as in SmartForms installation

K2 for SharePoint Installation

-          Go to K2 Installation Package 4.6.10 -> k2 for SharePoint 4.6.10 -> installation.

Start the Subscription Settings in Central Administration

To begin, open the SharePoint 2013 Central Administration page and click on System Settings.

On the System Settings page, in the Servers section, click on Manage services on server

Go to the Services on Server page.  Make sure that the status of Microsoft SharePoint Foundation Subscription Settings Service is listed as Started.

Configure the Subscription Settings service application by using Windows PowerShell

Before you begin, make sure that the user running the Windows PowerShell cmdlets has the following memberships on all databases that you will be using:

• db_securityadmin
• db_owner

Next, go to Start > All Programs.  Expand the folder MS SharePoint 2013 Products to reveal the SharePoint 2013 Management Shell program. 

Select SharePoint 2013 Management Shell with the Run as administrator option.

Run the following commands:

• Get and set the name of the managed account in the SharePoint farm to the $account for later use.

$account = Get-SPManagedAccount "<AccountName>"

Please note that "<AccountName>" is the name of the managed account in the SharePoint farm.

For example: $account = Get-SPManagedAccount domain\spFarmAccount

• Create an application pool for the Subscription Settings service application:

$appPoolSubSvc = New-SPServiceApplicationPool -Name SettingsServiceAppPool -Account $account

Create the Subscription Settings service application:


$appSubSvc =
New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPoolSubSvc
-Name SettingsServiceApp -DatabaseName <SettingsServiceDB>

Please note that
<SettingsServiceDB> should be the name of the Subscription Settings
service database.

For example:
$appSubSvc = New-SPSubscriptionSettingsServiceApplication -ApplicationPool
$appPoolSubSvc -Name SettingsServiceApp -DatabaseName SettingsServiceChauTeamDB



Create a proxy for the Subscription Settings service application:


$proxySubSvc =
New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication
$appSubSvc




Next, after running
the command lines above, you will need to verify that the Subscription Settings Service was successfully created on the server.

To do this, go to the SharePoint 2013 Central Administration page and click Application Management.




On the Application Management page, select the Manage service applications hyperlink.

On the Manage service applications page, make sure that the status of SettingsServiceApp is listed as Started

Next, you will need to go to the MS SQL Server to verify that, after running the command lines above, the database name was successfully created.





Finally, set permission from K2 WORKSPACE