DB-WAN-Accel from SpeedyDB is World’s fastest Data Connectivity Solution for Wide Area Networks.
Home Call SpeedyDB Technologies. (604)465-1387 Print Printer Friendly Version

Configure Datacenter Compression Server (DCS)

Change Datacenter Compression Server (DCS) Service Account

After installation, Datacenter Compression Server (DCS) service runs under the Local System account which is suitable in most cases. To change the account under which the service runs, please follow the steps listed below:
  1. Launch the Services Control Panel and right click on SpeedyDB DCS (highlighted below).
    Change service account of the key component of DB-WAN-Accel ( WAN Accelerator for databases such as Oracle, SQL Server, DB2 and MySQL)
  2. From the menu, choose Properties. The SpeedyDB DCS Properties form will appear. Click to choose the Log On tab.
    Change SpeedyDB DCS account properties.
  3. Click to choose This Account and type in the desired account name and password.
  4. Click on the OK button to confirm the change.

Change Datacenter Compression Server (DCS) Settings

The settings of Datacenter Compression Server (DCS) are stored in DCS.ini which is a text file. This file was created using the specified parameters during the installation.

There are a number of sections in the file:
  • Network
    Network specifies network related parameters such as IP address and port number for DCS.
  • DatabaseServer1
    DatabaseServer1 section specifies the connection information of the first database server this DCS connects to.
    DatabaseServer2 section specifies the connection information of the second database server this DCS connects to.
    And so on.
  • Encryption
    Encryption section specifies data encryption related parameters.
  • Log
    Log section specifies how DCS log information for auditing and trouble-shooting purpose.
  • Metadata Cache
    Metadata Cache section specifies cache parameters for metadata.
  • Row Cache
    Row Cache section specifies cache parameters for rows (records).
  • Result Cache
    Result Cache section specifies cache parameters for groups of rows (records).
  • Compressed Cache
    Compressed Cache section specifies cache parameters for compressed cache.
  • Uncompressed Cache
    Uncompressed Cache section specifies cache parameters for uncompressed cache.
  • SpeedyDB Manager
    SpeedyDB Manager section specifies the user name and password for SpeedyDB Manager.

Network Section

There are 5 items in this section. The following is an example of the section contents
        [Network]
        DcsServer=
        DcsPort=3568
        NumberOfDatabaseServers=1
        AutoAssignBranchID=1 ;0: The ID for BCS must be assigned manually.  1: The ID for BCS will be assigned by DCS on the fly
        TimeOut=120
        
  • DcsServer
    The IP addresses to which DCS listens. The default value is an empty string, which means DCS listens to all IP addresses on the host computer.
  • DcsPort
    The port number to which DCS listens.
  • NumberOfDatabaseServers
    Number of database servers to which this DCS connects.
  • AutoAssignBranchID
    Specifies how the IDs of Branch Compression Server (BCS) are determined.
    1: DCS assign a unique ID for each BCS when the BCS connects to the DCS.
    0: The ID of the Branch Compression Server (BCS) must be predetermined using BCS.ini. See Configure Branch Compression Server (BCS) for more details.
  • TimeOut
    Specify how long (in seconds) DCS will wait for BCS to reconnect. If a BCS does not reconnect in the specified time period, DCS will close all the database connections of the BCS.

DatabaseServer1 Section

DatabaseServer1 section specifies the first database server to which this DCS connects.
DatabaseServer2 section specifies the second database server to which this DCS connects.
And so on.
NumberOfDatabaseServers parameter in Network section specify the number of database servers to which this DCS connects.

There are 3 items in this section. The following is an example of the section contents
        [DatabaseServer1]
        Server=speedydb-server
        Port=1433
        DatabaseType=SQLServer
        
  • Server
    Specify the IP address or host name of the database server.
  • Port
    Specifies the port number of the database server.
  • DatabaseType
    Specifies the database type of the database server. Valid values are "SQL Server", "Oracle", "DB2", and "MySQL" etc.
    Currently, only SQL Server is supported.

Encryption Section

There are 5 items in this section. The following is an example of the section contents
        [Encryption]
        
        ;0--Encryption Off   1--Encryption On
        EncryptionOption=0   

        ;must be full path
        PrivateKeyFile=C:\SslCert\server.pem         

        ;must be full path
        CertificateFile=C:\SslCert\server.pem         

        ;must be full path
        CAFile=C:\SslCert\ca.pem   ;must be full path

        ;must be full path.  If both CAFile and CAPath is empty, then a dummy certificate will
        ;be created by BCS or DCS
        CAPath=C:\SslCert          
        
  • EncryptionOption
    Valid value is 0 and 1.
    • 0: Encryption is off
    • 1: Encryption is on
  • PrivateKeyFile
    The private key file of the DCS in PEM format. In order to enforce the security, the file must be stored in a secure location that requires special permission to access it. A full path must be specified.
  • CertificateFile
    The file contains the certificates from your database servers.
  • CAFile
    The file that contains certificate chain all the way to the trusted Certification Authorities (CA).
  • CAPath
    The directory that contains certificates wiath a chain all the way to the trusted Certification Authorities (CA).
See Enable data encryption in DB-WAN-Accel for more details.

Log Section
This section is used to configure how Datacenter Compression Server logs activities for trouble-shooting purposes.

There are 19 items in this section. The following is an example of the section contents
        [Log]
        
        LogDirectory=C:\MsgDump
        CallingTreeDumpLevel=0

        IsLogSql=0
        IsLogDbSentMessage=0
        IsLogDbRecvMessage=0

        IsLogSpdSentMessage=0
        IsLogSpdRecvMessage=0

        IsLogSpdSentRawMessage=0
        IsLogSpdRecvRawMessage=0

        IsLogCallingTree = 0

        ExceptionFileName=Exceptions.bin

        SqlFileName="sqlDcs.txt"
        DbSentFileName="DbSentDcs.bin"
        DbRecvFileName="DbRecvDcs.bin"

        SpdSentFileName="SpdSentDcs.bin"
        SpdRecvFileName="SpdRecvBcs.bin"

        SpdSentRawFileName = "SpdSentRawDcs.bin"
        SpdRecvRawFileName = "SpdRecvRawBcs.bin"

        CallingTreeFileName="CallingTreeDCS.bin"
        
        
  • LogDirectory
    The directory for log files.
  • IsLogDbSentMessage
    1: Log all messages sent to database servers.
    0: No to log messages sent to database servers.
  • IsLogDbRecvMessage
    1: Log all messages received from database servers.
    0: No to log messages received from database servers.
  • IsLogSpdSentMessage
    1: Log all messages sent to Branch Compression Server (BCS) in uncompressed format. 0: Not to log messages sent to Branch Compression Server (BCS) in uncompressed format.
  • IsLogSpdRecvMessage
    1: Log all messages received from Branch Compression Server (BCS) in uncompressed format. 0: Not to log messages received from Branch Compression Server (BCS) in uncompressed format.
  • IsLogSpdSentRawMessage
    1: Log all messages sent to Branch Compression Server (BCS) in compressed format. 0: Not to log messages sent to Branch Compression Server (BCS) in compressed format.
  • IsLogSpdRecvRawMessage
    1: Log all messages received from Branch Compression Server (BCS) in compressed format. 0: Not to log messages received from Branch Compression Server (BCS) in compressed format.
  • IsLogCallingTree
    1: Log calling tree 0: Not to log calling tree
  • RequestFileName
    The file name used to log requests (log level 5).
  • ExceptionFileName
    The file name used to log exceptions.
  • SqlFileName
    The file name used to log SQL statements and stored procedures issued.
  • DbSentFileName
    The file name used to log messages sent to database servers.
  • DbRecvFileName
    The file name used to log messages received from database servers.
  • SpdSentFileName
    The file name used to log messages sent to Branch Compression Server (BCS) in uncompressed format.
  • SpdRecvFileName
    The file name used to log messages received from Branch Compression Server (BCS) in uncompressed format.
  • SpdSentRawFileName
    The file name used to log messages sent to Branch Compression Server (BCS) in compressed format.
  • SpdRecvRawFileName
    The file name used to log messages received from Branch Compression Server (BCS) in compressed format.
  • CallingTreeFileName
    The file name used to log calling tree.

Metadata Cache Section
This section specifies how metadata is cached. There are 4 items in the section. The following is an example of the section contents.
        NumberOfItems = 500000
        Memory = 40
        MemoryFullThreshold = 95
        MemoryEmptyThreshold = 80
        
  • NumberOfItems
    Number of items can be stored in Metadata Cache of the DCS.
  • Memory
    The memory allocated for "Metadata Cache" in mega bytes. In the above example, up to 40M will be allocated to Metadata Cache.
  • MemoryFullThreshold
    Specifies how full the Metadata Cache can get before we have to purge the less frequently used items from Metadata Cache. In the above example, if the memory usage of Metadata Cache reaches 90% of the allocated memory (40M X 90% = 36M), the DCS will start to purge the less frequently used items until the memory usage reaches ItemEmptyThreshold.
  • MemoryEmptyThreshold
    Specifies how empty the metadata cache should be purged to. In the above example, if the memory usage of Metadata Cache reaches 85% of the allocated memory (40M X 85% = 34M), the DCS will stop purging.

Row Cache Section
This section specifies how rows (records) are cached. There are 4 items in the section. The following is an example of the section contents.
        [Row Cache]
        NumberOfItems =   21600000
        Memory = 330
        MemoryFullThreshold = 92
        MemoryEmptyThreshold = 87
        
See Metadata Cache section above for the meanings of each item.

Result Cache Section
This section specifies how groups of rows (records) are cached. There are 4 items in the section. The following is an example of the section contents.
        [Result Cache]
        NumberOfItems = 7000000
        Memory = 40
        MemoryFullThreshold = 95
        MemoryEmptyThreshold = 80
        
See Metadata Cache section above for the meanings of each item.

Compressed Cache Section
When the memory usages of Metadata Cache, Row Cache and/ or Result Cache reaches the threshold specified by MemoryFullThreshold, the less frequently used items will be purged into Compressed Cache. If those purged items are reused, those items are put back into the corresponding caches (Metadata Cache, Row Cache, or Result Cache).
        [Compressed Cache]
        Memory = 360
        MemoryFullThreshold = 93
        MemoryEmptyThreshold = 88        
        
See Metadata Cache section above for the meanings of each item.

Uncompressed Cache Section
Uncompressed Cache is a temporary buffer for decompressing Compressed Cache items.
        [Uncompressed Cache]
        Memory = 50
        MemoryFullThreshold = 75
        MemoryEmptyThreshold = 55
        
See Metadata Cache section above for the meanings of each item.

SpeedyDB Manager Section
This section is used to configure the user name and password for SpeedyDB Manager (A tool used to monitor DB-WAN-Accel).

There are 2 items in this section. The following is an example of the section contents:
        [SpeedyDB Manager]
        UserName=SpeedyDB
        Password=SpeedyDB  
        
  • UserName
    User Name for SpeedyDB Manager.
  • Password
    Password for SpeedyDB Manager.
The UserName and Password in this section correspond to the User Name and Password on the form to follow.

A monitor for DB-WAN-Accel (the WAN Accelerator for SQL Server, Oracle, DB2, MySql etc).



Send comments on this page to support@speedydb.com
2006--2009, SpeedyDB Technologies Corporation, All rights reserved.