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>
   <SvrSettings>
      <VERSION>4</VERSION>
      <DATAPROVIDER>SQL</DATAPROVIDER>
      <CONNECTIONSTRING>Server=localhost;Initial Catalog=COP_BIKE;Integrated Security=SSPI;pooling=false</CONNECTIONSTRING>
      <DATABASENAME>COP_BIKE</DATABASENAME>
      <LANGUAGE>DEFAULT</LANGUAGE>
      <PORTNUMBER>8963</PORTNUMBER>
      <OLAPSERVER>localhost</OLAPSERVER>
      <OLAPDB>COP_OLAP</OLAPDB>
      <OLAPCONNECTIONSTRING>Provider=SQLOLEDB.1;Persist Security Info=False;user id=sa;password=;Initial Catalog=COP_BIKE;Data Source=localhost</OLAPCONNECTIONSTRING>
      <OLAPAUTOPROCESS>NEIN</OLAPAUTOPROCESS>
      <WJ_VERSETZUNG>0</WJ_VERSETZUNG>
      <TcpFormatter>Bin</TcpFormatter>
      <Backuppath>C:\</Backuppath>
   </SvrSettings>
</SvrConfig.xml>

The following points have to be defined:

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
OLAPSERVER	Name of Server, on which OLAP-Database is located
OLAPDB	Name of OLAP-Database
OLAPAUTOPROCESS	Should OLAP-Database be worked up automatically by CoPlanner Server, if the SQL-Database has changed. Allowable inscriptions: YES NO
OLAPCONNECTIONSTRING	Provider Driver of data source, which should be used (standard inscription: SQLOLEDB.1) User ID User ID to login on data source (look above) Initial Catalog Database name of data source Data Source Server, on which data source is located
WJ_VERSETZUNG	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.
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
BackuppathFromCopServer	If SQL-Server and Cop-Server work on different machines, a path has to be indicated. With this path the Cop-Server has access (with rights of writing!) to device of SQL-Server, which was defined in Backuppath. If this path is not defined, Backuppath will be used as before. Example: Backuppath reads as follows „c:\copSqlBkups“. The name of BackuppathFromCopServer in the case, that the SQL-Server works on the computer called „TSCOP001“, is „\\tscop001\c$\copSqlBkups“, but the user, under which the COP-Server works, has to have rights of writing on c$ of the Server TSCOP001.

CoPlanner Server as Service

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>
   <startup>
   </startup>
   <appSettings>
      <add key="TCP_DEBUG_PORT" value="6900"></add>
      <add key="EXPATH" value="C:\temp"></add>
      <add key="DbCon_Stage" value="Server=copserver;Initial Catalog=COP_STAGE;Integrated Security=SSPI"></add>
      <add key="DbCon_Vorsystem" value="Server=erpserver;Initial Catalog=ERP;user id=sa;password=;"></add>
   </appSettings>
</configuration>

This file contains information, which is read in at the start of Service by CoPlanner Server. They are located in the Server-Directory. Two inscriptions, which are contained normally in this file, are:

Inscription	Description
TCP_DEBUG_PORT	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“.
EXPATH	This inscription describes which directory is the base directory of the Server. In the above mentioned example is that directory C:\temp. In this directory the following files and folders must contain: folder Reviews (with content) folder Report (with content) folder Transfer (with content) folder ReportTemplates (with content) file „SvrConfig.xml“ file „SysCommands.xml“ You find these files in the execution directory of CoPlanner Server. It is recommended to use this CoPlanner-execution directory. In this case leave the inscription as below mentioned free: <add key="EXPATH" value=""></add>

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.

A variable must start with DbCon_ in order that CoPlanner can identify it as such.

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

