Hot deploy API

Hi!
I have requirement to hot deploy/redeploy EJBs from my program. I know that
WLS Console has a UI to some API to do that. What are APIs? How can I get
it?
Thanks in advance
DJ

Hi,
          If I use weblogic.servlet.ServletServlet to try just the servlet , It
          works correctly.But When I develop it in a web application , there is a lot
          of hypelink to this servlet,thus I can't use the relative path reference to
          that servlet.I try to set the name of weblogic.servlet.ServletServlet same
          as the webapp,It doesn't work,how do I solve this problem?
          Thank you
          Pan
          Subject: Re: Hot deploy Servlet in webapp
          > http://www.weblogic.com/docs51/classdocs/API_servlet.html#134798
          >
          > It even explains why you shouldn't use it in production environment.
          >
          > Dimitri
          

Similar Messages

  • How to hot deploy EJB in Weblogic?

    Hi all,
    We use Weblogic 10.3 and EJB3.
    EJB has been build as ear and deployed in the server. And other deployed modules in server calls that.
    But the modification of EJB need to be rebuilt and restart the server.
    Does Weblogic support hot deploy for EJB? Do we need plugin or something else for this feature?
    Thanks a lot.

    Hi,
    The production redeployment strategy/hot deployment is supported for:
    a. Standalone Web Application (WAR) modules and Enterprise applications (EARs) whose clients access the application via a Web application (HTTP).
    b. Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.
    c. All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.
    Production redeployment is not supported for:
    a. Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.
    b. Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC for Oracle WebLogic Server.
    c. Applications that obtain JDBC data sources via the DriverManager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.
    d. Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.
    Please check the below Doc
    http://docs.oracle.com/cd/E14571_01/web.1111/e13702/redeploy.htm#
    Hope this answers your question!!
    Thanks,
    Vijaya

  • Hot Deploy

    When going through the "Creating a New Portal in a New Domain" whitepaper, everything works great until I get to the Hot Deploy. It begins Hot Deploying asks me for my username/password (weblogic/weblogic) continues along for a bit then constantly asks for my username/password. Any ideas?

    Hi Karen,
    This problem occurs when you don't have Internet access when you attempt hot-deploy (or your firewall blocks the ebcc).
    The DOCTYPE tag in the descriptor file specifies the dtd on Sun's website. When the ebcc fails to download the dtd, it
    (incorrectly) also fails to make the necessary changes to the application descriptor xml. Manually editing the application
    descriptor as you described should do the trick. In general, however, here is the workaround:
    1. Save the attached file to your hard drive (just save it to c:\).
    2. Edit the application.xml file as follows:
    a. First copy the entire DOCTYPE declaration and save it somewhere in a separate text file (in case want to revert back to it later).
    b. Edit the DOCTYPE declaration so that it looks like this:
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN' 'file:///application_1_3.dtd'>
    (Notice that the java.sun.com web address is replaced with a URI to the file on your hard drive.)
    3. Save your changes and hotdeploy will work with or without Internet access.
    Best Regards,
    Scott Ellis
    BEA Systems
    Karen Hensel wrote:
    I have had the same problem after following the directions multiple times. I could
    not get the portal to hot deploy or manually deploy from the console. It appears
    xml files are not being updated with the new portal information.
    I was finally able to get the portal deployed by adding (when the server was down,
    of course) a <module> to application.xml and a <WebAppComponent> to the config.xml.
    I'm still not sure things are fully correct.
    "Robert Costa" <[email protected]> wrote:
    I have tried 5 times now. The domain is created successfully but during
    the hot
    deploy of the portal, this is shown in the status window of the hot deploy:
    Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\portlets\Portlet1.portlet
    to sync list.
    Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\tools.wf
    to sync list.
    Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\webflow-extensions.wfx
    to sync list.
    Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\user_account.wf
    to sync list.
    Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\portal.wf
    to sync list.
    Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\security.wf
    to sync list.
    Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\testPortal.portal
    to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    At which time it begins prompting me for my username/password. The dialog
    box
    says:
    Logon (in titlebar)
    Connection:
    Server:
    Username:weblogic
    Password:
    Should connection and server have values? If so, why don't they? I
    followed
    the document completely.
    Thanks!
    "Daniel Selman" <[email protected]> wrote:
    Robert,
    Strange. Are there any clues in the EBCC or server logs you could post?
    Did
    you double check your password is correct by logging in to the console?
    Thanks,
    Daniel Selman
    "Robert Costa" <[email protected]> wrote in message
    news:[email protected]...
    When going through the "Creating a New Portal in a New Domain" whitepaper,everything works great until I get to the Hot Deploy. It begins Hot
    Deploying asks me for my username/password (weblogic/weblogic) continues
    along for a bit then constantly asks for my username/password. Anyideas?
    >
    <!--
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, U.S.A.
    All rights reserved.
    Sun Microsystems, Inc. has intellectual property rights relating to
    technology embodied in the product that is described in this document.
    In particular, and without limitation, these intellectual property
    rights may include one or more of the U.S. patents listed at
    http://www.sun.com/patents and one or more additional patents or
    pending patent applications in the U.S. and in other countries.
    This document and the product to which it pertains are distributed
    under licenses restricting their use, copying, distribution, and
    decompilation. This document may be reproduced and distributed but may
    not be changed without prior written authorization of Sun and its
    licensors, if any.
    Third-party software, including font technology, is copyrighted and
    licensed from Sun suppliers.
    Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail and and
    Enterprise JavaBeans are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries.
    Federal Acquisitions: Commercial Software - Government Users Subject to
    Standard License Terms and Conditions.
    DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
    CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
    WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
    NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
    DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, E'tats-Unis.
    Tous droits re'serve's.
    Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
    relatants a` la technologie incorpore'e dans le produit qui est de'crit
    dans ce document. En particulier, et sans la limitation, ces droits de
    proprie'te' intellectuels peuvent inclure un ou plus des brevets
    ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
    brevets plus supple'mentaires ou les applications de brevet en attente
    dans les E'tats-Unis et dans les autres pays.
    Ce produit ou document est prote'ge' par un copyright et distribue'
    avec des licences qui en restreignent l'utilisation, la copie, la
    distribution, et la de'compilation. Ce documention associe n peut
    e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
    l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
    licence, le cas e'che'ant.
    Le logiciel de'tenu par des tiers, et qui comprend la technologie
    relative aux polices de caracte`res, est prote'ge' par un copyright et
    licencie' par des fournisseurs de Sun.
    Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail et and
    Enterprise JavaBeans sont des marques de fabrique ou des marques
    de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
    pays.
    LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
    DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
    EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
    NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
    L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
    CONTREFAC,ON.
    -->
    <!--
    This is the XML DTD for the J2EE 1.3 application deployment
    descriptor. All J2EE 1.3 application deployment descriptors
    must include a DOCTYPE of the following form:
    <!DOCTYPE application PUBLIC
         "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
         "http://java.sun.com/dtd/application_1_3.dtd">
    -->
    <!--
    The following conventions apply to all J2EE deployment descriptor
    elements unless indicated otherwise.
    - In elements that contain PCDATA, leading and trailing whitespace
    in the data may be ignored.
    - In elements whose value is an "enumerated type", the value is
    case sensitive.
    - In elements that specify a pathname to a file within the same
    JAR file, relative filenames (i.e., those not starting with "/")
    are considered relative to the root of the JAR file's namespace.
    Absolute filenames (i.e., those starting with "/") also specify
    names in the root of the JAR file's namespace. In general, relative
    names are preferred. The exception is .war files where absolute
    names are preferred for consistency with the servlet API.
    -->
    <!--
    The application element is the root element of a J2EE application
    deployment descriptor.
    -->
    <!ELEMENT application (icon?, display-name, description?, module+,
              security-role*)>
    <!--
    The alt-dd element specifies an optional URI to the post-assembly
    version of the deployment descriptor file for a particular J2EE module.
    The URI must specify the full pathname of the deployment descriptor
    file relative to the application's root directory. If alt-dd is not
    specified, the deployer must read the deployment descriptor from the
    default location and file name required by the respective component
    specification.
    Used in: module
    -->
    <!ELEMENT alt-dd (#PCDATA)>
    <!--
    The connector element specifies the URI of a resource adapter archive
    file, relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT connector (#PCDATA)>
    <!--
    The context-root element specifies the context root of a web
    application.
    Used in: web
    -->
    <!ELEMENT context-root (#PCDATA)>
    <!--
    The description element is used to provide text describing the parent
    element. The description element should include any information that
    the application ear file producer wants to provide to the consumer of
    the application ear file (i.e., to the Deployer). Typically, the tools
    used by the application ear file consumer will display the description
    when processing the parent element that contains the description.
    Used in: application, security-role
    -->
    <!ELEMENT description (#PCDATA)>
    <!--
    The display-name element contains a short name that is intended to be
    displayed by tools. The display name need not be unique.
    Used in: application
    Example:
    <display-name>Employee Self Service</display-name>
    -->
    <!ELEMENT display-name (#PCDATA)>
    <!--
    The ejb element specifies the URI of an ejb-jar, relative to the top
    level of the application package.
    Used in: module
    -->
    <!ELEMENT ejb (#PCDATA)>
    <!--
    The icon element contains small-icon and large-icon elements that
    specify the file names for small and a large GIF or JPEG icon images
    used to represent the parent element in a GUI tool.
    Used in: application
    -->
    <!ELEMENT icon (small-icon?, large-icon?)>
    <!--
    The java element specifies the URI of a java application client module,
    relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT java (#PCDATA)>
    <!--
    The large-icon element contains the name of a file
    containing a large (32 x 32) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <large-icon>employee-service-icon32x32.jpg</large-icon>
    -->
    <!ELEMENT large-icon (#PCDATA)>
    <!--
    The module element represents a single J2EE module and contains a
    connector, ejb, java, or web element, which indicates the module type
    and contains a path to the module file, and an optional alt-dd element,
    which specifies an optional URI to the post-assembly version of the
    deployment descriptor.
    The application deployment descriptor must have one module element for
    each J2EE module in the application package.
    Used in: application
    -->
    <!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
    <!--
    The role-name element contains the name of a security role.
    The name must conform to the lexical rules for an NMTOKEN.
    Used in: security-role
    -->
    <!ELEMENT role-name (#PCDATA)>
    <!--
    The security-role element contains the definition of a security
    role. The definition consists of an optional description of the
    security role, and the security role name.
    Used in: application
    Example:
    <security-role>
         <description>
         This role includes all employees who are authorized
         to access the employee service application.
         </description>
         <role-name>employee</role-name>
    </security-role>
    -->
    <!ELEMENT security-role (description?, role-name)>
    <!--
    The small-icon element contains the name of a file
    containing a small (16 x 16) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <small-icon>employee-service-icon16x16.jpg</small-icon>
    -->
    <!ELEMENT small-icon (#PCDATA)>
    <!--
    The web element contains the web-uri and context-root of a web
    application module.
    Used in: module
    -->
    <!ELEMENT web (web-uri, context-root)>
    <!--
    The web-uri element specifies the URI of a web application file,
    relative to the top level of the application package.
    Used in: web
    -->
    <!ELEMENT web-uri (#PCDATA)>
    <!--
    The ID mechanism is to allow tools that produce additional deployment
    information (i.e., information beyond the standard deployment
    descriptor information) to store the non-standard information in a
    separate file, and easily refer from these tool-specific files to the
    information in the standard deployment descriptor.
    Tools are not allowed to add the non-standard information into the
    standard deployment descriptor.
    -->
    <!ATTLIST alt-dd id ID #IMPLIED>
    <!ATTLIST application id ID #IMPLIED>
    <!ATTLIST connector id ID #IMPLIED>
    <!ATTLIST context-root id ID #IMPLIED>
    <!ATTLIST description id ID #IMPLIED>
    <!ATTLIST display-name id ID #IMPLIED>
    <!ATTLIST ejb id ID #IMPLIED>
    <!ATTLIST icon id ID #IMPLIED>
    <!ATTLIST java id ID #IMPLIED>
    <!ATTLIST large-icon id ID #IMPLIED>
    <!ATTLIST module id ID #IMPLIED>
    <!ATTLIST role-name id ID #IMPLIED>
    <!ATTLIST security-role id ID #IMPLIED>
    <!ATTLIST small-icon id ID #IMPLIED>
    <!ATTLIST web id ID #IMPLIED>
    <!ATTLIST web-uri id ID #IMPLIED>

  • Hot deploying jsp tags

    Hi does anybody out there no how to hot -deploy non ejb classes .Like jsp
              tags for example? It is extremely to code them without a hot deployment
              ability.
              Thanks in advance
              Jeff Anderson
              

    Cameron,
              In general, what kind of "interesting bugs" and "design flaws" do you mean?
              I would expect that using any kind of cache can allow for bugs due to developers
              confusion... but are there inherent "bugs" (or design flaws) that are built into
              WL's Cache tag?
              Jack Lin
              Cameron Purdy wrote:
              > Install the latest SP. They are (relatively speaking) resource intensive.
              > However, properly implemented/used, this relative cost is close to 0.
              > (Instantiating a Java class and calling a few empty methods uses a couple
              > hundred clock cycles on a good JVM.) BTW Pooling is considerably more
              > expensive for simple objects than instantiating new ones. Also, due to
              > design flaws in the custom tag API, pooling JSP tags could lead to some
              > interesting bugs related to the lack of re-initialization.
              >
              > --
              >
              > Cameron Purdy
              > [email protected]
              > http://www.tangosol.com
              > WebLogic Consulting Available
              >
              > "Anthony Raiti" <[email protected]> wrote in message
              > news:39d4a35f$[email protected]..
              > We are researching JSP Tags as a method of seperating our creative and
              > coding efforts. Our research is showing that JSP tags is a resource hog and
              > noticed that none of the JSP Tags are being pooled. Docs that we have looked
              > at suggest that pooling does occur, but we do not see it happening. Is
              > anyone using this technology and if so how is the performance?
              

  • Weblogic deployment APIs giving error for deployment on weblogic 10.3.2

    I am using weblogic deployment APIs to distribute my war file on weblogic 10.3.2 but it gives the following error on distribute
    weblogic.management.ManagementException: [Deployer:149003]Unable to access application source information in '<!DOCTYPE HTML PUBLIC "-/W3C/DTD HTML 4.0 Draft/EN">/app/jamagent.war' for application 'jamagent.war'. The specific error is: No application files exist.
    My sample code is below.
    DeploymentOptions options = null;     
    Target[] targets = myConnectedManager.getTargets();     
    Class wlsFactoryClass = Class.forName("weblogic.deploy.api.tools.SessionHelper");
    Method m = wlsFactoryClass.getDeclaredMethod("getDeploymentManager",new Class[]{String.class,String.class,String.class,String.class});
    m.setAccessible(true);
    WebLogicDeploymentManager myConnectedManager = (WebLogicDeploymentManager)m.invoke(wlsFactoryClass, new Object[]{hostname,port,weblogicUsername,weblogicPasswd});
    myConnectedManager.enableFileUploads();
    options = new DeploymentOptions();
    options.setName(destWarName);
    ProgressObject po = myConnectedManager.distribute(targets, new File("/tmp/jamagent_orig.war), null,options);
    The header of web.xml is
    <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
    Can someone help why this is happening? I am not including weblogic-application.xml in the war file as i think this is not required for a war file. Is that the reason?
    Edited by: user790199 on Dec 28, 2009 7:37 AM

    Hi,
    The DTD used in "web.xml" should not cause any issue ...though it's the OLD "web.xml"...Please try to run the Following command to Generate the New Deployment Descriptors from the Existing Application:
    Step1). Open a Command Window and Run "setWLSEnv.sh" or "setWLSEnv.cmd".
    Step2). In the Command Prompt move to the Current Directory where you have placed your Application and then Run the Following Command
    java weblogic.DDConverter  -d NewDDs  jamagent.war
    Here Above Command Will read the "jamagent.war" War archive and then It will generate the New DDs in "NewDDs" directory...Which we need to replace with the OLD DDs present in our WebApplication..
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

  • Com.sap.tc.webdynpro.services.sal.deployment.api.WDClassLoaderException:

    my application run sucessfully for past copule of weeks but
    now it show the following exception and i can't able to see my
    output window.... i dont know why
    The Exception is:
    com.sap.tc.webdynpro.services.sal.deployment.api.WDClassLoaderException: Classloader of 'local/Certification' is null, even though application is started.
    if anyone knows, please help me....
    thank you

    Hi,
    plz check the values of all attributes.
    Suppose the values is not there(null) and ur checking some conditions based on this value.
    Null pointer exception will araise due to any nullvalue.
    To avoid this plz put the check--> if(!value = null){........ }.
    Reagrds,
    Lavanya.G

  • Creation of InitialContext fails when i hot-deploy scheduler-service.xml

    Creation of InitialContext fails when i hot-deploy scheduler-service.xml
    I configured scheduler-service as follows in Jboss 3.2:
    scheduler-service.xml
    <mbean code="org.jboss.varia.scheduler.Scheduler"
         name=":service=Scheduler">
    <attribute name="StartAtStartup">true</attribute>
    <attribute name="SchedulableClass">com.beta.my.utils.FMScheduler</attribute>
    <attribute name="SchedulableArguments">Schedulabe Test,12345</attribute>
    <attribute name="SchedulableArgumentTypes">java.lang.String,int</attribute>
    <attribute name="InitialStartDate">0</attribute>
    <attribute name="SchedulePeriod">10000</attribute>
    <attribute name="InitialRepetitions">-1</attribute>
    </mbean>
    Schedulable Class
    package com.beta.my.utils;
    import java.util.Date;
    import org.jboss.varia.scheduler.Schedulable;
    public static class FMScheduler
    implements Schedulable
    private String mName;
    private int mValue;
    public FMScheduler(String pName,int pValue)
    mName = pName;
    mValue = pValue;
    public void perform(Date pTimeOfCall,long pRemainingRepetitions)
    try {
              Context context = new InitialContext();//properties taken from jndi.properties file
              } catch (Exception e){
                   e.printStackTrace();
    I started my jboss..,FMScheduler created successfully, perform method in FMScheduler called succesfully after SchedulePeriod(1000)
    The problem occurs(NullPointerException) while i changed SchedulePeriod time and hot-deployed(just saved scheduler-service.xml).
    The following Exception occures due to InitialContext creation fails*(Context context = new InitialContext();)* in FMScheduler.
    17:46:27,361 ERROR [STDERR] java.lang.NullPointerException
    17:46:27,361 ERROR [STDERR] at org.jboss.mx.loading.UnifiedClassLoader.findR
    esources(UnifiedClassLoader.java:374)
    17:46:27,361 ERROR [STDERR] at java.lang.ClassLoader.getResources(ClassLoade
    r.java:825)
    17:46:27,361 ERROR [STDERR] at com.sun.naming.internal.VersionHelper12$5.run
    (VersionHelper12.java:145)
    17:46:27,361 ERROR [STDERR] at java.security.AccessController.doPrivileged(N
    ative Method)
    17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.VersionHelper12.getRe
    sources(VersionHelper12.java:142)
    17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.ResourceManager.getAp
    plicationResources(ResourceManager.java:468)
    17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.ResourceManager.getIn
    itialEnvironment(ResourceManager.java:159)
    17:46:27,377 ERROR [STDERR] at javax.naming.InitialContext.init(InitialConte
    xt.java:215)
    17:46:27,377 ERROR [STDERR] at javax.naming.InitialContext.<init>(InitialCon
    text.java:195)
    17:46:27,377 ERROR [STDERR] at com.beta.my.utils.FMScheduler.perform
    (FMScheduler.java:42)
    17:46:27,392 ERROR [STDERR] at org.jboss.varia.scheduler.Scheduler$Listener.
    handleNotification(Scheduler.java:1263)
    17:46:27,392 ERROR [STDERR] at org.jboss.mx.server.NotificationListenerProxy
    .handleNotification(NotificationListenerProxy.java:69)
    17:46:27,392 ERROR [STDERR] at javax.management.NotificationBroadcasterSuppo
    rt.sendNotification(NotificationBroadcasterSupport.java:95)
    17:46:27,392 ERROR [STDERR] at javax.management.timer.Timer.sendNotification
    s(Timer.java:441)
    17:46:27,392 ERROR [STDERR] at javax.management.timer.Timer.access$000(Timer
    .java:31)
    17:46:27,408 ERROR [STDERR] at javax.management.timer.Timer$RegisteredNotifi
    cation.doRun(Timer.java:612)
    17:46:27,408 ERROR [STDERR] at org.jboss.mx.util.SchedulableRunnable.run(Sch
    edulableRunnable.java:164)
    17:46:27,408 ERROR [STDERR] at org.jboss.mx.util.ThreadPool$Worker.run(Threa
    dPool.java:225)
    please help me if u have any idea,thanks

    Hi Hamsa,
    Did you also create and configure an "Execution Destination"?
    You can test the Metadata destination configuration on Web Service Navigator.
    On the web service navigator (http://hostname:portnumber/wsnavigator) search in the metatda destination you have created for the service you imported in web dynpro as a model. If you can find it there test it on the ws navigator.
    Best regards,
    Yasar

  • Hot deployment of class files (non-EJB)

     

    Also posting to the servlet newsgroup.
    "Craig Ambrose" <[email protected]> wrote in message
    news:[email protected]..
    >
    I am using WebLogic 6.1 and am interested in using auto-deployment indevelopment
    mode of JSPs and class files that those JSPs rely on. I have a simpleWebLogic
    application that gets deployed using the exploded directory format andwhen I
    modify the JSPs or the class files that they use everything reloadsproperly and
    a newly modified class file will be reloaded the next time the pageutilizing
    the Java class is requested.
    I have a much more complicated application (the one I am really doing workon)
    and I can't get the hot deploy of the class files to take effect. The JSPswill
    reload but I can't seem to cause the class loader to reload any changedclass
    files. If I use the WebLogic Console and un-deploy and then re-deploy theapplication
    then the class files will be reloaded, but I thought that wasn't necessaryfor
    hot deployment. This complex application stores many things in the HTTPsession
    context. I am wondering if that has an effect on the class loader fordependant
    class files.
    I'm pretty sure it is not a configuration issue as I have it working forthe simple
    application. I have the application deployed under the.\config\<domainname>\applications
    directory and am using the exploded directory format with the class filesalso
    exploded in the WEB-INF\classes directory.
    Any insights on dependancies of the hot depployment would be helpful.

  • Hot deployment of servlet

    hi
    i have compiled the servlet in jdeveloper and set the path to oc4j../../web-inf/classes path;after compiling the class Is it neccassary to shutdown the oc4j container;
    after shutdown the container only i am seeing the effect;without shutdown the container can we see the effect;we can do it Tomcat ;Is there any facility in OC4J ;
    bye
    chaitanya

              Hi, suppose you have the servlet called JoeServlet and registered as joeservlet with an argument, say, a file joe.txt. If you want to 'hot' deploy the JoeServlet you should make sure that a) the servlet's name must be unique b) the servlet's class must be in your servlet classpath (see the properties sheet aside) c) the initial argument, say: joeargument=./joe.txt, must match the the name expected by your servlet (eg. getInitParameter("joeargument")). If you have done correctly WLS must work.
              Joe
              "Jayesh Patel" <[email protected]> wrote:
              >
              >I am trying to hot deploy a simple servlet using weblogic console.
              >
              >I am getting error saying that
              >
              >"Property change error for property "RegisterNewServlet".
              >Servlet could not be loaded or instantiated"
              >
              >I am sure that servlet class I am trying to load is in servlet
              >class path.
              >
              >Any idea what is going wrong here.
              >
              >Thanks.
              >
              >
              >
              

  • Hot deployment of Plugin on OIM cluster

    Does someone  know , how to deploy(re-register) the plugin(event Handler ,schedule Task etc.) on OIM cluster in real time.
    I have observed  that when i do re-register the plugin(after any code changes etc.) from one of the nodes of the cluster, the new code does not get reflected on all the nodes.
    It works from one or two nodes but not from all nodes.
    Even after doing Purge Cache from all nodes the behavior remains the same.(Restart of OIM will do the trick, but i need hot deployment)
    Any ideas?
    Thanks
    Akshat

    That's what I have observed that even though the documentation says that PurgeCache.sh will do the trick but it never works. You have to restart the OIM Servers.

  • Servlet hot deployment with a webApp

    Hi everybody,
    Does anybody know something about hot deployment of servlets in a web
    application (.war) ?
    I tried many things (setting reloadCheckSecs in properties, in web.xml,
    hot-deploy from console...) but nothing really worked.
    So I have to register a servlet for hot deployment in the properties, but
    then it doesn't belong to the application.
    Thanx,
    Markus.

    I presume you are on 51.
    we do not support hot deployment of webapps in 51. We support this in 6.0
    Kumar
    "M. Hammer" wrote:
    Hi everybody,
    Does anybody know something about hot deployment of servlets in a web
    application (.war) ?
    I tried many things (setting reloadCheckSecs in properties, in web.xml,
    hot-deploy from console...) but nothing really worked.
    So I have to register a servlet for hot deployment in the properties, but
    then it doesn't belong to the application.
    Thanx,
    Markus.

  • Servlet Hot-Deploy with a WebApp

    Hi everybody,
    Does anybody know something about hot deployment of servlets in a web
    application (.war) ?
    I tried many things (setting reloadCheckSecs in properties, in web.xml,
    hot-deploy from console...) but nothing really worked.
    So I have to register a servlet for hot deployment in the properties, but
    then it doesn't belong to the application.
    Thanx,
    Markus.

    Are u saying that WARs are redeployed automatically but not individual servlets,
    or neither?
    Thanks.
    Viresh Garg wrote:
    Currently the automatic hot deployment of a servlet/JSP from exploaded WAR is
    broken. We are in the process of fixing it for next release. You have to
    redeploy your web application right now, for the change to take place.
    Viresh Garg
    Principal Developer Relations Engineer
    BEA Systems
    "M. Hammer" wrote:
    Hi everybody,
    Does anybody know something about hot deployment of servlets in a web
    application (.war) ?
    I tried many things (setting reloadCheckSecs in properties, in web.xml,
    hot-deploy from console...) but nothing really worked.
    So I have to register a servlet for hot deployment in the properties, but
    then it doesn't belong to the application.
    Thanx,
    Markus.

  • Hot deployment while running...

    Hi there!
    Does any body have experience HotDeployment while end user are using the application?
    For my self I got a real problem with HttpSession. After hot deployment all
    sessions are invalidate!! I mean "request.getSession(false)" return false. I
    have already carefully read documentation and pointed out that object store in
    session must be serializable. OK it's done. Now what else should I check?
    Thanks!

    redeploying will invalidate a servlet session. this is not a bug, but rather the intended
    behavior.
    if all you want to do is update content (jsp's, html, gif, jpeg, etc) you can use the
    refresh tool.
    it is a light-weight operation, instead of the heavyweight redeploy.
    to use it, please run the command:
    java weblogic.management.tools.WebAppComponentRefreshTool
    (this tool is compatible with 6.0 and 6.1)
    tracey
    "Thierry Giguère" wrote:
    Hi there!
    Does any body have experience HotDeployment while end user are using the application?
    For my self I got a real problem with HttpSession. After hot deployment all
    sessions are invalidate!! I mean "request.getSession(false)" return false. I
    have already carefully read documentation and pointed out that object store in
    session must be serializable. OK it's done. Now what else should I check?
    Thanks!

  • Hot deployment

    Hi,
    I have a gateway which instantiates and runs applications. Each application implements an interface so the gateways only sees the class at type (interface).
    I have a huge problem in that we have a number of developers working on these applications. There are constantly bug fixes, new functionality etc. that must be added.
    How can I hot deploy these classes? I cannot restart the entire gateway every time I upload a class. This affects all the other applications.
    I have looked at dynamic class loading but this is going to take some serious time to create a custom class loader that will actually destroy old class loaders when creating new ones.
    Is there a simpler way to enable my gateway for hot deployment?
    thanks!

    Creating a new classLoader does not take a lot, and you can tell it NOT to cache the class.
    Also, you can simply destroy all current references to a class when running, replace the class file, and then allow code to call the class object again - thus reading the new class file.
    It's not typically a good idea to deploy-in-production any code.

  • Hot Deploying Servlets from the command line

    Is it possible to hot deploy a servlet from the command line?
              

    Use the mbocutil command line tool located in:
    server root/bin/msg/admin/bin
    You can create a folder with spaces by using quotes like thus:
    ./mboxutil -c "user/Tuser/Test Folder"
    -Chris

Maybe you are looking for