In This Section:
Administering Provider Services
Updating References to Rehosted Servers
Setting TCP/IP Socket Communication
To perform administrative functions in Provider Services in Essbase, you must have an administrator role for the designated Essbase Server in Oracle Hyperion Shared Services. If you have an admin role, you are automatically given permission to add or administer Provider Services for that Essbase after logging into Oracle Essbase Administration Services. Provider Services communicates with the designated Essbase server and grants or denies administrator permissions based on the your role in that Essbase instance.
Use Administration Services Console to administer Provider Services:
You can manage Oracle BI EE and Essbase connections through the Smart View Panel in Smart View. For Essbase only, to add Provider Services through Administration Services, use the following procedure.
To add Provider Services:
From Enterprise View or a custom view, select the Hyperion Provider Services node.
In Add Hyperion Provider Services, in Provider Name, enter the Provider Services server name, for example, localhost.
Click the URL text box. This copies the URL of the Provider Services server you entered in the previous step. For example, http://localhost:13080/aps/APS.
In Authenticating Essbase Server, select the name of the Essbase server from the dropdown list. You must have an administrator role in this Essbase server to perform administrative actions.
The provider name is displayed under the Provider Services node.
You can manage Oracle BI EE and Essbase connections through Smart View. For Essbase only, to edit Provider Services through Administration Services, use the following procedure.
You can edit the Authenticating Essbase Server that you specified in Adding Provider Services while adding a Provider Services server in Administration Services.
You can manage Oracle BI EE and Essbase connections through Smart View. For Essbase only, to remove Provider Services through Administration Services, use the following procedure.
You can manage Oracle BI EE and Essbase connections through Smart View. For Essbase only, to connect Provider Services through Administration Services, use the following procedure.
Through Administration Services Console, Provider Services can connect to stand-alone Essbase Servers or Essbase Server clusters. Smart View, Java API, and XMLA users connect to Essbase Servers through Provider Services. To users, the accessed database is transparent. From their perspective, they connect to, and retrieve data from, one data source.
To enable users to select any stand-alone Essbase Server, add the stand-alone server to Provider Services through Administration Services Console. Add Essbase Server to the User Properties window in Administration Services Console before adding the stand-alone server to Provider Services. |
To connect to a stand-alone Essbase Server:
From Enterprise View or a custom view, select the Essbase Servers node to add Essbase Servers to administer.
In Add Analytic Server, enter the Essbase Server name, user name, and password, confirm the password, and click OK.
Repeat step 2 to add additional Essbase Servers.
From Enterprise View or a custom view, under the Hyperion Provider Services node, select a provider.
Right-click and select Create, then Create Stand-alone Server.
In Add Stand-alone Server, from the list of servers added in step 3, select a server.
The name of the stand-alone Essbase Server is displayed under the Stand-alone Server node.
You can manage Oracle BI EE and Essbase connections through Smart View. For Essbase only, to connect Provider Services through Administration Services, use the following procedure.
Start all Essbase Servers associated with Provider Services, as stand-alone servers or in a cluster. Ensure that Provider Services is connected so that clients can connect to it.
Use the sessions window to monitor sessions of users connected to Provider Services. You can view sessions of all users or specific users and which session types are running—Smart View, Java API, or XMLA.
To monitor Provider Services sessions:
From Enterprise View or a custom view, under the Hyperion Provider Services node, select a provider.
Right-click and select Sessions.
The Provider Services Sessions window is displayed:
Session—Active session ID
Session Type—Type of request, from stand-alone server or cluster
Mode—Stand-alone server mode (server) or Analytic Cluster mode (cluster)
User—The use who generated the request
Analytic Server— Essbase Server to which the request was made
Application—Application name
Database—Database name
Request Time—Time of request
Request—Name of current running request, if any
To see one user's sessions, select Show sessions for user and select from user lists.
To see a session, select Show sessions for type and select JAVA, XMLA, or SMARTVIEW
You can specify how many minutes the session can be inactive before timing out.
To specify the session timeout limit:
From Enterprise View or a custom view, under the Hyperion Provider Services node, select the Provider node.
In Idle Session timeout in minutes, specify how long the session can be inactive before timing out (default is 60). If the session times out, Smart View users must reconnect to Provider Services.
Administrators can specify maximum values for rows and columns to be retrieved in a Smart View grid. By default, Provider Services installations set a maximum of 5000 rows and a maximum of 255 columns. If all Smart View users are using Excel 2007 or later, the administrator can increase these maximum values for rows and columns. However, if some or all Smart View users are using Excel 2003, then the default values of 5000 rows and 255 columns (the limits set by Excel 2003) must be used.
Changes to the maximum row and column properties take effect only after the Smart View client connects to a new session of Provider Services.
To specify maximum rows and columns:
You can enable automatic deployment of new Smart View client releases.
To automatically deploy Smart View clients:
From Enterprise View or a custom view, under the Hyperion Provider Services node, select the Provider node.
In Hyperion Provider Services Properties, select Client Deployment.
Force Smart View client to upgrade—Users must upgrade to continue using Smart View.
Warn Smart View client to upgrade—Informs users of available Smart View upgrade. Users can continue using Smart View clients without upgrading.
Apply Smart View client to upgrade—Enables the administrator to apply new versions of Oracle Hyperion Smart View for Office and inform users without requiring Provider Services restart.
In ORACLE_HOME/common/epmstatic/wspace/SmartView, open version.xml.
Add the following Provider Services URL to version.xml:
http://<server name>:13080/aps/APS?downloadClient
This sample version.xml shows where to place the URL:
<?xml version="1.0" encoding="utf-8"?>
<CommonAddinVersion>
<internalVersion>
<major>
4
</major>
<minor>
2.1.0.0
</minor>
</internalVersion>
<externalVersion>
11.1.2.1.00
</externalVersion>
<installFile>
http://<server name>:13080/aps/APS?downloadClient
</installFile>
</CommonAddinVersion>
If you are upgrading to this release by installing EPM System products on a new host machine, you must update Provider Services references to any of the following to reflect the new host name and port number.
Essbase servers
Active-active Essbase clusters configured by Provider Services
Oracle Business Intelligence Enterprise Edition servers
See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide “Updating References to a Rehosted Environment” section for general rehosting information and for information about updating Provider Services references to Essbase servers.
To update Provider Services references to active-active Essbase clusters configured by Provider Services or to Oracle BI EE servers:
Execute this script once for each reference to be updated.
Provider Services uses the Oracle Diagnostic Logging framework (ODL) for logging purposes. See the Oracle Hyperion Enterprise Performance Management System Troubleshooting Guide.
In the TCP/IP socket communication between Provider Services Java API and Essbase, you do not need to configure the socket timeout. By default, control returns to the client when the socket communication completes, when the server resets the socket state or closes, or when the socket times out because TCP/IP timed out. However, you can specify the network operation timeout within which the control returns to the client.
The following Provider Services options are configurable only in essbase.properties:
Table 1. essbase.properties Settings
Setting | Description |
---|---|
The number of attempts a client makes to connect to an Essbase server | |
The time that the thread waits before attempting another connect against Essbase | |
The number of times an API can retry a unsuccessful network operation | |
For connections to hosts with both IPv4 and IPv6 network interfaces, enables performance benefit | |
The time that a network operation can be blocked before it times out | |
Indicates that the client will keep trying infinitely on a network operation |
The number of attempts a client makes to connect to an Essbase Server before failing and reporting an error.
Some causes of connection failures: network congestion, server inaccessibility, and network interruption.
The time in milliseconds that the thread waits before attempting another connect against Essbase.
The number of times an API can retry a unsuccessful network operation before failing and reporting an error. If olap.server.netSocketTryInfinite is true, then olap.server.netRetryCount is ineffective.
If Provider Services is needed to connect to hosts that have both IPv4 and IPv6 network interfaces enabled but only one is being used, this property can be set to false to get a performance benefit. When set to false, Provider Services will not loop through all the interfaces while connecting and instead use only the default one returned by host network environment.
The maximum time in milliseconds that a network operation can be blocked before the operation times out. A timeout of zero is interpreted as an infinite timeout.
Indicates that the client will keep trying infinitely on a network operation. If olap.server.netSocketTryInfinite is true, then olap.server.netRetryCount is ineffective.
For information about using Provider Services to cluster Essbase databases, see Oracle Hyperion Enterprise Performance Management System High Availability and Disaster Recovery Guide.
For information about clustering Provider Services, see “Clustering Web Applications” in Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.