• 01 Aug 2022
  • 3 Minutes to read
  • Dark
  • PDF


  • Dark
  • PDF

Enhancements in this Release v8.6.7

July 25th, 2022                                                                                                              Version 8.6.7

The DL Asset Track platform now supports multitenancy, meaning a single instance can serve multiple users. This release has significantly improved the Operator onboarding process, and now each Operator is associated with a tenant.

All activities performed by Data Operators, Subordinates, and Participants under an assigned Operator are stored and tracked on the blockchain separately. This segregation is classified based on the corresponding tenant.

The DL Asset Track platform has a security update. All the existing webhook credentials stored in the database are encrypted. The enhancements in the code base now enable the platform to save the webhook credentials in encrypted form for any future use.

Additionally, by using the PM2/cluster module, Workflow Management Service now uses all the available CPU cores, improving the performance.

Updates for ASIK

  • Multitenancy support is enabled in ASIK Track. 
  • On creating a new user, a User ID is generated, which is used to access the ASIK APIs in the system. 
  • The system now supports Hyperledger Fabric 1.4x and Fabric 2.x versions that deliver support for privacy patterns, enhanced governance around smart contracts, and new options for operating nodes.
  • In ASIK microservices, SSL connection is now enabled to connect to the external services.
  • Unwanted transactional data is eliminated while inserted into Elasticsearch indices to reduce the memory occupancy in Elasticsearch.
  • ASIK Track APIs have updated validation messages.
  • Connector modules in ASIK microservices are updated to provide support for managed services.

Features Delivered in this Update

Multitenancy support

  • The Operator onboarding process is now defined in two distinct steps: 
    • Tenant creation. 
    • Operator or SCA (Supply Chain Admin) creation.
  • The onboarding process executes asynchronously, and ASIK handles the creation process.
  • After a tenant is created or onboarded, each API call to the ASIK service is modified to include the user-id and tenant-id in the call headers.
  • The data in the blockchain is stored tenant-wise, and each tenant has its dedicated chaincode on the blockchain.
  • Flexible tenant creation: user can provide peer type, peer region & server type. Tenant creation is now an automated process, saving time and simplifying the process.
  • Tenants are deactivated without manual intervention (but data will persist for the tenant). After a certain period, if a tenant is permanently de-boarded, only data clean-up activity is required.

Secure Webhook Credentials 

  • Webhook credentials are now stored in encrypted form instead of plain text format.
  • Existing webhook credentials are also migrated in encrypted format for future use. 

 Improved User Data Management

  • Enterprises can make configurations such as:
    • Select data storage – whether in a shared environment or a dedicated environment, providing flexibility and control.
    • Select the number of data source points for respective data storage.
    • Provide the region where the data will be stored.
  • Addition of User IDs instead of User card names.
  • Support of multiple accounts for the same user.
  • There is no overhead for integrating services to maintain the mapping of User Id and Card Name.
  • Migration of users and data involves fewer manual interventions.

Improved CPU core usage

  • CPU usage is now optimized, using PM2/cluster modes or alternate configurations to offer superior platform performance.

Graceful start

  • After a service is deployed to the server, the APIs will only start taking requests once all connections have been successfully established (DB, Queues, and ASIK Connections).

Technical Enhancements 

 ASIK Track APIs

  • For the following external services, an SSL connection and managed services support are offered to accomplish a variety of operations and effortlessly improve the company's core values:
    • Kafka v2.4.1
    • PostgreSQL v11
    • Redis v6
  • Validation messages are updated to showcase meaningful success/failure codes. 
 Elasticsearch furtherance
  • Data clean-up activity in Elasticsearch was done by:
    • Eliminating unused/redundant data while inserting it into Elasticsearch indices.
    • In ASIK Track Sync Service, transformation logic is updated to remove unused data while going to Elasticsearch.

For any questions, please email us at dl.releasenotification@dltlabs.io

Was this article helpful?

What's Next
Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.