OAM 11R2 : T2P Process Fails While Moving Node Manager Configuration In Oracle Access Manager 11gR2
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Access Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Coloning fails with the error :
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://oam.example.com:7002: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090542]Certificate chain received from photond2.akamai.com - 192.168.24.48 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.; No available router to destination]
SEVERE : Oct 13, 2014 12:59:55 - ERROR - CLONE-20515 Unable to connect to AdminServer for domain(s) oamstag and eagdomain.
SEVERE : Oct 13, 2014 12:59:55 - CAUSE - CLONE-20515 The AdminServer for domains(s) oamstag and eagdomain was not running.
SEVERE : Oct 13, 2014 12:59:55 - ACTION - CLONE-20515 Bring up the AdminServer for each domain before running the t2p utility.
java.lang.Exception: Error while registering Node Manager with each domain. Check log for more details.
How to solve it.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms