Deploying EJB to an existing application

hi!
I've got an existing J2EE-application with many EJBs. Now I want to add 1 EJB to it.
If I deploy this EJB, the application.xml within the existing application ist replaced by the
application.xml of the deployed one. In this case, none of the old EJBs is startable.
The only possibility to get it to work, is to change the application.xml after deployment (insert all existing
<module> tags) or replacing the application.xml within the ear-file manually.
Is there a better way? (within an application of 10 EJBs this shouldn't be a problem, but in our case with more than 100 EJBs, it is tedious)
cu
ed

What I understand your posting that you have an existing application with say 10 EJBs and you overwrite the application.xml with new info about just the new EJBs. If you do so then application will lose the reference about the old EJBs and hence the old EJBs will not be available for use.
You can deploy the new EJBs in a separate application and use the parent attribute to make parent/child relation between applications.
The best way to redeploy is to package the EJBs in an EAR and redeploy the EAR. If your EAR is in $OC4J_HOME/j2ee/home/applications directory then replacing the EAR also redploys your application. You can use ant or tools like JDev to build your EAR.
regards
Debu

Similar Messages

  • How to create a deployment plan for an existing application?

    Using WebLogic 10MP1.
    I have an existing EAR deployment, and I want to create a deployment plan so I can make changes to it without changing the EAR file itself. My goal is to change the value of the "precompile" flag in all the web modules.
    I've read the documentation on creating deployment plans, and it doesn't seem like it's doing anything. That is, I was able to run "weblogic.PlanGenerator" from the command line, but that's about my only success.
    The doc says that if you make a change to the app config and save it, that will prompt for a place to save the deployment plan. This seems odd, as I'm pretty sure I've never seen a prompt like that before. It didn't happen for me. As a test, I tried changing the "Deployment Order" field. I activated it, and then I changed it back and activated that. No deployment plan prompt.
    I then read that if there is a "plan" subdirectory off the application root containing the deployment plan, WebLogic will use that at deployment. So, I created a "plan" subdir in my EAR tree, put the generated (from "weblogic.PlanGenerator") plan there, and restarted. I didn't notice any log message about the plan, and when I logged into the console to check the "Deployment Plan" tab on the deployment ("Tuning Parameters" subtab), it says "No variables present".
    I must be missing some simple detail.

    In case anyone else ever has this problem, I've been able to resolve this.
    I used "weblogic.planGenerator" on the command line to get a deployment plan to start with. The obstacle I had was actually finding the "Update" button. For some reason I had thought this button the docs refer to was on the "Deployment Plan" tab in the configuration of the deployment. It's actually on the list of the deployments, and is active when the deployment you want to configure is checked.
    Once I got there, I was able to enter the path to my deployment plan, which I edited to produce the result I wanted (turning on "precompile" on most of the modules). Once I stored all that and restarted my server, I was able to verify that the server was precompiling on deployment (although it's hard to tell if I don't have any JSP compile errors. :) ).

  • Time Out error in deploying EJB in Sun's application server

    I am facing the problem of time out error in sun's application server when deploy tool and application server is running in the same system. can any one solve my problem

    Hi,
    How big is your EJB application? i.e. how many EJBs do you have?
    Would you please try to deploy your application using the command line tool "asadmin" and see if it is also hanging? This will help us to tell if the deployment process that is hanging or the deploytool itself that is hanging. The "asadmin" tool is located under $INSTALL_HOME/bin.
    Thanks,
    Q^2

  • Error while deploying WC application: Unable to deploy EJB

    Hi All,
    we are getting the below error quite frequently, whenever we deploy the application to server:
    [03:35:14 AM] Weblogic Server Exception: weblogic.application.ModuleException: Exception preparing module: EJBModule(CAWrapperEJB.jar)
    Unable to deploy EJB: CAService from CAWrapperEJB.jar:
    [EJB:011055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    [03:35:14 AM] Caused by: java.lang.Throwable: Substituted for missing class [EJB - 11055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAnService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    [03:35:14 AM] See server logs or server console for more details.
    -to solve this issue we just delete the cache and restart the Managed server.
    Please tell me what is the cause of this error and how can we fix it permanently, as restarting the server everytime is not very convenient.
    TIA,
    Bob

    The content of "weblogic-ejb-jar.xml" present in code is:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd"
    xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar">
    </weblogic-ejb-jar>

  • Unable to deploy EJB application

    Hi iam getting the following exception while deploying an EJB application in WebLogic 8.1
    Exception:weblogic.management.ApplicationException: prepare failed for Addition
    Module: Addition Error: Exception preparing module: EJBModule(Addition,status=NEW)
    Unable to deploy EJB: Addition.jar from Addition.jar:
    Compiler failed executable.exec
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
    what might be the reason for this exception ????

    This problem is caused by the way WebLogic calls javac to compile the generated classes for the EJBs deployment. This became a big problem for our project with 50 Entity EJBs 2.0 with CMP/CMR, about 15 EJB-QL statements, 3 MDB and 8 Session EJB. I think that these numbers are limits, so exceeding any of these numbers cause javac to exhaust the memory it allocates by default. Even the WebLogic 8.1.Server's administarion console allows you to supply additional parameters for RMI and EJB compilers, it does not allow to supply the -J-Xmx256M (or more) option needed to increase the memory javac allocates.
    Thus:
    1. In the active $JAVA_HOME/bin of the Server create the file:
    Windows:
    javac1.cmd Containing:
    javac -J-Xmx256M %*
    Linux:
    javac1.sh Containing:
    #!/bin/bash
    javac -J-Xmx256M $*
    make it "executable"
    NOTE: startWeblogic script sets it own JAVA_HOME, so check it first.
    2. In the administraitve console of WebLogic 8.1 Server select the server in the left frame under the
    <Domain> / Servers branch. In the right frame select the General tab.
    3. In the Java Compiler box change javac to javac1.cmd or javac1.sh respectively. No restart is needed.
    This solved our problem.
    I could not find any solution published, hopefully this will help other colleagues.
    Rusi Popov

  • BC4J EJB deployment ; testing deployment to 8i with client application

    Hi,
    Is there a way to to connect a java client application to a 8i deployed BC4J using the oracle.dacf.dataset.SessionInfo ? Can we do this using the JDev wizards - property inspector ?
    (I've seen in the doc :"Testing a Business Components EJB Deployed to Oracle8i with a Code Client" but the given code
    // setup application module variable
    ApplicationModule appMod = null;
    javax.naming.Context ic = new InitialContext(env);
    ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(DeployedMod);
    appMod = home.create();
    does not contains any SessionInfo object.)
    Thanks,
    Xvc

    Chris,
    Perhaps you should be checking if the user you wish to deploy
    EJBs to has at least JAVAUSERPRIV.
    As SYSTEM
    grant JAVAUSERPRIV to <user>;
    Good luck
    /Mark
    Chris Jones (guest) wrote:
    : Hi,
    : I'm having a problem deploying an EJB to Oracle 8i with
    : JDeveloper 2.0.
    : I am receiving an insufficient privileges error in the
    : deployment process when it reaches the stage Generating EJBHome
    : and EJBObject on the server. I am logging in using the system,
    : sys, scott or internal account and all still receive the same
    : error. What role/privelege do I need to deploy an ejb to 8i?
    : Thanks in advance.
    : Here is a dump of the output JDeveloper produces.
    : *** Invoking the Oracle JDeveloper deployment utility ***
    : Scanning project files...done
    : Generating classpath dependencies...done
    : Generating archive entries table...done
    : Writing archive...done
    : *** Invoking the Oracle8i deployment utility ***
    : Reading Deployment Descriptor...done
    : Verifying Deployment Descriptor...done
    : Gathering users...done
    : Generating Comm Stubs...done
    : Compiling Stubs...done
    : Generating Jar File...done
    : Loading EJB Jar file and Comm Stubs Jar file...done
    : Generating EJBHome and EJBObject on the
    : server...oracle.aurora.server.tools.sess_iiop.ToolsException: A
    : SQL exception occured while compiling:
    : oracle.aurora.ejb.gen.test_MyEJB.EjbObject_MyEJB : ORA-01031:
    : insufficient privileges
    : at oracle.aurora.server.tools.sess_iiop.ToolImpl.error
    : (Compiled Code)
    : at oracle.aurora.ejb.deployment.GenerateEjb.generateBean
    : (Compiled Code)
    : at oracle.aurora.ejb.deployment.GenerateEjb.invoke
    : (Compiled Code)
    : at oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke
    : (Compiled Code)
    : at
    : oracle.jdeveloper.wizard.deployment.EJBDeployMonitor.run
    : (Compiled Code)
    : at oracle.jdeveloper.wizard.common.ProgressDialog.run
    : (Compiled Code)
    : at java.lang.Thread.run(Compiled Code)
    null

  • Deploying existing application (forms and reports) over the web

    Hi I do have the following environment:
    1) Oracle 8.1.6.0.0 on HP-UX.
    2) Application written using oracle forms6i and reports6i on NT (Client-Server environment)
    I am looking to deploy this existing application over the web using 9iAS, sure I don't want to rewrite my application. I did that in the past using OAS 4.0.8 and forms server and reports server.
    1)Does 9iAS support that, which one should I install the standard or the enterprise.
    2)Do I still need forms server and reports server.
    I stopped using the OAS because it had problems and the performance was not that good, I found CITRIX and Tarantella do better, performance wise.
    3)Does 9iAS has improved that.
    Any feedback regading these many questions is highly appreciated
    Thanks
    Khaled

    Sounds like the ideal 9i As environment (although you might want to consider either upgrading or patching the database - 8.1.6.0.0 does have patches)
    You'd be pleasantly surprised with the performance and stability improvements of 9iAS over OAS.
    Deploying reports & forms over the web (pure web access, not terminal services like citrix) require some form of web server, reports server and forms server. I believe that 9i AS is totally compatible with the reports and forms developed in 6i tools, so there should be no rewrite at all.
    If you have the time, strongly recommend you check it out.

  • Deploying EJB application

    Hi,
    We are developing an Enterprise application, using JSP pages, Servlets and EJBs. All EJB development is handled by one developer and I do the web tier development (JSPs, Servlets and other required Java classes). We are using Oracle Container for J2EE (OC4J) and having problems accessing the EJBs from the web application if I deploy them separately. The question is - should we deploy the EJBs and Web application together? What is the best practice?
    Deploying together takes a lot of time, that is why I want to avoid it.
    I appreciate your help.
    Giri.

    The most accepted practice is to deploy it as an ear file. Unfortunately, the classloader standard does not make them like DLL's. That is, if the EJB changes, you have to update each application / ear file. It's dumb, but that's the way it is.
    Another method, which can be more simple depending on your environment is to include that ejb/jar within your war files (in the web-inf/lib) directory and deploy it on the server as an EJB. Again, all applications have to be updated if the ejb is changed.
    The only way I know of to avoid this is to put the EJB within your classpath. Then it doesn't need be included in all your projects nor installed as an EJB on your server. However, whenever it gets updated the server will have to be restarted.
    Hope this helps.
    ~hayedid

  • Weblogic.Deployer using -deploy for existing application

    I'm running on weblogic 8.1 SP3
    when I use -deploy for an existing application the documentation says it will do a redeploy.
    documentation for the targets option says that it will use existing targets for an application that is currently deployed.
    BUT it doesn't work. Is this a known issue ?
    I use the following options:
    -name fortune
    -source /data/bea81/applications/stg/fortune.ear
    -verbose -debug -deploy -stage

    Check to see if the problem is with the Deployer tool or myApp.war:
    1) Does myApp.war deploy using the console?
    2) Check myApp.war has all the classes it needs?
    If your app does deploy from the console then we can focus in on the Deploy tool. If not it may help give us a clue as to what is going on e.g. your war file missing classes.
    Hoos

  • Error in deploying EJB

    the following error is encountered although I have created the user escappuser
    in the default realm. Any help ?
    Unable to deploy EJB: D:\bea8\USER_P~1\domains\EVALGU~1\.\applications\.wlnotdel
    ete\wlap24823\inv_ejb.jar from inv_ejb.jar:
    weblogic.ejb20.WLDeploymentException: The run-as principal 'escappuser' for EJB
    'InvHistoryFtyPoDetailEJB' is not a user in the current realm. The user must exi
    st for the EJB to successfully deploy.
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.getRunAsPrincipal(MBe
    anDeploymentInfoImpl.java:1039)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeRunAsSettin
    gs(MBeanDeploymentInfoImpl.java:830)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymen
    tInfoImpl.java:244)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:267)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
    at weblogic.j2ee.Application.addComponent(Application.java:319)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:162)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:240)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:747)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:726)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:458)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
    ServerImpl.java:765)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
    ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
    s(SlaveDeployer.java:1245)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
    ava:397)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
    e(DeploymentManagerServerLifeCycleImpl.java:230)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    at weblogic.Server.main(Server.java:32)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:267)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
    at weblogic.j2ee.Application.addComponent(Application.java:319)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:162)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:240)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:747)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:726)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:458)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
    ServerImpl.java:765)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
    ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
    s(SlaveDeployer.java:1245)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
    ava:397)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
    e(DeploymentManagerServerLifeCycleImpl.java:230)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    at weblogic.Server.main(Server.java:32)
    >
    <Mar 9, 2004 10:05:42 AM GMT+08:00> <Info> <EJB> <BEA-010008> <EJB Deploying fil
    e: bcInterface_ejb.jar>
    <Mar 9, 2004 10:05:42 AM GMT+08:00> <Error> <J2EE> <BEA-160001> <Error deploying
    bcInterface_ejb:
    Unable to deploy EJB: D:\bea8\USER_P~1\domains\EVALGU~1\.\applications\.wlnotdel
    ete\wlap24823\bcInterface_ejb.jar from bcInterface_ejb.jar:
    weblogic.ejb20.WLDeploymentException: The run-as principal 'escappuser' for EJB
    'JobSchedulerMDB' is not a user in the current realm. The user must exist for
    th
    e EJB to successfully deploy.
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.getRunAsPrincipal(MBe
    anDeploymentInfoImpl.java:1039)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeRunAsSettin
    gs(MBeanDeploymentInfoImpl.java:830)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymen
    tInfoImpl.java:244)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:267)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
    at weblogic.j2ee.Application.addComponent(Application.java:319)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:162)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:240)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:747)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:726)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:458)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
    ServerImpl.java:765)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
    ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
    s(SlaveDeployer.java:1245)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
    ava:397)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
    e(DeploymentManagerServerLifeCycleImpl.java:230)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    at weblogic.Server.main(Server.java:32)
    Unable to deploy EJB: D:\bea8\USER_P~1\domains\EVALGU~1\.\applications\.wlnotdel
    ete\wlap24823\bcInterface_ejb.jar from bcInterface_ejb.jar:
    weblogic.ejb20.WLDeploymentException: The run-as principal 'escappuser' for EJB
    'JobSchedulerMDB' is not a user in the current realm. The user must exist for
    th
    e EJB to successfully deploy.
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.getRunAsPrincipal(MBe
    anDeploymentInfoImpl.java:1039)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeRunAsSettin
    gs(MBeanDeploymentInfoImpl.java:830)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymen
    tInfoImpl.java:244)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:267)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
    at weblogic.j2ee.Application.addComponent(Application.java:319)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:162)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:240)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:747)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:726)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:458)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
    ServerImpl.java:765)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
    ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
    s(SlaveDeployer.java:1245)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
    ava:397)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
    e(DeploymentManagerServerLifeCycleImpl.java:230)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    at weblogic.Server.main(Server.java:32)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:267)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
    at weblogic.j2ee.Application.addComponent(Application.java:319)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:162)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:240)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:747)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:726)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:458)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
    ServerImpl.java:765)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
    ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
    s(SlaveDeployer.java:1245)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
    ava:397)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
    e(DeploymentManagerServerLifeCycleImpl.java:230)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    at weblogic.Server.main(Server.java:32)

    There is a similar command to unix "chmod" under sess_sh, whereby you could do grant permission to the perticular user you act as. I did not encounter this issue since I always use SYS to do it, or as a normal user with JAVASYSPRIV hranted.

  • Problems deploying EJB on a oracle 8i server

    We are trying to deploy a EJB on a oracle 8i server. We crossposted this question in BI Beans forum also.
    For doing so we are using the following command:
    "deployejb -republish -temp temp -u sys -p sys -s sess_iiop://NLWS122:2481:
    LOKAAL -descriptor AQServerReceive.ejb AQServerReceive.jar"
    It seems that everything goes allright (we can trace the classes in the database) but we get this message:
    Reading Deployment Descriptor...done
    Verifying Deployment Descriptor...done
    Gathering users...done
    Generating Comm Stubs.............................................done
    Compiling Stubs...done
    Generating Jar File...done
    Loading EJB Jar file and Comm Stubs Jar file...Exception in thread "main" org.om
    g.CORBA.COMM_FAILURE: java.io.IOException: Peer disconnected socket minor code:
    0 completed: No
    at com.visigenic.vbroker.orb.TcpConnection.read(TcpConnection.java, Compiled Code)
    at com.visigenic.vbroker.orb.GiopConnectionImpl.receive_message(GiopConnectionImpl.java:436)
    at com.visigenic.vbroker.orb.GiopConnectionImpl.receive_reply(GiopConnectionImpl.java, Compiled Code)
    at com.visigenic.vbroker.orb.GiopStubDelegate.invoke(GiopStubDelegate.java:562)
    at com.visigenic.vbroker.orb.GiopStubDelegate.invoke(GiopStubDelegate.java:503)
    at com.inprise.vbroker.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:60)
    at oracle.aurora.AuroraServices._st_JISLoadJava.add(_st_JISLoadJava.java, Compiled Code)
    at oracle.aurora.server.tools.sess_iiop.Loadjava.add(Loadjava.java:137)
    at oracle.aurora.server.tools.sess_iiop.Loadjar.loadAndCreate(Loadjar.java, Compiled Code)
    at oracle.aurora.server.tools.sess_iiop.Loadjar.invoke(Loadjar.java, Compiled Code)
    at oracle.aurora.server.tools.sess_iiop.Loadjava.<init>(Loadjava.java, Compiled Code)
    at oracle.aurora.server.tools.sess_iiop.Loadjar.<init>(Loadjar.java:52)
    at oracle.aurora.ejb.deployment.GenerateEjb.invoke(GenerateEjb.java:560)
    at oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke(ToolImpl.java:143)
    at oracle.aurora.ejb.deployment.GenerateEjb.main(GenerateEjb.java:575)
    What could be the problem?
    More info:
    We are trying to get the example in the white paper 275199.pdf (Building Internet Applications with Oracle Forms 6i and Oracle8i) working.
    Thx for helping.

    Hi Ralph,
    I don't know if you are aware of this, but Oracle has replaced
    the database embedded EJB container (a.k.a. "aurora") with an
    external EJB container named OC4J (Oracle Containers for J2EE).
    OC4J is available in both stand-alone version and as part of Oracle's
    application server product: 9iAS. Although the database embedded
    EJB container still exists in the latest database versions (as
    far as I know), Oracle has -- for a long time, now -- been discouraging
    its use in favour of OC4J.
    More information on OC4J is available from:
    http://technet.oracle.com/tech/java/oc4j/content.html
    Good Luck,
    Avi.

  • Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:

    Hi,
    I installed the weblogic portal 10.3.2 and configured the domain to use oracle express edition 11g. After configuring the domain, i got the error saying the weblogic server could not start because of tables does not exist. so i changed the database.properties and executed the create_db.cmd to create the tables and the server is started now.
    when i tried to deploy the weblogic portal application, i got the following error,
    <Aug 10, 2010 12:35:57 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Aug 10, 2010 12:37:44 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1281424006937' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
    Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
    [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
    weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
    Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
    [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
         Truncated. see log file for complete stacktrace
    Caused By: [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:251)
         at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300)
         at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249)
         at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
         at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166)
         Truncated. see log file for complete stacktrace
    >
    <Aug 10, 2010 12:37:44 PM IST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'MyPortalEAR'.>
    <Aug 10, 2010 12:37:44 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'MyPortalEAR'.>
    <Aug 10, 2010 12:37:44 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
    Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
    [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
         Truncated. see log file for complete stacktrace
    Caused By: [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:251)
         at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300)
         at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249)
         at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
         at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166)
         Truncated. see log file for complete stacktrace
    >
    <Aug 10, 2010 12:37:56 PM IST> <Warning> <Deployer> <BEA-149252> <No deployment 'MyPortalEAR' found for Operation stop.>
    Please guide me to resolve this issue.
    Thanks a lot,
    Suresh
    Edited by: user5701346 on Aug 10, 2010 10:34 PM

    I changed target for DataSource from AdminServer to my managed Server. That solved the problem.

  • Error while deploying EJB 1.1 on Weblogic 10.3.0.0

    I am trying to deploy an EJB (1.1) jar which is succesfully running on JBoss5.0 on WebLogic 10.3.0.0; I am getting following Error while deploying the jar on weblogic;
    Exception preparing module: EJBModule(ejb_RemoteServicesEjb) Unable to deploy EJB: RemoteServicesEjb.jar from RemoteServicesEjb.jar: There are 1 nested errors: weblogic.ejb.container.compliance.ComplianceException: In EJB com.package.ejbimpl.RemoteServicesEjb, the throws clause for ejbCreate method ejbCreate() contains exceptions that are NOT in the throws clause of the corresponding home interface method. at weblogic.ejb.container.compliance.HomeInterfaceChecker.checkCreateMethodsMatchBeanCreates(HomeInterfaceChecker.java:365) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:337) at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:286) at weblogic.ejb.container.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:952) at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:920) at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:246) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:552) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:519) at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:393) at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:715) at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:618) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1154) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Does anybody knows what must be going wrong?
    Can't I deploy EJB 1.1 jar directly on Weblogic 10.3.0.0 or I need to change or configure something before doing it?

    Does the ejbCreate() method of the com.package.ejbimpl.RemoteServicesEjb class have an exception on it's throws clause that is not present on the ejbCreate() method of your home interface? If so, does the error go away if you add the exception to the home's ejbCreate() method? In general, you want checked exceptions in a throws clause to match between the interface declaration of the method and the implementation of the method on the bean class.
    - Matt

  • Error while deploying web service in Netweaver application

    Hi,
    In my group, two members working in the development of a WebDynpro based application.  We have created a track and are using the same for development. For our application
    the team member 1 created a Dc say DC1 for EJBS(both
    entity and session) and another DC say DC2 for the application archieve 'ear'
    and activated the two DCS. When another member of
    the team is trying to create a webservice in the checked out DC, the
    webservice was created successfully but while deploying the
    application archive DC it gives an error (details furnished below).
    Error:
    :Caught exception during application deployment from SAP J2EE Engine's
    deploy service:java.rmi.RemoteException: Cannot deploy
    application asianpaints.com/pe_mgt_ear.. Reason: Webservices common
    deployment exception! The reason is: Error occurred,
    trying to update web services for application
    asianpaints.com/pe_mgt_ear. . Additional info: none; nested exception
    is:
    java.lang.Exception:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
    exception! The reason is: Error occurred, trying to update web services
    for application asianpaints.com/pe_mgt_ear.
    WSDeploymentException: Webservices common deployment exception! The
    reason is: Error occurred, trying to parse documentation
    for web service NewPEProcessorService. .
    So we created one more DC3(referring the entity beans of DC1) and
    created the required session bean and webservice in that
    DC. It got deployed successfully. Again when we are trying to create
    new webservice it got created but the deployment got
    aborted with the same error as mentioned above:
    The detailed error description we got in both the cases is given below:
    Mar 30, 2006 1:07:39 PM /userOut/deploy
    (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy
    Thread,5,main]] INFO:
    [005]Additional log information about the deployment
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[/usr/sap/J2E/JC00/SDM/program/log/sdmcl20060330074205.log]/>
    <!PATTERN[sdmcl20060330074205.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[ISO8859_1]/>
    <!LOGHEADER[END]/>
    Mar 30, 2006 1:12:07 PM Info: -
    Starting deployment -
    Mar 30, 2006 1:12:07 PM Info: Loading selected archives...
    Mar 30, 2006 1:12:07 PM Info: Loading
    archive '/usr/sap/J2E/JC00/SDM/program/temp/temp35515asianpaints.com~pe_mgt_ear.ear'
    Mar 30, 2006 1:12:17 PM Info: Selected archives successfully loaded.
    Mar 30, 2006 1:12:17 PM Info: Actions per selected component:
    Mar 30, 2006 1:12:17 PM Info: Update: Selected development component
    'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420' updates
    currently deployed development component
    'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'8008'.
    Mar 30, 2006 1:12:17 PM Info: The deployment prerequisites finished
    without any errors. All items are correct.
    Mar 30, 2006 1:12:17 PM Info: Saved current Engine state.
    Mar 30, 2006 1:12:17 PM Info: Error handling strategy: OnErrorStop
    Mar 30, 2006 1:12:17 PM Info: Update strategy: UpdateAllVersions
    Mar 30, 2006 1:12:17 PM Info: Starting: Update: Selected development
    component
    'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420' updates
    currently deployed development component
    'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'8008'.
    Mar 30, 2006 1:12:17 PM Info: SDA to be deployed:
    /usr/sap/J2E/JC00/SDM/root/origin/asianpaints.com/pe_mgt_ear/J2E_HSSPNEW_D/20060330130420/temp35515asianpaints.com~pe_mgt_ear
    .ear
    Mar 30, 2006 1:12:17 PM Info: Software type of SDA: J2EE
    Mar 30, 2006 1:12:17 PM Info: ***** Begin of SAP J2EE Engine
    Deployment (J2EE Application) *****
    Mar 30, 2006 1:15:07 PM Info: Begin of log messages of the target
    system:
    06/03/30 13:12:17 -
    06/03/30 13:12:20 - Start updating EAR file...
    06/03/30 13:12:20 - start-up mode is lazy
    06/03/30 13:12:23 - EAR file updated successfully for 3161ms.
    06/03/30 13:12:23 - Start updating...
    06/03/30 13:12:24 - EAR file uploaded to server for 525ms.
    06/03/30 13:15:07 - ERROR: Not updated. Deploy Service returned ERROR:
    java.rmi.RemoteException: Cannot deploy
    application asianpaints.com/pe_mgt_ear..
    Reason: Webservices common deployment exception!
    The reason is: Error occurred, trying to update web
    services for application asianpaints.com/pe_mgt_ear. . Additional info:
    none; nested exception is:
    java.lang.Exception:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException:
    Webservices common deployment exception! The reason is: Error occurred,
    trying to update web services for application
    asianpaints.com/pe_mgt_ear. . Additional info: none
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
    at
    com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
    (WSDeployer.java:274)
    at
    com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
    at
    com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
    at
    com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
    at
    com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
    :290)
    at
    com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
    at
    com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
    at
    com.sap.engine.services.deploy.server.DeployServiceImpl.update
    (DeployServiceImpl.java:584)
    at
    com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch
    (DeployServiceImplp4_Skel.java:1278)
    at
    com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
    (DispatchImpl.java:294)
    at
    com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
    at
    com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
    (P4SessionProcessor.java:119)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
    tener.java:33)
    at
    com.sap.engine.core.cluster.impl6.session.MessageRunner.run
    (MessageRunner.java:41)
    at
    com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged
    (Native Method)
    at
    com.sap.engine.core.thread.impl3.SingleThread.execute
    (SingleThread.java:95)
    at
    com.sap.engine.core.thread.impl3.SingleThread.run
    (SingleThread.java:160) Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices
    deployment exception! The reason is: Error occurred, trying to generate
    web services deployment files for application
    asianpaints.com/pe_mgt_ear. . The error refers to application: none,
    jar: , web service: .
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
    ... 21 more
    Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
    deployment exception! The reason is: Error occurred, parsing
    com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
    asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
    message: type: jar file, location:
    /usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
    ar . . Additional info:
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
    ... 23 more
    Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
    deployment exception! The reason is: Error occurred, trying to parse
    documentation for web service NewPEProcessorService. .
    Additional info:
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
    60)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
    ... 26 more
    Caused by: java.lang.NullPointerException
    at
    com.sap.engine.services.deploy.server.DeployServiceImpl.update
    (DeployServiceImpl.java:596)
    at
    com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch
    (DeployServiceImplp4_Skel.java:1278)
    at
    com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
    (DispatchImpl.java:294)
    at
    com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
    at
    com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
    (P4SessionProcessor.java:119)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
    tener.java:33)
    at
    com.sap.engine.core.cluster.impl6.session.MessageRunner.run
    (MessageRunner.java:41)
    at
    com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged
    (Native Method)
    at
    com.sap.engine.core.thread.impl3.SingleThread.execute
    (SingleThread.java:95)
    at
    com.sap.engine.core.thread.impl3.SingleThread.run
    (SingleThread.java:160) Caused by:
    java.lang.Exception:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The
    reason is: Error occurred, trying to update web services for
    application asianpaints.com/pe_mgt_ear. . Additional info: none
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
    at
    com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
    (WSDeployer.java:274)
    at
    com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
    at
    com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
    at
    com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
    at
    com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
    :290)
    at
    com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
    at
    com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
    at
    com.sap.engine.services.deploy.server.DeployServiceImpl.update
    (DeployServiceImpl.java:584)
    at
    com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch
    (DeployServiceImplp4_Skel.java:1278)
    at
    com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
    (DispatchImpl.java:294)
    at
    com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
    at
    com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
    (P4SessionProcessor.java:119)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
    tener.java:33)
    at
    com.sap.engine.core.cluster.impl6.session.MessageRunner.run
    (MessageRunner.java:41)
    at
    com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged
    (Native Method)
    at
    com.sap.engine.core.thread.impl3.SingleThread.execute
    (SingleThread.java:95)
    at
    com.sap.engine.core.thread.impl3.SingleThread.run
    (SingleThread.java:160) Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices
    deployment exception! The reason is: Error occurred, trying to generate
    web services deployment files for application
    asianpaints.com/pe_mgt_ear. . The error refers to application: none,
    jar: , web service: .
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
    ... 21 more
    Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
    deployment exception! The reason is: Error occurred, parsing
    com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
    asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
    message: type: jar file, location:
    /usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
    ar . . Additional info:
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
    ... 23 more
    Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
    deployment exception! The reason is: Error occurred, trying to parse
    documentation for web service NewPEProcessorService. .
    Additional info:
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
    60)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
    ... 26 more
    Caused by: java.lang.NullPointerException
    at
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:64)
    at sun.reflect.NativeMethodAccessorImpl.invoke0
    (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
    (NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke
    (DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke
    (Method.java:324)
    at java.io.ObjectStreamClass.invokeWriteReplace
    (ObjectStreamClass.java:896)
    at java.io.ObjectOutputStream.writeObject0
    (ObjectOutputStream.java:1011)
    at java.io.ObjectOutputStream.defaultWriteFields
    (ObjectOutputStream.java:1332)
    at java.io.ObjectOutputStream.writeSerialData
    (ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject
    (ObjectOutputStream.java:1247)
    at java.io.ObjectOutputStream.writeObject0
    (ObjectOutputStream.java:1052)
    at java.io.ObjectOutputStream.writeObject
    (ObjectOutputStream.java:278)
    at
    com.sap.engine.services.rmi_p4.DispatchImpl.throwException
    (DispatchImpl.java:135)
    at
    com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
    (DispatchImpl.java:296)
    ... 8 more
    For detailed information see the log file of the
    Deploy Service.
    06/03/30 13:15:07 -
    Mar 30, 2006 1:15:07 PM Info: End of log messages of the target
    system.Mar 30, 2006 1:15:07 PM Info: ***** End of SAP J2EE Engine
    Deployment
    (J2EE Application) *****
    Mar 30, 2006 1:15:07 PM Error: Aborted: development component
    'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420':
    Caught exception during application deployment from SAP J2EE Engine's
    deploy service:
    java.rmi.RemoteException: Cannot deploy application
    asianpaints.com/pe_mgt_ear..
    Reason: Webservices common deployment exception! The reason is: Error
    occurred, trying to update web services for application
    asianpaints.com/pe_mgt_ear. . Additional info: none; nested exception
    is:
    java.lang.Exception:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
    deployment exception! The reason is: Error occurred, trying to update
    web services for application
    asianpaints.com/pe_mgt_ear. . Additional info: none
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
    at
    com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
    (WSDeployer.java:274)
    at
    com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
    at
    com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
    at
    com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
    at
    com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
    :290)
    at
    com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
    at
    com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
    at
    com.sap.engine.services.deploy.server.DeployServiceImpl.update
    (DeployServiceImpl.java:584)
    at
    com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch
    (DeployServiceImplp4_Skel.java:1278)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
    (DispatchImpl.java:294)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run
    (DispatchImpl.java:183)
    at
    com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
    (P4SessionProcessor.java:119)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
    tener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run
    (MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run
    (ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute
    (SingleThread.java:95)
    at com.sap.engine.core.thread.impl3.SingleThread.run
    (SingleThread.java:160)
    Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices deployment exception! The
    reason is: Error occurred, trying to generate web services deployment
    files for application asianpaints.com/pe_mgt_ear. . The
    error refers to application: none, jar: , web service: .
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
    ... 21 more
    Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
    exception! The reason is: Error occurred, parsing
    com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
    asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
    message: type: jar file, location:
    /usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
    ar . . Additional info:
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
    at
    com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
    ... 23 more
    Caused by:
    com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
    exception! The reason is: Error occurred, trying to parse documentation
    for web service NewPEProcessorService. . Additional
    info:
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
    60)
    at
    com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
    ... 26 more
    Caused by: java.lang.NullPointerException
    (message ID:
    com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Mar 30, 2006 1:15:17 PM Info: J2EE Engine is in same state
    (online/offline) as it has been before this deployment process.
    Mar 30, 2006 1:15:17 PM Error: -
    At least one of the Deployments
    failed -
    Deployment failure happens only when the DC contains a web service; else, it goes through properly. 
    Can anyone of you indicate where we are going wrong and what should be done to resolve this issue?
    Thanks a lot in advance.
    Regards,
    Ravi

    Hi,
    You can go to the Visual Administrator -> <SID> -> Server -> Services -> Deploy -> Runtime tab -> option Container at the bottom and see if everything is correct and running in the webservices_container.
    If something necessary to the deployment is not started you can select it and click in start.
    I hope it helps.
    Thanks,
    Anderson

  • Deployment of an Adobe AIR application in an enterprise environment

    Dear Team members,
    first of all my apologies for posting this thread in more than one forum (see Installations Issues) but the argument is very important to us and I don't know where discuss it.
    I would like to post a question to you regarding deployment doubts that we are trying to address.
    My company is working on the new version of our primary application previously built as a J2EE application with some reporting functions with Flex, and we want to use AIR in order to leverage its possibilities:
    Seamless integration with existing application functionalities (implemented as standard JEE web application pages) thanks to the integrated HTML capabilities
    Improved integration of the user interface with the desktop
    Native processes to provide additional functionalities
    Our application is targeted to pharmaceutical industry, subject to FDA regulations, and it affects more than 5000 users for each customer, so we have some specific requirements affecting the deployment and distribution of the software:
    Allow to run multiple versions of the software on the same client machine (to support test and acceptance activities in addition to the production environment)
    Minimize the effort of the initial setup on each client
    Manage the version upgrades without manual activities on each client
    Keep the test/acceptance and production environments strictly aligned to improve effectiveness of formal validation (ideally, an application once validated should be transported in production without any source code modification, recompilation or repackaging)
    The current browser-based strategy is perfectly fit to these requirements, and in the shift towards a desktop-based strategy we need to continue satisfying them as much as possible. We evaluated the standard distribution strategy of Adobe AIR applications, and noticed several attention points in this scenario.
    The first issue we encountered is the back-end services endpoint discovery problem. Simply hardcoding a server URL in the packaged application could be a viable solution for public internet-accessible applications, but we need to support multiple customers in their intranet, and each one typically requires multiple environments for the application (acceptance, production, etc.). Maintaining dozens of different packages of the AIR application to support all these customer environments clearly is not the solution. Neither we want to force thousands of different users to enter and maintain the correct server location in their local preferences.
    So, we thought to use a badge hosted in the back-end application to run the local AIR application: using the underlying API, we could activate the application specifying also the network location of the back-end services. We could also rely on the badge to install the application (and the AIR runtime if necessary)… however, application packaged as native installers cannot be installed, upgraded, or launched by the badge API (and we need to package ours as native to use native processes).
    We also noticed that multiple versions of an AIR application cannot be installed side-by-side in a client machine, and that the installation and upgrade of the application can be performed only when the local user has administrative rights on the machine (using standard or native packages), forcing us to rely on external software distribution systems in some customer scenarios (introducing additional complexities in the release cycle).
    At this point, in our opinion the standard deployment strategies of Adobe AIR applications are unfit for enterprise environments. In the enterprise world, many of the applications have migrated to a completely browser-based solution, while others enhanced their client layer to comply with the requirements, for example installing only a thin portion of the client code and allowing to connect to multiple server versions/environments with it (e.g. the SAP GUI universal client). Without smarter deployment and distribution tools, AIR applications currently are a step back compared to web applications in terms of manageability.
    So, we are trying to develop a solution to address these problems, with some concepts similar to JStart: install on the client machine a launcher application capable of being activated from a web page, dynamically locate, download and run the actual client bytecode, transparently enforce client software updates, and supporting multiple applications (and multiple versions of the same application). However, we are facing many technical problems due to internal architecture of AIR and we already spent a considerable amount of effort trying to find a solution. We are now thinking to return on the choice of AIR, going back to Flex.
    What is the position of Adobe on this argument? Is Adobe aware of these issues and are there any plans on this topic? Any advice?
    Thank you in advance

    For those following along, Oliver Goldman will be answering this post in future articles on his blog.
    Many great comments and questions here. I’m working on some follow-up posts to address these; nothing I could cram into this comment field would really do your query justice. - Oliver Goldman
    Pursuit of Simplicity
    Chris

Maybe you are looking for