Architecture

This is the core offer processing engine. It provides interfaces for multi-channel offer eligibility, validity and price evaluations.

Forwards the client login API calls to the Auth Center service.

Provides implementation for search and guided browsing for offers. The offers are indexed in this engine for fast searches.

Provides data models to TIBCO OPE through the Model Loading Engine.

TIBCO OPE supports two modes for loading models: online and offline.

Read models posted on TIBCO Enterprise Message Service (EMS) queues. For more information, see the EMS documentation.

Handles authentication and authorization.

Loads configuration changes without the need to restart micro services, and notifies applications that run TIBCO OPE Core Engine of changes to configuration information when the Model Loading Engine loads the data models.

Consul is the external configuration management tool.

Provides a wrapper service around any vendor-specific persistent storage system (such as Amazon S3), so that you can use your own object storage.

When the Model Loading Engine loads the product models into TIBCO OPE, they are stored in binary format in the object storage. They can then be pulled by TIBCO OPE Core, where they can be served to any of the customer-facing channels. In case TIBCO OPE needs to be restarted, or there is an error that requires an update, TIBCO OPE Core re-retrieves the models from Object Storage.

Retains data after a power shut off. TIBCO does not provide persistent storage, but does provide a vendor-agnostic wrapper service so you can use your own storage system (such as Amazon S3 or Azure Storage).