Skip to content

Latest commit

 

History

History
256 lines (155 loc) · 4.7 KB

tomee-7-79c039a.md

File metadata and controls

256 lines (155 loc) · 4.7 KB

TomEE 7

Web applications deployed with SAP Java Buildpack 1 can run in an TomEE 7 container, which is compatible with Apache Tomcat 8.5 and 9.

Applications can explicitly define the target application container by using the TARGET_RUNTIME environment variable in the application's manifest.yml file

Example:


---
applications:
- name: myapp
  ...
  env:
    TARGET_RUNTIME: tomee7

Provided APIs

The tomee7 application runtime container provides the following standard APIs:

Runtime

Full Name

Supported Specifications

tomee7

Apache TomEE 7 (Java EE 7 Web Profile)

Note:

Only relevant for SAP Java Buildpack 1!

Java Servlet 3.1

Java Server Pages (JSP) 2.3

Java Expression Language (EL) 3.0

Java WebSocket 1.1

Java Standard Tag Library (JSTL) 1.2

Java RESTful Web Services (JAX-RS) 2.0

Java Server Faces (JSF) 2.2

Java Debugging Support for Other Languages 1.0

Java Enterprise Beans (EJB) Lite 3.2

Java Transactions API (JTA) 1.2

Java Persistence API (JPA) 2.1

Java Bean Validation 1.1

Java Managed Beans 1.0

Java Interceptors 1.2

Java Annotations 1.2

Java Dependency Injection 1.0

Java Contexts and Dependency Injection 1.1

. . .

For a full list of specification versions, see: Apache TomEE 7

Customize the buildpack defaults

SAP Java Buildpack 1 provides some default configurations for the Apache TomEE 7 application container. They can be customized by the application with the Resource Configuration feature.

Below is a list of all the placeholders that can be customized by the application, along with their default values:

Placeholder

Description

Default Value

connector.maxHttpHeaderSize

The maximum size of the request and response HTTP header, specified in bytes

8192

connector.maxThreads

The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled

200

connector.allowTrace

A Boolean value that enables or disables the TRACE HTTP method

false

To configure the HTTP header size, use:

env:
  JBP_CONFIG_RESOURCE_CONFIGURATION: "['tomee7/conf/server.xml': {'connector.maxHttpHeaderSize':1024}]"

To configure the maximum number of threads, use:

env:
  JBP_CONFIG_RESOURCE_CONFIGURATION: "['tomee7/conf/server.xml': {'connector.maxThreads':800}]"

To enable the TRACE HTTP method, use:

env:
  JBP_CONFIG_RESOURCE_CONFIGURATION: "['tomee7/conf/server.xml': {'connector.allowTrace':true}]"

Configure the maximum number of active sessions

SAP Java Buildpack 1 provides the default configurations for unlimited sessions for the Apache TomEE 7 application container. They can be customized by the application with the Resource Configuration feature. To limit the number of active sessions, set the maxActiveSessions attribute on a Manager element. For example:

Example:

<Context>
  <Manager maxActiveSessions="500" />
</Context>

Configure the session timeout value

To set session timeout value of active sessions, set the <session-config> tag in the application's web.xml file:

Example:

<session-config>
    <session-timeout>1</session-timeout>
</session-config>

Configure the context path attribute

The default value of context path in server.xml is "" (Empty String). You can override this default value by using app_context_root in the application's manifest.yml file. For example:

Example:


...
  env:
    JBP_CONFIG_TOMEE: "[tomee7:{app_context_root: test_context_path}]"
...