Connections
A connection is the means by which a CSM application connects to another tier of the CSM suite.
A client is a tier, a Cherwell Server is a tier, and the database is a tier.
CSM has two different types of connections that are used in different ways and from different places. Both types of connections are configured through the Connection Wizard:
|
|
|
For a new installation, configure the following three connections:
- Server connection: The Server connection is a configured direct-to-database (2-tier) connection between any Cherwell Server (primarily the Cherwell Application Server and the Cherwell Service Host.) and a CSM database. During the Server installation, you are prompted to create this connection which, by default, is named Cherwell.
- Browser connection: The Browser connection is a configured direct-to-database (2-tier) connection between the CSM Browser Applications and a CSM database. CSM Browser Applications use a different connection than the desktop clients because they run inside IIS, and the connection needs to work with the IIS security options. During the Portal and Browser Applications installation, you are prompted to create this connection which, by default, is (and should remain) named "Cherwell Browser."
- Client connection: A Client connection is a configured App Server connection (3-tier) that allows a user to connect to the CSM database through the Cherwell Application Server. Although users can manually configure this connection, we recommend that the system administrator configure the client connection as part of the Auto-Deploy configuration, and then push the client connection out to all users using the Auto-Deploy process. A client connection pushed out by Auto-Deploy is also referred to as an "Auto-Deployed Client connection."
The configuration steps vary by the type of connection. Typically, a system administrator configures all three connections during the installation process. To help with the configurations, CSM provides the Connection Wizard, which is launched automatically by the Installation Wizard during the Server and Browser/Portal Apps installations, and manually by the system administrator during the Auto-Deploy configuration.