Oim 9.1.0.1 installation Jboss4.2.3.GA

Hi All,
I'm trying install oim 9.1.0.1 in jboss app serv here me stack
OS: oracle enterprise linux 5
JDK: sun jdk 1.6u10 64 bits linux
APPSERV: JBOSS 4.2.3.GA
DB: oracle 11gR1 64 bit linux
there are many exceptions in jboss server.log at installation time:
ERROR [XELLERATE.DATABASE] Class/Method: DirectDB/DBPoolManager encounter some problems: No ClassLoaders found for: oracle.jdbc.driver.OracleDriver
shall I copy ojdbc6.jar to JBOSS_HOME/server/deafult/lib??? as docs says if you use SQL Server???
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[Nexaweb]] Error loading org.jboss.web.tomcat.service.WebCtxLoader$ENCLoader@7f19efa7 com.nexaweb.loader.ClientLoaderServlet
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[Nexaweb]] Servlet /Nexaweb threw load() exception
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[Nexaweb]] Error loading org.jboss.web.tomcat.service.WebCtxLoader$ENCLoader@7f19efa7 com.nexaweb.loader.NexawebDataService
and many more ERRORS I think something is not configured maybe a CLASSPATH or maybe a something in Jboss installation... I following
http://download.oracle.com/docs/cd/E14049_01/doc.9101/e14046/install_config_jboss.htm#BABIDGFE
but I think this is not a correct installation guide
Thanks in advance

Hi Sri,
First Question:
Yes. You need to install first OIM 9.1.0.1 and then install OIM 9.1.0.2 Patch.
Second question:
Patchset 8484010
I will also suggest you apply the latest patch of OIM 9.1.0.2 version available: Patchset 13527893, version BP19.
Be aware: Contact your Oracle Support team and check until when you have OIM 9.1.0.2 support.
I hope this helps,
Thiago Leoncio.

Similar Messages

OIM 9.1.0.1 Installation stuck at "Finalizing virtual Product Data Registry

Oracle Database is installed on server and I will be connecting to that one while installing OIM
I installed WebLogic Server 10.3.3 on my machine,started Admin Server
Then I tried to install OIM 9.1.0.1.
But Installation is not getting complete.
Its stuck at this point.
Finalizing Virtual Product Data Registry
This Operation may take a few moments.Please wait.........
and below that there is a progress bar which is showing 100%
One more thing I would like to tell you that When I specify the location of jdk(i.e C:\Oracle\Middleware\jdk160_18), it gave me error
"The Selected JDK Version is not supported by Oracle Identity Manager"
Oracle isentity Manager may not function correctly if you continue installation with this unsupported version of JDK.
Do you want to poceed with this unsupported version.?
So I installed JDK 1.5 on my machine ,gave path of JDK1.5,It also gave the same error
Then tried with JDK 1.6,then SDK EE 1.6......but all gave the same errors.
So I finally I use the one came with WebLogic server i.e C:\Oracle\Middleware\jdk160_18
and on prompting of following error
"The Selected JDK Version is not supported by Oracle Identity Manager"
Oracle isentity Manager may not function correctly if you continue installation with this unsupported version o JDK.
Do you want to poceed with this unsupported version.?
I chosen Yes

What does the setup_weblogic.log says?
-Bikash

Error in OIM 9.1.0.1 Installation

Hi All,
I am trying to install OIM using the following configuration:
OS: Windows Server 2003 SP2
JDK: Sun jdk 6 update 10
Database: Oracle 10g (10.2.0.1.0)
OIM: 9.1.0.1
Applicaton Server: Oracle Weblogic 10.3/JBOSS 4.2.3 (I have tried on both)
But in the end of the installation, I am getting the following error:
"Oracle Identity Manager has found that EncryptConfiguration.bat failed" and no xlStartServer file gets created..
I did not get any error during schema creation.
However in encryptconfiguration.log file, I am getting "Path is Incorrect!!" in the last line.
I have already tried all the options that have been posted for the same type of error but nothing helps.
Please let me know if anyone has idea about the same.
Thanks
Gaurav

Can you check whether path variables is set in your system under System Variables like Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;

OIm 9.1.0.1 installation in Weblogic

Hi,
I am installing OIm9.1.0.1 on linux5.4,weblogic10.3.0,database 11g,jdk1.6.0_21
I have unchecked Automatically aquire lock option in development mode.
But installation failed and when I checked the log I got below error:
[ant] Exiting /u01/app/serveroim/xellerate/setup/weblogic-setup.xml.
BUILD FAILED
/u01/app/serveroim/xellerate/setup/setup.xml:447: The following error occurred while executing this line:
/u01/app/serveroim/xellerate/setup/weblogic-setup.xml:308: weblogic.management.ManagementException: [Deployer:149163]The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using "Automatically Aquire Lock and Activate Changes" in the console, then the lock will expire shortly so retry this operation.
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)

