Not required if you deploy your app using Google Cloud SDK-based tooling, such as thegcloud app deploy command, IntelliJ plugins, Maven or Gradle plugins. The Google Cloud SDK-based tooling ignore this element and get the project ID from the gcloud config project property. Note that although you can override the project ID using the Google Cloud CLI, this sets a machine-wide project ID, which may cause confusion if you are developing multiple projects. The<application> element contains the application's project ID. This is the project ID you register when you create your project in theGoogle Cloud console.

Optional. If you want to use theApp Engine legacy bundled services for second-generation runtimes, set this field totrue.

Optional and only for second-generation runtimes. Overrides the default entrypoint which is the process command line that boots the Java application. By default, the generated entrypoint for a F4 instance class (memory settings are calculated from the instance class) is equivalent to the following configuration:

<appengine-web-appxmlns="http://appengine.google.com/ns/1.0"><entrypoint>java-showversion-Xms32M-Xmx819M-XX:+UseG1GC-XX:+ParallelRefProcEnabled-XX:+PrintCommandLineFlags--add-opensjava.base/java.lang=ALL-UNNAMED--add-opensjava.base/java.nio.charset=ALL-UNNAMED--add-opensjava.logging/java.util.logging=ALL-UNNAMED--add-opensjava.base/java.util.concurrent=ALL-UNNAMED-Dclasspath.runtimebase=/base/java_runtime-Djava.class.path=/base/java_runtime/runtime-main.jar-Djava.library.path=/base/java_runtime:com/google/apphosting/runtime/JavaRuntimeMainWithDefaults--fixed_application_path=/workspace/base/java_runtime</entrypoint></appengine-web-app>

You can modify the configuration to add extra JVM process flags or define your own process to boot. Notice that the application is deployed in the/workspace directory, while the runtime JARs are located under/base/java_runtime directory.

Optional. It's possible to reduce request latency by configuring your application to asynchronously write HTTP session data to the Datastore:

<async-session-persistenceenabled="true"/>

With async session persistence turned on, App Engine will submit a Task Queue task to write session data to the Datastore before writing the data to memcache. By default the task will be submitted to the `default` queue. If you'd like to use a different queue, add the `queue-name` attribute:

<async-session-persistenceenabled="true"queue-name="myqueue"/>

Session data is always written synchronously to memcache. If a request tries to read the session data when memcache is not available (or the session data has been flushed), it will fail over to Datastore, which might not yet have the most recent session data. This means that asynchronous session persistence can cause your application to see stale session data. However, for most applications the latency benefit far outweighs the risk.

default

Default. Uses scattered auto IDs that are large well-distributed integers that are small enough to be represented by 64-bit floats.

legacy

The legacy option will be deprecated in a future release and will eventually be removed. For more information, see theblog post announcing this change.

Optional. For a full explanation, see theautomatic scaling section.

Optional. For a full explanation, see thebasic scaling section.

Optional. Theappengine-web.xml file can define environment variables that are set when the application is running.

<env-variables><env-varname="DEFAULT_ENCODING"value="UTF-8"/></env-variables>

To avoid conflicts with your local environment, the development server does not set environment variables based on this file, and requires that the local environment have these variables already set to matching values.

exportDEFAULT_ENCODING="UTF-8"dev_appserverwar

When deployed to App Engine, the environment is created with these variables already set.

To determine how long a connection remains inactive without any data transmission before the client closes it, configure an idle timeout using the following syntax:

<env-variables><env-varname="APPENGINE_API_CALLS_IDLE_TIMEOUT_MS"value="TIMEOUT_IN_MS"/></env-variables>

ReplaceTIMEOUT_IN_MS with the required timeout in milliseconds.

To match a 60-second overall request/URL Fetch deadline, set it to60000. Alternatively, setting it slightly less than the server-side timeout (often 60 seconds) might be beneficial, for example,59000. The current default is58000 milliseconds.

This idle timeout configuration isn't the same as the overall request deadline for scaling, or the URL Fetch API deadline that you configure usingappengine.api.urlfetch.defaultDeadline.

