Red Hat Summit Red Hat SummitSuporteConsoleDesenvolvedoresComeçar um testeContato

Este conteúdo não está disponível no idioma selecionado.

32.2. GOOGLE_PING Configuration

Red Hat JBoss Data Grid works with Google Compute Engine in the following way:
  • In Library mode, use the JGroups' configuration file default-configs/default-jgroups-google.xml or use the GOOGLE_PING protocol in an existing configuration file.
  • In Remote Client-Server mode, define the properties on the command line when you start the server to use the JGroups Google stack ( see example in Section 32.2.1, “Starting the Server in Google Compute Engine”).
To configure the GOOGLE_PING protocol to work in Google Compute Engine in Library and Remote Client-Server mode:
  • Use JGroups bucket. These buckets use Google Compute Engine credentials.
  • Use the access key.
  • Use the secret access key.

Note

Only the TCP protocol is supported in Google Compute Engine since multicasts are not allowed.
Report a bug

32.2.1. Starting the Server in Google Compute Engine
Copiar o link

This configuration requires access to a bucket that can only be accessed with the appropriate Google Compute Engine credentials.
Ensure that the GOOGLE_PING configuration includes the following properties:
  • the access_key and the secret_access_key properties for the Google Compute Engine user.

Example 32.1. Start the Red Hat JBoss Data Grid Server with a Bucket

Run the following command from the top level of the server directory to start the Red Hat JBoss Data Grid server using a bucket: 
bin/standalone.sh
  -c cloud.xml
  -Djboss.node.name={node_name}
  -Djboss.socket.binding.port-offset={port_offset}
  -Djboss.default.jgroups.stack=google 
  -Djgroups.google.bucket={google_bucket_name}
  -Djgroups.google.access_key={access_key}
  -Djgroups.google.secret_access_key={secret_access_key}
Copy to Clipboard Toggle word wrap
  1. Replace {node_name} with the server's desired node name.
  2. Replace {port_offset} with the port offset. To use the default ports specify this as 0.
  3. Replace {google_bucket_name} with the appropriate bucket name.
  4. Replace {access_key} with the user's access key.
  5. Replace {secret_access_key} with the user's secret access key.
Report a bug
Voltar ao topo
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2025 Red Hat