Preparing for Installations and Upgrades

This chapter covers the following topics:

Pre-7.3.0.1 Upgrade Path
Installer Options Worksheet
Basic Preparation Checklist
Upgrade Preparation Checklist

Pre-7.3.0.1 Upgrade Path

If you are running a pre-7.3.0.1 version of Oracle Demantra, you must upgrade to 7.3.0.1 first and then upgrade to the latest version.

For more information, see Installing and Upgrading Oracle Demantra in the Oracle Demantra Installation guide.

Installer Options Worksheet

Note: Oracle does not support Microsoft SQL Server. Please monitor My Oracle Support for versions supporting SQL Server.

Note: When installing Demantra for the first time, install Tomcat version 8.5. If you are upgrading or re-installing Demantra, you only need to re-install Tomcat if the version installed is older than version 8.5.

To make installation quick and simple, use the following worksheet to collect the information that the Installer requires.

Screen	Item	Examples
DBA Information	DBA username	system
DBA Information	Password	manager
DBA Information	TNS Name	wysiwyg
Configure Oracle Database User	User	demo
Configure Oracle Database User	Password	d
Configure JDBC Connection*	Server name (host machine or IP address on which database resides)	wysiwyg
Configure JDBC Connection*	Port	1521
Configure JDBC Connection*	Oracle SID	usco
Database Options	Export by user	dp
Select Tablespaces Important: The default directory is the only tablespace used by Demantra. All tablespaces specified should be the same.	For default data	TS_DP
Select Tablespaces	For temporary data	TS_DP
Select Tablespaces	For sales data	TS_DP
Select Tablespaces	For index data	TS_DP
Select Tablespaces	For simulation data	TS_DP
Select Tablespaces	For simulation index data	TS_DP
Select Tablespaces	For sales data engine	TS_DP
Select Tablespaces	For sales data engine index	TS_DP
Specify Web Address	Root address	http://www/mycompany.com https://www.mycompany.com http://localhost:8080
Specify Web Address	Virtual directory	demantra
Designate Administrator Account	Mail server	mayflower.demantra.net
Designate Administrator Account	Administrator e-mail address	demantra-admin@acme.com
Designate Administrator Account	Administrator username	admin
Designate Administrator Account	Administrator password	admin

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.

DBA Information

The Installer must usually access your database as the database administrator so that it can create a new database user to store Demantra data (or modify an existing database user for that purpose). There are two options:

Enter a user with full SYSDBA privileges. Allow the Installer to automatically run a script that enables user password encryption and performs additional database configuration.
Do not enter a user with SYSDBA privileges. You will be prompted to run the SYS_GRANTS.SQL script manually at the end of the installation. Oracle recommends this option. For details, see Running SYS_GRANTS.SQL Script.

You will need to provide the basic information below:

Item	Details	Example
DBA username	Username that has DBA access to the database	system
Password	Password for that user	manager
TNS Name	Use the TNS name as specified in the tnsnames.ora file. To verify that you have the correct TNS name, enter the DOS command `tnsping <TNS_name>`. If the command returns successfully, you have the correct TNS name. Note that the TNS name is also referred to as the service name; it is often the same as the host name.	wysiwyg

Configure Oracle Database User

For your solution, the Oracle Demantra data is stored in a database user (for example, called dp). One of the most important considerations is deciding how to set up this database user. You have the following options:

If this database user is new, you can do either of the following:

Load the Oracle data model and demo that is supplied with the Installer.
Load a database dump file that was created from another Oracle database.

If you already have an Oracle database, you can do any of the following:

Replace the database user, which removes it entirely and replaces it with the Oracle data model and demo that is supplied with the Installer.
Upgrade the database user, which updates the schema and various default settings (such as parameter values).
Do nothing to the database user.

The Installer can create this database user for you, or you can create it ahead of time. If you create the database user, be sure to give the user DBA access.

For the Demantra database user, you will need the following information.

Item	Details	Example
User	Username where you will store the Oracle Demantra data	demo
Password	Password for that username	d

Configure JDBC Connection

Demantra uses a JDBC connection to access the database. When running the installer, specify the information in the table below to configure this connection for the Apache Jakarta Tomcat application server.

Item	Details	Examples
Server name	Specify the host machine or IP address on which the database resides	wysiwyg
Port	Specify the port to which the database is listening. If you are using Windows XP (not supported formally), avoid using the default port number.	1521
Oracle SID	Specify the Oracle SID or service name (Service_Name in the TNSNames.ora file). Note that the SID or service name is also called the database name; it is often the same as the host name. Note: If you are using Oracle 12c, enter the service name instead of the SID. See Additional Steps to Configure Oracle 12c.	usco

