Deployment on managed server

Problem deploying app on managed server:
testEAR.ear is built using wlpackage ant task, but it still causes the exception
while deploying
on managed server:
Exception:weblogic.management.ApplicationException: Application testEAR is packaged
using
the WebLogic Split Development Directory structure. The Split Development Directory
structure
can only be used in development environments with a single WebLogic Server. If
you wish to
deploy this application to a separate managed server or cluster, use the wlpackage
ant task to
create an exploded or archived EAR.
build.xml part:
<taskdef name="wlpackage" classname="weblogic.ant.taskdefs.build.WLPackageTask"
classpathref="task.classpath"/>
<target name = "package" description = "Create exploded or arhived AER" depends
= "build">
     <wlpackage srcdir="test" destdir="." toFile="testEAR.ear"/>
</target>
Ant doesn't alerts any errros.
What is the problem?

Can you show me the output of jar tvf testEAR.ear?
Also, please show me the Application snippet from your config.xml
-- Rob
vinni wrote:
Problem deploying app on managed server:
testEAR.ear is built using wlpackage ant task, but it still causes the exception
while deploying
on managed server:
Exception:weblogic.management.ApplicationException: Application testEAR is packaged
using
the WebLogic Split Development Directory structure. The Split Development Directory
structure
can only be used in development environments with a single WebLogic Server. If
you wish to
deploy this application to a separate managed server or cluster, use the wlpackage
ant task to
create an exploded or archived EAR.
build.xml part:
<taskdef name="wlpackage" classname="weblogic.ant.taskdefs.build.WLPackageTask"
classpathref="task.classpath"/>
<target name = "package" description = "Create exploded or arhived AER" depends
= "build">
     <wlpackage srcdir="test" destdir="." toFile="testEAR.ear"/>
</target>
Ant doesn't alerts any errros.
What is the problem?

