Deploying Portal App in exploded EAR format

Hi all,
We are using Portal BEA 8.1 SP2 and we also configured a cluster with
production mode enabled.
We want to deploy our portal app in exploded EAR format.
http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723
But when we use workshop to "Build App" and when the application build is successful.
And when we copy the App folder to the production server and deploy,
We get the following error,
[Deployer:149033]preparing application commApp on mgServer1
[Deployer:149033]preparing application commApp on mgServer2
[Deployer:149033]failed application commApp on mgServer1
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:
Exception:weblogic.management.ApplicationException: Application commApp is packaged using the WebLogic Split Development Directory structure. The Split Development Directory structure can only be used in development environments with a single WebLogic Server. If you wish to deploy this application to a separate managed server or cluster, use the wlpackage ant task to create an exploded or archived EAR.
[Deployer:149033]failed application commApp on mgServer2
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:
Exception:weblogic.management.ApplicationException: Application commApp is packaged using the WebLogic Split Development Directory structure. The Split Development Directory structure can only be used in development environments with a single WebLogic Server. If you wish to deploy this application to a separate managed server or cluster, use the wlpackage ant task to create an exploded or archived EAR.
What is the problem ?
Thanks,
Karthi.
[att1.html]

To deploy the app as EAR (I am confused by the expression "exploed EAR", my understanding
its either exploded or EAR format) build the app as EAR (there is an option in
the workshop build drop down).
Did this help?
S
"Karthi" <[email protected]> wrote:
>
>
Hi all,
We are using Portal BEA 8.1 SP2 and we also configured a cluster with
production mode enabled.
We want to deploy our portal app in exploded EAR format.
http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723
But when we use workshop to "Build App" and when the application build
=
is successful.=20
And when we copy the App folder to the production server and deploy,=20
We get the following error,
[Deployer:149033]preparing application commApp on mgServer1
[Deployer:149033]preparing application commApp on mgServer2
[Deployer:149033]failed application commApp on mgServer1
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
=
application commApp on devCluster,bkarthiPS.:=20
Exception:weblogic.management.ApplicationException: Application commApp
=
is packaged using the WebLogic Split Development Directory structure.
=
The Split Development Directory structure can only be used in =
development environments with a single WebLogic Server. If you wish to
=
deploy this application to a separate managed server or cluster, use
the =
wlpackage ant task to create an exploded or archived EAR.
[Deployer:149033]failed application commApp on mgServer2
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
=
application commApp on devCluster,bkarthiPS.:=20
Exception:weblogic.management.ApplicationException: Application commApp
=
is packaged using the WebLogic Split Development Directory structure.
=
The Split Development Directory structure can only be used in =
development environments with a single WebLogic Server. If you wish to
=
deploy this application to a separate managed server or cluster, use
the =
wlpackage ant task to create an exploded or archived EAR.
What is the problem ?
Thanks,
Karthi.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#c0c0c0 background=3D"">
<DIV><FONT face=3DArial size=3D2>Hi all,<BR><BR>We are using Portal BEA
=
8.1 SP2 and=20
we also configured a cluster with<BR>production mode enabled.<BR><BR>We
=
want to=20
deploy our portal app in exploded EAR=20
format.<BR><BR>http://edocs.bea.com/wlp/docs81/bestprac/conf.html#1056723=
<BR><BR>But=20
when we use workshop to "Build App" and when the application build is=20
successful. <BR><BR>And when we copy the App folder to the production
=
server and=20
deploy, <BR><BR>We get the following =
error,<BR><BR>[Deployer:149033]preparing=20
application commApp on mgServer1<BR>[Deployer:149033]preparing =
application=20
commApp on mgServer2<BR>[Deployer:149033]failed application commApp on=20
mgServer1<BR>[Deployer:149034]An exception occurred for task=20
[Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:=20
<BR>Exception:weblogic.management.ApplicationException: Application =
commApp is=20
packaged using the WebLogic Split Development Directory structure. The
=
Split=20
Development Directory structure can only be used in development =
environments=20
with a single WebLogic Server. If you wish to deploy this application
to =
a=20
separate managed server or cluster, use the wlpackage ant task to create
=
an=20
exploded or archived EAR.<BR>.<BR>[Deployer:149033]failed application
=
commApp on=20
mgServer2<BR>[Deployer:149034]An exception occurred for task=20
[Deployer:149026]Deploy application commApp on devCluster,bkarthiPS.:=20
<BR>Exception:weblogic.management.ApplicationException: Application =
commApp is=20
packaged using the WebLogic Split Development Directory structure. The
=
Split=20
Development Directory structure can only be used in development =
environments=20
with a single WebLogic Server. If you wish to deploy this application
to =
a=20
separate managed server or cluster, use the wlpackage ant task to create
=
an=20
exploded or archived EAR.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>What is the problem ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Karthi.</FONT></DIV></BODY></HTML>

Similar Messages

How to Deploy portal 8.1 production cluster in exploded ear format in solaris

Hi all,
How can we deploy our PORTAL application in
Weblogic 8.1 SP2 Weblogic 8.1 SP2 Weblogic 8.1 SP2 Weblogic 8.1 SP2
Solaris Solaris Solaris Solaris Solaris Solaris
PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL
APPLICATION
with PRODUCTION MODE = true PRODUCTION MODE = true PRODUCTION MODE = true
PRODUCTION MODE = true
Cluster Cluster Cluster Cluster Cluster Cluster Cluster Cluster Cluster
Cluster (2 x 2 managed servers)
As
exploded ear format exploded ear format exploded ear format exploded ear
format exploded ear format
PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE PLEASE
don't send me this link
http://e-docs.bea.com/wlp/docs81/deploy/deploy.html#1003591
I used this link 100 times, but no use.
Steps I did
1. Build the application using workshop ( NO ear NO ear NO ear NO ear NO ear
NO ear NO ear NO ear )
2. use wlpackage to pack the built application ( NO ear NO ear NO ear NO
ear NO ear NO ear NO ear NO ear )
3. Deploy using console ( NO stage NO stage NO stage NO stage NO stage)
The Error,
The following error message I got.
[Deployer:149033]preparing application commApp on mgServer1
[Deployer:149033]preparing application commApp on mgServer2
[Deployer:149033]failed application commApp on mgServer1
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
application commApp on devCluster,bkarthiPS.:
Exception:weblogic.management.ApplicationException: Application commApp is
packaged using the WebLogic Split Development Directory structure. The Split
Development Directory structure can only be used in development environments
with a single WebLogic Server. If you wish to deploy this application to a
separate managed server or cluster, use the wlpackage ant task to create an
exploded or archived EAR.
[Deployer:149033]failed application commApp on mgServer2
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
application commApp on devCluster,bkarthiPS.:
Exception:weblogic.management.ApplicationException: Application commApp is
packaged using the WebLogic Split Development Directory structure. The Split
Development Directory structure can only be used in development environments
with a single WebLogic Server. If you wish to deploy this application to a
separate managed server or cluster, use the wlpackage ant task to create an
exploded or archived EAR.
Thanks,
Karthi.

Its simple PORTAL application . After deploying this application we can add portlets as a childs to this application .
Now this is simple PORTAL application with CSS file.
Give me some idea about
How to create PORTLET application with CSS files . Where to include this CSS file in a PORTLET application??????
Normally we are creating first PORTAL application and adding CSS files to
Portlet Content-->Themes-->html--> abc.css .
--> Head.jsp we are giving the css file path in this JSP page as
<link href='<wps:urlFindInTheme file="abc.css"/>' rel="styleSheet" type="text/css">
After this I am adding my PORTLET application to this PORTAL .
Then its working fine. But I want to know how to add CSS files to PORTLET application???????
Please help me :-(

Deploy web application with exploded directory format

I am quite new with Oracle9iAS Containers for J2EE. Currently, my project is not using EJB, only JSP and Servlets. I want to deploy the war file with exploded directory format. I don't want to use the default web application directory j2ee/home/default-web-app. The "Using Oracle9iAS Containers for J2EE" get start documentation only explained how to deploy J2ee application. What about the web application without EJB jar file? Anybody knows how to do that. Please let me know.
Thanks in advance.

Though you don't have ejbs, you can still use the ear file format. This would be most convenient way of deploying.
Use of a tool like Ant is recommended if you are not using JDeveloper.
Also, you can findinfo on deploying using a exploded directory
http://otn.oracle.com/docs/tech/java/oc4j/htdocs/getstart.htm#1027810
But recommed having ear file as it is convenient. If you want to see an example of use of Ant and deploying using ear file
check out one of the recently posted how-tos E.g. http://otn.oracle.com/tech/java/oc4j/htdocs/how-to-servlet-events.html

Unable to deploy Web App in Exploded format

Using WLS 6.1 sp2, I am unable to deploy a web application successfully using the
web app "ora" from http://www.thejspbook.com/examples.jspbook.zip. I've moved
the /ora directory under the /WEB-INF/applications directory.
The error I am getting is:
java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException:
Distributed Management [1 exceptions]
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:543)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
     at $Proxy18.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Distributed update exception
- remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
- actionName: addDeployment
- params: [Ljava.lang.Object;@10c03e
- signature: [Ljava.lang.String;@3d4a20
Distributed update exception
- remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
     at java.lang.String.substring(String.java:1525)
     at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:476)
     at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:232)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3415)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3384)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
     at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:815)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy34.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
     at $Proxy18.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.j2ee.DeploymentException: Could not load ora - with nested exception:
[java.lang.StringIndexOutOfBoundsException: String index out of range: -1]
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:431)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy34.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.--------------- nested within: ------------------
weblogic.management.console.utils.SetException: An error occurred while updating
Targets-Server on Proxy for efs-developer3:Application=ora,Name=ora,Type=WebAppComponent
- with nested exception:
[java.lang.reflect.InvocationTargetException - with target exception:
[weblogic.management.DistributedManagementException: Distributed Management [1
exceptions]]]
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help is appreciated.
Thanks,
Dennis

you are probably using a older version of 6.1. please use the latest service pack. Service Packs are mostly bug fix releases and they are safe to be upgraded even on production systems. Please note - we always recommend using the latest service pack
http://www.sun.com/download/products.xml?id=47d5d3eb

Re: Exploded directory format in an EAR

          I am now trying to deploy the ear file in v6.1 sp2. Has anyone managed to deploy
          an ear where util / third party classes are stored in a lib directory of the ear
          and referenced in EJB-jar manifest.mf files using the classpath header?
          ie as documented in bea weblogic server bible on page 614/615
          EntApp/
          accountEJB.jar
          accountManager.war
          /lib/
          xerces.jar
          xalan.jar
          log4j.jar
          /META-INF/
          application.xml
          "erik" <[email protected]> wrote:
          >
          >This is hearsay but I was recommended to use v 6.1 SP 2.
          >/erik
          >
          >"Ivan" <[email protected]> wrote:
          >>
          >>I have a problem wrapping up an exploded directory format application
          >>into an ear
          >>file running weblogic 6.0sp2 on winnt 4. One of the things I would like
          >>to do
          >>is load a config file from a helper class without specifying a path.
          >>
          >>
          >>EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar
          >>statementwebapp.war
          >>META-INF/application.xml lib/log4j.jar (and other third party jar files
          >>crimson.jar,
          >>jaxp.jar etc.)
          >>
          >>The third party jar files have been manually unjar'ed and re-jar'ed
          >without
          >>compression
          >>(after reading that a suggestion to someone else).
          >>
          >>WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
          >>- servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds
          >>- tag library
          >>descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
          >
          >>
          >>Some of the helper classes make use of configuration files (for example
          >>I have
          >>a Logger class that uses Log4j). Here is how I would like to access
          >the
          >>config
          >>file
          >>
          >>... private static final String config = "config.properties" ; PropertyConfigurator.configure(
          >>config ) ; ...
          >>
          >>I have tried putting the config.properties file in the WEB-INF/classes
          >>directory
          >>and in the WEB-INF directory, however they don't seem to be found by
          >>the class
          >>loader.
          >>
          >>EJB statement.jar contains an ejb with the following: uk...business.statement...
          >>- Statement ejb classes with ejbc generated stub and skeleton classes
          >>uk...util
          >>- Several Helper classes
          >>
          >>One such helper is Logger for which the Log4j jar file is needed. I
          >deploy
          >>the
          >>statement.jar file in the ear (as listed above). Weblogic throws an
          >error
          >>message
          >>saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
          >>org/apache/log4j/Category ie it cannot find the log4j package which
          >is
          >>referenced
          >>in the Class-Path header of the manifest.mf file and located in the
          >ear
          >>file under
          >>the lib directory.
          >>
          >>The manifest.mf file contains a line with the following: Class-Path:
          >>lib/log4j.jar
          >>lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise
          >>classloader
          >>to pick up the log4j.jar and xml parsing classes (ref. weblogic server
          >>bible chap
          >>18) without needing to be referenced in the weblogic start up class
          >path.
          >>
          >>
          >>Can manifest class-path references be used like this in weblogic 6.0?
          >>Where should
          >>I put the application properties files in the war and jar files?
          >>
          >>Clarification much appreciated. Ivan.
          >>
          >>PS: I had this application working in exploded directory format with
          >>the jar files
          >>in the system classpath and the properties file locations hardcoded
          >in
          >>the class
          >>files. (not ideal for a clustered production environment!)
          >>
          >


          This is hearsay again.
          These people did as you did no compression etc. they were able to put the application's
          utility classes in a lib but not the third party jars. They suspected that the
          ear where to big to deploy so they put all thirdparty jars in the system classpath
          and then the internal utility classes were loaded by using CLASSPATH in the manifest
          file.
          I gave up because I could deploy everything except servlets and I went back to
          exploded deployment. That bloody EAR thing took to much time.
          If you succeed in everything including warfiles with JSPs and servlets (those
          I was talking about only had EJBs)
          let me know.
          I also had a peculiar problem with EARs that a cascading stylesheet was not found
          in the ear but it worked in an exploded it worked fine
          Otherwise I must recommend Orion, which I had up and running in a matter of days
          when ported from WLS 5.1.
          Good luck.
          "Ivan" <[email protected]> wrote:
          >
          >I am now trying to deploy the ear file in v6.1 sp2. Has anyone managed
          >to deploy
          >an ear where util / third party classes are stored in a lib directory
          >of the ear
          >and referenced in EJB-jar manifest.mf files using the classpath header?
          >
          >ie as documented in bea weblogic server bible on page 614/615
          >EntApp/
          > accountEJB.jar
          > accountManager.war
          > /lib/
          > xerces.jar
          > xalan.jar
          > log4j.jar
          > /META-INF/
          > application.xml
          >
          >"erik" <[email protected]> wrote:
          >>
          >>This is hearsay but I was recommended to use v 6.1 SP 2.
          >>/erik
          >>
          >>"Ivan" <[email protected]> wrote:
          >>>
          >>>I have a problem wrapping up an exploded directory format application
          >>>into an ear
          >>>file running weblogic 6.0sp2 on winnt 4. One of the things I would
          >like
          >>>to do
          >>>is load a config file from a helper class without specifying a path.
          >>>
          >>>
          >>>EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar
          >>>statementwebapp.war
          >>>META-INF/application.xml lib/log4j.jar (and other third party jar files
          >>>crimson.jar,
          >>>jaxp.jar etc.)
          >>>
          >>>The third party jar files have been manually unjar'ed and re-jar'ed
          >>without
          >>>compression
          >>>(after reading that a suggestion to someone else).
          >>>
          >>>WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
          >>>- servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds
          >>>- tag library
          >>>descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
          >>
          >>>
          >>>Some of the helper classes make use of configuration files (for example
          >>>I have
          >>>a Logger class that uses Log4j). Here is how I would like to access
          >>the
          >>>config
          >>>file
          >>>
          >>>... private static final String config = "config.properties" ; PropertyConfigurator.configure(
          >>>config ) ; ...
          >>>
          >>>I have tried putting the config.properties file in the WEB-INF/classes
          >>>directory
          >>>and in the WEB-INF directory, however they don't seem to be found by
          >>>the class
          >>>loader.
          >>>
          >>>EJB statement.jar contains an ejb with the following: uk...business.statement...
          >>>- Statement ejb classes with ejbc generated stub and skeleton classes
          >>>uk...util
          >>>- Several Helper classes
          >>>
          >>>One such helper is Logger for which the Log4j jar file is needed. I
          >>deploy
          >>>the
          >>>statement.jar file in the ear (as listed above). Weblogic throws an
          >>error
          >>>message
          >>>saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
          >>>org/apache/log4j/Category ie it cannot find the log4j package which
          >>is
          >>>referenced
          >>>in the Class-Path header of the manifest.mf file and located in the
          >>ear
          >>>file under
          >>>the lib directory.
          >>>
          >>>The manifest.mf file contains a line with the following: Class-Path:
          >>>lib/log4j.jar
          >>>lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise
          >>>classloader
          >>>to pick up the log4j.jar and xml parsing classes (ref. weblogic server
          >>>bible chap
          >>>18) without needing to be referenced in the weblogic start up class
          >>path.
          >>>
          >>>
          >>>Can manifest class-path references be used like this in weblogic 6.0?
          >>>Where should
          >>>I put the application properties files in the war and jar files?
          >>>
          >>>Clarification much appreciated. Ivan.
          >>>
          >>>PS: I had this application working in exploded directory format with
          >>>the jar files
          >>>in the system classpath and the properties file locations hardcoded
          >>in
          >>>the class
          >>>files. (not ideal for a clustered production environment!)
          >>>
          >>
          >

