28.2. GOOGLE_PING Configuration
28.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 28.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 28.2.1. Starting the Server in Google Compute Engine 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 28.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: Replace {server_ip_address} with the server's IP address. Replace {google_bucket_name} with the appropriate bucket name. Replace {access_key} with the user's access key. Replace {secret_access_key} with the user's secret access key. Report a bug
bin/clustered.sh -Djboss.bind.address= {server_ip_address} -Djboss.bind.address.management= {server_ip_address} -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}