Topic
  • 2 replies
  • Latest Post - ‏2012-12-11T09:00:37Z by SystemAdmin
SystemAdmin
SystemAdmin
3908 Posts

Pinned topic Apache 2.0.64 and WebSphere 6.1 integration confirmation

‏2012-12-05T16:51:21Z |
Hello EveryBody,

i have integrated Apache 2.0.64 and WebSpher 6.1 after completion of integration process restarting both the servers i see the following trace in the logs

Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - ERROR: lib_security: logSSLError: str_security (gsk error 408): GSK_ERROR_BAD_KEYFILE_PASSWORD
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - ERROR: lib_security: initializeSecurity: Failed to initialize GSK environment
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - ERROR: ws_transport: transportInitializeSecurity: Failed to initialize security
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - ERROR: ws_server: serverAddTransport: Failed to initialize security
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - ERROR: ws_server: serverAddTransport: HTTPS Transport is skipped
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - PLUGIN: Plugins loaded.
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - PLUGIN: --------------------System Information-----------------------
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - PLUGIN: Bld version: 6.1.0
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - PLUGIN: Bld date: May 12 2006, 19:32:38
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - PLUGIN: Webserver: Apache/2.0.64 (Win32)
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - PLUGIN: Hostname = XXXX-VM
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - PLUGIN: OS version 5.1, build 2600, 'Service Pack 2'
Wed Dec 05 08:34:54 2012 0000160c 00000fe8 - PLUGIN:

can some one please tell me whether i can say that the integration is success ful by seeing the log

thanks in advance
Updated on 2012-12-11T09:00:37Z at 2012-12-11T09:00:37Z by SystemAdmin
  • Sunit
    Sunit
    196 Posts

    Re: Apache 2.0.64 and WebSphere 6.1 integration confirmation

    ‏2012-12-06T13:48:09Z  
    Plugin is not able to set up the connection with Application Server's secure port because the public key of the SSL certificate used by the Web Container secure listener is not trusted by the plugin.

    You can either add the SSL certificate public key to the certificate store used by the plugin (kdb file) using ikeyman OR if you are using a managed server (federated) you can propagate the plugin and associated kdb file from WAS admin console.

    • Sunit
  • SystemAdmin
    SystemAdmin
    3908 Posts

    Re: Apache 2.0.64 and WebSphere 6.1 integration confirmation

    ‏2012-12-11T09:00:37Z  
    • Sunit
    • ‏2012-12-06T13:48:09Z
    Plugin is not able to set up the connection with Application Server's secure port because the public key of the SSL certificate used by the Web Container secure listener is not trusted by the plugin.

    You can either add the SSL certificate public key to the certificate store used by the plugin (kdb file) using ikeyman OR if you are using a managed server (federated) you can propagate the plugin and associated kdb file from WAS admin console.

    • Sunit
    Thanks Sunit...