Deploy huge J2EE apps

What are the steps which can be performed to deploy a
huge JEE2 application to server (500 Ejbs , 1000 Jsps). EAR size is 50MB+
It is imporntant that application deploy very fast and
once open for access not to wait for compliation of jsps
and servelts for the first hit/access

We currently deploy 350+ CMP Beans, and up to 20 different JARs containing various Stateless Session bean services. The time to deploy for the entity beans is rediculous. It takes almost 1.5 hours! I have raised a TAR on this and the team have suggested some settings but all to no avail. The EAR containing all this is being deployed on 9.0.4.1, running on HP-US 11i. We have the javac process running out of process with a heap size of > 1G.
This has been a long standing problem. The app is in production for nearly 2 years now. We started with 9.0.3, and we were told that by upgrading to 9.0.4.1 we would improve our deploy times....... I guess we're still waiting for that improvement!
If you get your app deploying fast, share the knowledge please.

Similar Messages

EJB Deployment in J2EE Apps Server

Hi,
Can any one please help me in deploying EJB in J2EE Apps server?I have installed J2EE Apps Server 9 in my machine.Can any one please suggest me a document regarding EJB deployment in J2EE apps server or help me regarding this?
Thanks in advance,
Aravindhan.C

Go to https://j2ee-sdk.dev.java.net/ and checkout "Methods of deploying applications" under the recent articles section; The tutorial link present in this page (under the references section) will also be useful. The samples bundle has reference samples which will also be useful

HowTo: deploy an j2ee app using "/" as context root on iAS 6.5

Hi all iAS expert
It is highly appreciated one can teach me how to get around below problem
l deployed an app using "/" as context root. But the iAS could respond to any HTTP request.
However, as l changed the context root to sth other than root. iAS responded properly.
Can someone help me get around this problem ?
thank you a lot
fox

I deployed the same EJB on WLS 6.1+sp3 and WLS 7.0.
These both work. Looks like there is some problem with WLS6.0+sp2. I have opened
a case with BEA customer support.
--Latha

Guide to deploy pure-j2ee app to WAS 640?

I know I found this guide somewhere on the SDN. Can someone please remind me where it is?
Thanks very much,
Jake

Hi Jake,
I don't know which doc you have in mind, but see http://help.sap.com/saphelp_nw04/helpdata/en/13/a3bb3eff62847ae10000000a114084/frameset.htm - development manual; within this, you will find the section "Deployment: Putting It All Together".
Hope it helps
Detlev
PS: As far as I know, on SDN a PDF Deployment Manual only for 6.20 exists.

Deploying J2EE Apps in WL9.0 using Maven2

Hi All,
Has any one using Maven2.0 to Deploy the J2EE Apps on WL9.0.
I don't think medrac sample app is deployed using Maven. If any of you tried it could you pls post the maven scripts..
Thanks
Kumar

