About updating Workbench configuration

One implication of the single-source business process is that configuration does not need to be uploaded to Oracle Endeca Workbench after it is initially uploaded.

That is, the Workbench is used as the primary source of configuration for a subset of files, and need not be updated with configuration from other sources. Because of this, the Deployment Template does not upload configuration settings to the Workbench during baseline or partial update scripts. It is expected that the Workbench is initialized with configuration when the application is deployed and that additional configuration updates are uploaded manually when necessary.

When deploying the application, users who have enabled integration with Oracle Endeca Workbench will run the initialize_services.[bat|sh] script to upload configuration to the Workbench. On an ad hoc basis, configuration can be uploaded to the Workbench to update any files that are not maintained by the Workbench. For example, if a new rule group is created and needs to be made available in Oracle Endeca Workbench, users can run the update_web_studio_config.[bat|sh] script to upload the latest configuration files to the Workbench. Note that this script merges the configuration files according to the previously defined process (skipping the merge step if no files are retrieved from the Workbench) before uploading to the Workbench, ensuring that only files that are not maintained in the Workbench are updated, and all changes developed and maintained in the Workbench remain there. The process of uploading configuration to Workbench requires obtaining locks on all Workbench configuration resources. This means that no locks may be held by users. The update script does not attempt to break locks, expecting that system administrators will ensure that Oracle Endeca Workbench is free of users before attempting to update the tool with new configuration.