GlassFish v3

Facebook Twitter
by Adam Bien Exploit the built-in monitoring and management capabilities of GlassFish to automate application deployment and gain insight into application performance. Published December 2013 IT is all about streamlining and automation, so it is somewhat ironic that we developers still tolerate repetitive and boring manual tasks, such as deployment. Also, our ignorance about easily accessible information for application servers, such as monitoring data, is surprising. RESTful GlassFish Monitoring and Management RESTful GlassFish Monitoring and Management
Build an automated deployment pipeline for your Java EE applications using leading open-source technologies, including NetBeans, Git, Maven, JUnit, Jenkins, and GlassFish. All source code for this post is available on GitHub. Introduction In my earlier post, Build a Continuous Deployment System with Maven, Hudson, WebLogic Server, and JUnit, I demonstrated a basic deployment pipeline using leading open-source technologies. In this post, we will demonstrate a similar pipeline, substituting Jenkins CI Server for Hudson, and Oracle’s GlassFish Application Server for WebLogic Server. Building a Deployment Pipeline Using Git, Maven, Jenkins, and GlassFish (Part 1 of 2) | ProgrammaticPonderings Building a Deployment Pipeline Using Git, Maven, Jenkins, and GlassFish (Part 1 of 2) | ProgrammaticPonderings
Glassfish 3.1.1 Cluster with Load-Balancer Installation Glassfish 3.1.1 Cluster with Load-Balancer Installation Posted: décembre 21st, 2011 | Author: usul | Filed under: Dev, Java, Java EE, Tutorial | Tags: Centos, Cluster, Debian, EJB, Glassfish, HowTo, Java, Java EE, Load-balancer, Oracle, Server, Setup, Tutorial | 10 Comments In this tutorial we’ll see how to install a Glassfish cluster with this architecture Assumptions : there’s nothing on servers (either java, xauth or whatever you want)
Optimize Glass Fish Performance 1Sun Microsystems, Inc Executive Summary This white paper will describe and provide general guidance for initial tuningvalues for eleven parameters in order to improve your application performanceon the Sun GlassFish application server v2. Additional specific tuning advice isalso provided for the CoolThreads UltraSPARC T1/T2 platform. Optimize Glass Fish Performance
Admin

On December 10, GlassFish v3 GA will spread the world. As you are aware, the marketing vehicle for this release will be Java EE 6 and the fact that GlassFish is now a full OSGi runtime/container!!! Both are innovative technology, but they will not save your life once you put GlassFish in production hence this survival guide :-). At the end, once your OSGi/EE 6 application is ready, you still want to have the same great performance you’ve got with GlassFish v2. This blog will gives some hints about how to configure and prepare GlassFish v3 for production use. Putting GlassFish v3 in Production: Essential Surviving Guide Putting GlassFish v3 in Production: Essential Surviving Guide
GlassFish v3 JDBC Resource | Java.net
TIP: Glassfish v3 as Windows Service TIP: Glassfish v3 as Windows Service That’s is something simple but I’ve taken a long time to figure out how to set my Glassfish v3 server as a Windows Service. After a long time doing google searching, I came across a simple solution. All that you need to do is enter in your Glassfish v3 bin directory and run the command:
The sun-web.xml File (Sun Java System Application Server Platform Edition 9 Application Deployment Guide) - Sun Microsystems The sun-web.xml File (Sun Java System Application Server Platform Edition 9 Application Deployment Guide) - Sun Microsystems Oracle Oracle Oracle Technology Network Indexes Documentation Index Documentation
Bonjour, Jusqu’ici je faisais tourner une appli sur Tomcat 6.0. Mon war contenait le context.xml dans le META-INF avec tout ce qui va bien (voir ci-dessous). J’ai réussi à faire tournée mon appli sous GlassFish 2.1 en enlevant le context.xml et un créant la jdbc resource et custom resource depuis la console web. J’aurais voulu savoir comment déclarer ces resources dans un xml qui serait pris en compte lors du deploy du war ? enfin si cela est possible… Merci Code : context.xml jdbc/custom resource context.xml jdbc/custom resource