Technics:CoPlanner-Server

The folder CoPlanner Server has to exist on that computer, which should act as Server. It contains some configuration files, which define variables, connection to clients etc. These have to be configured accurately

SysCommands.xml

You find this file in the Server-Directory. It contains information for system settings of CoPlanner. Please note in which language the SQL-Server is installed. If Setup is in German, the user does not have to intervene. If Setup, however, is in English, file „SysCommands.xml“ has to be deleted or it has to be renamed and after that file „SysCommands_EnSql.xml“ has to be renamed, which is in the Server-Directory as well.

SvrConfig.xml

This file defines features of CoPlanner Server. It is located in the Server-Directory.

<?xml version= "1.0" standalone="yes"?>
<SvrConfig.xml>
   <CopSettings>
      <Version>4</Version>
      <ConnectionString>Server=localhost;Initial Catalog=COP_BIKE;Integrated Security=SSPI;pooling=false</ConnectionString>
      <DataBaseName>COP_BIKE</DataBaseName>
      <PortNumber>8963</PortNumber>
      <FiscalYear>0</FiscalYear>
      <TcpFormatter>Bin</TcpFormatter>
      <ServiceName>copService</ServiceName>
      <TelnetDebugPort>6900</TelnetDebugPort>
      <DefaultLanguage>german</DefaultLanguage>
      <BackupPath>C:\temp\</BackupPath>
      <BackupRestoreLimitinMB>DE50FAULT</BackupRestoreLimitinMB>
      <WebAuthenticateUrl>http://copsupport.coplanner.com/licence/get_cop_lic_v3.php</WebAuthenticateUrl>
      <LicenceID></LicenceID>
      <SSPIPort>11000</SSPIPort>
      <ClientConnectionTimeOut>1440</ClientConnectionTimeOut>
      <EntitySecurity>true</EntitySecurity>
      <AllowNonPowerUserDeleteDimElementsWithData>false</AllowNonPowerUserDeleteDimElementsWithData>
      <SSPIServicePrincipalName></SSPIServicePrincipalName>
      <EventLogEntryLevel>ERROR</EventLogEntryLevel>
      <ServerLogPath></ServerLogPath>
      <IsAliveClientTypes></IsAliveClientTypes>
      <MultiThreadCommand>true</MultiThreadCommand>
      <OptimizeForCPUCount>4</OptimizeForCPUCount>
      <ProActiveCaching>true</ProActiveCaching>
      <SkipImportHistory>true</SkipImportHistory>
      <NTLogonTypes>INTERACTIVE|NETWORK|BATCH</NTLogonTypes>
      <CopSysIDStartOffset>0</CopSysIDStartOffset>
      <DynamicMode>false</DynamicMode>
      <MaxRows>300000</MaxRows>
      <MaxSvrLogFileSize>0</MaxSvrLogFileSize>
   </CopSettings>
   <SSASSettings>
      <Server>127.0.0.1</Server>
      <DataBaseName>cop_olap</DataBaseName>
      <Security>true</Security>
      <SplitCombinedObjects>true</SplitCombinedObjects>
      <ClientBasedLoad>false</ClientBasedLoad>
      <XmlaLoadActive>true</XmlaLoadActive>
      <UseRealElementIDs>true</UseRealElementIDs>
      <UseMultipleHierarchies>true</UseMultipleHierarchies>
      <MultiSelectFilterActive>false</MultiSelectFilterActive>
      <LoadMeasureFormatAndType>true</LoadMeasureFormatAndType>
      <ReplaceNullValues>false</ReplaceNullValues>
      <DimensionLoadMode>AsDimAndHierarchy</DimensionLoadMode>
      <LoadDimensionsByAlias>true</LoadDimensionsByAlias>
   </SSASSettings>
   <SSRSSettings>
      <ReportServerUrl>http://127.0.0.1/reportserver</ReportServerUrl>
      <ReportWebServiceUrl>http://127.0.0.1/reportserver/reportservice2005.asmx</ReportWebServiceUrl>
      <RootFolder>/CoPlanner/Reports</RootFolder>
      <UserFolder>/CoPlanner/User</UserFolder>
      <TempFolder>/CoPlanner/Temp</TempFolder>
      <SharedDataSourceReference>/CoPlanner/DataSources/CoPlanner</SharedDataSourceReference>
      <Parameters></Parameters>
   </SSRSSettings>
   <DBCon>
      <Stage>Server=localhost;Initial Catalog=COP_STAGE;Integrated Security=SSPI</Stage>
   </DBCon>
