My Oracle Support Banner

Understanding and Debugging Scenarios and Workflows (Doc ID 1374694.1)

Last updated on DECEMBER 18, 2019

Applies to:

Oracle Commerce Platform - Version 2006.3 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Feb-2014***

Purpose

One of the features that developers frequently run into trouble with is Oracle ATG Scenarios and Workflows. This document provides information on how scenarios are configured, work, and how to troubleshoot common problems related to scenarios.

Scope

 

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 ScenarioManager, InternalScenarioManager, and WorkflowProcessManager components
 Scenario Configuration
 The scenarioManager.xml file
 What will the ScenarioManager use for hostname and drp port?
 What is the drp port and why do I need to configure that?
 Multiple Process Editor Servers
 ScenarioClusterManager
 Scenario Lifecycle
 Scenario Registry
 Scenario Tables
 New Scenarios
 Modified Scenarios
 Deleted Scenarios
 Global/Individual Servers Bootstrapping
 Scenario Execution
 Forcing Scenario Updates
 Scenario Admin Servlet
 Listing Scenario Instances
 Viewing Scenario State Machines
 Turning on Scenario Debugging
 Conclusion
 Rule 1: There must be a single Process Editor Server per set of scenario tables
 Rule 2: Always use the scenarioManager.xml file to declare your Process Editor Server instance

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.