Optional. Before an application can receive email, the application must be configured to enable the service. You enable the service for a Java app by including an<inbound-services> section in theappengine-web.xml file.

The following inbound service is available:

mail

Allows your application toreceive mail.

Optional. The instance class size for this module.

The followinginstance classes are available when specifying different scaling options:

automatic_scaling

When using automatic scaling, the F1, F2, F4, and F4_1G instance classes are available.

Default: F1 is assigned if you don't specify an instance class along with theautomatic_scaling element.

basic_scaling

When using basic scaling, the B1, B2, B4, B4_1G, and B8 instance classes are available.

Default: B2 is assigned if you don't specify a instance class along with thebasic_scaling element.

manual_scaling

When using manual scaling, the B1, B2, B4, B4_1G, and B8 instance classes are available.

Default: B2 is assigned if you don't specify a instance class along with themanual_scaling element.

Note: Ifinstance-class is set toF2 or higher, you can optimize your instances by settingmax-concurrent-requests to a value higher than 10, which is the default. To find the optimal value, gradually increase it and monitor the performance of your application.

Optional. For a full explanation, see themanual scaling section.

Optional. App Engine uses a "precompilation" process with the Java bytecode of an app to enhance the performance of the app in the Java runtime environment. Precompiled code functions identically to the original bytecode.

If for some reason you prefer that your app not use precompilation, you can turn it off by adding the following to yourappengine-web.xml file:

<precompilation-enabled>false</precompilation-enabled>

Note: Modules are now namedServices and services are still declared inappengine-web.xml files as modules, for example:<module>service_name</module>.

Required if creating a service. Optional for the default service. Each service and each version must have a name. A name can contain numbers, letters, and hyphens. It cannot be longer than 63 characters, start or end with a hyphen, and contain the string `-dot`. Choose a unique name for each service and each version. Don't reuse names between services and versions.

Also seeservice.

Optional. The<public-root> is a directory in your application that contains the static files for your application. When a request for a static file is made, the<public-root> for your application is prepended to the request path. This gives the path of an application file containing the content that is being requested.

The default<public-root> is/.

For example, the following would map the URL path/index.html to the application path/static/index.html:

<public-root>/static</public-root>

Optional. The files listed in the<resource-files> element are accessible by the application code using the file system. These files are stored on the application servers with the app as opposed to how static files are stored and served.

The<resource-files> element can contain the following elements:

<include>

An<include> element designates the files as resource files and available to your application code. These files are only available to your code on a read-only basis and not for traffic serving.Including and excluding files.

<exclude>

Files and directories matching<exclude> patterns won't be uploaded or available to your application code. However, these files and directories will still be accessible to your application when running on the local Development Server. For more information, seeIncluding and excluding files.

Example:

<resource-files><includepath="/**.xml"/><excludepath="/feeds/**.xml"/></resource-files>

This example demonstrates how to designate all.xml files as resource files except those in thefeeds/ directory and all of its subdirectories.

App Engine resource files are read usingjava.io.File orjavax.servlet.ServletContext.getResource/getResourceAsStream. They aren't accessible withClass.getResourceAsStream().

To use the latest supported Java version, you must specify this entry with the valuejava25.

<runtime>java25</runtime>

Services were formerly known asmodules.

Defining a service as:<service>service_name</service > is supported only bygcloud app commands.

Optional. The<service-account> element lets you specify auser-managed service account as the identity for the version. The specified service account will be used when accessing other Google Cloud services and executing tasks.

<service-account>[SERVICE_ACCOUNT_NAME]@[PROJECT_ID].iam.gserviceaccount.com</service-account>

Optional. App Engine includes an implementation of sessions, usingthe servlet session interface. The implementation stores session data in Datastore for persistence, and also uses memcache for speed. As with most other servlet containers, the session attributes that are set with `session.setAttribute()` during the request are persisted at the end of the request.

This feature is off by default. To turn it on, add the following toappengine-web.xml:

<sessions-enabled>true</sessions-enabled>

The implementation creates Datastore entities of the kind_ah_SESSION, and memcache entries using keys with a prefix of_ahs. You can delete these entities using the Dataflow template.

