Technics:Reporting Services Integration - Revision history

ObsoleteAccounts: added 2 examples of how to define the ssrs coplanner datasource connection string

2022-03-04T10:17:08Z

added 2 examples of how to define the ssrs coplanner datasource connection string

← Older revision		Revision as of 12:17, 4 March 2022
Line 111:		Line 111:
	:*The folders on the report server won’t be created automatically.		:*The folders on the report server won’t be created automatically.
	:*The variable names are case-sensitive.		:*The variable names are case-sensitive.


			In the SSRS CoPlanner datasource the connection string has to be equal following the client connection string.

			2 examples:

			1) < COP10: Server=Rechnername;Port=8963;TcpFormatter=Native

			2) >= COP10: ServerUrl=http://Rechnername:8080/coplanner;

	===Data Processing Extension (DataExtension)===		===Data Processing Extension (DataExtension)===

Admin at 10:36, 22 February 2016

2016-02-22T10:36:41Z

← Older revision		Revision as of 12:36, 22 February 2016
Line 41:		Line 41:
	\|}		\|}

	An example for automatic installation for instance ~~SQL2008~~:		An example for automatic installation for instance SQL2012:

	<source lang="csharp">		<source lang="csharp">
	ReportServerConfigurator –autoinstall –autoquit –instance ~~SQL2008~~		ReportServerConfigurator –autoinstall –autoquit –instance SQL2012
	</source>		</source>

Admin at 10:36, 22 February 2016

2016-02-22T10:36:21Z

← Older revision		Revision as of 12:36, 22 February 2016
Line 9:		Line 9:
	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
	\|-		\|-
	\| <span style="color: darkblue;">'''Hint'''</span>  The BIStudioConfigurator application must always be made from the corresponding folder of reports. (SQL Server ~~2008 or~~ 2008R2 of the Reporting folder, SQL Server 2012 from Reporting.2012 folder and SQL Server 2014 from the folder Reporting.2014)		\| <span style="color: darkblue;">'''Hint'''</span>  The BIStudioConfigurator application must always be made from the corresponding folder of reports. (SQL Server 2008R2 of the Reporting folder, SQL Server 2012 from Reporting.2012 folder and SQL Server 2014 from the folder Reporting.2014)
	\|}		\|}

Admin at 15:00, 15 December 2015

2015-12-15T15:00:57Z

← Older revision		Revision as of 17:00, 15 December 2015
Line 9:		Line 9:
	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
	\|-		\|-
	\| <span style="color: darkblue;">'''Hint'''</span>  The BIStudioConfigurator application must always be made from the corresponding folder of reports. (SQL Server 2008 or 2008R2 ~~and older versions~~ of the Reporting folder, SQL Server 2012 from ~~SQL Server 2014 and~~ Reporting.2012 folder from the folder Reporting.2014)		\| <span style="color: darkblue;">'''Hint'''</span>  The BIStudioConfigurator application must always be made from the corresponding folder of reports. (SQL Server 2008 or 2008R2 of the Reporting folder, SQL Server 2012 from Reporting.2012 folder and SQL Server 2014 from the folder Reporting.2014)
	\|}		\|}