</SvrConfig.xml>

The following points have to be defined in area CopSettings:

Inscription	Description
ConnectionString	Server name of server, on which database is located Initial Catalog name of database User id name of the user, which is used to login on SQL-Server by CoPlanner Server (as standard, ID „sa“ should already exist). Alternatively, an user can or has to be set up with relevant rights on SQL-Server. Password password of the user Pooling to bring Restore Database (fix integrated in the development menue) into action, in Connectionstring Pooling has to be false there!
DataBaseName	name of SQL-Database
PortNumber	released and unused portnumber for the communication of CoPlanner Server with CoPlanner Clients
FiscalYear	it determines posting of financial year of the company to calendar year. It is calculated based on January. 0 means: none posting of financial year -1 means: start of financial year in December of previous year 1 means: start of financial year in February of the same year
TcpFormatter	it determines the mode of transmission between client and server. You can choose between „Bin“ for binary transmission and „Text“ for text transmission. The chosen mode has to be adjusted both on server and on client („ClientConfig.xml“) and both have to come to an agreement.
ServiceName	name of CopService
TelnetDebugPort	it is possible to establish a viewing window to CoPlanner Server with the aid of Telnet. This inscription determines portnumber for the connection of Telnet. The connection takes place by DOS-prompt (Start Run cmd). To start Setup please enter: telnet computer name portnummer (e.g. telnet hostname 6900) and click the button „Enter“.
DefaultLanguage	The default language of the server is adjustable with this setting (ML routine CoPlanner). The default setting is German. If for example English is used, in the actual tables those entries are stored, which are seized by means of „English Client Logon“. Settings for example in German are stored in the ML system table. All available languages are available in the documentation of the ML routine.
BackupPath	it determines temporary disk space for a database backup, which can be caused by a client. SQL-Server has to have rights of writing on the given directories. A network is not allowable, but it should refer to a local volume of the SQL-Server
BackupRestoreLimitinMB	maximum Size of db backup in MB.
WebAuthenticateUrl	link to evaluate CoPlanner Licence.
LicenceID	needs to be set. CoPlanner Server can not be started without a Licence ID.
SSPIPort	port for SSPI-Login communication.
ClientConnectionTimeOut	after the expiration the client session on the server is deleted.
EntitySecurity	With this inscription the company security can be deactivated. If there is no entry the default is set to true.
AllowNonPowerUserDeleteDimElementsWithData	defines whether non PowerUser can delete elements with data.
SSPIServicePrincipalName	Service Principal Name: Can be empty per default. Only in use in case of SSPI and double hop P.ex.: "cop/mycomputer.mydomain.com"
EventLogEntryLevel	it steers, which inscriptions are written in event log, it can be distinguished after severity code of errors Warning --> Warnings and errors (red and yellow Cop-Cubes) Error --> Only errors(red Cop-Cubes) None --> No entries
ServerLogPath	if this option isn't available or empty, the CoPlanner server folder will be used to store the file "Serverlog.txt". If a valid folder is entered, this folder will be used to write log file. If the folder isn't available, a message will be displayed and writing log file will be deactivated. The value "NoLog" deactivates writing log file too.
IsAliveClientTypes	entered client types send periodically "AliveCommands" to CoPlanner server. If the client sends no "AliceCommands" to the CoPlanner server for an extended period of time, the session will be deactivated. Following client types are valid: Excel, Windows, CubeWare, Web.
MultiThreadCommand	with this option the parallel access of Clients can be activated.
OptimizeForCPUCount	this option defines the number of simultaneous client requests. On default all CUPs will be used.
ProActiveCaching	with this option the "Tupel Caching" of CoPlanner cubes can be activated. This means, that interim results will be chashed.
SkipImportHistory	is this inscription on true, error messages will not be written to the histroy table.
NTLogonTypes	All listed NT logon types will be used in case of NT authentication. On default all tree types will be used. Following types are available: INTERACTIVE, NETWORK, BATCH
CopSysIDStartOffset	this offset will be added to the first created CopSysID. If there are several models in use, you avoid double CopSysIDs.
DynamicMode	activate dynamic reload.
MaxRows	maximum number of datasets send to the client.
MaxSvrLogFileSize	maximum size of server.txt. If the file will be greater it will be compressed and moved to a defined folder (archiv). Zero means no compression.

