Oracle Endeca Workbench deployed in a production environment

This deployment approach calls for Oracle Endeca Workbench to act directly on the production Dgraph cluster.

Note: This approach is often not recommended, as it allows changes to be made to a production application and requires unregulated updates to the production Dgraph cluster. However, some deployments may not find these concerns significant and may choose to deploy with this approach.

Without any configuration, the Deployment Template integrates with a Workbench in its local environment and Oracle Endeca Workbench assumes direct control of all of the Dgraphs provisioned for the deployed application. This means that no further configuration is required when deploying this approach in production.

It is important to note that most changes saved in Oracle Endeca Workbench are deployed to the production servers immediately when the Save Changes button is clicked in the Workbench. There are two exceptions to this behavior.

Changes that require a baseline update to apply are picked up by a scheduled baseline update. This includes changes to stop word configuration.
Changes to dynamic business rules must go through Oracle Endeca Workbench approval workflow before they are exposed in the production Dgraph. These changes are applied to the production Dgraphs when the Save Changes button is pressed, but may not be exposed to the end user until they have been approved in Oracle Endeca Workbench.