Hi,
Were you able to resolve this? I am running into same situation.
Installing OIM 9101 on WebLogic 10.3.0 in Production mode.
"Automatically acquire.." option is disabled (grayed out ) in production mode. It is set to false.
Any ideas?
Thanks

OIM 9.0.3.1 INSTALLATION -- DB ERROR

Hi,
I get this error towards the end of the installation program on Windows.
Following Error occured during schema creation connectedError loading database scriptC:\Documents and Settings\azaidi\Desktop\OIM9031\installServer\Xellerate/db/oracle/xell.sqlPlease contact your DBA!ORA-06550: line 1, column 7: PLS-00905: object SYSTEM.PIN_OBJ is invalid ORA-06550: line 1, column 7: PL/SQL: Statement ignored [2/22/08 7:25 PM]
Previous messages in this forum say that I should run the prepare_db_xell script.
Heres what I did:
Created a new Database called oim. Created a new user sysadm in the sql console. Granted permissions to this new user. Increased java_pool_size to 60M (diagnostic dashboards test needs this). Infact the diagnostic dashboard test passes the oracle database. The script also runs fine and the log shows one error (table or view does not exist). The installation instructions says that error can be ignored. Rest is all good in the script logs.
Can someone tell me what steps Iam missing ? If you could list the steps to prepare the DB it'd be great.
thanks !

Tried it. No user exists. Just a database instance called "oim".
then I ran the script. script ran fine. no errors. only one warning "table or view does not exist". the installer documentation says this warning can be ignored.
then i ran the installer and got the same error.

OIM 9.1.0.1 installation on Websphere 7

Hello,
Does any one have experience in installing OIM 9.1.0.1 on Websphere 7 instead of WAS 6? Do you foresee any issues during the installation? Our plan is to install OIM 9.1.0.2 BP 18 on WAS 7 (fresh installation).
Appreciate any feedback on this.
Thanks!

Check the certification matrix.
You can refer below links:
http://docs.oracle.com/cd/B31081_01/idmgr/b28762/install_config_websphere.htm
http://docs.oracle.com/cd/E10391_01/doc.910/e10371/websphere_cluster.htm
Re: OIM with Websphere
Post any errors if get during installation. Hope this helps.
regards,
GP

OIM 11.1.1.3 installation issues

Hi All,
I am facing issue while trying to install OIM 11G (11.1.1.3.0). I have installed SOA 11.1.1.4.0, OIM 11.1.1.3.0 and have used RCU 11.1.1.4.0. After installing these components, I am trying to run the config.sh from the <IDM_HOME>/common/bin and have selected Oracle Identity Manager ,Oracle SOA Suite, Oracle Enterprise Manager, Oracle WSM Policy Manager, Oracle JRF from the template options.
During this we are required to enter the schema information along with database details. I provided the same which I got from RCU. The utility then checks the database for those details but fails on OIM MDS Schema component check. I believe this might be an issue with the utility because the Database Query which is run for checking the OIM MDS Schema is looking for version 11.1.1.2.0 and not 11.1.1.4. Also for OWSM MDS Schema component check, the same query runs but for version 11.1.1.4 in the query.
Both the queries are same except for the version for which it is testing. Thus one of them is bound to fail. This utility checks 6 components in total and out of which only 1 is failing. I have already checked the schema_version_registry and there for mr_type=’MDS’ there is just one row and that has owner=’DEVOIM_MDS’ and version=’11.1.1.4.0’.
Will appreciate if anyone has any idea about this or have seen it earlier.
Another question which I have is about the compatibility for OIM 11.1.1.3.0, what are the supported versions of SOA, RCU and OFM IAM for this release of OIM as the latest OIM version is 11.1.1.3.0 while all the other components are 11.1.1.4.0.
Thanks,
BB

Rajiv Dewan wrote:
which are released on 11.1.1.4.0Not sure what you are asking but OIM 11g is certified with SOA Software to 11.1.1.3.0.
After the installation is complete, you must run the Patch Set Installer for Oracle SOA Suite (included in the Disk1 directory under the soa_patchset.zip file) to >>update your 11.1.1.2.0 software to the latest version of Oracle SOA Suite (11.1.1.3.0).
On March 8th I believe Oracle has release SOA 11.1.1.4.0 and somewhere in the docs it says it is supported while same places it skips them out totally. I will go ahead with 11.1.1.2.0 with upgrade to 11.1.1.3.0
Thanks!

OIM 9.1.0.2 installation

Hi,
I want to install oim 9.1.0.2 on weblogic server. Can you suggest weblogic version so that
I can deploy OIM 9.1.0.2
Regards
Sri

Hi Sri,
First Question:
Yes. You need to install first OIM 9.1.0.1 and then install OIM 9.1.0.2 Patch.
Second question:
Patchset 8484010
I will also suggest you apply the latest patch of OIM 9.1.0.2 version available: Patchset 13527893, version BP19.
Be aware: Contact your Oracle Support team and check until when you have OIM 9.1.0.2 support.
I hope this helps,
Thiago Leoncio.

OIM 9.1.0.1 installation issue in weblogic

OIM:9.1.0.1,DB:11g and weblogic 10.3.2 on linux 5.3 32 bit
After installtion not able to find xlwebapp in admin console.
When I search xlwebapp in /u01
oracle@oim ~]$ find /u01 -name xl*.war -print
/u01/app/oimserver/xellerate/webapp/xlScheduler.war
/u01/app/oimserver/xellerate/webapp/precompiled/xlWebApp.war
/u01/app/oimserver/xellerate/webapp/xlWebApp.war
Please let me know this is correct or not.
Its looks like xlwebapp not deployed in weblogic.

First, do a search for .ear files as well, that's where the xellerate app is going to be, not in a war file.
Weblogic should have 2 apps deployed: Nexaweb and Xellerate and those apps' files will be in
xellerate/OIMApplications/
That folder has : WLNexaweb.ear and WLXerateFull.ear for me.
If those don't exist, you can try the patch script, which will recompile and redeploy:
switch to xellerate/setup/
run ./patch_weblogic.sh [weblogicpassword] [oimdbpassword] (i think)
You can find detailed instructions on the patch script if u google it, search the install docs, or specifically where I read about it, in ANY of the upgrade patches, such as 9102 upgrade or BP11upgrade, etc... those docs have a section for what to do when the patching fails and they tell you to delete some files (precompile, etc..) and run the patch script again. I've done this a few times and it's worked for me.
Hope this helps
Alex
Edited by: Alex S on Sep 24, 2010 9:24 AM

JDK Version req for OIM 9.1.0.1 Installation

Hi,
As per Oracle's documentation, we need to use JDK 1_4_2_15 for Oracle Identity Manager 9.1.0.1. Installation. In my machine when I checked Java Version it shows jdk 1.5_0_06. Is there any problem if I go with the default jdk version or I have to change it to 1.4.2_15. Please advise.
Regards,
CC

This is given in docs:
C:\>java -version
java version "1.5.0_06"
http://download.oracle.com/docs/cd/E14049_01/doc.9101/e14062/install_config_oc4j.htm#BGBJAAID

Oim 9.1.0.1 installation over WebLogic App server 10.3 Error

