Weblogic-Server

Java-Examples

                                                                                                                                                                                                                    Show 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
  • Weblogic

      Owned by Oracle Corporation, Oracle WebLogic consists of a Java EE platform product-family that includes:

    • a Java EE application server, WebLogic Application Server

    • an enterprise portal, WebLogic Portal

    • an Enterprise Application Integration platform

    • a transaction server and infrastructure, WebLogic Tuxedo

    • a telecommunication platform, WebLogic Communication Platform

    • an HTTP web server
    Prior to co-founding WebLogic, Inc., in September 1995, Paul Ambrose and Carl Resnikoff had developed (pre-JDBC) Oracle, Sybase, and Microsoft SQL Server database-drivers for Java under the name dbKona, as well as a "three-tier" server to permit applets to connect to these databases.[1] This WebLogic 1.48 server had the name T3Server (a corruption of "3-Tier Server"[dubious - discuss]). Concurrently, Laurie Pitman and Bob Pasker had worked on network-management tools written in Java. Pasker had written an SNMP stack in Java and a W32 native method for ICMP ping,[2] while Pitman had worked on applets to display the management data. The 1.48 server version had (among other hidden features) the ability to extend itself by modifying a dispatcher and adding a handler for different types of messages. Pasker talked Ambrose into sending him the source code for the server, and Pasker extended it so that applets could make SNMP and PING requests on the network, and display the results. At this point, the founders worked together to pursue what eventually became the "Application Server". In 1998, WebLogic appointed board member and angel investor Ali Kutay as President and CEO. Shortly there after, BEA Systems acquired WebLogic, Inc. in 1998, following which it became BEA WebLogic. Oracle acquired BEA in 2008, following which it became Oracle WebLogic.
  • Application Server versions

    Oracle application server

    • WebLogic Server 12c (12.1.1) - March 2012 [3]
    • WebLogic Server 12c (12.0) - December 1, 2011 [4]
    • WebLogic Server 11gR1 (10.3.6) - February 2012 [5]
    • WebLogic Server 11gR1 (10.3.5) - May 16, 2011 [6]
    • WebLogic Server 11gR1 PS3 (10.3.4) - January 15, 2011
    • WebLogic Server 11gR1 PS2 (10.3.3) - April 2010 [7]
    • WebLogic Server 11gR1 PS1 (10.3.2) - November 2009
    • WebLogic Server 11g (10.3.1) - July 2009
    • WebLogic Server 10.3 - August 2008 [8]
    • WebLogic Server 10.0 - March 2007 [9]
    • WebLogic Server 9.2
    • WebLogic Server 9.1
    • WebLogic Server 9.0 - November 2006 [10]
    • WebLogic Server 8.1 - July 2003 [11]
    • WebLogic Server 7.0 - June 2002 [12]
    • WebLogic Server 6.1
    • WebLogic Server 6.0 - file date March 2001 on an old CD [13]
    • WebLogic Server 5.1 (code name: Denali) First version supporting hot deployment for applications (via command line)
    • WebLogic Server 4.0
    • WebLogic Tengah 3.1 - June 1998 [14]
    • WebLogic Tengah 3.0.1 - March 1998 [15]
    • WebLogic Tengah 3.0 - January 1998 [16]
    • WebLogic Tengah - November 1997 [17]
  • How to configure and install the weblogic

    Downloading and Installing WebLogic server 6.0 Downloading and Installing WebLogic server 6.0 You can download the BEA WebLogic Server for http://www.bea.com to test and run the examples described in this tutorial. BEA WebLogic Server?, is world
    Downloading and Installing WebLogic server 6.0

       
  This tutorial shows you how to Install Web Logic 6.1 Server on windows machine. You can download the BEA WebLogic Server for http://www.bea.com to test and run the examples described in this tutorial. BEA WebLogic Server?, is world class Web and Wireless Application Server. It delivers scalability, flexibility, and reliability. BEA WebLogic Server's trial version is available and it you can download it from the BEA's Download Center: http://commerce.bea.com/.
Installation of the WebLogic 6.0 is cool and only you have to do is to double click it and it will start installing the software. Follow the installation instruction and install the software. 
Download the weblogic610sp3_win.exe from http://www.bea.com. To start the installation double click on the weblogic610sp3_win.exe file. This will start the InstallAnywhere installer as shown below.

Installer will display Installation wizard as show below.

Click on the Next button. License Agreement page.

Select "Yes" and then click on Next button.

On the above screen leave "Sever with Examples" selected and click on the next button.

Leave BEA home directory "C:\\bea" abd Click on the next button.

Leave the default values and click on the next button on the above "Choose Product Directory" dialog box.
 
Leave the default values and click on the next button.

