Which Identity components run automatically (Windows)?

Question

Hi,
I've finished installing:
OID
OVD
OIF
OAM
OIM
On several Windows 2003 Servers, and while I haven't tested everything, things seem to be working.
I noticed that for most of these, you actually have to start the WebLogic instance (startWebLogic) and then start each component up via the WL console (e.g., oam_server1, etc.), but I also noticed that the ldapd part of OID and also OVD appear to run on startup, and shows up under opmnctl. I understand that without running WebLogic, I can't access the OID and OVD consoles, but the "servers" themselves appear to run autonomously.
So, I was wondering, what about the other components? Do any of them run like that, as kind of "services", and, in particular, OAM and OIF? Or, for those, do I always have to start the WebLogic console, and start the "servers" via the WL Console, in order for them to be "running"?
Thanks,
Jim

Answer 1

I think the way the fusion idm components are developed and deployed has an impact on what you see.
Lets talk of the individual products. I would assume we all know the very basics of weblogic architecture and the related terms.
1. OVD: The OVD is not a managed instance of the weblogic server. It is a standalone J2SE instance. Therefore the OVD can run perfectly well without the weblogic and can run the opmn control. But the ODSM is a webapp deployed on the weblogic, so to administer the ovd, you will have to run the weblogic and then run the odsm.
2. OAM: The OAM is a managed instance under weblogic server in a weblogic domain. (def port is 14001). So, the weblogic managed instance must be running for OAM to work. Note that the weblogic admin server might not run; you can start the managed instance through the command line as well. Same for OIM. Now, oamconsole is a webapp to administer the OAM instance, so the weblogic server needs to be running for oamconsole.
3. Node manager is tied to one of host: if you want to startup/shutdown any managed instance from the weblogic console, then you must have the node manager running. If the node manager is not running, then the only way to start the managed instances from the command prompt. The admin instance must be running nevertheless.
Hope this is correct and this helps. Let us know.