Hi,
Maven was originally started as an attempt to simplify the build processes in the Jakarta Turbine project. There were several projects each with their own Ant build files that were all slightly different and JARs were checked into CVS.
What resulted is a tool that can now be used for building and managing any Java-based project. We hope that we have created something that will make the day-to-day work of Java developers easier and generally help with the comprehension of any Java-based project.
System requirements
JDK     1.4 or above (this is to execute Maven - it still allows you to build against 1.3 and prior JDK's)
Memory     No minimum requirement
Disk     No minimum requirement. Approximately 100MB will be used for your local repository, however this will vary depending on usage and can be removed and redownloaded at any time.
Operating System     No minimum requirement. On Windows, Windows NT and above or Cygwin is required for the startup scripts. Tested on Windows XP, Fedora Core and Mac OS X.
Regards
Prasanna Yalam

How To Install J2EE app to ColdFusion's Tomcat Server

Our client has purchased IBM Analytics, that they want to run with the ColdFusion servers. IBM has given over the EAR files to deploy on Tomcat. But, ColdFusion uses a highly modified Tomcat. How would someone deploy another J2EE app in this scenario, without installing another server?

Hi,
Thank you for your post. Please refer to http://help.adobe.com/en_US/ColdFusion/10.0/Installing/WSc3ff6d0ea77859461172e0811cdec18c2 8-7fda.html for J2EE deployment.
Regards,
Anit Kumar

Problem with deploying j2ee app to weblogic server

I would like to deploy a j2ee application, that was successfully deploy on the iAS version 10.1.3, on to the web logic server.
It deploy successfully, but when I try to run it, I get a 404 error. I can see in the web center, the application is up.
What should I look for to trouble shoot this?
Thanks.

1. Check the context root of the webapplication to make sure you are accessing that webresources like html or jsp file with correct context root.
2. If you have a single server domain of WLS, then check access.log file located at: user_projects\domains\yourDomain\servers\yourServer\logs. This file should should show the resource you are accessing and the response status.
3. From Weblogic Console, after the application is Deployed, make sure that your application is in Active Mode. From Weblogic Console, under Deployments tab, select your app, and see that it is Active. If it is in Prepared state, then click Lock and Edit, and select your App, and click on Start button.
4. Check for CASE Sensitivity also for the resource you are accessing and context-root value etc for ex: like any JSPs or htmls.
Ravi Jegga

Building and deploying J2EE apps ? Now there is a solution for production root cause analysis.

Is your organization building and deploying J2EE apps? If so, Halo
can help solve one of the toughest issues facing enterprises today:
Finding the root cause of software faults.
"Halo monitors, pinpoints, reports on and provides a source-code level
root cause of software faults in deployed J2EE apps. Halo is unique
because it's the only technology that can give you a root cause
diagnosis in a fully deployed, live production application. Halo has
such low performance overhead that customers deploy their final,
production versions of their applications with Halo enabled.
Used with Web Application Servers like WebLogic, Halo helps ensure
that deployed code is reliable and able to be quickly fixed if
problems turn up. Most important, because Halo is an "always on"
technology, you get all the information you need to rapidly solve a
problem on the first fault. Problem replication and bug reports are
obsolete with Halo
"Halo has a unique ability to provide a root cause diagonosis and
understanding
of software problems in production systems, without needing to
replicate the
issue.
Test on WebLogic proved that Halo runs with extremely low overhead and
is suitable for use in deployed production systems"
Andrew Sliwkowski, Software Engineer
BEA Systems, Inc.
The key is Halo's high performance, low overhead TraceBack
instrumentation technology. Based on technology out of MIT and proven
in the field, TraceBack enables you to instrument JARs, EARs and WARs
within minutes, without touching source code.
Halo is useful throughout the entire application life cycle, from
development through test, beta and deployment.
If you have interest in learning more visit our website at
www.incer.com or email me directly at [email protected] (Rick Martin)

I have two questions. We have just started developing apps using jdev9i, 9iAS v2 and are new to the j2ee environment so my questions may be very easy ones.
Question 1: We have set up Oracle pooling connection to our databases. We have a development, test and production database. When I deploy my application, it includes the connections. This is preventing me from moving the EAR files from dev to test to prod without modification and re deploying to my EAR file. Is there a way or a place that I can put my database connections that will not be included in my EAR files and the application still find them?datasources.xml is where the info regradings connection to databases is licated. If you're using 9iAS
you can use EM to create datasource entry at the global level. In OC4J standalone you could use admin.jar
or edit the file. Check out the standalone user's guide at http://otn.oracle.com/tech/java/oc4j/pdf/oc4j_so_usersguide_r2.pdf.
Also, you will othe OC4J docs on OTN.
Question 2: I have a stand alone oc4j set up for our developers to use while testing their applications. The applications include libraries supplied in jdev such as xml parser v2. I do not want to deploy those lib files with the app because I will have to redeploy all my apps if I upgrade jdev. I just want to be able to upgrade the libraries, test the apps and not have to redeploy everything. I can do this by coping the jdev lib to 9iAS but I can't seem to find the right place to put the lib for the stand alone oc4j instance. You can use the library tag within application.xml for server wide availability. Check out the article
http://otn.oracle.com/oramag/oracle/02-sep/o52oc4j_2.html specifically class loading in OC4J section
Any help would be greatly appreciated. Thanks in advance.

Concurrent Deployment of Multiple Releases of a J2EE App to WLS 7.0

Is it possible to concurrently deploy multiple releases of the same
J2EE app to WLS? If so, what was the process and your experience with
it?

Is it possible to concurrently deploy multiple releases of the same
J2EE app to WLS? If so, what was the process and your experience with
it?

Deployment of Flex app to web and app server

Hi
I'm working on putting a Flex front-end on an existing J2EE
app which gets deployed as an ear file. The architecture consists
of web server, app server and database server. Is the following
approach to deployment possible / recommended?
My Flex app will be deployed to the web server. The J2EE ear
file will be deployed to the app server (Weblogic). BlazeDS will be
bundled within the ear file as a war file. Remote Objects will be
configured in my BlazeDS configuration files to enable me to access
the code in my J2EE app. In the compiler options of my Flex app,
I'll be setting the server root folder and server root URL to point
to the BlazeDS war file on my app server.
At present I'm at the stage where I can run my Flex app
directly from Flex builder on my development PC and it's able to
connect tto the J2EE app, which is running on the app server
(Weblogic) also on my development PC. I can't find documentation
explaining how to extend this to work on a multi-tier architecture.
Thanks
David

Hi,
I replied to your post in FDS forum. Please visit the URL
below for the response.
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=583&threadid=1373523
Hope this helps.

J2EE app server not able to compile JSP

Hi,
I have just installed J2EE app server and am trying to deploy a JSP. The following error is generated. can anyone help me please.
Thank you,
Deepika.
org.apache.jasper.JasperException: Unable to compile class for JSP
No Java compiler was found to compile the generated source for the JSP.
This can usually be solved by copying manually $JAVA_HOME/lib/tools.jar from the JDK
to the common/lib directory of the Tomcat server, followed by a Tomcat restart.
If using an alternate Java compiler, please check its installation and access path.
     org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:127)
     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:348)
     org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:424)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:464)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:448)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:551)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:300)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:324)
     org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:284)
     java.security.AccessController.doPrivileged(Native Method)
     javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:306)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:200)

This is a known issue.
Here's an explanation of the behaviour you are seeing:
The misleading error message is printed only in the case where a javac
compilation error line number cannot be mapped back to a line number
in the JSP source code.
The internal representation of a JSP element ("JSP node") in the JSP compiler
contains the following info:
- The begin line number of the JSP element in the JSP page
- The begin and end line numbers ("range") of the Java code that was
generated for the JSP element
When attempting to map a javac error line number back to the JSP
source line, we determine the range into which the javac error line
number falls, and retrieve the JSP source number of the JSP element
associated with that range.
However, in some cases, it is impossible to trace a javac error line
number back to the JSP element that caused the error. For example,
consider the following scriptlet:
<%
String query = request.getParameter("query");
if(query != null) {
out.println(query);
} else {
out.println("(null)");
// } // <-- !Missing brace syntax error
%>
Since the JSP compiler wraps the generated code into a
try-catch-finally block, the above syntax error in the scriptlet
causes havoc with that try-catch-finally block, and results in 3 javac
errors:
<file>jsp.java:<line1>: 'catch' without 'try'
} catch (Throwable t) {
^
<file>jsp.java:<line2>: 'try' without 'catch' or 'finally'
try {
^
<file>jsp.java:<line3>: '}' expected
Notice that all of the above javac error numbers are outside the range
of the java line numbers corresponding to the scriptlet that caused the
error, and therefore cannot be mapped back to any line numbers in the
JSP page source.
AS 8.0 PE does not handle this case correctly, and prints out the
misleading error message (though the real error message can be found
in the server log).
Notice that this problem is going to be fixed in AS 8.1, so that if a
javac error line number cannot be mapped back to a JSP page line
number, the javac error is still returned to the client.
In AS 8.0 PE, you need to check your server log to find out why the compilation failed.
If you still have any problems, send me your JSP, and I will take a look at it.
Thanks,
Jan

How to run a background process in a J2EE App ?

Hi guys,
Here is the requirement which totally stumped me.
" The web app should have a feature like a background process or something like cron jobs.. which keeps on running in the background and at a particular time each day calls a method". User intervention is not an option.
Now had this been a stand alone app .. I could have done this using Threads.. but i cant possibly use threads in a J2EE app. Any pointers.. how I can go about realizing this
Thanks for your replies.
Cheers!

You could take the approach that SoulTech mentioned and spawn a new thread from the Servlet's init method. To have the servlet invoke this method with no intervention, you would need to set the following parameter in your servlet definition in your web.xml:
<servlet>
<servlet-name>MyStartupServlet</servlet-name>
<servlet-class>com.my.company.MyStartupServlet</servlet-class>
*<load-on-startup>1</load-on-startup>*
</servlet>When you deploy your application, the servlet will be loaded, and its init method will be called.
If your application is running in a servlet container, I believe you are allowed (by the specification) to spawn your own threads, but you should do so carefully. Since you're writing a scheduler and not some kind of worker threads that are messing with your database, I think you should be okay. Still, just to keep it clean you should add any clean-up logic you may need to your servlet's destroy method. I know that in an EJB container, spawning your own threads can definitely be a problem and the container makes no guarantees that they will function correctly. The J2SE Timer class could be used if you're not using EJB, but the Timer class doesn't have support for J2EE - that's at least part of what led to the introduction of the timer beans in J2EE 1.4. If you're already using EJB, especially EJB 3.0, then the timer service provides a convenient built-in mechanism to do exactly what you want.
There are always multiple ways to solve any problem...
Edited by: proflux on May 15, 2008 1:04 PM

J2EE App Servers

Hi
I am currently investigating the setup we'll need to develop java apps - we're looking to develop multi-tier applications using jsp,servlets and ejb's. We are however currently tied into using Microsoft IIS webservers. From what I can gather we therefore have no choice but to purchase an (expensive) J2EE App Server to handle the jsp, servlet and ejb's - like Borland's AppServer 4.5 both for development and deployment of our final application to our customers (assuming they want to host the application themselves).... Does anyone know of some less expensive options to handle this kind of Java development or can someone suggest an alternative architecture?
Many thanks.

As some has said before there is a free app server for J2EE based applications, and you can find it at:
http://www.jboss.org/
As for web server you can use the Tomcat which is also free.

Unclear Deployment Exception in App Server PE 9

Hello,
try to deploy a J2EE application EDMProjectEAR in Sun App Server PE9 with Netbeans 5.5 The application uses entity and session beans and JSF components. No JMS at all. The deployment process fails mention that some queue is not set correctly (according to my knowledge). The whole stack trace of deployment exception below. Any hints what can be the reason? Is that really related to JMS components?
Any support would be great.
Thanks!
Best regards, Maik
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [EDMProjectEAR] -- This ejb has no message destination refernce by the name queue
     at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:362)
     at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:327)
     at com.sun.enterprise.deployment.backend.AppDeployer.explodeArchive(AppDeployer.java:332)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:182)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:129)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
     at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
     at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
