Installing and configuring Business Applications¶
Business Applications¶
Business Applications are packaged applications designed to support specific business tasks for users who rely on operational or organizational data, but who are not traditional Dataiku DSS users. They reduce the effort required to apply business expertise to data-driven capabilities and help organizations maximize the value of their data.
Business Applications provide rich, task-focused user interfaces and are tightly integrated with Dataiku DSS data, automation, and governance capabilities. As native DSS components, they benefit from built-in data integration, security, distribution, and lifecycle management.
Business Applications are distributed through the DSS Business Application Store and can be interacted with in two ways:
End users access Business Applications through dedicated, interactive application interfaces focused on completing specific tasks. These interfaces are available from the DSS sidebar after logging in.
Administrators manage Business Applications through dedicated administration features in DSS, which allow them to install, configure, and manage applications. In addition, each Business Application includes an embedded administration interface for application-specific settings.
A Business Application can support multiple instances in order to serve different teams or use cases.
Note
Business Applications are available starting with DSS 14.4 as part of the Dataiku Enterprise edition or an Enterprise AI Package.
Users must have a Data Designer license or higher to use them.
Installing a Business Application¶
Installing Business Applications is restricted to administrators.
Business Applications can be installed from the Business Application Store, accessible via ⋮⋮⋮ > Business Applications
Each Business Application requires a dedicated code environment to run. This code environment is created and built as part of the installation process.
Configuring a Business Application¶
Configuration is performed by administrators and typically includes the following steps:
Environment mapping
Define how the connections required by the Business Application are mapped to the connections available on the DSS instance, and specify where the Business Application backend runs (locally or using a containerized execution configuration).
Permissions
Define which user groups can view and access the Business Application, and which groups are allowed to create new instances.
Define under which user account the backend of Business Application instances runs. This can be:
A single, fixed account for all instances
The account of the user creating the instance, without the possibility to change it
Configurable by the user at instance creation time
Note
Permissions defined at the Business Application level control visibility and instance creation, while permissions defined at the instance level control access to individual instances.
Creating Business Application instances¶
Once a Business Application has been installed and configured, it must be instantiated before it can be used. Multiple instances can be created to support different teams or use cases.
Administrators can create instances from the Business Application configuration page (⋮⋮⋮ > Business Applications > Instances)
Non-administrator users with Create permission can create instances directly from the Business Application page, accessible from the DSS sidebar.
When creating an instance, users must provide:
A name
A project key to uniquely identify the instance
An optional description
If the Business Application has been configured to allow runtime account overrides, users can also select the account under which the instance backend runs.
After creation, instance-level permissions must be configured to define which users or groups can access the instance. To update these permissions, navigate to the instance, open … > Settings and configure the instance like a classic DSS project.
Note
Instance permissions are independent from Business Application permissions and must be explicitly configured for each instance.
To use a Business Application instance, users must have both View permission on the Application and Read permission on the instance.
Once instance-level permissions are configured, remaining instance-specific configuration can be done in the main screen of the application instance.
Upgrading a Business Application¶
Upgrading Business Applications is restricted to administrators and is performed from the Business Application Store.
During an upgrade, the Business Application is updated to a new version. A new dedicated code environment may be required and must be built.
Instances created after the upgrade use the new version, but existing instances are not upgraded automatically. Existing instances continue to run on the previous version until they are explicitly upgraded. Instance can be manually upgraded from Business Application configuration page (⋮⋮⋮ > Business Applications > Instances). A Python API is available to assist with upgrading multiple instances programmatically.
The code environment from the previous version is not automatically deleted. It can be safely removed manually once all instances have been either migrated to the new version or deleted.