Platform-managed SSL client connection points indicate SSL clients that rely on platform-specific SSL certificate stores to access the Internet using HTTPS. These are SSL clients that rely on no OpenEdge-specific management or features to access OpenEdge servers over the Internet. (Of course, where an OpenEdge client accesses an OpenEdge server over the Internet, it also relies on OpenEdge-specific features to do this.)
Similarly, platform-managed SSL server connection points indicate OpenEdge middleware that relies on platform-specific SSL key stores to manage SSL client requests from the Internet and pass them on to OpenEdge servers for processing. This OpenEdge middleware includes the WebSpeed Messenger and AppServer adapters that run on industry-standard Web servers (or Java Servlet Engines, JSEs) or, in the case of the Sonic ESB Adapter, that runs on the Sonic Enterprise Service Bus (ESB). Web server platforms and the Sonic ESB provide their own key store management.
The lightly shaded components in Figure 4 identify the client, middleware, and server components provided entirely by OpenEdge. Unshaded components, such as the .NET and Java Open Clients or the JDBC and ODBC SQL clients, rely on some OpenEdge-provided interface code to allow the otherwise non-OpenEdge clients to access OpenEdge servers. Other unshaded components, including the non-ABL SSL socket (client or server), Web service client, Web browser client, and Web server components, represent third-party components that are configured with no necessary functional elements from OpenEdge.
The darkly shaded components represent other non-OpenEdge-specific technologies for integrating OpenEdge applications with non-OpenEdge applications. The SSL support provided by OpenEdge has no connection (other than the standard SSL support) to any security features that might be provided by these integration technologies. For example, Web service client access to OpenEdge services provided by the Sonic ESB Adapter is entirely managed by the Sonic ESB, as is access by other ESB services and clients. Likewise, the SonicMQ BrokerConnect supports direct and Internet SSL access from ABL, but the security of Java Message Service (JMS) transactions between the SonicMQ BrokerConnect and SonicMQ is entirely managed by the SonicMQ JMS infrastructure.
The rest of this chapter describes how you can work with the components described in this architecture, and where you can go for more information. For more information on SSL and its basic components, see Public-Key Infrastructure (PKI).