Note: Because App Engine stores session data in Datastore and memcache, all values stored in the session must implement thejava.io.Serializable interface.

Seeasync-session-persistence element for reducing the latency of the storage of session data.

Optional. By default, any user can access any URL using either HTTP or HTTPS. You can configure an app to require HTTPS for certain URLs in the deployment descriptor. SeeDeployment Descriptor: Secure URLs.

If you want to disallow the use of HTTPS for the application, put the following in theappengine-web.xml file:

<ssl-enabled>false</ssl-enabled>

There is no way to disallow HTTPS for some URL paths and not others in the Java runtime environment.

Optional. When certain errors occur, App Engine serves a generic error page. You can configure your app to serve a custom static file instead of these generic error pages, so long as the custom error data is less than 10 kilobytes. You can set up different static files to be served for each supported error code by specifying the files in your app'sappengine-web.xml file. To serve custom error pages, add a<static-error-handlers> section to yourappengine-web.xml, as ins this example:

<static-error-handlers><handlerfile="default_error.html"/><handlerfile="over_quota.html"error-code="over_quota"/></static-error-handlers>

Warning: Make sure that the path to the error response file does not overlap with static file handler paths.

Eachfile entry indicates a static file that should be served in place of the generic error response. Theerror-code indicates which error code should cause the associated file to be served. Supported error codes are as follows:

over_quota

Indicates that the app hasexceeded a resource quota.

timeout

Served if a deadline is reached before there is a response from your app.

Theerror-code is optional; if it's not specified, the given file is the default error response for your app.

You can optionally specify amime-type to use when serving the custom error. Seea complete list of MIME types.

Optional. The<static-files> element specifies patterns that match file paths to include and exclude from the list of static files, overriding or amending the default behavior. Static file are served from dedicated servers and caches that are separate from the application servers and are useful for serving static content such as images, CSS stylesheets or JavaScript files.

The<static-files> element can contain the following elements:

<include>

An<include> element overrides the default behavior of including all non-JSP files. The<include> element can specify HTTP headers to use when responding to request for the specified resources. For more information, seeIncluding and excluding files.

You can override the default static cache expiration by specifying theexpiration attribute on the include element. The value is a string of numbers and units, separated by spaces, where units canbed for days,h for hours,m for minutes, ands for seconds. Forexample,"4d 5h" sets cache expiration to 4 days and 5 hours after the file isfirst requested. For more information, seeCache expiration.

<exclude>

Files and directories matching<exclude> patterns won't be uploaded when you deploy your app to App Engine. However, these files and directories will still be accessible to your application when running on the local Development Server. For more information, seeIncluding and excluding files.

<static-files><includepath="/my_static-files"><http-headername="Access-Control-Allow-Origin"value="http://example.org"/></include></static-files>

Optional. Theappengine-web.xml file can define system properties and environment variables that are set when the application is running.

<system-properties><propertyname="myapp.maximum-message-length"value="140"/><propertyname="myapp.notify-every-n-signups"value="1000"/><propertyname="myapp.notify-url"value="http://www.example.com/signupnotify"/></system-properties><env-variables><env-varname="DEFAULT_ENCODING"value="UTF-8"/></env-variables>

Optional. You can configure an HTTP connector for improving CPU and memory utilization. If your application interacts with Datastore or Task Queues operations,set up monitoring to monitor performance and behavior impacts after enabling this feature.

<system-properties><propertyname="appengine.use.httpconnector"value="true"/></system-properties>

Optional. You can configure the underlying Java 17 runtime to work on EE 8, Java 21 on EE 10, or Java 25 (preview) on EE 11 using the following system property. For more information regarding EE support, seeUpgrade Java on a compatible Enterprise Edition (EE) version.

<system-properties><propertyname="appengine.use.EE11"value="true"/><!--onlyforJava25(preview)--></system-properties>

<system-properties><propertyname="appengine.use.virtualthreads"value="true"/></system-properties>

Optional. Possible values,native orurlfetch.