The following points have to be defined in area SSASSettings:

Inscription	Description
Server	name of Server, on which OLAP-Database is located. If ClientBasedOlap is in use, you have to insert the name of server or IP address. Following names are not valid: localhost, ., 127.0.0.1 or local.
DataBaseName	name of OLAP-Database
Security	is this inscription on true, security is actice. If there is no entry the default is set to true.
SplitCombinedObjects
ClientBasedLoad	is this inscription on true, the client will load data. Therefore parallel execution of queries is possible . Hint  The components required of server (ADOMD, XmlParser), have to be installed on each client.
XmlaLoadActive	is this inscription on true, structure data will be loaded by XMLA.
UseRealElementIDs	is this inscription on true, real OLAP keys will be used, under the premise that they are numeric.
UseMultipleHierarchies	is this inscription on true, alternative hierarchies of OLAP dimensions will be loaded and can be used (since SSAS 2005).
MultiSelectFilterActive	is this inscription on true, dimensions, used as filter, support multiselect.
LoadMeasureFormatAndType	with this option it can be declared, if connectors (c3, combined …) should be loaded directly at the Server start. This is not advisable at any Olap console, due to the first user does not have to await the loading time.
ReplaceNullValues	is this inscription on true, all null values will be replaces with 0 by the connector.
DimensionLoadMode	Defines the load mode of OLAP dimensions. Following entries are valid: AsDimension (default), AsDimHierarchy and AsDimAndHierarchy Siehe: Exkurs SSAS Einstellungen
LoadDimensionsByAlias	OLAP dimensions will be loaded by alias. Siehe: Exkurs SSAS Einstellungen

The following points have to be defined in the area SSRSSettings:

Inscription	Description
ReportServerUrl	(required) The report server’s virtual directory.
ReportWebServiceUrl	(required) SOAP endpoint for managing objects in the report server.
RootFolder	(required) Root folder for reports on the reportserver.
UserFolder	(optional) Folder for reports which will be created using the report assistant in the BI-Center. If this folder is missing or empty the root folder will be used.
TempFolder	(optional) folder for reports which will be created using the report assistant in the Analyzer. If this folder is missing or empty the root folder will be used.
SharedDataSourceReference	path and name to an existing data source on report server, which is used by the report assistent to create a nre report. Is this tag missing, the report assistant creates an embedded data source. The report builder can show no preview for reports with an embedded data source.
Parameters

The following points have to be defined in the area DBCon:

Inscription

Description

Stage

Server name of server, on which database is located Initial Catalog name of database User id name of the user, which is used to login on SQL-Server by CoPlanner Server (as standard, ID „sa“ should already exist). Alternatively, an user can or has to be set up with relevant rights on SQL-Server. Password password of the user Pooling to bring Restore Database (fix integrated in the development menue) into action, in Connectionstring Pooling has to be false there!

Further variables:
Variables can be used e.g. at imports. Import objects require a Connectionstring to establish e.g. a connection to a previous system database. It is recommended to define such Connectionstrings as variables. On this way some objects can be changed at once and changes can be carried out more quickly.

<add key="Variable name" value="Value or inscription of the variable"></add>

Exkurs SSAS Einstellungen

Der CoPlanner-Server bietet mehrere Möglichkeiten SSAS-Dimensionen zu laden. Im Folgenden werden die zulässigen Einstellungen aufgelistet.

DimensionLoadMode	LoadDimensionByAlias	Einstellung	Ergebnis
AsDimension	False
AsDimension	True
AsDimHierarchy	True
AsDimAndHierarchy	True

CoPlanner-Server als Dienst

It is possible to install CoPlanner Server as service. In this case it is important, that the CoPlanner Server as service is NOT operated with the „local system account“. A NT-User has to be used as account to grant a correct execution at OLAP-scanning. Therefore the following points have to be considered:

CopService.exe.config

