Red Hat Summit Red Hat SummitSupportoConsoleSviluppatoriInizia una provaContatti

Questo contenuto non è disponibile nella lingua selezionata.

17.4. Run the Application

Once built the deployed applications may be accessed using the included classes.
Using the AdminClient

In this example neither the AdminServer nor the AppOneServer are clustered at the JBoss EAP level; only the JBoss Data Grid instances are clustered as configured by the application. This application will perform the following:

  • Add values to the App1 cache, using AdminApp, and validated they are replicated to the server instance of AppOne.
  • Add a value to the App2 cache, then rollback the transaction and confirm that it is not added to the cache after the rollback.

Procedure 17.4. Execute the AdminClient application

  1. Open a command line and navigate to the $QUICKSTART_HOME/client/ directory.
  2. Execute the following command: 
    mvn -Dexec.mainClass=org.jboss.as.quickstarts.datagrid.eap.app.AdminClient exec:java
    Copy to Clipboard Toggle word wrap

    Note

    By default the application will attempt to access localhost:4447 and localhost:4547 for the AdminHost and AppOneHost. This may be changed by adding the following parameter to the mvn command: 
    -Dexec.args="AdminHost AdminPort AppOneHost AppOnePort"
    Copy to Clipboard Toggle word wrap
  3. Confirm that the following text appears in the console; any unexpected results will raise an Exception: 
    Add a value to App1Cache with the AdminApp and check on the same instance that the value is correct added
    success
Check the previous added value of App1Cache by accessing the AppOne Server
    success
Add a value to App2Cache and check on the same instance that the value is correct added
    success
Check whether changes to a cache are rollbacked if the transaction fail
    The cache App2 work as expected on rollback
    Copy to Clipboard Toggle word wrap
Using the AppOneClient

In this example both JBoss EAP and the JBoss Data Grid caches are clustered; however, the purpose of this example is to demonstrate that the clusters are independent of one other. The JBoss Data Grid cluster is able to use a different JGroups implementation compared to the JBoss EAP servers, and this example will:

  • Add values to the App2 cache using the AdminApp and access AppOne to show that the EJB invocation is clustered and both AppTwo instances are used.

Procedure 17.5. Execute the AppOneClient

  1. Open a command line and navigate to the $QUICKSTART_HOME/client/ directory.
  2. Execute the following command: 
    mvn -Dexec.mainClass=org.jboss.as.quickstarts.datagrid.eap.app.AppOneClient exec:java
    Copy to Clipboard Toggle word wrap
  3. Confirm that the following text appears in the console; any unexpected results will raise an Exception: 
    Add a value to App2Cache with the AdminApp
Access the App2Cache from the AppOneServer by using the clustered EJB@AppTwoServer
    success : received the following node names for EJB invocation : [node3, node4]
    Copy to Clipboard Toggle word wrap
Report a bug
Torna in cima
Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Aiutiamo gli utenti Red Hat a innovarsi e raggiungere i propri obiettivi con i nostri prodotti e servizi grazie a contenuti di cui possono fidarsi. Esplora i nostri ultimi aggiornamenti.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Theme

© 2025 Red Hat