Integration WIS

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is one of the primary goals of the new integration architecture?

To eliminate the need for data extraction completely

To enhance user interface designs

To standardize ERP integration points (correct)

To reduce the number of data sources

What capability does the new architecture include regarding large datasets?

Complete storage of all data in one location

Transport large datasets broken down for efficient handling (correct)

Ensure all datasets are processed synchronously

Process large datasets without any breakdown

How does the new integration architecture aim to improve data processing speed?

By implementing asynchronous processing (correct)

By using synchronous processing methods

By decreasing the number of data sources

By relying solely on native database procedures

What happens if custom code references something in the private surface area in the Cloud?

It will fail the deployment checks Signup and view all the answers

What is a notable feature of the Windows Integration Server (WIS) overrides?

They can lead to breaking changes that are not documented Signup and view all the answers

When are direct database calls typically used?

When there is a large dataset and performance is critical. Signup and view all the answers

What is a characteristic of real-time calls made by Configured Commerce?

They enhance dependency on the ERP for data retrieval. Signup and view all the answers

What should be defined due to the dependency on the ERP for real-time calls?

A fallback process. Signup and view all the answers

In which situation is it recommended to use real-time functions sparingly?

When submitting orders via API calls. Signup and view all the answers

What type of data is essential for integration processes to run successfully within the Configured Commerce admin console?

Configuration or seed data provided manually. Signup and view all the answers

How should product inventory and pricing data be handled to optimize user experience?

By using real-time calls only when absolutely necessary. Signup and view all the answers

What scenario allows the use of web service calls rather than direct database calls?

For order submissions that need complex business logic processing. Signup and view all the answers

What integration architecture change was introduced with Configured Commerce 3.4?

A redesigned integration strategy. Signup and view all the answers

What is the primary function of the Windows Integration Service (WIS)?

To expose enterprise data and services to Optimizely Configured Commerce websites Signup and view all the answers

Which of the following statements about the integration processors is true?

They can run on both WIS and the Configured Commerce website server for development purposes. Signup and view all the answers

What types of integration tasks are identified in the overview?

Refresh and Submit Signup and view all the answers

Which component runs post-processor tasks during integration jobs?

The Configured Commerce website server Signup and view all the answers

Why is hosting the WIS on the Configured Commerce website server not recommended for production?

It affects performance and connectivity. Signup and view all the answers

What does a Refresh task in Configured Commerce involve?

Synchronizing new or updated data from ERP to the website Signup and view all the answers

What is an example of a Submit task in the context of Configured Commerce?

Order Submission Signup and view all the answers

Where should the SiteConnections.config file be placed for proper WIS operation?

Within the web applications root folder Signup and view all the answers

Study Notes

Windows Integration Service (WIS) Overview

The Windows Integration Service (WIS) provides a secure connection between Optimizely Configured Commerce and enterprise data sources, enabling seamless data integration.
WIS resides within the firewall and polls the commerce site for integration tasks, executing both real-time and batch jobs.
Integration tasks are executed on the WIS server, with pre- and post-processors running on the website server.
For development purposes, integration processors can be configured to run on the website server, but this is not recommended for production environments due to performance concerns.

Integration Architecture

Configured Commerce integration tasks are classified into two types: Refresh (pull) and Submit (push).
Refresh (pull) tasks retrieve data from the ERP system, such as products, inventory, and customers, ensuring data synchronization with Configured Commerce.
Submit (push) tasks send data created on the website to the ERP system, including order submissions and customer information.
Integration can be achieved through direct database calls for large datasets or performance-sensitive scenarios.
Web service calls are preferred for integration tasks that require complex business logic, such as order submission.

Real-time Calls

Configured Commerce can utilize real-time calls to fetch data from the ERP on demand, but this data is not stored in the Configured Commerce database.
Real-time calls are suitable for tasks like inventory validation at checkout, product inventory and pricing, and credit card authorization.
Excessive real-time calls can impact performance and user experience, so they should be used judiciously and only when there is no alternative solution.

Configured Commerce Admin Console (AC)

The AC requires certain configuration or seed data for successful integration processes, which can be manually imported or entered.
Example data includes product categories, product attributes, warehouses, and locations.

New Integration Architecture (Introduced in Configured Commerce 3.4)

The new architecture was designed to improve integration capabilities, optimize performance, and enhance flexibility.
Key features:
- Metadata/configurable data extraction to minimize code dependencies.
- Bidirectional data transfer (pull and push).
- Direct data interactions for efficient data exchange.
- Standardized ERP integration points with defined interfaces.
- Improved logging and alerting system.
- Delta datasets to minimize data transfer and workload.
- Accommodate large datasets by dividing them for transport.
- Asynchronous processing to eliminate web service call delays.
- Multi-threaded data transcription for enhanced performance.
- Single WIS to handle unlimited connections.
- Support for multiple data sources.

Windows Integration Server (WIS) Overrides

Overrides in the WIS do not have backward compatibility guarantees.
Breaking changes may occur in the WIS, and overrides should be made with caution.
Changes to the public surface area (method signatures and constructors) are documented as breaking changes.
Any modifications in the private surface area will cause deployment failures.
WIS code is not deployed in the site and is not checked for backward compatibility.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Description

This quiz covers the Windows Integration Service (WIS) in the context of Optimizely Configured Commerce. It discusses its architecture, data integration tasks, and the differences between refresh and submit processes. Gain insights into how WIS ensures seamless data synchronization and performance considerations for different environments.