Archive and Purge Configuration

Edit online

By default, the archived files are stored in the java.io.tmpdir/tenant_id location. For example, if java.io.tmpdir is /tmp and tenantId is default, the location is /tmp/default. However, you can store the archives in your preferred location. You can use the Archive file location field to set a different location to save archived files. This setting performs the same operation as the backupsharedFilelocation extended setting.

It is recommended to configure an alternate storage location for the archive files. If you use the default location, it uses the webMethods API Gateway disk space.

To configure the archive and purge settings

  1. Expand the menu options icon menu_options, in the title bar, and select Administration.
  2. Select Manage Data.
  3. Click Configuration.
  4. Type a new location to store the archives, in the Archive file location field.
    You must provide the complete path of the location in which you want to store the archives. webMethods API Gateway creates a folder called default, in the specified location and stores all the archive files in default folder, created in the specified location. For example, if you specify the location as C:\SoftwareAG\APIGateway, a folder called default is created in the webMethods API Gateway folder and archives are stored in this location.
  5. Purge throttle per second controls the number of documents to be purged per second. The default value is 1000. If the date range you selected for purge has 10000 documents, then it takes 10 seconds to complete the purge operation. The default value of 1000 must work for most of the cases. Increasing the value will increase the purge performance (speed). On a flip side, this may cause memory pressure on external Elasticsearch if the size of the documents being purged are high.