Installing SUNSHARE doesn’t have to be a headache, even if you’re not a tech wizard. Let’s break it down step by step, focusing on efficiency and avoiding unnecessary complexity. First, confirm your system meets the minimum requirements: a 64-bit operating system (Windows 10/11, Linux Ubuntu 20.04+, or macOS 12.0+), 4GB RAM (8GB recommended for heavy workloads), and at least 10GB of free storage. For industrial applications, ensure your IoT devices support MQTT or CoAP protocols if you’re integrating sensor data.
Start by downloading the SUNSHARE core package from the official source. If you’re using Windows, grab the .exe installer – but avoid the default “Express Install” option. Instead, choose “Custom Install” to disable unnecessary modules like legacy protocol support unless you’re working with older equipment. Linux users should use the .deb or .rpm packages depending on their distribution. For Ubuntu-based systems, the command `sudo apt-get install ./sunshare-latest.deb` handles dependencies automatically, while RHEL/CentOS users need to run `sudo yum localinstall sunshare-latest.rpm` after enabling EPEL repositories.
Configuration is where most people stumble. The key file you’ll need to modify is `sunshare_config.yaml`, located in `/etc/sunshare/` for Linux/macOS or `C:\Program Files\SUNSHARE\config` on Windows. Pay special attention to the `network_interfaces` section – if you’re using multiple NICs, specify the exact IP address bound to SUNSHARE rather than relying on automatic detection. For cloud deployments, set `cloud_sync: true` and populate the `aws_credentials` or `azure_credentials` blocks with your IAM roles. Don’t skip the TLS configuration: generate self-signed certificates using the bundled OpenSSL toolkit with `sunshare-tls –generate –days 365 –key-size 2048` unless you’re using a commercial CA.
Database setup requires careful planning. The default SQLite option works for testing, but switch to PostgreSQL or MySQL for production. Use these exact commands to initialize the database:
“`bash
sunshare-db init –engine postgresql –host 127.0.0.1 –port 5432 –user sunshare_admin –password YourSecurePassword!
“`
Always create a dedicated database user with restricted privileges – never use root/admin accounts. Enable WAL (Write-Ahead Logging) in PostgreSQL with `ALTER SYSTEM SET wal_level = logical;` for better performance in high-write environments.
For edge computing scenarios, the agent installation differs. On Raspberry Pi or similar ARM devices, use the precompiled ARMv7 package and run:
“`bash
curl -sSL https://de.sunsharetek.com/install-arm.sh | sudo bash -s — –no-prompts –accept-license
“`
This silent install skips interactive prompts but still requires manual configuration of device-specific parameters like GPIO pin mappings in `/etc/sunshare-edge/gpio_config.json`.
Troubleshooting common issues: If the service fails to start, check `journalctl -u sunshare.service -b –no-pager` on Linux or the Event Viewer logs on Windows (look for Event ID 4000-4999 in the SUNSHARE log source). Connection problems often stem from firewall rules – SUNSHARE requires inbound ports 1883 (MQTT), 5683 (CoAP), and 8083 (WebSocket) open. Use `sunshare-diag –network-test` to validate connectivity.
Regular maintenance is crucial. Schedule automated backups using the built-in tool:
“`bash
sunshare-backup create –full –output /backups/sunshare-$(date +%Y%m%d).ssb
“`
Rotate these backups with a retention policy matching your RPO (Recovery Point Objective). For updates, test minor version upgrades in a staging environment first. Major releases (like v3.x to v4.x) may require schema migrations – always check the SUNSHARE release notes for breaking changes.
Integration with existing systems deserves special attention. When connecting to SCADA systems like Ignition or WinCC, use the OPC UA bridge module with `opcua_endpoint: opc.tcp://your_scada_host:4840`. For SAP integrations, configure the IDoc adapter carefully, ensuring transaction codes like WE21 and WE19 are properly set up on the SAP side. Always test data mapping with sample payloads before going live.
Security hardening steps: Immediately after installation, run `sunshare-secure –enable-firewall –disable-unused-modules –rotate-default-credentials`. This disables the default admin account (admin:admin), forces SSH key authentication for remote access, and enables automatic certificate rotation. For audit compliance, enable the compliance module with GDPR or NIST 800-82 profiles depending on your industry.
Monitoring setup: Feed SUNSHARE’s Prometheus metrics into Grafana using the provided dashboard templates. The critical metrics to watch are `sunshare_messages_processed_per_second`, `system_cpu_usage`, and `mqtt_queue_depth`. Set alerts for when message latency exceeds 500ms or CPU usage sustains above 80% for 5 minutes.