Basic Concept

Standard Bucket

Our standard approach at InsureMO for document storage during tenant setup is as follows:

• Each tenant is provided with a standard tenant bucket. For example, for the UAT tenant, the bucket format will be tenant-sg-uat-bucket. Each tenant bucket will have a unique physical endpoint address.

• The standard tenant bucket functions when the BFF (Backend for Frontend) calls the standard platform API. For example, the BFF may call the DMS API for document management or when the project team needs to deploy configuration data and temporarily store the configuration file.

• If your project team requires detailed bucket information, please ask the InsureMO SiteOps team for help.

Storage Method

The project team has three options for storing content in the BFF:

• For technical purposes, call the Container CloudDisk API. This allows you to configure the bucket and store documents in any location. It is more suitable for technical scenarios such as file integration. For guidance, see CloudDisk-Service.

• For business purposes, utilize the ICS DMS API (not the filesupport JAR mentioned in this document). This API facilitates saving files to the tenant’s standard bucket. It is commonly used for business documents, such as policy document, as it offers business ID indexing.

• For SAAS purposes, adopt the InsureMO iDocs offering, which provides the entire UI journey for document management.

Bucket Naming Rule

For each environment, a common bucket will be set up for each tenant. The bucket format is {tenant code}-{env bucket prefix}bucket, e.g., TenantCode-vela-smk-bucket, freshman-ptdev-bucket.

Within each bucket, separate folders are created underneath, typically categorized as follows:

Share Bucket

If the project team has specific usage requirements and wants to share the bucket with the client’s IT team, for instance, exposing the bucket to the client’s team to fetch data like batch printing PDFs, we recommend setting up a separate bucket. This approach ensures:

• A clean new bucket, free from any temporary files in the platform bucket.
• Easy control over both read-only and editable authorities.

Depending on the volume of business transactions and security considerations, buckets can be set up under either a client’s account or an InsureMO account.

It is preferable to set buckets up under a client’s account to reduce S3 costs (storage and transmission fees) and address security concerns. However, if data security and regulatory compliance are the primary concerns, it is recommended that the bucket be set up under an InsureMO account.

Environment Parameter (for Private Cloud)

Global

For S3

For Azure

For Aliyun

For SFTP

For Google

For Custom

Custom storage, You can store files and operate it in customized storage media through API

To enable this function, here is the steps

1. by passing field customAppName in AbstractFileRequest
2. implement the interface CustomFileSupportRest

**note: It is recommended to use this function through DMS **

POM Dependency

 			<dependency>
                <groupId>com.insuremo.vela</groupId>
                <artifactId>vela-file-support</artifactId>
                <version>${project.version}</version>
            </dependency>

Method Summary

FileSaveRequest

Used in save() method

FileSaveResult

Return of save() method

FileGetRequest

Used in get(), listVersion(), getObjectSize() method

FileDeleteRequest

Used in delete() method

FileCopyRequest

Use in copy() method

ObjectVersion

Return of listVersion() method