can anyone help me solve the problem：
environment：redhat5.3-x64 ,database:11.1.0.7 weblogic 10.3 jdk:1.6.0.10
JDBC store "AdminServer_OIM_JDBCSTORE"
in this server is not the owner of database table "AdminServer_WLStore". Unexpected current owner is "[name={server=AdminServer!host=127.0.0.1!domain=oimDomain!store=AdminServer_OIM_JDBCSTORE!table=AdminServer_WLStore}:random=-544581572502067192:timestamp=1273295394768]", expected current owner is "[name={server=AdminServer!host=127.0.0.1!domain=oimDomain!store=AdminServer_OIM_JDBCSTORE!table=AdminServer_WLStore}:random=-4797053672388548299:timestamp=1273295377038]".>
sole/console.portal?_nfpb=true&_pageLabel=WebAppApplicationOverviewPage&WebAppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3DXIMDD%2CType%3DAppDeployment%22%29.>
<May 8, 2010 12:24:53 PM CST> <Error> <Store> <BEA-280061> <The persistent store "AdminServer_OIM_JDBCSTORE" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
<May 8, 2010 12:24:53 PM CST> <Warning> <Management> <BEA-141197> <The deployment of AdminServer_OIM_JDBCSTORE failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:62)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:
<May 8, 2010 12:24:53 PM CST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "AdminServer_OIM_JMSSERVER" due to weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist.
weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at
<May 8, 2010 12:24:53 PM CST> <Warning> <Management> <BEA-141197> <The deployment of AdminServer_OIM_JMSSERVER failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
<May 8, 2010 12:24:53 PM CST> <Critical> <Management> <BEA-141190> <The commit phase of the configuration update failed with an exception:
weblogic.descriptor.DescriptorUpdateFailedException: one or more registered update listeners reported activation problems.
The following failures occurred:
-- The following failures occurred:
-- Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
Caused by: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(Runti
"[name={server=AdminServer!host=127.0.0.1!domain=oimDomain!store=AdminServer_OIM_JDBCSTORE!table=AdminServer_WLStore}:random=-544581572502067192:timestamp=1273295374735]". Trying to wait for ownership.>
<May 8, 2010 1:09:58 PM CST> <Error> <Store> <BEA-280077> <JDBC store "AdminServer_OIM_JDBCSTORE" in this server is not the owner of database table "AdminServer_WLStore". Unexpected current owner is "[name={server=AdminServer!host=127.0.0.1!domain=oimDomain!store=AdminServer_OIM_JDBCSTORE!table=AdminServer_WLStore}:random=-544581572502067192:timestamp=1273295394768]", expected current owner is "[name={server=AdminServer!host=127.0.0.1!domain=oimDomain!store=AdminServer_OIM_JDBCSTORE!table=AdminServer_WLStore}:random=-4797053672388548299:timestamp=1273295377038]".>
<May 8, 2010 1:09:58 PM CST> <Error> <Store> <BEA-280072> <JDBC store "AdminServer_OIM_JDBCSTORE" failed to open table "AdminServer_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="AdminServer" store="AdminServer_OIM_JDBCSTORE" table="AdminServer_WLStore")
<May 8, 2010 1:09:58 PM CST> <Error> <Store> <BEA-280061> <The persistent store "AdminServer_OIM_JDBCSTORE" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed

Hello,
Were you able to find the solution to this ?
I have been facing the same problem with exactly the same environment settings.
Regards,
Rohan

Oim 9.1.0.1 installation over WebLogic App server Error

Please Fix this Error
weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
     at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
     at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
     at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
     at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:591)
     at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:64)
     at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:174)
     at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
     at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
     at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:361)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:356)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:63)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:235)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:131)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
     at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:510)
     at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:782)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
     at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
     at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
     at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:591)
     at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:64)
     at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:174)
     at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
     at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
     at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:361)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:356)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:63)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:235)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:131)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
     at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:510)
     at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:782)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>

I have the same problem at :redhat5.3-x64 ,database:11.1.0.7 weblogic 10.3 jdk:1.6.0.10
can anyone have solveit?

Installation OIM 9.1.0.1 on AIX 6.1 64 bit

I'm trying to install OIM 9.1.0.2 on Weblogic 10.3.5 on AIX.
Below the hardware description:
Processor: PowerPC/RISC
Bus Architecture: 64 bit
Operating System Name and Version: AIX 6.1
Operating System 64 bit
JDK: IBM JDK 1.6.0 64 bit
Here the steps we were following for installing the target versions of the products:
1. install WLS 10.3
2. install OIM 9.1.0.1
3. upgrade WLS from 10.3 to 10.3.1 or later (10.3.5 in my case)
4. upgrade OIM to 9.1.0.2
5. upgrade OIM to 9.1.0.2bp18
First step was succesfull without any problem but we are stuck in the second one.
We had some problems during the installation.
In the phase called "Finalizing Vital Product Data Registry..." of the ./install_server.sh we had faced with this error:
Oracle Identity Manager Installer has found that Keytool_svr.sh failed.
Do you have any suggestions for figuring out the issue?
Thanks,

Hope this helps:
https://kr.forums.oracle.com/forums/thread.jspa?threadID=464506
OIM 9.0.3.1 installation for OC4J
regards,
GP

In web console Attestation menu item not showing,after OIM 9.1.0.1 install

In web console Attestationmenu item not showing,after OIM 9.1.0.1 installation
Version: 9.1.0.1860.16
Build 1860.16
thanks.

Choose option Oracle Identity Manager with Audit and Compliance Module during installation.
INIYA.

Error occured in OIM client running

Hai all,
Am new to OIM . I completed basic installation java,jboss, oracle database, OIM server and OIM client . All the thing are running sucessfully except OIM client. It is also installed sucessfully but after entering the user name and password it showing an error . can any one please help me out from this error please . its urgent for me.

Hi,
First, make sure you have configured the client application and it can reach the OIM server side. For example, open the file [OIM_CLIENT_HOME_DIR]\xlclient\Config\xlConfig.xml.
Review the value of the <CoreServer> and <MultiCastAddress> elements.
Also, see the OIM console output to see what exception is being raised when you try to log in. Or you can open the xel.log file at [OIM_HOME_DIR]\xellerate\logs
Renato.

Oim 9.1.0.1 installation Jboss4.2.3.GA

Similar Messages

Maybe you are looking for