SQL Reporting Services

In K2 blackpearl 4.5 the K2 Workspace Report Designer does not use the SSRS server.

SSRS integration is still supported for customers:

Who wish to use the SSRS server to expose reports in other contexts other than K2 Workspace or K2 Process Portals
Who wish to use other design tools and then import reports into K2 Workspace Report Designer

K2 blackpearl leverages the services available in SQL Server 2008, which provides the following features:

“Microsoft SQL Server 2008 Reporting Services (SSRS) provides a full range of ready-to-use tools and services to help you create, deploy, and manage reports for your organization, as well as programming features that enable you to extend and customize your reporting functionality.” (http://msdn.microsoft.com/en-us/library/ms159106.aspx)

For further details on deployment options: http://msdn.microsoft.com/en-us/library/bb522791.aspx

For further details on security: http://msdn.microsoft.com/en-us/library/bb522728.aspx

K2 for SQL Server 2008 Reporting Services

This component is now optional for all K2 blackpearl installations and can only be installed during a Custom K2 blackpearl installation, and will not install as part of the default installation configuration. K2 for SSRS (SQL Server Reporting Services) is selected from the components listing and is installed on the local machine.

When a user wants to direct the local machine to the SSRS server, this is done from the K2 Workspace Management Console.

Additional Configuration.

A Reporting Service binding of 'All assigned' is recommended when installing K2.

In order for users to browse the reports on the server, the following permissions must be configured:
- Server Properties => Permissions, add <DOMAIN>\Domain Users place a check in the box for the role System User
- Home Folder Properties => Permissions, add <DOMAIN>\Domain Users place a check in the box for the role Browser

In SQL Server 2008, SSRS uses Http.sys to host the Reporting virtual directories. Read the following article for a brief explanation of this: http://blogs.devhorizon.com/reza/?p=748

While infrastructure changes are required by K2, each environment is different and has its peculiarities which must be taken into account. Modifying the infrastructure could have unforeseen results if the changes are not appropriately understood or managed. Given the broad spectrum of underlying infrastructure utilized, it is recommended that a panel or committee with appropriate skill in each area concerned be assembled to outline the underlying infrastructure changes and gauge the impact of the required changes.