Skip to main content

 –

Changing the storage destination for the import data wizard, BIX, and file listeners

Suggest edit Updated on August 16, 2021

Use dynamic system settings to change the storage destination used by the import data wizard, BIX, and file listeners to store files. For example, for a multi-node system, you can set the destination to a shared location so that a user can access files from any node in the system.

  1. In the header of Dev Studio, click CreateSysAdminDynamic System Settings.
  2. Enter a short description for the setting.
  3. In the Owning Ruleset field, enter Pega-Engine.
  4. In the Setting Purpose field, enter storage/class/defaultstore:/type.
  5. Click Create and open.
  6. In the Value field, enter the value for the setting. For example, filesystem, aws-s3, or azureblob.
    Note: filesystem is shared only when there is a network drive attached to each machine.
  7. If you are using aws-s3 or azureblob, configure the following additional settings:
    aws-s3
    • storage/class/defaultstore:/bucket – Required. Enter the AWS bucket name.
    • storage/class/defaultstore:/accesskeyid – Enter your AWS access key. The key is optional if you are using EC2 instances with attached IAM roles; otherwise, it is required.
    • storage/class/defaultstore:/secretaccesskey – Enter your AWS secret key. The key is optional if you are using EC2 instances with attached IAM roles; otherwise, it is required.
    • storage/class/defaultstore:/rootpath – Optional. Enter the root path under the bucket for this share.
    • storage/class/defaultstore:/kmsencryptionkeyid – Optional. To read or write encrypted files, enter the Amazon Key Management System (KMS) encryption key ID.
    azureblob
    • storage/class/defaultstore:/bucket – Required. Enter the Azure container name.
    • storage/class/defaultstore:/accesskeyid – Required. Enter your Azure user name.
    • storage/class/defaultstore:/secretaccesskey – Required. Enter your Azure secret access key.
    • storage/class/defaultstore:/rootpath – Optional. Enter the root path under the bucket for this share.
  8. Click Save.
    Note: You can also change the location using the prconfig.xml file or by updating the JVM arguments.
What to do next: For file listeners, you can view a list of storage destinations on the File Storage landing page. The landing page only displays storage destinations with a valid file specification and only repositories that are compatible with the file listener.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us