Overview

This article provides a comprehensive guide for Database Administrators planning to migrate the 360Suite repository and/or 360Eyes databases from PostgreSQL or another unsupported/outdated DBMS to a supported enterprise database platform (e.g., SQL Server, Oracle).

It covers:

• Migration strategies (data migration vs fresh installation)
• Prerequisites and technical steps
• Key considerations and best practices

Key Considerations

Role of Databases in 360Suite / 360Eyes

• 360Suite database: Stores application configuration and task definitions
• 360Eyes database: Stores monitoring data collected by jobs

⚠️ Important dependency:

• Changing the 360Suite database impacts 360Eyes
• Changing the 360Eyes database does NOT impact 360Suite

👉 If migrating both, ensure the correct sequence and validation.

Will SQL Server or Oracle Improve Performance?

PostgreSQL is fully supported and performs well with 360Suite.

Switching to SQL Server, Oracle, or another enterprise database may help if:

• These platforms are already standardized internally
• Your organization has strong DBA expertise on them

✅ In most cases, performance depends more on:

• Server sizing
• Database tuning
• Overall infrastructure configuration
  than on the database engine itself.

Migration Strategy Options

Option 1 — Data Migration (Recommended when history is required)

Best Practices

1. Create new empty databases/schemas in the target DBMS
2. Configure connections in the Admin Console
3. Let 360Suite generate tables and schema automatically
4. Migrate historical data using:
   • Your DBA team tools (export/import)
   • Or Wiiisdom migration service (see below)

Option 2 — Fresh Installation (Simpler approach)

Use this when historical data is not required.

Steps

1. Export existing tasks/jobs
2. Install the latest 360Suite version
3. Configure new database connections
4. Import tasks/jobs into the new environment

Prerequisites

Before starting:

• Full access to source and target databases
• Access to 360Suite Admin Console
• Backup of current JDBC credentials
• JDBC driver for the target database
• DBA tooling for data migration (if applicable)

Technical Migration Procedure

1. Prepare Target Database

• Create a new schema
• Assign a user with full control permissions

2. Install JDBC Driver (if not PostgreSQL)

1. Stop Tomcat server
2. Add JDBC .jar to:

   <360Suite Tomcat>/webapps/360.suite/WEB-INF/lib
   

3. Restart Tomcat

3. Configure Database Connections

For 360Suite

• Go to Admin Console → General Parameters → Database
• Update JDBC configuration
• Save changes

For 360Eyes

• Go to Admin Console → 360Eyes Configuration
• Update or create repository with new JDBC credentials

4. Migrate Data

• Use export/import tools (file-based migration recommended)
• Example tool used by engineering: RazorSQL (tested internally)

⚠️ Data migration tooling and execution are out of 360Suite support scope and typically handled by DBAs.

5. Validate Migration

After migration:

• Check configuration integrity in Admin Console
• Validate:
  • Task definitions
  • Schedules
  • 360Eyes collected data (if applicable)

Professional Migration Service (Optional)

Wiiisdom offers a Solution Engineering migration service:

• Uses internally developed scripts
• Supports PostgreSQL / HANA / deprecated databases → SQL Server / Oracle / other supported databases migration
• Includes scoping and assistance

📩 To request:

• Contact your Account Manager
• Or open a support ticket with: "DB Migration Service – Solution Engineering"

⚠️ Subject to availability and may include additional fees

Additional Resources

• 360Suite - Supported Platforms (PAM)
  
• How to migrate 360Cast Tasks from 360 Legacy to 360 Web Platform
  
• 360Suite Update & Technical Dependencies
• Installation Guide

Summary