Exploded directory format in an EAR

          I have a problem wrapping up an exploded directory format application into an ear
          file running weblogic 6.0sp2 on winnt 4. One of the things I would like to do
          is load a config file from a helper class without specifying a path.
          EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar statementwebapp.war
          META-INF/application.xml lib/log4j.jar (and other third party jar files crimson.jar,
          jaxp.jar etc.)
          The third party jar files have been manually unjar'ed and re-jar'ed without compression
          (after reading that a suggestion to someone else).
          WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
          - servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds - tag library
          descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
          Some of the helper classes make use of configuration files (for example I have
          a Logger class that uses Log4j). Here is how I would like to access the config
          file
          .. private static final String config = "config.properties" ; PropertyConfigurator.configure(
          config ) ; ...
          I have tried putting the config.properties file in the WEB-INF/classes directory
          and in the WEB-INF directory, however they don't seem to be found by the class
          loader.
          EJB statement.jar contains an ejb with the following: uk...business.statement...
          - Statement ejb classes with ejbc generated stub and skeleton classes uk...util
          - Several Helper classes
          One such helper is Logger for which the Log4j jar file is needed. I deploy the
          statement.jar file in the ear (as listed above). Weblogic throws an error message
          saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
          org/apache/log4j/Category ie it cannot find the log4j package which is referenced
          in the Class-Path header of the manifest.mf file and located in the ear file under
          the lib directory.
          The manifest.mf file contains a line with the following: Class-Path: lib/log4j.jar
          lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise classloader
          to pick up the log4j.jar and xml parsing classes (ref. weblogic server bible chap
          18) without needing to be referenced in the weblogic start up class path.
          Can manifest class-path references be used like this in weblogic 6.0? Where should
          I put the application properties files in the war and jar files?
          Clarification much appreciated. Ivan.
          PS: I had this application working in exploded directory format with the jar files
          in the system classpath and the properties file locations hardcoded in the class
          files. (not ideal for a clustered production environment!)


          This is hearsay but I was recommended to use v 6.1 SP 2.
          /erik
          "Ivan" <[email protected]> wrote:
          >
          >I have a problem wrapping up an exploded directory format application
          >into an ear
          >file running weblogic 6.0sp2 on winnt 4. One of the things I would like
          >to do
          >is load a config file from a helper class without specifying a path.
          >
          >
          >EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar
          >statementwebapp.war
          >META-INF/application.xml lib/log4j.jar (and other third party jar files
          >crimson.jar,
          >jaxp.jar etc.)
          >
          >The third party jar files have been manually unjar'ed and re-jar'ed without
          >compression
          >(after reading that a suggestion to someone else).
          >
          >WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
          >- servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds
          >- tag library
          >descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
          >
          >Some of the helper classes make use of configuration files (for example
          >I have
          >a Logger class that uses Log4j). Here is how I would like to access the
          >config
          >file
          >
          >... private static final String config = "config.properties" ; PropertyConfigurator.configure(
          >config ) ; ...
          >
          >I have tried putting the config.properties file in the WEB-INF/classes
          >directory
          >and in the WEB-INF directory, however they don't seem to be found by
          >the class
          >loader.
          >
          >EJB statement.jar contains an ejb with the following: uk...business.statement...
          >- Statement ejb classes with ejbc generated stub and skeleton classes
          >uk...util
          >- Several Helper classes
          >
          >One such helper is Logger for which the Log4j jar file is needed. I deploy
          >the
          >statement.jar file in the ear (as listed above). Weblogic throws an error
          >message
          >saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
          >org/apache/log4j/Category ie it cannot find the log4j package which is
          >referenced
          >in the Class-Path header of the manifest.mf file and located in the ear
          >file under
          >the lib directory.
          >
          >The manifest.mf file contains a line with the following: Class-Path:
          >lib/log4j.jar
          >lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise
          >classloader
          >to pick up the log4j.jar and xml parsing classes (ref. weblogic server
          >bible chap
          >18) without needing to be referenced in the weblogic start up class path.
          >
          >
          >Can manifest class-path references be used like this in weblogic 6.0?
          >Where should
          >I put the application properties files in the war and jar files?
          >
          >Clarification much appreciated. Ivan.
          >
          >PS: I had this application working in exploded directory format with
          >the jar files
          >in the system classpath and the properties file locations hardcoded in
          >the class
          >files. (not ideal for a clustered production environment!)
          >

Deploying exploded ear file

Hi,
I have exploded an ear file, and I am trying to deploy it in weblogic 7.0.
This ear has several jars and war files.
However, when I deploy it
(Access is denied) at java.io.FileInputStream.open(Native Method) -- while trying
to open the war file.
I have followed the same steps as mentioned in the bea docs , by exploding all
the individual wars, jars, inside the ear ..
Any help is appreciated..
Thanks in advance.

I believe manifest class-paths should work fine for exploded EARs as
well. Don't you want 'common' rather than '../common' in your
class-path entry?
-- Rob
Eric Ma wrote:
Rob:
Yes, I was talking about the MANIFEST.MF Class-Path entries. My exploded ear
looks like (under mydomain/applications)
app
--META-INF
----application.xml
--ejb
----com
------abc.class
----META-INF
------MANIFEST.MF
------ejb-jar.xml
--common
----com
------xyz.class
--web
----jsp
----WEB-INF
------web.xml
------lib
--------struts.jar
The MANIFEST.MF file has
Class-Path: ../common/
I read at http://e-docs.bea.com/wls/docs61/ejb/EJB_deployover.html#1074087 that
Class-Path is only supported in the .ear format. Is it true?
Rob Woollen <[email protected]> wrote:
Are you talking about manifest class-path entries? If so, can you show
me what your exploded EAR looks like? (ie its layout and your
class-path entries.)

