Adding Components to an Analytics Link Server

In This Section:

Overview of Adding Components to an Analytics Link Server

Startup Order of Oracle Products

Adding an Analytics Link Server

Adding a Financial Management Server

Adding a Financial Management Application

Adding a User-Defined Financial Management Application Data Region

Adding an Essbase Server

Adding an Essbase Application

Adding an Essbase Database

Adding a Data Synchronization Server

Adding a Data Store

Creating a Bridge

About the Bridge Window

Overview of Adding Components to an Analytics Link Server

  Adding bridge components to an Analytics Link Server:

  1. Add the Analytics Link Server to the Analytics Link Servers node.

    See Adding an Analytics Link Server.

  2. Add the Financial Management server and application to the Analytics Link Server.

    See:

  3. Optional: Add a user-defined region.

    See Adding a User-Defined Financial Management Application Data Region.

  4. Add the Essbase Server, application, and database to the Analytics Link Server.

    See:

  5. Add the Data Synchronization Server to the Analytics Link Server.

    Adding a Data Synchronization Server.

  6. Add the Data Store to the Analytics Link Server.

    Adding a Data Store.

  7. Add a bridge.

    See Creating a Bridge and About the Bridge Window.

Startup Order of Oracle Products

Before you can add components to the Analytics Link Server, all required Oracle product components must be running.

The following Oracle Enterprise Performance Management System products and Analytics Link components are listed in their recommended startup order.

  1. Databases used as repositories

  2. Any corporate user directories that you plan to configure for use with Oracle Hyperion Shared Services

  3. Shared Services Oracle Internet Directory, which is used as Shared Services Native Directory

  4. Shared Services Server

  5. Essbase Server

  6. Optional: Oracle Hyperion Provider Services Server

  7. Essbase Administration Server

  8. Data Synchronization Server

  9. Analytics Link Server

  10. Administration Services Console

Adding an Analytics Link Server

See Analytics Link Server.

  To add an Analytics Link Server:

  1. In Administration Services Console, in the Enterprise or custom view, right-click the Analytics Link Servers node and select Add Analytics Link Server.

  2. In the Add Analytics Link Server dialog box, under Analytics Link Server, enter a display Name for Analytics Link Server.

  3. Enter the Analytics Link Server Host name.

  4. Select the URL to Analytics Link Server. The format of the URL depends on which Web Server Analytics Link Server is deployed and whether Analytics Link Server is SSL enabled.

    • Oracle WebLogic Server formats:

      • Analytics Link Server non-SSL enabled:

        http://host:port/hyperroll_livelink/
      • Analytics Link Server SSL enabled:

        https://host:port/hyperroll_livelink/
    • Apache Tomcat formats:

      • Analytics Link Server non-SSL enabled:

        http://host:port/hyperroll_livelink/services/
      • Analytics Link Server SSL enabled:

        https://host:port/hyperroll_livelink/services/

    Note:

    The URL must end with a slash ( / ). The default Analytics Link Server port is 5423.

  5. Under Analytics Link login, enter the Analytics Link Server (Web Service) User name.

    These credentials must be of a Shared Services user with permissions to create projects and provision users.

    To add Analytics Link components, the user must have the following Repository Manager provisions: Provisioning Manager and Administrator.

    See Repository Manager Application Provisions.

  6. Enter the user Password.

  7. Click Test to verify the connection.

  8. Click OK.

Adding a Financial Management Server

  To add a Financial Management server to use with Analytics Link Server:

  1. From the Analytics Link Server, right-click HFM Servers and select Add HFM Server.

  2. In the Add HFM Server dialog box, under HFM Server, enter a display Name for the Financial Management Server.

  3. Enter the HFM Domain, if one exists.

  4. Enter the HFM Host name.

  5. Enter the HFM Cluster name.

    If Financial Management Server is not clustered, enter the Financial Management Server host name.

  6. Under HFM Database, select the RDBMS type for the Financial Management repository:

    • Oracle

      If you select Oracle, there are two methods for entering the Oracle RDBMS connection description to the Financial Management repository (see Connection Description in step 13).

    • SQL Server

  7. Enter the Financial Management database Host name.

    Note:

    If the Financial Management database runs on SQL Server, and there are multiple instances of SQL Server on the same computer, use the following format for the host name: hostName\instanceName.

  8. Enter the Financial Management database Port:

    • Oracle default port—1521

    • SQL Server default port—1433

  9. Enter the Financial Management Database name; for Oracle, enter the SID.

  10. Enter the name of a Financial Management database User with read permission.

  11. Enter the user Password.

  12. Confirm the user password.

  13. Connection Description is enabled only if you selected Oracle as the Financial Management repository RDBMS (see RDBMS in step 6).

    • When Connection Description is selected:

      • The following fields, under HFM Database, are disabled on screen: Host, Port, and Database.

      • In the Connection Description field, you must enter the Oracle RDBMS connection description to the Financial Management repository. For example:

        (DESCRIPTION=
           (ADDRESS_LIST=
              (ADDRESS=(PROTOCOL=TCP)(HOST=oracleserver)(PORT=1521))
           )
           (CONNECT_DATA=
              (SERVICE_NAME=ORCL)
           )
        )
    • When Connection Description is not selected, this field is disabled and the Host, Port, and Database fields are enabled. You must enter the appropriate Oracle RDBMS connection information in the Host, Port, and Database fields.

  14. Click OK.

