In This Section:
About the WebLogic Server EPMSystem Domain
Starting Oracle Services and Processes
Configure Analytics Link Server
Configure Analytics Link Repository
Configure Data Synchronization Server
Configure Data Synchronization Server Administrator
Configure Analytics Link Services
Configure Financial Management Connector
If you are using Analytics Link with the 11.1.2.0 or 11.1.2.1 releases of EPM System, WebLogic Server is the supported Web application server.
The Analytics Link Server is deployed to the WebLogic Server EPMSystem domain.
The WebLogic Server EPMSystem domain was created when you installed EPM System products that use a Web application server, such as Shared Services, on WebLogic Server.
Each WebLogic Server domain has its own Admin Server.
Before continuing with configuring Analytics Link Server for deployment to WebLogic Server, start the following EPM System product services and processes:
Shared Services
WebLogic EPMSystem domain Admin Server
Oracle Universal Installer installs all Analytics Link components on a given computer; however, if you are installing Analytics Link on multiple computers, you can configure only those components that you want to run on any given computer.
Select the Analytics Link components that you want to configure on this computer and the components that you want to enable with Secure Sockets Layer (SSL) protocol.
Select the Analytics Link components that you want to configure:
Analytics Link Server
See:
Data Synchronization Server
See:
Financial Management Connector
See:
In the Enable SSL group, select the components for which you want to enable an SSL connection:
Analytics Link Server and Data Synchronization Server—Enables an SSL connection to all Analytics Link components.
RDBMS—Enables an SSL connection to the RDBMS repositories to which Analytics Link connects.
Shared Services—Enables SSL for Shared Services.
To configure and activate SSL, see Configure SSL.
Use the configuration worksheets throughout this chapter to plan your configuration and to document the configuration steps for your company if required for disaster recovery.
Note the following about component selection:
When running Analytics Link Configuration Tool for the first time on a computer, all Analytics Link components are selected by default. When running the configuration tool subsequent times on a computer, components that have been previously configured on the computer are selected.
You can clear components that you either do not want to configure on this computer or that you want to configure later.
You can rerun Analytics Link Configuration Tool to reconfigure previously configured components.
The order of the configuration screens depends on the components that you are configuring at one time.
Before you configure SSL, see Secure Sockets Layer (SSL) for Analytics Link.
For a list of the SSL certificates that you must import, see Configuring SSL When Configuring Analytics Link Server and Configuring SSL When Configuring Data Synchronization Server.
To load certificates into Java Keystore:
To load certificates into Oracle Wallet:
Under Data Synchronization Server, click Import Certificates.
On the Import Certificates dialog box, navigate to the directory where the required certificate is located.
Select the certificate file and then click Import Certificates.
The configuration tool imports the certificate into the correct certificate store.
Before you configure Analytics Link Server, see Analytics Link Server Analytics Link Prerequisites for WebLogic Server.
Table 6 describes the options for Analytics Link Server configuration.
Table 6. Configure Analytics Link Server Page
Field | Description | Your Information |
---|---|---|
Container | Select WebLogic Server. Note: If you are using Analytics Link with 11.1.2.0 or 11.1.2.1 releases of EPM System, you must select this option. | |
Supported Essbase Version | Select 11.1.2 or 11.1.2.1. Note: If you are running Analytics Link on Red Hat Enterprise Linux (64-bit), 11.1.2.1 is the only available option. | |
Analytics Link Server Port | Specify the port number on which Analytics Link Server listens. The default port is 5423. | |
Essbase Max Alias Tables | Specify the maximum number of alias tables for the Essbase database that Analytics Link creates. Maximum number of supported alias tables by Essbase release:
|
Table 7 describes the options for WebLogic Server configuration:
Table 7. Configure WebLogic Server Page
Field | Description | Your Information |
---|---|---|
WebLogic Home | Specify the path to the WebLogic Home location. By default, the WebLogic Home location is: MIDDLEWARE_HOME/wlserver_10.3 | |
WebLogic User | Specify the name of the user for the WebLogic Server EPMSystem domain Admin Server. | |
WebLogic Password | Specify the password of the user. | |
WebLogic Host | This field is read only. localhost is automatically specified as the name of the computer on which WebLogic Server is located. Note: Analytics Link Server and WebLogic Server must be on the same computer. | |
WebLogic Port | Specify the port number on which the WebLogic Server EPMSystem domain Admin Server listens. The default port is 7001. | |
Analytics Link Server Name | Specify the name of the Analytics Link Server as defined in the WebLogic Server EPMSystem domain. For example: EssbaseAnalyticsLink |
Before you configure the database for the Analytics Link repository, see Analytics Link Prerequisites.
Table 8 describes the options for Analytics Link repository configuration.
Table 8. Configure Analytics Link Repository Page
Field | Description | Your Information |
---|---|---|
RDBMS | Select a supported relational database type for the Analytics Link repository:
| |
Database Host | Specify the host name of the database server on which the relational database is located. | |
Database Port | Specify the port number on which the database server listens.
| |
Database Name |
| |
Database User | Specify the name of the Analytics Link repository user. | |
Database Password | Specify the password of the Analytics Link repository user. | |
JDBC Path | Note: This option is enabled only if you selected Microsoft SQL Server as the Analytics Link repository in the RDBMS field. Click Browse or enter the full path to the Microsoft SQL Server JDBC 2.0 driver (Type 4) that is installed on the computer where the Data Synchronization Server is installed. Note: You must obtain the SQL Server JDBC driver from Microsoft. | |
Connection Description | Note: This option is enabled only if you selected Oracle as the Analytics Link repository RDBMS. See RDBMS in this table. When Connection Description is selected:
When Connection Description is not selected, this field is disabled and the Database Host, Database Port, and Database Name fields are enabled. You must enter the appropriate Oracle RDBMS connection information in the Database Host, Database Port, and Database Name fields. | |
Clear DB | Click to clear data from an existing Analytics Link repository. When prompted, click Yes to start the process and then click OK when the process is completed. Caution! If you are upgrading Analytics Link from a previous release, you must select Clear DB to clear the Analytics Link repository that was created in the previous Analytics Link release before you can use the Analytics Link repository in the release that you are currently installing. If you encounter an error message indicating that the database cannot be cleared, see Analytics Link Repository: Cannot Clear Database Error Message. |
Before you configure Foundation Services, see Analytics Link Prerequisites.
Table 9 describes the options for Foundation Services configuration.
Table 9. Configure Foundation Services Page
Field | Description | Your Information |
---|---|---|
Shared Services User | Specify the name of a Shared Services administrator. | |
Shared Services Password | Specify the Shared Services administrator password. | |
EPM Instance Home | Specify the path to EPM Instance Home. By default, the path is: MIDDLEWARE_HOME\user_projects\empsystem1 | |
Unregister Product from Shared Services | Click if you want to unregister this instance of Analytics Link Server from Foundation Services (Shared Services). Caution! If you are upgrading Analytics Link from a previous release, you must select Unregister Product from Shared Services to unregister the Analytics Link Server project from the previous release of Analytics Link before you can use Analytics Link Server in the release that you are currently installing. In Oracle Hyperion Shared Services Console, the Analytics Link Server project is listed as LiveLink@server_name under Application Groups. | |
RDBMS | Select a supported relational database type for the Foundation Services repository:
| |
Database Host | Specify the host name of the database server on which the active Foundation Services repository database is located. Note: Although Foundation Services must be installed on the same computer on which Analytics Link Server runs, if the Foundation Services instance that actively manages security in your environment runs on a different computer, specify the host name of the database server on which the active Foundation Services repository database is located. | |
Database Port | Specify the port number on which the database server listens. The default port:
| |
Database Name |
| |
Database User | Specify the name of the Foundation Services repository database user. | |
Database Password | Specify the password of the Foundation Services repository database user. | |
Connection Description | Note: This option is enabled only if you selected Oracle as the Foundation Services repository RDBMS. See RDBMS in this table. When Connection Description is selected:
When Connection Description is not selected, this field is disabled and the Database Host, Database Port, and Database Name fields are enabled. You must enter the appropriate Oracle RDBMS connection information in the Database Host, Database Port, and Database Name fields. |
Before you configure Data Synchronization Server, see Analytics Link Prerequisites.
Table 10 describes the options for Data Synchronization Server configuration.
Table 10. Configure Data Synchronization Server Page
Field | Description | Your Information |
---|---|---|
Specify the full path where the Data Synchronization Server log file (dss.log) should be written. | ||
Data Store Dir | Specify the path to the directory where Data Synchronization Server stores data related to the Data Synchronization Server database. | |
Data Store Size | Specify the maximum size (in MB) of disk space allocated to the Data Synchronization Server storage directory. Note: The store size must exceed the maximum memory size allocated to the Data Synchronization Server. | |
Job Units | Specify the number of threads that Data Synchronization Server can use to process data. Note: The number of threads cannot exceed the number of CPU cores. | |
Query Units | Specify the number of threads that Data Synchronization Server can use to process queries. Note: The number of threads cannot exceed double the number of CPU cores. | |
Max Memory Size | Specify the maximum amount of memory (in MB) allocated to Data Synchronization Server processes. Note: The maximum memory size must be less than the store size. If the Data Synchronization Server is installed on a 32-bit Windows operating system, the maximum memory limit is 2600 MB. This is a limit of 32-bit Windows operating systems. | |
DSS Port | Specify the port number on which Data Synchronization Server listens. The default port is 5024. | |
Essbase Port | Specify the port number for the Analytics Link port that simulates the Essbase Server port. The default port is 5025. | |
Analytics Link Server Port | Specify the port number on which Analytics Link Server listens. The default port is 5423. | |
Analytics Link Server Host | Specify the name of the server on which Analytics Link Server is located. | |
Reset Data Synchronization Server | Click to clear data from Data Synchronization Server. When prompted, click Yes to start the process and then click OK when the process is completed. Caution! If you are upgrading Analytics Link from a previous release, you must select Reset Data Synchronization Server to delete all Data Synchronization Server databases that were created in the previous release of Analytics Link before you can use Data Synchronization Server in the release that you are currently installing. |
Table 11 describes the options for the Data Synchronization Server Administrator configuration.
The Analytics Link components that are configured as Windows services depends on the components that you selected on the Components to Configure page:
If you selected Analytics Link Server but did not select Data Synchronization Server, only Analytics Link Server is configured as a Windows service.
If you selected Data Synchronization Server but did not select Analytics Link Server, only Data Synchronization Server is configured as a Windows service.
If you selected Analytics Link Server and Data Synchronization Server, both components are configured as Windows services.
Windows service names:
Hyperion Essbase Analytics Link Server - Web Application
Oracle Analytics Link Data Synchronization Server
Table 12 describes the options for Windows services configuration.
Table 12. Configure Analytics Link Services Page
Field | Description | Your Information |
---|---|---|
Run as Service | Select Run as Service to configure the Windows service. | |
Log on As | If you are configuring Analytics Link Server only, or are configuring Analytics Link Server and Data Synchronization Server, select This Account.
If you are configuring Data Synchronization Server only, you can enter the name and password of any user who has permission to run Windows services. Or you can select Local System Account. |
Before you configure Analytics Link Financial Management Connector, see Analytics Link Prerequisites.
The Financial Management Application Server uses Microsoft IIS (Internet Information Services) Web Server.
Note: | IIS6 Metabase Compatibility and IIS6 Scripting Tools roles must be installed as part of the IIS7 installation on Windows Server 2008. Without these roles, the Financial Management Connector component cannot be properly installed and configured. |
Table 13 describes the options for Analytics Link Financial Management Connector configuration.
Table 13. Configure Analytics Link Financial Management Connector Page
Field | Description | Your Information |
---|---|---|
Anonymous Access | Select Anonymous Access, if the user wants to use the anonymous access method for accessing the Microsoft IIS Web site that Analytics Link creates to connect to Financial Management Server. Note: If you select Anonymous Access and you want to use the predefined credentials, do not specify a user and password. | |
User | Define the operation system user that will be used for anonymous access. The user name must be formatted as: domain\user_name Note: If you want to use the default IIS user, leave this field blank. | |
Password | Define the password of the operation system user that will be used for anonymous access. Note: If you want to use the default IIS user, leave this field blank. |
Automatic conversion of Financial Management Dynamic Accounts into Essbase is supported for the following versions of Financial Management:
Financial Management 11.1.2.0 and later—Supported by default. No patch is required.
Financial Management 11.1.1.3—Requires that you install Financial Management Patch 9450270.
Specify the setting for the Financial Management patch.
11.1.1.3-32-bit—Select this option if you are using:
Financial Management 11.1.1.3 and you have installed Financial Management Patch 9450270
Financial Management 11.1.2.0 or later
None—Select this option if you are:
Using a Financial Management pre-11.1.1.3 release
Unsure whether a patch has been installed
Note: | Analytics Link Configuration Tool does not install Financial Management patches for you. You must install Financial Management patches yourself. |
Caution! | During the configuration of Analytics Link Server, Analytics Link Configuration Tool checks for the existence of the ESSBASEPATH system variable. If ESSBASEPATH does not exist, Analytics Link creates the system variable. If ESSBASEPATH already exists, the configuration tool opens a pop-up window with a message indicating that ESSBASEPATH is already set globally and might interfere with creating a partition between the Data Synchronization Server and Essbase databases. If you encounter the pop-up window and a partition is not created during the creation of the Essbase database, contact Oracle Technical Support. |