archive-es.com » ES » E » EPPA.ES

Total: 100

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Apache Tomcat 7 Architecture (7.0.22) - Architecture Overview
    the response back to the appropriate connector for transmission to the client The Engine interface may be implemented to supply custom Engines though this is uncommon Note that the Engine may be used for Tomcat server clustering via the jvmRoute parameter Read the Clustering documentation for more information Host A Host is an association of a network name e g www yourcompany com to the Tomcat server An Engine may contain multiple hosts and the Host element also supports network aliases such as yourcompany com and abc yourcompany com Users rarely create custom Hosts because the StandardHost implementation provides significant additional functionality Connector A Connector handles communications with the client There are multiple connectors available with Tomcat These include the HTTP connector which is used for most HTTP traffic especially when running Tomcat as a standalone server and the AJP connector which implements the AJP procotol used when connecting Tomcat to a web server such as Apache HTTPD server Creating a customized connector is a significant effort Context A Context represents a web application A Host may contain multiple contexts each with a unique path The Context interface may be implemented to create custom Contexts but this is rarely the

    Original URL path: http://ticket.eppa.es/docs/architecture/overview.html (2015-09-25)
    Open archived version from archive


  • Apache Tomcat 7 Architecture (7.0.22) - Startup
    page describes how the Tomcat server starts up There are several different ways to start tomcat including From the command line From a Java program as an embedded server Automatically as a Windows service description A text description of the startup procedure is available here diagram A UML sequence diagram of the startup procedure is available here comments The startup process can be customized in many ways both by modifying

    Original URL path: http://ticket.eppa.es/docs/architecture/startup.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Architecture (7.0.22) - Request Process Flow
    Request Process Flow Request Process Flow This page describes the process used by Tomcat to handle an incoming request This process is largely defined by the Servlet Specification which outlines the order of events that must take place description TODO diagram A UML sequence diagram of the request process is available here comments The Servlet Specification provides many opportunities for listening in using Listeners or modifying using Filters the request

    Original URL path: http://ticket.eppa.es/docs/architecture/requestProcess.html (2015-09-25)
    Open archived version from archive

  • Catalina Functional Specifications (7.0.22) - Administrative Apps - Overall Requirements
    the following requirements To the maximum extent feasible all administrative functions and the access methods that support them shall run portably on all platforms where Tomcat itself runs In a default Tomcat distribution all administrative capabilities shall be disabled It shall be necessary for a system administrator to specifically enable the desired access methods such as by adding a username password with a specific role to the Tomcat user s database Administrative functions shall be realized as direct calls to corresponding Catalina APIs or through a business logic layer that is independent of the access method used to initiate it The common business logic components shall be implemented in package org apache catalina admin The common business logic components shall be built as part of the standard Catalina build process and made visible in the Catalina class loader The Java components required for each access method shall be implemented in subpackages of org apache catalina admin The build scripts should treat each access method as optional so that it will be built only if the corresponding required APIs are present at build time It shall be possible to save the configured state of the running Tomcat container such that this state can be reproduced when the container is shut down and restarted Administrative commands to start up and shut down the overall Tomcat container are out of scope for the purposes of these applications It is assumed that other usually platform specific mechanisms will be used for container startup and shutdown Dependencies Environmental Dependencies The following environmental dependencies must be met in order for administrative applications to operate correctly For access methods that require creation of server sockets the appropriate ports must be configured and available Container Dependencies Correct operation of administrative applications depends on the following specific features of the surrounding container To the maximum extent feasible Catalina components that offer direct administrative APIs and property setters shall support live changes to their operation without requiring a container restart External Technologies The availability of the following technologies can be assumed for the implementation and operation of the various access methods and the corresponding administrative business logic FIXME This list below is totally outdated but nobody cares about the administrative app anymore It is removed and unsupported since Tomcat 6 0 Java 2 Standard Edition Version 1 2 or later Servlet 2 4 supported natively by Tomcat 5 JavaServer Pages 2 0 supported natively by Tomcat 5 JavaServer Pages Standard Tag Library 1 0 Jakarta Taglibs Standard 1 0 3 Struts Framework Version 1 0 MVC Framework for Web Applications TO BE DETERMINED Application for hosting SOAP based web services Functionality Properties of Administered Objects Functional requirements for administrative applications are specified in terms of Administered Objects whose definitions and detailed properties are listed here In general Administered Objects correspond to components in the Catalina architecture but these objects are defined separately here for the following reasons It is possible that the administrative applications do not expose every possible configurable

    Original URL path: http://ticket.eppa.es/docs/funcspecs/fs-admin-apps.html (2015-09-25)
    Open archived version from archive

  • Catalina Functional Specifications (7.0.22) - Tomcat MBean Names
    none type LISTENER sequence service service port connector port address connector address Server Service Engine 1 1 none type ENGINE service service name Server Service Engine Host 1 n name type HOST host name service service name Server Service Engine Host Context 1 n path type CONTEXT context name host host name service service name Server Service Engine Host Context InstanceListener 0 n none type INSTANCE LISTENER sequence context context name host host name service service name Server Service Engine Host Context Listener 0 n none type LISTENER sequence context context name host host name service service name Server Service Engine Host Context Loader 0 1 none type LOADER context context name host host name service service name Server Service Engine Host Context Manager 0 1 none type MANAGER context context name host host name service service name Server Service Engine Host Context Realm 0 1 none type REALM context context name host host name service service name Server Service Engine Host Context Resources 0 1 none type RESOURCES context context name host host name service service name Server Service Engine Host Context Valve 0 n none type VALVE sequence context context name host host name service service name Server Service Engine Host Context Wrapper 0 n none j2eeType Servlet name name WebModule host name context name J2EEApplication context J2EEApplication J2EEServer context J2EEServer Server Service Engine Host Context WrapperLifecycle 0 n none type WRAPPER LIFECYCLE sequence context context name host host name service service name Server Service Engine Host Context WrapperListener 0 n none type WRAPPER LISTENER sequence context context name host host name service service name Server Service Engine Host Listener 0 n none type LISTENER sequence host host name service service name Server Service Engine Host Realm 0 1 none type REALM host host name service service name Server Service Engine Host Valve 0 n none type VALVE sequence host host name service service name Server Service Engine Listener 0 n none type LISTENER sequence FIXME disambiguate from Server Service Listener Server Service Engine Realm 0 1 none type REALM service service name Server Service Engine Valve 0 n none type VALVE sequence service service name Server Service Listener 0 n none type LISTENER sequence FIXME disambiguate from Server Service Engine Listener MBean Groups and Names The following MBean names shall be defined in the resource file org apache catalina mbeans mbeans descriptors xml and therefore available for use within the Administration Configuration web application for Tomcat MBean Name Group Name Catalina Interface Implementation Class AccessLogValve VALVE org apache catalina Valve org apache catalina valves AccessLogValve BasicAuthenticator VALVE org apache catalina Valve org apache catalina authenticator BasicAuthenticator CertificatesValve VALVE org apache catalina Valve org apache catalina valves CertificatesValve ContextConfig LISTENER org apache catalina LifecycleListener org apache catalina startup ContextConfig ContextEnvironment RESOURCES org apache catalina deploy ContextEnvironment org apache catalina deploy ContextEnvironment ContextResource RESOURCES org apache catalina deploy ContextResource org apache catalina deploy ContextResource ContextResourceLink RESOURCES org apache catalina deploy ContextResourceLink org apache catalina deploy ContextResourceLink CoyoteConnector CONNECTOR org

    Original URL path: http://ticket.eppa.es/docs/funcspecs/mbean-names.html (2015-09-25)
    Open archived version from archive

  • Catalina Functional Specifications (7.0.22) - Administrative Apps - Administered Objects
    Default Context A Default Context represents a subset of the configurable properties of a Context and is used to set defaults for those properties when web applications are automatically deployed A Default Context object can be associated with an Engine or a Host The following configurable properties are supported cookies Should be use cookies for session identifier communication true crossContext Should calls to ServletContext getServletContext return the actual context responsible for the specified path false reloadable Should Tomcat monitor classes in the WEB INF classes directory for changes and reload the application if they occur false useNaming Should Tomcat provide a JNDI naming context containing preconfigured entries and resources corresponding to the requirements of the Java2 Enterprise Edition specification true Each Default Context is owned by a parent Engine or Host and is associated with Zero or more Environment Entries representing environment entries for the JNDI naming context associated with a web application Zero or more JDBC Resources representing database connection pools associated with a web application An optional Loader representing default configuration properties for the Loader component of deployed web applications An optional Manager representing default configuration properties for the Manager component of deployed web applications Default Deployment Descriptor Default web application characteristics are configured in a special deployment descriptor named CATALINA BASE conf web xml This section describes the configurable components that may be stored there FIXME Complete the description of default servlets default mappings default MIME types and so on Engine An Engine is the representation of the entire Catalina servlet container and processes all requests for all of the associated virtual hosts and web applications The standard component implementing an Engine is org apache catalina core StandardEngine It supports the following configurable properties debug Debugging detail level 0 defaultHost Name of the Host to which requests will be directed if the requested host is unknown localhost name Logical name of this engine Tomcat Stand Alone Each Engine is owned by a parent Service and is associated with An optional Access Logger that logs all requests processed by the entire container A Default Context representing default properties of a Context for automatically deployed applications for all associated Hosts unless overridden by a subordinate component One or more Hosts representing individual virtual hosts supported by this container A Realm used to provide authentication and access control information for all virtual hosts and web applications unless overridden by a subordinate component Zero or more Request Filters used to limit access to the entire container based on remote host name or IP address Environment Entry An Environment Entry is the representation of a env entry element from a web application deployment descriptor It will cause the creation of a corresponding entry in the JNDI naming context provided to the corresponding Context The following configurable properties are supported description Description of this environment entry name Environment entry name relative to the java comp env context type Environment entry type must be one of the fully qualified Java classes listed in the

    Original URL path: http://ticket.eppa.es/docs/funcspecs/fs-admin-objects.html (2015-09-25)
    Open archived version from archive

  • Catalina Functional Specifications (7.0.22) - Default Servlet
    The container shall provide a servlet context attribute that lists the welcome file names that have been defined for this web application The container shall provide a servlet context attribute that contains a javax naming directory DirContext implementation representing the static resources of this web application Functionality Initialization Functionality The following processing must be performed when the init method of the default servlet is called Process and sanity check configuration parameters Per Request Functionality For all HTTP request methods the resource path is determined from the path information provided to this request either as request attribute javax servlet include path info for a request dispatcher access to a static resource or by calling request getPathInfo directly On each HTTP DELETE request processed by this servlet the following processing shall be performed If modifications to the static resources are not allowed set by a configuration parameter return HTTP status 403 forbidden If an attempt is made to delete a resource from META INF or WEB INF return HTTP status 403 forbidden If the requested resource does not exist return HTTP status 404 not found Unbind the resource from the directory context containing the static resources for this web application If successful return HTTP status 204 no content Otherwise return HTTP status 405 method not allowed On each HTTP GET request processed by this servlet the following processing shall be performed If the request is for a resource under META INF or WEB INF return HTTP status 404 not found If the requested resource does not exist return HTTP status 404 not found If the requested resource is not a directory but the resource path ends in or return HTTP status 404 not found If the requested resource is a directory If the request path does not end with redirect to a corresponding path with appended so that relative references in welcome files are resolved correctly If one of the specified welcome files exists redirect to the path for that welcome file so that it will be served explicitly If the request being processed contains an If Range header perform the processing described in the HTTP 1 1 specification to determine whether the client s information is up to date Determine the content type of the response by looking up the corresponding MIME type in our servlet context If the requested resource is a directory If directory listings are suppressed return HTTP status 404 not found Set the content type to text html Determine the range s to be returned based on the existence of any If Range and Range headers If the requested resource is a directory include an ETag header in the response with the value calculated based on the content of the directory Include a Last Modified header in the response documenting the date time that the resource was last modified Unless we are processing a HEAD request include the appropriate content or content ranges in the response On each HTTP HEAD request processed by this servlet the following

    Original URL path: http://ticket.eppa.es/docs/funcspecs/fs-default.html (2015-09-25)
    Open archived version from archive

  • Catalina Functional Specifications (7.0.22) - JDBCRealm
    a configurable debugging detail level Current Log debugging and operational messages suitably internationalized via the getContainer log method Current Dependencies Environmental Dependencies The following environmental dependencies must be met in order for JDBCRealm to operate correctly The desire to utilize JDBCRealm must be registered in CATALINA BASE conf server xml in a Realm element that is nested inside a corresponding Engine Host or Context element Container Dependencies Correct operation of JDBCRealm depends on the following specific features of the surrounding container Interactions with JDBCRealm will be initiated by the appropriate Authenticator implementation based on the login method that is selected JDBCRealm must have the JDBC standard API classes available to it For a JDK 1 2 or later container these APIs are included in the standard platform When connection pooling is implemented JDBCRealm must have the JDBC Optional Package version 2 0 or later APIs available to it This library is available as a separate download and will be included in Tomcat binary distributions Functionality Overview of Operation The main purpose of JDBCRealm is to allow Catalina to authenticate users and look up the corresponding security roles from the information found in a relational database accessed via JDBC APIs For maximum flexibility the details of how this is done for example the names of the required tables and columns should be configurable Each time that Catalina needs to authenticate a user it will call the authenticate method of this Realm implementation passing the username and password that were specified by the user If we find the user in the database and match on the password we accumulate all of the security roles that are defined for this user and create a new GenericPrincipal object to be returned If the user is not authenticated we return null instead The GenericUser object caches the set of security roles that were owned by this user at the time of authentication so that calls to isUserInRole can be answered without going back to the database every time Detailed Functional Requirements Configurable Properties The implementation shall support the following properties that can be configured with JavaBeans property setters Configuration parameters defining the JDBC driver to use the database connection URL to be accessed and the username password to use for logging in Current Configuration parameters describing the connection pool to be created to support simultaneous authentications Requested Name of the tables to be searched for users and roles Current Name of the columns to be used for usernames passwords and role names Current Lifecycle Functionality The following processing must be performed when the start method is called Establish a connection to the configured database using the configured username and password Current Configure and establish a connection pool of connections to the database Requested The following processing must be performed when the stop method is called Close any opened connections to the database Method authenticate Functionality When authenticate is called the following processing is required Acquire the one and only connection Current or acquire a connection

    Original URL path: http://ticket.eppa.es/docs/funcspecs/fs-jdbc-realm.html (2015-09-25)
    Open archived version from archive