EAS with 2 admin servers? possible

helllo,
i have added 2 essbase servers
1. local host( my essbase server)
2. My work (company)
but what i meant is now .. i able to add both the servers in Administration servers but is there any possibility to open both in same EAS.. because when i open local host iam not able to open My work (company ) for that i need to open new EAS again ..is there any possibility for both servers as local host is installed in my PC and my work is installed in another location
i hope i made my self clear ..if not please do drop ur comments

yes you can expand them both if you have added them? remember there is a difference between EAS server and Essbase server. Add 1 EAS/Administration server and 2 Essbase servers.
hopefully we're talking about the same thing
what exactly are you trying to achieve? (what do you want to be able to do with 2 servers)

Similar Messages

  • Re: Precompiling JSP with admin/managed servers

    Thanks, but I'm not doing any copying.
              The admin/managed-server communication copies things to the managed server,
              which then always recompiles the pages when hit.
              -Greg
              Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
              www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
              "Robert Coonrad" <[email protected]> wrote in message
              news:[email protected]...
              >
              > check out post 8366...i found that i was not preserving
              > the lastmodified date on my jsps and this was causing
              > unnecessary re-compilation.
              >
              > hope it helps...
              > bobc
              >
              > "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
              > >I believe I have exhausted all permutations of EARing/notEARing,
              > >WARing/notWARing, placing precompiled jsp class files in WEB-INF/classes,
              > >placing them in a static location and setting workingDir to that
              location,
              > >combinations of the above.
              > >
              > >No matter what, the managed server re-compiles pages the first time they
              > >are
              > >hit. Non admin/managed-server I have no problems.
              > >
              > >Can anyone from BEA comment on this problem? Or give me a workaround
              > >for
              > >getting a cluster working with precompiled jsps?
              > >
              > >-Greg
              > >
              > >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
              > >news:[email protected]...
              > >> Grrr... The JSP engine is extremely frustrating! I've spent many hours
              > >> fighting the "staleness" checker in WL. I've been through all of the
              > >> newsgroup messages pertaining to pre-compiling, etc., and I've gotten
              > >> pre-compilation working on single-server deployments, but admin/managed
              > >> server deployments have me beat.
              > >>
              > >> WL6.1, SP1, Solaris
              > >>
              > >> I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
              > >> place. The fixed place contains pre-compiled versions of all jsps
              > >made on
              > >> that machine using jspc not 20 minutes earlier using the JSP files
              > >in the
              > >> exploded EAR file used by the admin server as the model for managed
              > >> servers.. The managed servers are on the same machine.
              > >>
              > >> When the admin server gives an application to a managed server, the
              > >managed
              > >> server creates a temporary directory containing all of the webapp
              > >> components, etc. The file timestamps on these files is the set by
              > >the
              > >> copying process to the time of the managed server boot (why?!?!????!?),
              > >so
              > >> the staleness check always thinks they are new and could care less
              > >what
              > >> precompiled jsps I have in my workingDir, the WEB-INF/classes
              directory,
              > >or
              > >> anywhere else. The pageCheckSeconds=-1 seems to be completely ignored
              > >in
              > >> this scenario.
              > >>
              > >> If I tell the managed server to precompile everything on boot (about
              > >45
              > >> minutes for this app) it will create versions of the classes that match
              > >th
              > >e
              > >> new JSP file timestamps, but this does not even survive a reboot of
              > >the
              > >> managed server because it AGAIN creates a new temp version of
              everything
              > >on
              > >> the next reboot with new timestamps.
              > >>
              > >> If I wait for the managed server to boot and find the directory like
              > >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
              > >copy
              > >> (via cp -pr to retain timestamps) all of the original webapp components
              > >on
              > >> top of the temp versions, the staleness checker is happy and the
              > >> pre-compiled versions work fine.
              > >>
              > >> There HAS to be a way to package pre-compiled versions of the JSPs
              > >in the
              > >> "model" application in the admin server and keep from having to
              precompile
              > >> the JSPs on every managed server every time managed server is booted..
              > >>
              > >> It would help if we had a way to bypass the staleness checking
              > >completely..
              > >> Or you guys should make the timestamps on the files copied by the
              > >> admin/managed deployment process match properly so the staleness
              checker
              > >> doesn't think the JSP is different.
              > >>
              > >> It would also help if the engineer who wrote this could explain the
              > >rules
              > >> being implemented by the staleness checker. So far all the messages
              > >in
              > >the
              > >> newsgroup have amounted to point solutions for problems without a good
              > >> understanding of what the engine is checking for and/or doing under
              > >the
              > >> covers. Looking at the generated .java files for the JSP pages helps,
              > >but
              > >> it is not good enough...
              > >>
              > >> Anyone out there have a working admin/managed server JSP application?
              > >> -Greg
              > >>
              > >> -----------------------------------------------------------
              > >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
              > >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
              > >>
              > >>
              > >>
              > >
              > >
              >
              

    The admin/managed-server communication copies things to the managed server, which then always recompiles the pages when hit.
              This is a known issue and is fixed. The timestamps of the compiled classes was not being preserved when extracted from the war file used to distribute to the managed servers. This will be available in WLS6.1 Service Pack 3 - and there is a temporary patch available for SP2. Please ask your friendly BEA support person for it (you can refer to CR058946)
              I'd give you the patch myself, but they like to keep track of these things...
              Regards,
              Alex
              "Girish" <[email protected]> wrote in message news:[email protected]...
              >
              > "Aditya Kiran Gavvala" <[email protected]> wrote:
              > >Greg,
              > >
              > >I have been following your posts, because our application deployment
              > >ran
              > >into exact same problem you ran into. I had spent a full two days
              > >researching into the problem. And I figured the solution. Hope this
              > >helps.
              > >
              > >Here are my discoveries:
              > >
              > >The following applies only to the following environment:
              > >OS: Linux (perhaps for Win/Unix/Solaris etc)
              > >WLS 6.0 SP2 ( no rolling patches): I found Rolling Patch2 (RP2) not useful
              > >for this problem.
              > >Clustered environment with Admin/Managed servers
              > >
              > >- When you compile JSP using weblogic.jspc compiler it puts the JSP file
              > >timestamp into the compiled class. You can see it in the generated java
              > >file
              > >(you need to supply -keepgenerated switch to jspc)
              > >
              > >- When a request is made to a JSP page after the application is deployed,
              > >it
              > >seems to be retrieving this timestamp from the compiled class file and
              > >comparing it with the JSP file timestamp. If they dont match a compile
              > >command gets run by the server. Thereby you see a compile happening at
              > >run
              > >time.
              > >
              > >- If you have exploded directory deployment, when you start the managed
              > >servers they create a ".war" file (under some temp dir) with all the
              > >JSP
              > >source files going into the file. You can notice this by looking into
              > >the
              > >server log file. Therefore all JSP source files get a brand new timestamp
              > >in
              > >the archive (a timestamp later than what was put class files by
              > >weblogic.jspc). So, the server at run time sees that the timestamp in
              > >the
              > >class file is older than the JSP source file and runs a recompile. So
              > >DONT
              > >DO EXPLODED directory deployment if your environment is as described
              > >in this
              > >post.
              > >
              > >- If you have ".war" file deployment, you will not have a problem. At
              > >the
              > >start up time managed server still creates "".war" file under a temp
              > >directory however it seems to be copying the content of the your ".war"
              > >file. So, the timestamps of JSP remain the same as they were before.
              > >SO NO
              > >RE-COMPILATION.
              > >
              > >- Another important thing to remember is to make sure you specify the
              > >workingDir in the weblogic.xml file. That is where the precompiled class
              > >files should reside. This should be any directory the server uses as
              > >scratch
              > >pad to compile classes or find (pre)compiled classes. This is not a
              > >directory inside your .war file is what I am trying to get at.
              > >
              > >Hope this helps,
              > >Aditya
              > >
              > >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
              > >news:[email protected]...
              > >> Thanks, but I'm not doing any copying.
              > >>
              > >> The admin/managed-server communication copies things to the managed
              > >server,
              > >> which then always recompiles the pages when hit.
              > >>
              > >> -Greg
              > >>
              > >> -----------------------------------------------------------
              > >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
              > >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
              > >>
              > >> "Robert Coonrad" <[email protected]> wrote in message
              > >> news:[email protected]...
              > >> >
              > >> > check out post 8366...i found that i was not preserving
              > >> > the lastmodified date on my jsps and this was causing
              > >> > unnecessary re-compilation.
              > >> >
              > >> > hope it helps...
              > >> > bobc
              > >> >
              > >> > "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
              > >> > >I believe I have exhausted all permutations of EARing/notEARing,
              > >> > >WARing/notWARing, placing precompiled jsp class files in
              > >WEB-INF/classes,
              > >> > >placing them in a static location and setting workingDir to that
              > >> location,
              > >> > >combinations of the above.
              > >> > >
              > >> > >No matter what, the managed server re-compiles pages the first time
              > >they
              > >> > >are
              > >> > >hit. Non admin/managed-server I have no problems.
              > >> > >
              > >> > >Can anyone from BEA comment on this problem? Or give me a workaround
              > >> > >for
              > >> > >getting a cluster working with precompiled jsps?
              > >> > >
              > >> > >-Greg
              > >> > >
              > >> > >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
              > >> > >news:[email protected]...
              > >> > >> Grrr... The JSP engine is extremely frustrating! I've spent many
              > >hours
              > >> > >> fighting the "staleness" checker in WL. I've been through all
              > >of the
              > >> > >> newsgroup messages pertaining to pre-compiling, etc., and I've
              > >gotten
              > >> > >> pre-compilation working on single-server deployments, but
              > >admin/managed
              > >> > >> server deployments have me beat.
              > >> > >>
              > >> > >> WL6.1, SP1, Solaris
              > >> > >>
              > >> > >> I've done the pageCheckSeconds=-1 and the workingDir is set to
              > >a
              > >fixed
              > >> > >> place. The fixed place contains pre-compiled versions of all
              > >jsps
              > >> > >made on
              > >> > >> that machine using jspc not 20 minutes earlier using the JSP files
              > >> > >in the
              > >> > >> exploded EAR file used by the admin server as the model for managed
              > >> > >> servers.. The managed servers are on the same machine.
              > >> > >>
              > >> > >> When the admin server gives an application to a managed server,
              > >the
              > >> > >managed
              > >> > >> server creates a temporary directory containing all of the webapp
              > >> > >> components, etc. The file timestamps on these files is the set
              > >by
              > >> > >the
              > >> > >> copying process to the time of the managed server boot
              > >(why?!?!????!?),
              > >> > >so
              > >> > >> the staleness check always thinks they are new and could care
              > >less
              > >> > >what
              > >> > >> precompiled jsps I have in my workingDir, the WEB-INF/classes
              > >> directory,
              > >> > >or
              > >> > >> anywhere else. The pageCheckSeconds=-1 seems to be completely
              > >ignored
              > >> > >in
              > >> > >> this scenario.
              > >> > >>
              > >> > >> If I tell the managed server to precompile everything on boot
              > >(about
              > >> > >45
              > >> > >> minutes for this app) it will create versions of the classes that
              > >match
              > >> > >th
              > >> > >e
              > >> > >> new JSP file timestamps, but this does not even survive a reboot
              > >of
              > >> > >the
              > >> > >> managed server because it AGAIN creates a new temp version of
              > >> everything
              > >> > >on
              > >> > >> the next reboot with new timestamps.
              > >> > >>
              > >> > >> If I wait for the managed server to boot and find the directory
              > >like
              > >> > >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
              > >> > >copy
              > >> > >> (via cp -pr to retain timestamps) all of the original webapp
              > >components
              > >> > >on
              > >> > >> top of the temp versions, the staleness checker is happy and the
              > >> > >> pre-compiled versions work fine.
              > >> > >>
              > >> > >> There HAS to be a way to package pre-compiled versions of the
              > >JSPs
              > >> > >in the
              > >> > >> "model" application in the admin server and keep from having to
              > >> precompile
              > >> > >> the JSPs on every managed server every time managed server is
              > >booted..
              > >> > >>
              > >> > >> It would help if we had a way to bypass the staleness checking
              > >> > >completely..
              > >> > >> Or you guys should make the timestamps on the files copied by
              > >the
              > >> > >> admin/managed deployment process match properly so the staleness
              > >> checker
              > >> > >> doesn't think the JSP is different.
              > >> > >>
              > >> > >> It would also help if the engineer who wrote this could explain
              > >the
              > >> > >rules
              > >> > >> being implemented by the staleness checker. So far all the messages
              > >> > >in
              > >> > >the
              > >> > >> newsgroup have amounted to point solutions for problems without
              > >a
              > >good
              > >> > >> understanding of what the engine is checking for and/or doing
              > >under
              > >> > >the
              > >> > >> covers. Looking at the generated .java files for the JSP pages
              > >helps,
              > >> > >but
              > >> > >> it is not good enough...
              > >> > >>
              > >> > >> Anyone out there have a working admin/managed server JSP application?
              > >> > >> -Greg
              > >> > >>
              > >> > >> -----------------------------------------------------------
              > >> > >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
              > >> > >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
              > >> > >>
              > >> > >>
              > >> > >>
              > >> > >
              > >> > >
              > >> >
              > >>
              > >>
              > >
              > >
              >
              [att1.html]
              

  • Creating Weblogic domain with Admin Server and managed servers on different

    I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.

    Whilst the method that Lawrence gives can result in a domain that is perfectly functional, it is a method that can result in errors as you are having to enter the same information twice. Also you will create two admin servers, as the second domain creation will have the console added to it on the renamed admin server and this will give issues.
    The best method to create a domain spamming multiple physical machines, is to create the domain with all the components on the first machine. This means planning the domain and making sure all components are added once; so having the information about the domain written out is wise. Ensure that the WLS software is installed in the same path on each machine before starting.
    Then copy the domain that you have created from one machine to the other, keeping the same paths. You can simply copy (I've used this method multiple times without issue) but the supported way would be to use the WLST PACK and UNPACK methods. These create and extract domains from templates. Some more information on these is given here -> http://docs.oracle.com/cd/E13179_01/common/docs100/pack/intro.html#wp1069056

  • Can we create multiple admin servers in one one weblogic domain.

    Hi All,
    Can we create multiple admin servers in one one weblogic domain.
    if yes, please let me know.
    Thanks

    http://download.oracle.com/docs/cd/E21764_01/web.1111/e13716/toc.htm
    Not through the configuration wizard.
    To handle admin server availability (the admin server is not clusterable). This means that if the admin server goes
    down, you cannot administer your WebLogic Server domain until you bring it back up. In most cases, you may
    not be too concerned if the admin server goes down because all you need to do is restart it. If you use the node
    manager to start the admin server, the node manager can automatically restart a failed admin server just like it can any other server.
    What happens if the machine where the admin server runs fails in such a way that you cannot restart the admin server?
    The answer is simple if you prepare for this event. Proper operation of the admin server relies on several configuration files
    and any application files it controls. Typically, the best thing to do is to store the admin server's directory tree on a shared disk.
    As long as the configuration and application files are accessible, you can restart the admin server on another machine. It is up
    to you to make sure that you don't have more than one admin server running at a time. If the new machine can assume the
    original admin server's Listen Address (or if it was not set), you can simply start the admin server on the new machine without
    any configuration changes.
    Otherwise, you will need to change the admin server's Listen Address. Since the managed servers ping the admin server URL every
    10 seconds until it comes back up, you need to devise a way for the admin server URL to allow the managed server to find the restarted
    admin server on the new IP address. The easiest way to achieve that is using a DNS name that maps to both IP addresses, or better yet
    that is dynamically updated to point to the correct location of the admin server. If this is a graceful shutdown and migration, use the
    WebLogic Console to change the Listen Address just before shutting down the admin server. If not, you will need to edit the config.xml
    file by hand to replace the old Listen Address with the new one. Typically, it is recommended to plan ahead so that everything you need is
    already in place to make admin server failover as painless as possible.

  • How do I create an Integration Domain with 3 servers ?

    Hi,
    I would like to create a WLI domain with three servers:<br>
    Ø     One for the administration console;<br>
    Ø     One for WLI;<br>
    Ø     And the last to deploy EJB Session (which are the service called by WLI)<br><br>
    To create the domain, I use the WLI 8.1 SP4 Configuration Wizard.<br><br>
    After creating the domain with 3 services, I have not succeeded to start the WLI Server.<br><br>
    For another test, I would like to create a WLI domain with two servers:<br>
    Ø     One for the administration console and WLI;<br>
    Ø     And the last to deploy EJB Session<br><br>
    To create the main server, I have used the configuration wizard. For the other, I have used the console administration. With this configuration, the message brocker was not initialised.<br><br>
    For the last test, I have created a domain with single server and I had no errors.<br><br>
    <b>So, my question is: What is the method to create a domain with three servers?</b><br><br>
    Thanks for your help<br> <br><br><br>
    <b>Case 1: Test to define 3 servers</b>
    <4 nov. 2005 14 h 45 CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "etsoWLI" for domain "complexDomain">
    The WebLogic Server did not start up properly.
    weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [com.bea.wli.management.BPMComponentInitializationException: Failed to initialize ProcessConfiguration module]
    at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:92)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
    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 weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
    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)
    Reason: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [com.bea.wli.management.BPMComponentInitializationException: Failed to initialize ProcessConfiguration module]
    <4 nov. 2005 14 h 45 CET> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [com.bea.wli.management.BPMComponentInitializationException: Failed to initialize ProcessConfiguration module]>
    <br> <br>
    <b>Case 2 : Test to define 2 servers</b><br>
    <4 nov. 2005 15 h 03 CET> <Error> <WLI-Core> <BEA-484037> <Process Tracking failed to initialize properly. Tracking data cannot be recorded for process typ
    e "/MailProcess/processes/process02.jpd".>
    <4 nov. 2005 15 h 03 CET> <Error> <WLI-Core> <BEA-481000> <The Message Broker is not initialized>
    <4 nov. 2005 15 h 03 CET> <Error> <WLW> <000000> <Failed to register subscriptions for JPD /MailProcess/processes/process02.jpd
    java.lang.RuntimeException: The Message Broker is not initialized
    at com.bea.wli.broker.MessageBroker.getMessageBroker(MessageBroker.java:277)
    at com.bea.wli.control.MBUtils.registerSubscriptionRules(MBUtils.java:99)
    at com.bea.wli.bpm.runtime.JpdDispFile$3.run(JpdDispFile.java:903)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at com.bea.wli.bpm.runtime.JpdDispFile.registerSubscriptions(JpdDispFile.java:912)
    at com.bea.wli.bpm.runtime.JpdDispFile.<init>(JpdDispFile.java:212)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    at com.bea.wlw.runtime.core.dispatcher.DispUnit.loadDispFile(DispUnit.java:219)
    at com.bea.wlw.runtime.core.dispatcher.DispUnit.<init>(DispUnit.java:153)
    at com.bea.wlw.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:578)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.getDispUnit(HttpServerHelper.java:501)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executeGetRequest(HttpServerHelper.java:541)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doGet(HttpServer.java:81)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    javax.management.InstanceNotFoundException: lastEtsoDomain:Location=etsoMain,Name=MsgBroker,Type=MsgBrokerRuntime (admin server:true)
    at weblogic.management.internal.MBeanHomeImpl.getMBean_helper(MBeanHomeImpl.java:145)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:130)
    at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:557)
    at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:549)
    at weblogic.management.internal.AdminMBeanHomeImpl.getRuntimeMBean(AdminMBeanHomeImpl.java:580)
    at com.bea.wli.management.MBeanHelper.getMsgBrokerRuntimeMBean(MBeanHelper.java:549)
    at com.bea.wli.bpm.runtime.__broker.listSubscriptions(__broker.java:178)
    at com.bea.wli.bpm.runtime.__broker._jspService(__broker.java:833)
    at com.bea.wlw.runtime.core.dispatcher.ServiceView.dispatchToPage(ServiceView.java:269)
    at com.bea.wlw.runtime.core.dispatcher.ServiceView.forward(ServiceView.java:438)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executeGetRequest(HttpServerHelper.java:617)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doGet(HttpServer.java:81)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    To use 3 managed servers with Weblogic, I must a cluster environment.
    Weblogic say: "WebLogic Integration domain that includes an administrative server and one or more managed servers must include a cluster. A WebLogic Integration domain that includes an administrative server and one or more managed servers without a cluster is an unsupported configuration."
    Fred

  • Issue - login to Hyperion Planning 11.1.2.0 with admin user

    Hi,
    I am using Hyperion 11.1.2.0 version. I have an issue with the login to Hyperion Planning using admin credentials. The error which i am facing is "An Error occured while processing this page. Check the log for details." Please help me out.
    But i am able to login to Essbase, Shared Services & Work space with the admin user.
    Thanks
    Dhamu

    Hi john,
    I went through the log file, but could not trace what is the exact issue, can you please have a look at the below log and tell me what needs to be done for corrective actions
    The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Notice> <Security> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139237> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Notice> <Security> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139237> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Info> <WebLogicServer> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139252> <BEA-000307> <Exportable key maximum lifespan set to 500 uses.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Info> <Server> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139424> <BEA-002610> <Dynamic Listener Service initialized.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Notice> <Server> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139424> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on 127.0.0.1:8343 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Notice> <Server> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139424> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:8300 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Notice> <Server> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139424> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.47.33.205:8343 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Notice> <Server> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139424> <BEA-002613> <Channel "Default" is now listening on 10.47.33.205:8300 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Notice> <WebLogicServer> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139440> <BEA-000330> <Started WebLogic Managed Server "Planning0" for domain "EPMSystem" running in Production Mode>
    ####<Oct 19, 2011 10:25:39 AM GMT+05:30> <Info> <Server> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000139549> <BEA-002635> <The server "AdminServer" connected to this server.>
    ####<Oct 19, 2011 10:25:40 AM GMT+05:30> <Info> <JMX> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000140065> <BEA-149511> <Established JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://10.47.33.205:7001/jndi/weblogic.management.mbeanservers.domainruntime.>
    ####<Oct 19, 2011 10:25:42 AM GMT+05:30> <Notice> <WebLogicServer> <Korbsbvm19> <Planning0> <Main Thread> <<WLS Kernel>> <> <> <1319000142158> <BEA-000365> <Server state changed to RUNNING>
    ####<Oct 19, 2011 10:25:42 AM GMT+05:30> <Notice> <WebLogicServer> <Korbsbvm19> <Planning0> <Main Thread> <<WLS Kernel>> <> <> <1319000142174> <BEA-000360> <Server started in RUNNING mode>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param verbose initialized to: true>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param packagePrefix initialized to: jsp_servlet>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param compilerclass initialized to: null>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param compileCommand initialized to: javac>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param compilerval initialized to: javac>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param pageCheckSeconds initialized to: -1>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param encoding initialized to: null>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param superclass initialized to null>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: param workingDir initialized to: C:\Documents and Settings\admin\Local Settings\Temp\1\admin\servers\Planning0\tmp\_WL_user\PLANNING_11.1.2.0\3i5tnd>
    ####<Oct 19, 2011 10:26:34 AM GMT+05:30> <Info> <ServletContext-/HyperionPlanning> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1319000194845> <BEA-000000> <JspServlet: initialization complete>
    ####<Oct 19, 2011 10:30:56 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000456074> <BEA-320143> <Scheduled 1 data retirement tasks as per configuration.>
    ####<Oct 19, 2011 10:30:56 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000456090> <BEA-320144> <Size based data retirement operation started on archive HarvestedDataArchive>
    ####<Oct 19, 2011 10:30:56 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000456090> <BEA-320145> <Size based data retirement operation completed on archive HarvestedDataArchive. Retired 0 records in 0 ms.>
    ####<Oct 19, 2011 10:30:56 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000456090> <BEA-320144> <Size based data retirement operation started on archive EventsDataArchive>
    ####<Oct 19, 2011 10:31:18 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000478933> <BEA-320145> <Size based data retirement operation completed on archive EventsDataArchive. Retired 22 records in 22,843 ms.>
    ####<Oct 19, 2011 10:39:00 AM GMT+05:30> <Info> <JDBC> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000940034> <BEA-001128> <Connection for pool "EPMSystemRegistry" closed.>
    ####<Oct 19, 2011 10:39:00 AM GMT+05:30> <Info> <JDBC> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319000940049> <BEA-001128> <Connection for pool "EPMSystemRegistry" closed.>
    ####<Oct 19, 2011 11:30:56 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319004056833> <BEA-320143> <Scheduled 1 data retirement tasks as per configuration.>
    ####<Oct 19, 2011 11:30:56 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319004056943> <BEA-320144> <Size based data retirement operation started on archive HarvestedDataArchive>
    ####<Oct 19, 2011 11:30:56 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319004056943> <BEA-320145> <Size based data retirement operation completed on archive HarvestedDataArchive. Retired 0 records in 0 ms.>
    ####<Oct 19, 2011 11:30:56 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319004056943> <BEA-320144> <Size based data retirement operation started on archive EventsDataArchive>
    ####<Oct 19, 2011 11:31:37 AM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319004097555> <BEA-320145> <Size based data retirement operation completed on archive EventsDataArchive. Retired 24 records in 40,596 ms.>
    ####<Oct 19, 2011 12:30:56 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319007656183> <BEA-320143> <Scheduled 1 data retirement tasks as per configuration.>
    ####<Oct 19, 2011 12:30:56 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319007656183> <BEA-320144> <Size based data retirement operation started on archive HarvestedDataArchive>
    ####<Oct 19, 2011 12:30:56 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319007656199> <BEA-320145> <Size based data retirement operation completed on archive HarvestedDataArchive. Retired 0 records in 32 ms.>
    ####<Oct 19, 2011 12:30:56 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319007656199> <BEA-320144> <Size based data retirement operation started on archive EventsDataArchive>
    ####<Oct 19, 2011 12:31:04 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319007664355> <BEA-320145> <Size based data retirement operation completed on archive EventsDataArchive. Retired 24 records in 8,156 ms.>
    ####<Oct 19, 2011 1:30:56 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319011256083> <BEA-320144> <Size based data retirement operation started on archive HarvestedDataArchive>
    ####<Oct 19, 2011 1:30:56 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319011256083> <BEA-320143> <Scheduled 1 data retirement tasks as per configuration.>
    ####<Oct 19, 2011 1:30:56 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319011256083> <BEA-320145> <Size based data retirement operation completed on archive HarvestedDataArchive. Retired 0 records in 0 ms.>
    ####<Oct 19, 2011 1:30:56 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319011256083> <BEA-320144> <Size based data retirement operation started on archive EventsDataArchive>
    ####<Oct 19, 2011 1:31:06 PM GMT+05:30> <Info> <Diagnostics> <Korbsbvm19> <Planning0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319011266520> <BEA-320145> <Size based data retirement operation completed on archive EventsDataArchive. Retired 24 records in 10,437 ms.>
    Thanks
    Dhamu

  • Oracle RAC with Admin tools

    Hello!
    I use Weblogic Server 10.3.2. I have a portal application and I want to manage the content with Portal Administration Console from admin-tools.war . Admin-tools is a part of my portal application. I eclipse I check for my ear project on Project Facets : Admin Console, Admin Framework, Portal Application Services, Portal Customizations Framework.
    I have a cluster with two servers. As a database I use Oracle 10 with two instances : instance 1, instance 2. I have created my domain with wizard and I checked RAC Multidatasources.
    All datasources and multidatasources are targeted to my weblogic cluster, also where is deployed my app and Portal Administration Console ( admin-tools.war).
    I use the multidatasources :
    Multidatasource Name : cgDataSource JNDI:      cgDataSource     Load-Balancing     
    Oracle Driver for data sources cgDataSource-rac0, cgDataSource-rac1 : oracle.jdbc.xa.client.OracleXADataSource
    MultiDataSource Name : cgDataSource-nonXA     JNDI : cgDataSource-nonXA      Load-Balancing     Oracle Driver:
    Oracle driver for datasources from multidatasource : oracle.jdbc.OracleDriver . Supports Global Transaction
    Name : p13nDataSource
    JNDI : p13n.trackingDataSource,p13n.sequencerDataSource,cm.sequencerDataSource,p13n.leasemanager,p13n.dataSyncDataSource,p13n.entitlementsDataSource,p13n.jobManagerDataSource,p13n.quiescenceDataSource,p13n.credentialsDataSource     Load-Balancing     
    Oracle driver for datasources from multidatasource: oracle.jdbc.OracleDriver .
    !!DOESN'T Supports Global Transaction!!
    Name: portalDataSource     
    JNDI : weblogic.jdbc.jts.commercePool contentDataSource contentVersioningDataSource portalFrameworkPool     Load-Balancing     
    Oracle driver for datasources from multidatasource: oracle.jdbc.OracleDriver .
    Supports Global Transaction
    Name: portalDataSourceAlwaysXA     
    JNDI : portalFrameworkPoolAlwaysXA     Load-Balancing     
    Oracle driver for datasources from multidatasource: oracle.jdbc.xa.client.OracleXADataSource
    Name: portalDataSourceNeverXA JNDI: portalFrameworkPoolNeverXA
    Oracle driver for datasources from multidatasource: oracle.jdbc.xa.client.OracleXADataSource
    But when I try to add a content, after a server restart, I receive the following error :
    <Error> <PortalAdminTools> <sun1> <Server-0> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1289472419642> <BEA-415097> <A RepositoryException was thrown: java.sql.BatchUpdateException: ORA-00001: unique constraint (WEBLOGIC_PORTAL_PROD.PK_CM_PROPERTY) violated
    com.bea.content.RepositoryException: java.sql.BatchUpdateException: ORA-00001: unique constraint (WEBLOGIC_PORTAL.PK_CM_PROPERTY) violated
         at com.bea.content.internal.server.common.dbaction.Batcher.processWithRetries(Batcher.java:148)
         at com.bea.content.internal.server.common.dbaction.Batcher.processAnyRemainingItems(Batcher.java:86)
         at com.bea.content.repo.internal.server.dao.PropertyDao.insert(PropertyDao.java:383)
         at com.bea.content.repo.internal.server.persister.JDBCNodePersister.createNode(JDBCNodePersister.java:148)
         at com.bea.content.repo.internal.server.logic.NodeOpsLogic.create(NodeOpsLogic.java:227)
         at com.bea.content.repo.internal.server.bean.NodeOpsBean.create(NodeOpsBean.java:106)
         at com.bea.content.repo.internal.server.bean.RepoNodeOps_ehgg7y_ELOImpl.create(RepoNodeOps_ehgg7y_ELOImpl.java:323)
         at com.bea.content.repo.internal.client.common.Node.create(Node.java:123)
         at com.bea.content.spi.internal.NodeOpsImpl.createNode(NodeOpsImpl.java:823)
         at com.bea.content.spi.internal.ExtendedNodeOpsImpl.createNodeWithNodeTypeAndObjectClassAndWorkflow(ExtendedNodeOpsImpl.java:81)
         at com.bea.content.federated.internal.delegate.LatestInterfaceVersionWrapper.invoke(LatestInterfaceVersionWrapper.java:72)
         at $Proxy457.createNodeWithNodeTypeAndObjectClassAndWorkflow(Unknown Source)
         at com.bea.content.federated.internal.filter.logging.NOPSLoggingFilter.createNodeWithNodeTypeAndObjectClassAndWorkflow(NOPSLoggingFilter.java:111)
         at com.bea.content.federated.internal.delegate.NodeLogic.createNodeWithType(NodeLogic.java:275)
    Caused By: java.sql.BatchUpdateException: ORA-00001: unique constraint (WEBLOGIC_PORTAL.PK_CM_PROPERTY) violated
         at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:629)
         at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9447)
         at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:211)
         at weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:191)
    What is the problem? Please tell me if you need more details about my configuration and problem.

    This issue is beyond simple WLS JDBC. I suggest opening a WLS portal bug.

  • Opening Files with Admin Privleges

    Hello all:
    How do you open a file with admin privileges once you are in the program? Is it possible to run a program with admin privileges? The reason I ask is that I installed the GUI version of vim and need to be able to open some files which will be read-only unless I supply an administrator password.
    John

    You can open any application capable of running in Mac OS X natively as root by entering:
    sudo /path/to/application/Contents/MacOS/application
    in the Terminal, which is in the /Applications/Utilities/ folder. This works on a per-run basis, and the command will need to be entered each time you want to launch the application. Other methods exist which only require the password to be entered once, and work on a per-application basis.
    (18291)

  • Additional User with admin rights

    Hi all,
    i checked the documentation but i could not found a possibility to create an additional user with admin rights to access the Vibe Management Console.
    Does anybody know if this is possible and how to do this?
    Thanks in advance
    Alex

    Hi Willem,
    thank you for the great post. It did the job very well.
    Alex
    >>> <[email protected]> schrieb am 1.8.2013 um 07:46 AM:
    > arlorenz;2275156 Wrote:
    >> Hi all,
    >>
    >> i checked the documentation but i could not found a possibility to
    >> create an additional user with admin rights to access the Vibe
    >> Management Console.
    >> Does anybody know if this is possible and how to do this?
    >>
    >> Thanks in advance
    >>
    >> Alex
    >
    > Hey Alex,
    >
    > Yes, that's possible. It's somewhat a twofold/threefold process, as
    > you have to give an accounts right to administer the zone, and then also
    > have to give that account rights to the personal workspace root (to be
    > able create/delete user accounts) and any workspaces that need to be
    > administered.
    >
    > I always create an vibe-admins group (local group) that gets the rights
    > to the zone and workspace roots. Then add the needed users to that
    > group.
    >
    > Access for the zone can be set within the administration console:
    > https://www.novell.com/documentation...ata/bk4saug.ht
    > ml
    >
    > Then add the needed rights on the workspace roots, Global, personal &
    > team workspaces.
    >
    >
    > !Do note that admin is the only user that is not allowed to get
    > blocked. Other admin users can be filtered out via ACL's.
    >
    >
    > Cheers,
    > Willem

  • How to add user with admin priviledges to  multiple machines

    Hi all,
    I would like to be able to create a local ARD user on each machine on the network, with admin privileges on the machine. Is this possible?
    The custom client installer seems to only allow adding standard users. Is there away I can create a Unix command that I could send to each machine, to add an administrator user? Your advice would be greatly appreciated.

    Since machines ship with ARD 2 already installed, rather than go through the hassle of creating a Client package and having to edit that, you can simply run a shell script to take care of everything.
    We utilze a BASH script to create the ARD user, set the password of the user, hide it in the login window, add the user to the sudoers file (just to make sure the user can sudo), and add the path to kickstart to the PATH variable in the default .profile (/etc/profile) so that you can use kickstart without having to type the entire path.
    Script follows:
    #!/bin/bash
    # add kickstart to path
    echo "PATH="\"/bin:/sbin:/usr/bin:/usr/sbin:/System/Library/CoreServices/RemoteManag ement/ARDAgent.app/Contents/Resources:/Developer/Tools"\"" >> /etc/profile
    export path
    # add ARD user
    niutil -create . /users/arduser
    niutil -createprop . /users/arduser gid 499
    niutil -createprop . /users/arduser uid 499
    niutil -createprop . /users/arduser shell /bin/bash
    niutil -createprop . /users/arduser home /private/var
    niutil -createprop . /users/arduser realname ard
    niutil -createprop . /users/arduser shadowpasswd
    niutil -appendprop . /groups/admin users arduser
    # now set the passwd for the ard user
    dscl . -passwd /Users/arduser ardpass
    # now add to the sudoers file
    echo "arduser ALL=(ALL) ALL" >> /etc/sudoers
    # now hide the ARD user from the loginwindow process
    mkdir /var/temp/
    cp /Library/Preferences/com.apple.loginwindow.plist /var/temp/com.apple.loginwindow.bak
    defaults write /Library/Preferences/com.apple.loginwindow HiddenUsersList -array-add arduser
    /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/ki ckstart -configure -users arduser -access -on -privs -all
    exit 0
    Just copy that into a text file, chmod it to 755 and you can then run it on the machine. We will put it at the root of the hard drive, run it, and then remove it. If you want the script to delete itself, just put the following before "exit 0":
    rm $0
    That will delete the file.
    Hope that helps out.
    Steve
    XServe G5, XServe RAID (1TB), MacBook Pro Mac OS X (10.4.6)

  • In my Iphone 5, Nothing on my App Store is working its displaying blank (Except for Genius section). I've tried to uninstall and install itunes and all its component but still it doen't fix. Not sure if its problem with apple servers. Someone help please!

    In my Iphone 5, Nothing on my App Store is working,  its displaying blank (Except for Genius section). I've tried to uninstall and install itunes and all its component in my desktop but still it doesn't fix the app store issue. Not sure if its problem with apple servers. Someone help please!

    settigns>itunes and app store to make sure you are signed in.. If  you are, you will see your account name..... anyhow, click your account name, sign out and sign back in
    also go to to settings>general>reset and reset network settings... if that doesnt work settings>general>reset and reset all settings!
    one of those shall work. The last step would be to restore your device (apple.com/support) HT1414

  • MacBook Pro battery had accumulated more than a 1000 charges, and stopped functioning unexpectedly. Went and got the battery replaced. Just saw that SMC Firmware 1.6 update deals with this. Possible to get my money back?

    MacBook Pro battery had accumulated more than a 1000 charges, and stopped functioning unexpectedly. Went and got the battery replaced. Just saw that SMC Firmware 1.6 update deals with this. Possible to get my money back?

    The firmware update corrects an error that may occur, however the techs would have checked the condition of the battery prior to installing a new one.  If the battery was questionable, the firmware update was really not too important.
    You can check the battery condition by going to the apple, left side of the menu bar, About This Mac, More Info, System Report, Hardware, Power and see what it says about Cycle Count, Condition, Capacity: Condition anything but Normal needs to be checked and may need to be replaced.
    The cycle count of 1,000 charge cycles is the typical life of a Lithium-Ion battery, the point at which the capacity drops to 80% of the as built capacity.

  • Ipod doesn't work on speakers but headphones are fine and speaker works with iPhone. Possible connector issue? Any thoughts on how I can get the fixed?

    ipod doesn't work on speakers but headphones are fine and speaker works with iPhone. Possible connector issue? Any thoughts on how I can get the fixed?

    Try:
    - Reset the iOS device. Nothing will be lost
    Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
    least ten seconds, until the Apple logo appears.
    - Reset all settings
    Go to Settings > General > Reset and tap Reset All Settings.
    All your preferences and settings are reset. Information (such as contacts and calendars) and media (such as songs and videos) aren’t affected.
    - Restore from backup. See:       
    iOS: How to back up           
    - Restore to factory settings/new iOS device.

  • Need help: Deployment of application on multiple admin servers in a cluster

    Forwarding this to the weblogic.developer.interest.clustering group as well:
              Hi,
              I have created two admin servers and one managed server on each of them. Then I have added these two managed servers to both the admin servers.
              So I have two admin servers and a cluster having two managed servers.
              Now, if I deploy through one of the admin servers to the cluster cotaining both managed servers, i can see the deployment happening when I log on to the admin server from which I tried the deployment. IF i log onto the other admin server I do not see the deployment happening.
              Interestingly, if I restart both the managed servers from the second admin server, i can see the deployment from the same one but now, if I loginto the first admin server, I see the deployment missing!
              Is this a normal behaviour? Is there any way in which we can see the deployment from both the admin servers?
              Thanks in advance,
              -Sen

    Why do you have two admin servers? How many config.xml files exist? Are both admin servers pointing to the same domain if so how is the domain shared? Are both admin servers on the same box? Are they supposed to be the same domain? I'm just trying to understand why it is configured this way.
              -Jesus

  • What does this statement mean: "There is a problem with your authentication, possibly due to inactivity. For your safety, you have been logged out and must sign in again to continue?"

    I am able to make it to the site for about 2 seconds and then I am quickly logged off and the statement, "There is a problem with your authentication, possibly due to inactivity. For your safety, you have been logged out and must sign in again to continue."
    I don't have a clue as to the problem but since this is impacting my participation in these classes and ultimately could have a negative impact on my grade, I am more than a little concerned!

    Have you allowed this site to set cookies?

Maybe you are looking for