SKP Deployment Models

SKP Deployment Models

• There are two deployment models for the Migrate Solution on SKP, depending on the customer's hosting requirements.

Customer-Hosted Architecture (Hybrid)

• Data is hosted by the customer in their own environment.
• Software communicates with the data, rather than bringing the data to the software.
• High-level flow for customer-hosted architecture:
  • Data team members log in to SKP via the Internet.
  • SKP connects to the data environment via the Syniti Connector on the Customer's network.
  • Data team members access SKP functionality via the Internet.
  • Data team members access working databases within their internal company network.
  • Data is loaded to and from Source and Target systems behind the company's firewall.

Syniti-Hosted Architecture

• Syniti hosts the working and snapshot data in their cloud environment.
• High-level flow for Syniti-hosted architecture:
  • Data team members log in to SKP via the Internet.
  • SKP connects to the data environment via the Syniti Connector on the Syniti cloud environment.
  • Data team members access working data outside of the company's firewall.
  • SKP crosses the company's firewall to extract and load data to and from Source and Target systems.

SKP Deployment Models

• There are two SKP Deployment Models depending on customer hosting requirements: Hybrid option and Full Cloud option.
• In the Hybrid option, the customer hosts their own data, and the software interacts with the data in the customer's environment.
• In the Full Cloud option, Syniti hosts the customer data in their cloud environment.

Customer-hosted Architecture (Hybrid)

• The customer hosts data in their environment, and the software connects to the data via the Syniti Connector running on the customer's network.
• Data team members access the SKP functionality via the internet.
• Data team members access working databases within their internal company network.
• Data is loaded to and from source and target systems behind the company's firewall.

Syniti-hosted Architecture

• Syniti hosts the working and snapshot data in their cloud environment.
• Data team members access working data outside of the company's firewall.
• The SKP crosses the company's firewall to extract and load data to and from source and target systems.

Migrate Setup - Naming Conventions

• Working Database: WRK()(), e.g., WRKMM, WRKMM2D.
• Source Snapshot Database: SRC, e.g., SRCJDE.
• Target Snapshot Database: TGT(_CLIENT), e.g., TGTS4H, TGTS4H_600.

Migrate Setup and Naming Conventions

• All uppercase letters are used in database setup to ensure case sensitivity.
• Underscores are used to separate words in database naming conventions, enhancing readability.

Migration Prefixes

• Unique two or three-letter prefixes are used to identify active migration datasets.
• These prefixes help in grouping, sorting, and identifying tables, reports, and other related components.
• Common migration prefixes and their corresponding datasets are:
  • MM: Material Master
  • CM: Customer Master
  • VM: Vendor Master

Learn about the two SKP Deployment Models, including the Hybrid option where customers host their own data and the Full Cloud option where Syniti hosts the customer data.