WSO2 Data Analytics Server (WSO2 DAS) is shipped with default configurations that allow you to download, install and get started with your product instantly. However, when you go into production, it is recommended to change some of the default settings to ensure that you have a robust system that is suitable for your operational needs. Also, you may have specific use cases that require specific configurations to the server. If you are a product administrator, the follow content provides you with an overview of the administration tasks that you need to perform when working with Data Analytics Server (WSO2 DAS).
Upgrading from a previous release
If you are upgrading from WSO2 DAS 3.0.1 to WSO2 DAS 3.1.0, see Upgrading from WSO2 DAS 3.0.1.
Changing the default database
To change the default database configurations for WSO2 DAS, see Working with Databases.
Configuring users, roles and permissions
The user management feature in your WSO2 DAS allows you to create new users and define the permissions granted to each user. You can also configure the user stores that are used for storing data related to user management.
- For instructions on how to configure user management, see WSO2 Administration Guide - Working with Users, Roles and Permissions.
- For descriptions of permissions that apply to WSO2 DAS users, see WSO2 DAS - Specific User Permissions.
After you install WSO2 DAS, it is recommended to change the default security settings according to the requirements of your production environment. As WSO2 DAS is built on top of the WSO2 Carbon Kernel (version 4.4.x), the main security configurations applicable to WSO2 DAS are inherited from the Carbon kernel.
If you are configuring your production environment, be sure to check the Security Guidelines for Production Deployment before applying any security configurations.
For instructions on configuring security in your server, see the following topics in the WSO2 Administration Guide.
- Configuring Transport-Level Security
- Using Asymmetric Encryption
- Using Symmetric Encryption
- Enabling Java Security Manager
- Securing Passwords in Configuration Files
- Resolving Hostname Verification
The WSO2 Carbon Kernal on which WSO2 DAS is built on supports a variety of transports.
For instructions on configuring these transports, see WSO2 Administration Guide - Working with Transports.
You can create multiple tenants in your DAS server which allows you to maintain tenant isolation in a single server/cluster. For instructions on configuring multiple tenants for your server, see WSO2 Administration Guide - Working with Multiple Tenants.
Configuring the registry
A registry is a content store and a metadata repository for various artifacts such as services, WSDLs and configuration files. In WSO2 products, all configurations pertaining to modules, logging, security, data sources and other service groups are stored in the registry by default.
For instructions on setting up and configuring the registry for your server, see WSO2 Administration Guide - Working with the Registry.
You can optimize the performance of your WSO2 server by using configurations and settings that are suitable to your production environment. At a basic level, you need to have the appropriate OS settings, JVM settings etc. Since WSO2 products are all based on a common platform called Carbon, most of the OS, JVM settings recommended for production are common to all WSO2 products. Additionally, there are other performance enhancing configuration recommendations that depend on very specific features used by your product.
For instructions on the Carbon platform-level performance tuning recommendations, see WSO2 Administration Guide - Performance Tuning.
For instructions to tune performance for a Spark cluster, see Tuning Performance for a Spark Cluster.
For instructions to tune performance for real time analytics, see Tuning Performance for Real Time Analytics.
Changing the default ports
When you run multiple WSO2 products, multiple instances of the same product, or multiple WSO2 product clusters on the same server or virtual machines (VMs), you must change their default ports with an offset value to avoid port conflicts.
For instructions on configuring ports, see WSO2 Administration Guide - Changing the Default Ports.
Managing product features
Each WSO2 product is a collection of reusable software units called features where a single feature is a list of components and/or other feature. By default, WSO2 DAS is shipped with the features that are required for your main use cases.
For information on installing new features, or removing/updating an existing feature, see WSO2 Administration Guide - Working with Features.
Configuring custom proxy paths
This feature is particularly useful when multiple WSO2 products (fronted by a proxy server) are hosted under the same domain name. By adding a custom proxy path you can host all products under a single domain and assign proxy paths for each product separately .
For instructions on configuring custom proxy paths, see WSO2 Administration Guide - Adding a Custom Proxy Path.
Customizing error pages
You can make sure that sensitive information about the server is not revealed in error messages, by customizing the error pages in your product.
For instructions, see WSO2 Administration Guide - Customizing Error Pages.
Customizing the Management Console
Some of the WSO2 products, such as WSO2 DAS consist of a web user interface named the management console. This allows administrators to configure, monitor, tune, and maintain the product using a simple interface. You can customize the look and feel of the management console for your product.
For instructions, see WSO2 Administration Guide - Customizing the Management Console.
For instructions on applying patches (issued by WSO2), see WSO2 Administration Guide - WSO2 Patch Application Process.
Monitoring the server
Monitoring is an important part of maintaining a product server. Monitoring capabilities available for WSO2 DAS are listed below.
- Monitoring server logs: A properly configured logging system is vital for identifying errors, security threats and usage patterns in your product server. For instructions on monitoring the server logs, see WSO2 Administration Guide - Monitoring Logs.
- Monitoring Spark logs: WSO2 DAS generates logs to monitor the performance of Spark workers in a clustered set up. For more information, see Monitoring Spark Performance.
- Monitoring using JVM Metrics: WSO2 DAS is shipped with Metrics that allows you to monitor statistics of your server using Java Metrics. For instructions on setting up and using Carbon metrics for monitoring, see WSO2 Administration Guide - Using WSO2 Carbon Metrics.
JMX-based monitoring: For information on monitoring your server using JMX, see WSO2 Administration Guide - JMX-based monitoring.