Error coming while deploying portal EAR file into the weblogic Portal 8.1..

HI Guys,
When I deploy the latest PORTAL EAR file into the BEA portal environment we
receive a number of these errors:
####<Feb 27, 2008 4:36:14 PM PST> <Warning> <netuix> <dev147> <portalName>
<ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>>
<BEA-423171> <
java.lang.Throwable: New portlet file
[portlet/portletname.portlet] and existing portlet
file null have the same definition label
Lebel Name. Will not create a definition for
portlet file [portlet/portletname.portlet].
at
com.bea.netuix.application.manager.persistence.jdbc.PortletDefinitionDelegate.c
reatePortletDefinitionInternal(PortletDefinitionDelegate.java:1442)
at
com.bea.netuix.application.manager.persistence.jdbc.PortletDefinitionDelegate.c
reatePortletDefinition(PortletDefinitionDelegate.java:906)
at
com.bea.netuix.application.manager.persistence.jdbc.PortletDefinitionManagerImp
l.createPortletDefinition(PortletDefinitionManagerImpl.java:520)
at
com.bea.netuix.application.manager.persistence.jdbc.PortletDefinitionManager_41
0kn4_EOImpl.createPortletDefinition
(PortletDefinitionManager_410kn4_EOImpl.java:476)
at
com.bea.netuix.servlets.repository.PortletFilePersistenceManager.create
(PortletFilePersistenceManager.java:189)
at
com.bea.netuix.servlets.repository.PortletFilePersistenceManager.createUpdatePo
rtletDefinitions(PortletFilePersistenceManager.java:304)
at com.bea.netuix.servlets.repository.PortletFilePersistenceManager.sync
(PortletFilePersistenceManager.java:609)
at
com.bea.netuix.servlets.repository.AbstractFilePersistenceManager$Sync.run
(AbstractFilePersistenceManager.java:187)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs
(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs
(SecurityManager.java:147)
at
com.bea.netuix.servlets.repository.AbstractFilePersistenceManager.startup
(AbstractFilePersistenceManager.java:86)
at com.bea.netuix.servlets.manager.PortalServlet.initFilePoller
(PortalServlet.java:511)
at com.bea.netuix.servlets.manager.PortalServlet.init
(PortalServlet.java:242)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run
(ServletStubImpl.java:1099)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs
(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs
(SecurityManager.java:121)
at weblogic.servlet.internal.ServletStubImpl.createServlet
(ServletStubImpl.java:975)
at weblogic.servlet.internal.ServletStubImpl.createInstances
(ServletStubImpl.java:954)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet
(ServletStubImpl.java:893)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet
(WebAppServletContext.java:3456)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets
(WebAppServletContext.java:3413)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets
(WebAppServletContext.java:3399)
at weblogic.servlet.internal.WebAppServletContext.preloadResources
(WebAppServletContext.java:3382)
at weblogic.servlet.internal.WebAppServletContext.setStarted
(WebAppServletContext.java:6262)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:892)
at weblogic.j2ee.J2EEApplicationContainer.start
(J2EEApplicationContainer.java:2181)
at weblogic.j2ee.J2EEApplicationContainer.activate
(J2EEApplicationContainer.java:2222)
at
weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateCo
ntainer(SlaveDeployer.java:2521)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit
(SlaveDeployer.java:2439)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit
(SlaveDeployer.java:2156)
at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit
(SlaveDeployer.java:2255)
at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare
(SlaveDeployer.java:2150)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare
(SlaveDeployer.java:2402)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask
(SlaveDeployer.java:884)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta
(SlaveDeployer.java:592)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate
(SlaveDeployer.java:501)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute
(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Thanks in advance...
Regards,
Sandeep K

Before deploying the app, you could check database table PF_PORTLET_DEFINITION for any entries there which might conflict with yours.
--Stefan

Deploying BEA Portal App in Managed Server problems....

Hello,
I have a BEA portal application (exploded EAR) that I want to deploy in a managed server. I first created a regular portal domain (8.1 SP4). I then created a managed server via the console. When I went to deploy my portal application (in the console), I received an error indicating that the application was a Split Development Directory and that I would have to run the wlpackage Ant task against the application first. I ran the wlpackage ant task and it seemingly worked.
I then used the wldeploy Ant task to deploy it in the managed server but got an error indicating that it could not find a JNDI name from one of the data sources. I went back to the console and targeted/deployed all of the default Connection Pools & Data Sources to the managed server thinking that was the reason the deploy failed.
When I ran the wldeploy again I got the following error:
Module: content.jar Error: Exception activating module: EJBModule(content.jar, status=PREPARED)
Unable to deploy EJB: ValueBean from content.jar
java.sql.SQLException: javax.naming.NameNotFoundException: While trying to lookup 'portalFrameworkPool; contentDataSource;weblogic.jdbc.jts.commercialPool' didn't find subcontext 'portalFrameworkPool;contentDataSource;weblogic' Resolved ; remaining name 'portalFrameworkPool;contentDataSource;weblogic/jdbc/jts/commercialPool'
Has anyone run into this? Am I not suppose to deploy a portal application in a managed server?
Any help would be greatly appreciated.
Thanks - Peter Len

Problem solved.......
After targeting all the data sources and poolers to the managed server, I restarted the main domain but did not restart the managed server. After restarting the managed server all was well.
Thanks - Peter

Deploying jars within a single (exploded) ear

Our project currently uses 8.1 SP3 with split deployment structure.
Currently the project is split into multiple ears deployed on a single (managed) server. It is my understanding that calls made across ear's even on the same server (jvm) need to be marshalled and unmarshalled using pass by value.
We are trying to consolidate all our EJBs and Web apps into a single .ear so that we can take advantage of call-by-reference. We also have a requirement of being able to deploy "groups" of EJBs (within a single jar) and/or a web app. Deploying a single ear for the entire project would be one extreme, as it would be painful to deploy individual modules within the ear. On the other hand, using an exploded ear would be too "granular" a way of deploying our changes (we have many EJBs, etc.).
Is it possible to deploy an exploded ear consisting of jar and war files ? I am in the process of trying this and was looking for feedback. The idea is of being able to deploy parts of the app, such as a .jar or a .war file. Can wlpackage create an exploded ear using .jar and .war files instead of modules consisting of .java/.jsp, etc. files? Thanks for your help!

There is a classpath issue. Normally ejbs are loaded on top of the ears classpath, so whenever you redeploy them, you have to redeploy the webapps, too. In 8.1 you can build your custom class loader hierarchy. Take a look at http://e-docs.bea.com/wls/docs81/programming/classloading.html#1065667
-Kai

Any tool to help deploy with Exploded Directory Format

I read through the "Oracle9iAS Containers for J2EE" Getting Started document and saw the section on "Deploying with Exploded Directory Format". I would like to take the Petstore1.1.2 code and put it in exploded directory format so that OC4J can easily pick up changes to servlets and EJBs. But the codebase for Petstore is complicated enough that I would like to have a tool (possibly ant) that can automate the process of going from either the source directory or even ear file to the "exploded directory format".
Are there any tools available to help automate this process??

Never mind. This stuff is a lot simpler than I initially thought. There is no need for a tool because it is easy enough to do by hand.
Sorry for bothering everyone

NetWeaver exploded ear deployment

Hi
I'm depolying my application on the NetWeaver App Server 7.1 through the script files (DeploymentManager etc.) - question is this:
Is it possible to deploy an exploded ear, if so what entries should be putted into a deploy-manager-config.xml file?
Regards
P

This is not possible.
Regards,
Benny

Deployment question: exploded EAR application

I've been having some EJB connection problems when I try to deploy an exploded
EAR app.
Here is some background info.
Running WL 6.1 SP2 on Solaris 8
I have the following directory structure for my EAR app which
contains my EJB's and WEB app
/deployment/config/mydomain
/myApp
/META-INF/application.xml
/classes
/ejb
/webApp
/WEB-INF/web.xml
/weblogic.xml
The application.xml file contains all the descriptors for each EJB jar file in
the ejb directory as well as the deployment descriptor to the webApp.
In the Weblogic console I can create a new application called myApp and point
it to the above directory (/deployment/config/mydomain/myApp) and it will deploy
all the EJB's and the web app and I can display the login page to my webApp but
as soon as I try to login and the webApp has to connect to a LOGIN ejb it fails
because it cannot connect to the EJB.
If I deploy each ejb jar file separately into a running weblogic environement
I can login which means I can successfully connect to the EJB's.
Has anyone done something similar to this. I'm following the BANK example that
came with WL6.1, but I have not been successful and wondering if anyone can shed
some light here for me.
If you want to see my application.xml or web.xml let me know and I'll post it
up.
Thanks
Ray

Make sure your EJB's have a deployment target. I noticed that when I
deployed an exploded ear file, the EJB's weren't deployed to the server,
they were present in the console, but not deployed.
-Brett Schmoll
"Ray" <[email protected]> wrote in message
news:3c374e60$[email protected]..
>
I've been having some EJB connection problems when I try to deploy anexploded
EAR app.
Here is some background info.
Running WL 6.1 SP2 on Solaris 8
I have the following directory structure for my EAR app which
contains my EJB's and WEB app
/deployment/config/mydomain
/myApp
/META-INF/application.xml
/classes
/ejb
/webApp
/WEB-INF/web.xml
/weblogic.xml
The application.xml file contains all the descriptors for each EJB jarfile in
the ejb directory as well as the deployment descriptor to the webApp.
In the Weblogic console I can create a new application called myApp andpoint
it to the above directory (/deployment/config/mydomain/myApp) and it willdeploy
all the EJB's and the web app and I can display the login page to mywebApp but
as soon as I try to login and the webApp has to connect to a LOGIN ejb itfails
because it cannot connect to the EJB.
If I deploy each ejb jar file separately into a running weblogicenvironement
I can login which means I can successfully connect to the EJB's.
Has anyone done something similar to this. I'm following the BANK examplethat
came with WL6.1, but I have not been successful and wondering if anyonecan shed
some light here for me.
If you want to see my application.xml or web.xml let me know and I'll postit
up.
Thanks
Ray

Exploded EAR deployment supported?

Hi,
I am currently developing with the MyEclipse IDE. Does Sun Java Studio Enterprise 8.1 support exploded deployment of EARs, and can it 'hot deploy' changes into the running Application Server?
Thank You

Hi.
SJSE 8.1 doesn't support exploded deployment of EAR projects. It currently supports exploded deployment of WAR projects.
I know that folks have extended NetBeans to support exploded EAR deployment in NB 6.0...
You can find out more about that in this blog entry and screencast:
http://blogs.sun.com/vkraemer/entry/new_glassfish_integration_feature_directory
http://serverplugins.netbeans.org/screencasts/pfsc1.html
Can you clarify what you mean by 'hot deploy'? Different folks have different definitions of this phrase... I think SJSE 8.1 does 'hot deploy' as I understand it... but my understanding may not match your vision of this feature...
vbk

Deployment (Ejb and third party jars with portal app)

My problem is that I'm trying to set up the development env for a portal project.
I have an ejb and a third party jar in my portal app. My portlets have some java
classes associated with them. The ejb needs to reference(instantiate) the java
classes in the portlets.
Right now the only way I can get it to work is to put the ejb, third party jar
and the portlet classes(jarred up) into the classpath of the server.
I think there should be a way to deploy these things without putting them in the
class path. I've read all the manual sections about deploying.
Can anyone help me with this. It would be much appreciated.
Thanks
Rob Castle
Principal
NuWave Solutions, LLC
12510 Prosperity Drive
Suite 300
Silver Spring, MD 20904
office phone: (301) 625-3000 ext. 2003
mobile phone: (410) 340-5529
email: [email protected]
website: www.nuwavesolutions.com

On 01/10/2002 06:40 AM, Rob Castle wrote:
My problem is that I'm trying to set up the development env for a portal project.
I have an ejb and a third party jar in my portal app. My portlets have some java
classes associated with them. The ejb needs to reference(instantiate) the java
classes in the portlets.
Right now the only way I can get it to work is to put the ejb, third party jar
and the portlet classes(jarred up) into the classpath of the server.
I think there should be a way to deploy these things without putting them in the
class path. I've read all the manual sections about deploying.
Refer to the portal deployment guide
(http://edocs.bea.com/wlp/docs40/deploygd/index.htm). Also refer to
http://edocs.bea.com/wls/docs61/ejb/deploy.html for more general
information on deployment of ejbs.
Regards,
Subbu

Deploying Portal App in exploded EAR format

Similar Messages

Maybe you are looking for