If you are deploying Demantra with WebLogic, or WebSphere, you must configure the data source after installing or upgrading. Oracle recommends performing this setup before deploying the Demantra WAR file.

For all supported application servers, the JNDI should be set to jdbc/DemantraDS. Note that JNDI is case sensitive. For additional details, please refer your Web application server's version-specific documentation.

For general information about JDBC and connection URLs, see Oracle Database JDBC Developer's Guide and Reference 10g.

Database Options

In most cases, the Installer loads a database dump file.

Item	Details	Example
Database to import	Choose one of the following: STANDARD CUSTOM: Your own database dump file that was exported from another Oracle database	-
Export by user	Name of the database user who created this dump file. Needed only if you are importing a custom database.	dp

Select Tablespaces

Oracle Demantra stores its data in the dataspace specified during the installation.

Specify Web Address

For the Web-based products, Oracle Demantra uses Web addresses that start with a core URL that you specify. You specify this URL in two parts as shown in the example below:

Item	Details	Example
Root Address	All Demantra Web addresses start with this URL. This address does not include the virtual directory. Instead of http, you can use https for SSL security; see also Configuring Web Applications for SSL and Firewalls	http://www.mycompany.com https://www.mycompany.com http://localhost:8080
Virtual Directory	The virtual directory is added to the root address in all Oracle Demantra URLs. This is case sensitive.	demantra

These two items are used together in all Oracle Demantra Web addresses. For example, the Web address for the Demantra Local Applicationis as follows:

http://<server name>/<virtual directory>/portal/loginpage.jsp

For example:

http://frodo/demantra/portal/loginpage.jsp

Designate Administrator Account

If you are using any of the Oracle Demantra Web-based software, Oracle Demantra can automatically send email on specific occasions, for example, within workflows.

To enable this functionality, you should set up an administrator email account on an SMTP server; this account will be the originator of all Oracle Demantra's automatic messages. You must make sure that Oracle Demantra has the needed permissions on the mail server.

Then, when you run the Installer, you will provide the following details of that account

Item	Details	Example
Mail server	Specify the SMTP server that is hosting the e-mail service	frodo.demantra.net
Administrator e-mail address	Specify the e-mail address of the administrator e-mail account	demantra-admin@acme.com
Administrator username	Specify the administrator username; this is usually the network username of the administrator	admin
Administrator password	Specify the administrator username; this is also usually the network username of the administrator	admin

You can also set up the administrator email account after running the Installer. See the fine-tuning information in the Oracle Demantra Implementation Guide.

Log Configuration

You can configure Installer logging settings either in the Installer screen or as you run it from the command line.

To modify the log configuration settings when running the Installer screens, double-click setup.exe to launch the Installer and then click Configure Log. Then, select from the following:

Default Log Configuration File (default setting): The Installer creates an installation directory defined by the environment variable %temp%. Once installation is complete, you can review the log file Oracle_Demantra_Spectrum.log from the %temp% location. For details, see Checking the Log Files and Tables.
Custom Log Configuration File: Select this option if you want to specify a file name and location where the log file will be located.
Custom Settings: Select this option to specify a file name and logging level (FATAL, ERROR, WARN, INFO, DEBUG, or TRACE).

To provide the command line arguments, use either of these methods:

Command line: Run the Installer from the command line and pass arguments:

${installer path}/install -D${argument}=${value}

For example:

install -DLOG_CONF_DIR="C:\conf" -DBACKUP_LOG_FILE=Y
Enhanced setup: On the setup menu, click Install Demantra Spectrum, then click Configure Log. Enter the arguments into the Log Configuration dialog.

The arguments are as follows:

Default (enhanced setup only): Use the default values.
Custom Log Configuration File (command line LOG_CONF_DIR): Specifies the directory where the Installer should find the log file. If you use the command line method and the directory has spaces or special characters, enclose (value) in double quotation marks.
Custom Settings > Log File Name (command line LOG_FILENAME): Specifies the fully-qualified filename of the log.
Custom Settings > Log Level (command line LOG_LEVEL): Specifies the contents of the log file. If you use the command line method, use FATAL, ERROR, WARN, INFO, DEBUG, or TRACE.
Backup > Backup Log File (command line BACKUP_LOG_FILE): Specifies whether the Installer should back up the log file. If you use the command line method to enable log backup, use Y, YES, or TRUE; to disable log backup, do not submit the argument.

The order of precedence for initializing the log file is as follows:

