To use bridges, the Analytics Link Server and all other required components must be running. See Startup Order of Oracle Products.
Bridges are managed in the bridge window. See About the Bridge Window.
See:
Analytics Link bridges are located in the Analytics Link Servers node, under the Bridges node.
After a bridge is created, you can change the bridge definition by selecting different Financial Management and Analytics Link components. However, the type of database selected for the bridge target cannot be changed.
See Creating a Bridge.
To edit the bridge definition:
Under the Analytics Link Servers node, expand the Bridges node.
Right-click the bridge that you want to edit, and then select Edit Bridge.
In the Edit Bridge dialog box, modify the bridge definition.
See Creating a Bridge.
Caution! | Some changes to the bridge definition may require that you recreate some of the bridge components, such as the Data Synchronization Server database or the Essbase database. |
Deleting a bridge does not delete any components in the bridge definition from the Analytics Link Server node.
Bridge status determines whether the target database can be modified and queried.
Bridge status types:
Open—The target database can be updated with changes made to the bridge, and queries to the database return results.
Closed—The target database cannot be updated with changes made to the bridge, and queries to the database do not return results.
See:
The Summary tab, as shown in Figure 11, Summary tab: Bridge with an Essbase Target Database, provides information about the status of bridge components; for example, whether all required servers are available, whether databases were created, whether data is available, when the last database update occurred, and so on. The right pane of the Summary tab has the following groups:
HFM Settings
Essbase Settings (this group is displayed only when the bridge target is an Essbase database)
Analytics Link Settings
You can check the status of Data Sync Server on the following bridge window tabs:
Summary tab, under Analytics Link Settings
Data Synch tab, under Data Status
You can check the status of Analytics Link Data (which is the Data Synchronization Server database for the bridge) on the following bridge window tabs:
Summary tab, under Analytics Link Settings
Data Synch tab, under Data Status
Extract tab, under Status
For a bridge whose target is an Essbase database, you can check the status of an Essbase server, application, and database on the following bridge window tabs:
Summary tab, under Essbase Settings
Essbase tab, under Status
Extract tab, under Status
See:
You can export a target grid definition in XML format, which allows you to easily recreate a grid by importing the XML text, instead of going through the process of creating the grid for the first time. You might also want to export the grid definition as part of your Analytics Link configuration documentation, if required by your company for disaster recovery.
Although Oracle recommends importing a previously exported grid definition, you can import any correctly formatted XML text.
To import a target grid definition:
In the Mapping XML dialog box, enter or paste an XML-formatted grid definition.
In the Messages pane below the bridge window, look for messages that indicate that the format of the grid is expressed incorrectly and, if necessary, look in the eal.log file for more information. For example:
[2011-May-16 15:22:02] "memberSelection" attribute must be defined for type="MEASURE" (id=13) for Essbase bridge target
Correct any XML errors and repeat the import process.
In Analytics Link, two types of validation processes exist for the Essbase target grid:
XML format validation—Validate button
When you press Validate, and the Perform Full Mapping Validation option is not selected, Analytics Link verifies that the target grid is expressed correctly in XML format.
In the Validation dialog box, look for messages that indicate that the format of the grid is expressed incorrectly. For example:
ERROR: Matrix dimension mapping should be used for replicated partitions only
If the XML format validation fails, you cannot proceed with creating the Essbase database. Correct any XML errors and repeat the validation process.
Member name validation—Perform Full Mapping Validation check box.
When you select Perform Full Mapping Validation and then press Validate, depending on the transformation type of the dimension, Analytics Link validates the names of Financial Management or Essbase members, as well as validates the XML format of the grid.
ERROR: The mapping definition members selection contains the following invalid member: newmbr, that is not found in Essbase.
If the XML format validation fails, you cannot proceed with creating the Essbase database. Correct any XML errors and repeat the validation process.
See:
You can edit user-defined regions that are not used by a bridge when creating the Data Synchronization Server database. The Default region cannot be edited.
To edit a region:
In the Analytics Link Servers node, navigate to the Financial Management application whose region you want to edit.
In the Region node, right-click a user-defined region and then select Edit Region.
In the Edit HFM Region dialog box, modify the Selection Type and Member Selection columns, as appropriate.
You cannot modify the region name.
Optional: Select Include Dynamic Accounts.
In Financial Management, dynamic accounts are accounts with values that are dynamically calculated when the data is requested. The values for dynamic accounts are not stored. The most common type of dynamic calculation is ratio calculation. Only base accounts can be dynamic.
See Adding a User-Defined Financial Management Application Data Region.
Click Save to save the region definition and to close the dialog box.
You can export a region definition in XML format, which allows you to easily recreate a region by importing the XML text, instead of going through the process of creating the region for the first time. You might also want to export the region definition as part of your Analytics Link configuration documentation, if required by your company for disaster recovery.
Although Oracle recommends importing a previously exported region definition, you can import any correctly formatted XML text.
To import a region definition:
In the Add HFM Region or Edit HFM Region dialog box, click Import XML.
In the Mapping XML dialog box, enter or paste an XML-formatted region definition.
In the Messages pane below the bridge window, look for messages that indicate that the format of the region is expressed incorrectly. For example:
[2011-Mar-22 16:33:19] Filling regions grid failed: The element type "Scenario" must be terminated by the matching end-tag "</Scenario>".
Correct any XML errors and repeat the import process.
In Analytics Link, two types of validation processes exist for data regions:
XML format validation—Validate button
When you press Validate, and the Perform Full Validation of the Region option is not selected, Analytics Link verifies that the region is expressed correctly in XML format.
If the XML format validation fails, you cannot proceed with the process.
Financial Management member name validation—Perform Full Validation of the Region check box.
When you select Perform Full Validation of the Region and then press Validate, Analytics Link validates the names of Financial Management members in the region and the XML format of the region.
If Financial Management member name validation fails, Analytics Link returns a warning, but you can proceed with the process.
For example:
WARNING: The following Financial Management members are invalid in member selection for the region 'myRegion':: xyz,
When you create a user-defined region, Analytics Link automatically validates the XML format of the region.
You can also explicitly validate a data region when you extract data to an RDBMS database target. See Extracting Financial Management Data to an RDBMS Bridge Target.
In the Analytics Link Servers node, you can delete any component that you added if is not used in a bridge definition. See Adding Components to an Analytics Link Server.
If the component is used in a bridge definition, you must first remove the component from the bridge definition before you can delete the component in the Analytics Link Servers node.