Weblogic 9.0 on WinXP 64bit with Sun JDK 64bit

I installed Weblogic 9.0 on WindowXP 64bit version and it's fine with build in Sun's JDK and JRockit JDK but as soon as I switch to Sun's 64bit implementation of JDK (update 5) it fails to start.
Am I doing something wrong or it is not compatible with 64bit JDK on windows platform?
If so are there any plans to make it compatible with Sun's JDK 64bit version on windows platform in the near future, or any chance of 64bit JRockit JDK for windows?

On 07/20/2015 06:35 AM, Itzhak Hovav wrote:
> hi
> [snip]
> [root@p22 eclipse]# cat eclipse.ini -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120913-144807
>
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms40m
> -Xmx512m
> [snip]
Try this: http://wiki.eclipse.org/Eclipse.ini. You should have read the
sticky posts at forum's top for getting started help.

Similar Messages

  • -Xmx1024M is working with Jrockit but not with Sun JDK.

    Hi,
    We have a window server box with 8GB RAM. in which there are few other processes running apart from that we have more than 1GB space available.
    We have weblogic 10.3 present in this system. when we try to Run a managed server with JRockit JVM with -Xmx as 1024M -- it is allocating the space properly.
    but when we try the same with Sun JDK , it is failing to allocate memory.
    Please let me know if any one have come across this situaton.

    Maybe you have a large number of DLLs loaded and have insufficient amounts of contiguous free memory for the Sun JVM? Unlike Sun, JRockit does not require a contiguous heap.
    Background:
    http://blogs.oracle.com/jrockit/2008/09/how_to_get_almost_3_gb_heap_on_windows.html
    Edited by: Henrik (JRockit PM) on 2009-sep-15 07:17

  • GC taking long time when using Concurrent Mark Sweep GC with Sun JDK 150_12

    We are having problem of Garbage collection taking too long. We are using Weblogic 9.2 and Sun JDK 150_12
    Below are the memory arguments we are using. We are using Concurrent Mark Sweep GC. What we are observing is Young Generation is getting filled up and consequent tenured generation also hangs with long pauses.
    Below are the JVM arguments we are using
    -Xms2560M -Xmx2560M -Xloggc:${LOGDIR}/gc.log -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=128 -XX:MaxTenuringThreshold=0 -XX:CMSInitiatingOccupancyFraction=60 -XX:NewSize=512m -XX:MaxNewSize=512m -XX:MaxPermSize=256m
    I have seen many forums where there are many reported issues with Concurrent Mark Sweep garbage collection with Sun JDK, but with different recommendations. But did not find any defnite recommendation. Please advice.
    - - Tarun

    We are having problem of Garbage collection taking too long. We are using Weblogic 9.2 and Sun JDK 150_12
    Below are the memory arguments we are using. We are using Concurrent Mark Sweep GC. What we are observing is Young Generation is getting filled up and consequent tenured generation also hangs with long pauses.
    Below are the JVM arguments we are using
    -Xms2560M -Xmx2560M -Xloggc:${LOGDIR}/gc.log -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=128 -XX:MaxTenuringThreshold=0 -XX:CMSInitiatingOccupancyFraction=60 -XX:NewSize=512m -XX:MaxNewSize=512m -XX:MaxPermSize=256m
    I have seen many forums where there are many reported issues with Concurrent Mark Sweep garbage collection with Sun JDK, but with different recommendations. But did not find any defnite recommendation. Please advice.
    - - Tarun

  • [svn:fx-trunk] 11488: Resubmitting binary distribution of xercesPatch. jar from the third party module in the SDK and compiled it with Sun JDK 1.4 .2_12.

    Revision: 11488
    Author:   [email protected]
    Date:     2009-11-05 17:10:10 -0800 (Thu, 05 Nov 2009)
    Log Message:
    Resubmitting binary distribution of xercesPatch.jar from the third party module in the SDK and compiled it with Sun JDK 1.4.2_12.
    QE notes: N/A
    Doc notes: N/A
    Bugs:
    SDK-16818 - Must open-source the code for xercesPatch.jar.
    Reviewer: Discussed with Gordon
    Tests run: Checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-16818
    Modified Paths:
        flex/sdk/trunk/lib/xercesPatch.jar
        flex/sdk/trunk/modules/thirdparty/xerces-patch/build.xml

    Did you try this:
    http://forum.java.sun.com/thread.jsp?thread=434718&forum=60&message=1964421

  • WebLogic 9.0 with Sun JDK and JVMTI

    WebLogic 9.0 runs a JVMTI agent fine with JRockit, but when using the BEA supplied Sun JVM it gives following error "Could not reserve enough space for object heap". I tried all kind of settings for Xms, Xmx, PermSize and MaxPermSize, but no luck. Anyone any suggestions?
    Thanks,
    Luc

    WebLogic 9.0 runs a JVMTI agent fine with JRockit, but when using the BEA supplied Sun JVM it gives following error "Could not reserve enough space for object heap". I tried all kind of settings for Xms, Xmx, PermSize and MaxPermSize, but no luck. Anyone any suggestions?
    Thanks,
    Luc

  • Java Generics in Ejbs WebLogic 9.2 MP1 WindowsXP Sun JDK

    Hi guys,
    I tried to deploy our application on Weblogic Server 9.2 MP1 (Windows, Sun JDK) and during deployment I have this error see bellow.
    Can somebody tell me what is the problem with generics and EJB compiler?
    Is necessary to add any path or change any server settings?
    Thanks for help
    Robert
    location: interface
    ...daoadapter_DaoAdapter_rge4uk_Intf
    public void batchPersist(java.util.List<T> arg0);
    ^
    ...daoadapter_DaoAdapter_rge4uk_Intf.java:20: cannot find symbol
    symbol : class T
    location: interface
    2 errors
    at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
    at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
    at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
    at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperatio
    n.java:189)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:15
    7)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(Deploymen
    tReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiv
    erCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCal
    lbackDeliverer.java:45)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Thanks Matt for your answer.
    But I don't finish my testing :)
    I tried to deploy the same application on Weblogic 9.2 MP2 and then MP3 (sun jdk domain) and I didn't have problem with generics (application was correctly deployed and running).
    Then something was fixed in newer versions or may be bea guys support more then is in EJB 2.x specification.
    My next step, I'll try to deploy it on Jrockit domain and I give a note to conference what happen, may be it can help to somebody else.
    Thanks
    Robert

  • Duplicate soap envelope with JRockit and not Sun JDK

    I have been installed Weblogic 10.3.6 with Sun JDK 1.6 on Windows 7 64 bit. This has worked great for a client sending in a soap request which is processed in my war as a 1.2 message. Debugging this shows the response is valid in my code, and works on Sun 1.6 fine.
    When I switched to JRockit [jrockit-jdk1.6.0_33-R28.2.4-4.1.0-windows-x64] I started to receive a duplicate soap envelope and soap body wrapped around the valid soap envelope which worked before.
    With the only change being switching to JRockit, this must be the cause of the addition of the duplicate the soap body and envelope. I searched this forum and Google and have not found a reason or solution.
    Any ideas on a solution?

    Seems to be the case that using MTOM stops this problem with JRockit. Strange but apparently true (so far).

  • Uninstall SUN JDK 1.6_14 and install SUN JDK 1.6_18 for Weblogic

    My GridControl server has all of a sudden gone wild in consuming 100% of the cpu. The process was java.exe in the Middleware folder. Somebody suggested to verify the JDK and I indeed have an older version than the one recommended.
    Does anybody know where it is documented on how to uninstall and then reinstall SUN JDK 1.6_18 and have Weblogic still work afterward? (Win 2008 32 bit)
    I'd hate to reinstall the entire Gridcontrol 11g because I have the wrong jdk.
    Thanks.

    Hi,
    Uninstalling SUN JDK 1.6_14 from your Box is optional step....Most of the Servers are flexible enough ...they provide us the facility to change the JDK at any point of time...Without reinstalling the Product from the scrap....
    You can directly install SUN JDK 1.6_18 in your WebLogic Server Box. Then you need to make a small change in the *"<DOMAIN_HOME>\bin\setDomainEnv.cmd"* file ...to change the JAVA_HOME variable value...That's all.
    Next time whenever you will start your WebLogic Servers it will pick up the SUN JDK 1.6_18 version only.
    I am pasting few lines from *"setDomainEnv.cmd"*
    @REM *************************************************************************
    set WL_HOME=C:\bea103\wlserver_10.3
    for %%i in ("%WL_HOME%") do set WL_HOME=%%~fsi
    set BEA_JAVA_HOME=C:\bea103\jrockit_160_05
    <b><font color=red>set SUN_JAVA_HOME=C:\all_Jdks\JDK 1.6_18</font></b>
    set JAVA_OPTIONS=%JAVA_OPTIONS% -Dwhat.is.your.name=Jay_SenSharma
    if "%JAVA_VENDOR%"=="BEA" (
         set JAVA_HOME=%BEA_JAVA_HOME%
    ) else (
         if "%JAVA_VENDOR%"=="Sun" (
              set JAVA_HOME=%SUN_JAVA_HOME%
         ) else (
              set JAVA_VENDOR=Sun
              set JAVA_HOME=C:\bea103\jdk160_05
    @REM We need to reset the value of JAVA_HOME to get it shortened AND
    @REM we can not shorten it above because immediate variable expansion will blank it
    set JAVA_HOME=%JAVA_HOME%
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

  • Unable to use JProfiler with SUN Access Manager (in Weblogic Server)

    Whe I was trying to profiling with JProfiler , I am getting the following exception during the Weblogic startup:
    <Dec 12, 2005 6:30:49 PM IST> <Warning> <HTTP> <BEA-101247> <Application: '/opt/SUNWam', Module: 'amcommon': Public ID references the old version of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
    Dec 12, 2005 6:30:54 PM com.sun.xml.rpc.server.http.JAXRPCContextListener contextInitialized
    INFO: JAXRPCSERVLET12: JAX-RPC context listener initializing
    <Dec 12, 2005 6:30:56 PM IST> <Warning> <Net> <BEA-000905> <Could not open connection with host: ctsblrsun14.gmacfs.com and port: 8001.>
    <Dec 12, 2005 6:30:56 PM IST> <Warning> <Net> <BEA-000905> <Could not open connection with host: ctsblrsun14.gmacfs.com and port: 8001.>
    <Dec 12, 2005 6:30:56 PM IST> <Warning> <Net> <BEA-000905> <Could not open connection with host: ctsblrsun14.gmacfs.com and port: 8001.>
    <Dec 12, 2005 6:30:56 PM IST> <Warning> <Net> <BEA-000905> <Could not open connection with host: ctsblrsun14.gmacfs.com and port: 8001.>
    <Dec 12, 2005 6:30:57 PM IST> <Error> <HTTP> <BEA-101216> <Servlet: "LoginLogoutMapping" failed to preload on startup in Web application: "amserver".
    javax.servlet.ServletException
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:919)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:883)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:822)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3335)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3292)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3278)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3261)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5951)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:862)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2127)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2168)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2115)
    at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3082)
    at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.jprofiler.agent.Agent$_E.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: java.lang.NullPointerException
    at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1028)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:904)
    ... 25 more
    >

    This is an SSL handshake problem of Websphere - has nothing to do with AM.
    Websphere�s JDK does not trust the Signer / Cert of AM�s deployment container.
    Either configure a truststore (or use an existing webshpere truststore) where you import the Cert of the Signing CA of your AM DC�s cert.
    Other option - import the mentioned cert in cacert file of IBM JDK - but be aware that this might get lost when applying an Websphere fixpack/refreshpack.
    BTW what have you configured for server.port,server.host and server.protocol in your AMConfig.properties?
    If you have not changed that settings agent will use the port/protocol specified to communicate with AM.
    -Bernhard

  • Using BEA Weblogic Portal with Sun Access Manager

    Hello all,
    I am wondering if anyone has had experience with using Weblogic Portal (versions 8.1 or 9.2) with Sun's Access Manager tool (part of the Identity Management suite).
    In particular, I would like to know what access control tasks were performed through access manager, and which were performed portal-side.
    Any information would be appreciated.
    Thanks!

    Hi
    Has any one explored the below question.
    Is WLP 9.2 compatible with Sun Access Manager?
    If yes, please let know the details.
    Thanks

  • CS4 GPU works fine in WinXP 64bit -with some tweaking

    For several weeks I was unable to get the CS4 GPU accelleration working under WinXP 64 bit (not officially supported by Adobe). I spent hours on the phone with ATI and a bit of time w Adobe also. No sucess with my ATI FireGL V3600 which works fine with DAZ Studio showing full textures in the View window and does decent and very fast renders.
    Afte I gave up and started building a Vista 64bit machine, I saw a post from Slim_W who got GPU accelleration working fine with his very expensive FL card.
    I had already gone through installing latest drivers, running special Adobe Reg patching utility files etc.
    When I checked ATI, I saw there was brand new driver available. I downloaded and installed, ran the Adobe utility and GPU Accelleration works beautifully.
    Read more here:
    http://forums.dpreview.com/forums/read.asp?forum=1004&message=30072969
    Anyone else who is using WinXP 64bit might find this info useful.
    Dan

    For several weeks I was unable to get the CS4 GPU accelleration working under WinXP 64 bit (not officially supported by Adobe). I spent hours on the phone with ATI and a bit of time w Adobe also. No sucess with my ATI FireGL V3600 which works fine with DAZ Studio showing full textures in the View window and does decent and very fast renders.
    Afte I gave up and started building a Vista 64bit machine, I saw a post from Slim_W who got GPU accelleration working fine with his very expensive FL card.
    I had already gone through installing latest drivers, running special Adobe Reg patching utility files etc.
    When I checked ATI, I saw there was brand new driver available. I downloaded and installed, ran the Adobe utility and GPU Accelleration works beautifully.
    Read more here:
    http://forums.dpreview.com/forums/read.asp?forum=1004&message=30072969
    Anyone else who is using WinXP 64bit might find this info useful.
    Dan

  • Jdeveloper 9i with Sun ONE (iPlanet) Web Server 6.0

    Hi,
    Has any one working Jdeveloper 9i with Sun ONE (iPlanet) Web Server 6.0 ?
    When i add new application server it gives only Oracle App Server and Web Logic.
    Thanks
    Ramesh

    Currently JDeveloper provides Application server connections to Oracle9iAS and WebLogic, which can be used to deploy J2EE Modules.
    JDeveloper allows to create assemble generic J2EE archives from projects which can used to deploy to other application servers.
    Check out How-To documents on this topic
    http://otn.oracle.com/products/jdev/howtos/content.html
    raghu
    JDev Team

  • Problems for wlserver on win2kpro with sun jdk1.3.1

    "I make evaluation for my company for BEA Weblogic Server 5.1 for Win2kPro with SP10 and with SUN jdk1.3.1 all is ok when I setup wlconfig -JAVA_HOME=C:\jdk1.3.1 but when I start wlserver I receive :

    after the first time, maybe WeChat is not completely turned off (= headless app).
    What you can simply do is open the device monitor (it is in the device settings, but I have put it directly in the Quick Settings drawer).
    Once the device monitor is open, in the bottom row tap on the "Memory" button. The screen changes, and you can find the WeChat app in the list. Tap and hold on it, and a menu will appear to the right, the top button in that overflow menu is "Close".
    If you tap on it it will really close the app, and you can then open it again.
    That being said, I can open and close WeChat and reopen it without doing all that.
    WeChat is a very nice app, even though it does not always show me people around me, sometimes people 4000km away.
    The search box on top-right of this page is your true friend, and the public Knowledge Base too:

  • NI-DAQ for WinXP 64bit Edition

    Hello,
    Does anyone know NI-DAQ is going to support WinXP 64bit Edition or the NI-DAQ 7.3 version can be installed on the Win64 already? Thank you!
    Rolly

    Hi Rolly,
    The NI-DAQ driver is currently not supported. Please consider the following KnowledgeBase article for more details:
    Are National Instruments Products Compatible with Windows XP 64-bit for AMD's x86-64 Technology?
    Thanks,
    Lesley Y.

  • Discoverer 4i not working with Sun JRE plugin

    Hi All,
    Recently i replaced jinitiator with Sun JRE plugin, after the deployment of the plugins the discoverer is not launching from the form based responsibility.
    Its displaying on window as
    Applet oracle.disco.DiscoApplet notinited
    But i see the document 290807.1 for deployment of Sun JRE its no where mentioned that 4i will not Support Sun JRE plugins.
    Any inputs are appreciated
    Thanks in advance.

    Hi,
    You can upgrade to Discoverer 10g (10.1.2.3).
    Note: 313418.1 - Using Discoverer 10.1.2 with Oracle E-Business Suite 11i
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=313418.1
    Note: 459344.1 - What JRE Client Works With Discoverer 10.1.2 and e-Business Suite 11.5.10.2?
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=459344.1
    Note: 367389.1 - Recommended Patch for Discoverer 10g (10.1.2.1 / 10.1.2.0.2) Plus Known Issues
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=367389.1
    If you are not planning to use Oracle AS 10g features (like Discoverer Connection Management, Discoverer Portlet Provider, and Oracle Single Sign On, ..etc), you can choose to install Oracle Business Intelligence Server 10g Release 2. Oracle Business Intelligence Server 10g Release 2 is available on a separate standalone CD and includes Discoverer Server 10g, Discoverer Plus 10g, and Discoverer Viewer 10g.
    Regards,
    Hussein

Maybe you are looking for