The journey of discovery continues. I can report a successful install of Oracle Business Intelligence 11.1.1.9 on Microsoft Windows 2012 R2, but I encountered one last bug and set of supplemental instructions worth sharing.
During the Configuration Progress step of the Enterprise Install the “Setting Up BI Publisher” step never completed. From the screenshot below you can see that I let the installer run for quite a while, over 90 minutes, and still no progress. This step normally takes less than a minute so something was definitely wrong.
I opened the log file shown in the screenshot above, but it didn’t include any detail. Fortunately, the related .OUT file (same file name as the .LOG file, but with different extension) held the details about the problem
updateBIPConfigFiles: Problem invoking WLST - Traceback (innermost last): updateBIPConfigFiles: File "D:\Middleware\Oracle_BI1\bifoundation\install\updateBIPConfigFiles.py", line 15, in ? updateBIPConfigFiles: File "D:\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/javaos$py.class", line 334, in system updateBIPConfigFiles: File "D:\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/popen2.py", line 235, in system updateBIPConfigFiles: File "D:\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/popen2.py", line 72, in __init__ updateBIPConfigFiles: File "D:\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/javashell.py", line 64, in execute updateBIPConfigFiles: OSError: (0, 'Failed to execute command ([\'sh\', \'-c\', \'java -classpath D:\\\\Middleware\\\\Oracle_BI1/clients/bipublisher/xdo-server.jar oracle.xdo.install.UpdateConfigFiles 9704 9703 9710 jdbc/mds/owsm D:\\\\Middleware\\\\user_projects\\\\domains\\\\bifoundation_domain\']): java.io.IOException: Cannot run program "sh": CreateProcess error=2, The system cannot find the file specified') updateBIPConfigFiles: java.lang.Exception: WLST Script task failed with status 1
After some digging on Oracle Support I ran across the following Bug Report.
Bug 21187922 : OBIEE 11.1.1.9 INSTALL FAILED AT CONFIGURATION STEP : WINDOWS SERVER 2012
There is no direct solution to this problem, but the following support document points to a workaround.
OBIEE 11g: Error: “UpdateBIPConfigFiles: Problem invoking WLST – Traceback (innermost last)” BI Publisher Set Up Fails on Windows Server 2012 when Running the Configuration Assistant (Doc ID 1580583.1)
The solution involves updating the javashell.py file within the jython-modules.jar file. To leverage this fix we have to interrupt the Oracle BI installation, modify the appropriate file, then continue the installation. The detailed process is below.
- Download and install Oracle WebLogic Server 11gR1 (10.3.6) Generic and Coherence [V29856-01]
- Step 2 requires that Oracle WebLogic Server be installed in advance
- Oracle WebLogic Server 10.3.6 is required for Oracle Business Intelligence 11.1.1.9
- Perform a Software Only Install of Oracle Business Intelligence 11g (11.1.1.9.0) for Microsoft Windows (64-bit) [V76016-01]
- Update the javashell.py file
- Open a Command Prompt
- Navigate to the [Middleware Home]\wlserver_10.3\common\wlst\modules directory
- Extract the javashell.py file with the following command: [JDK Home]/bin/jar xf jython-modules.jar Lib\javashell.py
- Use a text editor to modify the [Middleware Home]\wlserver_10.3\common\wlst\modules\Lib\javashell.py file
- Search for the first incidence of _osTypeMap in the file
- Add ‘Windows Server 2012’ to the map for “nt” right after ‘Windows 7’ (see below for details)
- Import the javashell.py file with the following command: [JDK Home]/bin/jar uf jython-modules.jar Lib\javashell.py
- Run the Oracle Business Intelligence 11.1.1.9 Configuration Assistant to continue your install as normal
The section of text in javashell.py to modify in 3.4.2 above will look like this when complete. The added text is in bold red.
_osTypeMap = ( ( "nt", ( 'nt', 'Windows NT', 'Windows NT 4.0', 'WindowsNT', 'Windows 2000', 'Windows 2003', 'Windows XP', 'Windows CE', 'Windows Vista', 'Windows Server 2008', 'Windows 7', 'Windows Server 2012' )),
Awesome! Thanks for the post! This worked great for me! I actually was installing BI Publisher 11.1.1.7, but ran into the exact same error since I was installing on Server 2012. This fix the issue for my installation as well.
-Jonathan
very helpful. I was able to get obiee 11.1.1.9 working on my windows 8 laptop due to this input.
Hi, I proceed just like you did but Windows 10 so I have :
_osTypeMap = (
( “nt”, ( ‘nt’, ‘Windows NT’, ‘Windows NT 4.0’, ‘WindowsNT’,
‘Windows 2000’, ‘Windows 2003’, ‘Windows XP’, ‘Windows CE’,
‘Windows Vista’, ‘Windows Server 2008’, ‘Windows 7’, ‘Windows 10’ ))
in my javashell.py.
But I still have the same error. My java is 1.7.0_79.
Do you think Windows 10 is not OK for OBIEE 11g(1.1.1.9) ?
Thanks.
Thanks for document, it works.
I followed the steps, but fixed as soon as it’ completed the weblogic and click retry button then it will pick up the new change and continue processing.
I mean, I install the OBIEE 11.1.1.9 (enterprise install) without the weblogic first.
Chris,
Please refer to the OBIEE 11.1.1.9 Certification Matrix for complete details on what is supported. http://www.oracle.com/technetwork/middleware/bi/bi-11gr1certmatrix-11-1-1-9-0-2541437.xls
You will see that Windows 10 is not listed as a supported operating system. Also, the Java version required for most installations is 1.7.0_80+. Since 1.7.0_80 is the terminal version of Java 7 that is the version I recommend if you want to try again.
Make sure you have step 5 as documents :
5.Import the javashell.py file with the following command: [JDK Home]/bin/jar uf jython-modules.jar Lib\javashell.py
I had the same error, same version of OS (Win server 2012 R2), but I use another workaround:
1)Install the OBIEE component from setup selecting Enterprise Install (ignoring AppCrash at 97%)
2)Exit the configuration tool after complete the install task just before “Create a new BI System” step.
3)I use your guide,step 3
” Update the javashell.py file
Open a Command Prompt
Navigate to the [Middleware Home]\wlserver_10.3\common\wlst\modules directory
Extract the javashell.py file with the following command: [JDK Home]/bin/jar xf jython-modules.jar Lib\javashell.py
Use a text editor to modify the [Middleware Home]\wlserver_10.3\common\wlst\modules\Lib\javashell.py file
Search for the first incidence of _osTypeMap in the file
Add ‘Windows Server 2012’ to the map for “nt” right after ‘Windows 7’ (see below for details)
Import the javashell.py file with the following command: [JDK Home]/bin/jar uf jython-modules.jar Lib\javashell.py”
4)Execute the config tool ($OBIEE_HOME\Oracle_BI1\bin\config.sh or config.bat)
It worked for me 😉
Good luck and thanks for this helpful post!
please right the final command for step 3 and 5 beacuse i can’t run this script right as example .
Extract the javashell.py file with the following command: [JDK Home]/bin/jar xf jython-modules.jar Lib\javashell.py
Use a text editor to modify the [Middleware Home]\wlserver_10.3\common\wlst\modules\Lib\javashell.py file
Search for the first incidence of _osTypeMap in the file
Add ‘Windows Server 2012’ to the map for “nt” right after ‘Windows 7’ (see below for details)
Import the javashell.py file with the following command: [JDK Home]/bin/jar uf jython-modules.jar Lib\javashell.py
I cannot be more specific on the commands to 3.3 and 3.5 since I don’t know the location of your JDK. An example location is “C:\Program Files\Java\jdk1.8.0_92”. Find your JDK and replace [JDK Home] with that location.
Please remember that Microsoft Windows command prompt commands consider a space a break in the command. If your JDK home has a space in the name as the example above you will need to put the entire command up to “jar” in quotes.
“C:\Program Files\Java\jdk1.8.0_92\bin\jar” xf jython-modules.jar Lib\javashell.py
I am having the same issue and when I go to run the script from the directory using the syntax C:\Program Files\java\jdk1.7.0_79/bin/jar xf jython-modules.jar Lib\javashell.py I get the response ” ‘C:\Program’ is not recognized as an internal or external command, operable or batch file. Please help me it seems I’m on the right track with your workaround but I can’t quite execute.
I’m deploying on WLS 12.1.3 with BI Pub 11.1.1.9 JDK 7u79 and Windows Server 2012 R2
Try enclosing the command line/path with quotes. The space between C:\Program and Files is causing a parsing problem, I imagine.
does the same workaround also work for Windows 10? or reverting to Windows 8 or server version is the only alternate?