A Secure Socket Layer (SSL) configuration references many other configuration objects. To help you make valid selections for the new SSL configuration before you create it, view information about existing configuration objects. Information about existing objects is also useful when you create a node scoped SSL configuration using the createSSLConfig command of the AdminTask object.
Before starting this task, the wsadmin tool must be running. See the Starting the wsadmin scripting client article for more information.
To use the information in this task effectively, familiarize yourself with the instructions in the Creating a Secure Sockets Layer configuration topic.
Perform the following task to create an Secure Socket Layer (SSL) configuration at the node scope:
<repertoire xmi:id="SSLConfig_1136652770753" alias="BIRKT40Node02SSLConfig" type="JSSE" managementScope="ManagementScope_1134610924357"> <setting xmi:id="SecureSocketLayer_1136652770924" clientKeyAlias="default" serverKeyAlias="default" clientAuthentication="false" securityLevel="HIGH" jsseProvider="IBMJSSE2" sslProtocol="SSL_TLS" keyStore="KeyStore_1134610924357" trustStore="KeyStore_1134610924377" trustManager="TrustManager_1" keyManager="KeyManager_1134610924357"/> </repertoire>
In this information ...Related concepts
| IBM Redbooks, demos, education, and more(Index) |