Adding a Financial Management Application

  To add a Financial Management application:

  1. From the Analytics Link Server, right-click a Financial Management server and select Add HFM Application.

  2. In the Add HFM Application dialog box, enter the Financial Management Application Name.

  3. Enter the Snapshot name.

    See About Financial Management Application Snapshots.

  4. Enter the Financial Management application User name.

  5. Enter the user Password.

  6. Confirm the user password.

  7. Click OK.

When you add a Financial Management application to the HFM Servers node, a Regions subnode and a Default region are automatically added to the tree hierarchy. See Determining the Data Region of the Financial Management Application.

Adding a User-Defined Financial Management Application Data Region

If you plan to only use the Default region, which is created automatically when you add a Financial Management application to the HFM Servers node, you can skip this topic.

  To define a new Financial Management application data region:

  1. From the Analytics Link Server, navigate to the Financial Management application for which you want to define a data region.

  2. Right-click Region and then select Add Region.

  3. In the Add HFM Region dialog box, enter a display Name for the region.

    After you save the region definition, the region name cannot be changed.

  4. For each Financial Management dimension, in the Selection Type column, double-click the field and select a type:

    Dimension selection types for Financial Management dimensions except the Value dimension:

    • ALL—All members in the dimension are included in the data set.

      Member selection is not supported.

    • BASE—Only base-level dimension members are included in the data set.

      Base-level members can be limited to the base members of the members that are specified in the Member Selection column. If the Member Selection column is empty, all base-level members are included.

    • IDESCENDANT—Only dimension members that are specified in the Member Selection column and all of their descendants are included in the data set.

      Member selection is required.

    • MEMBERS—Only the dimension members that are specified in the Member Selection column are included in the data set.

      Member selection is required.

    Dimension selection types for the Value dimension:

    • ALL—All members without alias names are included in the data set.

      Alias member names are enclosed in angle brackets <>; for example, <Parent Curr Total>.

      Member selection is not supported.

    • BASE—All currencies, currency adjustments (for example, USD and USD Adj), and [None] are included in the data set.

      Members can be limited to the members that are specified in the Member Selection column. If the Member Selection column is empty, all currencies, currency adjustments and [None] are included in the data set.

    • BASE_AND_CONSOLIDATED—Only members from the BASE selection type (all currencies, currency adjustments and [None] and consolidation members are included in the data set.

      Consolidation member names are enclosed in brackets []; for example, [Elimination].

      Members can be limited to the members that are specified in the Member Selection column. If the Member Selection column is empty, all currencies, currency adjustments, [None]), and consolidation members are included in the data set.

    • IDESCENDANT—Only dimension members that are specified in the Member Selection column and all of their descendants are included in the data set.

      Member selection is required.

    • MEMBERS—Only the dimension members that are specified in the Member Selection column are included in the data set.

      Member selection is required.

  5. For each Financial Management dimension with a selection type of:

    1. MEMBERS or IDESCENDANT—In the Member Selection column, double-click the field and enter a comma-separated list of dimension member names.

      The Member Selection field must not be empty.

    2. BASE or BASE_AND_CONSOLIDATEDOptional: In the Member Selection column, double-click the field and enter a comma-separated list of dimension member names.

      If the Member Selection column is empty, the data set includes all base-level dimension members (for BASE) and all base-level dimension members and consolidation members (for BASE_AND_CONSOLIDATED).

  6. Optional: For the Accounts dimension, select Include Dynamic Accounts.

    In Financial Management, members in the Account dimension that are tagged with the Dynamic account type are called dynamic accounts. The values of dynamic accounts are dynamically calculated when the data is requested. You can include dynamic accounts members only in user-defined regions.

    The Include Dynamic Accounts checkbox is available when the Account dimension selection type is ALL, BASE, or IDESCENDANT. When the selection type is MEMBERS, you must explicitly specify the dynamic accounts members that you want included in the data set in the Member Selection column.

    Note:

    Including dynamic accounts in a region increases the size of the extracted data. Depending on the expression of the dynamic accounts members, the increase in size could be significant.

  7. Click Save to save the region definition.

  8. Click Close.

You can import the region definition. Exporting and Importing Data Regions in XML Format.

When you add a region, Analytics Link automatically validates the region. See Validating Data Regions.

