This chapter covers the following topics:
If you loaded a large database dump file, Oracle recommends that you run database procedure REBUILD_SCHEMA to make the database run more quickly, before you start using Oracle Demantra. This procedure requires tablespaces equal in size to the current tablespaces.
REBUILD_SCHEMA performs these tasks:
Rebuilds table indexes
Rebuilds sales_data and mdp_matrix, large, core tables used by Oracle Demantra
Analyzes all the tables in the schema
For performance reasons, it is also useful to move each large table into its own tablespace. The Installer places some of the tables into their own tablespaces, depending on your choices, but you may have additional large tables. The following sample SQL moves the table TABLENAME and its index into the tablespace called TS_TABLENAME:
declare
sqlstr varchar2(2000);
begin
sqlstr := 'alter table TABLENAME move tablespace TS_TABLENAME';
dynamic_ddl(sqlstr);
for idx in (select index_name from user_indexes where table_name = 'TABLENAME')
loop
sqlstr := 'alter index '||idx.index_name||' rebuild tablespace
TS_SALES_DATA_TEST_X';
dynamic_ddl(sqlstr);
end loop;
After moving tables to different tablespaces, you should run ANALYZE_SCHEMA again.
The Installer provides options to perform additional configuration steps that make the database work with certain Demantra products. You can perform these configuration steps afterwards instead, if necessary.
See Update Settlement Levels for Oracle Demantra Deductions and Settlement Management (DSM) for details.
If implementing Predictive Trade Planning (PTP), configure the Analytical Engine appropriately for Promotion Effectiveness. If you are also implementing Trade Promotion Optimization (TPO), configure the optimization methods as needed. For details, see the Oracle Demantra Analytical Engine Guide.
You need to run this script manually after installing or upgrading Demantra only if you did not specify a database user with full SYSDBA privileges when running the Installer. In this scenario, the Installer displays a message at the end of the installation/upgrade prompting you to run this script.
SYS_GRANTS.sql performs the following:
Adds 'EXECUTE' privileges to access DBMS_CRYPTO (UPGRADE_PASSWORDS): Provides the highest level of user password encryption.
Adds 'EXECUTE' privileges to access DBMS_LOCK: Provides as SLEEP operation for improved concurrency.
Adds 'EXECUTE' privileges to access V_$PARAMETER so that Oracle Demantra can better adapt to your database's configuration.
(10g only) Adds 'GRANT' privileges to access the package UTL_HTTP, which enables Oracle Demantra to send notification messages to the application server and engine.
(11g only) Adds an ACL to enable HTTP communications for Oracle Demantra to send notification messages to the application server and engine.
Syntax:
C:\DEMANTRA_INSTALL_DIRECTORY\Demand Planner\Database Objects\Oracle Server\admin> sqlplus SYS@SERVER as sysdba @sys_grants.sql DB_USER ACL_for_WebServerURL ACL_for_EngineServerURL
Where:
DEMANTRA_INSTALL_DIRECTORY is the location of the unzipped Demantra installation file
SYS is the DB user with SYSDBA privileges · SERVER is the DB server TNS name
DB_USER is the Demantra database user name (must be entered in upper case)
ACL_for_WebServerURL is the full path to the access control list (ACL) for the Web Server URL. If you pass the name ACL_DEFAULT it will use the ACL named /sys/acls/demantra.xml. The ACL will be created if it does not exist.
ACL_for_EngineServerURL is the full path to the access control list for the Engine Server URL. If you pass the name ACL_DEFAULT it will use the ACL named /sys/acls/demantra.xml. The ACL will be created if it does not exist.
The Web client includes Demand Planner Web, Promotion Effectiveness, and Settlement Management. It uses the Sun Java plug-in.
Verify that the plug-in version you specified in the Java Control Panel is correct. See Java Tips.
To use SSL security or if users need to work through a firewall, perform the following procedure:
When you install Oracle Demantra, be sure to configure all URLs with https instead of http.
Switch off the HTTP server on port 80. The procedure to perform this is dependent on the Web server.
Configure the Web server for SSL support. You will need to obtain a VeriSign certificate or equivalent certificate authority.
Configure the firewalls to allow connections to port 443.
Optional: Configure the firewall to disallow all communication to port 80 instead of disabling it on the Web server.
If you have a firewall between the Web Platform Server and the database, you will also need to open the port that is defined for the connection between the Application Server and the database. For Oracle, this port is 1521 by default.
If you change any of the default port numbers, make sure to also change them in the Oracle Demantra URLs, the Web server, and the firewall. See Other Configuration Files in this document.
If you want to enable mutual (client) SSL Authentication, set the client.ssl.authentication parameter in to "1" (true). You define this parameter in Business Modeler > Parameters > System Parameters > Application Server > DP Web. By default, this parameter is false, which means only standard (server) SSL authentication is supported.
After client SSL authentication is enabled, a pop-up dialog box appears prompting you to insert keystore, truststore locations and passwords. Once validated, Demantra will save these parameters in an encrypted file under the user.home/demantra directory for future logins.
Note: Demantra supports both standard and mutual (client) SSL Authentication. In IE 7.x, the Java plugin cannot obtain user credentials from the browser and users will be prompted to enter this information for every applet within the current Demantra page (in the Demantra Local Application, there may be between 2-4 applets).
To avoid this issue, it is recommended that the web server administrator exclude the Demantra .jar files from the Web Server Basic Authentication rules. To do this, add the following filter to the <files> directive in httpd-sll.conf:
<Files ~ “^(\.jar”> </Files>
You may need to adjust the Web Platform Server parameters settings, shown below. To edit these parameters, use the Business Modeler. See the Oracle Demantra Analytical Engine Guide.
| Parameter | Recommended Setting and Notes |
|---|---|
| MaxDBConnections | Number of concurrent users multiplied by 2 |
| DBIdleTimeOut | 300000 (5 minutes) This setting frees up unused database connections more quickly, because they overstress the database. |
| threadpool.update.data.manual.size: Update threadpool data manual size. threadpool.update.table.manual.size: Number of parallel manual update tables that the Applications server can handle per process. threadpool.update.comb.manual.size: Number of parallel manual update combinations that the Applications server can handle per table. threadpool.update.record.manual.size: Number of parallel manual update records that the Applications server can handle per combination. threadpool.update.data.batch.size: Update threadpool data batch size. threadpool.update.table.batch.size: Number of parallel batch (Integration/Ble) update tables that the Applications server can handle per process. threadpool.update.comb.batch.size: Number of parallel batch (Integration/Ble) update combinations that the Applications server can handle per table.threadpool.update.record.batch.size: Number of parallel batch (Integration/Ble) update records that the Applications server can handle per combination. |
Batch and manual update parameters |
| threadpool.level_method.size | Use a size that is less than MaxDBConnections and that also leaves space for other system processes. |
| threadpood.copy_paste.size | Use a size that is less than MaxDBConnections and that also leaves space for other system processes. |
| threadpool.query_run.size | Use a size that is less than MaxDBConnections and that also leaves space for other system processes. |
| threadpool.level_method.timeout | 300000 (5 minutes) This setting frees up unused threads. |
You may need to run some security configuration changes to use Workflow Manager with Oracle Demantra. See Configuring the was.policy File on the IBM Web site.
Graphs do not work with WebSphere. To work around this problem, rename the WebSphere archive file WebSphere_directory/AppServer/lib/chart.jar.
Rename the file using a different extension. This will allow WebSphere to use the chart class from the Demantra JAR file.
On older Windows NT versions, you may get errors when you run the Analytical Engine regarding 2K DLL missing.
To solve this, run the file mdac_typ.exe before running the Analytical Engine. It is in folder ../analytical engine/bin.
When using the Firefox Web browser, if a Demantra user closes the browser using the X icon, it is possible to restore the session by re-launching a new Firefox browser. In this scenario, the login page is not displayed and the user is not required to enter a username and password.
Caution: Use caution when downloading and installing any add-ons to the Mozilla Firefox Web browser. Some add-ons can, for example, compromise application security or cause issues when running Demantra worksheets. These customizations are not supported by Oracle.
It is the responsibility of your organization and your users to prevent unauthorized access to Oracle Demantra by configuring Firefox correctly.
Modify Firefox configuration settings as follows:
Select Tools > Options > Startup > Main tab.
Verify that the When Firefox Starts setting is NOT set to Show my windows and tabs from last time. Change this setting as required.
Navigate to the Security tab and verify that Remember password for sites is clear.
Save your changes.
Oracle requires that you or your users set the browser locale. The applet locale is based on the browser locale.
If you have set browser locale, Oracle Demantra can manage both the portal and applet. With client machine locale alone, Oracle Demantra can manage applets, but cannot determine the locale for portal parts.
If an applet starts as standalone, Oracle Demantra uses the client machine locale.
The instructions for setting the browser locale are in the Oracle Demantra User's Guide > First Time Login.
If you access Oracle Demantra from a remote system, for example, Oracle E-Business Suite, specify the URL that points to the landing page after you log out of the remote system.
Set parameter ExternalLogoutUrl; it has no default value. In Business Modeler, navigate to Parameters > System Parameters, navigate to System tab. In field Value, enter the URL.
When you upgrade, Oracle Demantra Installer runs an upgrade script that makes structural changes and populates data.
Prior to release 7.3.0, the script gathers product configuration data, creates configuration file appserver.properties, and puts the configuration data there.
When you upgrade from a pre-7.3.0 version to release 7.3.0 or later, the script gathers product configuration data from configuration file appserver.properties, deletes configuration file appserver.properties, and puts the configuration data into table APS_PARAMS. This process is not visible when you are running the Oracle Demantra Installer.
If the script fails to delete configuration file appserver.properties, it displays a warning message, with the full directory path to the file that asks you to manually delete it after installation. If the script fails to update table APS_PARAMS, it displays Business Modeler, System Parameters window. See the Oracle Demantra Analytical Engine Guide for information about the following parameters, then specify values for them.
workflow.group
server.generalurl
database.password
When you have finished, the installation process continues.