Urgent help require to configure an SSL incoming socket provider

Question

Hi,
We are using RIDC to integrate UCM with Portal application.
Also using SSL Communication for the same but we are unable to stablish a connection between portal and UCM.
We have filled the SSL provider's details as given below
Provider Name: SSL_Provider
Provider Description: For RIDC Test
Connection State: down
Last Activity Date: None
Provider Type: sslincoming
Provider Class: idc.provider.ssl.SSLSocketIncomingProvider
Provider Connection: intradoc.provider.SocketIncomingConnection
Server Thread Class: intradoc.server.IdcServerThread
Server Port: 16204
Request Client Authentication: Yes
Require Client Authentication: Yes
Keystore File Path: /ucmapp/wlserver_10.3/server/lib/DemoIdentity.jks
Alias: RIDCTest
Truststore File Path: /ucmapp/wlserver_10.3/server/lib/DemoTrust.jks
we are using the following Ports
Server Port = 16204
SSL Server Port = 16302
Intradoc Port = 9999
Somebody let us know if we are going somewhere wrong.
Thanks in Advance

Answer 1

Just to verify you do not have your own router/gateway correct? Your computer either connects directly into the wall or into a box provided by the ISP?
Router/gateways stop incoming requests. And if it is yours then you have to figure out how to configure it so it allows those requests through.
But presuming that you do not....
Again i wanna make it clear that nobdy is able to ping
my machine and i am also not able to ping any
ipaddress whether it be yahoo or anything else. But i
am able to access every site (ofcourse through
browser) and i am also able to use every application
which is using custom ports.
Get ethereal. Play with it a bit. Use your browser and capture what occurs so you know what is going on.
Then have someone ping you while running.
I suspect you will not see the ping packet.
What this means is that your ISP is blocking all incoming socket connection requests. You solution is ....
- Get them to open the ports up
- Get a different ISP.
The problem : nobdy is able to connect to the server
writen by me in java.
Also the client and the server are diferent. The
server waits for incoming client requests (using
sock.accept() ) while the client simply tries to
connect to server through the constructor
'Socket(ipaddress, port)'.Yes, but in one case your machine connects to something while in the other something connects to it.
One thing is clear from all this that the path to
server is not getting resolved whether i try to
connect to the server using my client or the browser
or any other application which tries to connect to an
ipaddress on a particular port.
Resolved? Resolution only occurs when you use a domain name. There is no resolution when an IP is being used. You are using an IP for all of your testing correct?