Similar Messages

  • Bea 9.2 : deployment to managed server failed (J2EE:160149)

    Hi,
    I am trying to deploy portal application to managed server instance. When i am deploying it to an admin server, deployment is fine but when i am deploying to managed server instance, it fails with following error:
    ********* log start ************
    [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: wlp-groupspace-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-collab-portlets-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-framework-full-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-commerce-tools-support-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-tools-support-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-webdav-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-tools-admin-app-lib, Specification-Version: 9.2, Implementation
    ********* log end **************
    Can you note that the it was fine when deployment was done to admin server.
    I am not sure whether i have set up the managed server instance in the proper way. This is what i did to set up managed server instance before deployment
    (1) create weblogic domain
    (2) create managed server listening at port 8001. (admin is at 7001)
    (3) created machine and in the node manager added the managed server to the machine just created.
    (4) started node manager through script, started admin server and started managed server by
    startManagedWebLogic.cmd managedserver admin_url
    => No errors so far. but now when i try to deploy portal application to managed server instance, it fails.
    Any pointers???
    (ps : can a moderator help me to move this message to the portal forum instead of here..thanx)
    Edited by tamugrg13 at 03/25/2007 8:09 PM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    don't worry about this. i have resolved this by deploying into a cluster. looks like BEA doesn't support non-clustered deployment to managed server instances.

  • Partition not found- While deploying to managed server

    We are using 11gR1. We have configured a soa managed server. While deploying Sales demo application in BPM Studio, we set up connection to the Admin Server and when we test the connection it is successful. During the last step of deployment, where the SOA managed server is prompted, SOA server is listed properly but we get a message saying that partition is not available.
    We went to EM and found that there is a default partition, we also created a new partition and restarted both the servers. But still we face the same error. The Log gives the following information:
    <Error> <RepositoryPartitionModel.class> <BEA- 000000> <Getting Partitions>
    Is this a product bug or are we missing out on anything.
    Venkat

    Hi venkat,
    I am also having the same problem. Were you able to find out the solution for this issue. I currently manually deploy the GUI EAR from the admin console and the SAR file from the EM.
    Thanks,

  • Server Hangs when I tried to Access web Application that deployed in Managed Server

              Hai All!
              Here is my problem ! I started Admin Server and Managed server in a same machine.
              I deployed HttpClusterServlet in web.xml of Managed server. When i started servers
              they start fine and says Clustering started.... But when i tried to Access index.jsp
              that is in Managed Server default web application ..Nothing happens. It neither
              throws exception nor shows the desired page.. Seems to be Browser hang and server
              hang. At this stage i am unable to access Admin console also.(I can access before
              i tried index.jsp of managed server).. It seems to be Hang Allover..
              Pls suggest me how to come out of this hanging...
              Rgds
              Manohar
              

    See my answer to your last post. The short answer is that the HttpClusterServlet is
              likely to be the problem and not the cluster. You can try one of the web server plugins
              or a hardware load balancer as a temporary workaround. You should file a case with
              support too...
              Manu Kar wrote:
              > Hai All!
              >
              > Here is my problem ! I started Admin Server and Managed server in a same machine.
              > I deployed HttpClusterServlet in web.xml of Managed server. When i started servers
              > they start fine and says Clustering started.... But when i tried to Access index.jsp
              > that is in Managed Server default web application ..Nothing happens. It neither
              > throws exception nor shows the desired page.. Seems to be Browser hang and server
              > hang. At this stage i am unable to access Admin console also.(I can access before
              > i tried index.jsp of managed server).. It seems to be Hang Allover..
              >
              > Pls suggest me how to come out of this hanging...
              >
              > Rgds
              > Manohar
              

  • OSB deployment on managed server

    Hello,
    We have a OSB clustered environment where managed servres and admin server reside on separate machines. OSB admin server does not have access to database (The architecture does not allow Admin server to connect to DB). As far as my understanding OSB applications/projects have to be targeted on Admin server for deployment even the SB console is accessible via admin server.
    How can we use the Oracle OSB WLST deployment scripts for target on the managed servers currently this works only when pointed to the Admin sserver.
    If WLSTscript is pointed to the managed server the deployment script throws exception stating 'cannot start Mbean server'
    Your help on this greatly appreciated.
    Thanks,
    P

    Hi Prashant,
    OSB apps don't have to be necessary targeted to Admin server. In our project OSB apps are targeted to OSB managed server.
    I think reason why you can't deploy it in your case is that there are no OSB components deployed in Admin server. Those components are
    deployed to admin server during the installation even if you choose install OSB to separate OSB managed server (they are deployed to both admin and OSB managed servers). I think that's OSB design issue.
    During our deployment we recreate domain including OSB apps every time from scratch. It works fine.
    Regards,
    Milan

  • Unable to deploy to managed server - ExceptionInInitializerError

    I have a development/integration environment that lives on a single HP-UX server: two Weblogic domains, each containign an admin server and several managed servers. The machine is running a node manager process, and the node manager plus all servers are started via a WLST Python script (as recommended in the documentation).
    I have a seriously annoying issue whereby I cannot deploy any application, or data source, to a managed server unless that server is shut down. I get an 'ExceptionInInitializerError' any time I try. I can shut down the target server, install the deployment using the console, then start the server, and everything works great. Any insight is greatly appreciated.
    Version: Weblogic 10.3.0.0
    OS: HP-UX B.11.23 U ia64
    Stacktrace:
    ####<Nov 2, 2010 11:58:17 AM EDT> <Warning> <Deployer> <borg.abc.virginia.gov> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288713497985> <BEA-149004> <Failures were detected while initiating deploy task for application 'pta'.>
    ####<Nov 2, 2010 11:58:17 AM EDT> <Warning> <Deployer> <borg.abc.virginia.gov> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288713497985> <BEA-149078> <Stack trace for message 149004
    java.lang.Exception: java.lang.ExceptionInInitializerError
         at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.includePrepareFailure(AdminRequestStatus.java:1418)
         at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.signalCancelFailed(AdminRequestStatus.java:1266)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.signalCancelCompletion(AwaitingCancelResponses.java:126)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.doCancelCompletionCheck(AwaitingCancelResponses.java:112)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.receivedCancelFailed(AwaitingCancelResponses.java:97)
         at weblogic.deploy.service.internal.adminserver.AdminRequestImpl.receivedCancelFailed(AdminRequestImpl.java:503)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveCancelFailedMsg(CommonMessageReceiver.java:295)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:779)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.ExceptionInInitializerError
         at weblogic.management.mbeans.custom.Domain.lookupTarget(Domain.java:247)
         at weblogic.management.configuration.DomainMBeanImpl.lookupTarget(DomainMBeanImpl.java:6139)
         at weblogic.deploy.internal.TargetHelper.lookupTargetMBeans(TargetHelper.java:183)
         at weblogic.management.deploy.DeploymentData.getAllTargetedServers(DeploymentData.java:413)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isTargetListContainsCurrentServer(AbstractOperation.java:644)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isDeploymentRequestValidForCurrentServer(AbstractOperation.java:854)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:206)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.NullPointerException
         at weblogic.management.mbeans.custom.AttributeAggregator.<init>(AttributeAggregator.java:36)
         at weblogic.management.mbeans.custom.Domain$TARGETAGGREGATOR.<clinit>(Domain.java:239)
         at weblogic.management.mbeans.custom.Domain.lookupTarget(Domain.java:247)
         at weblogic.management.configuration.DomainMBeanImpl.lookupTarget(DomainMBeanImpl.java:6139)
         at weblogic.deploy.internal.TargetHelper.lookupTargetMBeans(TargetHelper.java:183)
         at weblogic.management.deploy.DeploymentData.getAllTargetedServers(DeploymentData.java:413)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isTargetListContainsCurrentServer(AbstractOperation.java:644)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isDeploymentRequestValidForCurrentServer(AbstractOperation.java:854)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:206)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Nov 2, 2010 11:58:18 AM EDT> <Error> <Console> <borg.abc.virginia.gov> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1288713498054> <BEA-240003> <Console encountered the following error java.lang.Exception: java.lang.ExceptionInInitializerError
         at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.includePrepareFailure(AdminRequestStatus.java:1418)
         at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.signalCancelFailed(AdminRequestStatus.java:1266)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.signalCancelCompletion(AwaitingCancelResponses.java:126)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.doCancelCompletionCheck(AwaitingCancelResponses.java:112)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.receivedCancelFailed(AwaitingCancelResponses.java:97)
         at weblogic.deploy.service.internal.adminserver.AdminRequestImpl.receivedCancelFailed(AdminRequestImpl.java:503)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveCancelFailedMsg(CommonMessageReceiver.java:295)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:779)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.ExceptionInInitializerError:
         at weblogic.management.mbeans.custom.Domain.lookupTarget(Domain.java:247)
         at weblogic.management.configuration.DomainMBeanImpl.lookupTarget(DomainMBeanImpl.java:6139)
         at weblogic.deploy.internal.TargetHelper.lookupTargetMBeans(TargetHelper.java:183)
         at weblogic.management.deploy.DeploymentData.getAllTargetedServers(DeploymentData.java:413)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isTargetListContainsCurrentServer(AbstractOperation.java:644)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isDeploymentRequestValidForCurrentServer(AbstractOperation.java:854)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:206)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    >
    Thanks,
    Chris

    Hi Chris,
    Did you manage to get a solution to this error, as I am facing the same issue.
    Thanks in advance,
    Pranav

  • Adminconsole deployment on managed server

    can we deploy the Admin Console application on Weblogic Managed Servers?
    Thanks in advance.
    Bhanu.

    can we deploy the Admin Console application on Weblogic Managed Servers?Not sure what you mean, but on Fusion Middleware Control you have a link to the Admin Console for each server.

  • Deployment of Web Application when the managed Server is down .....

    Part of our installation, we want to deploy our web application on to a managed server.
    So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
    But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
    We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
    Can anyone help to deploy web application on to a managed server when the managed server is down ?
    Thanks,
    Selva-
    [att1.html]

    This is currently being fixed in 7.0 line, contact [email protected] and reference
    CR110687
    Cheers
    mbg
    "Selvamohan Neethiraj" <[email protected]> wrote in message news:[email protected]..
    Part of our installation, we want to deploy our web application on to a managed server.
    So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
    But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
    We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
    Can anyone help to deploy web application on to a managed server when the managed server is down ?
    Thanks,
    Selva-
    [att1.html]

  • Problem when we created the managed server to configure different ports.

    I am trying to configure different ports for admin console and my communication service as we can’t share admin port to the outside world.
    So that only admin can access admin console using admin port.
    And out side clients can access my webapplication using different port.
    For this i have created the managed server in weblogic.and I deployed the application on managed server.
    Now admin server is running on 8001 port and my Communication Service application is running on 7001 port.
    But when I tried to configure MBeans related to myCommunicationServiceApplication those were disapper on admin console. And the other wlng services are appearing on admin console.
    1. Since my application deployed on managed server MBeans registration happened from myapplication hence it’s disappear on admin console.
    Now If I want to configure Mbeans (related to my communication service) how can I configure it?
    2. My communication service using configurationStore module and other wlng services.
    When I tried to start my application on managed server I got the below error:
    <Apr 28, 2009 12:22:44 PM IST> <Error> <Deployer> <BEA-149231> <dscp11166.TechMahindra.com> <Unable to set the activation state to true for the application 'wlng_nt_qualcomm_active_mediation [Version=1.0]'.
    com.bea.wlcp.wlng.api.storage.configuration.ConfigurationException: Configuration store module is not available.
    3. I tried to target all wlngResources to manged server by editing config.xml file.
    Then all wlng services disappears on admin console. If this is the case how can I configure container/account services on wlng?
    I have created the Basicweblogic domain.
    Below is the config.xml for reference.
    "QualcommServer" is managed server name.
    Can any one please suggest me how to configure this kind of scenarios?
    <server>
    <name>AdminServer</name>
    <machine>new_Machine_1</machine>
    <listen-port>8001</listen-port>
    <default-iiop-user>weblogic</default-iiop-user>
    <default-iiop-password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</default-iiop-password-encrypted>
    <listen-address>localhost</listen-address>
    </server>
    <server>
    <name>QualcommServer</name>
    <machine>new_Machine_1</machine>
    <listen-address>localhost</listen-address>
    <server-start>
    <java-vendor>Sun</java-vendor>
    <java-home>C:\Program Files\Java\jdk1.6.0</java-home>
    <class-path>C:\bea\wlng400\server\lib\weblogic.jar;C:\bea\wlng_pds400\lib\wlng\wlng.jar</class-path>
    <bea-home>C:\bea</bea-home>
    <username>weblogic</username>
    <password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</password-encrypted>
    </server-start>
    </server>
    <embedded-ldap>
    <name>managedserver</name>
    <credential-encrypted>{3DES}9q80YuFJueVVJxoWduJA1OGhbqk14EpgQWWyTrzlmxo=</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.0.1.0</configuration-version>
    <app-deployment>
    <name>wlng_nt_session#4.0</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/wlng_nt_session.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>interceptors</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/interceptors.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>wlng_prm</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/wlng_prm.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>wlng_nt_qualcomm_active_mediation#1.0</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>servers\AdminServer\upload\wlng_nt_qualcomm_active_mediation.ear</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <machine>
    <name>new_Machine_1</name>
    <node-manager>
    <name>new_Machine_1</name>
    <listen-address>localhost</listen-address>
    </node-manager>
    </machine>
    <jms-server>
    <name>JMSServer-AdminServer</name>
    <target>AdminServer</target>
    </jms-server>
    <jms-system-resource>
    <name>WLNGJMSResource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <custom-resource>
    <name>networktier</name>
    <target>AdminServer</target>
    <descriptor-file-name>custom/nt.xml</descriptor-file-name>
    <resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngTierResource</resource-class>
    <descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean</descriptor-bean-class>
    </custom-resource>
    <custom-resource>
    <name>wlng-edr</name>
    <target>AdminServer</target>
    <descriptor-file-name>custom/wlng-edr.xml</descriptor-file-name>
    <resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngEdrResource</resource-class>
    <descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngEdrBean</descriptor-bean-class>
    </custom-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <jdbc-system-resource>
    <name>wlng.datasource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jdbc/wlng-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>wlng.localTX.datasource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jdbc/wlng-localTX-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    Thanks,
    Srinu Babu P

    Dear Nariharan,
    Today I faced a simlar issue, and this SAP Note helped me fix it: 1966807 - Duplication of AET table records in change processing
    In my case, cardinality of AET table was 1:1, and I was getting duplicate PARENT_ID every time when trying to create a subsequent service request for my activity.
    Regards,
    Andrew

  • War not running on managed server but run on admin

    Hi,
    WLS 10.3.1 , application deploy on admin runs successfully but doesnot runs when deployed on managed server.
    netstat show when access via browser the managed server show connection status as FIN_WAIT_2 but established when accessing via admin.
    any idea why?
    Thanks in advance.

    Hi,
    To understand your problem can you let us know
    - If you are using any proxy between the client and WLS.
    - Is this happing with only one managed servers or all the managed servers.
    - What is the basic difference with you try to access the same application when it is deployed on Admin sever and Managed server.
    - Does the response comes from the server (MS) after sometime or its stuck and you do not get any response, and if you do not get it then what do you error do you get if any.
    Regards,
    Ravish Mody

  • Cannot contact MANAGED SERVER in a CLUSTER

    I have configured a BEA CLUSTER (8.1 Sp2) on a SUN CLUSTER.
              If I try to contact a Managed Server using a browser from my PC, (using httpt or https as well) it does not responde until I put a "ping" to this Managed Server's IP ADDRESS using a DOS console.
              Someone can help me?
              Stefano

    How do you contact managed server using browser?
              what is the request (URL) that you sent through browser?
              For the request to be successful you should have an application deployed on managed server.
              -Vijay

  • Cannot deploy SOA composite to a managed server

    My problem: cannot deploy SOA composite to a managed server.
    The following is what I did:
    1. I created a domain "devDomain". admin server is created automatically for me.
    *2. I created a manged server (soa_server1) on my domain after.*
    2. started the admin server
    3. started soa_server1
    4. see both servers in WLS control, both server state=running
    5. see both server in EM console, both server status are up
    6. in JDev(11.1.1.5.0), created an application server connection, and tested the connection successfully
    7. when I tried to deploy my composite from JDev, I selected the application server connection, on step "SOA servers", it only lists AdminServer.
    8. Then I tried to deploy the composite from EM by right-click soa_server1, but "SOA deployment" is not in the list.
    My guess: there should be some libraries or other resources applied to soa_server1 before it could accept soa deployment. What are these libraries/resources?
    I tried to target all 10 libraries under the path "oracle.soa." to soa_server1, and checked the config.xml and found the file was updated correcly, reboot my pc, restarted the servers, but still face the same problem.
    My environment is weblogic 10.3.5.
    Basically, my question is:
    after a domain is created and admin server is there, if I want to add a managed server which will host soa composites, what should I do to configure the managed server?
    Edited by: wiky on Jul 20, 2011 11:39 AM

    How can I add new code to a clustered environment without causing an          outage. Right
              > now I have to deploy the new code using the admin server to both managed
              servers.
              > My question is if I pull one managed server out of the cluster, add new
              code and
              > test it, how do I add this one managed server back to the cluster that is
              referencing
              > the old code without causing an outage for the site?
              This is something addressed much better in the 7.0 release.
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              Clustering Weblogic? You're either using Coherence, or you should be!
              Download a Tangosol Coherence eval today at http://www.tangosol.com/
              "William" <[email protected]> wrote in message
              news:3cc9847a$[email protected]..
              >
              

  • Error 401--Unauthorized when deployed on WL Managed server (10.3.3)

    Hi,
    I created & started a WL-Managed server on my window desktop machine. I deployed to this Managed server, an application which is running without problem on Admin Server. (The managed server is created in the same Domain as that of Admin Server)
    However, when I log on to the application on Managed server & enter the UID & PW I get the Error 401--Unauthorized page. The same security works perfectly well for Admin Server.
    Any clues what could be going wrong.
    Thanks in advance.
    Edited by: Prakash Chavan on Feb 28, 2011 4:57 PM

    Thanks Faisal,
    Here is the log after I add the 2 flags
    <Mar 1, 2011 8:59:30 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
    e changed to RUNNING>
    <Mar 1, 2011 8:59:30 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server star
    ted in RUNNING mode>
    Mar 1, 2011 9:13:27 AM oracle.jbo.uicli.mom.CpxUtils$Visitor logMainApplicationC
    px
    INFO: zip:C:/JDev11g/Middleware/user_projects/domains/base_domain/servers/Svr0/t
    mp/_WL_user/TestTrackApp_V2.0/77qs7f/war/WEB-INF/lib/_wl_cls_gen.jar!/view/DataB
    indings.cpx
    [JpsAuth] Check Permission
    PolicyContext: [TestTrackApp#V2.0]
    Resource/Target: [view.pageDefs.ttsPageDef]
    Action: [view]
    Permission Class: [oracle.adf.share.security.authorization.RegionP
    ermission]
    Result: [FAILED]
    For more information on this failure, please set -Djps.auth.debug.verb
    ose=true
    I have emailed you the requested log & the config files.
    Edited by: Prakash Chavan on Mar 1, 2011 9:35 AM

  • How to use jspx deployed in different managed server from bpm work space

    Hi,
    I have created and deployed my view project having all the jspx files and managed beans into a different managed server(created a new server,not into the soa server).
    I have created a bpm process and now I want to use the jspx page(deployed into the new managed server) in my bpm wrokspace.
    Can anyone help me how I can do it.
    thanks in advance.
    Regards,
    Tukuna

    Hi ,
    I tried with the below url and still i am not able to open the jspx page deployed into the admin server.
    http://docs.oracle.com/cd/E21764_01/integration.1111/e10224/bp_designtf.htm#BDCFBJIE
    28.8.4 How To Deploy a Task Form to a non-SOA Oracle WebLogic Server
    Any help on this is appreciatable.
    Many thanks
    Tuku

  • Error while deploying to Production Managed Server

    My setup is one Domain, one AdminServer, one Managed Server all running in Production Mode.. The AdminServer:7001 and ManagedServer:7003 are on the same box.
    I can deploy my app and hit it via a web service on AdminServer:7001 but I can't hit is on the ManagedServer:7003.
    What happens is I tell the ODSI Admin Console to target the application to either ManagedServer or ManagedServer and AdminServer. Doing this put's the ManagedServer into an Admin STANDBY mode, lists the following error, and remains in an UNKNOWN state. I eventually have to shut the ManagedServer down and start it again.
    The server is running on the latest version of Oracle Mission Control 3.1.0 with the version of JRockit that's in there (1.6.0_11 R27.6.3).
    I mean, I'd rather not run the application on the AdminServer. Does anyone have any suggestions on what to look into to try to trouble shoot this issue??
    ####<Sep 16, 2009 10:02:46 AM EDT> <Error> <Deployer> <computername> <XYZ_ManagedServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1253109766565> <BEA-149231> <Unable to set the activation state to true for the application 'OraclePackage2_request_handlers'.
    java.lang.IllegalArgumentException: Session: null does not exist.
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
         at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
         at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
         at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:292)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:194)
         at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:66)
         at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.IllegalArgumentException: Session: null does not exist.
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
         at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
         at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
         at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:292)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:194)
         at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:66)
         at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >

    Hey ,Can you please help me?can you tell me how you resolved this issue.Our production is down due to
    java.lang.IllegalArgumentException: Session: null does not exist.
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
         at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
         at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
         at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
         Truncated. see log file for complete stacktrace.
    Its urgent plz

