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

Similar Messages

Deployment descriptor error for an EJB 3.0 entity bean module

Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto

Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto

Deployment Descriptor - run time modification

As EJB spec states that deployment descriptor is for dynamic modification of EJB properties.
I don't understand that once we give these (EJBs) JAR files to customer, how customer can change deployment descriptors which are hidden inside JAR files.
Is there any tool which will open these JARs and modify the deployment descriptors.
Any other comments are appreciated.
I am using BAS 4.5 and JBoss 2.4.4.

Greetings,
As EJB spec states that deployment descriptor is for
dynamic modification of EJB properties.Actually, the deployment descriptor allows for "post compile-time customization" of beans by means of the "declarative deployment model"...
IOW, the DD provides information that is to be made available to the bean by its runtime environment (container), which information is provided in between compile-time and runtime. Such information may provide customization data ("Environment References"), make resources available (reference links), and/or provide security information (role references). The bean ("component", actually, since web-tier components now also benefit from deployment descriptors ;), can then get access to this information during it's runtime as required. Typically, this means customization data - which, of course, allow the bean to initialize its state for the application/enterprise in which it runs - though, role-references may be used to fine-grain security authorizations; reference links, however, may be thought of as working in the opposite direction - they are handled transaparently by the container - since, in essence it is the bean that is providing link value.
I don't understand that once we give these (EJBs) JAR
files to customer, how customer can change deployment
descriptors which are hidden inside JAR files.Technically, it is the "bean descriptor", possibly the "assembly (application) descriptor", that is given to the end user (either the application assembler or deployer...), since the deployment descriptor is not created until actual deployment. ;)
Of course, the real issue here is "component customization": the customer does not modify the DD, but rather provides values for the lookups the component is making (which lookups -as well as other details about what's expected from them - are provided to the customer along with the component), during either the assembly and/or deployment phases (each of which may produce their own DD levels).
Is there any tool which will open these JARs and
modify the deployment descriptors.In a manner of speaking... the vendor's deployment tool provides the intended capability.
Any other comments are appreciated.
I am using BAS 4.5 and JBoss 2.4.4.Regards,
Tony "Vee Schade" Cook

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
          >

Error in Sun XML schema for servlet2.4 deployment descriptor?

Hi,
I'm including the new XML schema for version 2.4 of the servlet standard in my web.xml deployment descriptor, using http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
When I try to save the XML file, XMLSpy reports an error in the schema file itself: "Undefined schema component 'base' encountered - simpleContext can not have a base that is a complexType with complexContent"
This error is on line 744, and is caused by the snippet:
<xsd:simpleContent>
<xsd:extension base="j2ee:nonEmptyStringType"/>
</xsd:simpleContent>
Can anyone explain why I'm getting a validation failure on this schema? Surely someone else must have experienced the same thing, but I can't track down any reference to it anywhere. Help!

XMLSpy is known to be flawed. From my own experience of implementing
validators and data-binding tools, and from my experience of working in the
W3C Schema working group, I can tell you that there are countless cases
where XMLSpy violates the schema specification.
I checked the corresponding part of the schema, but it looks correct to me.
So I suspect that this is another bug in XMLSpy.
Try Xerces. That's probably the best in terms of conformance to the spec.

Alternate deployment descriptor for an exploded war (web.xml/weblogic.xml)

Hi.
I believe this is a simple question: Am i able to deploy an exploded war directory using an alternate deployment descriptor (web.xml outside the directory structure of my application)? According to the docs, I can do it for an ear, but I'm not sure if it can be done for an war.
http://download.oracle.com/docs/cd/E13222_01/wls/docs81b/deployment/concepts.html#1001945
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/Application.html#AltDescriptorPath
Thanks in advance.
Best regards,
Daniel.

Or should i use a deployment plan?
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/deployment/config.html#wp1057141

How to specify the security policy "Allow access to everyone" for security role in Deployment descriptor

Hi,
I am migrating a web application from Websphere to Weblogic. The web application has a security role defined in web.xml (Use LDAP for authentication).
security-role>
        <description>Authenticated</description>
        <role-name>Authenticated</role-name>
    </security-role>
This role is mapped to a special subject "All authenticated user in appliation realm" in WAS.
In weblogic, I have the following setting in weblogic.xml
<wls:security-role-assignment>
        <wls:role-name>Authenticated</wls:role-name>
        <wls:externally-defined />
    </wls:security-role-assignment>
And after deploy the application, have to manually add a security role and add the security policy "Allow access to everyone" to this role.
I am wondering if this setting can be specified in for example weblogic.xml so just deploy web applicaiton using deployment descriptor, and I don't need write script to do that .
Thanks

Hi,
You need to have Back End support to achieve this. In Back End you need to create two groups . You need to know what joins has to be made for which group (which is more important) and also make session variable for the userrole (with SQL supporting it). In the BMM layer, we need to put the security join conditions in the 'where clause'.
And make a common report. User loggin in with the respective userid will have userrole and joins assigned in the Back end. And they will be viewing the report according to their access.
Hope this will solve your problem.
Regards
MuRam

JNDI environment properties for EJB in deployment descriptor

Is it possible to deploy an EJB on weblogic 6.0 such that the EJBHome
object is bound using JNDI to a different JNDI server such as ldap
server instead of the weblogic server by specifying JNDI env.
properties like PROVIDER_URL, INITIAL_CONTEXT_FACTORY in the
deployment descriptor? That is use the weblogic built-in deployer but
bind the JNDI names to a different JNDI server. For this, can the
EJBHome objects be treated as just RMI (over IIOP) objects and bind
them (stubs of the RMI objects) using the Sun's JNDI service provider.
The goal is that thereafter the Home JNDI names can be looked up by
RMI clients and the interface methods invoked.
Thanks,
... arun

Must I put the war and jar files in the same ear ?
oh..ft...my boss is killing me ..
package..repackage...package..repackage..and test ??
Could anybody tell me how to refer a SLSB without put the webApp
and the EjbApp together in an Ear file ??
thanks very much!!!!

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.

Plugin to migrate deployment descriptors for J2EE apps

I was told there is a JDev 10g plugin that deals with migration of deployment descriptors for different kinds of J2EE application servers.
If it is true, what is the plugin name? Is it already contained within JDev or we are supposed to download and install it?
Regards,
Eduardo Gouvea.

Have a look at the deployment desriptor category in the JDeveloper new gallery - you'll see support for OC4J, JBoss, and Weblogic built-in.

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.

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]

