Error When Starting SSL Enabled OAM Managed Server After Upgrade

If SSL is enabled for Oracle Access Manager Managed Servers, the SSL port for the Administration Server must be changed manually before starting the servers.

This issue occurs when you upgrade Oracle Identity Manager (OIM) and Oracle Access Manager (OAM) integrated environments. If the SSL port is not updated for the SSL enabled Oracle Access Manager Managed Server, the following exception is displayed when you start the Managed Server:

<Error> <Server>  <idmr2ps3> <AdminServer> <[ACTIVE] ExecuteThread: '11' 
for  queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>  
<303f1768-cdd2-4e0c-9b1e-564a32e22aa1-00000056> <1494577396454>  <[severity-value: 8] 
[rid: 0] [partition-id: 0] [partition-name: DOMAIN] >  <BEA-002606> <The server is unable to 
create a server socket for listening on  channel "DefaultSecure[iiops]". The address x.x.x.x 
might be incorrect  or another process is using port 7503: java.net.BindException: Address  already in use>  

The following exception is seen in the Administration Server log file:

<Error> <Server> <idmr2ps3>  <AdminServer> <DynamicJSSEListenThread[DefaultSecure]> 
<<WLS Kernel>> <>  <1880691887b793b2:4b6e5462:15ba94a4abd:-8000-0000000000000015>  <1493194022003> 
<BEA-002606> <Unable to create a server socket for listening  on channel "DefaultSecure". 
The address x.x.x.x might be incorrect or  another process is using port 7503: java.net.BindException: Address already  in use.> 

To resolve this issue, do the following:

1. Change the SSL port of the Administration Server from 7503 to another free port, for example, 7505, on the WebLogic Administration Console.
2. Edit the startManagedWebLogic.sh file located at DOMAIN_HOME/bin/ to change the port from 7503 to 7505.

In an OIM and OAM integrated environment, you must use different SSL ports for OIM Administration Server and OAM Administration Server.