Why is an Application Server Restart Required for Many Demantra Configuration and Data Changes?

(Doc ID 1069013.1)

Last updated on DECEMBER 18, 2017

Applies to:

Oracle Demantra Demand Management - Version 7.1 and later
Information in this document applies to any platform.
***Checked for relevance on 12-Nov-2013***


Goal


Why do we have to restart the Weblogic server in order to see configuration
changes made in Demantra?   Is this normal behavior?


The following example changes have been made:

1.  Create new series and  bounce just the
container.
Series name will exist in Worksheet Designer > Series tab > Available series list.
However, User is not able to move the new series from Available series list to Selected series list.

2.  Display Units assigned to the Item and Location level in Business Modeler.
Example: Business Modeler > Configuration > Configure Units for Levels
a.) Add Customer CCN for Level Name
b.) Add Pound for Level Unit
c.) Save and bounce the container.
d.) Go to any worksheet with Customer CCN as a level and select Display unit
drop down list.
e.) The new Pound unit doesn't exist in LOV.

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms