Optimized Development for WebLogic Portal Apps. If you would like to improve the speed at which you can develop a WebLogic Portal 9.2 application, this blog is for you. Actually, most of this advice applies to anyone developing medium to large Java web applications, but I will focus on WLP. Across BEA we have been investigating ways to improve what we call iterative development performance. I will share some discoveries that you can put to use today. NOTE: this blog entry was originally posted May 12th, 2007 on my previous blogging system (dev2dev.bea.com). The 5 Easy Ways to Improve Development Performance I will explain the 5 tips we have found to be most useful in improving iterative development performance. Performance here is measured in the time it takes to republish your application. Use JRockit as your server JVM!!! BEA JRockit is your Friend This one is a no-brainer.
Not sure what you are using? JRockit is a good choice not only for performance reasons. Life is Better in a Parallel Universe Another no-brainer. Work Continues... Configuring Apache 2 and Tomcat 5.5 with mod_jk. Update May 15th 2007 If you're interested in setting up Apache virtual hosts with Tomcat 5.5 and mod_jk, check out my recent blog post on that subject. I recently went through the painful exercise of configuring Tomcat 5.5 behind Apache 2 using the mod_jk connector. I had done it before with mod_jk2, but it seems that mod_jk2 is deprecated, so I wanted to redo it with the officially supported mod_jk connector. Although I found plenty of tutorials and howtos on Google, they all missed some important details or were not exactly tailored to my situation. Step 1: Install Apache 2 I won't go into many details, as this a very well documented process. . In the following discussion, I will assume that Apache 2 is installed in /usr/local/apache2.
Step 2: Install JDK 1.5 In my case, I put the JDK files in /usr/local/java and I added this line to root's .bash_profile file: export JAVA_HOME=/usr/java/jdk1.5.0_05 Step 3: Install Tomcat 5.5 Download apache-tomcat-5.5.12.tar.gz and put it in /usr/local. A. Using WLST Offline. Systems - Spring on Weblogic. Making the Most of WebLogic Classloaders @ WEBLOGIC JOURNAL. As a Java developer, have you ever found yourself running into what might be politely called 'issues' related to the CLASSPATH and class loading? If you haven't, you're one of the few. This is one of the most notorious sources of developer aggravation in Java development. Now J2EE has added a new set of wrinkles to this phenomenon. This article dispels some of the mystery of what's going on behind the classloader curtain and provides insights into how you can use this knowledge to your advantage when designing, packaging, and deploying your WebLogic Server applications.
Quick Classloader Review Let's begin with a short review of how classloaders work: Classes are loaded when new bytecode is executed for the first time, either via a new class instance as in "MyClass x = new MyClass();" or by a first reference made to a static class, "MyStatic.staticMethod();". Nonetheless, there are certain rules all classloaders follow, many of which can ultimately impact your WebLogic applications. Apache Jakarta Tomcat 5.5: Configuration and Usage Tutorial. Automate resource configuration on WebLogic Server. Every deployable J2EE component must be specifically configured on the application server to function.
For WebLogic Server, developers generally complete this configuration manually by using the console, by using WebLogic Ant tasks wlconfig and wldeploy, or by using the command line tool weblogic.deployer. The Ant tasks and the command line tools need much environment-specific information for correct configuration, and WebLogic 9.0 recommends limited use of these tools. Applications don't have a uniform way for maintaining and communicating configuration information to application deployers, which can result in custom scripts or manual configuration.
As custom scripts are difficult to maintain and manual configuration may lead to errors, achieving a smooth propagation and release mechanism for J2EE artifacts proves difficult. This article provides a sample format in which configuration information should be maintained by the application. Types of WebLogic Server configuration Process.