Leave the default selection ( as we don't want the Bea to run as service) and click on the next button.

Enter password "system123" and click on "Install" button. This will start the weblogic installation.

Once the installation is completed, it installer will display the "Install Complete" confirmation window. Click on the "Done" button to exit the installer.

 To run it go to the start menu --> Programs --> BEA WebLogic E-Business Platform--> Start Default Server. It will ask the password, type the password that you provided during the installation and then press 'Enter Button'. It will start the WebLogic Server. To check it open your browser and the key in "http://localhost:7001" and this will show the welcome page.
To start the Administrative consol of weblogic type "http://localhost:7001/console". This will ask you the user and password, give 'system' as user and the password of the weblogic server. Now explore the administrative console yourself. 
  
  • Download

    click here to download from official site.
  • External links

    Cilck here for External links or resource
  • More script and css style : www.htmldrive.net

    0 comments:

    Glassfish-Servers

    Java-Examples

                                                                                                                                                                                                                        Show 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:
      1. In the NetBeans IDE, if the Services window is not visible, choose Window > Services.
      2. 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.


        Services Window with 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.

        SGreen Badge Indicates Application Server is Running

        If a green arrow badge does not appear, proceed to next step of this procedure to start the application server.
      3. 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.

    Configuring the GlassFish 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:
    1. In the NetBeans IDE, if the Services window is not visible, choose Services > Runtime.
    2. 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.
    3. In the Choose Server page, from the Server drop-down list, select GlassFish V2.
    4. (Optional) In the Name field, change the default name for the server.

      The IDE uses this name to identify the server.
    5. Click Next.

      The Platform Folder Location page opens.
    6. 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
      Linux
      root /opt/SUNWappserver /opt/SDK
      Solaris OS
      Linux
      user ~/SUNWappserver ~/SDK
      Mac OS X N/A ~/SUNWappserver ~/SDK
      Windows N/A C:\Sun\AppServer C:\Sun\SDK
    7. Select the Register Local Default Domain radio button and click Next.
    8. 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.
    9. Click Finish.


  • Download

    Cilck here to download glashfish server
  • External links

    Cilck here for External links or resource
  • 0 comments:

    Oc4j-Servers

    Java-Examples

                                                                                                                                                                                                                        Show 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
    • OC4J

      OC4J is a slimmed down version of Oracle Application Server. For those that have done an OBIEE install, you are familiar with the one installation prompt where you can choose either the standard or advanced option. If you choose advanced you are prompted to provide Oracle Application Server connection information. Otherwise, you are defaulted to OC4J. And, this version of OC4J that you get with OBIEE is a pre-packaged "StandAlone" (or, unmanaged) version that only has a little more than the basic functionality that the full-blown Oracle Application Server (OAS) has. Think of OC4J as OAS-lite. Now to some specifics. OC4J is entirely written in Java. It is a complete J2EE compliant environment that provides all the containers, APIs, and services that enable a J2EE product to run. It runs on the Java Virtual Machine (JVM) which is provided inside of the JDK (version 1.5 or higher). This is the reason why during the install you must actually reference where your JDK install directory exists. It is because it's heavily used by OC4J. All of these relationships to Java is why OC4J stands for Oracle Containers for J2EE. Most people don't even know that OC4J standalone comes with a application server administration tool. You could re-deploy another instance of analytics or deploy any other J2EE compliant application just like you would with WebLogic or WebSphere using OC4J. Remember that password that you entered for OC4JAdmin during the installation? Well just navigate to the following URL on your OC4J installation box, http://:9704/em, enter that password, and presto, you are able to now manage the deployed analytics.war application that got deployed during your OBIEE installation.
    • Steps to follow to configure oc4j server

      OC4J Readme

      OC4J ReadMe

      =========================================
      
      Oracle Containers for J2EE 10g (10.1.3.1)
      
      =========================================
      
      
      
      OC4J Zip Distribution ReadMe
      
      
      
      Contents
      
      --------
      
      
      
          * Introduction
      
          * Prerequisites
      
          * Extracting OC4J
      
          * OC4J Command Script
      
          * First Time Initialization
      
          * Starting and Stopping OC4J
      
          * Directly Starting and Stopping OC4J
      
          * Testing the OC4J Installation
      
          * Using Application Server Control
      
          * Using the admin_client.jar Command Line Utility
      
          * Example usages of admin_client.jar
      
      
      
      Introduction
      
      ------------
      
      
      
      The Oracle Containers for J2EE (OC4J) zip distribution provides
      
      a complete J2EE 1.4 server environment distributed as a simple zip file.
      
      
      
      The OC4J zip distribution includes an HTTP/S server, all of the required J2EE
      
      1.4 APIs and services, a complete EJB 3.0 and JPA implementation,
      
      Oracle TopLink, extensive Web Services capabilities and the browser-based
      
      Application Server Control Console management interface to configure the server
      
      and deploy applications.
      
      
      
      
      
      Prerequisites
      
      --------------
      
      
      
      In order to use the OC4J zip distribution, a Java2 Standard
      
      Edition (J2SE) SDK version 5.0 (or 1.4.2) must be installed on the host machine.
      
      
      
      
      
      Extracting OC4J
      
      ---------------
      
      
      
      Extract the oc4j_extended.zip file using  any archive utility which handles zip
      
      files, including the jar utility in the J2SE.
      
      
      
      The following directory structure will be created:
      
      
      
          
      
              /ant
      
              /bin
      
              /diagnostics
      
              /j2ee
      
              /javacache
      
              /javavm
      
              /jdbc
      
              /jlib
      
              /lib
      
              /opmn
      
              /rdbms
      
              /sqlj
      
              /toplink
      
              /webservices
      
              /xqs
      
      
      
      Where  is the directory into which the oc4j_extended.zip file was
      
      extracted.
      
      
      
      
      
      OC4J Command Script
      
      -------------------
      
      
      
      The OC4J zip distribution provides a script that can be used to start and stop a
      
      local OC4J instance. The oc4j script is located in the /bin
      
      directory.
      
      
      
          Usage: oc4j [Options]
      
      
      
      The commands supported by the OC4J command script are:
      
      
      
          Usage: oc4j [Options]
      
          Options:
      
      
      
          -start                                           : start OC4J
      
          -shutdown -port  -password  : stop OC4J
      
          -version                                         : display the version
      
          -help                                            : display this message
      
      
      
      Before using the OC4J command script, the following environment variables must
      
      be set:
      
      
      
          ORACLE_HOME : directory where oc4j_extended.zip was extracted.
      
          JAVA_HOME   : location of the J2SE SDK to be used.
      
      
      
      For example, if oc4j_extended.zip was extracted to /java/oc4j-10131 and the
      
      J2SDK was installed in /java/j2se15 then JAVA_HOME and ORACLE_HOME would be set
      
      as:
      
      
      
          JAVA_HOME=/java/j2se15
      
          ORACLE_HOME=/java/oc4j-10131
      
      
      
      
      
      First Time Initialization
      
      -------------------------
      
      
      
      There are no specific tasks that need to be performed to ready the new OC4J
      
      instance for use.  The new OC4J instance can be used immediately after the unzip
      
      operation has completed.
      
      
      
      ** Note: on the first use of OC4J, you will be prompted to enter a password for
      
      the OC4J administrator account. The username for this account defaults to
      
      "oc4jadmin".
      
      
      
      Change to the /bin  directory, and issue the following command:
      
      
      
          > cd /bin
      
          > oc4j -start
      
      
      
          Starting OC4J from /java/oc4j-10131/j2ee/home ...
      
      
      
          ... 
      
      
      
          06/08/23 13:57:17 Set OC4J administrator's password (password text will not
      
          be displayed as it is entered)
      
          Enter password: ******
      
          Confirm password: ********
      
          The password for OC4J administrator "oc4jadmin" has been set.
      
          06/08/23 13:57:17  The OC4J administrator "oc4jadmin" account is activated.
      
          06/08/23 13:57:22 The OC4J administrator "oc4jadmin" account is activated.
      
          06/08/23 13:57:31 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
      
      
      
      OC4J is configured with a set of defaults that includes a Web site from which
      
      deployed applications and the management console can be accessed. These are
      
      provided so OC4J can be started and used immediately without requiring
      
      additional configuration tasks to be performed.
      
      
      
      
      
      Starting and Stopping OC4J
      
      --------------------------
      
      
      
      The OC4J command script can be used to start and stop OC4J processes.
      
      
      
      Start OC4J using the command script as follows:
      
      
      
          >cd /bin
      
          >oc4j -start
      
      
      
          Starting OC4J from /java/oc4j-10131/j2ee/home ...
      
          06/08/23 14:00:38 Oracle Containers for J2EE 10g (10.1.3.1.0)  initialized
      
      
      
      
      
      Stop OC4J using the command script as follows:
      
      
      
          >cd /bin
      
          >oc4j -shutdown -port 23791 -password welcome
      
      
      
          Shutdown OC4J instance...
      
      
      
          Where :
      
      
      
          -port specifies the ORMI port in use with the local OC4J process.
      
      
      
          -password specifies the administration password entered as
      
           described in the "Basic Installation" section of this document.
      
      
      
      
      
      Directly Starting and Stopping OC4J
      
      -----------------------------------
      
      
      
      In addition to the OC4J command script, it possible to directly start OC4J using
      
      oc4j.jar on the command line.
      
      
      
      Directly start OC4J server by changing to the J2EE_HOME directory and issuing
      
      one of the following commands:
      
      
      
      Option 1: Start OC4J using the default configuration files, which are located in
      
      the j2ee/home/config directory.
      
      
      
          > cd /j2ee/home
      
          > java -jar oc4j.jar
      
      
      
      Option 2: Start OC4J using a customized server.xml OC4J configuration file
      
      located in a non-default directory (/mypath).
      
      
      
          > cd /j2ee/home
      
          > java -jar oc4j.jar -config /mypath/server.xml
      
      
      
      The server outputs an initialization string with the version number when it is
      
      ready to accept requests. For example:
      
      
      
          Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
      
      
      
      Stop OC4J using one of these methods:
      
      
      
      - Use the "stop" button from within Application Server Control
      
      
      
      - Use the shutdown command in the admin_client.jar command-line utility
      
      
      
      - Press ^c (Ctrl+c) in the window where the process was started
      
      
      
      - Use the process termination command (for example
      
      "kill" on Unix/Linux) for the operating system in use.OC4J will indicate on the
      
      console window that it is shutting down when it receives a shutdown signal.
      
      
      
      
      
      Testing the OC4J Installation
      
      -----------------------------
      
      
      
      Test the installation by starting the OC4J instance and accessing the welcome
      
      page from a Web browser.
      
      
      
          http://:8888
      
      
      
      Where  is the name of the server on which OC4J is running. The OC4J
      
      welcome page will be displayed.
      
      
      
      On the right hand side of the welcome page is a portlet with links to enable the
      
      testing of the JSP and Servlet environments using standard examples.
      
      
      
      If the default port number in the default-web-site.xml file has been changed,
      
      access the Web server using :
      
      
      
          http://:
      
      
      
      Where  is the value specified in the "port" attribute of the
      
       element in the file.
      
      
      
      
      
      Using Application Server Control Console
      
      ----------------------------------------
      
      
      
      The OC4J zip distribution contains the JMX-based Application
      
      Server Control Console, which enables you to perform server configuration tasks
      
      as well as deploy and manage applications.
      
      
      
      Application Server Control Console provides:
      
      
      
          + JSR-77 management and JSR-88 based deployment support
      
          + Extensive deployment support, including a comprehensive deployment
      
            plan editor
      
          + Configuration and management support for Web Services
      
          + An MBean browser for directly accessing OC4J System MBeans as well as
      
            application-specific MBeans
      
          + A JNDI browser
      
      
      
      Application Server Control Console is configured to be auto-deployed when the
      
      OC4J instance is started for the first time.
      
      
      
      Application Server Control Console can be accessed using the URL:
      
      
      
          http://:8888/em
      
      
      
      To logon to Application Server Control Console use the "oc4jadmin" username and
      
      the password you set during the first initialization of OC4J.
      
      
      
      Using the admin_client.jar Command-Line Utility
      
      -----------------------------------------------
      
      
      
      OC4J provides a command-line utility, admin_client.jar,that can be used to
      
      perform operations on a running OC4J instance. Among other things, you can use
      
      admin_client.jar to restart and stop OC4J, deploy applications, and configure
      
      various resources. The admin_client.jar utility can operate
      
      against OC4J instances running in a standalone mode or when in an Oracle
      
      Application Server environment.
      
      
      
      Note: the admin_client.jar utility is the replacement utility of the earlier
      
      admin.jar.  It operates using the OC4J MBeans and the J2EE Deployment API. It
      
      has a similar usage model to admin.jar but provides more comprehensive support
      
      for deployment operations.
      
      
      
      The admin_client.jar utility uses ORMI to connect to a running OC4J process. This
      
      means OC4J must be started before using the utility. Note that OC4J can't be
      
      started using admin_client.jar.
      
      
      
      The admin_client.jar utility is exercised using the following command:
      
      
      
          > java -jar admin_client.jar   
      
            
      
      
      
      Usage Notes:
      
      
      
         - The deployment URI specifies the target OC4J on which to perform the
      
           specified command.  A deployment URI can be one of three forms
      
      
      
           OC4J Standalone:
      
      
      
               deployer:oc4j:hostname:ormi_port
      
      
      
               deployer:oc4j:localhost:23791
      
      
      
               deployer:oc4j:localhost (defaults to 23791)
      
      
      
           Oracle Application Server - Single Instance:
      
      
      
               deployer:oc4j:opmn://opmn_host:opmn_port/oc4jInstanceName
      
      
      
               deployer:oc4j:opmn://localhost:6003/home
      
      
      
               deployer:oc4j:opmn://localhost/home (defaults to 6003)
      
      
      
           Oracle Application Server - Group:
      
      
      
               deployer:cluster:opmn://opmn_host:opmn_port/groupName
      
      
      
               deployer:cluster:opmn://localhost/Colors
      
      
      
         - The admin_user should be specified as "oc4jadmin" by default.
      
      
      
         - The admin_pwd is the "oc4jadmin" account password you configured
      
           during the first time initialization of the OC4J instance.
      
      
      
      Use the -help option see all of the available admin_client.jar commands.
      
      
      
          > java -jar admin_client.jar -help
      
      
      
      Use the -usage  option to see detailed information for a specific
      
      command.
      
      
      
          > java -jar admin_client.jar -usage 
      
      
      
          > java -jar admin_client.jar -usage deploy
      
      
      
      
      
      Example usages of admin_client.jar
      
      ----------------------------------
      
      
      
      Note: all these examples are executed from within the /j2ee/home
      
      directory.
      
      
      
      To restart OC4J:
      
      
      
          > java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin 
      
            -restart
      
      
      
      To shutdown OC4J:
      
      
      
          > java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin 
      
            -shutdown
      
      
      
      To deploy a WAR:
      
      
      
          >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin 
      
           -deploy
      
           -file 
      
           -deploymentName 
      
           -contextRoot 
    >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -deploy -file /tmp/archer/archer_web.war -deploymentName archer -contextRoot web_one To deploy an EAR file: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -deploy -file -deploymentName -bindAllWebApps >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -deploy -file /tmp/archer.ear -deploymentName archer_app -bindAllWebApps To redeploy an application: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -redeploy -file -deploymentName -bindAllWebApps >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -redeploy -file /tmp/archer_v2.ear -deploymentName archer -bindAllWebApps To undeploy an application: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -undeploy >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -undeploy archer To stop an application: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -stop >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -stop archer To start an application: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -start >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -start archer To add a JDBC Connection Pool: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -addDataSourceConnectionPool -applicationName -name -factoryClass -dbUser -dbPassword -url >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -addDataSourceConnectionPool -applicationName default -name ScottCP -factoryClass "oracle.jdbc.pool.OracleDataSource" -dbUser scott -dbPassword tiger -url "jdbc:oracle:thin:@localhost:1521:XE" To add a JDBC DataSource: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -addManagedDataSource -applicationName -name -jndiLocation -connectionPoolName >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -addManagedDataSource -applicationName default -name ScottDS -jndiLocation "jdbc/ScottDS" -connectionPoolName ScottCP To test a ConnectionPool: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -testDataSourceConnectionPool -name -sqlStatement >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -testDataSourceConnectionPool -name ScottCP -sqlStatement "select sysdate from dual" To test a DataSource: >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -testDataSource -datasourceName -sqlStatement >java -jar admin_client.jar deployer:oc4j:localhost oc4jadmin -testDataSource -datasourceName ScottDS -sqlStatement "select sysdate from dualì Copyright 2006, Oracle. All Rights Reserved.
  • Versions


    Versions:
      Oracle9iAS (1.0.2.2)
      Oracle9iAS (1.0.2.3)
      OC4j 10g (10.0.3)
  • How to configure oc4j in eclispe

     
     Eclipse Corner Article

    WTP Tutorials - Deploy Web Applications to the Oracle Application Server

    Summary
    This tutorial will step you through the details of deploying a Web Application to the Oracle Application Server Containers for J2EE (OC4J). By Raghu Srinivasan, Oracle Corporation.
    October 27, 2005

    Introduction

    The Eclipse Web Tools Platform project release 1.0 M8 has added support for deploying Web Applications to the Oracle Application Server Containers for J2EE (OC4J). This tutorial will step you through the details of installing and configuring the Oracle Application Server Container for J2EE (OC4J) and deploying a Web Applications from the Eclipse Web Tools Platform to the Oracle Application Server.

    Getting Started

    This section will walk you through the software that you need to download, install and configure. Following is the list of software you will need to install:
    • Java 2 Platform, Standard Edition(J2SE) 1.4
    • Eclipse and WTP
    • Oracle Application Server Containers for J2EE (OC4J

    Java 2 Platform, Standard Edition(J2SE) 1.4

    You must first install the Jaav2 Platform, Standard Edition (J2SE) version 1.4.2. You can get the latest release of J2SE 1.4.2 from the Sun's web site.. Install the JDK.
    Make a note of the folder in which you install J2SE. This will be required later in the tutorial.

    Eclipse and WTP

    You need to download and install the WTP 1.0 release build. Download the WTP all-in-one package. It includes the complete set of software to start using wtp immediately.

    Oracle Application Server Containers for J2EE (OC4J)

    And finally, you need to download, install and configure the Oracle Application Server Containers for J2EE (OC4J). The server adapter in the WTP 1.0 release is certified for the OC4J 10g (10.1.3.0.0) release.
    The Oracle Application Server Containers for J2EE (OC4J) zip distribution provides a complete J2EE 1.4 server environment, distributed as a simple zip file. You can download the server from the Oracle download site.
    Extract OC4J
    Extract the oc4j_extended_101300.zip file using any archive utility which handles zip files, including the jar utility in the J2SE.
    Initialize OC4J
    You need to start the OC4J instance once to set the password for the OC4J administrator account. The username for this account defaults to "oc4jadmin". Set the following environment variables:
    • JAVA_HOME: Directory where J2SE was installed
    • ORACLE_HOME: Directory where oc4j_extended_101300.zip was extracted.
    For example, if J2SE was installed in C:\j2sdk1.4.2_09 and oc4j_extended.zip was extracted to C:\Oracle\oc4j the environment variables should be set as follows:
    • JAVA_HOME=C:\j2sdk1.4.2_09
    • ORACLE_HOME=C:\Oracle\oc4j
    Start the server.From the bin directory of oc4j, issue the following command:
    • oc4j -start
    You should see the following messages in the console. You will be prompted to enter the password for the OC4J administrator account. Make a note of the password.
    • Starting OC4J from C:\Oracle\oc4j\j2ee\home ...
    • 05/10/20 14:09:58 Set OC4J administrator's password (password text will not be displayed as it is entered)
    • Enter password:
    • Confirm password:
    • Confirm password: The password for OC4J administrator "oc4jadmin" has been set.
    • 05/10/20 14:10:41 The OC4J administrator "oc4jadmin" account is activated.
    • 05/10/20 14:10:51 Oracle Containers for J2EE 10g (10.1.3.0.0) -Developer Preview 4 initialized
    Stop the server.From the bin directory of oc4j, issue the following command:
    • oc4j -shutdown -port 23791 -password admin password
    This completes the installation and configuration of all the required software. The following information will be required in the later part of this tutorial
    • User name of the OC4J administrator account is oc4jadmin.
    • The password for the administrator account.

    Run a Web Application on the Oracle Application Server

    In this section you will build a simple JSP Web Application, deploy and run it on the Oracle Application Server. Following is the list of tasks:
    • Create a server
    • Build a JSP Web Application
    • Deploy and Run the Web Application

    Create a Server

    Launch Eclipse.
    Open the J2EE perspective; select Window > Open Perspective > Other menu and in the resulting dialog, choose J2EE. The J2EE perspective includes the Servers view, which is the focus for the rest of the tutorial.
    You will also need the Console view to see the output of the Server. Select Window > Show View > Console menu.
    From a command prompt, you can launch Eclipse using the following command:
    $EclipseInstallFolder\eclipse\eclipse.exe -vm "$J2SEInstallFolder\bin\javaw.exe" -clean -data "$WorkspaceFolder"
    where $EclipseInstallFolder is folder where you installed Eclipse and $WorkspaceFolder is where you want to create new or access an existing Eclipse workspace.
    Figure 1 shows the Eclipse Workbench displaying the J2EE perspective. Note the Servers view and the Console view.
    Figure 1. The Eclipse Workbench with the Servers view and the Console view.
    The Eclipse Workbench
    Register the JDK you installed with Eclipse.

    • Open Windows>Preferences.
    • Select Java>Installed Runtimes.
    • Select the Add button and in the resulting dialog, add the JDK you installed above.
    For the field JRE home directory , point it to the root folder of the J2SE install and not the jre sub-folder. Next you register the Oracle Application Server runtime and create a server.
    Right-click in the Servers View and select New > Server menu. This launches the New Server wizard.
    Figure 2 shows the New Server Wizard with the Generic Oracle OC4J Standalone 10.1.3 DP4 Runtime selected.
    Figure 2. The New Server Wizard
    The New Server Wizard
    1. In the Define a New Server panel, Select Oracle > Generic Oracle OC4J Standalone Server 10.1.3 DP4. Click Next.
    2. In the Define a new Generic Oracle OC4J Standalone 10.1.3 DP4 Runtime panel,
      • For JRE, select the JDK you registered above.
      • For Oracle J2EE Home, browse to the subdirectory j2ee\home in the folder where you installed the Oracle Application Server. Click Next.
      Figure 3 shows the panel to register the Generic Oracle OC4J Standalone 10.1.3 DP4 Runtime.
      Figure 3. Register the Generic Oracle OC4J Standalone 10.1.3 DP4 Runtime
      Register runtime
    3. In the Create a new Generic Oracle OC4J Standalone 10.1.3 DP4 server panel,
      • Set the password to the password for the administrator account you created during the Oracle Application Server install.
      • Accept the defaults for all the other fields. Click Finish.
    You will see the Oracle OC4J Standalone 10.1.3 DP4 Preview server in the Servers view. Right-click on the server and select Start to start the server. This starts the server and displays the output in the Console view. Figure 4 shows the Oracle OC4J Standalone 10.1.3 DP4 Preview server in the Servers view.
    Figure 4. Oracle OC4J Standalone 10.1.3 DP4 Preview server in the Servers view
    Oracle OC4J Standalone 10.1.3 DP4 Preview server

    Build a JSP Web Application

    You will now build a simple JSP application that you will then run on the server. The Eclipse WTP web site has a several tutorials that can help you build sophisticated applications using the WTP tools.
    The first step to build a JSP application is to create a Dynamic Web Project.
    • From the ProjectExplorer view, right-click on the Dynamic Web Projects folder and select New Dynamic Web Project menu.
    • Enter a name for the project, say, DemoOC4J.
    • Click on the button, ShowAdvanced.
    • Note that the Target runtime field is pre-populated with the entry for OC4J: Generic Oracle OC4J Standalone 10.1.3 DP4.
    • Accept the default values for all the fields in this dialog. Click Finish.
    This will create the project. Next, you will create a JSP page.
    • Open the Dynamic Web projects folder. Expand the project you created to the WebContent folder.
    • Right-click on the WebContent folder and select New JSP menu.
    • Enter a name for the file, say, index.jsp. Click Finish.
    • The file is opened in a JSP Editor. Enter the text between the body tags:
    •  <% out.print("Hello World!!"); %>
    • Save the file.
    You are ready to run the page on the server.

    Deploy and Run the Web Application

    Right-click on the jsp file, index.jsp, in the ProjectExplorer. Select Run As > Run on Server menu.
    In the Run On Server dialog, ensure that the server, Oracle OC4J Standalone Server v10.1.3 DP4 Preview, is selected. Click on Finish.
    The Eclipse WTP tool will now do the following:
    • Package the Web Application
    • Start the server if it is not running
    • Publish the Web Application to the Server
    • Launch the application in a browser
    The Console view displays the log tracking the progress of the deployment. Figure 5 shows the application running on Oracle OC4J Standalone 10.1.3 DP4 Preview server.
    Figure 5. Running the application on Oracle OC4J Standalone 10.1.3 DP4 Preview server.
    Running the application

    Conclusion

    In this tutorial you have learned to configure the Eclipse Web Tools Platform Project to deploy and run a web application on the Oracle Application Server. The WTP web site has articles and tutorials that explain the numerous tools provided in WTP to help you build and deploy web applications. The Oracle web site has extensive resources to help you explore the capabilities of the Oracle Application Server.

    References

    1. WTP Articles and Tutorial.
    2. Oracle Application Server.
  • Download

    Cilck here to download application server
  • 0 comments:

    IBM-WebSphere-Servers

    Java-Examples

                                                                                                                                                                                                                        Show 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
    • IBM websphere

      IBM WebSphere Application Server (WAS), a software application server, is the flagship product within IBM's WebSphere brand. It was initially created by Donald Ferguson, who later became CTO of CA Technologies,[3] and the first version was launched in 1998.
    • Architecture

      WAS is built using open standards such as Java EE, XML, and Web Services. It is supported on the following platforms: Windows, AIX, Linux, Solaris, i/OS and z/OS. Beginning with Version 6.1 and now into Version 8.5, the open standard specifications are aligned and common across all the platforms. Platform exploitation, to the extent it takes place, is done below the open standard specification line. It works with a number of Web servers including Apache HTTP Server, Netscape Enterprise Server, Microsoft Internet Information Services (IIS), IBM HTTP Server for i5/OS, IBM HTTP Server for z/OS, and IBM HTTP Server for AIX/Linux/Microsoft Windows/Solaris. It uses port 9060 for connection as the default administration port and port 9080 as the default website publication port. In case you install more WebSphere instances these values will be changed.
    • Versions

      This table is derived from IBM Information Center: Specifications and API documentation and WebSphere product lifecycle dates.
      WebSphere version 8.5 8.0 7.0 6.1 6.0 5.1 5.0 4.0 3.5
      Release date 15 Jun 2012 [4] 17 Jun 2011 17 Oct 2008 30 Jun 2006 31 Dec 2004 16 Jan 2004 03 Jan 2003 15 Aug 2001 31 Aug 2000
      End of support 30 Sept 2013[5] 30 Sept 2010 30 Sept 2008 30 Sept 2006 30 April 2005 30 Nov 2003
      J2SE/Java SE 7 [6] 6 6 5 1.4 1.4 1.3 1.3 1.2
      JavaEE 6 6 5 1.4 1.4 1.3 1.3 1.2 1.2 (not fully compliant)
      Servlet 3.0 3.0 2.5 2.4 2.4 2.3 2.3 2.2 2.1&2.2
      JSP 2.2 2.2 2.1 2.0 2.0 1.2 1.2 1.1 0.91 and 1.0&1.1
      JSF 2.0 2.0 1.2 1.1 1.0
      EJB 3.1 3.1 3.0 3.0 [7] 2.1 2.0 2.0 1.1 1.0
      JMS 1.1 1.1 1.1 1.1 1.1 1.02
      JDBC 4.1 4.0 4.0 3.0 3.0
      JPA 2.0 2.0 2.0 1.0
    • Security


      The WebSphere Application Server security model is based on the services provided in the operating system and the Java EE security model. WebSphere Application Server provides implementations of user authentication and authorization mechanisms providing support for various user registries:
      Local operating system user registry
      LDAP user registry
      Federated user registry (as of version 6.1)
      Custom user registry
      The authentication mechanisms supported by WebSphere are[11]
      Lightweight Third Party Authentication (LTPA)
    • Download

      Cilck here to download websphere

    0 comments:

    JBoss-Servers

    Java-Examples

                                                                                                                                                                                                                        Show 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
    • JBoss

      JavaBeans Open Source Software Application Server (JBoss AS, or simply JBoss) is an application server that implements the Java Platform, Enterprise Edition (Java EE). JBoss is written in Java and as such is cross-platform: usable on any operating system that supports Java. JBoss was developed by JBoss, now a division of Red Hat. Licensed under the terms of the GNU Lesser General Public License, JBoss is free and open source software.
    • Origin

      In 1999, Marc Fleury started a free software project named EJB-OSS (stands for Enterprise Java Bean Open Source Software) implementing the EJB API from J2EE (Java 2 Enterprise Edition). Sun Microsystems asked the project to stop using the EJB trademark within its name. EJB-OSS was then renamed to JBOSS, then JBoss later.[2] .
    • Versions

      JBoss AS 4.0, a Java EE 1.4 application server, features an embedded Apache Tomcat 5.5 servlet container.
      It supports any Java Virtual Machine (JVM) between versions 1.4 and 1.6. JBoss can run on numerous operating systems including many POSIX platforms (like GNU/Linux, FreeBSD and Mac OS X), Microsoft Windows and others, as long as a suitable JVM is present.
      JBoss AS 4.2 also functions as a Java EE 1.4 application server, but deploys Enterprise JavaBeans 3.0 by default. It requires the Java Development Kit version 5, and includes Tomcat 5.5.
      JBoss AS 5.1, released in 2009, operates as a Java EE 5 application server. It is a minor update of the major release JBoss AS 5.0, which was in development for at least three years and was built on top of a new JBoss microcontainer.[3] JBoss AS 5.1 contains a preview of some elements from the Java EE 6 specification.[4]
      JBoss AS 6.0,[5] an unofficial implementation of Java EE 6, was released on December 28, 2010. Although JBoss AS 6 does not support the full Java EE 6 stack,[6] it chose not to support this officially[7][8] by obtaining an official certification from Oracle. It does, however, officially support the Java EE 6 Web Profile.
      JBoss AS 7,[1] was released on July 12, 2011, only six months after the last major release, JBoss AS 6. Unlike previous increments of the major versioning number, JBoss AS 7 supports the same Java EE specification as the last major release, namely Java EE 6. The Java EE profile is only partially implemented in JBoss AS 7, e.g. it includes MDBs, but listening to JMS destinations (which is mandated by the full spec) is not supported.[9] It is, however, certified for the Web Profile. The software code has been completely rewritten for JBoss AS 7.[10][11] Major changes visible to the user are the inability to define resources like JMS destinations and datasources inside archives (war/ear),[12][13] the way datasources are defined,[14][15] a much smaller size (less than half of JBoss AS 6)[1] and a 10-fold reduction in startup time.[16]
      JBoss AS 7.1, the current stable version, was released in February 2012. The remaining parts of the EE spec were implemented, and this version was certified for the EE full profile [17].
    • Installation steps

      JBoss Installation
      Before we start I would like to make one note and that is when you install software try and rename the installation directory (not to use any spaces) because in some environments (Windows) it likes to place JBoss in a pathname that has spaces (c:\program files\...), when you develop applications later, spaces in pathnames will cause you major headaches.
      The first task we need to do is to obtain the JDK from Sun (http://java.sun.com), I used version 1.6.0 and JBoss runs perfectly but you might want to try with the latest version, download the JDK and install into your environment following Sun's instructions. Once installed don't forgot to set a JAVA_HOME environment variable that points to your JDK.
      JAVA_HOME set JAVA_HOME=c:/jdk1.6.0_12
      Installing JBoss is simple and there are a number of ways that you can install it
      • Binary
      • Using JEMS (GUI)
      The fastest way to install JBoss is to download the binary version from http://www.jboss.org, unzip it and copy it to directory and that's it, it is ready to go, no installation. If you are going to install it straight into Production, then you need to make some changes to the default configuration to secure it, I have a topic on Production configurations. JBoss will work straight out of the box and is ideal for a development environment, the other route is to use JEMS installer which is a GUI based installer that allows you to configure the services that JBoss will use, you need to download the jems-installer file (http://labs.jboss.com/jeminstaller) which is an executable JAR file (90MB), looking at the web site the JEMS installer does not appear to supported very well as the link did not work but you can obtain the file from SourceForge.
      It appears that the binary installation is the preferred way to go, one note is that there is no installation and everything that you need is contained in one directory (no registry settings or package stuff), this means you just copy the directory and put onto any server (Windows or Unix) and it should start up, the only difference is the way you start JBoss
      • Windows - run.bat
      • Unix - run.sh
      There is a file called "service" in the bin directory which can create a windows JBoss service for you, I had problems when using this, it gave a file error message, this was because of the "jbosssvc" wrapper file was either corrupt or the wrong type, search for a newer version on the web and replace the one in the original install (I have a link below to the one I used)
      create a windows JBoss service c:\jboss6\bin\service install
      Note: downloaded jbosssvc file
      Directory Structure
      When you have finished installing JBoss you should have a top level directory structure like below (Yes. I know its JBoss 4 but its the same layout)

      bin This directory contains all the scripts (both Unix and Windows) that you will need to start and stop JBoss. There are a number of others files here
      • twiddle - we discussed this earlier
      • probe - used to discover JBoss AS clusters
      • wsconsume - Used for web services
      • wsprovide - Used for web services
      • wsrunclient - Used for web services
      • wstools - Used for web services
      • run.sh and run.bat - used to start JBoss
      client This directory contains many Java libraries that are used to communicate with JBoss server from a client application. These client applications are called standalone client or remote clients and could be Swing applications, remote Web services, JMS clients. If for what ever reason you need to use these libraries use the jbossall-client.jar file, this jar file contains a META-INF/Manifest.mf file that contains a class path reference to all the jar files in this directory.
      common This directory I believe is from the version 4 JBoss implemention, where all common Java libraries were placed so that all web application could use them, I now believe that all common libraries should be placed in the <server config>/lib directory (see below).
      docs There are no user manuals in this directory, but it contains the following
      • Document type definition (DTD) files and XML schemas for the configuration files that JBoss AS uses
      • Configuration examples for various J2EE and JBoss AS
      • Licenses for various libraries included in JBoss AS
      • Unit test results from the tests run against the server for the particular release
      lib This directory contains all the libraries that need to start the core JBoss server. Do not put any libraries that you want to use across all web applications, these need to go in <server config>/lib (see below)
      server This directory only has the server configurations in it, each directory represents a different server configuration that JBoss can be started in (see above).
      Normally you copy a particular directory that suits you and rename to what ever you want and then configure this directory for your environment, then use the -c option to start your server configuration

      c:\jboss5\bin\run.bat -c myServerConfig
      The server directory holds the server configuration, see above for the layout of this directory
      conf Each server configuration has a conf directory that holds files used for servlet-wide configuration. This directory is only scanned once during the boot sequence so any changes that yo make are not picked up until you restart the server. The import files in this directory are
      • bootstrap.xml - defines core microcontainer services
      • jboss-service.xml - defines core JMX services
      • jboss-log4j.xml - configures logging
      • login-config.xml - configures authentication and authorization modules for security
      • standardjboss.xml - used to configure the various EJB containers
      • jacorb.properties - Used to configure the Java Object Request Broker (JacORB) service, used in clustering
      • jax-ws-catalog.xml - Used to map XML metadata names to local metadata descriptor files
      • jbossjta-properties.xml - Used to configure the Java Transaction API (JTA) service
      • jboss-service.xml - a variation of the jboss-service.xml file configured for a minimal app server configuration
      • jndi.properties - Used by the JNDI service to define default properties
      • standardjbosscmp-jdbc.xml - Used by the EJB service to define type mappings for various databases for data persistence
      deploy this is where applications and services are deployed. You can deploy any application packages here for example JAR, WAR or EAR that you create. By copying them into this directory JBoss will automatically deploy them to the application server.
      deployers contains all the JBoss AS services that are used to recognize and deploy different applications and archive types, for example the ejb3.deployer directory contains libraries and configuration files necessary for starting the service that deploys EJB3 applications that you deploy into the deploy directory.
      lib this directory holds all the Java libraries that can be accessed by all web applications.
      Generated Directories JBoss creates additional directories when first started
      • data - used to write to the filesystem for storing temporary data
      • log - holds three log files: boot.log, server.log, audit.log
      • tmp - stores temporary data by various services
      • work - used by the web server to store compiled JSP files and other temporary data
      Server Configurations
      JBoss is designed to be modular, this means that you add or remove services very easily, by removing unwanted services you can decrease the memory allocation and increase performance, it also reduces security risks. The picture below shows how the microcontainer runs on top of the JVM and how various application-server services plug into the microcontainer. When you start JBoss you are always starting a server configuration which is a directory structure under the server's server directory, it contains code, libraries and configuration files for a set of services and applications that run when the server starts.

      Typically you copy one of the already supplied configurations and adapt it to your environment, then start this configuration using the -c option with run.bat or run.sh, or you can just use one of the supplied configurations.
      start a different configuration run.bat -c minimal

      run.bat -c <your configuration>
      Pre-Configurations
      all Includes everything - clustering, RMI/IIOP support
      default this is the default configuration if you do not specify anything, it does not include a web container, no ejb or JMS support
      minimal Includes only JNDI, logging services an a URL deployment scanner to find new deployments
      standard
      web Used to contain services which will allow simple web applications (servlet, jsp) to be deployed.
      JBoss Boot Sequence
      I have read a number of JBoss books and none of them detailed the JBoss boot sequence, searching the web and using the JBoss log file, I will put a quick summary of the boot sequence below, it may not be to accurate but there is no document that explains this well, I will update this as and when I get more information.
      • You start JBoss by running the run.bat or run.sh script, this script sets some variables and then initiates the boot sequence using the org.jboss.Main.main method entry point.
      • The main method creates a thread group then starts the microcontainer org.jboss.bootstrap.microcontainer.ServerImpl
      • The microcontainer opens the bootstrap.xml, which is a file that contains various MBeans descriptors that should be loaded by the BasicXMLDeployer
      • Once the MainDeployer has been invoked it uses the conf/jboss-service.conf file to start the services required for the web application
      bootstrap.xml Defines the core microcontainer services that start when the server first starts.
      bootstrap.xml file
      vfs.xml This configures the Virtual filesystem, which is a simple read-only framework abstracting the way we look at the the filesystem. It uses virtual files which can be accessed by a URI/URL (uses a URI/URL:MBean link pairing)
      classloader.xml This configures the core classloading system and classpath
      aop.xml Aspect-oriented programming is a programming paradigm that increases modularity by allowing the separation of cross-cutting concerns. (its a post OOP programming paradigm)
      jmx.xml This configures the JMX Kernel Mbeans
      deployers.xml This configures the MainDeployer, Structure Deployers, the bootstrap MC and the JMX deployer
      binding.xml This configures the ServiceBindingManager bean and configuration
      profile-repository.xml This configures the ProfileService beans which includes management and deployment support.
      Starting and Stopping JBoss
      To start JBoss using the default configuration, you open a console window and go to the bin directory, then run "run.sh" or "run.bat", you can also use the -c option to change the default server configuration, I have already discussed this above. To stop JBoss use the "shutdown" command
      Starting JBoss # cd <JBoss dir>/bin

      # run.sh
      c:\> run.bat

      # run.sh -c all
      Stopping JBoss # shutdown.sh
      c:\> shutdown.bat
      When JBoss has started you should see the below line in the log file, you can also check that JBoss has started by using the following URL http://localhost:8080
      JBoss has started 2009-04-03 12:05:12,125 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 1m:907ms
      Logging
      JBoss uses log4j an open source logging framework, the configuration file is located at server/xxx/conf/jboss-log4j.xml. I have already discussed log4j in my Tomcat tutorial, so have a look there first then continue back here. JBoss be default has two appenders configured, one for the console and for the server/xxx/log/server.log file. Most configuration setups use a rolling log file, it is created each time JBoss is stopped and restarted and at midnight it is rolled over, you can also specify a size for it to rollover.
      Rolling logfile <log4j: ...>
        <appender name="FILE" class="org.jboss.logging.appender.RollingFileAppender">
          <errorHandler ../>
          <param name="File" value="${jboss.server.log.dir}/server.log"/>
          <param name="Append" value="true"/>
          <param name="MaxFileSize" value="10MB"/>
          <param name="MaxBackupIndex" value="20"/>
          <layout ../>
        </appender>
        ...
      </log4j>
      Limiting logging <log4j:...>
        ...
        <category name="org.jboss.jms">
          <priority value="WARN"/>
        </category>
      </log4j>
      System Properties
      There are a number of system properties that define default directory locations
      jboss.home.dir c:\jboss-5.0.0.GA
      /opt/jboss-5.0.0.GA
      jboss.home.url file:/c:\jboss-5.0.0.GA
      file://opt/jboss-5.0.0.GA
      jboss.lib.url <jboss.home.url>lib/
      jboss.patch.url -none-
      jboss.server.base.dir <jboss.home.dir>/server
      jboss.server.base.url <jboss.home.url>server/
      jboss.server.home.dir <jboss.server.base.dir>/default
      jboss.server.home.url <jboss.server.base.url>default/
      jboss.server.config.url <jboss.server.home.url>conf/
      jboss.server.data.dir <jboss.server.home.dir>/data
      jboss.server.lib.url <jboss.server.home.url>lib/
      jboss.server.log.dir <jboss.server.home.dir>/log
      jboss.server.temp.dir <jboss.server.home.dir>/tmp
      You can also provide system properties on the commandline by using the "-D" option
      supplying commandline properties c:\> run.bat -Djboss.server.log.dir=d:/log
      There are two more systems properties which are of interest
      jboss.server.name default
      jboss.bind.address 127.0.0.1
      System properties are used in a number of configuration XML files and as stated above you can add your own properties using the "-D" option
      Using your own system properties c:\> run.bat -Dtrading.database.login=trader1 -Dtrading.database.password=traderpw
      // In your oracle-ds.xml file
      <user-name>${trading.database.login}</user-name>
      <password>${trading.database.password}</password>
    • Download Jboss

      To download Click Here

    0 comments: