Configuring Application Archives

An application archive containing encrypted profiles require keystore configuration.

To use a non-encrypted profile when deploying an application archive, there is no need to configure an application archive.

This functionality is not supported with the local mode.

BWAdmin Command Line

Use the following command line to configure an application archive: 

BW_HOME\bin>bwadmin config -d <domain name> -keyStoreFile <keystore file path> -keyAlias <alias name> -keyStorePassword <keystore password> -keyStore <keystore file name> -keyAliasPassword <key alias password> archive <name of archive>

Admin UI

    Procedure
  1. Go to Application Archive Level 1 page and click Configure.

  2. Optionally, go to the Application Archive Level 2 page and click Configure.

    3. You can upload the Keystore file to the database by clicking the Upload button.

  3. Provide the following encryption settings:
    • Keystore File Name
    • Keystore Type - It is automatically populated based on the type of keystore file provided. The following keystore file types are supported:
      • JKS
      • JCEKS
      • PKCS12
    • Keystore Password
    • Key Alias Name
    • Key Alias Password
  4. Click Configure Archive.
    A success message is displayed.

    Note: After configuring the archive, a copy of the Keystore file is stored in the database. When the domain is spanned, the Keystore copy file is created in the remote agent.

REST API

To perform the same operation from REST API, follow the below APIs to encrypt, decrypt, and configure the archive:

Encrypt profile:

http://<Hostaddress>:<port>/bw/v1/domains/<domain_name>/archives/encrypt?name=<archive_name>

Decrypt profile:

http://<Hostaddress>:<port>/bw/v1/domains/<domain_name>/archives/decrypt?name=<archive_name>

Configure the archive:

http://<Hostaddress>:<port>/bw/v1/domains/<domain_name>/archives/config?name=<archive_name>

For more information, see Accessing the BWAgent REST API with the Swagger UI.