WebSphere Application Server supports four ways of choosing the SSL configuration for an outbound connection: scope selection, direct selection, dynamic selection, and programmatic selection. Scope selection relies on the management-scope hierarchy, so the configuration defined at the most specific applicable scope is used. Direct selection names an SSL configuration for a particular endpoint. Dynamic selection maps outbound protocol, host, and port information to a configuration through the dynamic outbound selection mechanism. Programmatic selection is the application-level method, and it is the correct answer when the question concerns code that opens an outbound SSL connection.
With programmatic selection, application code calls the com.ibm.websphere.ssl.JSSEHelper API, for instance to set an SSL alias or a set of SSL properties on the running thread before the connection is made. The settings apply to outbound connections made on that thread, and the helper allows the properties to be cleared once the call completes. Because the application states its requirement explicitly at run time, this approach carries the highest precedence of the four, overriding whatever the administrator defined through scope, direct, or dynamic selection.
The remaining options describe administrator-side configuration rather than something an application implements, so none of them answers a question about application-level implementation.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit