Undeploy EAR on Oracle10gAS 10.1.2 using ANT

I am using JDeveloper10g - 10.1.2 on my local machine and Oracle10gAS - 10.1.2 on a remote machine.
I am able to deploy remotely using ANT task oc4j_remote_deploy.jar, but UNDEPLOY doesnt work. Anybody has a readymade UNDEPLOY task on a remote machine?
Also, while using remote DEPLOY task, I noticed that though it takes the Application Name as a parameter, it deploys with the first part of EAR filename. For example, if I specify shop.ear for ear file name and SHOPALR8 for applciation name, still it deploys shop.ear with the name as shop. Any patch available for this?
Any pointers will be highly appreciated.
Thanks,
Aravind.

That seems to be fine. The warning message '[05/Mar/2013:16:39:01 +0800] [warning 11917] [ecid: -] SSL wallet Origin Server Wallet file SYSTEM DEFAULT LOCATION (See Documentation)\ewallet.p12 does not exist." wou;d however indicate that the Web Cache has been configured with SSL so it is quit odd.
Given the fact that it is a warning only, I would expect the web cache to be available. But I noticed a different error as well :
{code}
[05/Mar/2013:16:39:04 +0800] [alert 11201] [ecid: -] OracleAS Web Cache is unable to resolve the IP address of xxxxxxx. Check your DNS setup.
[05/Mar/2013:16:39:04 +0800] [alert 9609] [ecid: -] The server process could not initialize
{code}
That would suggest that you have defined a host name which cannot be resolved to IP number. That may cause the web cache not to start.
Thanks,
EJ