The default value isnative, which means that standard Java network classes use the standard Java HTTP(S) transport. To use this setting, you must enable billing for your app, or you will get exceptions, which are documented inIssue requests.

If you seturl-stream-handler tourlfetch,URL.openConnection and related methods will use URL Fetch forhttp andhttps transport.

<url-stream-handler>urlfetch</url-stream-handler>

The<version> element contains the version identifier for the latest version of the app's code. The version identifier can contain lowercase letters, digits, and hyphens. It cannot begin with the prefix "ah-" and the names "default" and "latest" are reserved and cannot be used.

Version names should begin with a letter, to distinguish them from numeric instances which are always specified by a number. This avoids the ambiguity with URLs like123.my-module.uc.r.appspot.com, which can be interpreted two ways: If version "123" exists, the target will be version "123" of the given module. If that version does not exist, the target will be instance number 123 of the default version of the module.

Optional. Default: true. Warmup requests are enabled by default for Java applications.

With warmup requests enabled, the App Engine infrastructure issues `GET` requests to/_ah/warmup, initializing<load-on-startup> servlets,ServletContextListeners, and custom warmup servlets, which allow you to initialize your application's code as it requires. You might need to implement your own handler for/_ah/warmup depending on which of these methods you choose.

To disable warmup requests, specifyfalse for this element:

<warmup-requests-enabled>false</warmup-requests-enabled>

Optional. Configures your application to use a Serverless VPC Access connector, enabling the application to send requests to internal resources in your VPC network. Specify the fully-qualified name of a connector in the<name> element:

<vpc-access-connector><name>projects/[PROJECT_ID]/locations/[REGION]/connectors/[CONNECTOR_NAME]</name></vpc-access-connector>

For more information, seeConnecting to internal resources in a VPC network.

Optional. Automatic scaling is assumed by default with a default instance class ofF1 unless specified otherwise.

Theautomatic_scaling element sets minimum and maximum levels for number of instances, latency, and concurrent connections for a module.

This element can contain the following elements:

<target-cpu-utilization>

Optional. Specify a value from 0.5 to 0.95.

This parameter specifies the CPU usage threshold at which new instances will be started to handle traffic, enabling you to balance between performance and cost, with lower values increasing performance and increasing cost, and higher values decreasing performance but also decreasing cost. For example, a value of 0.7 means that new instances will be started after CPU usage reaches 70 percent.

<target-throughput-utilization>

Optional. Specify a value from 0.5 to 0.95.

Used withmax-concurrent-requests to specify when a new instance is started due to concurrent requests. When the number of concurrent requests reaches a value equal tomax-concurrent-requests timestarget-throughput-utilization, the scheduler starts a new instance.

<max-instances>

Optional. The maximum number of instances for App Engine to create for this application version. This is useful to limit the costs of a module. Specify a value between 0 and 2147483647.

<min-instances>

Optional. The minimum number of instances for App Engine to create for this module version. These instances serve traffic when requests arrive, and continue to serve traffic even when additional instances are started up as required to handle traffic.

Specify a value from 0 to 1000. You can set the parameter to the value 0 to allow scaling to 0 instances to lower costs when no requests are being served. Note that you are charged for the number of instances specified whether they are receiving traffic or not.

<max-concurrent-requests>

Optional. The number of concurrent requests an automatic scaling instance can accept before the scheduler spawns a new instance (Default: 10, Maximum: 80).

You might experience increased API latency if this setting is too high. Note that the scheduler might spawn a new instance before the actual maximum number of requests is reached.

Note: Ifinstance-class is set toF2 or higher, you can optimize your instances by settingmax-concurrent-requests to a value higher than 10, which is the default. To find the optimal value, gradually increase it and monitor the performance of your application.

<max-idle-instances>

The maximum number of idle instances that App Engine should maintain for this version. The default value is "automatic." Keep the following in mind:

• A high maximum reduces the number of idle instances more gradually when load levels return to normal after a spike. This helps your application maintain steady performance through fluctuations in request load, but also raises the number of idle instances (and consequent running costs) during such periods of heavy load.
• A low maximum keeps running costs lower, but can degrade performance in the face of volatile load levels.

