Tuesday, January 01, 2013

Can't Talk to WebLogic Admin Server After Enabling SSL

When we enable SSL for WebLogic Admin server login for security reasons,  we may have issues when other nodes can't talk to Admin server.

Thus  any changes on console can't populate to other nodes in Weblogic cluster.

We used to create a new jdbc datasource on weblogic console,  the jdbc config will not be copied to rest of nodes due to this issue.

And you will see such error on weblogic .out files

<Jan 1, 2013 6:11:38 PM CST> <Warning> <oracle.jps.idmgmt> <JPS-01520> <Cannot initialize identity store, cause: javax.naming.ServiceUnavailableException: test.testdomain.com:7002; socket closed.>

<Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>

How to fix:
In Domain home
find startManagedWebLogic.sh 
finds  ADMIN_URL="http://test.testdomain.com:7002" 
which it should be ADMIN_URL="https://test.testdomain.com:7002" 

UCM Service Can't Start Due To Jdbc Temp Table

UCM service can't start and stay in "Admin" mode in WebLogic Console
From weblogic .out file ,we can see such error

java.sql.SQLException: !csJdbcTempTableExists,USERSTemp,Users
        at intradoc.jdbc.JdbcWorkspace.alterTable(JdbcWorkspace.java:1679)
        at intradoc.server.datastoredesign.DataDesignGenerator.alterTable(DataDesignGenerator.java:2075)
        at intradoc.server.datastoredesign.DataDesignGenerator.generateTable(DataDesignGenerator.java:255)
        at intradoc.server.datastoredesign.DataDesignInstall.configTableForComponents(DataDesignInstall.java:284)
        at intradoc.server.IdcExtendedLoader.dataStoreDesignConfigTables(IdcExtendedLoader.java:2551)
        at intradoc.server.IdcExtendedLoader.performDatabaseUpgradeTasks(IdcExtendedLoader.java:397)

It's quite possible there was hiccup when we create weblogic DataSource or mis-communication  somewhere among UCM cluster. The temp was not deleted after test

we need to drop it manually on DB end to fix the issue