Configure the Application Server

Use the Server Manager to configure the Cherwell Application Server so that a 3-tier connection can be maintained between the CSM applications and the database. When configuring the Application Server, define:

• Connection: Which 2-tier connection the Application Server should use to connect to the CSM database. Typically, this is the connection named Cherwell, but CSM should detect the default connection name.
• Communication protocol: TCP or HTTP.
• Port: The communication port number through the firewall for the connection between Client applications and the Application Server, the default is 8001.
• Server name: Name of the Application Server.
• Security settings:The settings between the Client applications and the Application Server.

To configure the Application Server:

1. Open the Server Manager

   To open the Server Manager:

   1. Click Start>All Programs>Cherwell Service Management>Tools>Server Manager.

      The Cherwell Server Manager window opens.

      

2. In the Server field drop-down, select Cherwell Application Server.

   

3. Click the Configure button.

   The Server Configuration window opens.

   

4. Database: Select the connection the server should use to connect to the CSM Database.
   1. Connection: If the name of the correct database connection is not displayed, click the Ellipses button to open the Connection window and select an existing connection or configure a new connection.
5. Server: Provide the server information.
   1. Communication:
      • Communicate via TCP: Select this radio button to use Transmission Control Protocol (TCP) to communicate with the Application Server. This is the default.
      • Communicate via HTTP: Select this radio button to use HyperText Transfer Protocol (HTTP) to communicate with the Application Server.
   2. Port: Confirm the port number used by the client to connect to the Application Server. The default port is 8001. Do not change the port number, otherwise all clients have to specify a different port in the address for the server.
   3. Server name: The server name normally shows CherwellAppServer, although older installations might display TrebuchetServer.

      Note: In older CSM versions, this field could be customized. If this was done previously, then the field can be edited. Otherwise, the field is read-only.

   4. Security Mode:
      • None: Communications are neither encrypted nor signed. This is only recommended in development or test environments running within a company's secure intranet.
      • Encrypted: Communications are signed and encrypted using the specified server certificate. The encryption is at the transport level using SSL/TLS.
   5. Server certificate: If the Security Mode is set to Encrypted, click the Ellipses button to select a certificate to use for signing or encryption. In the window, select a certificate from one of several different certificate stores.
   6. Certificate authentication: If one of the certificate-based options is selected, specify if and how to authenticate the certificate.

      Note: Individual clients can override this to make their checks more or less enforced.

      • None: No validation of the server certificate is performed by the client. This is useful for self-signed certificates where authentication is not a concern. This validation still allows for encrypted communications if the Security Mode is set to Encrypted.
      • Peer Trust: The certificate is valid if it is in the client’s trusted people store.
      • Peer or Chain Trust: The certificate is valid if it is in the client’s trusted people store, or if the chain builds to a certification authority in the client’s trusted root store.
      • Chain Trust: The certificate is valid if the chain builds to a certification authority in the client’s trusted root store. This is the most secure option.
6. Click the Advanced tab.

   Refer to the table for descriptions of these settings.

   Note: These settings provide limiting values to help prevent Denial of Service attacks. Do not change these values without consulting the Cherwell Support team.

   

   Item	Description
   Maximum TCP Connections	Maximum number of client connections the server keeps pooled. Note: A client might maintain a connection that is not actively being used for a service request.
   Maximum Concurrent Calls	Maximum number of service requests the server handles concurrently. Service requests above this amount fail.
   Maximum Concurrent Instances	Maximum number of concurrent service instances. This value is used for testing purposes.
   Maximum Concurrent Sessions	Maximum number of concurrent sessions allowed to the server. Note: A client may have more than one session at a time. Trying to create sessions above this amount result in an error.
   Allowed Connection Backlog	Number of connections above the maximum that can be backlogged before the server returns an error.
   Maximum Buffer Pool Size	Maximum memory, in bytes, the server uses for buffering messages. Decreasing this amount can reduce the memory usage of the server but could cause a performance degradation on each service call.
   Maximum Message Size	Maximum size of a message, in bytes, the server or client consumes. Messages over this size are not be processed and result in an error. Note: The message header is included in this size.
   Maximum Message Depth	Maximum depth the client or server accepts when parsing an XML message. Depth refers to the nesting of XML elements in a message.
   Maximum Message Table Count	The message table contains the unique names of all elements and attributes in a message as it is consumed on the client or server. If this value is exceeded, an error message is generated. Reports with large datasets could require this setting to be increased.
   Maximum Content Length	Maximum number of characters allowed in XML element content.
   Maximum Array Length	Maximum allowed size of a message being received by the client or server.
   Enable Message Compression	When selected, compresses message traffic between the client and application server.
   Enable Service Performance Counters	When selected, allows the entire service behavior to be measured, which can then be used to diagnose performance. These can be found under the performance object when viewing with Performance Monitor (Perfmon.exe).
   Restore Default Value	When selected, restores all limits and options to their default values.