This chapter covers the following topics:
The core Oracle Demantra configuration details are stored in multiple locations:
The desktop executables (Business Modeler, Demand Planner, Analytical Engine, and so on) get the configuration information from file Demantra_root\Demand Planner\Security Management\ds.ini. Parts of this are encrypted and must be edited with a utility provided by Oracle Demantra (encryption.exe); see Redirecting Demantra to a Different Database.
The Web-based products get configuration information from the APS_PARAMS table (accessed using Business Modeler) that is on the machine where the Web server is installed.
Other settings are stored in the Oracle Demantra database, in the form of parameters. You can also edit these through Business Modeler.
The Web-based products also use configuration information in the XML files.
This section summarizes the key settings that the Installer controls and indicates where those settings are stored. In this table, *** means that it is encrypted in the ds.ini file. NA means that the item is not applicable.
| Installer Screen | Installer Option | in APS_PARAMS Table | in ds.ini |
|---|---|---|---|
| DBA Information | DBA username (to access database as DBA and load data) | NA | NA |
| DBA Information | Password | NA | NA |
| DBA Information | Password | NA | Tnsname |
| Configure Oracle Database User | Database type | NA | DB Type |
| Configure Oracle Database User | User (to store Oracle Demantra data) | DBType | LogID*** |
| Configure Oracle Database User | Password | DBUser | LogPassword*** |
| Configure JDBC Connection* | Server name (host machine or IP address on which database resides) | DBName | ServerName |
| Configure JDBC Connection* | Port | DBPort | DBPort |
| Configure JDBC Connection* | Oracle SID | DBName | DBName |
| Specify Web Address | Root address and virtual directory | server.generalurl | NA |
Note: The Demantra installer configures the JDBC connection only for the Apache Jakarta Tomcat application server. Add the automatically created JDBC context XML file to your Tomcat deployment. If you are deploying Demantra with WebLogic or WebSphere, see Configure JDBC Connection.
The APSMode parameter (stored only in the ds.ini file) controls whether to use the Stand-Alone Integration Tool (aps.exe). This tool consists of a subset of the APS, packaged as an executable file.
The Installer automatically sets this parameter. This parameter is defined as follows:
0: Do not use Stand-Alone Integration Tool. When you use encryption.exe to edit ds.ini, only the General tab is displayed.
1: Use the Stand-Alone Integration Tool (Demantra_root/Demand Planner/Integration/aps.exe). Also, when you use encryption.exe to edit ds.ini, the ASP Stand Alone tab is displayed, in addition to the General tab.
For information on using aps.exe, refer to the Oracle Demantra Implementation Guide.
The Installer also sets parameters for the following purposes:
The tablespaces that Oracle Demantra should use.
The configuration of the administrator email account.
For these parameters, see the fine-tuning information in the Oracle Demantra Implementation Guide.
If the client machine does not have JDK version 1.6 or 1.7 installed, the Installer prompts you to download and install it. After installation, set JAVA_HOME to the JDK installation directory (for example, C:\Program Files\Java\jdk1.6.0_16).
The Installer also makes edits to the files mentioned below. If you make a change to a port or protocol or other, you must be sure to make the change in the following files:
Demantra_root/Collaborator/virtual_directory/WEB-INF/web.xml
The internet shortcuts in directory Demantra_root/Collaborator/Links.
If you are using Tomcat: Demantra_root/Collaborator/Tomcat/conf/ server.xml (refers to the Demantra host and port, as well as the path to the Demantra virtual directory).
If you are using WebSphere:
WAS_HOME/installedApps/host_name/demantra.war/demantra.war/WEB-INF/web.xml
WAS_HOME/config/cells/host_name/applications/demantra.war/ deployments/demantra/demantra.war/WEB-INF/web.xml
Back up any file before making edits, and then carefully search and replace as needed.
In Demantra 7.3.0 and later, the database connection (and data source configuration) is controlled by the Java Naming Directory Interface (JNDI).
If you are using the Apache Jakarta Tomcat application server, perform the following steps to redirect Demantra to a different database:
Using a text editor, open the file server.xml. This file is located in Demantra_install\Collaborator\Tomcat\conf.
Locate the section that begins with "Resource name="jdbc/DemantraDS."
Change the "url" parameter to specify the host name and SID of the new database. For example: url="jdbc:oracle:thin:@DB_hostname.mycompany.com:1521:DB_SID"
Change the "username" and "password" parameters as required. For example: username="demantra_prod1" password="DP123"
Save your changes.
Restart Tomcat.
If you are not using Apache Jakarta Tomcat, refer to your application server's version-specific documentation to learn how to modify the database hostname, username, password, and SID (system identifier) specified by the JNDI.
This section contains background information about how Oracle Demantra uses Java. The Oracle Demantra Web client (Demand Planner Web, Promotion Effectiveness, or Settlement Management) uses JRE. Each machine that runs the Web client should have JRE, which Demantra automatically downloads when necessary.
Note: JDK is needed:
Only if you are using Tomcat.
On the machine that runs Tomcat, not on the client machines.
In theory, JRE versions are generally backwards compatible. If you are using an older version of the Web client, you can use the same JRE as the current Demantra. This means that, from a single machine, you can log into different Oracle Demantra installations, even if they use different versions of Java. In such a case, each Oracle Demantra version is likely to have a different version of the JAR files.
It is possible, but tricky, to keep multiple versions of Java running on a single machine. Oracle recommends that you carefully remove all Java versions other than the current version used by Oracle Demantra. To remove them, use the Add or Remove Programs from the Control Panel.
It is also useful to check your PATH system environment variable. Java is added to this, and you should make sure it includes only the Java that you intend to use. Note that Oracle provides Java as well; you do not need to uninstall these, but you should probably remove those versions from the PATH system environment variable.
Finally, you should make sure that Internet Explorer is configured to use the correct Java version as follows:
Click Tools > Internet Options.
Click the Advanced tab.
Within the Java item, make sure that the correct version of Java is selected for use with applets, as specified in this manual.
Verify memory settings:
From the Windows Start menu, choose Settings, Control Panel, and then Java. The Java Control Panel dialog box appears.
Click the Java Tab.
From the Java Applet Runtime Settings section, click View.
Verify that the value of the field Java Runtime Parameters is at least -Xmx256M and is based on the client machine hardware/RAM capacity. Oracle recommends value -Xmx512M for heavy-duty client side use.
Oracle Demantra supports Tomcat Web Server version 5.5 and higher and requires the latest version of Java 1.6 or 1.7. For this release, Oracle tested with Apache Jakarta Tomcat 6.x.
This section briefly notes the differences between installing Tomcat in a production environment and installing Tomcat in a demonstration environment.
Apache Jakarta Tomcat 6.0 requires Sun JDK 1.6 or 1.7, latest version. You can get it for free from http://java.com. You do not have to pre-install it, but you should make sure you do not have an earlier version of JRE on the machine. If you do, uninstall it.
Install Apache Jakarta Tomcat as usual, except choose Demo for the Web Server type.
If prompted, specify the desired value for the JAVA_HOME system environment variable. During installation, you are prompted for this if more than one Java is installed on the machine.
The Tomcat default port is 8080. You can change the default configuration for the port manually in the file Demantra_root/ Collaborator/Tomcat/conf/server.xml.
Note: If you do use the 8080 port, note that the Oracle XDB database user tries to use that port. See troubleshooting information in the Oracle Demantra Implementation Guide.
If you chose the Demo Web Server type for a demonstration environment, you can add Start menu options to start and stop Tomcat. To start Tomcat:
From the Windows Start menu, select Programs.
Click Demantra > Demantra Spectrum release > Start Web Server.
Clear the Tomcat cache after you upgrade your Oracle Demantra version. To clear the Tomcat cache, delete the directory Demantra_root/Collaborator/ Tomcat/work/standalone/localhost. You may need to do this if you receive the Object Error message, discussed in the Oracle Demantra Implementation Guide.
It is safest to reinstall Oracle Demantra rather than to rename the root directory where it is installed. However, if you are using Tomcat, you can rename the Oracle Demantra root directory and redirect Tomcat. To redirect Tomcat, edit the file Demantra_root/Collaborator/Tomcat/conf/server.xml. In this file, edit the parameter docBase. This parameter should specify the full path to the Oracle Demantra virtual directory.
By default, the Tomcat log is written to the console. To reconfigure Tomcat to write its log to a file, edit the file Demantra_root/Collaborator/Tomcat/conf/server.xml.
Find the Logger section and edit it as follows:
<Logger name="tc_log"
path="logs/tomcat.log"
verbosityLevel = "INFORMATION" /> f
The data cleanup database package facilitates cleansing of extraneous data. This procedure is only intended for use by experienced consultants and should never be run on a production schema. It can be used to remove data from small, test systems prior to a full production data load.
It performs cleanup of the following:
Temporary objects
Level data
Integration-related settings
Warning: Back up the schema before running this package.
Before running the package:
Make sure there are no active connections to the schema before executing these procedures.
Make sure the application server is shutdown before executing these procedures.
After running the package, issue a COMMIT to make sure all transactions are committed.
Notes about running the package:
Alias levels may create infinite loops on the level tree; currently the process will stop deleting data once it looped more times than the number of levels in the system.
There are some levels that are protected from being deleted, see table PROTECTED_OBJECTS in the schema.
Objects that are not currently cleaned up are Worksheets, Users, Groups, Integration Profiles, Series, Series Groups, and Workflows.
This also calls clean_schema_int.
Procedure:
DATA_CLEANUP.clean_schema_temps(commit_point NUMBER DEFAULT DEFAULT_COMMIT_POINT );
Demantra objects affected:
DB_EXCEPTION_LOG, INTEG_STATUS, AUDIT_PROFILES, AUDIT_TRAIL, AUDIT_PROFILE_USERS, E1_SALES, E1_BRANCH, E1_CUSTOMER, E1_ITEM, E1_ITEM_BRANCH, T_SRC_ITEM_TMPL, T_SRC_ITEM_TMPL_ERR, T_SRC_LOC_TMPL, T_SRC_LOC_TMPL_ERR, T_SRC_SALES_TMPL, T_SRC_LOC_TMPL_ERR
DROP_TEMPS(0) is the standard procedure to drop temporary tables created by worksheet runs. See additional objects in clean_schema_int.
Command:
EXECUTE DATA_CLEANUP.CLEAN_SCHEMA_TEMPS; COMMIT;
Cleaning Up Level Data
This should not delete the default member 0 in each level.
Procedure:
DATA_CLEANUP.clean_level_data( commit_point NUMBER DEFAULT DEFAULT_COMMIT_POINT );
Demantra objects affected:
SALES_DATA, MDP_MATRIX and the General Level data and matrix tables PROMOTION, PROMOTION_DATA and PROMOTION_MATRIX.
Recursively deletes all members for level data except protected levels in PROTECTED_OBJECTS table and the default member.
Command:
EXECUTE DATA_CLEANUP.CLEAN_LEVEL_DATA; COMMIT;
These are mainly created by Oracle e-Business Suite collections.
Procedure:
DATA_CLEANUP.clean_schema_int(commit_point NUMBER DEFAULT DEFAULT_COMMIT_POINT);
Oracle Demantra objects affected:
DISPLAY_UNITS, REAL_VALUES (only update), DCM_PRODUCTS_UNITS, DCM_PRODUCTS_INDEX, INDEXES_FOR_UNITS, AVAIL_UNITS
Deletes levels from TGROUP_RES and removes the column from INPUTS.
Command:
EXECUTE DATA_CLEANUP.CLEAN_SCHEMA_INT; COMMIT;