Document for deployment descriptor and config

Hi,
I just downloaded wls8.1. I am browsing the online document. I ca't find any document
on config.xml (there is one in 70). I can't find the deployment descriptor too
like application.xml, weblogic-application.xml
Thanks

more info at:
http://e-docs.bea.com/wls/docs81/programming/app_xml.html
"Erik Johnson" <[email protected]> wrote:
>
application.xml documentation at:
http://e-docs.bea.com/wls/docs81/programming/app_xml.html#1007302
"Erik Johnson" <[email protected]> wrote:
Documentation on config.xml at:
http://e-docs.bea.com/wls/docs81/config_xml/overview.html
"Jen " <[email protected]> wrote:
Hi,
I just downloaded wls8.1. I am browsing the online document. I ca'tfind
any document
on config.xml (there is one in 70). I can't find the deployment descriptor
too
like application.xml, weblogic-application.xml
Thanks

How To Define Security in the deployment descriptor for an ejb

Hi All
Pls help!
I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
Thanks
Yours in Java

Hi All
Pls help!
I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
Thanks
Yours in Java

Custom deployment descriptor

Hi there
We are in the process of deploying our standard J2EE EAR file to
WebLogic 9.2 MP2. The EAR file does not contain weblogic custom
deployment descriptors (e.g.: weblogic.xml) but only standard DDs (e.g.:
web.xml)
I have some doubts about resources mapping and I'd like to get some help
from experienced WL users.
Basically our EAR file is composed of an EJB module and a WEB module.
Each module declares some references such as:
WEB.XML snippet
<resource-ref>
<description>DataSource for partition 'default'</description>
<res-ref-name>jdbc/Datasource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Now the questions:
1) Is there a way to map the resources during the deployment, using the
console? This is the way followed by WebSphere and Oracle AS, for
example. If this is not possible, should I provide a Deployment Plan for
that EAR file? I tried to provide the xml Deployment Plan generated by
weblogic.PlanGenerator utility together with the EAR file while
deploying the app, but no luck. It seems the Deployment Plan should be
provided in a jar file. Is that correct?
2) If the previous options are not possible, how can I create the custom
deployment descriptor? Is there an "Assembly Tool" that imports the
standard EAR and then export the custom EAR file with the custom
deployment descriptors correctly generated?
Thank you a lot in advance.

A deployment plan is external to the ear/jar file.
It is probably easiest to deploy the application with the console, and then
use the console to change the values you want. It will automatically
generate a deployment plan for you.
"Quasar" <[email protected]> wrote in message
news:[email protected]..
Hi there
We are in the process of deploying our standard J2EE EAR file to
WebLogic 9.2 MP2. The EAR file does not contain weblogic custom
deployment descriptors (e.g.: weblogic.xml) but only standard DDs (e.g.:
web.xml)
I have some doubts about resources mapping and I'd like to get some help
from experienced WL users.
Basically our EAR file is composed of an EJB module and a WEB module.
Each module declares some references such as:
WEB.XML snippet
<resource-ref>
<description>DataSource for partition 'default'</description>
<res-ref-name>jdbc/Datasource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Now the questions:
1) Is there a way to map the resources during the deployment, using the
console? This is the way followed by WebSphere and Oracle AS, for
example. If this is not possible, should I provide a Deployment Plan for
that EAR file? I tried to provide the xml Deployment Plan generated by
weblogic.PlanGenerator utility together with the EAR file while
deploying the app, but no luck. It seems the Deployment Plan should be
provided in a jar file. Is that correct?
2) If the previous options are not possible, how can I create the custom
deployment descriptor? Is there an "Assembly Tool" that imports the
standard EAR and then export the custom EAR file with the custom
deployment descriptors correctly generated?
Thank you a lot in advance.

Deployment Descriptor defaults for clustering

Similar Messages

Maybe you are looking for