SharePoint 2013 K2
Add item to list then add new item to same list using K2 Blackpearl workflow
Read Excel Using Javascript ActiveXObject
K2 Blackpearl Document Approval Workflow
Install the K2 for Reporting Services component
K2 Blackpearl System Key
Install k2 blackpearl software
At one stage wizard will ask enter licence key, here you can see System Key, this System Key you have to enter in the K2 Portal site and generate licence key.
K2 Blackpearl Training
K2 Blackpearl OVERVIEW OF KERBEROS
K2 blackpearl Installation prerequisite
The System Account Requirements topic in the K2 blackpearl Getting Started guide recommends the K2 Service account be granted “Local Administrator” rights on the server where K2 blackpearl is installed. These rights are necessary for a K2 blackpearl installation to function and are detailed in this KB article. These rights can be individually granted to a non-Administrator account when a security policy requires stricter security on application service accounts.
RUNTIME RIGHTS REQUIRED BY THE K2 ACCOUNTS
The K2 Service and Workspace accounts require access and rights to the following folders and registry keys: Folder or Registry Key | Account | Rights | Server |
%SYSTEMROOT%\temp | K2 Service | Full Control | K2/MOSS |
%COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12 | K2 Service | Write Access | MOSS |
%ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA | K2 Service | Full Control | K2/MOSS |
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCode\Logging | K2 Service | Full Control | K2/MOSS |
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\CONFIG | K2 Service | Modify | K2/MOSS |
%PROGRAMFILES%\K2 blackpearl\Host Server\Bin | K2 Service | Modify | K2 |
%SYSTEMROOT%\Temp | K2 Workspace (Web Application Pool) Account | Modify | K2/MOSS |
Granting these rights to the appropriate accounts will allow companies with strict security policies to avoid granting the K2 Service and Workspace accounts full administrative rights to the server.
If installing in a distributed environment, security rights on these folders and the registry key will depend on which components are installed on the server. The only folder listed above that is not directly related to the K2 blackpearl Server or Workspace components is the “%COMMONPROGRAMFILES%\Microsoft Shared\web WHITE PAPER: SECURITY AND KERBEROS AUTHENTICATION WITH K2 SERVERS PAGE 5
server extensions\12” folder, which is present only if SharePoint (WSS v3 or MOSS 2007) is installed. If SharePoint is installed on different server, the K2 Service account still requires rights to the folder on that server.
Note: Users deploying K2 Web Designer workflows to SharePoint need ‘Contributor’ rights on the SharePoint site collection. The MOSS/WSS Web Application Pool account requires Write access to %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\Layouts\Features and %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions \12\ISAPI and must be a local administrator on the server in order to log K2 blackpearl Server errors to the event log.
INSTALLATION RIGHTS
The account under which K2 blackpearl is installed requires an account in the local administrators group. This allows the “eventbus” and “eventbus error” message queues to be created as well as the event log source “K2 BlackPearl Server.”
The account under which K2 blackpearl is installed also creates the following Performance Counter registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\K2 [blackpearl] Server
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\K2 Server
Once these registry keys are present, the K2 service account will be able to write values to these performance counters without administrative privileges because the K2HostServer.exe application is a trusted application.
Other modifications during installation include the installation of program files, entries in configuration files, such as machine.config, and the creation of the K2 databases. These actions require administrator privileges.
For more information about installing K2 blackpearl, including setting up Kerberos and MSDTC for distributed environments, see the Getting Started guide available on the K2 Customer and Partner portal.
RIGHTS REQUIRED BY THE WSS/MOSS APPLICATION POOL ACCOUNT
The WSS or MOSS Web application pool account needs both db_DataReader and db_DataWriter rights on the WebWorkflow SQL database that is used for the K2 Web Designer in SharePoint sites. The Execute right is also need for stored procedures in this database. Without this access the K2 Web Designer will not function.