Installing WLPI 1.2 on WLS 6.0

How do I install WebLogic Process Integrator 1.2 on WebLogic 6.0?
Thanks,
Richard

Unfortunately, it is not yet supported. Look for something on this early
next year.
Michael Girdley
BEA Systems Inc
"Richard Colley" <[email protected]> wrote in message
news:[email protected]..
>
How do I install WebLogic Process Integrator 1.2 on WebLogic 6.0?
Thanks,
Richard

Similar Messages

  • Trying to instal Service Pack 2 under WLS 6.0

    Below you can find my original message posted five days ago.
    Just as comment: I don't have a beta version. It is <release level="6.0" Status="installed".
    Any help?
    Thanks
    Sergio Ríos
    PS: please don't erase !!!
    Hi !
    I already have WLS installed and running under a Red Hat Linux release 6.2 (Zoot)Kernel
    2.2.14-6.1.1smp on an i686
    When I try to install the service pack 2 this happens: ===============================================================================
    Choose BEA Home Directory -------------------------
    1- /home/bea/wlserver6.0
    Existing BEA Home: 1
    ===============================================================================
    WebLogic Server 6.0 not found -----------------------------
    WebLogic Server Service Pack 2 Installation failed. You do not seem to have WebLogic
    Server 6.0 installed for BEAHOME /home/bea/wlserver6.0.
    What is happening?
    Thanks in advance Sergio Ríos

    Hi.
    You can get individual service packs by logging into your esupport
    account at http://support.bea.com. Alternatively you can download
    WLS6.0 with service pack 2 from
    http://commerce.bea.com/downloads/weblogic_server.jsp.
    Regards,
    Michael
    Alexandre Portella wrote:
    Hi,
    From where can I download the sp2 for WLS 6.0 on Solaris?--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Trying to install service pack 2 for WLS 6.0

    Hi !
    I already have WLS installed and running under a Red Hat Linux release 6.2 (Zoot)Kernel
    2.2.14-6.1.1smp on an i686
    When I try to install the service pack 2 this happens:
    ===============================================================================
    Choose BEA Home Directory
    1- /home/bea/wlserver6.0
    Existing BEA Home: 1
    ===============================================================================
    WebLogic Server 6.0 not found
    WebLogic Server Service Pack 2 Installation failed.
    You do not seem to have WebLogic Server 6.0
    installed for BEAHOME /home/bea/wlserver6.0.
    What is happening?
    Thanks in advance
    Sergio Ríos

    Daryl,
    That is really strange...i just tried downloading from the same link and it is working fine for me.
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/bobj_download/main.htm
    -Anil

  • Tip for installing App Dev CD into WLS on 64-bit windows

    Hi All,
    After pulling out some hair, I thought I'd share this tip.
    Scenario:
    You are installing WebLogic 10.3.x on a 64-bit Windows platform, but are using a 32-bit JDK. You want to install the Application Development CD so that you can extend your WLS domains with the JRF, EM, etc.
    Symptoms:
    You run setup.exe, the installer prompts you for a location of a JRE/JDK and you give it the 32-bit JDK location. The installer then quits without so much as a peep.
    Solution:
    Instead of running setup.exe, navigate to install\win32 and run that setup.exe instead. The same thing works for installing the SOA suite.
    Hope this saves someone else some time too.
    John

    Thanks for the help - I edited the C:\Oracle\Middleware\user_projects\domains\test_domain2\bin\setDomainEnv.cmd file as follows:
    @REM set BEA_JAVA_HOME=C:\Oracle\Middleware\jrockit_160_24_D1.1.2-4 (I commented out this line)
    set BEA_JAVA_HOME=C:\Oracle\Middleware\jdk160_24 (I added this line)
    set SUN_JAVA_HOME=C:\Oracle\Middleware\jdk160_24 (this line was already here)
    After confirming ENV's:
    Path=C:\Java\jdk1.6.0_24\bin;C:\app\bschamac\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
    JAVA_HOME=C:\Java\jdk1.6.0_24
    I then restarted WLS, but the C:\Oracle\Middleware\wlserver_10.3\common\bin\commEnv.sh still says:
    JAVA_HOME="C:/Oracle/Middleware/jrockit_160_24_D1.1.2-4"
    SO I think I am still hosed.

  • General install and deployment problem with WLS clustering on two boxes

    Hi,
    I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
    The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
    So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
    Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
    One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
    Any help appriecated.
    Surfbum.

    Hi I think I've found the answer. You can build a managed server template using the pack command.
    http://e-docs.bea.com/common/docs90/pack/tasks.html

  • ( REPOST ) WLPI 1.2.1 & WLS 6SP1 Domain/server  configuaration

    Hello,
    I have installed WLP 1.2.1 & WLS6SP1 on Sun Solaris. WLPI creates default domain
    "wlpiexampledomain" under wlpi dir. Instead of using default domain name created
    in wlpi dir, i'd like to use domain under WLP6SP1 dir. Can i do this ? If yes,
    How ?
    I am able to change domain name under wlpi dir by changing domain name & server
    name in server.sh file. I can't move/point domain it to wls6sp dir.
    Thanks in advance !!!
    Thanks Jignesh Patel

    Hi Subash,
    I tried the same installer on a 32bit machine and was able to run without any issues.
    I did however come across a few users jdeveloper users who had similar issues with the jdev installer and the following workaround seems to have solved the issue for them. coudl you try the same and let us know if that helped ?
    1. Extract "oepe-12.1.2.1-kepler-installer-win32.exe" file into C:\oepe-12.1.2.1-kepler-installer-win32
    2. In cmd go to C:\oepe-12.1.2.1-kepler-installer-win32
    3. Execute follow command:
       C:\PROGRA~1\Java\jdk1.6.0_31\bin\java.exe ( path to your JDK)  -jar install/modules/ora-launcher.jar DISKCNT=1 JRE_COMPONENT=oracle.jdk,oracle.jre
    thanks
    Raj

  • Installing WLPI 121 on WLS60SP1 ?

    I'm trying to install WLPI121 on my existing WLS60SP1 install.
    I keep getting a window pop-up telling me that I do not appear
    to have WLS6.0 installed. But I can assure I do.
    thanks,
    Per Jessen, Zürich.

    I'm trying to install WLPI121 on my existing WLS60SP1 install.
    I keep getting a window pop-up telling me that I do not appear
    to have WLS6.0 installed. But I can assure I do.
    thanks,
    Per Jessen, Zürich.Thi turned out to be a relatively simple problem - after my initial
    installation of WLS6.0 and SP1, I had changed the hostname of my
    system. And the hostname is recorded in the registry.xml file in
    the BEA home directory. So, I changed the hostname here, et voila.
    just FYI,
    Per Jessen, Zürich.

  • MYSTERY-Installing WLPI erases Registry.xml

    I have installed weblogic server and it is working fine .
    When I install weblogic integration it erases registry.xml meaning all the contenets
    in registry.xml file gets erased .
    Please let me know of any solutions .
    Thanks
    Deepth Dinesan

  • 11.1.1.7.1 wls install questions

    I have the following Questions/Comments related to the latest version of MapViewer Install on WebLogic/Windows Server (WLS ver 10.3.5.0)
    1. When installing MapViewer, the documentation suggests not needing to expand the ear file, but there is some question as to where to get an initial version of the MapViewerConfig.xml file. I assume you can pull if from the documentation, but shouldn't there be copy external to the ear file? (or do you copy it from the deployed version)
    2. Specifying the location of the MapViewerConfig.xml file. Section 1.4.2.1 suggest setting a property in the setDomainEvn.sh file. It is assumed that the windows equivalent file is "setDomainEnv.cmd". There is no "–Djava.awt.headless=true" property within the "setDomainEnv.cmd file. (note it is not contained within the setDomainEnv.sh in WLS ver 10.3.5.0 either. I successfully deployed this within the java options, but not exactly sure it is in the correct location.
    3. http://www.example.com:8888/mapviewer/omserver?getv=t returns Ver11_1_1_7_1_B130516 -- assume this works
    4. http://localhost:8888/mapviewer -- login works.
    5. http://localhost:8888/mapviewer/fsmc/tutorial/demos.html -- doesn't work. In reviewing the deployed version, no tutorial folder exists -- how do you get to the tutorials?
    6. When performing a MapViewer restart from within the Admin page, WLS provides an error stating that the mds.xml file was missing from the MapViewerConfig.xml folder. Should this file be there? This was not in the install instructions (to my knowledge).
    Thanks

    1. Yes we will bundle the config files (there are two now, mapViewerConfig.xml plus the new mds.xml file) and upload them to OTN for download in the next couple days. In the mean time you can unzip the mapviewer.ear and the web.war file inside it to a temp folder, then copy the two .xml files from the WEB-INF/conf/ directory to the folder of your choice.
    2. We will fix the doc with regard to the reference of -Djava.awt.headless; but it sounded like you were able to add the -Doracle.maps.config option to that file. To verify if this option was actually picked up and used by mapViewer, you can log into mapViewer's admin console, click Management then Configuration. On top of the configuration data, there is a File Location field which shows where the mapViewerConfig.xml file is being loaded.
    5. The new mapviewer.ear no longer ships any tutorial/demo/sample request or online API docs; all of those are now packaged into the separately deploy-able MVDEMO application (which you can download from the same OTN mapviewer site since version 11.1.1.7.1). This was mentioned in the 11.1.1.7 release note (http://download.oracle.com/otndocs/products/mapviewer/mapviewer_11p6_readme.txt).
    6. Please refer to 1 above about needing both .xml files (mds.xml and mapViewerConfig.xml) for mapviewer to function properly.
    thanks
    LJ

  • Installing SOA Suite on the integrated WLS in JDeveloper

    Hi,
    I'm wondering if it's possible to install SOA suite on the integrated WebLogic provided with JDeveloper?
    If it is not possible, what is the recommended way for provisioning for development? Is it to install a full-blown WebLogic & SOA Suite on each developers' machine?

    Hi Mark,
    No, it is not possible to install SOA on the integrated WLS in JDeveloper. There are some technical issues preventing it now but we would like to get this working in the future.
    So yes, you can install the full WLS + SOA on your own machine for development. After you install, go into WLS and turn off whatever you are not using to shrink the footprint (e.g., you don't need both soa composer and bpm composer, you don't need both worklist and workspace).
    Heidi.

  • WLPI Installation  in Silent Mode  using  sh  wlpi_121_unix.bin -i console

    Hello,
    I am installing WLPI 1.2.1 on Sun Solaris.
    JAVA_HOME : /prod/appl/java/jdk1.3.0_02
    WEBLOGIC_HOME : /prod/appl/weblogic. This directory contains WLS 6.0.0.1.
    PATH : /prod/appl/java/jdk1.3.0_02/bin:/usr/bin:/usr/local/bin:/prod/appl/weblogic/6.0.0.1/bin:.
    Console mode installation doesn't display all option mentioned in WLPI Console-Mode
    Installation. WHY ? It displays only 1st option.
    After selecting first option , JDK 1.3 was not found at
    /prod/appl/weblogic/jdk130. It is required for all WebLogic Server products.
    Why WLPI Installer is giving me above error ???
    Thanks
    JIgnesh Patel

    hi Yuri,
    Am not expert, But I beleive ur situation exactly matched the below secnario.
    EM 12c: Enterprise Manager 12.1.0.3 Cloud Control Agent deployment fails with Error: The plug-in configuration for the oracle.sysman.oh monitoring plug-in may have failed (Doc ID 1930414.1)
    PERL5LIB variable should be unset and the issue occurs even after unsetting it (see Note 1587715.1).
    Regards
    Krishnan

  • Error when installing Oracle Identity Manager 9.1.0.1

    Hello friends,
    I installed Oracle Identity Manager 9.1.0.2 Oracle Weblogic Server on a cluster, at the time of treaties authenticated in the web console of Oracle Identity Manager, I get the following message:
    A system error was encountered.
    View the full log here
    http://pastebin.com/ucN1LHP4
    BUILD FAILED
    /opt/oim/xellerate/setup/setup.xml:447: The following error occurred while executing this line:
    /opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:508)
         at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
         at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
         at org.apache.tools.ant.Task.perform(Task.java:348)
         at org.apache.tools.ant.Target.execute(Target.java:357)
         at org.apache.tools.ant.Target.performTasks(Target.java:385)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
         at org.apache.tools.ant.Main.runBuild(Main.java:758)
         at org.apache.tools.ant.Main.startAnt(Main.java:217)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    Caused by: /opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:357)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
         at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
         at org.apache.tools.ant.Task.perform(Task.java:348)
         at org.apache.tools.ant.Target.execute(Target.java:357)
         at org.apache.tools.ant.Target.performTasks(Target.java:385)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
         at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
         at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
         ... 16 more
    Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.Deployer.run(Deployer.java:72)
         at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
         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:597)
         at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
         at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
         ... 28 more
    Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
         at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
         at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:115)
         at weblogic.Deployer.run(Deployer.java:70)
         ... 35 more
    As I can solve this problem, not to reinstall everything again
    thanks

    Not sure if I understand your issue correctly. Your deployment failed during the installation and you have started the servers and trying to login?
    When installing OIM in a clustered WLS domain, the docs specify various cluster configurations needed to be completed in the WLS Admin Console before running the OIM installer. These steps DO NOT include starting up of the first managed server. In fact, if you start up the managed server then you may very well run into deployment issues after the OIM application is built. Instead, when installing OIM, the installer detects that not all nodes are on-line and so will queue the deployment for later. Deployment then takes place in later steps when you are instructed to restart the app server and start managed nodes.
    Thus was your managed server running when you were doing the installation? That has caused the issue. I would suggest to dump this domain (save the .xldatabasekey) if you don't wanna to dump the database part and start the installation again BUT don't start the managed server while doing the installation.
    HTH,
    BB

  • OIM 9.1 installation WLS 10.3.0

    Hi,
    I'm installing oim 9.1 on WLS 10.3.0 following "Installation and Configuration Guide for BEA WebLogic Server" (oficial oracle doc). Actually XlWebApp is running, I mean, I able to login to Admin console with "xelsysadm", But I'm not sure if my oim installation is correct, AdminServer.log display some errors at init time whe I execute ./xlStartWLS.... I dont understand the "default JMS queue configuration":
    Default JMS Queue Configuration
    Previously, Oracle Identity Manager used a single JMS queue (named xlQueue) for all asynchronous operations including requests, reconciliation, attestation, and offline tasks. In release 9.1.0, by default, Oracle Identity Manager uses separate JMS queues for specific operations to optimize JMS queue processing. The following list shows the JMS queues in the default configuration and indicates the operation related to each queue:
    xlQueue (for request operations)
    xlReconQueue (for reconciliation operations)
    xlAuditQueue (for auditing operations)
    xlAttestationQueue (for attestation operations)
    xlProcessQueue (for use in a future release)
    Does the installation proces SHOULD crete these queues?? or SHOULD be created manually in the WLS console???
    In the "Requiered Post Installation Tasks" -> "Setting Up XML Registry" I think the document refers to an alder version of WLS, and for me, its not clear how to create/configure correctly "the XML registry" in WLS 10.3.0, I create a XML Registry but when I Try to Configure a New XMLParserSelectRegistryEntry with the following instructions:
    In the left frame, click XML, and then click your new XML registry entry to expand it.
    Right-click Parser Select Entries, and then select Configure a New XMLParserSelectRegistryEntry from the shortcut menu.
    Enter the configuration information:
    1.Ensure that the Public ID field is blank.
    2.Ensure that the System ID field is blank.
    3.In the Root Element Tag field, enter database.
    4.In the Document Builder Factory field, enter the following: org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
    5.Ensure that the Parser Class Name field is blank.
    6.In the SAX Parser Factory field, enter the following: org.apache.xerces.jaxp.SAXParserFactoryImpl
    7.Click Create.
    Weblogic display:
    A XML Parser Select Entry Public ID must be specifed.
    SO..... STEPS 1 and 2 are correct for WLS 10.3.0??? how to know the "Public ID"???
    Please helpme to clarify the correct postinstallation steps.
    Anay help aprecciated.

    These queues are automatically created by OIM during installation. You can verify this by loggin into WLS admin console and going to
    Home >Services > Messaging >JMS Modules >OIM_JMS_MODULE >Summary of Resources

  • Installing WebLogic on Windows 7 64-bit

    I am new to weblogic and am trying to install it on my local machine but am having major issues. I found a document that stated I should have a "jar" folder in my MW_HOME but there is no such folder. I found a note where it says to perform the command:
    java -jar wljarbuilder.jar
    but I do not have the wljarbuilder.jar file - instead I have wljarbuilder.jar.pack.
    Can anyone provide assistance? Or is there a weblogic for dummies that I can get?
    Thanks in advance,
    Rob

    Hi Rob,
    What version of Oracle WebLogic Server (WLS) are you installing?
    As I'm not sure what version you are using, I'll use WLS 10.3.6 as an example. Depending on the WebLogic Server download you downloaded, the file name that was downloaded should be "wls1036_generic.jar" (12c would be wls1211_generic.jar, etc.). Of course, if you are installing a different version of WLS such as 12c, the numbers will be different (everything else is the same). To start the installer, you can run the following command in Command Prompt (as an administrator): java -D64 -jar wls1036_generic.jar
    IMPORTANT: You will need to have a JDK installed and deployed in your PATH environment variable; otherwise, the above command will not work. If you do not have a Java JDK installed (or downloaded), you can download the most recent JDK at http://www.oracle.com/technetwork/java/javase/downloads/index.html. Make sure you download the version of the JDK that is certified with your version of WebLogic Server:
    WLS 11g (10.3.x): http://www.oracle.com/technetwork/middleware/downloads/fmw-11gr1certmatrix.xls
    WLS 12c (12.1.1.x): http://www.oracle.com/technetwork/middleware/ias/downloads/wls-1211x-certmatrix-1395408.xls
    If you do not have the jar file (or one similar) I mentioned above, you can download it with your OTN license at http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html (or in Edelivery if you have purchased the software). It is the one in the section for Oracle WebLogic Server and Oracle Coherence that is for "Generic". Hope this helps!
    Thanks,
    Scott (PITSS)

  • Installing Weblogic 12c on windows server 2008

    Trouble installing Weblogic 12 on windows server 2008 ,i have oracle 11g databse in the same system.Now i am trying to install Oracle Weblogic 12 ,but WLS requires JDK 1.6 as a minimum ,after i install the Oracle11g database it automatically installed the Jdk 1.5 ..now how can i go about and install Weblogic 12 .

    install JDK 6 or 7. Load the environment variables from CMD.EXE
    set JAVA_HOME = RUTA_DEL_JDK_6_OR_7
    set PATH =%JAVA_HOME%\BIN;% PATH%
    Then, from the same terminal (cmd.exe) run the weblogic runInstaller.exe 12c.

Maybe you are looking for

  • Connecting to the upgrade server issues

    Hi i just bought a used MacBook from a friend i have been having a problem when trying to use the software update. when i click on software update it says it can not connect to the update server and that i should use network diagnostics. when i click

  • Inbox time received doesn't reflect Daylight Savings - Timestamp Correct

    The inbox list view in Mail of From, Subject, Date and Time Received does not reflect the correct time. The email itself in the header has the correct time received however the list view is an hour ahead. Considering the last time change was springin

  • Online Survey Help

    My partner has created an online survey as part of her PHD studies. Once the user has completed the form using drop downs and text input, they press a send button and the information is supposed to be e-mailed to her account. The Send is driven by Fl

  • AIP-50079

    Hi All, We are exchanging the 850 documents with the remote TP. A one transaction failed and gives the below error. 2009.07.07 at 14:15:17:120: Thread-25: (ERROR) [IPT_HttpSendHttpResponseError] HTTP response error :{0}. java.io.InterruptedIOExceptio

  • Oracle Incentive Compensation Question

    Hi, I would like to know if there are other users who have implemented "Oracle Incentive Compensation". We have implemented OIC about a year ago, and are currently running into performance issues in the "Loader, Collection and Calculation" process. W