Caused by: java.lang.IllegalArgumentException: This ejb has no message destination refernce by the name queue
     at com.sun.enterprise.deployment.WebBundleDescriptor.getMessageDestinationReferenceByName(WebBundleDescriptor.java:796)
     at com.sun.enterprise.deployment.node.runtime.MessageDestinationRefNode.setElementValue(MessageDestinationRefNode.java:86)
     at com.sun.enterprise.deployment.node.SaxParserHandler.endElement(SaxParserHandler.java:408)
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
     at com.sun.org.apache.xerces.internal.impl.dtd.XMLNSDTDValidator.endNamespaceScope(XMLNSDTDValidator.java:260)
     at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:2059)
     at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:932)
     at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
     at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:279)
     at com.sun.enterprise.deployment.archivist.Archivist.readRuntimeDeploymentDescriptor(Archivist.java:514)
     at com.sun.enterprise.deployment.archivist.ApplicationArchivist.readRuntimeDeploymentDescriptor(ApplicationArchivist.java:387)
     at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:320)
     ... 11 more

Maik,
If this is still a problem, could you please post the descriptors from the EAR?
Are you using any annotations?
- Tim

Trouble deploying a J2EE application using the J2EE 6.20 Deploy Tool

I am having trouble deploying a J2EE application using the J2EE 6.20 Deploy Tool.
I successfully create the WAR/EAR files, I then select deploy and the deploy process gets to 100% before displaying an error message.
Can anybody help?
Please see Deploy Tool log entry:
01:39 - **********************************************************
05/01/17 10:19:16 - Applying user role management mappings.
05/01/17 10:19:16 - Start updating EAR-file...D:\SAP_J2EEngine6.20_Cluster\deploying\carmodeller\carmodeller.ear
05/01/17 10:19:27 - Temp files deleted...
05/01/17 10:19:27 - Ear-file updated successfully for 11375ms.
05/01/17 10:19:27 - Start deploying ...
05/01/17 10:20:15 - Ear-file uploaded to server for 47297ms.
05/01/17 10:21:47 - ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
                     com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
                          at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.deploy(ServletsAndJspImpl.java:482)
                          at com.inqmy.services.servlets_jsp.server.WebContainer.commitDeploy(WebContainer.java:256)
                          at com.inqmy.services.deploy.server.DeployServiceImpl.commit(DeployServiceImpl.java:2848)
                          at com.inqmy.services.deploy.server.DeployServiceImpl.deploy1(DeployServiceImpl.java:512)
                          at com.inqmy.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:140)
                          at com.inqmy.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:184)
                          at com.inqmy.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:157)
                          at com.inqmy.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:108)
                          at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
                          at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
                          at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
                          at java.security.AccessController.doPrivileged(Native Method)
                          at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:153)
05/01/17 10:21:47 - **********************************************************

Hi, it looks like the app has trouble starting up:
05/01/17 10:21:47 - ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
Did you have any errors on the compile of the code?
You also want to check if the app is deployed (if so you may want to remove it before re-deploying it)

Deploy huge J2EE apps

Similar Messages

Maybe you are looking for