Installing IDM Suite on WebLogic 10.3.3 - need JRF

Question

Hi,
We're trying to install the OID software on a WebLogic 10.3.3, where the WL domain has been pre-laid down using the "regular" WebLogic 10.3.3 installation.
Apparently, that WL domain doesn't have the JRF template/files, so when we try to extend the domain using the IDM installer, it fails.
Is there a way to "add" the JRF package to this already-existing WebLogic domain?
Thanks,
Jim

Answer 1

Kevin and Kerry,
It isn't a "mistake".
I've already done a successful installation of both the IDM and IDAM suites earlier, using the "normal" way, i.e., letting the config wizard create the WL domains.
But, the management at our project is insisting on having the WL domain laid down prior to doing the IDM/IDAM installations, actually by another group that normally handles the WebLogic stuff.
So now we're "tasked" (= "stuck") with figuring how to do the installs that way.
Anyway, having said all that, I've made some progress.
I used the "appdev" product, and installed that, and then:
- Started the WL config wizard and was able to add the JRF to the domain, then
- I ran wlst per the link you all provided
After that, the IDM installer got past the "need JRF" step, and I was able to get further in the installation.
At this point, I have:
- The AdminServer starts ok
- The wls_oid1 server starts ok
- The wls_oif1 server starts ok.
But, the IDM installer is stuck at the "Deploy Directory Integration Platform step".
I checked the installation .out file, and it's showing:
Retry Start taskStarted DIP
Retry StCompleted taskStarted DIP
[OOB IDM CONFIG EVENT] onConfigurationError -> set RETRY ExecutionResponse..
getDomainRuntimeMBeanServerConnection ...
Connecting to Domain runtime ...
trying to connect to oamoidoif.whatever.com 7001
Successfully connected to the Domain Runtime ...
ASDomain.getMBeanServerConnection ...
oracle.as.provisioning.util.ConfigException:
Error while deploying the Application oracle.ldap.odip.install.DIPInstaller .
Cause:
An internal operation has failed: Unable to reach host
Action:
See logs for more details.
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
at oracle.as.provisioning.weblogic.ASDomain._executeJ2EEConfigAssistant(ASDomain.java:830)
at oracle.as.provisioning.weblogic.ASDomain.executeJ2EEConfigAssistant(ASDomain.java:681)
at oracle.as.provisioning.engine.WorkFlowExecutor._runJ2EEAssistant(WorkFlowExecutor.java:1142)
at oracle.as.provisioning.engine.WorkFlowExecutor._deployApps(WorkFlowExecutor.java:913)
at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:472)
at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
at oracle.as.idm.install.config.IdMDirectoryServicesManager.doExecute(IdMDirectoryServicesManager.java:1282)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.rmi.ConnectException: Unable to reach host
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:145)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:211)
at javax.management.remote.rmi.RMIConnectionImpl_1033_WLStub.getAttribute(Unknown Source)
at weblogic.management.remote.common.RMIConnectionWrapper$12.run(ClientProviderBase.java:726)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.RMIConnectionWrapper.getAttribute(ClientProviderBase.java:724)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:878)
at oracle.as.provisioning.weblogic.ASObject.getDomainConfig(ASObject.java:272)
at oracle.as.provisioning.weblogic.ASDomain._executeJ2EEConfigAssistant(ASDomain.java:773)
... 15 more
progress in calculate progress8
I also checked "opmnctl status", and everything there is "Alive", oid, ovd, EMAGENT:
[oracle@oamoidoif bin]$ ./opmnctl status
Processes in Instance: asinst_1
--------------------------------------------------------------+---------
ias-component | process-type | pid | status
--------------------------------------------------------------+---------
ovd1 | OVD | 15685 | Alive
oid1 | oidldapd | 15565 | Alive
oid1 | oidldapd | 15549 | Alive
oid1 | oidmon | 15538 | Alive
EMAGENT | EMAGENT | 16382 | Alive
[oracle@oamoidoif bin]$
So I'm not quite sure what to look for (it says check the logs, but which one?)....
Jim