Similar Messages

  • NW7.3] Problem while trying to deploy an EAR using ant task

    (I posted this in another forum, but I think this is the right one )
    Hello!
    I'm trying to deploy a EAR file to my Netweaver instance using ANT but I'm facing the following problem.
    I've downloaded all the files from j2ee/deployment and j2ee/j2eeclient as SAP's documentation states, the classpath is correctly set, however I get this error:
    BUILD FAILED!
    build.xml:16: taskdef class com.sap.engine.services.dc.ant.convert.SAPImportEAR cannot be found
    I've taken a look at tcjedc_ant.jar, which I downloaded from my instance, and it appears that SAPImportEAR is missing.
    By opening the file I can see com.sap.engine.services.dc.ant.deploy, com.sap.engine.services.dc.ant.undeploy and com.sap.engine.services.dc.ant.params, but the whole package com.sap.engine.services.dc.ant.convert is missing.
    Is it suposed to be anywhere else? All the articles/posts I found state that it should be on tcjedc_ant.jar.
    Thanks in advance!

    Hi,
    I guess this example_build.xml is outdated (belongs to NW 7.1).
    To build an SDA, look at make_SDA.csh.
    Class is com.sap.engine.lib.deploy.sda.SDAProducer.
    To buid an EAR, you do not need SAPImportEAR at all, just <taskdef "sapdeploy"...
    Regards
    Rolf

  • Need build.xml to create Ear file using Ant in jdeveloper 11g??

    Hi all,
    I think Jdeveloper use ANT to create Ear file and how to get build.xml from Jdeveloper.
    1) I have created ADF Fusion web Application having separte Model and View Controller.
    2) Now when I select View Controller project and then i create New ant-> Build.xml i get the required build.xml which can be used to create war file for my View Controller project.
    3) Similarly when I select Model project and then i create New ant-> Build.xml i get the required build.xml which can be used to create Jarfile for my Model project.
    4) If I select my application and then i click deploy... I'm able to create my ear file having both war file for View Controller and Jar File for Model.
    5) But I dont know how to get built.xml file which will create ear file having both View Controller and Model in it.
    Thanks a lot....

    However note the generated Ant script includes unnecessary targets. See the following blog post: http://one-size-doesnt-fit-all.blogspot.com/2010/11/using-ojdeploy-and-ant-for-creating-adf.html
    CM.

  • Can't undeploy EAR via both SDM and VA

    Hi All,
    I can't undeploy EAR via both SDM and VA. SDM starts undeploying and then hangs up. When I try to redeploy (update) I can't reach the final deploy page too. The same is when execute "Remove" action within VA in Deploy service - it reaches 99% and then hangs up. Netweaver trial 7.0 SP12.
    How can I manually undeploy EAR?
    Regards,
    Alex

    Hello Mike,
    Thank you for delay response and sorry for our delay answer. In SDM log there is nothing. In defaultTrace the next records appears after near 20 minutes wait (mentioned RunRulesQueue is JMS queue for MDB):
    "08/06/2007","14:51:50:232","Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 341 |  src: 2 target-node: 14109850 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=14109850,SAP_J2EECluster='' getApplicationStatus [Ljava.lang.Object;@1dce6df [Ljava.lang.String;@1b95305 ]
    [EXCEPTION]
    javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application JMSConnector : Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application JMSConnector : Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ","Warning","/System/Server","com.sap.engine.services.jmx.MBeanServerInvoker","","SAPEngine_Application_Thread[impl:3]_11","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E005600000293000014B80004370688BB4E9B","com.sap.engine.services.jmx.MBeanServerInvoker","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application JMSConnector : Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
         ... 24 more
    caused by -
    java.rmi.RemoteException: Error in getting status of application JMSConnector : Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application JMSConnector : Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
         ... 24 more
    caused by -
    java.rmi.RemoteException: Error in getting status of application JMSConnector : Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","","","","0","0","","1","/System/Server","","15506","com.sap.engine.services.jmx.MBeanServerInvoker","SAPEngine_Application_Thread[impl:3]_11","","Administrator",
    "08/06/2007","14:51:50:232","Exception com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ","Error","/System/Audit","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_11","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E005600000291000014B80004370688BB4433","com.sap.engine.services.deploy","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1352)
    ,","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","","","","0","0","","1","/System/Audit","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_11","","Administrator",
    "08/06/2007","14:51:50:232","Application sap.com/JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.","Error","/System/Server","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_11","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E005600000290000014B80004370688BB3F98","com.sap.engine.services.deploy","sap.com/JMSConnector,Server 0 1_41098,get its status,","sap.com/JMSConnector,Server 0 1_41098,get its status,","","","","0","0","deploy_5005","1","/System/Server","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_11","","Administrator",
    "08/06/2007","14:51:49:029","Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 357 |  src: 2 target-node: 14109850 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=14109850,SAP_J2EECluster='' getApplicationStatus [Ljava.lang.Object;@1de783a [Ljava.lang.String;@a7351a ]
    [EXCEPTION]
    javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application RunRulesQueue - JMSConnector : Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
         ... 24 more
    caused by -
    java.rmi.RemoteException: Error in getting status of application RunRulesQueue - JMSConnector : Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ","Warning","/System/Server","com.sap.engine.services.jmx.MBeanServerInvoker","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E005800000012000014B80004370688A8DF90","com.sap.engine.services.jmx.MBeanServerInvoker","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application RunRulesQueue - JMSConnector : Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application RunRulesQueue - JMSConnector : Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application RunRulesQueue - JMSConnector : Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application RunRulesQueue - JMSConnector : Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","","","","0","0","","1","/System/Server","","15506","com.sap.engine.services.jmx.MBeanServerInvoker","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    "08/06/2007","14:51:49:029","Exception com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ","Error","/System/Audit","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E005800000010000014B80004370688A8D526","com.sap.engine.services.deploy","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","","","","0","0","","1","/System/Audit","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    "08/06/2007","14:51:49:029","Application sap.com/RunRulesQueue - JMSConnector is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.","Error","/System/Server","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E00580000000F000014B80004370688A8D072","com.sap.engine.services.deploy","sap.com/RunRulesQueue - JMSConnector,Server 0 1_41098,get its status,","sap.com/RunRulesQueue - JMSConnector,Server 0 1_41098,get its status,","","","","0","0","deploy_5005","1","/System/Server","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    "08/06/2007","14:51:48:529","Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 375 |  src: 2 target-node: 14109850 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=14109850,SAP_J2EECluster='' getApplicationStatus [Ljava.lang.Object;@1ffb98f [Ljava.lang.String;@1ef71da ]
    [EXCEPTION]
    javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application mycompany.com/MyApplication - METAMODELREPOSITORY : Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application mycompany.com/MyApplication - METAMODELREPOSITORY : Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ","Warning","/System/Server","com.sap.engine.services.jmx.MBeanServerInvoker","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E00580000000D000014B80004370688A16E4A","com.sap.engine.services.jmx.MBeanServerInvoker","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application mycompany.com/MyApplication - METAMODELREPOSITORY : Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application mycompany.com/MyApplication - METAMODELREPOSITORY : Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application mycompany.com/MyApplication - METAMODELREPOSITORY : Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application mycompany.com/MyApplication - METAMODELREPOSITORY : Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","","","","0","0","","1","/System/Server","","15506","com.sap.engine.services.jmx.MBeanServerInvoker","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    "08/06/2007","14:51:48:529","Exception com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ","Error","/System/Audit","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E00580000000B000014B80004370688A163F5","com.sap.engine.services.deploy","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","","","","0","0","","1","/System/Audit","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    "08/06/2007","14:51:48:529","Application mycompany.com/MyApplication - METAMODELREPOSITORY is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.","Error","/System/Server","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E00580000000A000014B80004370688A15F5D","com.sap.engine.services.deploy","mycompany.com/MyApplication - METAMODELREPOSITORY,Server 0 1_41098,get its status,","mycompany.com/MyApplication - METAMODELREPOSITORY,Server 0 1_41098,get its status,","","","","0","0","deploy_5005","1","/System/Server","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    "08/06/2007","14:51:48:092","Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 350 |  src: 2 target-node: 14109850 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=14109850,SAP_J2EECluster='' getApplicationStatus [Ljava.lang.Object;@f6a63e [Ljava.lang.String;@11c54d7 ]
    [EXCEPTION]
    javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application MyApplication - web : Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application MyApplication - web : Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ","Warning","/System/Server","com.sap.engine.services.jmx.MBeanServerInvoker","","SAPEngine_Application_Thread[impl:3]_11","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E00560000028E000014B800043706889A984F","com.sap.engine.services.jmx.MBeanServerInvoker","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application MyApplication - web : Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application MyApplication - web : Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application MyApplication - web : Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application MyApplication - web : Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","","","","0","0","","1","/System/Server","","15506","com.sap.engine.services.jmx.MBeanServerInvoker","SAPEngine_Application_Thread[impl:3]_11","","Administrator",
    "08/06/2007","14:51:48:092","Exception com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ","Error","/System/Audit","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_11","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E00560000028C000014B800043706889A8DD7","com.sap.engine.services.deploy","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","","","","0","0","","1","/System/Audit","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_11","","Administrator",
    "08/06/2007","14:51:48:092","Application sap.com/MyApplication - web is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.","Error","/System/Server","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_11","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E00560000028B000014B800043706889A892C","com.sap.engine.services.deploy","sap.com/MyApplication - web,Server 0 1_41098,get its status,","sap.com/MyApplication - web,Server 0 1_41098,get its status,","","","","0","0","deploy_5005","1","/System/Server","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_11","","Administrator",
    "08/06/2007","14:51:34:357","Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 345 |  src: 2 target-node: 14109850 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=14109850,SAP_J2EECluster='' getApplicationStatus [Ljava.lang.Object;@6183fd [Ljava.lang.String;@208566 ]
    [EXCEPTION]
    javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application Server 0 1_41098 : Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application Server 0 1_41098 : Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ","Warning","/System/Server","com.sap.engine.services.jmx.MBeanServerInvoker","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E005800000008000014B80004370687C91D91","com.sap.engine.services.jmx.MBeanServerInvoker","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application Server 0 1_41098 : Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application Server 0 1_41098 : Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","javax.management.MBeanException: Exception invoking method getApplicationStatus
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
    Caused by: java.rmi.RemoteException: Error in getting status of application Server 0 1_41098 : Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    caused by -
    java.rmi.RemoteException: Error in getting status of application Server 0 1_41098 : Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1370)
    ,","","","","0","0","","1","/System/Server","","15506","com.sap.engine.services.jmx.MBeanServerInvoker","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    "08/06/2007","14:51:34:357","Exception com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ","Error","/System/Audit","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E005800000006000014B80004370687C906F5","com.sap.engine.services.deploy","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3864)
    ,","","","","0","0","","1","/System/Audit","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    "08/06/2007","14:51:34:357","Application sap.com/Server 0 1_41098 is not deployed on cluster element Server 0 1_41098 and it is not possible to get its status.","Error","/System/Server","com.sap.engine.services.deploy","","SAPEngine_Application_Thread[impl:3]_12","14109850:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc","001731BAFD2E005800000005000014B80004370687C8FE65","com.sap.engine.services.deploy","sap.com/Server 0 1_41098,Server 0 1_41098,get its status,","sap.com/Server 0 1_41098,Server 0 1_41098,get its status,","","","","0","0","deploy_5005","1","/System/Server","","15506","com.sap.engine.services.deploy","SAPEngine_Application_Thread[impl:3]_12","","Administrator",
    Thank you in advance!
    Alex

  • How to build ear files for ADF application using Ant task

    How to build ear files for ADF applications using Ant. The ojdeploy ant task can not find application-level deployment profiles. I am trying to automated build and release for ADF application.
    Any help is highly appreciated.
    Thanks
    Shiva

    Hi Timo
    Thanks for your reply.
    I have successfully created ear file using ojdeploy on jenkins. however when am trying to auto deploy using WLDeploy ant task am getting the following
    error :
    weblogic.application.ModuleException: :oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/oracle/webcenter/quicklinks/scopedMD" mapped to metadata-store-usage "WebCenterFileMetadataStore" but its definition was not found in MDS configuration
    Please advise how to handle this.
    As am a newbie to ADF, could you please advise if it is possible for the ADF application deployments can be automated for different environments using jenkins due to this MDS dependencies.
    Appreciate your help.
    Thanks
    Shiva

  • Deploying using ant to oc4j 10.0.3

    We previously deployed our application using ant to OC4J 902.
    Now we try to deploy to OC4J 10.0.3 but it seems that
    com.evermind.client.orion.OrionConsoleAdmin doesn't exist anymore.
    Could someone plz tell me by what it is replaced ?
    I found com.evermind.client.orion.OrionConsoleAdmin but i'm not shure of this is the right one

    Actually, I'd recommend that you not use the direct classname in your ant scripts (it's not really a public class) and instead fork off a Java process to run the public admin.jar utility. If Oc4JAdminConsole is ever changed, using admin.jar insulates you from it.
    It's basically the same, just runs the Jar file instead.
    <target name="deploy" depends="core">
    <java jar="${j2ee.home}/admin.jar" fork="yes">
    <arg value="${oc4j.deploy.ormi}"/>
    <arg value="${oc4j.deploy.username}"/>
    <arg value="${oc4j.deploy.password}"/>
    <arg value="-deploy"/>
    <arg value="-file"/>
    <arg value="${this.build}/${this.ear}"/>
    <arg value="-deploymentName"/>
    <arg value="${this.application.name}"/>
    </java>
    </target>
    See http://radio.weblogs.com/0132383/stories/2004/03/16/antDeploymentToOc4j.html
    for examples to do undeployent and webbindings.
    cheers
    -steve-

  • How to deploy jar file in WLS using ant script

    Hi,
    Im trying to deploy a jar file in weblogic 10.3 using ant script and am running into the below error.
    +[wldeploy] weblogic.management.DeploymentException: [J2EE:160177]The application at "/u01//RSJBObjects.jar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.+
    When i try to deploy the same manually from the console, i get a warning stating that WLS thought this as a library and hence proceeding to deploy as a library. After this warning the deployment continues and completes.
    Problem is when i try to deploy using ant, it breaks at this point.
    Is there any means that we can deploy a jar to WLS using ant script. This has to be deployed as a library as other apps would be using this jar.
    Im unable to create a ear file for this single jar file.
    If there is any suggestion on can this be done, please share.
    Thanks,
    Vijay.

    Hi Sunil,
    Thanks for the reply, it worked.
    Another doubt on the same lines. Now that the jar has been deployed as a library in WLS, when i try to deploy a WAR which refers to this deployed jar library, im unable to. I run into and error stating that the library is inaccessible.
    I have to bounce the server and before doing that, i have to manually copy the library.jar from <WLS_domain>/servers/AdminServer/upload/ directory to <WLS_domain>/lib/ directory, once copied i then try to deploy the WAR, then the deployment goes fine.
    Is there any means that this deployed library jar be made available soon after deployment and also to avoid copying the file.
    Thanks,
    Vijay.

  • Deploying servlet on Tomcat using "ant install" not working. Please help.

    Hello. Normally I can find answers by using search, but I can't today for some reason. So please bare with me if this has been mentioned before. I will try to provide as much info as possible so that helping me isn't too much a chore. Thank you.
    I have downloaded and installed the JWSDP 1.3. and Tomcat is running. I am also using Ant 1.5.4 (previous installation - not one included with JWSDP) and modeled my build.xml file after the template provided here:
    http://jakarta.apache.org/tomcat/tomcat-5.0-doc/appdev/build.xml.txt.
    When I run ant on my respository, everything builds fine. But when I run Ant with the install target, I get the following error:
    BUILD FAILED
    file:C:/owl/build.xml:366: java.io.IOException: Server returned HTTP response co
    de: 401 for URL: http://localhost:8080/manager/deploy?path=%2Fowl&war=file%3A%2F
    %2FC%3A%5Cowl%2Fbuild
    Here is line 366 build.xml:
    localWar="file://${build.home}"/>
    ...which is included in this block for the target "install":
    <target name="install" depends="compile"
    description="Install application to servlet container">
    <deploy url="${manager.url}"
    username="${manager.username}"
    password="${manager.password}"
    path="${app.path}"
    localWar="file://${build.home}"/>
    </target>
    When I point my brower to the url located in the error verbose, I get the following:
    FAIL - Encountered exception java.lang.NullPointerException
    I am trying to get my environment set up correctly before I start spending time developing servlets, but I am getting tempted to just develop to servlets and "manually" installing/deploying them either by copying and pasting or by using the Tomcat manager. I would really like to do everything from Ant though if possible. Please help.

    I don't think this is at all correct:
    localWar="file://${build.home}"/>You've got to create a real WAR file - a JAR file with WEB-INF and all its minions inside it:
    http://access1.sun.com/techarticles/simple.WAR.html
    That's the file you need to refer to there. You can manage that with Ant too, of course.
    Here's what my Ant build.xml looks like for Web apps (there's a build-web.properties file that follows):
    build-web.xml
    <project name="Tomcat Build Tasks" default="clean" basedir=".">
        <target name="init-props">
            <tstamp>
                <format property="touch.time" pattern="MM/dd/yyyy hh:mm aa" />
            </tstamp>
            <filterset id="ant.filters">
                <filter token="DATE" value="${TODAY}" />
                <filter token="TIME" value="${TSTAMP}" />
            </filterset>
            <!-- Load in all the settings in the properties file -->
            <property file="build.properties" />
            <!-- Load in all Tomcat settings in the properties file -->
            <property file="build-web.properties" />
        </target>
        <target name="prepare" depends="init-props">
            <mkdir dir="${war.classes}"/>
            <mkdir dir="${war.lib}"/>       
            <mkdir dir="${manifest}" />
        </target>
        <target name="clean" depends="init-props" description="clean up temporary files">
            <delete file="${project}.war" />   
            <delete dir="${war.root}"/>
            <delete dir="${manifest}" />
        </target>
        <target name="set-tomcat-classpath" depends="prepare">
            <path id="tomcat.class.path">                  
                <fileset dir="${tomcat.home}/bin">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
                <fileset dir="${tomcat.home}/shared/lib">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
                <fileset dir="${tomcat.home}/common/lib">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
                <fileset dir="${tomcat.home}/server/lib">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
                <fileset dir="${ant.home}/lib">
                    <patternset>
                        <include name="**/*.jar" />
                    </patternset>
                </fileset>
            </path>              
        </target>
        <target name="create" depends="set-tomcat-classpath" description="create the war file">
            <!-- All files at root level -->       
            <!-- Temporarily put the JSPs at root until you figure this out -->
            <copy todir="${war.root}">
                <fileset dir="${src.jsp}"/>
            </copy>
    <!--
            <copy todir="${war.root}">
                <fileset dir="${src.html}" includes="*.html"/>
            </copy>
    -->
            <copy todir="${war.root}/css">
                <fileset dir="${src.css}"/>
            </copy>
            <copy todir="${war.root}/images">
                <fileset dir="${src.images}"/>
            </copy>
            <copy todir="${war.root}/js">
                <fileset dir="${src.js}"/>
            </copy>
            <!-- All files at the WEB-INF level and below -->       
            <copy todir="${war.web}">
                <fileset dir="${src.etc}" includes="web.xml"/>
            </copy>
            <!-- All files in the CLASSPATH lib -->
            <copy todir="${war.web}/lib">
                <fileset dir="${src.lib}" includes="**/*.jar" excludes="**/*-tests.jar, **/junit.jar"/>
            </copy>
            <!-- Put the dispatcher XML in WEB-INF/config -->
            <copy todir="${war.web}/config">
                <fileset dir="${src.etc}" includes="${project}-config.xml"/>
            </copy>
            <!-- Put XSL stylesheets in WEB-INF/xsl -->
            <copy todir="${war.web}/xsl">
                <fileset dir="${src.xsl}" includes="**/*.xsl"/>
            </copy>
            <!-- Put the project JAR file in WEB-INF/lib -->
            <copy todir="${war.web}/lib">
                <fileset dir="${deploy}" includes="**/${project}.jar"/>
            </copy>
            <!-- Create the manifest -->
            <buildnumber />
            <manifest file="${manifest}/manifest.mf">
                <attribute name="Implementation-Title"      value="${project}" />
                <attribute name="Built-By"                  value="${user.name}"/>
                <attribute name="Build-Date"                value="${TODAY}" />
                <attribute name="Major-Version"             value="${major}" />
                <attribute name="Minor-Version"             value="${minor}" />
                <attribute name="Build-Number"              value="${build.number}" />
            </manifest>
            <!-- Create the WAR file -->
            <jar jarfile="${project}.war"
                 manifest="${manifest}/manifest.mf">
                <fileset dir="${war.root}"/>
                <metainf dir="${src.etc}" includes="context.xml"/>
            </jar>
        </target>
        <target name="create-tomcat-admin-tasks" depends="set-tomcat-classpath">
    <!--
            <pathconvert targetos="windows" refid="tomcat.class.path" property="converted.class.path" />
            <echo message="CLASSPATH: ${converted.class.path}" />
    -->       
            <taskdef name="install"     classname="org.apache.catalina.ant.InstallTask"     classpath="tomcat.class.path"/>
            <taskdef name="remove"      classname="org.apache.catalina.ant.RemoveTask"      classpath="tomcat.class.path"/>       
            <taskdef name="reload"      classname="org.apache.catalina.ant.ReloadTask"      classpath="tomcat.class.path"/>
            <taskdef name="deploy"      classname="org.apache.catalina.ant.DeployTask"      classpath="tomcat.class.path"/>       
            <taskdef name="undeploy"    classname="org.apache.catalina.ant.UndeployTask"    classpath="tomcat.class.path"/>       
            <taskdef name="start"       classname="org.apache.catalina.ant.StartTask"       classpath="tomcat.class.path"/>       
            <taskdef name="stop"        classname="org.apache.catalina.ant.StopTask"        classpath="tomcat.class.path"/>       
            <taskdef name="list"        classname="org.apache.catalina.ant.ListTask"        classpath="tomcat.class.path"/>       
            <taskdef name="resources"   classname="org.apache.catalina.ant.ResourcesTask"   classpath="tomcat.class.path"/>       
            <taskdef name="roles"       classname="org.apache.catalina.ant.RolesTask"       classpath="tomcat.class.path"/>
        </target>
        <target name="install" depends="create-tomcat-admin-tasks" description="install the war file on Tomcat">
            <install    url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}"
                        config="file:/${basedir}/${src.etc}/context.xml"
                        war="file:/${basedir}/${project}.war" />
        </target>
        <target name="remove" depends="create-tomcat-admin-tasks" description="remove the war file on Tomcat">
            <remove     url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}" />
        </target>
        <target name="reload" depends="create-tomcat-admin-tasks" description="reload the war file on Tomcat">
            <reload     url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}" />
        </target>
        <target name="deploy" depends="create-tomcat-admin-tasks" description="deploy the war file on Tomcat">
            <deploy    url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}"
                        config="file:/${basedir}/${src.etc}/context.xml"
                        war="file:/${basedir}/${project}.war" />
        </target>
        <target name="undeploy" depends="create-tomcat-admin-tasks" description="undeploy the war file on Tomcat">
            <undeploy   url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}" />
        </target>
        <target name="start" depends="create-tomcat-admin-tasks" description="start an application on Tomcat">
            <start      url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}"/>
        </target>
        <target name="stop" depends="create-tomcat-admin-tasks" description="stop an application on Tomcat">
            <stop       url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        path="/${project}" />
        </target>
        <target name="list" depends="create-tomcat-admin-tasks" description="list all applications running on Tomcat">
            <list       url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"/>
        </target>
        <target name="resources" depends="create-tomcat-admin-tasks" description="list all resources on Tomcat">
            <resources  url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"/>
        </target>
        <target name="data-sources" depends="create-tomcat-admin-tasks" description="list all data sources on Tomcat">
            <resources  url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"
                        type="javax.sql.DataSource"/>
        </target>
        <target name="roles" depends="create-tomcat-admin-tasks" description="list all user roles on Tomcat">
            <roles      url="${tomcat.manager.url}"
                        username="${tomcat.username}"
                        password="${tomcat.password}"/>
        </target>
    </project>
    build.properties
    # Properties file for setting up an Ant build.xml
    # Project specific items that change each time
    project=api-prototype
    major=1
    minor=0
    version=${major}.${minor}
    jar.name=${project}
    versiondate=${TODAY}
    # Directory structure (these should never change)
    bin=bin
    deploy=deploy
    doc=doc
    manifest=META-INF
    xml=xml
    # Everything under src should come out of a repository
    src=src
    src.bin=${src}/bin
    src.config=${src}/config
    src.data=${src}/data
    src.dtd=${src}/dtd
    src.java=${src}/java
    src.lib=${src}/lib
    src.profile=${src}/profile
    src.properties=${src}/properties
    src.schema=${src}/schema
    src.sql=${src}/sql
    src.templates=${src}/templates
    src.testdata=${src}/testdata
    src.xml=${src}/xml
    src.xsl=${src}/xsl
    # These are created and deleted by Ant each time
    javadocs=javadocs
    reports=reports
    output=output
    output.classes=${output}/classes
    output.lib=${output}/lib
    # Required for proper use of XDoclet
    xdoclet.home = C:/Tools/xdoclet-1.2b3
    build-web.properties
    war.root=war-root
    war.pages=${war.root}/pages
    war.web=${war.root}/WEB-INF
    war.classes=${war.web}/classes
    war.css=${war.web}/css
    war.js=${war.web}/js
    war.lib=${war.web}/lib
    war.tld=${war.web}/tld
    # Properties needed by Tomcat tasks
    ant.home =
    tomcat.home         =
    tomcat.manager.url  = http://localhost:8080/manager
    tomcat.username     =
    tomcat.password     = MOD

  • Deploying bpm 11g project sar file using ant task

    I am trying to deploy the bpm project using ant task file. The status I get is [deployComposite] ---->Deploying composite success. However when I check the deployments, they are not there. If I try to deploy this using Jdeveloper it works correctly. I need to get this to work for production deployments. Any suggestions?
    C:\Oracle\Middleware\Oracle_SOA1\bin>ant -f ant-sca-deploy.xml -DserverURL=http:
    //10.140.183.71:7001 -DsarLocation=N:\RuleBasedProjectInitiate\deploy\RequestPro
    ject.ear -Doverwrite=true -Duser=weblogic
    Buildfile: C:\Oracle\Middleware\Oracle_SOA1\bin\ant-sca-deploy.xml
    [echo] oracle.home = C:\Oracle\Middleware\Oracle_SOA1\bin/..
    deploy:
    [input] skipping input as property serverURL has already been set.
    [input] skipping input as property sarLocation has already been set.
    [deployComposite] created temp dir =C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cli
    ent_1279894885343
    [deployComposite] Creating HTTP connection to host:10.140.183.71, port:7001
    [deployComposite] Enter username and password for realm 'default' on host 10.140
    .183.71:7001
    [deployComposite] Authentication Scheme: Basic
    [deployComposite] Username:
    weblogic
    [deployComposite] Password:
    [deployComposite] Received HTTP response from the server, response code=200
    [deployComposite] clean up temp dir: C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cl
    ient_1279894885343
    [deployComposite] ---->Deploying composite success.
    BUILD SUCCESSFUL
    Total time: 4 seconds
    C:\Oracle\Middleware\Oracle_SOA1\bin>

    You can always deploy the ADF web apps from the Application (top menu) deploy option. Just make sure you're deploying the EAR profile for the project. Deploying the web projects from the composite deployment wizard can be convenient. But I think it's often the case that you deploy them (the composite and forms) separately (e.g. you make a series of changes to the composite without needed to redeploy the UI projects).
    Bottom line is you don't have to delete the projects to be able to modify/deploy them.

  • Java.lang.VerifyError when using ant 1.6.2

    In short, I get the VerifyError when deploying my .ear in Weblogic 8.1 SP2. I have nailed down the issue to this:
    I compile all my code using Ant 1.6.2. If I package the code up using ant 1.6.2 I get the VerifyError. If I pacakge the code up using ant 1.4, all is well. Note that when I deploy the 1.6.2 packaged ear file on Windows, all is well also.
    During the ant package target I assembly the war and ear using the core war and ear tasks.
    We are using precompiled JSPs in the war file. It seems that WL8.1 wants to recompile the JSP file. I am not sure why - the ant 1.4 packaged ear does not want to recompile the same JSP.
    The detailed error is:
    Servlet class jsp_servlet._portal.__capitalmarketsoverview for servlet /portal/CapitalMarketsOverview.jsp could not be verified.
    java.lang.VerifyError: (class: jsp_servlet/_portal/__capitalmarketsoverview, method: _jspService signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) Incompatible object argument for function call.>
    Any help is appreciated,
    Harry Duin

    Hello,
    I could not find an easy way to get the wls version of ant to start using the tasks you mention from ant 1.6.2.
    I tried defining the tasks using taskdef and also adding them to wls ant.jar and updating the deafult.properties file but the ant complained about unexpected elements in the build.xml file where I added the new tags (e.g import)
    If your really up against it you can try adding wls tasks to ant 1.6.2, they are listed here:
    http://e-docs.bea.com/wls/docs81/toolstable/ToolsTable.html#1009580
    Although I could not located exactly which jar they are in. Good luck.
    Cheers
    Hussein Badakhchani
    www.orbism.com

  • Using Ant to execute WLST setAppMetadataRepository command

    I am having a problem using Ant to execute the setAppMetadataRepository WLST command. This command puts an entry in adf-config.xml that points to the MDS datasource.
    This is the ant task that I'm using. These commands work from the WLST tool, but when using them with Ant, I get the error below.
       <target name="setAppMetadataRepositoryUsingWlst">
          <wlst debug="true" failonerror="true">
             <script>
                archive = getMDSArchiveConfig(fromLocation='C:/ADE/michande_platSavedSearch/commsplatform/ri/dist/comms-ri.ear')
                archive.setAppMetadataRepository(repository='mds-commsRepository',partition='riPartition', type='DB', jndi='jdbc/mds/commsRepository')
                archive.save()
            </script>
          </wlst>
       </target>Here is the error that I get (NameError: getMDSArchiveConfig). This is saying that getMDSArchiveConfig isn't a recognized command. Other commands (like connect(...)) work ok from ant, but not these MDS commands. Is this a bug or am I doing something wrong here?
    [wlst] <WLSTTask> All lines will be trimmed by 12
    [wlst] <WLSTTask> Line: archive = getMDSArchiveConfig(fromLocation='C:/ADE/michande_platSavedSearch/commsplatform/ri/dist/comms-ri.ear'). Final trim length: 12, String length: 124
    [wlst] <WLSTTask> Line: archive.setAppMetadataRepository(repository='mds-commsRepository',partition='riPartition', type='DB', jndi='jdbc/mds/commsRepository') . Final trim length: 12,
    String length: 147
    [wlst] <WLSTTask> Line: archive.save(). Final trim length: 12, String length: 26
    [wlst] <WLSTTask> The script that will be executed
    [wlst] archive = getMDSArchiveConfig(fromLocation='C:/ADE/michande_platSavedSearch/commsplatform/ri/dist/comms-ri.ear')
    [wlst] archive.setAppMetadataRepository(repository='mds-commsRepository',partition='riPartition', type='DB', jndi='jdbc/mds/commsRepository')
    [wlst] archive.save()
    [wlst]
    [wlst] Error: Error executing the script snippet
    [wlst] archive = getMDSArchiveConfig(fromLocation='C:/ADE/michande_platSavedSearch/commsplatform/ri/dist/comms-ri.ear')
    [wlst] archive.setAppMetadataRepository(repository='mds-commsRepository',partition='riPartition', type='DB', jndi='jdbc/mds/commsRepository')
    [wlst] archive.save()
    [wlst]
    [wlst] due to:
    [wlst] Traceback (innermost last):
    [wlst] File "<string>", line 1, in ?
    {color:red} [wlst] NameError: getMDSArchiveConfig{color}
    Thanks,
    Mike

    Not all WLST installations are equivalent. Have a read of [http://www.oracle.com/technetwork/articles/adf/part10-085778.html]this, specifically the paragraph right after Figure 13 for something to try. Bottom line - the WLST that comes with the base WLS server install cannot do the MDS operations.
    John

  • How to use ant with Jdeveloper 11g

    Hello, as we develop our app with ADF Faces & EJB 3.0 we are using tomcat 6.x + openEJB 3.0 as a sort of app server. So we need to build application archive 2 differrent methods (collapsed war for tomcat and ear for Jdev's integrated WLS). Besides, some xml files need to be modificated depending on target server. So we are going to use ant to build archives.
    My questions:
    - Where should I copy built archive for deployment on integrated WLS (should I copy it in ant's target or Jdev can do it for me)? Or there is another way to do the following: when one presses Run button on a page ant builds an archive for local WLS and then app is deployed and the page is opened in a new browser tab (just like default Jdev behaviour)?
    - Where can I find tutorial on integration of Jdev & ant?

    Here is a good example [http://biemond.blogspot.com/2009/04/weblogic-jdeveloper-ant-tasks.html]

  • Using Ant  or JUnit with Sun's Verifier

    Hi,
    I am trying to integrate Sun's J2EE "Verifier" into the build process. I am trying two different approaches, but am encountering similar issues.
    Using Ant
    One approach I am trying is with an Ant target. I keep getting this error "No local string for com.sun.enterprise.tools. ....etc...". I suspect the problem is with the setting of J2EE_HOME or the setting of a system property "com.sun.enterprise.home". I see this is set in verifier.bat...and I have decompiled Verifier.class and I see that this environmental variable is read at line 377 of Verifier.class. I am trying to set it...but ....there is the error that seems to indicate that the property file LocalStrings.properties is not being found. Of course the Verifier works when I run verifier.bat.
    <?xml version="1.0"?>
    <project name="verify" default="verify" basedir = "C:\j2sdkee1.3.1\">
    <target name="verify">
    <java fork="yes" classname="com.sun.enterprise.tools.verifier.Verifier">
    <classpath>
    <pathelement path="C:/j2sdkee1.3.1/lib/j2eetools.jar" />
              <pathelement path="c:/j2sdkee1.3.1/lib/j2ee.jar" />
    </classpath>
    <sysproperty key="com.sun.enterprise.home" value="C:\j2sdkee1.3.1\" />
         <sysproperty key="J2EE_HOME" value="C:\j2sdkee1.3.1\" />     
         <sysproperty key="LOCALEDIR" value="C:\j2sdkee1.3.1/lib/locale/" />          
    <arg value="C:/Ascential/RTIServer/apps/jboss/server/default/deploy/RTI.ear"/>
         <arg value="-oc:/verifierant/result"/>
    <arg value="-f"/>     
    </java>
    </target>
    </project>
    From JUnit
    I am trying to call the main() method of the Verifier...but getting similar "No local string..." errors.
    String[] args = { "I:\Release_30Sep2003\development\deploy\build\jboss\RTI.ear",
    "-oI:\Release_30Sep2003\development\deploy\build\jboss\results",
    "-f"};
    Verifier.main(args);
    Has anyone integrated this tool into Ant or Junit that could offer me some advice?
    Thanks,
    Mike Foley
    [email protected]

    How about running verifier.bat using ants exec task?

  • Deploy application using ant script vs shell script

    Hi,
    I work with OAS 10.1.2 and I'm using shell script with dcmctl command to deploy EAR into OC4J but I know that ant script do the same things. I want to know if my choice is good or is it better to use ant script ?
    Regards

    This is difficult to decide.
    When you have just a few ear files you deploy once in a while a shell script might be sufficient. When developing more complex systems you should use ant as this is easier to maintain.
    cu
    Andreas

  • Creating SDA (or other suitable archives) using ANT

    I have just competed writing a LoginModule that calls our product from WebAS. Until now I was using the NetWeaver Developer Studio to create the SDA file. But we need to create the SDA file (or onother suitable archive file) using ANT scripts so our automated build process can create it along with deployment files for other platforms. Please let me know if anyone can provide any info on this. Search of the forums and help has not yielded any result the whole day.
    Thanks in advance.
    Roshan

    Yes, about a month back I discovered that I dont have to rename the zip file, but was too lazy to write it here.
    About " do you have a task which deploys the sda to the server?" :
    Search the forum. I remember reading something about deploying. There is also a PDF doc "Deploying J2EE Applications on SAP NetWeaver". I can email it to you if you cant find it.
    I have some scripts that I copied from the forum but never used. You can check it out if it works:
    <target name="deploy">
         <property name="webas.j2ee.home" value="D:/usr/sap/TWD/JC00/j2ee" />
         <property name="webas.deploying.dir" value="${webas.j2ee.home}/deploying" />
         <property name="app.name" value="SALoginModule" />
         <property name="webas.user" value="Administrator" />
         <property name="webas.password" value="Integra7" />
         <exec dir="${webas.deploying.dir}" executable="${webas.deploying.dir}/deploymanager.bat">
              <arg value="$/sap/Deployer.xml"/>
         </exec>
         <telnet server="localhost" port="50008">
              <read>Login:</read>
              <write>${webas.user}</write>
              <read>Password:</read>
              <write>${webas.password}</write>
              <read>&gt;</read>
              <write>JUMP 0</write>
              <read>You jumped on node</read>
              <write>ADD DEPLOY</write>
              <read>&gt;</read>
              <write>START_APP ${app.name}</write>
              <read>&gt;</read>
         </telnet>
    </target>
    <project name="test_sdm" basedir="." default="deploy">
    <!--
    AUTHOR: David Beisert http://www.beisert-btc.de
    -->
    <!--property name="server" value="localhost"/>
    <property name="httpport" value="56000"/>
    <property name="sdmport" value="56018"/-->
    <property name="server" value="vmw0004"/>
    <property name="httpport" value="54100"/>
    <property name="sdmport" value="54118"/>
    <property name="SDM_HOME" value="C:/usr/sap/SNE/JC60/SDM"/>
    <target name="deploy">
         <taskdef name="sdm" classname="dbeisert.ant.ext.sap.SDMRemoteDeployTask" >
              <classpath >
                   <pathelement location="$/sdmAnt.jar"/>
                   <pathelement location="$\program\bin\SDM.jar"/>
                   <fileset dir="$\program\lib">
                   <include name="*/.jar"/>
                   </fileset>
              </classpath>
         </taskdef>
         <sdm
              host="$"
              port="$"
              password="sdm"
              archive="../MY_EAR/MY_EAR.ear"/>
    </target>
    </project>

Maybe you are looking for

  • How to show 2 views of a HTML Document

    Hello. I have 2 JEditorPanes. I want the first JEditorPane shows the document with colours, bold text... and the second JEditorPane shows the same document with tags. I have this code: editor1.setContentType("text/html"); editor2.setContentType("text

  • Problem of SAP WebAS Engine is starting...

    Dear experts,                     i am working properly in portal but some time an error automatically arise 503 Service Unavailable 7.00 SAP WebAS Engine is starting... If this state does not change within a few minutes, please contact your system a

  • Illustrator CS6 Update Error Problem

    Hi, as I have a problem with my Adobe Illustrator CS6 (Spanish Version) in Windows 8.1 Pro and me is that when I'll update via Adobe Updater, I get the following error: Actualización de Adobe Illustrator CS6 (versión 16.0.3) Error de instalación. Cód

  • Paint Component using scaled Graphics with TiledImage

    Hello, I am in the process of adding minor image manipulation in an application I created. I have paint overridden on the component that displays the image and in that component I am scaling the graphics to a representation of the image at 300 dpi ve

  • DATE Feild error

    Hi guru's and Expert I have a date field in which is in hte following format 25-4-2012 i get the below error Error View Display Error Odbc driver returned an error (SQLExecDirectW). Error Details Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P State: HY000.