<?xml version= "1.0?>
<configuration>
   <runtime>
      <legacyUnhandledExceptionPolicy enabled="true" >
   </runtime>
   <startup>
   </startup>
   <appSettings>
   </appSettings>
   <system.net>
      <mailSettings>
         <smtp deliveryMethod="Network" from="aboexecutor@coplanner.com">
            <network
               host="psad001.graz.coplanner.com"
               port="25"
               defaultCredentials="true"
               />
         </smtp>
      </mailSettings>
   </system.net>
</configuration>

This file contains information, which is read in at the start of Service by CoPlanner Server. They are located in the Server-Directory. Further information of e-mail settings.

CopServiceInstall.bat

To install CoPlanner as Service, only this file has to be started. It is located in the Server-Directory of CoPlanner. A console window appears and informs you about the status of installation.

Has a CoPlanner Server Service already been installed, you have to finish and to deinstall the old Service before you start the new installation. The deinstallation takes place by starting file CopServiceUnInstall.bat, which is located in the Server-Directory as well.

Install some CoPlanner Services on one computer

Some CoPlanner Services can be installed on one computer. Therefore in file „CopService.exe.config“ some features are necessary. Furthermore two CoPlanner Server folders will be required. Two CoPlanner Services are not allowed to refer to the same folder.

Settings in „CopService.exe.config“

For each Service a separate name has to be allocated in file „CopService.exe.config“. Therefore within the day „<appSettings>“ the following line can be added:

      <add key="SERVICE_NAME" value="copService_bike2"></add>

The item „value“ identified the name of constructed CopService.
To install the Services, for each Service file „CopServiceInstall.bat“ has to be carried out subsequently.

Example of a configuration

File „CopService.exe.config“ is located e.g. in folder „C:\Program Files\coplanner\server1“

<?xml version= "1.0?>
<configuration>
   <startup>
   </startup>
   <appSettings>
      <add key="SERVICE_NAME" value="copService_bike1"></add>
   </appSettings>
</configuration>

File „CopService.exe.config“ for the second CopService is located e.g. in folder „C:\Program Files\coplanner\server2“

<?xml version= "1.0?>
<configuration>
   <startup>
   </startup>
   <appSettings>
      <add key="SERVICE_NAME" value="copService_bike2"></add>
   </appSettings>
</configuration>

After adopting portnumber the relative Services can be installed with the aid of batch file “CopServiceInstall.bat”. Under Windows Services there are two independent Services.

Debug messages of Server can be displayed about the command of console:

telnet localhost 6900

or

telnet localhost 6901

CoPlanner Server as a console

It is possible to install CoPlanner as a console. In process the following points have to be considered:

CopServer.exe.config

<?xml version= "1.0?>
<configuration>
   <startup>
   </startup>
   <appSettings>
   </appSettings>
   <system.net>
      <mailSettings>
         <smtp deliveryMethod="Network" from="aboexecutor@coplanner.com">
            <network
               host="psad001.graz.coplanner.com"
               port="25"
               defaultCredentials="true"
               />
         </smtp>
      </mailSettings>
   </system.net>
</configuration>

This file contains information, which is read in at the start of Service by CoPlanner Server. They are located in the Server-Directory. For all available options CopService.exe.config.

Start of the Server as a console

The installation has finished by copying of Server-directory onto the computer. You only have to start file CopServer.exe. A console window appears. Here you can see which operations the CoPlanner Server is carrying out.

CoPlanner Server and 64 Bit Systems

The CoPlanner Server can be operated on 64 bit systems. The advantages are faster process cycle times and the possibility to use more than 1.3 Gb of memory

Requirements

The CoPlanner Server and Client needs the 64 bit components of the standard 32 bit components.

• Windows Server 2003 x64
• Net Framework 2.0 x64 with SP1
• XML Parser 4 with SP2
• XML Parser 6 x64
• AdoMD.Net
• SQL Server 2005 with SP2
• Analysis Server 2005 with SP2

Conversion of existing systems

SQL Server 2000 Database can be imported on SQL Server 2005 or SQL Server 2008 Systems.

bei DTS Packages (Data Transformation Services) and Analysis Server 2000 Databases (Olap) cannot be imported. The packages need to be recreated with the SQL Server Integration Services (SSIS). No downward compatibility is given from Microsoft.

Analysis services data bases can be ported. But rrors can occur and/or ported data bases can be limited in function or not to be used at all. Here we recommend a reconstruction of the data base.