Nowadays the granulated versions of the middleware applications, whether it's Release version, Patch Sets, or a Bundle patch, is not typically located within the GUI interface (probably because it's often a nightmare to link the RCU and application versions to the rendering GUI page).
In order to validate the deployed version, I wanted to view the current version of OAM 11g (Oracle Access manager) that's currently deployed. The information for this can be location within two areas; the database and by using the OPatch utility.
Validate the OAM Database version
This one is simple. Simply log into the OAM user and execute the following SQL script, Select * from OAM_VERSION. This will provide you the database schema that the RCU executed., this includes the following:
- OAM Policy Store
- OAM Session Store
- OSTS Blob Store
- OAM Password policy
- OAM OAUTH Consent store
- OAM OAUTH token-lifecycle store
- OAM Session Stored procedures
Validate the OAM Application version
Depending on how many versions of OPatch you have on your server, this can be a little tricky though all-in-all, this is too pretty simple. When you deploy the middleware configurations when you create a new WLS domain, one of the OOTB functionalities that is deployed is opatch OPatch is a utility (basically a script) that allows you to search for versions. This is also ideal if you want to patch the Oracle software or even roll back versions.
To start off, you need to go to the middleware Home (MW_HOME). once you're there you then need to access the Oracle home within the MW_HOME and locate a directory called OPatch. It's likely to be something like this, '/home/oracle/Oracle/OAM11gR2PS2/OPatch' though if you're still struggling
you can execute the following command within a terminal window: find /* -name OPatch.
Once you've done that, run the following command with the parameters
./opatch lsinventory -details
The lsinventory will present a list of all the inventory items that opatch acknowledges. If your environment variables are set you should be able to see the Oracle fusion middleware applications. the
additional parameter, -details will provide you additional information of all the listed items
If done successfully, you will see the following line, 'OPatch detects the Middleware Home as "/home/oracle/Oracle/OAM11gR2PS2"'.
Scrolling down, you should see the line, Oracle IDM Suite 11.1.2.0.0, which states that the fusion
middleware applications is 11g R2 PS2. and Oracle Access Manager Server 11.1.2.2.0 which states that OAM 11gR2PS2 is installed
Issue: version is not applicable for current OPatch version.
If you're running the The OUI version is not applicable for current OPatch version. All the details can be located within the Oracle Support Document There you also have the patch URL on how to update the Opatch version.
- You also need to ensure that the $MW_HOME variable is set
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
Tags
Recent Posts
Monthly Activity
Group by date