1 person found this helpful
Actually you are installing on a OS not officially supported, so if it doesn't work it is not shocking ....
Difficult to know if you are supposed to be able to install OBIEE 12c on a Windows 7 because a) it's a desktop OS b) it's a "old" OS c) it isn't supported ....
Ugh. Haven't seen anything to indicate that it shouldn't be supported, but not impossible that I've overlooked it somewhere. The documentation isn't exactly the best organized I've ever seen.
Win7 is supported by MS until 2020, though, so seems weird to me for it not to be supported. Pretty sure we can't be the only shop still running on this (though I hope we get an upgrade i the coming year).
Can you provide the screen shot and config.bat file.
Not saying Windows 7 isn't a valid OS for your desktop daily work... (and there is also still some form of support for it by Microsoft).
But the first and most important thing: OBIEE isn't a desktop application, it is a enterprise level server software. So just this explain why there is no effort to officially support a desktop OS.
For the details of certified systems look at the certification matrix: http://www.oracle.com/technetwork/middleware/fusion-middleware/documentation/fmw-122120-certmatrix-3254735.xlsx
As I said it doesn't mean it's impossible and will never ever be able and so don't even try. It's just that the documentation will not cover your case, the support will not cover your case and if you have problems first up to you to prove isn't because of your unsupported OS and only after the OBIEE side of problem will managed.
So, knowing how easily you can have a linux running in a virtualmachine (with a desktop, no need to go command line if you are not comfortable with it) and it will be a supported configuration and so the install will just work I would say it's good to at least evaluate that option.
The only part of OBIEE officially supported by Windows 7 is the OBIEE Admin tool, this one it's fine with Windows 7, 8.1 or 10.
Screenshot of run (with -debug):
Problem seems to be that ilaunch.exe runs, but does nothing.
Sure, I understood that. Though it seems odd that this should break at the configuration step, rather than somewhere else (and very annoying not to have any explanation about what is breaking).
Anyway, I expect I'll just have to wait for the infrastructure team here to spin up some Linux VMs and see if that works better. Thanks for responding.