SSL testing with OE DataServers

SSL Testing:
The Secure Sockets Layer (SSL) is a computer networking protocol that manages server authentication, client authentication and encrypted communication between servers and clients.

SSL-enabled DataServer operation:

With this feature DataServer components get the option of configuring DataServer client and server instance to require Secure Sockets Layer (SSL) client connections in remote DataServer configurations. User can maintain both SSL-enabled and non-SSL Transaction Server instances, but a given instance supports only one type of connection, either secure or non-secure.

To connect to an SSL-enabled OE DataServer component, Client and Servers must have access to a digital (public key) certificate (often called a CA Root Certificate) that can authenticate with the digital certificate used by the server, and the client must be configured to send SSL requests.

Distributed DataServer Configuration with ssl:

Dtaserver can connect to remote server using any of the below broker-

• DataServer applications using ProBroker

 OpenEdge client runs on a client machine (either in Windows or on UNIX) and can access a remote Windows/Unix server. Multiple brokers can be running simultaneously on one server machine. The client connects initially to the ProBroker executable by locating the host and port of the executing broker. It is then automatically reconnected to a DataServer established for it by the broker. Each executing broker can spawn a multitude of DataServer processes.

• DataServer applications using the Unified Broker

When using the Unified Broker framework, user needs to configure the DataServer by editing ubroker.properties file. This file stores configuration definitions for instances of many OpenEdge products.

When you use this file to configure the DataServers, you provide information that enables the host to start a broker that spawns the appropriate DataServer process (_msssrv.exe/_orasrv.exe). Each configuration definition contains the environment variable and property settings for a broker instance. The command-line utilities use this file to store, validate, and manage the configurations for these brokers. A single copy of this file maintains all supported broker configurations for each OpenEdge installation. The ubroker.properties file is read on startup of the AdminService process.

To perform these configuration tasks, you can use OpenEdge Management/ OpenEdge Explorer or manually edit the ubroker.properties file.

 Sections of ubroker.properties file:

Section	Description
UBroker.MS / UBroker.OR	Parent Group The parent entity of DataServer for MSS/ Oracle brokers. It defines default property settings for all of these broker instances.
UBroker.MS.mssbroker1 / UBroker.OR.orabroker1	Derived Property A sample property entity of a DataServer for MSS/Oracle broker instance. It defines default property settings for the broker instance named mssbroker1/orabroker1
Environment.mssbroker1 / Environment.orabroker1	A sample environment entity of DataServer broker instance. It defines environment variable settings that apply to the broker instance named mssbroker1 / orabroker1.

• DataServer applications using the Appserver Broker

It is similar to unified broker configuration but instaed of unified broker we'll use appserver broker.  

Steps to test datserver connection in ssl mode-

• Start the db in mutiuser mode: proserve <shema holder name> -S <service name or port number> -ssl
• for mss dataserver: Connect the schema holder and logical db: prowin32 -1 <schema holder name> -S <service name or port number> -ssl -db <dsn name> -ld <logical db name> -dt MSS -U <user id> -P <password>  -S <broker service name> -ssl
• for oracle dataserver: Connect the schema holder and logical db: prowin32 -1 <schema holder name> -S <service name or port number> -ssl -db <logical db name> -ld <logical db name> -dt Oracle -U <user id> -P <password>  -S <broker service name> -ssl