Deploying simple EAR to WL10.3 in Production Mode

Hi,
I'm trying to deploy a simple EAR developed using Workshop and am getting library reference errors for beehive-controls-1.0.1-10.0.
The target server is running on Solaris with a domain created using the wls.jar template.
I'd like to bundle the additional libraries needed in the EAR file (in APP-INF/lib, dropped in automagically using the workshop J2EE module dependencies setting) but don't know which libraries I need (can only find beehive-controls.jar on the filesystem).
Will this work on a server running in production mode, and if so, what libraries do i need?
Cheers.
Martin.
Edited by: user10925870 on 23-Nov-2009 03:19
The library references that wls complains about are:
- beehive-controls-1.0.1-10.0
- weblogic-controls-10.0
- wls-commonsloggingbridge

You can do one thing. Create a workshop domain in a test environment and then start the console. All the shared libraries are deployed as modules and can be seen in the admin console. Then search and place theses libraries in the lib of your application and used the <prefer-web-inf-classes> or <prefer-application-packages> in case of .war or .ear respectively. Hope this helps :)
Edited by: Manish Chellappan on Nov 24, 2009 1:05 PM

Similar Messages

  • Deploy applications thru autodeploy in production mode in Weblogic 10

    In Weblogic 10, we can deploy applications though autodeploy in development mode. But now I need to deploy my applications in production mode. Iam very much convenient using autodeploy. Can I use this autodeploy in production mode..?..Any alternative..?
    Will there be any problems If I deploy things thru autodeploy in production mode..?
    Please help..
    Thanks.

    Kumar_Spore <> wrote:
    In Weblogic 10, we can deploy applications though autodeploy in
    development mode. But now I need to deploy my applications in production
    mode. Iam very much convenient using autodeploy. Can I use this autodeploy
    in production mode..?..Any alternative..? Will there be any problems If I
    deploy things thru autodeploy in production mode..? Please help.. Thanks.Hi,
    As far as I know, the autodeploy will not work as soon as your weblogic
    instance is in production mode.
    And this mostly for 'security' reasons.
    Imagine that you have an application running in production, you don't want
    to deploy something 'unplanned' or allow mistakes by administrators. And
    with autodeploy you can easily copy something wrong.
    B
    Schelstraete Bart
    [email protected]
    http://www.schelstraete.org

  • Web service does not work in production mode

    Hi!
    I created a small web service with the WorkShop in BEA Weblogiv 7.0.
    If I start the server in production mode, then my service is not visible. It can
    not be accessed, neither its WSDL. In development mode it works. I tried to create
    an EAR file and deploy it, but when I do that in the web console, it all says
    that it is deployed, but I can not access the WSDL or anything else.
    Does the WSDL URL change in production mode ?
    Help !
    Best regards,
    David

    Thanks for reply.
    It seems nothing matters.
    I changed wlw-config file:
         <hostname>localhost</hostname>
         <protocol>http</protocol>
         <http-port>8002</http-port>
         <service>
              <class-name>com.mycom.MyWS</class-name>
              <protocol>http</protocol>
         </service>
    I changed wsdl soap address
    to
    http://localhost:8002/MyWS/com/mycom/MyWS.jws
    I deployed it to managed server at port 8002 and admin server at 7001. but still, admin server works and the other one does not.

  • Error While Deploying the Ear .

    HI ,
    I am getting an error while deploying my ear through Deploy Tool . the ear get loaded but fails to deploy... the error message i got is pasted below...
    It gives error about EJBContainer, but the J2EE Engine's Visual Admin shows the service is runing
    Any help is highly appreaciated
    Eror Message.....
    06/05/13 18:49:09 -  ***********************************************************
    06/05/13 18:49:10 -  Start updating EAR file...
    06/05/13 18:49:10 -  start-up mode is lazy
    06/05/13 18:49:12 -  EAR file updated successfully for 2078ms.
    06/05/13 18:49:12 -  Start deploying ...
    06/05/13 18:49:14 -  EAR file uploaded to server for 1172ms.
    06/05/13 18:49:16 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/omnidocs_ejb..
                         Reason: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.; nested exception is:
                              com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.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:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3139)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
                              ... 10 more
                         Caused by: java.lang.NoClassDefFoundError: com/newgen/omni/jts/txn/NGOServerInterface
    Loader Info -
                         ClassLoader name: [Deployment:Runtime:sap.com/omnidocs_ejb]
                          Parent loader name: [Frame ClassLoader]
                          References:
                            common:service:http;service:servlet_jsp
                            service:ejb
                            common:service:iiop;service:naming;service:p4;service:ts
                            service:jmsconnector
                            library:jsse
                            library:servlet
                            common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
                            library:ejb20
                            library:j2eeca
                            library:jms
                            library:opensql
                            common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
                            interface:resourcecontext_api
                            interface:webservices
                            interface:cross
                            interface:ejbserialization
                          Resources:
                            C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\deploy\1147526354539
                            C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\deploy\1147526354539\omnidocs_ejb.jar
                          Loading model: {parent,references,local}
                         The error occurred while trying to load "com.newgen.omni.jts.txn.oracle.docdb.NGOConnectCabinet".
                              at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
                              at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
                              at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:253)
                              at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                              ... 16 more
                         For detailed information see the log file of the Deploy Service.
    06/05/13 18:49:16 -  ***********************************************************
    <b></b>

    Hi
    I would suggest you to do the deployment of the EAR using NWDS rather that using deploy tool. for Doing this please follow this link for creating ,building and deplopying as ear using dev studio
    http://help.sap.com/saphelp_nw04/helpdata/en/08/51ec41b9a24f4a8359c61ae4a02db1/frameset.htm
    Anyways if you ar still tied up using deploy tool pleas cross verify that all the dependent jars (including jars which  NgoServerinterface will beusing internally has to be in the classpath . Would be great if you can post the stack trace
    hope this helps !<b>  please mark points for helpful answers .</b>
    regards
    rajeshkr

  • Warning in Deployment of EAR in AS Java Server

    Hi,
    I am getting below exception while deploying a particular EAR.
    Description:
              1. Warning exception has been returned while the [cnfg_fed_ear] was starting. Warnings:[
    Warning occurred on server 3226150 during startApp of cnfg_fed_ear : Cannot load servlet. Error is: java.lang.IllegalArgumentException: there is no message configured for the property key: log appenders
    Result
    Status:Warning
    Following this exception, the depending EAR r facing exception.
    What is the probable reason

    Hi,
    NW app server, verifies the web application(EAR/WAR...) during deployment.
    The warning you are getting is due to error in your web application. please check [here|http://docs.oracle.com/javaee/1.4/api/javax/jms/Message.html]
    if you still have some doubt about NW itself, try deploying simple Hello world web app see if you still facing the issue.
    Good luck,
    Idan

  • Not Loaded status after deploying a EAR file in Oracle 10g application serv

    Hi,
    I am deployed a simple ear file in Oracle App Server 10g. The deployment went on well. But when i use the enterprise manager to see the status , it shows 'Not Loaded'.
    Can any body kindly give me a suggestion on why this is happening.
    Any help is highly appreciated.
    Thanks
    SK

    Hi,
    You have to register your Portlet provider.
    How to register new portlet in Oracle Portal 10g ?
    Here are the steps -
    1- Go to your oracle portal home page e.g. http://oracleportal.com/pls/portal
    2- Login into the oracle portal by clicking on 'login' link
    3- Go to the Builder and then Administer
    4- Click on Portlets tab
    5- Click on 'Register a Provider' in 'Remote Providers' portlet.
    6- Enter the provider URL and other information and click finish. Normally the provider URL for portlets developed using JPDK is in the form of http://[your portal]/[context root]/providers/
    Please note that you must have deployed the portlet before trying to register the provider for the portlet.
    Best Regards,
    Kevin

  • Deploy the .ear file in Oracle 10g Application server10.1.3

    Hi Friends,
    I have deploy the .ear file in Oracle10g Application Sever 10.1.3 through Enterprise Manager. in Progress Messages shows the application has been successfully deployed,like this
    when i hit the URL in Web brower, i got a HTTP 403 showing.............
    Plz help me ..............
    Sep 27, 2008 12:11:41 PM] Application Deployer for BO13 STARTS.
    [Sep 27, 2008 12:11:41 PM] Copy the archive to C:\product\10.1.3\OracleAS_1\j2ee\BO13Dev\applications\BO13.ear
    [Sep 27, 2008 12:11:42 PM] Initialize C:\product\10.1.3\OracleAS_1\j2ee\BO13Dev\applications\BO13.ear begins...
    [Sep 27, 2008 12:11:42 PM] Unpacking BO13.ear
    [Sep 27, 2008 12:11:49 PM] Done unpacking BO13.ear
    [Sep 27, 2008 12:11:49 PM] Unpacking backoffice.war
    [Sep 27, 2008 12:11:53 PM] Done unpacking backoffice.war
    [Sep 27, 2008 12:11:53 PM] Unpacking backoffice-help.war
    [Sep 27, 2008 12:11:57 PM] Done unpacking backoffice-help.war
    [Sep 27, 2008 12:11:57 PM] Unpacking resourceadapter-rar.rar
    [Sep 27, 2008 12:11:57 PM] Done unpacking resourceadapter-rar.rar
    [Sep 27, 2008 12:11:58 PM] Initialize C:\product\10.1.3\OracleAS_1\j2ee\BO13Dev\applications\BO13.ear ends...
    [Sep 27, 2008 12:11:58 PM] Starting application : BO13
    [Sep 27, 2008 12:11:58 PM] Initializing ClassLoader(s)
    [Sep 27, 2008 12:11:58 PM] Initializing EJB container
    [Sep 27, 2008 12:11:58 PM] Loading connector(s)
    [Sep 27, 2008 12:11:59 PM] Starting up resource adapters
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: shared-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: store-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: storeops-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: parameter-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: report-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: scheduler-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: workflow-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: item-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: employee-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: employee-webapp-app-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: journal-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: label-webapp-app-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: label-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: timemaintenance-ejb.jar
    [Sep 27, 2008 12:11:59 PM] Processing EJB module: timemaintenance-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: party-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: transaction-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: customer-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: calendar-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: currency-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: financial-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: till-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: tax-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: postprocessor-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: codelist-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: pricing-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: trigger-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: report-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: parameter-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: item-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: store-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: admin-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: dashboard-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: storeops-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: pricing-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: task-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: storeserver-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:00 PM] Processing EJB module: transaction-webapp-app-ejb.jar
    [Sep 27, 2008 12:12:11 PM] Compiling EJB generated code
    [Sep 27, 2008 12:12:58 PM] Initializing EJB sessions
    [Sep 27, 2008 12:12:58 PM] Committing ClassLoader(s)
    [Sep 27, 2008 12:12:58 PM] Initialize backoffice begins...
    [Sep 27, 2008 12:12:58 PM] Initialize backoffice ends...
    [Sep 27, 2008 12:12:58 PM] Initialize backoffice-help begins...
    [Sep 27, 2008 12:12:58 PM] Initialize backoffice-help ends...
    [Sep 27, 2008 12:12:58 PM] Started application : BO13
    [Sep 27, 2008 12:12:58 PM] Binding web application(s) to site default-web-site begins...
    [Sep 27, 2008 12:12:58 PM] Binding backoffice web-module for application BO13 to site default-web-site under context root backoffice13dev
    [Sep 27, 2008 12:13:01 PM] Initializing Servlet: org.springframework.web.context.ContextLoaderServlet for web application backoffice
    [Sep 27, 2008 12:13:01 PM] Initializing Servlet: org.quartz.ee.servlet.QuartzInitializerServlet for web application backoffice
    [Sep 27, 2008 12:13:01 PM] Initializing Servlet: org.apache.struts.action.ActionServlet for web application backoffice
    [Sep 27, 2008 12:13:05 PM] Binding backoffice-help web-module for application BO13 to site default-web-site under context root backoffice-help
    [Sep 27, 2008 12:13:05 PM] Initializing Servlet: oracle.help.web.OHWController for web application backoffice-help
    [Sep 27, 2008 12:13:06 PM] Initializing Servlet: oracle.cabo.servlet.UIXServlet for web application backoffice-help
    [Sep 27, 2008 12:13:06 PM] Binding web application(s) to site default-web-site ends...
    [Sep 27, 2008 12:13:06 PM] Application Deployer for BO13 COMPLETES. Operation time: 85020 msecs
    Thanks
    Hari

    Can you tell me what's the status of components (value of "In sync" column) when you run "dcmctl getState" command?
    Thanks
    Shail

  • Start Weblogic 10.3.5 in production mode

    I am doing a Weblogic upgrade from 9.1 to 10.3.5.
    I am also simultaneously doing a Java upgrade to 1.6.0_27.
    All changes are done and the project is in in System test mode.
    I have configured my Sysytem test environment in development mode and used JDk installed on my computer.
    To move the changes to the UAT server, I want to start weblogic in production mode.
    can anyone help me as to how will this be different,I am planning thing for UAT and production right now.
    Can I run my System test server in production mode .
    Is it that with production mode ,we have to use jrockit and not Sun Jdk?
    Please help.
    Thanks,

    Hi
    When you started the Weblogic Server, in the starup window (or nohup output file) search for the word named like "Development". When I started my AdminServer and in the output from startup window, I could see a line like this: and in the end it says like AdminServer started in Development mode. On your side search for the word like "Production" or just "WLS Start Mode".
    WLS Start Mode=Development
    There should be a way to find out from Weblogic Admin Console, but I am not aware of this.
    Coming to redirecting the log file(s). do you want to redirect the startup log file(s) like when you start weblogic, you want all the outputs to go to someother file. Or is it the full log files from each server which are under like domain/servers/AdminServer/logs folder. I guess from weblogic console you should be able to control this.
    Coming to redirecting startup log files on Linux, under the domain root folder I created a simple file like admin_start.sh with below contents. And I run this admin_start.sh instead of startWeblogic.sh command. This takes care of starting weblogic and all output goes to specific file I mentioned. Also I can kill this window and still weblogic will be starting:
    DOMAIN_HOME="/home/ravijegga/Oracle/Middleware115/user_projects/domains/myDomain1"
    LOG_FILE="/home/ravijegga/Oracle/Middleware115/user_projects/domains/myDomain1/logs/admin.log"
    nohup ${DOMAIN_HOME}/bin/startWebLogic.sh > ${LOG_FILE} &
    The point is if you use > you can redirect to any log file. Google around and you should be able to find more examples for Windows OS also.
    Thanks
    Ravi Jegga

  • Wls 9.1 doesn't pick up changes to static content in production mode

    Hi Everybody,
              I'm running wls 9.1 on XP in production mode as a stand-alone server. My web app is deployed in exploded format in an external directory.
              I'm trying to force the server to pick up the changes to static content like JSPs automatically and it's not working.
              1. I've set pageCheckSeconds = 1 in weblogic.xml and even though server picks this setting up it does nothing about it.
              2. I tried weblogic.Deployer utitlity to redeploy just one jsp file and it's not working because it's unable to get the full path to a source file. Can this happen due to application Context Path not being set properly?
              Does anybody come across issues like this?
              Thanks.
              Paul.

    Hi Everybody,
              I'm running wls 9.1 on XP in production mode as a stand-alone server. My web app is deployed in exploded format in an external directory.
              I'm trying to force the server to pick up the changes to static content like JSPs automatically and it's not working.
              1. I've set pageCheckSeconds = 1 in weblogic.xml and even though server picks this setting up it does nothing about it.
              2. I tried weblogic.Deployer utitlity to redeploy just one jsp file and it's not working because it's unable to get the full path to a source file. Can this happen due to application Context Path not being set properly?
              Does anybody come across issues like this?
              Thanks.
              Paul.

  • Production mode startup failure for 8.1SP2

    I'm running BEA WL 8.1 on Windows 2000 and have created a new server configuration
    in production mode with JRocket using the Configuration Wizard through Express
    Setup. I am unable to successfully start the server manually or through the Workshop
    interface. Below is the exception stack trace. Any suggestions would be most appreciated.
    <> <000000> <Error in startup class com.bea.wli.init.WLIDBCreate Method: init:
    com.bea.wli.init.WLIDBCreateException: At least one WLI data base object (TABLE
    WLI_USER) was missing
         at com.bea.wli.init.WLIDBCreate$WLIDataSource.checkDBObjects(WLIDBCreate.java:875)
         at com.bea.wli.init.WLIDBCreate.init(WLIDBCreate.java:994)
         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 com.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:324)
         at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:189)
         at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
         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 weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.java:229)
         at weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.java:160)
         at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.java:36)
         at weblogic.t3.srvr.StartupClassService$1.run(StartupClassService.java:121)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.t3.srvr.StartupClassService.invokeStartupClass(StartupClassService.java:116)
         at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:88)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(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(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         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)

    Thanks, I fixed the problem following the steps you outlined.
    All that was needed was to create a database named Workshop, and then execute the scripts as explained.
    For the benefit of others here is what I followed before going by your suggestion:
    1. Go to: weblogic81\common\eval\pointbase\tools
    2. Start pointbase by executing: startPointBase.cmd
    (edit this file if it should run on any specific port that you require e.g 9093)
    3. Under the same directory, execute: startPointBaseConsole.cmd so that the pointbase console comes up.
    4.Click on the radio button: Create new database
    5. In the dialog box, specify URL as:
    jdbc:pointbase:server://localhost:9093/workshop
    (I used port 9093 on localhost)
    6. specify username and password
    7. Click OK.
    Now follow the steps on the links below:
    http://forums.bea.com/bea/thread.jspa?messageID=202437477&tstart=0
    or
    http://www.webservertalk.com/message148326.html
    Also, it does not matter whether you start the server in prod. mode or dev mode as this DB lookup is before you specify dev mode or prod. mode startup while creating the domain (when you test connection through config. wizard while creating the domain). I created the domain in custom mode and not in express mode to have greater visibility of what I am configuring (On Windows env.).
    Rommel Sharma.

  • Problem deploying simple WS

    I'm trying to create a simple Web Service and get a problem at deployment stage.
    Firstly I create a simple Java class in the Java perspective.
    public class HelloNige {
         public String hello (String name) {
              return "Hello " + name;
    I then go to the Web service perspective and right click on the project to create a Web service Deployment Descriptor.
    I then right click on the project to build the EAR file.
    I then try to deploy the EAR file which is when I get the following error:
    4/09/2006 08:45:52 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager)
    [Thread[Deploy Thread,5,main]] ERROR:
    [005]Deployment aborted
    Settings
    SDM host : ausyd-8rvgc1s
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME~1/smithnp/LOCALS~1/Temp/temp19039EasyTestWS.ear
    Result
    => deployment aborted :
    file:/C:/DOCUME~1/smithnp/LOCALS~1/Temp/temp19039EasyTestWS.ear
    Aborted: development component 'EasyTestWS'/'sap.com'/'localhost'/'2006.09.04.08.45.45':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException:
    Error occurred while deploying ear file ./temp/deploy/work/deploying/EasyTestWS.ear.
    Reason: None of the available containers recognized the components
    of application sap.com/EasyTestWS;
    it is not possible to make deploy.
    (message ID:
    com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.
    performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    What am I doing wrong?
    Thanks in advance,
    nigel

    I might be wrong here, but I don't think that's enough to create a web service. Maybe the link below migh be of osme help. Do a search in the forums and sdn for more information.
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/d6/f9bc3d52f39d33e10000000a11405a/frameset.htm">SAP help</a>
    regards,
    Dion

  • SP2 Weblogic Integration Template Production Mode Failure

    I was surprised that in SP2, this simple failure is still not fixed:
    Launch configuration wizard.
    Choose Integration Template
    Choose Express Configuration
    Choose Production Mode
    Launch new domain
    You'll see the startup fails because the WLI tables are missing. This
    was broken in every release so far, and is pretty sad since it's one of
    the most basic things you can do with WL.

    Figured it out. When you try to create a new domain, it must be created in development mode (even if you want to run it in production mode). Start it at least once in development mode before trying to start it in production mode. To change whether the server starts in development or production - edit the setDomainEnv.sh file (in the same directory as config.xml). Towards the bottom of the file, there is an if condition that looks like this:
    if ("" = "true"){
    change it to
    if ("true" = "true) {
    then your server will start in production mode.

  • Deployment of ear file - invalid file

    Hi,
    i'm trying to deploy an ear file using the ANT wldeploy tasks.
    The file contains
    - ejb (separate jar for the client interfaces)
    - jpa persistence
    - webapp.
    The app server is 10.3.3
    I can deploy the ear via eclipse with no problems on my local server.
    When i try and publish/deploy on a remote server i get an error [Caused by: weblogic.deployment.EnvironmentException: duplicate persistence units with name . . .]
    Hence the attept to depoy via ant. This method fails even on my local server. Saying the (ear) file is invalid.
    It seems that the 'publish' action in eclipse performs modifications on the ear that the simple file->export->ear in eclipse doesnt do.
    I then tried to package the the environment in the split directory structure (up until then i just used the standard eclipse setup - multiple java/j2ee projects).
    That attempt failed at the wlappc stage. ArrayIndexOutofRange exception.
    Any ideas ?
    thanks,
    Michael

    Hi Steve,
    i've attached the stacktrace below.
    It seems to me that the ear file is either unpacked incorrectly (ending up with two persistence xml files) or eclipse isn't packageing them the 'weblogic way'.
    I found the cause of the ArrayIndexArrayOutofBounds exception when packageing with the wlappc task in the split directory setup: the references to the ejb and web modules in the application.xml have .jar/.war suffixes:
    <module>
    <ejb>ejbapp.jar</ejb>
    removing these and the ear builds fine with wlcompile/wlappc. So i can package the ear using wlcompile/wlappc and deploy the ear manually via the admin console. unfortunately i still have to remove the suffixes. working on an xslt script to fix the suffixes.... :-)
    cheers,
    Michael
    Remote deployment error from eclipse:
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
         at oracle.eclipse.tools.weblogic.server.internal.DeploymentProgressListener.watch(DeploymentProgressListener.java:190)
         at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:466)
         at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1420)
         at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:861)
         at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:655)
         at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:522)
         at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775)
         at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2889)
         at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    Caused by: weblogic.management.DeploymentException:
         at weblogic.application.internal.flow.ParseJpaDescriptorFlow.prepare(ParseJpaDescriptorFlow.java:44)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.deployment.EnvironmentException: duplicate persistence units with name myapp_persistence in scope myapp. First PU location: file:/var/opt/oracle/middleware/user_projects/domains/ecm_domain/servers/AdminServer/tmp/_WL_user/myapp/upzgei/lib/myapp_persistence.jar. Second PU location: file:/var/opt/oracle/middleware/user_projects/domains/ecm_domain/servers/AdminServer/tmp/_WL_user/myapp/upzgei/APP-INF/lib/myapp_persistence.jar
         at weblogic.deployment.AbstractPersistenceUnitRegistry.assertNoDuplicate(AbstractPersistenceUnitRegistry.java:313)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.processDescriptor(AbstractPersistenceUnitRegistry.java:291)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:192)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptors(AbstractPersistenceUnitRegistry.java:101)
         at weblogic.deployment.EarPersistenceUnitRegistry.<init>(EarPersistenceUnitRegistry.java:55)
         at weblogic.application.internal.flow.ParseJpaDescriptorFlow.prepare(ParseJpaDescriptorFlow.java:39)

  • Deploy given EAR file having application.xml and change context-root

    hi
    Please consider deploying a given EAR file on WebLogic Server 10.3.5 (part of JDeveloper 11.1.1.6.0) and changing the context-root for its web-module.
    For example an EAR file with only a web-module (ReviewContextRootFirstApp.ear [1]) or an EAR file with a web-module and an ejb-module (ReviewContextRootSecondApp.ear [2]).
    Given documentation appendix B section "context-root" [3] saying
    "... A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml. ..."
    and documentation section "Typical Deployment Configuration Workflows" [4] saying
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file. "
    Some observed behaviour:
    - scenario (sc1) : deploy ReviewContextRootFirstApp.ear without deployment plan, results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc2) : deploy ReviewContextRootFirstApp.ear with deployment plan fa-plan.xml (tries to configure "/rcrfaweb11"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc3) : deploy ReviewContextRootSecondApp.ear without deployment plan, results in context-root "/rcrsaweb" (as in application.xml)
    - scenario (sc4) : deploy ReviewContextRootSecondApp.ear with deployment plan sa-plan.xml (tries to configure "/rcrsaweb21"), results in context-root "/rcrsaweb" (as in application.xml)
    The blog post "Defining the context root of a web application in Oracle WebLogic server" [5] by Silviu Leahu in its section "Defining the context root in deployment plan" suggests to
    "Remove the META-INF/application.xml DD from the EAR"
    - scenario (sc5) : remove application.xml from ReviewContextRootFirstApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan fa-plan.xml, results in context-root "/rcrfaweb11" (as in fa-plan.xml)
    - scenario (sc6) : remove application.xml from ReviewContextRootSecondApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan sa-plan.xml, results in context-root "/rcrsaweb21" (as in sa-plan.xml)
    One could expect that using a deployment plan (like in scenario's (sc2) and (sc4)) would allow to configure/change the context-root, whithout having to make changes to the EAR file to make this possible. (Somewhat like "Figure 4-2 Single Deployment Plan Workflow")
    Only in scenario's (sc5) and (sc6) I see something close to what I would like to achieve, but there the application.xml file has been removed from the EAR file.
    So ...
    - (q1) Is it impossible to change the context-root at deploy-time for a web-module in a given EAR file that includes an application.xml file, without changing the EAR file?
    - (q2) Is working with EAR files that don't have an application.xml file a supported approach (to change the context-root at deploy-time)?
    Seems like a simple goal, but I must be missing something that is required to achieve it.
    - [1] ReviewContextRootFirstApp/deploy/ReviewContextRootFirstApp.ear in the ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [2] ReviewContextRootSecondApp/deploy/ReviewContextRootSecondApp.ear in the (same) ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [3] http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#WBAPP623
    - [4] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [5] http://blog.leahu.net/it/2011/01/04/defining-the-context-root-of-a-web-application-in-oracle-weblogic-server/
    many thanks
    Jan Vervecken

    Thanks for your reply René van Wijk.
    René van Wijk wrote:
    You can use deployment plans in order to change the context-root ...That is what I tried and describe in scenario's (sc2), (sc4), (sc5) and (sc6) in this forum thread.
    Because the application.xml file (in the "given EAR file"), added by JDeveloper 11.1.1.6.0 when deploying to an EAR file, doesn't have id attributes on its application/module elements, I first tried a different XPath expression:
    "/application/module/web[web-uri/text()="WebProject.war"]/context-root"
    But, that didn't work.
    Although the "given EAR file" does not have the suggested id attributes, I tried adding a deployment descriptor application.xml file that does have such id attributes [2], allowing an XPath expression like the one suggested:
    "/application/module[id="WebProject"]/web/context-root"
    - scenario (sc7) : deploy ReviewContextRootFirstApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan fa-plan-application-xml-with-id.xml (tries to configure "/rcrfaweb14"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc8) : deploy ReviewContextRootSecondApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan sa-plan-application-xml-with-id.xml (tries to configure "/rcrsaweb24"), results in context-root "/rcrsaweb" (as in application.xml)
    So, it does not seem to work.
    ... you have to use a variable assignment in the right part of the deployment plan (in this case the application.xml) ...My observations I describe above (that it does not seem to work) seem to confirm the Oracle documentation [1] I referred to in this forum thread before:
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. ... "
    ... By using an xpath expression, you can define which part of the xml has to be changed. ...The values for the deployment-plan xpath elements seem to be "peculiar".
    Although it should not be a problem in an XPath expression, using single quotes (like module[id='WebProject'] ) instead of double quotes (like module[id="WebProject"] ) results in:
    "java.lang.AssertionError: Attributes must be defined as name value pairs, eg, name="value" -- [id='WebProject']"
    Because an XPath predicate expression would use an "@" to refer to an attribute, I also tried to replace what you suggested module[id="Web"] with something like module[@id="Web"] but that also did not make a difference.
    - [1] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [2] http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.02.zip
    regards
    Jan Vervecken

  • Weblogic admin console always loads in production mode

    We recently upgraded from Weblogic 12.1.1 to 12.1.3.  Up until then we've used the <internal-apps-deploy-on-demand-enabled>true</internal-apps-deploy-on-demand-enabled> option in config.xml without any issues.  However, after the upgrade any time we start the server in production mode Weblogic deploys the admin console even with the option set.  The documentation for this option hasn't changed so we're led to believe that it should still work the way it worked in 12.1.1.  We're wondering if this is a bug with the new version or if there is something else we need to set to get the behavior in 12.1.3 to work the same as 12.1.1.  We don't utilize the admin console frequently but would like it to be available without using WLST to enable it before logging in.
    Thank you,
    Kent Z.

    Could be that the element name or location in the config.xml has been changed.
    Try to set InternalAppsDeployOnDemandEnabled through the general config page in the wlc or use wlst to see if if works.
    On-demand Deployment of Internal Applications
    Cheers,
    Peter

Maybe you are looking for