EJB descriptors for clustering!

Hi,
          Are ALL EJB's compiled for clustering by default (without specifying the
          value for <home-is-clusterable>, etc in the weblogic-ejb-jar) ?
          If yes, is there any recommendation from BEA to specify this voluntarily for
          every EJB ?
          Bye,
          Sriram.C.S
          

[att1.html]
          

Similar Messages

  • Creating  Standard EJB Descriptor (ejb-jar.xml) by JDeveloper

    Hi
    If I create a Session Bean by JDeveloper it create a weblogic-ejb-jar file (Weblogic EJB Descriptor) for it
    Do you know how can I use JDeveloper for creating Standard EJB Descriptor (ejb-jar.xml) for my Session Bean ? please if you can explain step by step
    thank you

    Hi,
    Right-click Model project and select New -> General -> Deployment Descriptors -> Java EE Deployment Descriptor and click OK, on the next screen you can choose ejb-jar.xml.
    Pedja

  • Deployment Descriptor defaults for clustering

              If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
              Darko Bohinc
              Synergy International Limited
              www.synergy.co.nz
              

              Darko,
              All EJB "homes" are clusterable by default (a request for a home interface can be routed to any server in the cluster).
              In the case of stateless session beans, you also achieve load-balancing by default (method calls can be sent to any server in the cluster). Failover is achieved by default only BETWEEN method calls and not DURING method calls. In other words, the stub will retry a method call on another server in the cluster only if the stub is absolutely sure that the method call did not reach the server in the cluster during the first try. If the stub cannot determine this, it will not retry by default and you should eventually get an error. If you would like the server to retry all method calls even if the server failed in the middle of a call, then you need to write your EJB methods to be idempotent (calling any method in the EJB many times with the same parameters should achieve the same result with no side effects such as duplicate inserts in the database etc). You will then have to explicitly set the "stateless-bean-methods-are-idempotent" element in the deployment descriptor for the EJB to let WL know that all methods can be retried without any worries.
              Please see the following link for additional information:
              http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#1046391
              Hope this answers your questions.
              Giri
              "Darko Bohinc" <[email protected]> wrote:
              >
              >If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
              >
              >Darko Bohinc
              >Synergy International Limited
              >www.synergy.co.nz
              

  • EJB deployment descriptors in clustered environment

              I was wondering how EJB deployment descriptor settings work in a clustered environment. Are the deployment descriptors per WebLogic instance they are deployed in or the entire clustered environment? For example, if my descriptor for a stateless session ejb has max-beans-in-free-pool set to 5 and I deploy this stateless ejb in 4 WebLogic instances of one cluster, does this mean that there will be a max of 5 instance of this bean in the free pool for the entire cluster or will there be a max of 20 (5 per WebLogic instance and 4 WebLogic instances in the cluster) instances of this bean for the entire cluster?
              Thanks,
              Bryan
              

    Those settings are per server instance.
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com
              +1.617.623.5782
              WebLogic Consulting Available
              "Bryan Dixon" <[email protected]> wrote in message
              news:3a6b51a0$[email protected]..
              >
              > I was wondering how EJB deployment descriptor settings work in a clustered
              environment. Are the deployment descriptors per WebLogic instance they are
              deployed in or the entire clustered environment? For example, if my
              descriptor for a stateless session ejb has max-beans-in-free-pool set to 5
              and I deploy this stateless ejb in 4 WebLogic instances of one cluster, does
              this mean that there will be a max of 5 instance of this bean in the free
              pool for the entire cluster or will there be a max of 20 (5 per WebLogic
              instance and 4 WebLogic instances in the cluster) instances of this bean for
              the entire cluster?
              >
              > Thanks,
              > Bryan
              >
              

  • Weblogic Deployment Descriptor for CMP EJB

    Hi all,
    Am new to EJB, CMP. Pls help me how to write deployment descriptors for the CMP EJB for Weblogic.
    Give me the list of the Deployment descriptors needed and also pls give me some samples
    thanks in advance
    rgds
    Ravi Bharathi

    The easiest way is to go through some tutorial or refer the code samples. If you have installed weblogic, there are examples provided in the weblogic installation folder itself for each type of bean. Basically for cmp you have to provide the table names and mapping between the class variables to db fields in weblogic_cmp_rdbms.xml deployment descriptor.

  • "Edit EJB Descriptor..."  Not working

    Hi
    When i press the "Edit EJB Descriptor..." in a EJB under Deployments in the web-logic
    6.1 console, I get this Error:
    Error Start -
    "There was an error while loading the descriptor for component:
    EnvelopeEntityBeans
    Please fix the error in the component descriptor file(s), redeploy the component
    and then press continue to attempt to edit this components descriptor.
    The following error(s) occurred:
    error in finding weblogic.Home"
    Error end
    I deploy a EAR File containing 2 EJB's - one of them have entity beans in it, and
    it is the one that have the error.
    Thanks
    Gal

    Just so everyone knows, I was on hold with Adobe tech support for ALMOST TWO HOURS despite the 2-minute wait time they estimated at the beginning of my call. I really don't know how else to describe how I feel, except:
    Clearly Adobe gives zero f*cks, even though I pay $40 per month for the creative cloud membership.
    Adobe, if you were a person (which you are, because now corporations are people in the USA), I would wish upon you the most severe case of herpes-slash-genital-rot the world has ever seen. I hope that the discomfort of this particular ailment results in your inability to participate in even the shortest meetings or conference calls, due to the fiery burning pain in your nether regions. Then perhaps maybe a more competent and ethical software company could assume your role in the marketplace.
    I will be especially amused if an Adherpe forum moderator has time to delete my post and/or ban me forever from the Adobe community, given that a tech support person has no time to answer my call. The plot thickens.
    Toodle-loo.
    PS: I am extremely sleep deprived, so I refuse to be held accountable for any offense taken to any of the statements set forth above.

  • Weblogic console Edit EJB Descriptor link missing

    Hi..
    I am running weblogic 6.1 sp1. And I have a set of EJB's deployed. But when I click
    on any ejb in the tree view in console, i can not see the Edit EJB Descriptor link
    on the right hand side screen.
    I have two server instances running with the same set of EJB's deployed. And I can
    get this link on one console and do not get it on the other console.
    Can anyone tell me what is wrong with it ? Or is there any setting using which we
    can disable the access to Edit EJB Descriptor link ?
    Thanks in advance..
    Mandar

    hi..
    I have NOT disabled the link myself.... but for some reasons, the link is not available.
    I also checked the right click menu (right click on the deployed ejb in the tree
    view) and i didnt get the Edit EJB Descriptor option there also... I have two server
    instances running in Development mode and one console is not showing the link while
    the other is showing the link..
    I am attaching a screenshot to explain the situation. Can anyone has experienced
    this before ? Please help me..
    Regards
    Mandar
    "Mihir Kulkarni" <[email protected]> wrote:
    I am running weblogic 6.1 sp1. And I have a set of EJB's deployed. Butwhen I click
    on any ejb in the tree view in console, i can not see the Edit EJBDescriptor link
    on the right hand side screen.
    I have two server instances running with the same set of EJB's deployed.And I can
    get this link on one console and do not get it on the other console.
    Can anyone tell me what is wrong with it ? Or is there any setting usingwhich we
    can disable the access to Edit EJB Descriptor link ?No there is no such option to disable the access to edit the EJB
    Descriptors - its present both in the Dev and the Prod mode.
    Besides the link in the right frame, you can also right click on the EJB
    Name in the navigation tree to edit the descriptors ....
    cheers,
    Mihir
    Thanks in advance..
    Mandar
    [Ejb Descriptor missing.JPG]

  • Failed to save deployment descriptor for: EEdnc cause: null

    I am getting nowhere fast trying to deploy an ear with 1 EJB jar and a war file.
    The war deploys by itself ok. So the EJB jar has 2 stateless beans and an MDB
    configured for mqseries. I deployed a sample with some EJBs so the configuration
    must be ok. It verifies with no errors, compiles with ejbc, javac and rmi ok. then I get
    this error...
    I was wondering if anyone has run into this before or if an expert knows what it is.
    I have been using the admin console to deploy as well as asadmin.
    \j2ee-apps\EEdnc\com\boeing\bca\ednc\ejbcontainer\services\imsaccess\_IMSAccess_Stub.class
    [24/Sep/2003:10:47:33] INFO ( 1564): DPL5110: EJBC - END of EJBC for [EEdnc]
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]uid: 69758199598546944
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: BoltsReceiver
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546944
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: IMSAccess
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546945
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: JmsEjb
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546946
    [24/Sep/2003:10:47:33] FINE ( 1564): Saving the app descriptor....................
    [24/Sep/2003:10:47:33] WARNING ( 1564): DPL5035:Error while running ejbc
    com.iplanet.ias.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: EEdnc
    cause: null
         at com.iplanet.ias.deployment.backend.EJBCompiler.wrapException(EJBCompiler.java:589)
         at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:186)
         at com.iplanet.ias.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:215)
         at com.iplanet.ias.deployment.backend.AppDeployer.deploy(AppDeployer.java:98)
         at com.iplanet.ias.deployment.backend.AppDeployer.doRequest(AppDeployer.java:50)
         at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:745)
         at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:667)
         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.iplanet.ias.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:188)
         at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:137)
         at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
         at com.iplanet.ias.admin.servermodel.controllers.SOMRequestDispatcher.invoke(SOMRequestDispatcher.java:88)
         at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.doDeploy(AppServerInstanceController.java:2244)
         at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.deployApplication(AppServerInstanceController.java:1099)
         at com.iplanet.ias.admin.servermodel.AppServerInstance.deployApplication(AppServerInstance.java:249)
         at com.iplanet.ias.admin.server.gui.jato.DeployEARApplicationViewBean.add(DeployEARApplicationViewBean.java:111)
         at com.iplanet.ias.admin.server.gui.jato.IASViewBean.handleOkRequest(IASViewBean.java:235)
         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.iplanet.jato.view.command.DefaultRequestHandlingCommand.execute(DefaultRequestHandlingCommand.java:183)
         at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:299)
         at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:811)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:749)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:596)
         at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:772)
         at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:446)
         at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:324)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
         at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
         at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardHostValve.invoke(Standar
    [24/Sep/2003:10:47:34] WARNING ( 1564): Deployment Error
    com.iplanet.ias.deployment.backend.IASDeploymentException: Error while running ejbc -- Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: EEdnc
    cause: null

    I don't remember exactly what it was, but I think it was a JNDI name. I resolved it by using
    <ejb-link></ejb-link> in the ejb-local-ref in the ejb-jar.xml. I made the ejb-link match the
    ejb-name in the same descriptor. This seemed to work better than changing the jndi-name in the sun-ejb-jar.xml.
    One thing you can do is set the logging for server1 to finest, then bounce the server and deploy.
    Shut down the server and look at the log with wordpad. Start at the bottom and work your
    way up looking for stack traces. They get more and more detailed as you go up and may
    point you to the exact problem. Works most of the time.

  • Exception Description: Missing descriptor for ...

    I have this to query:
    codes:
    UnitOfWork uow = getSessionFactory().acquireUnitOfWork();
    Vector params = new Vector(1);
    params.add(argCompanyId);
    VsaSpaVendor result = (VsaSpaVendor)uow.executeQuery("findVendorByCompanyId", VsaSpaVendor.class, params);
    uow.commit();
    return result;
    then I startup the embedded oc4j in jdeveloper,I got the following errors,
    but when I deploy my application to a standalone oc4j server, it works.
    errors:
    Caused by: Exception [TOPLINK-6007] (Oracle TopLink - 10g Release 3 (10.1.3.3.0) (Build 070608)): oracle.toplink.exceptions.QueryException
    Exception Description: Missing descriptor for [class com.vs.espa.model.VsaSpaVendor].
    Query: ReadObjectQuery(com.vs.espa.model.VsaSpaVendor)
         at oracle.toplink.exceptions.QueryException.descriptorIsMissing(QueryException.java:358)
         at oracle.toplink.queryframework.ReadObjectQuery.checkDescriptor(ReadObjectQuery.java:211)
         at oracle.toplink.queryframework.ObjectLevelReadQuery.checkPrePrepare(ObjectLevelReadQuery.java:566)
         at oracle.toplink.queryframework.ObjectLevelReadQuery.checkEarlyReturn(ObjectLevelReadQuery.java:501)
         at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:564)
         at oracle.toplink.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:779)
         at oracle.toplink.queryframework.ReadObjectQuery.execute(ReadObjectQuery.java:388)
         at oracle.toplink.queryframework.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:836)
         at oracle.toplink.publicinterface.UnitOfWork.internalExecuteQuery(UnitOfWork.java:2604)
         at oracle.toplink.publicinterface.Session.executeQuery(Session.java:993)
         at oracle.toplink.publicinterface.Session.executeQuery(Session.java:950)
         at oracle.toplink.publicinterface.Session.readObject(Session.java:2541)
         at com.vs.espa.model.EspaPublicFacadeBean.findVendorByCompanyId(EspaPublicFacadeBean.java:1037)
         at com.vs.espa.model.EspaPublicFacadeBean.findUserByUserName(EspaPublicFacadeBean.java:796)
         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:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
         ... 129 more
    Anyone can tell me why?
    Jerry

    Thank you, James
    I create SessionFactory by this:
    public EspaPublicFacadeBean() {
    this.sessionFactory =
    new SessionFactory("META-INF/sessions.xml", "default");
    the sessions.xml
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <!DOCTYPE toplink-configuration PUBLIC "-//Oracle Corp.//DTD TopLink Sessions 9.0.4//EN" "sessions_9_0_4.dtd">
    <toplink-configuration>
    <session>
    <name>default</name>
    <project-xml>META-INF/espaMap.xml</project-xml>
    <session-type>
    <server-session/>
    </session-type>
    <login>
    <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
    <datasource>jdbc/devvsDS</datasource>
    <platform-class>oracle.toplink.platform.database.oracle.Oracle10Platform</platform-class>
    <user-name>vsc</user-name>
    <encryption-class-name>oracle.toplink.internal.security.JCEEncryptor</encryption-class-name>
    <encrypted-password>03B2E88B1EC44B3883BEF6EB790DF0F8D62D1A19DF561D1E</encrypted-password>
    <uses-native-sequencing>true</uses-native-sequencing>
    <sequence-preallocation-size>1</sequence-preallocation-size>
    <uses-external-connection-pool>true</uses-external-connection-pool>
    <uses-external-transaction-controller>true</uses-external-transaction-controller>
    </login>
    <external-transaction-controller-class>oracle.toplink.transaction.oc4j.Oc4jTransactionController</external-transaction-controller-class>
    <enable-logging>true</enable-logging>
    <logging-options>
    <log-debug>true</log-debug>
              <log-level>fine</log-level>
    <print-thread>true</print-thread>
    </logging-options>
    </session>
    </toplink-configuration>
    class-mapping-descriptor defined in espaMap.xml
    <opm:class-mapping-descriptor xsi:type="toplink:relational-class-mapping-descriptor">
    <opm:class>com.vs.espa.model.VsaSpaVendor</opm:class>
    <opm:alias>VsaSpaVendor</opm:alias>
    <opm:primary-key>
    <opm:field table="VSA_SPA_VENDOR" name="COMPANY_ID" xsi:type="opm:column"/>
    </opm:primary-key>
    <opm:events xsi:type="toplink:event-policy"/>
    <opm:querying xsi:type="toplink:query-policy">
    <opm:queries>
    <opm:query name="findVendorByCompanyId" xsi:type="toplink:read-object-query">
    <opm:criteria operator="equal" xsi:type="toplink:relation-expression">
    <toplink:left name="companyId" xsi:type="toplink:query-key-expression">
    <toplink:base xsi:type="toplink:base-expression"/>
    </toplink:left>
    <toplink:right xsi:type="toplink:parameter-expression">
    <toplink:parameter name="argCompanyId" xsi:type="opm:column"/>
    </toplink:right>
    </opm:criteria>
    <opm:arguments>
    <opm:argument name="argCompanyId">
    <opm:type>java.lang.Integer</opm:type>
    </opm:argument>
    </opm:arguments>
    <toplink:timeout>0</toplink:timeout>
    <toplink:reference-class>com.vs.espa.model.VsaSpaVendor</toplink:reference-class>
    <toplink:cache-usage>primary-key</toplink:cache-usage>
    <toplink:lock-mode>none</toplink:lock-mode>
    </opm:query>
    Any ideas? Or could you give me some sample codes?
    Jerry

  • Is Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.

    All I want to know is if Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.
    I have been planning and deploying my companies first Windows Server 2012/SQL Server 2012 Always On cluster and Always On Availability Groups Multi-Subnet cluster and instances for SharePoint 2013, and I will be brutally honest, the documentation on either
    the MSDN and TechNet leave alot to be desired. Continually finding links in the documentation will take me from a Windows 2012 reference to a page talking about Windows Server 2008 or R2, The differences of which there are so many when it comes to configurations,
    settings, roles, services when working with SQL Server 2012. I have been confused, frustrated, screaming mad, with all the misdirection in this documentation.  The documentation takes me windows 2008 R2 which is different than 2012!
    Tired and trying to pick myself up off the floor!
    Greg
    Gman

    In general, DTC is not required for SQL 2012.  But, since you are asking specifically about SharePoint, it would be better to ask in a SharePoint forum.  They would be more likely to know those situations where FTC might be needed by SharePoint. 
    .:|:.:|:. tim

  • Why we need to go for clusters ?

    Hi ,
        Plz clarify me y we need to go for clusters in ABAP-HR programming ?...
    Thanks in advance..
    Suresh..

    Because, that is where the ( Time & Payroll)  Transactional Data is stored.. For Reporting off the Master Data tables you can use the PAnnnn & HRPnnnn Tables with the relevant Authority checks.. PL go through the following <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/4f/d528ff575e11d189270000e8322f96/frameset.htm">SAP Help</a> for additional info on HR Clusters.
    ~Suresh

  • Cannot use file for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Serve

    Hi
    Windows serv 2012 cluster on sql 2012 cluster with 2 instance. on works fine , Second instanc ewhen i try to creat DB a get this message. 
    Cannot use file  for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql
    Server does not have a dependency on it.
    CREATE DATABASE failed. Some file names listed could not be created. Check related errors. (Microsoft SQL Server, Error: 5184)
    Any help please
    kam
    KAMEL

    Hi Saurabh
    Exactly I have SQL SERVER 2012
    Failover Clustering   in windows server 2012 with two nodes with
    two instances and exactly I run them in the same server and each instance with
    three drives Backup, Data and log.   
    KAMEL

  • Create EJB Control For Remote Server

    I'm having trouble creating an EJB control for a EJB residing in a remote server.
    First, I've a JAR containing the remote/home interfaces and added it as a Library in the WLW 8.1 application.
    When creating a new EJB Control, there's no way to successfully create the control.
    At the STEP 2 GUI:
    I am able to specify a JNDI-NAME, but the home/bean interface fields are empty. If I click on "Browse application EJBs..." button, nothing is available. If I click on "Browse server EJBs", it only shows EJBs in the current server.
    Thanks

    Hi
    I believe you are on Workshop8.1 Spx.
    This is a known issue. The reason the ejb does not show up as an application ejb because we have just the interfaces as a library and not the whole EJB.
    Since the EJB's are not deployed on the server it will not show up either.
    Unfortunately there is no way to point to a remote domain and get all the ejb's deployed there.
    Workaround:
    You can deploy the ejb locally, create the ejbcontrol and then undeploy the EJB. You need to manually change the home jndiname to use the remote server url.
    Thanks
    Vimala

  • Error getting the EJB Handle for context name: User

    I am getting EJB Handle for context name: User.
    1) I specified ejb's and datasource in the ejb-jar.xml in the session tags.
    <session> </session>
    and I also included ejb's and datasource in the sun-ejb-jar.xml still I am getting the above error I am new to EJB how can I resolve this?

    What is the Oracle application server version?
    JDeveloper 11g supports direct deployment to Oracle Application Server 11g
    http://www.oracle.com/technology/products/jdev/collateral/papers/11/newfeatures/index.html

  • Deployment Descriptor for SOA-SAR files on weblogic?

    Hi,
    i want to access a shared library (that i deployed separately) from within a SOA Project with an SCA composite that is deployed as a SOA-SAR.
    I am using JDeveloper 11.1.1.3 along with the according Weblogic Server and SOA Suite.
    My shared library is deployed correctly, because i can access it from e.g. other web applications. These are deployed as war files and therefore i have a weblogic.xml file, where i define my library-refs. The problem is, that weblogic.xml as well as weblogic-application.xml seem not to be processed when deploying the SOA-SAR file. Is there another descriptor for that, or is it just not possible to access shared libraries from within a SOA Project deployed as SOA-SAR?
    For some more background information, i have my entities deployed as a shared library in weblogic (deployed as a web application(war file)). Now i want to create an SCA composite with a Spring component. A Bean defined in the Spring context shall access the entities from within the shared library.
    I hope someone has a solution for this, because i already spent a lot of time on searching for a solution and did not even get close to one. The closest solution i found was deploying the SCA composite as a web application using in Spring the sca:service tag. In that case i have the problem that i want to use the SCA composite from within another SCA composite and i want it to use a local call, not a SOAP request for performance reasons. So this solution unfortunately doesn't fit my requirements.

    Please ask this in the SOA Suite forum:
    SOA Suite
    You might also find the answer in the SOA Suite 11g docs:
    http://download.oracle.com/docs/cd/E12839_01/soa.htm

Maybe you are looking for