Friday, May 27, 2011

 

Good ol' Oblix schema alive and well in OAM11g

While preparing to install OAM 11g, some of us were curious whether all the "ob..." attributes would remain intact or if they would be renamed with, for instance, an "orcl..." prefix. It struck one of my colleagues that the "ob" attributes would survive, if only to facilitate a workable upgrade path or to ease product development.

Whatever the case, it turns out that the attributes we've all known since the days of NetPoint and COREid have endured and can be found in OAM 11g after all.

During the LDAP pre-configuration step - one of the many, many steps required to get OAM installed - an LDAPConfigPreSetup.sh script is run, which performs the following:
The LDIFs used to load the schema into OID contain all the old Oblix attribute names, and in my environment they are found in [MW_HOME]/Oracle_IDM[x]/oam/server/oim-intg/schema.
This is great, because it should mean that we can count on using familiar attributes like obuseraccountcontrol and obusersessiontimeout.

Some things just don't change...at least not for another 6 months or so...

Labels: , ,


Friday, May 20, 2011

 

EM Console 11g shows OID is down

The Enterprise Manager Fusion Middleware Control 11g shows OID is down even though opmnctl shows OID is up.

The EM console also displays the following error while trying to access the OID instance under Farm_IDMDomain -> Identity and Access -> oid1 or while trying to create a wallet for SSL

Error:
Information Configuration settings are unavailable because /Farm_IDMDomain/OID_Inst/oid1 is down.


There could be 2 reasons for this.

Reason1:
The WebLogic user password used by EM Console to monitor OID is not correct.
Solution:
  • Go to the Farm drop down menu on the top of EM Console -> Agent Monitored Targets -> Configure . Verify if the Weblogic Monitoring User Name is correct and Change the WebLogic Monitoring Password to the correct password. Click Ok.
  • Check the OID status now.
Reason2:
The IP address/hostname given in the Middleware Administration Server Service URL is wrong.
The following is an example of the Middleware Administration Server Service URL
service:jmx:t3://your_ip_address:7002/jndi/weblogic.management.mbeanservers.domainruntime
Solution:
  • Go to the Farm drop down menu on the top of EM Console -> Agent Monitored Targets -> Configure .
  • Try using hostname instead of IP address. Click OK and verify the status of OID from EM console.


This page is powered by Blogger. Isn't yours?