Adding an Essbase Server

  To add an Essbase Server:

  1. From the Analytics Link Server, right-click Essbase Servers and select Add Essbase Server.

  2. In the Add Essbase Server dialog box, enter the Essbase Server Name.

  3. Enter the Essbase Host name.

  4. In APS URL, select an option to connect Analytics Link Server to Essbase Server:

    • To use Provider Services, select a Provider Services URL.

      • Provider Services non-SSL enabled:

        http://APS_server_host:port/aps/JAPI
      • Oracle Hyperion Provider Services SSL enabled:

        https://APS_server_host:port/aps/JAPI
    • To use Essbase APIs that are embedded in Analytics Link Server, select embedded.

  5. Click OK.

Adding an Essbase Application

Analytics Link supports only Essbase block storage applications. If the Essbase application that you specify does not exist, Analytics Link creates one in block storage mode.

Analytics Link supports non-Unicode mode and Unicode mode Essbase applications. See Unicode Database Property.

  To add an Essbase application:

  1. From the Analytics Link Server, right-click an Essbase Server and select Add Essbase Application.

  2. In the Add Essbase Application dialog box, enter the Essbase Application Name.

    The limit for Essbase application names is 8 characters.

  3. Enter the name of the Essbase application User with Administrator privileges.

  4. Enter the user Password.

  5. Confirm the user password.

  6. Click OK.

Adding an Essbase Database

Analytics Link supports only Essbase block storage databases. If the Essbase database does not exist, Analytics Link creates one in block storage mode.

Analytics Link supports non-Unicode mode and Unicode mode Essbase databases. See Unicode Database Property.

  To add an Essbase database:

  1. From the Analytics Link Server, right-click an Essbase application and select Add Essbase Database.

  2. In the Add Essbase Database dialog box, enter the Essbase Database Name.

    The limit for Essbase database names is 8 characters.

  3. Click OK.

Adding a Data Synchronization Server

See Analytics Link Data Synchronization Server.

  To add a Data Synchronization Server:

  1. From the Analytics Link Server, right-click Data Synchronization Servers and select Add Data Synchronization Server.

  2. In the Add Data Synchronization Server dialog box, enter a display Name for the Data Synchronization Server.

  3. Enter the Data Synchronization Server Host name.

  4. Enter the Data Synchronization Server Port.

    The default port is 5024.

  5. Enter the name of the Data Synchronization Server User.

  6. Enter the user Password.

  7. Confirm the user password.

  8. Click OK.

Adding a Data Store

See Data Store.

  To add a Data Store:

  1. From the Analytics Link Server, right-click Data Stores and select Add Data Store.

  2. In the Add Data Store dialog box, enter a display Name for the Data Store database.

  3. Select the RDBMS type:

    • Oracle

      If you select Oracle, there are two methods for entering the Oracle RDBMS connection description to the Data Store database (see Connection Description in step 10).

    • SQL Server

  4. Enter the Data Store Host name.

    Note:

    If the Data Store runs on SQL Server, and there are multiple instances of SQL Server on the same computer, use the following format for the host name: hostName\instanceName.

  5. Enter the Data Store Port:

    • Oracle default port—1521

    • SQL Server default port—1433

  6. Enter the Database name; for Oracle, enter the SID.

  7. Enter the name of a User with read, write, and create permissions to the Data Store.

  8. Enter the user Password.

  9. Confirm the user password.

  10. Connection Description is enabled only if you selected Oracle as the Data Store RDBMS (see RDBMS in step 3).

    • When Connection Description is selected:

      • The following fields are disabled on screen: Host, Port, and Database.

      • In the Connection Description field, you must enter the Oracle RDBMS connection description to the Data Store database. For example:

        (DESCRIPTION=
           (ADDRESS_LIST=
              (ADDRESS=(PROTOCOL=TCP)(HOST=oracleserver)(PORT=1521))
           )
           (CONNECT_DATA=
              (SERVICE_NAME=ORCL)
           )
        )
    • When Connection Description is not selected, this field is disabled and the Host, Port, and Database fields are enabled. You must enter the appropriate Oracle RDBMS connection information in the Host, Port, and Database fields.

  11. Click OK.

Creating a Bridge

See Analytics Link Bridges.

  To add a bridge:

  1. From the Analytics Link Server, right-click Bridges and select Add Bridge.

  2. In the Add Bridge dialog box, under Bridge, enter a display Name for the bridge.

    The bridge name cannot contain spaces.

  3. Under HFM, select a Financial Management Server and Application.

    See Adding a Financial Management Server and Adding a Financial Management Application.

  4. Under Analytics Link, select a Data Synchronization Server.

    See Adding a Data Synchronization Server.

  5. Select a Data Store.

    See Adding a Data Store.

  6. Under Target, select an option:

  7. Click OK.

Figure 3, Analytics Link Servers Node Showing All Components shows the tree hierarchy of the Analytics Link Servers node after components have been added.

Figure 3. Analytics Link Servers Node Showing All Components

This image of the Enterprise View shows the tree hierarchy of the Analytics Link Servers node after all components have been added.

About the Bridge Window

You manage a bridge in the bridge window, which has multiple tabs.

Bridge window tabs:

If multiple bridges are open, each is displayed in a separate bridge window.