Note: When settling back to normal levels after a load spike, the number of idle instances can temporarily exceed your specified maximum. However, you won't be charged for more instances than the maximum number you've specified.

<max-pending-latency>

The maximum amount of time that App Engine should allow a request to wait in the pending queue before starting additional instances to handle requests so that pending latency is reduced.

• A low maximum means App Engine will start new instances sooner for pending requests, improving performance but raising running costs.
• A high maximum means users might wait longer for their requests to be served, if there are pending requests and no idle instances to serve them, but your application will cost less to run.

<min-idle-instances>

The number of instances to be kept running and ready to serve traffic.This setting only applies to the version that receives most of the traffic. Keep the following in mind:

• A low minimum helps keep your running costs down during idle periods, but means that fewer instances might be immediately available to respond to a sudden load spike.

• A high minimum lets you prime the application for rapid spikes in request load. App Engine keeps the minimum number of instances running to serve incoming requests. You are charged for instances, whether or not they are handling requests. For this feature to function properly, you must make sure that warmup requests are enabled and that your application handles warmup requests.

  If you set a minimum number of idle instances, pending latency will have less effect on your application's performance. Because App Engine keeps idle instances in reserve, it is unlikely that requests will enter the pending queue except in exceptionally high load spikes. You will need to test your application and expected traffic volume to determine the ideal number of instances to keep in reserve.

<min-pending-latency>

The minimum amount of time in seconds that App Engine should allow a request to wait in the pending queue before starting a new instance to handle it. Specify a value from 0.01 to 15.

• A low minimum means requests must spend less time in the pending queue when all existing instances are active. This improves performance but increases the cost of running your application.
• A high minimum means requests will remain pending longer if all existing instances are active. This lowers running costs but increases the time users must wait for their requests to be served.

<appengine-web-appxmlns="http://appengine.google.com/ns/1.0"><application>simple-app</application><module>default</module><version>uno</version><instance-class>F2</instance-class><automatic-scaling><target-cpu-utilization>0.65</target-cpu-utilization><min-instances>5</min-instances><max-instances>100</max-instances><max-concurrent-requests>50</max-concurrent-requests></automatic-scaling></appengine-web-app>

Optional. The<basic-scaling> element sets the number of instances for a module.

This element can contain the following elements:

<idle-timeout>

Optional. The instance will be shut down this amount of time after receiving its last request. The default is 5 minutes.

<max-instances>

Required. The maximum number of instances for App Engine to create for this module version. This is useful to limit the costs of a module.

<appengine-web-appxmlns="http://appengine.google.com/ns/1.0"><application>simple-app</application><module>default</module><version>uno</version><instance-class>B8</instance-class><basic-scaling><max-instances>11</max-instances><idle-timeout>10m</idle-timeout></basic-scaling></appengine-web-app>

Optional. The<manual-scaling> element enables manual scaling for a module and sets the number of instances for a module.

This element can contain the following elements:

<instances>

The number of instances to assign to the module at the start.

<appengine-web-appxmlns="http://appengine.google.com/ns/1.0"><application>simple-app</application><module>default</module><version>uno</version><instance-class>B8</instance-class><manual-scaling><instances>5</instances></manual-scaling></appengine-web-app>

Optional. Most applications don't need to change default behavior.

The staging element lets you specify a particular staging configuration if needed for deployment.

This element can contain the following elements:

<enable-jar-splitting>

Optional. Split large jar files (> 10 Megabytes) into smaller fragments. (Default: true).

<jar-splitting-excludes>

Specifies a comma-separated list of file suffixes. Ifenable-jar-splitting is enabled, all files that match the suffixes will be excluded from all JARs.

<disable_jar_jsps>

Don't jar classes generated from JSPs. (Default: false).

<enable-jar-classes>

Jar the contents of WEB-INF/classes. (Default: true).

<delete-jsps>

Delete the JSP source files after compilation. (Default: true).

<compile-encoding>

Input encoding of source files for compilation. (Default: utf-8).

For example:

        <staging>          <delete-jsps>false</delete-jsps>        </staging>