Maybe you are looking for

  • I upgrade from the previous version to Firefox 4.o, I can no longer connect to my work HTTPS website.

    The site I connect to is my citrix account at work, which needs a certificate. I could connect with the previous version of Firefox (3.6). When I upgraded the browser I got the errors mentioned earlier. I changed the setting for the specific setting

  • Unsure the correct procedure to follow.

    Yesterday BT or a department of BT came out to our street and replaced a telegraph pole.  This pole is from what I can see is at the beginning of the chain which then connects on to the rest down the street. They have quite clearly changed some of th

  • Allow third-party browser extentions

    Hello, After upgrading to Java 7 up21, I now need to enable the Internet Explorer security option to "Allow third-party browser extensions" to allow the Java login applet at the DCO Jabber site. How can I increase verbose logging in Java to help expl

  • Error on login....how do I fix this?

    So, I have a IDSM-2 module in a 6513 switch. When I try to login to the device I get the follow error: login: PAM Failure, aborting: Critical error - immediate abort This looks like a Linux error, at least Google searchs show that it happens in linux

  • CO15 Adjustment on Goods Movement Problem

    Hi SAP consultant, Currently i encountered problem when back flush transaction performed in CO15- PO confirmation, then i have right to make adjustment to the component like add or delete the component or change the quantity. Can SAP deny the access