Technics:Abo-System - Revision history

Admin at 08:28, 23 October 2015

2015-10-23T08:28:21Z

@@ Line 5: / Line 5: @@
 :*Microsoft SQL Server 2005 Management Objects Collection  (XMO)
-As far as possible the component language should meet the SQL Server language. For executing [[Enterprise_Edition:Subscription_Manager|subscriptions]] the '''xp_cmdshell'''-feature must be enabled.
+As far as possible the component language should meet the SQL Server language.
 The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.
-The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the [[Framework:Developer_mode#PowerUser|PowerUser's]] password must be set.
 You have to provide a '''[[Technics:CoPlanner_Win-Client#ClientConfig.xml|ClientConfig.xml]]'''-configuration file for the Abo-Executor.
 {| {{Bausteindesign1}}
@@ Line 27: / Line 34: @@
 :*maxAttachmentSizeInKB: The maximum attachment size in kB. If 0 or not available, then unlimited.
 :*mailSettings: [[Technics:E-Mail Settings|e-mail settings]]
 ==Architecture (Customizing)==

Admin at 07:50, 6 March 2012

2012-03-06T07:50:20Z

← Older revision		Revision as of 09:50, 6 March 2012
Line 65:		Line 65:
	These tables contain the result of the latest execution for each [[Enterprise_Edition:Subscription_Manager\|subscription]].		These tables contain the result of the latest execution for each [[Enterprise_Edition:Subscription_Manager\|subscription]].

	{\| ~~style=cellspacing~~="1" ~~cellpadding~~="5" ~~border="1" width=~~{{~~{breite\|100%}~~}}		{\| class="wikitable" width="100%"
	\|-		\|- {{Tabellentitel}}
	\|width="200pt" ~~style=background-color:#f6f6f6~~ \|~~'''''~~Column~~'''''~~		\|width="200pt" \|Column
	\|~~style=background-color:#f6f6f6 \|'''''~~Description~~'''''~~		\|Description
	\|-		\|-
	\|AboId		\|AboId
Line 81:		Line 81:


	{\| ~~style=cellspacing~~="1" ~~cellpadding~~="5" ~~border="1" width=~~{{~~{breite\|100%}~~}}		{\| class="wikitable" width="100%"
	\|-		\|- {{Tabellentitel}}
	\|width="200pt" ~~style=background-color:#f6f6f6~~ \|~~'''''~~Column~~'''''~~		\|width="200pt" \|Column
	\|~~style=background-color:#f6f6f6 \|'''''~~Description~~'''''~~		\|Description
	\|-		\|-
	\|AboId		\|AboId

Admin at 07:34, 19 July 2010

2010-07-19T07:34:47Z

← Older revision		Revision as of 09:34, 19 July 2010
Line 1:		Line 1:
	==Prerequisites==		==Prerequisites==
	The following components from the Feature Pack for SQL Server 2005 (even if a new version of SQL Server is used) must be installed on the CoPlanner ~~server~~ using the proper architecture (x86 resp. x86):		The following components from the Feature Pack for SQL Server 2005 (even if a new version of SQL Server is used) must be installed on the [[Technics:CoPlanner-Server\|CoPlanner Server]] using the proper architecture (x86 resp. x86):

	:*Microsoft SQL Server Native Client		:*Microsoft SQL Server Native Client
Line 30:		Line 30:
	==Architecture (Customizing)==		==Architecture (Customizing)==

	For each [[Enterprise_Edition:Subscription_Manager\|subscription]] defined in the CoPlanner client the CoPlanner ~~server~~ will create a SQL Server Agent job. Each job consists of a single T-SQL step which is executing the stored procedure ''dbo.ExecReportAbo'' passing the [[Enterprise_Edition:Subscription_Manager\|subscription]]’s ''COPSYS_ID'' as parameter.		For each [[Enterprise_Edition:Subscription_Manager\|subscription]] defined in the CoPlanner client the [[Technics:CoPlanner-Server\|CoPlanner Server]] will create a SQL Server Agent job. Each job consists of a single T-SQL step which is executing the stored procedure ''dbo.ExecReportAbo'' passing the [[Enterprise_Edition:Subscription_Manager\|subscription]]’s ''COPSYS_ID'' as parameter.

	The job will be executed according to the schedule, but can be also started manually in the CoPlanner client		The job will be executed according to the schedule, but can be also started manually in the CoPlanner client
Line 40:		Line 40:

	:*Determine the Abo-Executor’s path		:*Determine the Abo-Executor’s path
	In the default configuration the Abo-Excutor AboExecutor.exe is located in the AboExecutor directory in the CoPlanner ~~server~~ directory.		In the default configuration the Abo-Excutor AboExecutor.exe is located in the AboExecutor directory in the [[Technics:CoPlanner-Server\|CoPlanner Server]] directory.

	:*Determine the path to the configuration file [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]]		:*Determine the path to the configuration file [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]]

Admin at 07:31, 19 July 2010

2010-07-19T07:31:52Z

← Older revision		Revision as of 09:31, 19 July 2010
Line 5:		Line 5:
	:*Microsoft SQL Server 2005 Management Objects Collection (XMO)		:*Microsoft SQL Server 2005 Management Objects Collection (XMO)

	As far as possible the component language should meet the SQL Server language. For executing subscriptions the '''xp_cmdshell'''-feature must be enabled.		As far as possible the component language should meet the SQL Server language. For executing [[Enterprise_Edition:Subscription_Manager\|subscriptions]] the '''xp_cmdshell'''-feature must be enabled.
	The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.		The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.
	The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the [[Framework:Developer_mode#PowerUser\|PowerUser's]] password must be set.		The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the [[Framework:Developer_mode#PowerUser\|PowerUser's]] password must be set.
Line 18:		Line 18:
	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
	\|-		\|-
	\| <span style="color: darkblue;">'''Hint'''</span>  For using the abo-system you have to pay attention to the login information of the data source. The full functionality is available only, if the mode ''request login information'' is selected. In case of windows authentication the subscriptions run in the context of ''xp_cmdshell''.		\| <span style="color: darkblue;">'''Hint'''</span>  For using the abo-system you have to pay attention to the login information of the data source. The full functionality is available only, if the mode ''request login information'' is selected. In case of windows authentication the [[Enterprise_Edition:Subscription_Manager\|subscriptions]] run in the context of ''xp_cmdshell''.
	\|}		\|}

Line 30:		Line 30:
	==Architecture (Customizing)==		==Architecture (Customizing)==

	For each subscription defined in the CoPlanner client the CoPlanner server will create a SQL Server Agent job. Each job consists of a single T-SQL step which is executing the stored procedure ''dbo.ExecReportAbo'' passing the ~~subscription’s~~ ''COPSYS_ID'' as parameter.		For each [[Enterprise_Edition:Subscription_Manager\|subscription]] defined in the CoPlanner client the CoPlanner server will create a SQL Server Agent job. Each job consists of a single T-SQL step which is executing the stored procedure ''dbo.ExecReportAbo'' passing the [[Enterprise_Edition:Subscription_Manager\|subscription]]’s ''COPSYS_ID'' as parameter.

	The job will be executed according to the schedule, but can be also started manually in the CoPlanner client		The job will be executed according to the schedule, but can be also started manually in the CoPlanner client
Line 52:		Line 52:


	The stored procedure ''dbo.ExecReportAboInternal'' will be called using these values and the ~~subscription’s~~ id as parameter.		The stored procedure ''dbo.ExecReportAboInternal'' will be called using these values and the [[Enterprise_Edition:Subscription_Manager\|subscription]]’s id as parameter.

	===dbo.ExecReportAboInternal===		===dbo.ExecReportAboInternal===
Line 58:		Line 58:

	===Logging===		===Logging===
	Each subscription execution (started automatically or manually) will be logged in the following tables:		Each [[Enterprise_Edition:Subscription_Manager\|subscription]] execution (started automatically or manually) will be logged in the following tables:

	:*''dbo.tb_ExecReportAboLog''		:*''dbo.tb_ExecReportAboLog''
	:*''dbo.tb_ExecReportAboLogMsg''		:*''dbo.tb_ExecReportAboLogMsg''

	These tables contain the result of the latest execution for each subscription.		These tables contain the result of the latest execution for each [[Enterprise_Edition:Subscription_Manager\|subscription]].

	{\| style=cellspacing="1" cellpadding="5" border="1" width={{{breite\|100%}}}		{\| style=cellspacing="1" cellpadding="5" border="1" width={{{breite\|100%}}}
Line 71:		Line 71:
	\|-		\|-
	\|AboId		\|AboId
	\|Subscription ID		\|[[Enterprise_Edition:Subscription_Manager\|Subscription]] ID
	\|-		\|-
	\|AboName		\|AboName
	\|Subscription name		\|[[Enterprise_Edition:Subscription_Manager\|Subscription]] name
	\|-		\|-
	\|ExecTime		\|ExecTime
	\|Last subscription execution		\|Last [[Enterprise_Edition:Subscription_Manager\|subscription]] execution
	\|}		\|}

Line 87:		Line 87:
	\|-		\|-
	\|AboId		\|AboId
	\|~~SubscriptionID~~		\|[[Enterprise_Edition:Subscription_Manager\|Subscription]] ID
	\|-		\|-
	\|LineNr		\|LineNr
Line 116:		Line 116:
	''variable:=value''		''variable:=value''

	At present the only defined variable is AboName which returns the ~~subscription’s~~ name.		At present the only defined variable is AboName which returns the [[Enterprise_Edition:Subscription_Manager\|subscription]]’s name.

Admin at 09:22, 16 July 2010

2010-07-16T09:22:32Z

← Older revision		Revision as of 11:22, 16 July 2010
Line 46:		Line 46:

	:*Set the username and password the Abo-Excutor will use for connecting tot he CoPlanenr server		:*Set the username and password the Abo-Excutor will use for connecting tot he CoPlanenr server
	In the default configuration the [[Framework:Developer_mode#PowerUser\|PowerUser]] with an empty password will be used. The Abo-Executor is working with the accounts [[Framework:Developer_mode#PowerUser\|PowerUser]], [[Framework:Developer_mode#Partner\|partner]] and ~~Hersteller~~ only.		In the default configuration the [[Framework:Developer_mode#PowerUser\|PowerUser]] with an empty password will be used. The Abo-Executor is working with the accounts [[Framework:Developer_mode#PowerUser\|PowerUser]], [[Framework:Developer_mode#Partner\|partner]] and [[Framework:Developer_mode#Manufacturer\|manufacturer]] only.

	:*Set additional Abo-Executor parameters		:*Set additional Abo-Executor parameters

Admin at 09:21, 16 July 2010

2010-07-16T09:21:04Z

← Older revision		Revision as of 11:21, 16 July 2010
Line 46:		Line 46:

	:*Set the username and password the Abo-Excutor will use for connecting tot he CoPlanenr server		:*Set the username and password the Abo-Excutor will use for connecting tot he CoPlanenr server
	In the default configuration the [[Framework:Developer_mode#PowerUser\|PowerUser]] with an empty password will be used. The Abo-Executor is working with the accounts [[Framework:Developer_mode#PowerUser\|PowerUser]], Partner and Hersteller only.		In the default configuration the [[Framework:Developer_mode#PowerUser\|PowerUser]] with an empty password will be used. The Abo-Executor is working with the accounts [[Framework:Developer_mode#PowerUser\|PowerUser]], [[Framework:Developer_mode#Partner\|partner]] and Hersteller only.

	:*Set additional Abo-Executor parameters		:*Set additional Abo-Executor parameters

Admin at 09:17, 16 July 2010

2010-07-16T09:17:27Z

← Older revision		Revision as of 11:17, 16 July 2010
Line 7:		Line 7:
	As far as possible the component language should meet the SQL Server language. For executing subscriptions the '''xp_cmdshell'''-feature must be enabled.		As far as possible the component language should meet the SQL Server language. For executing subscriptions the '''xp_cmdshell'''-feature must be enabled.
	The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.		The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.
	The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the ~~PowerUser‘s~~ password must be set.		The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the [[Framework:Developer_mode#PowerUser\|PowerUser's]] password must be set.
	You have to provide a '''[[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]]'''-configuration file for the Abo-Executor.		You have to provide a '''[[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]]'''-configuration file for the Abo-Executor.

Line 46:		Line 46:

	:*Set the username and password the Abo-Excutor will use for connecting tot he CoPlanenr server		:*Set the username and password the Abo-Excutor will use for connecting tot he CoPlanenr server
	In the default configuration the PowerUser with an empty password will be used. The Abo-Executor is working with the accounts PowerUser, Partner and Hersteller only.		In the default configuration the [[Framework:Developer_mode#PowerUser\|PowerUser]] with an empty password will be used. The Abo-Executor is working with the accounts [[Framework:Developer_mode#PowerUser\|PowerUser]], Partner and Hersteller only.

	:*Set additional Abo-Executor parameters		:*Set additional Abo-Executor parameters

Admin at 08:25, 15 July 2010

2010-07-15T08:25:14Z

← Older revision		Revision as of 10:25, 15 July 2010
Line 5:		Line 5:
	:*Microsoft SQL Server 2005 Management Objects Collection (XMO)		:*Microsoft SQL Server 2005 Management Objects Collection (XMO)

	As far as possible the component language should meet the SQL Server language. For executing ~~abonnements~~ the '''xp_cmdshell'''-feature must be enabled.		As far as possible the component language should meet the SQL Server language. For executing subscriptions the '''xp_cmdshell'''-feature must be enabled.
	The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.		The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.
	The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the PowerUser‘s password must be set.		The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the PowerUser‘s password must be set.
Line 12:		Line 12:
	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
	\|-		\|-
	\| <span style="color: darkblue;">'''Hint'''</span>  ~~Das Abo~~-~~System ist nur für Berichte geeignet~~, ~~die mit der~~ CoPlanner Reporting Services Integration ~~auf reine CoPlanner~~-~~Daten zugreifen. Der Zugriff über den~~ Matrixbuilder ~~auf Olap-Würfel wird aus technischen Gründen nicht unterstützt~~, ~~da das Abo-System üblicherweise mit einem Serviceaccount ausgeführt wird und der Olap~~-~~Zugriff nur mit~~ SSPI ~~möglich ist~~.		\| <span style="color: darkblue;">'''Hint'''</span>  The abo-system is suited only for reports, which access CoPlanner data with CoPlanner Reporting Services Integration. The access to OLAP-cubes is not supported via Matrixbuilder, because the abo-system runs with a service account usually and the OLAP access is only available with SSPI.
	\|}		\|}

Line 18:		Line 18:
	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
	\|-		\|-
	\| <span style="color: darkblue;">'''~~Hinweis~~'''</span>  ~~Bei der Verwendung des Abo~~-~~Systems ist auf die Anmeldeinformationen für die Datenquelle zu achten~~. ~~Die volle Funktionalität (Berechtigungen für die Benutzer) ist nur dann gegeben~~, ~~wenn für die Anmeldeinformationen der Modus Zur Eingabe der~~ ''~~Anmeldeinformationen auffordern~~'' ~~eingestellt ist~~. ~~Bei ''Windows Authentifizierung'' wird das Abonnement immer im Kontext von~~ ''xp_cmdshell'' ~~ausgeführt~~.		\| <span style="color: darkblue;">'''Hint'''</span>  For using the abo-system you have to pay attention to the login information of the data source. The full functionality is available only, if the mode ''request login information'' is selected. In case of windows authentication the subscriptions run in the context of ''xp_cmdshell''.
	\|}		\|}

Line 30:		Line 30:
	==Architecture (Customizing)==		==Architecture (Customizing)==

	For each ~~abonnement~~ defined in the CoPlanner client the CoPlanner server will create a SQL Server Agent job. Each job consists of a single T-SQL step which is executing the stored procedure ''dbo.ExecReportAbo'' passing the ~~abonnement’s~~ ''COPSYS_ID'' as parameter.		For each subscription defined in the CoPlanner client the CoPlanner server will create a SQL Server Agent job. Each job consists of a single T-SQL step which is executing the stored procedure ''dbo.ExecReportAbo'' passing the subscription’s ''COPSYS_ID'' as parameter.

	The job will be executed according to the schedule, but can be also started manually in the CoPlanner client		The job will be executed according to the schedule, but can be also started manually in the CoPlanner client
Line 52:		Line 52:


	The stored procedure ''dbo.ExecReportAboInternal'' will be called using these values and the ~~abonnement’s~~ id as parameter.		The stored procedure ''dbo.ExecReportAboInternal'' will be called using these values and the subscription’s id as parameter.

	===dbo.ExecReportAboInternal===		===dbo.ExecReportAboInternal===
Line 58:		Line 58:

	===Logging===		===Logging===
	Each ~~abonnement~~ execution (started automatically or manually) will be logged in the following tables:		Each subscription execution (started automatically or manually) will be logged in the following tables:

	:*''dbo.tb_ExecReportAboLog''		:*''dbo.tb_ExecReportAboLog''
	:*''dbo.tb_ExecReportAboLogMsg''		:*''dbo.tb_ExecReportAboLogMsg''

	These tables contain the result of the latest execution for each ~~abonnement~~.		These tables contain the result of the latest execution for each subscription.

	{\| style=cellspacing="1" cellpadding="5" border="1" width={{{breite\|100%}}}		{\| style=cellspacing="1" cellpadding="5" border="1" width={{{breite\|100%}}}
Line 71:		Line 71:
	\|-		\|-
	\|AboId		\|AboId
	\|~~Abonnement~~ ID		\|Subscription ID
	\|-		\|-
	\|AboName		\|AboName
	\|~~Abonnement~~ name		\|Subscription name
	\|-		\|-
	\|ExecTime		\|ExecTime
	\|Last ~~abonnement~~ execution		\|Last subscription execution
	\|}		\|}

Line 87:		Line 87:
	\|-		\|-
	\|AboId		\|AboId
	\|~~Abonnement ID~~		\|SubscriptionID
	\|-		\|-
	\|LineNr		\|LineNr
Line 116:		Line 116:
	''variable:=value''		''variable:=value''

	At present the only defined variable is AboName which returns the ~~abonnement’s~~ name.		At present the only defined variable is AboName which returns the subscription’s name.

Admin at 07:42, 15 July 2010

2010-07-15T07:42:33Z

← Older revision		Revision as of 09:42, 15 July 2010
Line 8:		Line 8:
	The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.		The account of the process spawned by '''xp_cmdshell''' must be in the Report-Builder (or higher) role on the report server.
	The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the PowerUser‘s password must be set.		The stored procedure '''dbo.ExecReportAbo''' must be customized. In the default configuration at least the PowerUser‘s password must be set.
	You have to provide a '''ClientConfig.xml'''-configuration file for the Abo-Executor.		You have to provide a '''[[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]]'''-configuration file for the Abo-Executor.

	{\| {{Bausteindesign1}}		{\| {{Bausteindesign1}}
Line 42:		Line 42:
	In the default configuration the Abo-Excutor AboExecutor.exe is located in the AboExecutor directory in the CoPlanner server directory.		In the default configuration the Abo-Excutor AboExecutor.exe is located in the AboExecutor directory in the CoPlanner server directory.

	:*Determine the path to the configuration file ClientConfig.xml		:*Determine the path to the configuration file [[Technics:CoPlanner_Win-Client#ClientConfig.xml\|ClientConfig.xml]]
	In the default configuration the configuration file is located in the Abo-Executor-directory.		In the default configuration the configuration file is located in the Abo-Executor-directory.

Admin at 07:18, 15 July 2010

2010-07-15T07:18:43Z

← Older revision		Revision as of 09:18, 15 July 2010
Line 26:		Line 26:
	The following points have to be adopted:		The following points have to be adopted:
	:*maxAttachmentSizeInKB: The maximum attachment size in kB. If 0 or not available, then unlimited.		:*maxAttachmentSizeInKB: The maximum attachment size in kB. If 0 or not available, then unlimited.
	:*mailSettings: [[Technics:E-Mail Settings\|E-mail settings]]		:*mailSettings: [[Technics:E-Mail Settings\|e-mail settings]]

	==Architecture (Customizing)==		==Architecture (Customizing)==