Glassfish-Servers
03:45Show all | Close all
-
Overview
-
What is server
In most common use, a server is a physical computer (a computer hardware system) dedicated to run one or more services (as a host), to serve the needs of the users of other computers on the network. Depending on the computing service that it offers it could be a database server, file server, mail server, print server, web server, gaming server, or some other kind of server. In the context of client-server architecture, a server is a computer program running to serve the requests of other programs, the "clients". Thus, the "server" performs some computational task on behalf of "clients". The clients either run on the same computer or connect through the network. In the context of Internet Protocol (IP) networking, a server is a program that operates as a socket listener. Servers often provide essential services across a network, either to private users inside a large organization or to public users via the Internet. -
Usage
The term server is used quite broadly in information technology. Despite the many server-branded products available (such as server versions of hardware, software or operating systems), in theory any computerised process that shares a resource to one or more client processes is a server. To illustrate this, take the common example of file sharing. While the existence of files on a machine does not classify it as a server, the mechanism which shares these files to clients by the operating system is the server. Similarly, consider a web server application (such as the multiplatform "Apache HTTP Server"). This web server software can be run on any capable computer. For example, while a laptop or personal computer is not typically known as a server, they can in these situations fulfill the role of one, and hence be labelled as one. It is, in this case, the machine's role that places it in the category of server. In the hardware sense, the word server typically designates computer models intended for hosting software applications under the heavy demand of a network environment. In this client-server configuration one or more machines, either a computer or a computer appliance, share information with each other with one acting as a host for the other[s]. While nearly any personal computer is capable of acting as a network server, a dedicated server will contain features making it more suitable for production environments. These features may include a faster CPU, increased high-performance RAM, and increased storage capacity in the form of a larger or multiple hard drives. Servers also typically have reliability, availability and serviceability (RAS) and fault tolerance features, such as redundancy in power supplies, storage (as in RAID), and network connections. Servers became common in the early 1990s as businesses increasingly began using personal computers to provide services formerly hosted on larger mainframes or minicomputers. Early file servers housed multiple CD-ROM drives, which were used to host large database applications.[citation needed] Between the 1990s and 2000s an increase in the use of dedicated hardware saw the advent of self-contained server appliances. One well-known product is the Google Search Appliance, a unit that combines hardware and software in an out-of-the-box packaging. Simpler examples of such appliances include switches, routers, gateways, and print server, all of which are available in a near plug-and-play configuration. Modern operating systems such as Microsoft Windows or Linux distributions rightfully seem to be designed with a client-server architecture in mind. These operating systems attempt to abstract hardware, allowing a wide variety of software to work with components of the computer. In a sense, the operating system can be seen as serving hardware to the software, which in all but low-level programming languages must interact using an API. These operating systems may be able to run programs in the background called either services or daemons. Such programs, such as the aforementioned Apache HTTP Server software, may wait in a sleep state for their necessity to become apparent. Since any software that provides services can be called a server, modern personal computers can be seen as a forest of servers and clients operating in parallel. The Internet itself is also a forest of servers and clients. Merely requesting a web page from a few kilometers away involves satisfying a stack of protocols that involve many examples of hardware and software servers. The least of these are the routers, modems, domain name servers, and various other servers necessary to provide us the world wide web. -
Types of servers
In a general network environment the following types of servers may be found. Application server, a server dedicated to running certain software applications Catalog server, a central search point for information across a distributed network Communications server, carrier-grade computing platform for communications networks Database server, provides database services to other computer programs or computers Fax server, provides fax services for clients File server, provides remote access to files Game server, a server that video game clients connect to in order to play online together Home server, a server for the home Name server or DNS Print server, provides printer services Proxy server, acts as an intermediary for requests from clients seeking resources from other servers Sound server, provides multimedia broadcasting, streaming. Standalone server, an emulator for client-server (web-based) programs Web server, a server that HTTP clients connect to in order to send commands and receive responses along with data contents
-
-
Glashfish
GlassFish is an open-source application server project started by Sun Microsystems for the Java EE platform and now sponsored by Oracle Corporation. The supported version is called Oracle GlassFish Server. GlassFish is free software, dual-licensed under two free software licences: the Common Development and Distribution License (CDDL) and the GNU General Public License (GPL) with the classpath exception. GlassFish is the reference implementation of Java EE and as such supports Enterprise JavaBeans, JPA, JavaServer Faces, JMS, RMI, JavaServer Pages, servlets, etc. This allows developers to create enterprise applications that are portable and scalable, and that integrate with legacy technologies. Optional components can also be installed for additional services. GlassFish is based on source code released by Sun and Oracle Corporation's TopLink persistence system. It uses a derivative of Apache Tomcat as the servlet container for serving Web content, with an added component called Grizzly which uses Java New I/O (NIO) for scalability and speed. -
Versions
Sun Microsystems launched the GlassFish project on 6 June 2005. On 4 May 2006, Project GlassFish released the first version that supports the Java EE 5 specification. On 8 May 2007 Project SailFin was announced at JavaOne as a sub-project under Project GlassFish. Project SailFin aims to add Session Initiation Protocol (SIP) servlet functionality to GlassFish.[1] On 17 September 2007 the GlassFish community released version 2 (aka Sun Java System Application Server 9.1) with full enterprise clustering capabilities, Microsoft-interoperable Web Services. On 21 January 2009 Sun Microsystems and the community released version GlassFish 2.1 (aka Sun GlassFish Enterprise Server 2.1) which serves as the basis for the Sailfin SIP AppServer project (aka Sun Communication Application Server). On 10 December 2009 GlassFish v3 was released. Being the Java EE reference implementation, this was the first application server to completely implement Java EE 6 JSR 316. JSR 316 was however approved with reservations. In this version GlassFish adds new features to ease migration from Tomcat to GlassFish.[2] The other main new features are around modularity (GlassFish v3 Prelude already shipped with an Apache Felix OSGi runtime), startup time (a few seconds), deploy-on-change (provided by NetBeans and Eclipse plugins), and session preservation across redeployments.[3] On 25 March 2010, soon after the acquisition of Sun Microsystems, Oracle issued a Roadmap for versions 3.0.1, 3.1, 3.2 and 4.0 with themes revolving around clustering, virtualization and integration with Coherence and other Oracle technologies. The open source community remains otherwise unaffected. On 28 February 2011, Oracle Corporation released GlassFish v3.1. This version introduced support for ssh-based provisioning, centralized admin, clustering and load-balancing. It maintains its support for both the Web Profile and full Java EE 6 Platform specifications. On 28 July 2011, Oracle Corporation released GlassFish v3.1.1. This is fix release for GlassFish v3.1 with multiple component updates (Weld, Mojarra, Jersey, EclipseLink, ...), JDK 7 support, AIX support and more. On 29 February 2012, Oracle Corporation released GlassFish v3.1.2. This release includes bug fixes and new features including administration console enhancements, transaction recovery from a database and new thread pool properties. On 17 July 2012, Oracle Corporation released GlassFish v3.1.2.2. This is a "micro" release to address some exceptional issues in the product.[4] -
How to configure and install the glassfish
Overview
Before you can run many of the tutorials provided with NetBeans documentation, the GlassFish Application Server must be configured correctly and running. This tutorial describes how to configure and start the GlassFish Application Server within the NetBeans 6.0 IDE.
In most cases, you will be using the default version of the GlassFish Application Server provided with NetBeans. However, you can configure the NetBeans IDE to use an alternate version of the GlassFish Application Server. This tutorial contains a section that describes configuring an alternate version of the GlassFish Application Server.
Note: In the following procedures, GlassFish Application Server node refers to the node that represents the GlassFish V2 installation of the application server. GlassFish V2 Application Server is equivalent to the Sun Java System Application Server, Version 9.1.
Starting the GlassFish Application Server
This procedure assumes you have either installed the default GlassFish Application Server when you installed NetBeans 6.0, or you have configured an application server, as described in the section Configuring the GlassFish Application Server.
To start the GlassFish Application Server:
- In the NetBeans IDE, if the Services window is not visible, choose Window > Services.
-
In the Services window, expand the Servers node.
The Servers node should contain a GlassFish Application Server subnode. If a GlassFish Application Server node does not appear, go to the section Configuring the GlassFish Application Server.
If a green arrow badge appears on the GlassFish Application Server node, the server is running. You are finished with this tutorial.
If a green arrow badge does not appear, proceed to next step of this procedure to start the application server. -
To start the application server, right-click the GlassFish Application Server node and select Start.
The Output window displays logging information about the application startup. If the Output window is not visible, choose Window > Output > Output
When the message Application server startup complete. appears in the Output window, the application server is running.
If you had previously deployed applications to the application server, the Output window will display additional messages as those applications are started by the application server.
The full NetBeans 6.0 download for Milestone 10 includes the GlassFish Application Server. When you install NetBeans 6.0, you also install the GlassFish Application Server.
However, you might want to use a different version of the application server than the one provided with NetBeans 6.0. For example, you might want to download and install a more current version of the GlassFish V2 application server from the GlassFish Community site.
The following procedure shows how to configure the NetBeans 6.0 IDE to use an alternate version of the GlassFish V2 Application Server. It assumes that you have downloaded and installed the alternate version of the application server.
To configure the NetBeans IDE to use an alternate version of the GlassFish V2 Application Server:
- In the NetBeans IDE, if the Services window is not visible, choose Services > Runtime.
- In the Runtime window, right-click the Servers node and choose Add Server from the pop-up menu.
The Add Server Instance dialog box opens. - In the Choose Server page, from the Server drop-down list, select GlassFish V2.
- (Optional) In the Name field, change the default name for the server.
The IDE uses this name to identify the server. - Click Next.
The Platform Folder Location page opens. - In the Platform Location field, use the Browse button to navigate to and select the installation location of the application server.
If you installed the GlassFish application server in the default location, then use Table 1 as a guide for locating the installation. Otherwise, navigate to the location where you installed GlassFish V2 Application Server.
Table 1: Default Application Server Installation Directory
Platform Installing As... SOA Installation Tools Bundle Installation Solaris OS
Linuxroot /opt/SUNWappserver /opt/SDK Solaris OS
Linuxuser ~/SUNWappserver ~/SDK Mac OS X N/A ~/SUNWappserver ~/SDK Windows N/A C:\Sun\AppServer C:\Sun\SDK - Select the Register Local Default Domain radio button and click Next.
- Enter the user name and password for the domain's administrator.
If you accepted the default values during the installation, the user name is admin and the password is adminadmin. - Click Finish.
Download
Cilck here to download glashfish server
External links
Cilck here for External links or resource
0 comments: