Deploy in cluster

HI,
we have a clustered env for our production system. I am trying to deploy an SDA file from SDM of central instance. I am getting the following error.
Error: An error occured while starting a cluster instance.
Error: There is no control instance running in the cluster:
Name:JM_T1137182930718_hostname |Host:hostname |State:5|
Info:|Name:JC_hostname |Host:hostname |State:5|
Info:Please check if there are running cluster instances.
do i need to configure something in sdm of our central instance?
please help us.
Thank you

As per the previous message, it should work if the
cluster is installed correctly.
With a clustered installation the SCS (SAP Central
Services) would be installed using a virtual hostname.
Later when the Central instance is installed it must
refer to this logical hostname for the SCS.
My guess is that SDM is using the hostname of the CI
instead of the SCS  logical hostname.
When you installed the Central Instance, did you use
the HA instructions for installing a Central Instance ?
regards
Tom

Similar Messages

  • WLS6sp2 Hot deployment in cluster does not work

              I have two WLS6sp2 servers in cluster in two different machines. There is an EJB
              deployed in the cluster that works fine. Now I go to the console and I undeploy
              it: the servers show a message of "ejb undeployed". Now I activate the "deploy"
              checkbox again: the following error appears:
              weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested exception
              is:
              javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
              stub to a name that is currently bound to a replica-aware stub; remaining name
              javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
              stub to a name that is currently bound to a replica-aware stub; remaining name
              The object is obviously clusterable (it is a stateless EJB with "home-is-clusterable=true").
              It has been deployed to the cluster target. When is working it is load balanced
              between both servers. It deploys perfectly when starting up both servers, but
              hot deployment does not work.
              This works fine when only one server is up.
              ¿Is not possible to do hot deployment in cluster?
              

    Hm, where are you seeing the javax.naming.NameAlreadyBoundException? In one of your managed
              servers, in all of your managed server, or in your admin server?
              If you see this in your admin server, then this means you got your admin joined in the cluster,
              which is not good. Remove it from the cluster if this is so.
              Gene
              "David Agudo" <[email protected]> wrote in message news:[email protected]...
              >
              > Yes, target="mycluster".
              >
              > "Gene Chuang" <[email protected]> wrote:
              > >Did you target the ejb to the cluster, or to each individual Node in
              > >your cluster? There is a
              > >difference...
              > >
              > >Gene
              > >
              > >"David Agudo" <[email protected]> wrote in message news:[email protected]...
              > >>
              > >> I have two WLS6sp2 servers in cluster in two different machines. There
              > >is an EJB
              > >> deployed in the cluster that works fine. Now I go to the console and
              > >I undeploy
              > >> it: the servers show a message of "ejb undeployed". Now I activate
              > >the "deploy"
              > >> checkbox again: the following error appears:
              > >>
              > >> weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB;
              > >nested exception
              > >> is:
              > >> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              > >replica-aware
              > >> stub to a name that is currently bound to a replica-aware stub; remaining
              > >name
              > >> ''
              > >> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              > >replica-aware
              > >> stub to a name that is currently bound to a replica-aware stub; remaining
              > >name
              > >> ''
              > >>
              > >> The object is obviously clusterable (it is a stateless EJB with "home-is-clusterable=true").
              > >> It has been deployed to the cluster target. When is working it is load
              > >balanced
              > >> between both servers. It deploys perfectly when starting up both servers,
              > >but
              > >> hot deployment does not work.
              > >>
              > >> This works fine when only one server is up.
              > >>
              > >> ¿Is not possible to do hot deployment in cluster?
              > >>
              > >
              > >
              >
              

  • How to deploy WebLogic Cluster on a Blade?

    Hi, I am looking for recommendations on how ( if it makes sense ) to deploy WebLogic
    Cluster on the (Intel) Blade HW. The question is, actually, caused by the fact
    that the Blade is totally redundant and load-balanced HW where the requests are
    managed by a Big-IP module ( and redirected to the IPs on the internal Blade Cassettes
    One of possible solutions, we discuss now, is "either-or", i.e. let's discard
    the App.Server cluster and use the HW cluster. This might work for the request
    load balance but we loose all other, out-of-the-box, cluster features like session,
    EJB, JNDI and so on failover and balance features.
    Any notes with this regard will be greatly appreciated.
    Thanks, - Michael
    P.S. I repeated the same question om "cluster" Newsgroup but have not seen any
    responds so far.

    It sounds like you're getting request routing and fail-over in front of
    WLS with the Big-IP. Typically people would enable WLS clustering to
    get replicated HTTP sessions in an environment like this.
    -- Rob
    Michael Poulin wrote:
    Hi, I am looking for recommendations on how ( if it makes sense ) to deploy WebLogic
    Cluster on the (Intel) Blade HW. The question is, actually, caused by the fact
    that the Blade is totally redundant and load-balanced HW where the requests are
    managed by a Big-IP module ( and redirected to the IPs on the internal Blade Cassettes
    One of possible solutions, we discuss now, is "either-or", i.e. let's discard
    the App.Server cluster and use the HW cluster. This might work for the request
    load balance but we loose all other, out-of-the-box, cluster features like session,
    EJB, JNDI and so on failover and balance features.
    Any notes with this regard will be greatly appreciated.
    Thanks, - Michael
    P.S. I repeated the same question om "cluster" Newsgroup but have not seen any
    responds so far.

  • Error during application deployment in cluster

    Hi All,
              I am seeing a weird error when I deploy my application in 2 node cluster. Few months back, the same cluster worked perfectly alright. The error relates to lookup at localhost:7001 which is no where in the configuration as admin server url is http://srai-xp:7001. I created a new domain and see the same problem.
              Any pointers are greatly appreciated.
              Thanks
              --shashi
              Here is the error log:
              D:\apps\bea\user_projects\domains\nclusterdomain>startManagedWebLogic.cmd NodeSR http://srai-xp:7001
              D:\apps\bea\user_projects\domains\nclusterdomain>echo off
              CLASSPATH=CR190380_81sp3.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jax-qname.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\li
              jsafe.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jsafejce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\asn1.jar;;C:\j2sd
              .4.2_04\lib\tools.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic.jar;d:\apps\bea\WEBLOG~1\common\eval\
              intbase\lib\pbserver44.jar;d:\apps\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\j2sdk1.4.2_04\jre\lib\rt.jar;d:\apps\bea\WEBLOG~1\server\lib\webservices.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_base.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_jce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb_jaas.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_license.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_provider.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\mysql-connector-java.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\nls_charset12.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\ojdbc14.jar;
              * To start WebLogic Server, use a username and *
              * password assigned to an admin-level user. For *
              * server administration, use the WebLogic Server *
              * console at http://[hostname]:[port]/console *
              <Mar 17, 2005 4:19:27 PM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
              Enter username to boot WebLogic server:weblogic
              Enter password to boot WebLogic server:
              <Mar 17, 2005 4:21:22 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.2_04-b05 fr
              Sun Microsystems Inc.>
              <Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://srai-xp:7001 to ch
              k if there exists a running admin server at this URL.>
              <Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
              <Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
              WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
              <Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://srai-xp:7001 to retriev
              the initial configuration.>
              <Mar 17, 2005 4:21:25 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file D:\apps\bea\user_projects\domains\nclusterdomain\NodeSR\No
              SR.log is opened. All server side log events will be written to this file.>
              <Mar 17, 2005 4:21:30 PM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
              <Mar 17, 2005 4:21:30 PM PST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "NodeSR" for domain "nclusterdomain">
              <Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster XCluster on 237.0.0.101:8050.>
              <Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of XCluster.>
              <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 153.32.158.12
              <Mar 17, 2005 4:22:08 PM PST> <Notice> <Cluster> <BEA-000102> <Joining cluster XCluster on 237.0.0.101:8050>
              <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "NodeSR" for domain "nclusterdomain" running i
              Production Mode>
              <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
              <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_de': Public ID references the old
              rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_fr': Public ID references the old
              rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_ja': Public ID references the old
              rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Mar 17, 2005 4:23:35 PM PST> <Warning> <J2EE> <BEA-160081> <The JMS connection factory resource EDCEventQCF declared in the EJB "EventManagerBean"
              part of application "edc-server" does not support XA. It cannot be used inside a transaction context.>
              javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
                      java.net.ConnectException: Connection refused: connect; No available router to destination]
              at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
              at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
              at javax.naming.InitialContext.init(InitialContext.java:219)
              at javax.naming.InitialContext.<init>(InitialContext.java:175)
              at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
              at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
              at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
              at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
              at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
              at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
              at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
              at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
              at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
              at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
              at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
              Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
              java.net.ConnectException: Connection refused: connect; No available router to destination
              at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
              at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
              ... 28 more
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Unable to create InitialContext ] - with nested exception:
              [javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is
                      java.net.ConnectException: Connection refused: connect; No available router to destination]]
              at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:770)
              at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
              at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
              at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
              at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
              at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
              at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
              at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
              at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
              at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
              at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
              <Mar 17, 2005 4:23:40 PM PST> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application edc-server.
              java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
              java.net.ConnectException: Connection refused: connect; No available router to destination
              at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
              at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
              at javax.naming.InitialContext.init(InitialContext.java:219)
              at javax.naming.InitialContext.<init>(InitialContext.java:175)
              at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
              at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
              at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
              at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
              at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
              at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
              at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
              at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
              at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
              at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
              at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
              --------------- nested within: ------------------
              weblogic.management.ManagementException: - with nested exception:
              [java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
                      java.net.ConnectException: Connection refused: connect; No available router to destination]
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2327)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
              >

    I checked all deployment descriptions and there are no references to t3://localhost:7001. Few months back, I had the complete clustering setup working on 2 machines and now when I deploy my application on same configuration, it fails with t3://localhost:7001 unreachable error. I created a new cluster configuration on one machine with 2 managed server and it deploys fine. Can not figure out what has changed ?

  • Web modules don't get deployed to cluster instance directory

    Hi,
    I have a domain with one cluster, which has one instance. Sometimes (!), the web aplications I deploy don't get unpacked in the directory {instanceRoot}/applications/j2ee-modules but only in {domainRoot}/applications/j2ee-modules. When that happens, they don't work and I cannot access them through their URL.
    I deploy them using the web admin console, enable the to the cluster in question. Everything goes ok (or at least the UI says so) and in the domain.xml I have this:
    <web-module availability-enabled="false" context-root="/myapp" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/myapp" name="myapp" object-type="user"/>
    <server...
    <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="myapp"/>
    <cluster...
    <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="myapp"/>
    In both the apps the were copied to the instance applications dir and in the ones that remained only in the domain applications dir (and do not work). In the latter, the location dir does not exist.
    Anyone has gone through any similar situation? This deployment process is a bit confusing for me, wrt instances, clusters, domains etc.
    Thanks!
    Jo�o.

    Thanks for the answer.
    But how is this mechanism controlled? Sometimes, the domain just doesn't seem to propagate the changes to the cluster instances (or stand-alone instances). For example, sometimes when I change a property of a data source through the admin gui of the domain, it does not get propagated to the desired instance config, even after restarting the whole system.
    I think that it may have something to do with the manual changes that I have to do sometimes in the domain.xml file (this is neede when you have huge config changes to be replicated in many servers).
    Is there any option to enforce the replication of the config from the domain to the instances? Or at least to make it verbose so that I can realize what is going on underneath.
    Thanks.

  • OSB Proxy Service deployed in cluster environment FTP issue

    Hi,
    I have a OSB 11g proxy service based on a FTP JCA adapter. Here are the JCA settings:
    <connection-factory location="JNDI_FILE_TOKEN" UIincludeWildcard="FILENAME_TOKEN"/>
      <endpoint-activation portType="Get_ptt" operation="Get">
        <activation-spec className="oracle.tip.adapter.ftp.inbound.FTPActivationSpec">
          <property name="DeleteFile" value="true"/>
          <property name="MinimumAge" value="0"/>
          <property name="PhysicalDirectory" value="FOLDER_TOKEN"/>
          <property name="Recursive" value="false"/>
          <property name="PollingFrequency" value="30"/>
          <property name="FileType" value="ascii"/>
          <property name="IncludeFiles" value="FILENAME_TOKEN"/>  
        </activation-spec>
      </endpoint-activation>
    When I deploy this proxy in a cluster (having 2 osb nodes) and place the very first file on FTP server. Both nodes pick the file simultaneously. But after this when I place files on FTP server only one node is picking file. Could you kindly tell where is the issue ?
    Thanks and Regards

    Hi Mani,
    Do check the configuration of ProxyService-2 that it is enabled or not.
    Do check the input payload of it, that ProxyService-1 is passing the correct payload to ProxyService-2.
    Redeploy the ProxyService-2
    There is some issue in your proxyService-2.
    Regards,
    Richa

  • Resource Adapter deployment on cluster

    Hi,
    I have a weblogic cluster with 2 nodes and a load balancer. Recently I have deployed a database adapter to connect to a sql server database which is used by a service (OSB proxy service). The deployed was performed with both nodes running and I connected to the admin console using the LB IP. The deployed was done with successful and I have restarted both nodes. The cluster is configured with a stage mode in order to copy files from admin server.
    When I call this service, it goes ok when node1 is used but not ok when node2 is used. It gives an JCA error accessing the sql server database. To solve this issue I had to copy the deployment plan file from node1 to node2 and reploy de dbadapter resource with node1 down in order to update the node2. I was expecting that these files were updated on both nodes whenever I deploy a resource adapter on admin console.
    What am I doing wrong? Or what config should I check/update on admin console in order to avoid this manual task?
    Thanks,
    Regards,
    António Amado

    Use the shared location for deployment plans.
    Please see the link : Managing the Topology for an Enterprise Deployment - 11g Release 1 (11.1.1)

  • JMS Server deployed to cluster of servers

    Hey guys,
    I was trying to deploy a JMS server to a cluster of servers and in the target section there wasn't an option for the cluster. They had an option for each individual server and another migratable version of the server. If I target one of the migratable servers in the cluster will it apply to all of the servers?
    I read the following passage in the weblogic documents:
    Obtain a Clustered JMS Licence
    In order to implement JMS clustering, you must have a valid clustered JMS license, which allows a connection factory and a destination to be on different WebLogic Server instances. A clustered JMS license is also required to use the Foreign JMS Providers feature, as described in "Simple Access to Remote or Foreign JMS Providers" in the Administration Console Online Help. If you do not have a valid clustered JMS license, contact your BEA sales representative.
    If i'm just building a model does this apply to me?
    Thanks

    continued reading to clarify. Problem solved, thanks for looking

  • Deploying in cluster env

    HI,
    we have a clustered env for our production system. i defined a track and set up the runtime systems. since our production box is a clustered environoment, i specified the SDM hostname as the host on which the central instance is running.
    so when i try to transport, until QA everything is  fine (as they are non - clustered), but while trying to import particluar assembly to production, the error shown in deploy log is
    Error: An error occured while starting a cluster instance.
    Error: There is no control instance running in the cluster:
    Name:JM_T1137182930718_hostname |Host:hostname |State:5|
    Info:|Name:JC_hostname                      |Host:hostname                         |State:5|
    Info:Please check if there are running cluster instances.
    do i need to configure something in SDM of our central instance?
    please help us.
    Thanks

    This sounds like a bug to me. I'd suggest you contact [email protected]
    -- Rob
    Lars M wrote:
    We are running WL 8.1 SP2
    When the administration server is running, our ear is deployed to a cluster (2
    managed instances on 2 different nodes) using stage mode, and everything is fine.
    The problem:
    Afterwards, if we try to start a managed server when the administraion server
    is down, the managed server cannot activate the deployed application. It reports
    that the application path is invalid.
    The application path stored in the config.xml (and msi-config.xml) is the upload
    path of the administration server (e.g. DOMAIN_HOME/adminserver/upload/OurApp.ear)
    - and of course this path is only available on the node where the admin server
    is running - and NOT on another hw node where the managed server is running.
    Why is the managed server trying to open the original "source" application?
    Especially when the application is staged?
    Thanks
    Lars

  • Problem with weblogic.deploy and cluster

              I'm having some problems with the weblogic.deploy class when trying to refresh
              a jsp file. Using the following command to redeploy the entire application works
              fine:
              java weblogic.deploy -port 9876 -host apptest01 update
              administrator portal c:\portal-site
              However using the following command to refresh just one jsp
              file:
              java weblogic.deploy -url t3://apptest01:9876 -username system
              -jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
              refresh administrator portal
              produces the following stack trace:
              javax.naming.NameNotFoundException: Unable to resolve
              weblogic.management.home.olbcluster.
              Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
              remaining name ''
              at weblogic.rmi.internal.BasicOutboundRequest.
              sendReceive(BasicOutboundRequest.java:85)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
              invoke(ReplicaAwareRemoteRef.java:255)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
              invoke(ReplicaAwareRemoteRef.java:222)
              at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
              at $Proxy0.lookup(Unknown Source)
              at weblogic.jndi.internal.WLContextImpl.
              lookup(WLContextImpl.java:323)
              at weblogic.management.tools.WebAppComponentRefreshTool.
              getMBeanHomeForManagedServer
              WebAppComponentRefreshTool.java:498)
              at weblogic.management.tools.
              WebAppComponentRefreshTool.
              getComponentMBeanForServer
              (WebAppComponentRefreshTool.java:225)
              at weblogic.management.tools.
              WebAppComponentRefreshTool.findInternalPaths
              (WebAppComponentRefreshTool.java:187)
              at weblogic.management.tools.WebAppComponentRefreshTool.
              refresh(WebAppComponentRefreshTool.java:151)
              at weblogic.deploy.refresh(deploy.java:704)
              at weblogic.deploy.runBody(deploy.java:374)
              at weblogic.utils.compiler.Tool.run(Tool.java:79)
              at weblogic.deploy.main(deploy.java:1601)
              Unable to resolve weblogic.management.home.olbcluster.
              Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
              Any ideas?
              

              "John Murphy" <[email protected]> wrote:
              >
              >I'm having some problems with the weblogic.deploy class when trying to
              >refresh
              >a jsp file. Using the following command to redeploy the entire application
              >works
              >fine:
              >
              >java weblogic.deploy -port 9876 -host apptest01 update
              >administrator portal c:\portal-site
              >
              >However using the following command to refresh just one jsp
              >file:
              >
              >java weblogic.deploy -url t3://apptest01:9876 -username system
              >-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
              >refresh administrator portal
              >
              >produces the following stack trace:
              >
              >javax.naming.NameNotFoundException: Unable to resolve
              >weblogic.management.home.olbcluster.
              >Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
              >remaining name ''
              > at weblogic.rmi.internal.BasicOutboundRequest.
              > sendReceive(BasicOutboundRequest.java:85)
              > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
              > invoke(ReplicaAwareRemoteRef.java:255)
              > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
              > invoke(ReplicaAwareRemoteRef.java:222)
              > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
              > at $Proxy0.lookup(Unknown Source)
              > at weblogic.jndi.internal.WLContextImpl.
              > lookup(WLContextImpl.java:323)
              > at weblogic.management.tools.WebAppComponentRefreshTool.
              > getMBeanHomeForManagedServer
              > WebAppComponentRefreshTool.java:498)
              > at weblogic.management.tools.
              > WebAppComponentRefreshTool.
              > getComponentMBeanForServer
              > (WebAppComponentRefreshTool.java:225)
              > at weblogic.management.tools.
              > WebAppComponentRefreshTool.findInternalPaths
              > (WebAppComponentRefreshTool.java:187)
              > at weblogic.management.tools.WebAppComponentRefreshTool.
              > refresh(WebAppComponentRefreshTool.java:151)
              > at weblogic.deploy.refresh(deploy.java:704)
              > at weblogic.deploy.runBody(deploy.java:374)
              > at weblogic.utils.compiler.Tool.run(Tool.java:79)
              > at weblogic.deploy.main(deploy.java:1601)
              >Unable to resolve weblogic.management.home.olbcluster.
              >Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
              >
              >Any ideas?
              >
              Hi John,
              How's tricks?
              It looks to me as though the olbcluster JNDI reference isn't being resolved from
              the tree. A similar error results when a Connection Pool cannot be resolved, the
              JNDI context env.jdbc is resolved but the particlar pool isn't. In my experience
              it often turns out to be an error in the correlation between the deployment descriptors,
              settings applied via the console and references made in the code.
              That's my tuppence worth,
              James :-)
              

  • UnPacked Deployment And Cluster

    Hi
    we have web application and we plan to deploy it to 3 clustered weblogic servers
    our application also need to deal with users docs and imgs dynamically, so in our webroot we have sub folder named (files) contain all user files and we need to read/write files in this folder
    now we have  tow scenarios :
    1: in regular deployment by deploy EAR file to this clustered
    this work fine and deploy one time and update one time then the file will be reflected on other servers
    but users (files) folder will be in EAR file inside WAR file and this difficult to mange files inside war specially writing and save because physical path needed and also updating war to keep new files available
    2: in unpacked deployment by extract the EAR/WAR archive in to some directory in managed server folder then deploy using this directory from administrator console
    this work fine even for user files management
    but if we have 3 clustered weblogic server
    is must  extract files in all 3 servers ?
    and in case of update is also must be extracted (every time) in all 3 servers  ?
    or is there a way in cluster environment -without EAR- to extract one time and then be reflected to others

    Let me get it correct - you want to externalize the files from the package. If that is the case then,
    Package the files in a jar and deploy it on the Cluster as a Shared Library and let you WAR reference this library.
    Cheers,
    NJ

  • Adding remote producer deployed to cluster

    We are developing a federated portal with WLP 10.2 in which both the consumer and producer applications are deployed to the same cluster.
    I want to add the remote producer to the Portal Resources Library of my consumer application so that producer books/pages/portlets can be added to a desktop.
    To add a producer using the Portal Admin Console's Add Producer dialog you specify the producer's WSDL URL in the following format:
    http://host:port/producerWebApp/producer?wsdl
    In a clustered environment, each server is listening on a different port, so I would have to specify the port number of one of the servers, which I don't think is right.
    What is the proper way to add a remote producer using the Portal Admin Console when the producer is deployed to a cluster?

    continued reading to clarify. Problem solved, thanks for looking

  • Singleton deployed in cluster runs in both managed servers

    Hi,
    I have deployed a singleton service in a Weblogic (9.2) cluster. This cluster has two managed servers.
    Recently we saw instances of this singleton services running on both these managed servers, which resulted in a lot of duplicate data in our system.
    Is this a bug in the system? How can we prevent this?

    Hi,
    Could you please refer the following links and confirm me if you had defined and configured the singleton service as mentioned in the links:
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/clusters/ConfigureSingletonService.html
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/clusters/DefineSingletonService.html
    regards,
    Zeno

  • Online Deployment in Cluster

    Hello,
    we have currently set up a Netweaver application server cluster on SLES10. The cluster is setup like this:
    Two physical servers.
    1 WebDispatcher
    1 SCS
    1 JavaCentral Instance with SDM
    3 Dialog Instances.
    We wanted to know if the SDM provides an online deployment possibility, in which the WebDispatcher recognizes which dialog instance is not available due to current deployment.
    Does there have to be something configured in the SDM or WebDispatcher?
    We want to ensure if we deploy something during runtime that the server handles this appropriately without timeouts or errors.
    Regards,
    Kai

    Hi Kai,
    No the webdispatcher cannot be used by SDM to deploy software to other instances. The webdispatcher is used specifically to load balance HTTP, HTTPS and SMTP requests over different instances to one logical backend system.
    This is not specific to SDM but the webdispatcher will poll the backend message server for specific information about the availability of all backend instances via the profile paraemeter wdisp/auto_refresh (default 120 seconds).
    The information relayed from the message server includes the state of the instances. If the message server reports to the webdisp that a server is down it will be removed from the webdispatcher server pool.
    Note: Dont set the wdisp/auto_refresh parameter too low as the webdispatcher uses this for receiving load balancing information as well as the state of the instances.
    Hope this helps
    Michael

  • ANT deployment in cluster env - urgent pls

    All,
    version: 10g(10.1.3.4)
    We have set up 10g in cluster env. I tried to deploy a bpel thru ANT got the below error
    A problem occurred while establishing a connection to the BPEL Server.
    Please make sure the server is running on host "localhost", port "7777".
    The same bpel, when I tried to deploy thru JDev it deployed succesfully! What could be the possible reason? Also, the same bpel deployed thru ANT successfully in non-cluster env
    thanks,
    sen

    1.Go to the particular composite and create folder build.
    2. Place build.properties and build.xml files inside the folder.
    3. Generate configuration plan on right clicking composite.xml.
    4. Open build.properties file and cross check the following elements
    composite.name=Process (particular composite name)
    composite.revision=1.0 (version)
    oracle.home=C:/Oracle/Middleware/jdeveloper ( middleware home)
    soa.server.oracle.home=C:/Oracle/Middleware/jdeveloper
    admin.server.host=test.checf.com (admin server host)
    admin.server.port=7007 (admin server port)
    server.domain.name=SOADEV (soa domain)
    managed.server.host=soa.test.com (soa server host)
    managed.server.port=8007 (soa server port)
    server.user=weblogic (user credential)
    server.password=soadev123 (server passwd)
    java.home.set=D:/jdk160_18 (jdk path)
    server.targets=WLS_SOA2 (target node)
    config.plan=Process_cfgplan_17.xml (compiste config plan)
    5.Open build.xml file check the following
    <project name="rProcess " default="deploy" basedir="."> (check the project name)
    Commands from cmd
    1. Go to the cmd.
    2. Set the following variables in cmd.
    C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>set ORACLE_HOME=C:\Oracle\Middleware
    C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>set ANT_HOME=%ORACLE_HOME%\jdeveloper\ant
    C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>set PATH=%ANT_HOME%\bin;%PATH%
    C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>set JAVA_HOME=D:\jdk160_18
    3. Go the particular composite build folder
    Bpel Process
    |-> SOA Content
    |->build
    4. Give ant command
    C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>ant
    check the same whther it helps u or not

Maybe you are looking for

  • Newb needs help w small office network setup

    Just started a new job at small start-up company that needs their 6-7 macs and a couple of printers networked. I'm just a designer and I'm trying to help but I'm not familiar with osX networking and I hope someone could point me in the right directio

  • The lastest iTunes wont work and the existing one is now corrupt

    Has anyone else experienced this problem ? I'm annoyed.

  • ALV subtotal & grand total

    Hi experts, I have a ALV display which displays subtotals & grandtotals. I only want the subtotals, How can I supress the grantotal? ex. DOC num 50003859 200 USD 300 USD subtotal = 500 DOC num 50005469 600 USD subtotal = 600 Grandtotal = 1100 <- I do

  • TS1386 Play a music video downloaded from iTunes.

    I used my iPad to download a music video from iTunes but it doesn't play the visual just a still frame along with audio. What do I need to do to see my purchased video?

  • Hi guys, I hope someone can help me with a technical question

    a couple of days I recharge the battery of my iphone with the original usb adapter to the electrical plug and then in the right moment when I plugged the phone it came a little spark from the electrical plug and my iphone  was shut down by itself the