Merge remote-tracking branch 'origin/jetty-9.4.x'
This commit is contained in:
commit
32ca2ff973
|
@ -15,16 +15,16 @@
|
|||
// ========================================================================
|
||||
|
||||
[[configuring-sessions-gcloud]]
|
||||
=== Configuring Google Cloud DataStore
|
||||
=== Configuring Session Clustering with Google Cloud DataStore
|
||||
|
||||
==== Preparation
|
||||
|
||||
You will first need to create a project and enable the Google Cloud api: https://cloud.google.com/docs/authentication#preparation.
|
||||
Take note of the project id that you create in this step as you need to supply it in later steps.
|
||||
|
||||
==== Communicating with GCloudDataStore
|
||||
===== Communicating with GCloudDataStore
|
||||
|
||||
===== When running Jetty outside of google infrastructure
|
||||
====== When running Jetty outside of google infrastructure
|
||||
|
||||
Before running Jetty, you will need to choose one of the following methods to set up the local environment to enable remote GCloud DataStore communications.
|
||||
|
||||
|
@ -38,7 +38,7 @@ Before running Jetty, you will need to choose one of the following methods to se
|
|||
* Generate a JSON link:https://cloud.google.com/storage/docs/authentication?hl=en#service_accounts[service account key] and then define the environment variable `GOOGLE_APPLICATION_CREDENTIALS=/path/to/my/key.json`
|
||||
|
||||
|
||||
===== When Running Jetty Inside of Google Infrastructure
|
||||
====== When Running Jetty Inside of Google Infrastructure
|
||||
|
||||
The Google deployment tools will automatically configure the project and authentication information for you.
|
||||
|
||||
|
@ -49,7 +49,7 @@ This file is named `index.yaml` and you can find it in your distribution in `$je
|
|||
|
||||
Follow the instructions link:https://cloud.google.com/datastore/docs/tools/#the_development_workflow_using_gcloud[here] to upload the pre-generated `index.yaml` file.
|
||||
|
||||
==== Communicating with the GCloudDataStore Emulator
|
||||
===== Communicating with the GCloudDataStore Emulator
|
||||
|
||||
To enable communication using the GCloud Emulator:
|
||||
|
||||
|
|
|
@ -16,7 +16,7 @@
|
|||
|
||||
[[configuring-sessions-infinispan]]
|
||||
|
||||
=== Configuring Remote Inifinspan Clustering
|
||||
=== Configuring Remote Session Clustering with Inifinspan
|
||||
|
||||
When using the Jetty distribution, you will first need to enable the `session-store-infinispan-remote` link:#startup-modules[module] for your link:#startup-base-and-home[Jetty base] using the `--add-to-start` argument on the command line.
|
||||
|
||||
|
|
|
@ -16,7 +16,7 @@
|
|||
|
||||
[[configuring-sessions-mongo]]
|
||||
|
||||
=== Configuring MongoDB Clustering
|
||||
=== Configuring Session Clustering with MongoDB
|
||||
|
||||
When using the Jetty distribution, you will first need to enable the `session-store-mongo` link:#startup-modules[module] for your link:#startup-base-and-home[Jetty base] using the `--add-to-start` argument on the command line.
|
||||
|
||||
|
|
|
@ -48,6 +48,8 @@ image::images/SessionsHierarchy.png[]
|
|||
|
||||
==== Configuring Sessions in the Jetty Distribution
|
||||
|
||||
Jetty provides support for several different Session Management/Clustering technologies including link:#configuring-sessions-jdbc[JDBC], link:#configuring-sessions-mongo[MongoDB], link:#configuring-sessions-infinispan[Inifinispan], link:#configuring-sessions-gcloud[Google Cloud Datastore] and one for link:#configuring-sessions-file-system[local file storage.]
|
||||
Jetty provides support for several different Session Management technologies.
|
||||
Both link:#configuring-sessions-file-system[local file storage] and link:#configuring-sessions-jdbc[JDBC] Session Management can be implemented for standard implementations.
|
||||
For implementations using clusted technologies, link:#configuring-sessions-mongo[MongoDB], link:#configuring-sessions-infinispan[Inifinispan] and link:#configuring-sessions-gcloud[Google Cloud Datastore] are all supported.
|
||||
Setting up these technologies is as easy as enabling it's link:#startup-modules[module] and editing it's associated ini file with any usernames, passwords or changes you need to make for your instance.
|
||||
The following sections will cover how exactly to enable the required modules as well as an overview of what options are available for customization.
|
||||
|
|
Loading…
Reference in New Issue