Line 52:		Line 52:
	[[Image:T_Screenshot des BiStudioConfigurator.jpg\|thumb\|center\|Technical, Screenshot des BiStudioConfigurator]]		[[Image:T_Screenshot des BiStudioConfigurator.jpg\|thumb\|center\|Technical, Screenshot des BiStudioConfigurator]]

	If several versions of Visual Studio exist, the ~~first~~ one with an report designer extension will be chosen ~~(in order 2005, 2008 and 2010~~. Using command line arguments other versions can be selected. Command line arguments can start with / or –.		If several versions of Visual Studio exist, the last one with an report designer extension will be chosen. Using command line arguments other versions can be selected. Command line arguments can start with / or –.

	{\| class="wikitable" width={{{breite\|100%}}}		{\| class="wikitable" width={{{breite\|100%}}}

Admin at 08:14, 16 June 2015

2015-06-16T08:14:12Z

← Older revision		Revision as of 10:14, 16 June 2015
Line 9:		Line 9:
	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
	\|-		\|-
	\| <span style="color: darkblue;">'''Hint'''</span>		\| <span style="color: darkblue;">'''Hint'''</span>  The BIStudioConfigurator application must always be made from the corresponding folder of reports. (SQL Server 2008 or 2008R2 and older versions of the Reporting folder, SQL Server 2012 from SQL Server 2014 and Reporting.2012 folder from the folder Reporting.2014)
	The BIStudioConfigurator application must always be made from the corresponding folder of reports. (SQL Server 2008 or 2008R2 and older versions of the Reporting folder, SQL Server 2012 from SQL Server 2014 and Reporting.2012 folder from the folder Reporting.2014)
	\|}		\|}

Admin at 08:13, 16 June 2015

2015-06-16T08:13:54Z

← Older revision		Revision as of 10:13, 16 June 2015
Line 6:		Line 6:

	The setups for both components must be executed with administrator rights.		The setups for both components must be executed with administrator rights.

			{\| {{Bausteindesign1}}
			\|-
			\| <span style="color: darkblue;">'''Hint'''</span>
			The BIStudioConfigurator application must always be made from the corresponding folder of reports. (SQL Server 2008 or 2008R2 and older versions of the Reporting folder, SQL Server 2012 from SQL Server 2014 and Reporting.2012 folder from the folder Reporting.2014)
			\|}

Admin at 06:58, 24 April 2015

2015-04-24T06:58:01Z

← Older revision		Revision as of 08:58, 24 April 2015
Line 220:		Line 220:
	<font color="#0000ff"><</font><font color="#a31545">Kerberos </font><font color="#ff0000">SPN</font><font color="#0000ff">=</font><font color="#000000">"</font><font color="#0000ff"></font><font color="#000000">"</font><font color="#0000ff">/></font>		<font color="#0000ff"><</font><font color="#a31545">Kerberos </font><font color="#ff0000">SPN</font><font color="#0000ff">=</font><font color="#000000">"</font><font color="#0000ff"></font><font color="#000000">"</font><font color="#0000ff">/></font>
	Defines the Service Principle Name (SPN) if Kerberos authentication must be used		Defines the Service Principle Name (SPN) if Kerberos authentication must be used

			===SQL Server Reporting Services 2012===

			For accessing to an CoPlanner data source with SSRS 2012 the transmission mode ''Native'' has to be activated. Therefore the connection settings have to be extended: ''server=vpcopsq2;port=8963;tcpformatter=native''

			{\| {{Bausteindesign1}}
			\|-
			\| <span style="color: darkblue;">'''Hint'''</span>  The chosen mode has to be adjusted both on server (SvrConfig.xml) and on client (ClientConfig.xml) and both have to come to an agreement.
			\|

Admin at 06:57, 28 August 2013

2013-08-28T06:57:54Z

← Older revision		Revision as of 08:57, 28 August 2013
Line 198:		Line 198:

	The TimeOut-Attribute controls the time, within the command has to be executed by the CoPlanner server. The EntryLifeTime–Attribut defines, within which time span a connection has to be reused by the data extension.		The TimeOut-Attribute controls the time, within the command has to be executed by the CoPlanner server. The EntryLifeTime–Attribut defines, within which time span a connection has to be reused by the data extension.


			{\| {{Bausteindesign1}}
			\|-
			\| <span style="color: darkblue;">'''Important'''</span>  During the installation you must set the TimeOut, otherwise it doesn't work. The TimeOut must be set at the BI-Studio in ''RSReportDesigner.config'' (C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies) and at the ReportServer in ''RSReportServer.config'' (C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer).
			\|}


	<font color="#ff0000">ConnectMaxAttempts</font><font color="#0000ff">=</font><font color="#000000">""</font>		<font color="#ff0000">ConnectMaxAttempts</font><font color="#0000ff">=</font><font color="#000000">""</font>

Admin at 06:47, 28 August 2013

2013-08-28T06:47:32Z

← Older revision		Revision as of 08:47, 28 August 2013
Line 109:		Line 109:
	===Data Processing Extension (DataExtension)===		===Data Processing Extension (DataExtension)===

	You can cinfugure the data processing extension in configuration file RSReportServer.config and RSReportDesigner.config. The following figure shows all kinds of options with their default values. All elements and attributes are optional, that means if they are missing, the default value will be taken.		You can cinfugure the data processing extension in configuration file RSReportServer.config and RSReportDesigner.config. The following figure shows all kinds of options with their default values. All elements and attributes are optional, that means if they are missing, the default value will be taken. If the server delivers an error message, like the figure below, the TimeOut Setting values must be increased.


			[[Image:T_Screenshot der Fehlermeldung.png\|thumb\|center\|Technics, Server Error Message]]



	<font color="#0000ff"><</font><font color="#a31545">Extension </font><font color="#ff0000">Name</font><font color="#0000ff">=</font><font color="#000000">"</font><font color="#0000ff">CoPlanner</font><font color="#000000">"</font> <font color="#ff0000">Type</font><font color="#0000ff">=</font><font color="#000000">"</font><font color="#0000ff">...</font><font color="#000000">"</font><font color="#0000ff">></font>		<font color="#0000ff"><</font><font color="#a31545">Extension </font><font color="#ff0000">Name</font><font color="#0000ff">=</font><font color="#000000">"</font><font color="#0000ff">CoPlanner</font><font color="#000000">"</font> <font color="#ff0000">Type</font><font color="#0000ff">=</font><font color="#000000">"</font><font color="#0000ff">...</font><font color="#000000">"</font><font color="#0000ff">></font>

Admin at 08:55, 18 December 2012

2012-12-18T08:55:23Z

← Older revision		Revision as of 10:55, 18 December 2012
Line 3:		Line 3:

	:*A server component which must be installed on the report server.		:*A server component which must be installed on the report server.
	:*A client component which must be installed on the client computer (only if report creating and editing using Business Intelligence Development Studio (BIDS) will be done).		:*A client component which must be installed on the client computer (only if report creating and editing using Business Intelligence Development Studio (BIDS) will be done). For SQL Server 2012 you will find a seperate component.

	The setups for both components must be executed with administrator rights.		The setups for both components must be executed with administrator rights.