Inscription	Description
ENTITY_SECURITY	With this inscription the company security can be deactivated. If this inscription either does not exist or it exists in the following form: <add key="ENTITY_SECURITY" value="True"></add> the company security is active. You can deactivate it in this way: <add key="ENTITY_SECURITY" value="False"></add>
OlapSecurity	Is this inscription on true, the OlapSecurity is active, is the inscription on false, it is inactive. Does this inscription not exist in Config Folder, Security per default is active.
OlapLoadMeasureFormatAndType	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.
OlapUseMultipleHierarchies	Is this inscription on true, alternative hierarchies of OLAP dimensions will be loaded and can be used (since SSAS 2005).
OlapReplaceNullValues	Is this inscription on true, all null values will be replaces with 0 by the connector.
OlapMultiSelectFilterActive	Is this inscription on true, dimensions, used as filter, support multiselect.
OlapXmlaLoadActive	Is this inscription on true, structure data will be loaded by XMLA.
OlapClientBasedLoad	Is this inscription on true, data will be loaded by client. This allows a parallel processing of queries. Hint  The required components of the server (ADOMD, XmlParser) have to be installed at the client!!! Furthermore, you have to register the name or IP address of the OlapServer in the „SvrConfig.xml“.
LoadConnectorsOnStartUp	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. If LoadConnectorsOnStartUp is on true and OlapSec on false, the Olap-historical data will never be reloaded. Therefore a server command was implemented: OBJ_OBV_RELOAD_CONNECTORS It constrains a new structure of all connectors. Call is available about macro => NavAction => ServerCommand => OBJ_OBV_RELOAD_CONNECTORS.
EventLogEntryLevel	It steers, which inscriptions are written in event log, it can be distinguished after severity code of errors <add key="EventLogEntryLevel" value="Warning"></add> --> Warnings und Fehler (Rote und Gelbe Cop-Würfel) <add key="EventLogEntryLevel" value="Error"></add> --> Nur Fehler (Rote Würfel) <add key="EventLogEntryLevel" value="None"></add> --> Gar keine Einträge
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. Example: <add key="DefaultLanguage" value="german"></add>
ClientConnectionTimeOut	After the expiration the client session on the server is deleted.
MultiThreadCommand	With this option the parallel access of Clients can be activated. Example: <add key="MultiThreadCommand" value="true"></add>
GCCollectAfterClientDataCommand	After every ClientDataCommand the GarbageCollector releases unused memory. Example: <add key="GCCOLLECTAFTERCLIENTCOMMAND" value="True"></add>
ProActiveCaching	With this option the "Tupel Caching" of CoPlanner cubes can be activated. This means, that interim results will be chashed. Example: <add key="ProActiveCaching" value="true"></add>
EmptyCellsClientGenerated	The CoPlanner client generates empty cells, not the CoPlanner server. This improves performance in case of thinly populated matrices. Example: <add key="EmptyCellsClientGenerated" value="true"></add>
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" Example: <add key="SSPIServicePrincipalName" value="cop/mycomputer.mydomain.com"></add>
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. Example: <add key="IsAliveClientTypes" value="Excel|Windows"></add>
OptimizeForCPUCount	This option defines the number of simultaneous client requests. On default all CUPs will be used. Example: <add key="OptimizeForCPUCount" value="4"></add>
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 Example: <add key="NTLogonTypes" value="INTERACTIVE|NETWORK"></add>
ServerLogPath	Available at CoPlanner Server 9.1, Hotfix 2.1 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. Example: <add key="ServerLogPath" value=""></add> Valid values: No value <add key="ServerLogPath" value=""></add> Valid folder <add key="ServerLogPath" value="C:\temp\logs"></add> No log file will be written <add key="ServerLogPath" value="NoLog"></add>

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. "TCP_DEBUG_PORT" has to be adopted as well in order that Debug messages of the Server can be read on Telnet:

      <add key="TCP_DEBUG_PORT" value="6901"></add>

In addition, for each Server a separate portnumber has to be allocated in file „SvrConfig.xml“.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="TCP_DEBUG_PORT" value="6900"></add>
      <add key="EXPATH" value="C:\Programme\coplanner\server1"></add>
      <add key="SERVICE_NAME" value="copService_bike1"></add>
      <add key="DbCon_Stage" value="Server=copserver;Initial Catalog=COP_STAGE;Integrated Security=SSPI"></add>
      <add key="DbCon_Vorsystem" value="Server=erpserver;Initial Catalog=ERP;user id=sa;password=;"></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="TCP_DEBUG_PORT" value="6901"></add>
      <add key="EXPATH" value="C:\Programme\coplanner\server2"></add>
      <add key="SERVICE_NAME" value="copService_bike2"></add>
      <add key="DbCon_Stage" value="Server=copserver;Initial Catalog=COP_STAGE;Integrated Security=SSPI"></add>
      <add key="DbCon_Vorsystem" value="Server=erpserver;Initial Catalog=ERP;user id=sa;password=;"></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>
      <add key="TCP_DEBUG_PORT" value="6900"></add>
      <add key="EXPATH" value="C:\temp"></add>
      <add key="DbCon_Stage" value="Server=copserver;Initial Catalog=COP_STAGE;Integrated Security=SSPI"></add>
      <add key="DbCon_Vorsystem" value="Server=erpserver;Initial Catalog=ERP;user id=sa;password=;"></add>
   </appSettings>
</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.