Custom Log Configuration File passed and file found: Uses the values in that configuration file.
Custom Log Configuration File passed and file not found: Uses the default values but will override them with values of any passed arguments.
Custom Log Configuration File not passed: Uses the default values but will override them with values of any other passed arguments.
No arguments passed: Uses the default configuration file values.
No arguments passed and default configuration fine not found: Uses the default values.

Basic Preparation Checklist

In addition to collecting information needed for the Installer, be sure to complete the following steps below in any order.

Item	Details
Decide SSL needs	Decide whether you will need to use SSL protocol for all pages. If so, obtain a VeriSign certificate or equivalent certificate authority.
Hardware and software requirements	See System Requirements. Oracle recommends that the machine on which you will run the Installer has at least 16GB of RAM. Install any patches or service patches for the third-party software that you use, including the database software.
Java	Check carefully for Java (JRE or JDK) versions that are older or newer than supported by Oracle Demantra. Remove these.
Oracle (if used)	If installing Demantra in a multi-byte language (Korean, Chinese, Japanese, or Russian), set the following initialization parameters on the Oracle database: NLS_LENGTH_SEMANTICS = BYTE· NLS_CHARACTERSET = AL32UTF8 NLS_LANG = language_territory.characterset Important: The NLS_LENGTH_SEMANTICS parameter must be set to BYTE on the database to provide compatibility with Oracle EBS. However, the Demantra products refer to the same parameter in the Demantra schema table DB_PARAMS, and in this table the parameter must be set to 'CHAR.' After installing Demantra, be sure to check the value of NLS_LENGTH_SEMANTICS in DB_PARAMS. If it is not set to 'CHAR,' then run the following command: `UPDATE db_params SET pval='CHAR' WHERE pname = 'nls_length_semantics';COMMIT;` More information on these parameters is in: Oracle Database Installation Guide 11g Release 1 (11.1) for Microsoft Windows > Configuring Oracle Database Globalization Support Oracle Database Globalization Support Guide 11g Release 1 (11.1) > Supporting Multilingual Databases with Unicode This setup is optional for English-only installations. Set the compatibility parameter in the init.ora file to 8.1.7 or higher. Make sure the NLS_DATE_FORMAT environment variable is set appropriately, the same as in the database. A typical format is MM-DD-YYYY HH24:MI:SS If you are performing a new installation, create tablespaces within Oracle for use by the Oracle Demantra database user. Oracle recommends that you set up tablespaces with the following names: TS_SALES_DATA TS_SALES_DATA_X TS_SALES_DATA_ENGINE TS_SALES_DATA_ENGINE_X If you are not familiar with Oracle tablespaces, consult an Oracle administrator or Oracle Support. If you use these standard names and map them in the standard way, it is easier for you to share your database with Oracle Support. See Installer Options Worksheet. You will need up to eight tablespaces. These four contain the data that is most commonly shared with Oracle Demantra. Caution: There is a known issue when using parallel hints to improve Demantra performance on Oracle 11g version 11.2.0.1 and earlier. If your Oracle 11g version is earlier than 11.2.0.1, refer to My Oracle Support Note 1249314.1 before installing Demantra.
Administrator e-mail account	Set up the e-mail account as needed, see Designate Administrator Account.
Terminal Services (if used)	Install this using Microsoft Windows Control Panel > Add/Remove programs.
Java (on each client machine)	Use the Java Plug-in control panel to: Clear the Java cache and any competing Java certificates. Set the maximum Java cache to 100 MB (or higher).
Windows settings (on each client machine)	Locale: <your locale> The locale generally controls the date, time, and number displays.
Review common installation issues	Read and understand My Oracle Support Note 430913.1, Common issues or problems encountered when running the Oracle Demantra Installation.

Upgrade Preparation Checklist

Before upgrading Oracle Demantra, complete the following additional steps described in the table below.

Item	Details
System path	Remove previous installations from the system PATH variable. (Leaving them does not necessarily cause a problem, but ultimately the variable can become too long and the later additions can't be seen.)
Backup installation folder	Before applying a new patch, backup the Oracle Demantra installation folder on Windows.
Backup WAR file	Before deploying the Demantra web application after applying a patch on the application server, take a backup of the current web deployment war file.
Back up database	Save a dump of the database user that currently stored the Oracle Demantra data.
Windows themes	Change your Windows theme to "Windows Classic" from the available Basic and High Contrast themes. If not selected, your upgrade conversion may hang and not complete. From the Desktop, right-click and choose Properties to personalize your display themes.
Define parameter to grant custom users access to new seeded series (optional)	If you want all users to have access to new seeded series after upgrading, define the SYNCHRONIZE_USER_SERIES parameter in the SYS_PARAMS table before upgrading Demantra. See Automatically Provide Custom Users with Access to New Seeded Series for more information.