![]() ![]() NOTE: You can ignore steps 1, 5, 6, and 8 since they are not needed on the IBM i. The steps to configure the web server plugin to accept SSL communications are listed here: To resolve your issue, IBM recommends the following steps be taken to enable the Web Server plugin to accept SSL/TLS communications. These errors are a direct result of the previous messages.ĮRROR: ws_common: websphereFindTransport: Nosecure transports availableĮRROR: ws_common: websphereWriteRequestReadResponse: Failed to find a transportĮRROR: ESI: getResponse: failed to get response: rc = 4ĮRROR: ws_common: websphereHandleRequest: Failed to handle request The following messages indicate no active secure HTTPS transport can be found. To run with SSL, additional products may need to be installed: 1) OS/400 Digital Certificate Manager (5722-SS1 or 5769-SS1, option 34) 2) Cryptographic Access Provider 5769-AC1 (40-bit), 5722-AC2 or 5769-AC2 (56-bit), 5722-AC3 or 5769-AC3 (128-bit) Secure communication between app server and plugin will NOT occur. IMPORTANT: If a HTTP transport is defined, it will be used for communication to the application server.ĮRROR: ws_server: serverAddTransport: Plugin will continue to startup, however, SSL transport :6003 did not initilize. Secure transports are not possible.ĮRROR: ws_server: serverAddTransport: HTTPS Transport is skipped. Secure transports are not possible.ĮRROR: ws_server: serverAddTransport: Failed to initialize security. Secure transports are not possible.ĮRROR: ws_transport: transportInitializeSecurity: Failed to initialize security. Thus, the secure HTTPS transport cannot be initialized.ĮRROR: lib_security: logSSLError: str_security (gsk error 202): Key database file was not found.ĮRROR: lib_security: initializeSecurity: Failed to initialize GSK environment. The following messages indicate the Web Server plugin's key database file was not copied to the web server keystore directory. The change causes the following errors are recorded in the plugins_root/logs/web_server_name/http_plugin.log file if the Web Server plugin is not properly configured to accept SSL communications. Beginning at IBM WebSphere Application Server v8.5.5, the WebSphere Web Server Plugin product is no longer redirecting HTTPS SSL communications to the HTTP IP transport if the WebSphere Web Server Plugin is not properly configured to accept SSL communications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |