When attempting to configure OIM, I would receive the following error when trying to connect to the Weblogic instance 'Check the SOA version compatibility'
INST-6193: The attribute JpsContextName in MBean com.oracle.sdp.messaging:Location=soa_server1,name=ServerConfig,type=SDPMessagingServerConfig,Application=usermessagingserver not found
Check the SOA version compatibility
SOLUTION
Turned out I did have an incorrect compatibility issue with WLS 10.3.6 and SOA 11.1.1.7 along with OIM 11.1.2.2.
The first step I took was to check that correct SOA database installation was correct. This was accomplished by querying the Oracle database and checking that the schema installed for both OIM and SOA was correct.
This was achieved by logging into SQLPLUS and running the following SQL command
select version,status,owner,upgraded from schema_version_registry;
This would then return for me all the owners along with the version numbers. you can see that OIM is 11.1.2.2.0 and the rest are 11.1.1.7.0... so far so good. The next thing I did was check that I had the correct SOA installed. This was my downfall because I accidentially downloaded 11.1.1.6 and not 11.1.1.7.
The best thing to do here is download SOA server version 11.1.1.7 (V37380-01) from the Oracle software cloud and proceed with the normal installation. If you select the same MW_HOME within the SOA installation, it will simply overwrite the version that's installed.
Here is a similar blog on HOW TO: install SOA server
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