K2 Deployment - Custom SQL service broker

When using SQL Service broker is used with Stored Procedures you need to make sure the service instance user has the view definition permission on DB so that Stored procedures and views are loaded with proper Schema.


If not then following thing will happen.


your Stored Procedure parameters will always show as Required ( even if you have provided default value.)


Thanks

K2 Client Set Up - Error connecting to K2 Server

When installing K2 Client using set up in Windows machine after you have removed existing K2 client installation, if the Type of installation page is not showing during set up , do the following.


1. Go to Registry - start-> run-> regedit
2. HKEY_LOCAL_MACHINE - SOFTWARE - look for source code. if there is registry entry already there. Please remove and restart your machine. the Set up will ask for Type of installation page now.

K2 Blackpearl Roles Update or Refresh (Instantly)

The trick of all this is that K2 won't actually refresh its identity cache until it needs that identity again. Setting the ExpiresOn, etc. fields as mentioned above is only half the equation. The other half is to tell K2 you need that identity object which actually triggers the refresh.

You can force the identity cache to expire for a particular role by running the following SQL query on your K2 database:

update [Identity].[Identity] set
ExpireOn = '2013-01-01',
MembersExpireOn = '2013-01-01',
ContainersExpireOn = '2013-01-01'
where FQN = 'role_name';

where role_name is the name of the role you wish to refresh. To actually trigger the role refresh, execute the Get Role Users method in the UMUser SmartObject on the role you wish to refresh.

New Framework K2

You can configure K2 to support .net framework 4.0 by doing the tollowing:

Modifying the "K2HostServer.config" file located in c:\program files\k2blackpearl\hostserver\bin folder.
Add the following key to the section of the K2HostServer.config file:

add key="netfxversion" value="v4.0.30319"
Restart K2HostServer.exe
a. You will be running in .NET 4 host, but will still execute .NET 3.5 code.
b. Although you can utilize .NET 4 based code constructs and references, you will not be able to use WF4 activities at this time

Ref: http://www.k2underground.com/forums/t/13211.aspx

Using the SQL Service Broker

http://www.k2underground.com/blogs/johnny/archive/2010/08/04/k2-4-5-tip-of-the-day-using-the-sql-service-broker.aspx

http://www.astaticstate.com/2007/11/create-custom-blackpearl-smartobject.html

Installing K2 Blackpoint / Blackpearl in a one way trust environment

Installing K2 Blackpoint / Blackpearl in a one way trust environment you need to run the K2 server service account & application pool using an account from the ‘trusted’ domain. It is also recommended that you install K2 components using this account:

Note: It is recommended to install all K2 components using the K2 Service Account. Log on to the server as the K2 Service Account before installing.

However if you try you will get the following error:

“The K2 Setup Manager requires the logged on user to have domain user privileges to proceed”

As you are in a one way trust environment you cant easily give the required permissions (if at all) so the work around is –

“If you have a scenario where you have multiple domains, you can disable the Installer’s domain check. 1. Please browse to the directory where you are executing the installation files from. 2. Look for an configuration file called product.config. This file will reside in the installer directory. 3. Please edit the file and change the Domainusercheck from true to false as shown below. 4. Save the file and execute the setup.exe again.

setting key=”domainusercheck” value=”false”

source: K2underground

Forms authentication in K2 workspace

In ‘C:\Program Files\K2 blackpearl\WorkSpace\Site\web.config’

Look for and change the following lines – in all cases change the top entry to the bottom entry (obviously without the comments and ‘OD:’).

Line 17:

<add key="authenticationMode" value="Windows" />

Line 20:

<add key="DefaultSecurityLabel" value="K2" />

Line 101:

<membership defaultProvider="AspNetActiveDirectoryMembershipProvider" userIsOnlineTimeWindow="1600">

Line 110:

<authentication mode="Windows">

Save and close – not sure whether an iisreset is necessary.

Open Workspace.

Please note that there are still issues that we are aware of with SQLUM which we are in the process of sorting out.

Please refer the below link

http://www.k2underground.com/forums/p/6424/19945.aspx