Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Se hai aggiunto la gestione API alla tua applicazione su Google Cloude
successivamente decidi di non volere le funzionalità di gestione API, puoi configurare
Cloud Endpoints Frameworks per interrompere la gestione della tua API.
La rimozione della gestione delle API non impedisce la pubblicazione dell'API. Se vuoi
interrompere la pubblicazione dell'API, puoi disattivare l'applicazione nella pagina Impostazioni
App Engine nella console Google Cloud oppure
puoi eliminare il progetto Google Cloud . Per saperne di più, consulta Disattivazione di un'applicazione e chiusura di un progetto.
Per rimuovere la gestione delle API:
Esegui il backup dei file web.xml e appengine-web.xml del progetto API.
Nel file web.xml del progetto API, rimuovi quanto segue:
Il filtro endpoints-api-configuration.
Il filtro endpoints-api-controller.
La mappatura dei filtri endpoints-api-configuration.
La mappatura dei filtri endpoints-api-controller.
Dopo aver eliminato i filtri e i mapping dei filtri, il file web.xml dovrebbe
essere simile al seguente:
Nel file appengine-web.xml, rimuovi la riga che definisce la variabile di ambiente
ENDPOINTS_SERVICE_NAME. Se ENDPOINTS_SERVICE_NAME
è l'unica variabile di ambiente che hai definito, rimuovi l'intera sezione
env-variables.
Pulisci il progetto e poi crea l'API:
Maven
mvnclean
mvnpackage
Gradle
gradleclean
gradlebuild
Esegui nuovamente il deployment dell'applicazione:
Maven
mvnappengine:deploy
Gradle
gradleappengineDeploy
Dopo aver eseguito nuovamente il deployment dell'applicazione, Cloud Endpoints Frameworks smette di gestire
l'API.
Verifica della rimozione della gestione delle API
Per verificare che Endpoints Frameworks non gestisca più la tua API:
Nella console Google Cloud , vai alla pagina Endpoint > Servizi.
Il contatore delle richieste per il metodo non viene aggiornato.
Fai clic sul link View logs per il metodo.
Il log Produced API non contiene voci di log per le richieste che
hai inviato.
Rimozione delle dipendenze nella configurazione della build
Sebbene non sia obbligatorio, ti consigliamo di rimuovere le dipendenze nella configurazione di build.
Per rimuovere le dipendenze nella configurazione della build:
Esegui il backup del file pom.xml o del file build.gradle.
Rimuovi le seguenti dipendenze:
endpoints-management-control-appengine
endpoints-management-control-appengine-all
endpoints-framework-auth
Pulisci il progetto e poi crea l'API:
Maven
mvnclean
mvnpackage
Gradle
gradleclean
gradlebuild
Esegui nuovamente il deployment dell'applicazione:
Maven
mvnappengine:deploy
Gradle
gradleappengineDeploy
Testa l'API per assicurarti che funzioni come previsto.
Eliminazione del servizio gestito
Endpoints Frameworks utilizza Service Management di Google per gestire la tua API.
Quando hai eseguito il deployment del documento OpenAPI utilizzando il comando gcloud endpoints services
deploy, il comando ha utilizzato Service Management per creare un servizio gestito per la tua API. Se non hai bisogno dei dati nella pagina
Endpoint > Servizi e nel log API prodotta nella pagina Visualizzatore log, puoi eliminare il servizio gestito per la tua API, che rimuove i dati
dalla console Google Cloud .
Per eliminare il servizio gestito:
Assicurati che gcloud CLI (gcloud) sia autorizzata ad accedere ai tuoi dati e servizi su Google Cloud:
gcloudauthlogin
Inserisci quanto segue per visualizzare gli ID progetto per i tuoi Google Cloud
progetti:
gcloudprojectslist
Utilizzando l'ID progetto applicabile del passaggio precedente, imposta il progettoGoogle Cloud predefinito su quello in cui si trova la tua applicazione:
gcloudconfigsetproject[YOUR_PROJECT_ID]
Ottieni il nome di tutti i servizi gestiti nel tuo progetto Google Cloud :
gcloudendpointsserviceslist
Elimina il servizio da Service Management. Sostituisci
SERVICE_NAME con il nome del servizio che vuoi
rimuovere.
gcloud endpoints services delete SERVICE_NAME
L'esecuzione di gcloud endpoints services delete non elimina immediatamente il servizio gestito. La gestione dei servizi disattiva il servizio gestito per 30 giorni, il che ti consente di ripristinarlo se necessario. Dopo 30 giorni,
Service Management elimina definitivamente il servizio gestito.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 UTC."],[[["\u003cp\u003eYou can disable Cloud Endpoints Frameworks API management features without stopping your API from being served, if it was previously added to your application.\u003c/p\u003e\n"],["\u003cp\u003eTo remove API management, you will need to modify the \u003ccode\u003eweb.xml\u003c/code\u003e and \u003ccode\u003eappengine-web.xml\u003c/code\u003e files within your API project, clean and rebuild the API, then redeploy the application.\u003c/p\u003e\n"],["\u003cp\u003eAfter removing the API Management, you can verify it is no longer being managed by checking the Google Cloud Console's Endpoints Services page and reviewing the request counter and log entries.\u003c/p\u003e\n"],["\u003cp\u003eYou have the option to remove API management dependencies from your build configuration files (\u003ccode\u003epom.xml\u003c/code\u003e or \u003ccode\u003ebuild.gradle\u003c/code\u003e) by deleting specific dependency entries and redeploying.\u003c/p\u003e\n"],["\u003cp\u003eIf you no longer need the data from the Google Cloud Console's \u003cstrong\u003eEndpoints\u003c/strong\u003e > \u003cstrong\u003eServices\u003c/strong\u003e page or the \u003cstrong\u003eProduced API\u003c/strong\u003e log, you can delete the managed service for your API, by using \u003ccode\u003egcloud endpoints services delete\u003c/code\u003e which will initiate a 30-day disabling period before permanent deletion.\u003c/p\u003e\n"]]],[],null,["# Removing API management\n\nIf you added API management to your application on Google Cloud, and\nsubsequently decide that you don't want the API management features, you can configure\nCloud Endpoints Frameworks to stop managing your API.\n\n\u003cbr /\u003e\n\n\nRemoving API management doesn't stop your API from being served. If you want\nto stop serving your API, you can either disable the application on the **App\nEngine Settings** page in the Google Cloud console, or\nyou can delete the Google Cloud project. See [Disabling\nan application and shutting down a project](https://cloud.google.com/appengine/docs/flexible/python/managing-projects-apps-billing#disabling_an_application) for more information.\n\n\u003cbr /\u003e\n\nTo remove API management:\n\n1. Backup your API project's `web.xml` and `appengine-web.xml` files.\n\n2. In your API project's `web.xml` file, remove the following:\n\n - The `endpoints-api-configuration` filter.\n - The `endpoints-api-controller` filter.\n - The `endpoints-api-configuration` filter-mapping.\n - The `endpoints-api-controller` filter-mapping.\n\n After deleting the filters and filter mappings, your `web.xml` should\n be similar to the following: \n\n \u003cweb-app xmlns=\"http://xmlns.jcp.org/xml/ns/javaee\"\n xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n xsi:schemaLocation=\"http://xmlns.jcp.org/xml/ns/javaee\n http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd\"\n version=\"3.1\"\u003e\n \u003c!-- Wrap the backend with Endpoints Frameworks v2. --\u003e\n \u003cservlet\u003e\n \u003cservlet-name\u003eEndpointsServlet\u003c/servlet-name\u003e\n \u003cservlet-class\u003ecom.google.api.server.spi.EndpointsServlet\u003c/servlet-class\u003e\n \u003cinit-param\u003e\n \u003cparam-name\u003eservices\u003c/param-name\u003e\n \u003cparam-value\u003ecom.example.skeleton.MyApi\u003c/param-value\u003e\n \u003c/init-param\u003e\n \u003c/servlet\u003e\n \u003c!-- Route API method requests to the backend. --\u003e\n \u003cservlet-mapping\u003e\n \u003cservlet-name\u003eEndpointsServlet\u003c/servlet-name\u003e\n \u003curl-pattern\u003e/_ah/api/*\u003c/url-pattern\u003e\n \u003c/servlet-mapping\u003e\n \u003c/web-app\u003e\n\n3. In your `appengine-web.xml` file, remove the line that defines the\n `ENDPOINTS_SERVICE_NAME` environment variable. If `ENDPOINTS_SERVICE_NAME`\n is the only environment variable that you have defined, remove the entire\n `env-variables` section.\n\n4. Clean your project and then build your API:\n\n ### Maven\n\n ```bash\n mvn clean\n mvn package\n ```\n\n ### Gradle\n\n ```bash\n gradle clean\n gradle build\n ```\n5. Redeploy your application:\n\n \u003cbr /\u003e\n\n ### Maven\n\n ```java\n mvn appengine:deploy\n ```\n\n ### Gradle\n\n ```java\n gradle appengineDeploy\n ```\n\n \u003cbr /\u003e\n\nAfter you redeploy your application, Cloud Endpoints Frameworks stops managing\nyour API.\n\nVerifying API management removal\n--------------------------------\n\nTo verify that Endpoints Frameworks is no longer managing your API:\n\n1. In the Google Cloud console, go to the **Endpoints** \\\u003e **Services** page.\n\n\n [Go to the Endpoints Services page](https://console.cloud.google.com/endpoints)\n\n \u003cbr /\u003e\n\n2. Write down the number of requests to one of the methods in your API.\n\n3. Click the `View logs` link for the method.\n\n4. In the `Produced API` log, write down the date and time of the most recent\n log entry.\n\n5. Send some requests to the method in your API.\n\n6. In the Google Cloud console, go to the **Endpoints** \\\u003e **Services** page.\n\n\n [Go to the Endpoints Services page](https://console.cloud.google.com/endpoints)\n\n \u003cbr /\u003e\n\n The request counter for the method isn't updated.\n7. Click the `View logs` link for the method.\n\n The `Produced API` log doesn't contain log entries for the requests that\n you sent.\n\nRemoving dependencies in your build configuration\n-------------------------------------------------\n\nAlthough not required, you might want to remove dependencies in your build\nconfiguration.\n\nTo remove dependencies in your build configuration:\n\n1. Backup your `pom.xml` file or your `build.gradle` file.\n\n2. Remove the following dependencies:\n\n - `endpoints-management-control-appengine`\n - `endpoints-management-control-appengine-all`\n - `endpoints-framework-auth`\n3. Clean your project and then build your API:\n\n ### Maven\n\n ```bash\n mvn clean\n mvn package\n ```\n\n ### Gradle\n\n ```bash\n gradle clean\n gradle build\n ```\n4. Redeploy your application:\n\n \u003cbr /\u003e\n\n ### Maven\n\n ```java\n mvn appengine:deploy\n ```\n\n ### Gradle\n\n ```java\n gradle appengineDeploy\n ```\n\n \u003cbr /\u003e\n\n5. Test your API to make sure it is working as expected.\n\nDeleting the managed service\n----------------------------\n\n\nEndpoints Frameworks uses Google's Service Management to manage your API.\nWhen you deployed the OpenAPI document by using the `gcloud endpoints services\ndeploy` command, the command used Service Management to create a\nmanaged service for your API. If you don't need the data on the\n**Endpoints** \\\u003e **Services** page and in the **Produced API** log on the **Logs Viewer**\npage, you can delete the managed service for your API, which removes the data\nfrom the Google Cloud console.\n\n\u003cbr /\u003e\n\nTo delete the managed service:\n\n1. Make sure that the gcloud CLI (`gcloud`) is authorized to access your\n data and services on Google Cloud:\n\n gcloud auth login\n\n2. Enter the following to display the project IDs for your Google Cloud\n projects:\n\n gcloud projects list\n\n3. Using the applicable project ID from the previous step, set the default\n Google Cloud project to the one that your application is in:\n\n gcloud config set project [YOUR_PROJECT_ID]\n\n4. Obtain the name of all managed services in your Google Cloud project:\n\n gcloud endpoints services list\n\n5. Delete the service from Service Management. Replace\n \u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e with the name of the service you want\n to remove.\n\n ```\n gcloud endpoints services delete SERVICE_NAME\n ```\n\n Running `gcloud endpoints services delete` doesn't immediately delete the\n managed service. Service Management disables the managed service for\n 30 days, which allows you time to restore it if you need to. After 30 days,\n Service Management permanently deletes the managed service.\n\nWhat's next\n-----------\n\n- To restore a managed service, see\n [Restoring a managed service](/endpoints/docs/frameworks/java/restore-managed-service).\n\n- For information on the `gcloud` commands used on this page, see the\n [`gcloud` reference](/sdk/gcloud/reference).\n\n- For information on Service Management, see\n [Creating and deleting managed services](/service-infrastructure/docs/create-services)."]]