Specify the configuration information for Essbase Server, or click or select Next to accept the default settings. In general, Oracle recommends that you keep the default settings. However, if you are upgrading from an earlier release of Essbase, for Full path to application location (ARBORPATH), specify the existing location or the replicated location of the Essbase application directory. The default location might not be correct.
Note: | Oracle HTTP Server is installed with Foundation Services. It is also installed on the Essbase Server machine. In a distributed environment, configure only one instance of Oracle HTTP Server, the one on the Foundation Services machine. |
Using automatic configuration with EPM System Configurator, you can configure only the 32-bit version of Essbase on 32-bit systems and the 64-bit version of Essbase on 64-bit systems.
If required, you can manually configure 32-bit Essbase client or server on a 64-bit machine. See Additional Essbase Configuration..
For information about configuring an additional instance of Essbase Server, see Configuring and Starting Additional Instances of Essbase Server.
During configuration, if you do not select “Essbase in Standalone mode,” EPM System Configurator automatically registers Essbase with Shared Services and writes the Shared Services connection information to essbase.cfg. In addition, it specifies environment variables in a file used to launch Essbase Server.
The following table describes the configuration options for Essbase Server.
Table 27. Essbase Server Configuration
| EPM System Configurator Fields | Description | Your Information |
|---|---|---|
Essbase Instance Name | Enter a name for this instance of Essbase. | |
Set up Cluster | Click or select Set up Cluster to create a cluster to provide active-passive Essbase failover support with write-back capabilities. You can include only two instances in a cluster. See Setting Up Essbase Clusters. For each instance of Essbase that you configure, select Set up Cluster. When you configure the first instance of Essbase on the first machine, you define the cluster. When you configure the second instance of Essbase on the second machine, you make this Essbase Server join the cluster you created on the first machine. | |
Agent Port Number | Accept the default port number on which the Essbase listens for client requests. If you change the default value, enter a port number that is not used by other programs. | |
SSL Agent Port Number | Specify the SSL port on which Essbase listens for client requests. | |
Start Port | Accept the default number or enter the first port number on which the Essbase Server listens for client requests. | |
End Port | Enter the greatest port number that Essbase Server can use to connect. Essbase uses at least two ports for each application. For a large number of applications, you need a larger port range. | |
The location for applications. Note: Previous versions of Essbase used ARBORPATH to refer to the installation location. If you are setting up an Essbase cluster, the application location must be a shared drive. When you configure the second machine in the cluster, the location must match the location you specified for the first machine in the cluster. Upgrade Note! If you are upgrading from an earlier release of Essbase, specify the existing location or the replicated location of the Essbase application directory. The default location might not be correct. | ||
Set the language to be used by Essbase (ESSLANG) | The ESSLANG variable is a locale definition. For example, to support American English, set ESSLANG to English_UnitedStates.Latin1@Binary. Based on the value you specify, EPM System Configurator updates setEssbaseEnv.bat (in EPM_ORACLE_INSTANCE/EssbaseServer/essbaseserver1/bin) with the ESSLANG value and Essbase uses this value. Verify the operating system locale setting on your computer and select the matching ESSLANG value. The ESSLANG setting for a computer must agree with the locale setting of the computer’s operating system. In addition, on a Windows machine, the ESSLANG value and the system locale must match the language of the Planning application that you plan to take offline. You must choose the correct ESSLANG setting for Essbase products to start successfully. The ESSLANG setting can affect the function of applications and databases. On Windows, if ESSLANG is already set on the computer (for example, if you have already installed Essbase), the current value is selected by default. On UNIX platforms, the ESSLANG setting defaults to English (Latin I) regardless of the setting in the operating system. For more details about ESSLANG, see ESSLANG Variable.For the full list of supported ESSLANG values, see Oracle Essbase Database Administrator's Guide. | |
Select to use legacy security for Essbase Server instead of Shared Services security. This option is not available if you use the -forceRegistry option to start EPM System Configurator. |
Each Essbase Server installation requires that you set an ESSLANG value. See the topic on managing file encoding in the Oracle Essbase Database Administrator's Guide.
The default value for ESSLANG is English (Latin1). For examples of ESSLANG values for non-English languages, see the list of supported locales in the Unicode-mode applications topic in the Oracle Essbase Database Administrator's Guide.
During configuration, EPM System Configurator writes the ESSLANG value that you specify to the Shared Services Registry and to the launch file used to start Essbase.
For Administration Services and Provider Services, there is no prompt to specify the ESSLANG value; it is set to the default value “English_UnitedStates.Latin1@Binary.”
The ESSLANG environment variable on the Essbase Server computer must retain the locale value of an application for as long as that application is in use.
Note: | If the ESSLANG variable is changed after applications are created on an Essbase Server computer, those applications cannot be started. |
Clients also use locales. ESSLANG variables are optional for clients. EPM System Configurator sets the Essbase client ESSLANG environment variable during configuration, and defaults it to “English_UnitedStates.Latin1@Binary.” Client and Essbase locale values must be the same for non-Unicode-mode clients and applications. For Unicode-mode applications, client and Essbase locale values can be different.
To avoid possible database corruption, the ESSLANG locale specification must be the same on client and Essbase Server in the following situations:
The client is not Unicode-enabled.
A Unicode-enabled client saves an outline over an existing outline on a version of the Essbase Server that is not Unicode-enabled.
A Unicode-enabled client saves an outline to a non-Unicode application on a Unicode-enabled Essbase Server.
The ESSLANG locale specifications on clients and Essbase Server computers can be different when a Unicode-enabled client views and updates an outline belonging to a Unicode-mode application.
For products that use Essbase RTC in a non-English environment, you must set ESSLANG manually on the client.