Hyperion Application Builder for.net. Readme. Release

Transcription

1 Hyperion Application Builder for.net Release Readme Hyperion Application Builder for.net... 1 Readme... 1 Purpose... 2 New Features... 2 Embedded JAPI Mode... 2 Non Unique Member Names... 2 Support for HTTPS DataServer... 2 GridAdapterOWC ComboBoxAdapter... 2 ListBoxAdapter... 2 TreeviewAdapter...2 Installation Updates... 3 Installation workflow... 3 Using Application Builder for.net with Essbase Deployment Services Releases 9.2 or Replacing ESS_JAPI.JAR... 4 Configuring the Essbase Server with Oracle Hyperion Provider Services... 5 Configuring the Analytic Server with Hyperion System 9 BI+ Analytic High Availability Services... 7 Deploying EssbaseObjects.war file Known Issues Embedded JAPI Utility Configuration Utility Defects Fixed in this Release Managing Sample Applications Windows Samples ASP.NET Samples Note: Any references in the documentation to the Oracle E-Delivery site pertain if your site has access.

2 Purpose This document includes important, late-breaking information about this release of Oracle s Hyperion Application Builder for.net. Review this information thoroughly before installing Application Builder for.net. Top of Document New Features Embedded JAPI Mode Embedded JAPI is a simple deployment of Java APIs using jar files and property files. These jar files and property files are bundled into the Application Builder for.net Server application. After deployment of the Embedded JAPI feature, the Application Builder for.net Server establishes direct connection to Oracle Essbase through these Java APIs. With the Embedded JAPI option enabled, the middle tier (APS/EDS application) configuration is not required. Non Unique Member Names The Allow Duplicate Members option in Essbase, allows Application Builder for.net to query and display data that have same member names within multiple dimensions. For example, New York State and New York City can be named "New York" within State and City dimensions: Support for HTTPS 2.0 Application Builder for.net utilizes Secured Socket Layer (SSL) over the HTTP transport mechanism to accomplish a secure request or response pattern between Application Builder for.net components and Application Builder for.net Server. DataServer The DataServer component provides a middle-tier layer between application objects (buttons, listboxes, and so on) and Essbase. This component maintains an internal data instance grid that is accessed by the application controls. GridAdapterOWC11 The GridAdpaterOWC11 provides an easy to use spreadsheet environment for OLAP analysis with Essbase. An Essbase applications utilize this adapter to enable ad hoc OLAP data analysis operations such as Retrieve data, Zoom In, Zoom Out, Pivot, and so on using OWC11 spreadsheet. ComboBoxAdapter The ComboBoxAdapter manages transfer of OLAP data between the data server component and a standard Microsoft.NET ComboBox control. ListBoxAdapter The ListBoxAdapter manages transfer of OLAP data between the data server component and a standard Microsoft.NET ListBox control. TreeviewAdapter The TreeviewAdapter manages transfer of OLAP data between the data server component and a standard Microsoft.NET Treeview control.

3 Note: All the new components (Data Server through TreeViewAdapter) are Windows-based components (as opposed to the Web-based components from the prior release). Installation Updates Top of Document The section includes important information about installing the release of Application Builder for.net. Designing Reports in Application Builder for.net Applications If you are designing reports with Application Builder for.net application using query adapters like ListboxAdapter, DropdownlistAdapter, and TreeviewAdapter, include the query adapter connected to an Essbase dimension in either the row or the column. Installation workflow The following table lists the high-level steps required to install and configure the Application Builder for.net Product. Review these steps first, before you begin the installation process. For detailed information, refer to the product component and related documentation listed at each step. Step Instruction Product Component Documentation 1 Complete prerequisites for Application Builder for.net (System requirements, and so on) 2 Installing the Application Builder for.net 3 Configuring Application Builder for.net 4 (Optional) Configuring the Application servers BEA WebLogic IBM WebSphere Oracle Application Server 5 Creating a basic application within the.net environment, enabled to access Oracle Essbase data Enterprise Performance Management Installer EPM System Configurator Application Server Installers Microsoft Visual Studio for.net Development Environment Oracle Hyperion Enterprise Performance Management System Installation Start Here Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide Hyperion Application Builder for.net Developer's Guide

4 6 Configuring the Essbase Server with Provider Services Oracle Essbase Administration Services- Administration console Essbase Server Provider Services This document, Oracle Hyperion Application builder for.net Readme 7 Configuring the Analytic Server with Analytic High Availability Services 8 Using Hyperion Application Builder.NET with EDS 9.x and Replacing ESS_JAPI.JAR Oracle Essbase Administration Services, Administration console Essbase Server High Availability Server Application Builder for.net Server This document, Oracle Hyperion Application builder for.net Readme This document, Oracle Hyperion Application builder for.net Readme Using Application Builder for.net with Essbase Deployment Services Releases 9.2 or 9.3 This release of Application Builder for.net supports backward compatibility to Essbase Deployment Services (EDS) Releases 9.2 and 9.3. The Application Builder for.net server installation contains separate folders for 9.2 and 9.3 releases of EDS. These folders contain the ess_japi.jar file. To work with 9.2 or 9.3 releases of EDS: From the location <HYPERION_HOME>\products\Essbase\habnet\Server\essjapi\9.x (where x pertains to the release of EDS that you want to use), copy the relevant ess_japi.jar file to the location <HYPERION_HOME>\products\Essbase\habnet\Server\lib, thereby replacing the ess_japi.jar file. Replacing ESS_JAPI.JAR To replace the existing JAPI with 9.x ESS JAPI in EssbaseObjects.war: Copy the EssbaseObjects.war file from HABNET_HOME\products\Essbase\habnet\Server\servlet to a temporary folder, for example, C:\warUpdate. Unzip and extract the.war file to the temporary folder. The temporary folder should now contain two subfolders META-INF and WEB-INF. The WEB-INF folder contains a lib folder and the web.xml file. Browse to the respective <HYPERION_HOME>\products\Essbase\habnet\Server\essjapi\9.x\ folder and copy the corresponding ess_japi.jar file to the WEB-INF\Lib folder in the temporary directory you previously created, overwriting the previous ess_japi.jar file. For example: To replace ess_japi.jar ( ) with ess_japi.jar (9.2), browse to <HYPERION_HOME>\products\Essbase\habnet\Server\essjapi\9.2\ and copy the ess_japi.jar (9.2) to the WEB-INF\Lib folder in the temporary directory you previously created, overwriting ess_japi.jar ( ). Open the command prompt, navigate to the temporary folder you created (C:\warUpdate), and enter the following command: jar -cvf EssbaseObjects.war *.*

5 The temporary folder (C:/warUpdate) now contains the updated EssbaseObjects.war file which can be redeployed on the application server to communicate to earlier release of EDS (i.e. APS in this release). Configuring the Essbase Server with Oracle Hyperion Provider Services This section details how to configure Provider Services (APS) with Essbase Server; specifically the registration process for Provider Server and Essbase Server in the Essbase Administration Services (EAS) Console. Note that the following procedures refer to Essbase Administration Services (EAS) Release 9 Note: This section is only applicable for backward compatibility from 9.3 Releases. To configure the Essbase Server with Provider Services: Select Start > Programs > Oracle EPM System > Essbase > Essbase Server > Essbase to start the Essbase Server. Select Start > Programs > Oracle EPM System > Essbase > Provider Services > Start Provider services to start the Provider Server. Select Start > Programs > Oracle EPM System > Essbase > Administration Services > Start Administration Service to start the EAS server. Select Start > Programs > Oracle EPM System > Essbase > Administration Services > Start Administration Services Console to launch the EAS Administration Console. Administration Services Login dialog box Select an Administration Server, enter the user credentials, and click OK to log on to EAS Admin console. EAS Admin Console Screen

6 To add an Essbase Server user to Admin console, expand Administration Servers, <server name>, right click Users and select Create User. To add an Essbase server, right click Essbase Servers and select Add Essbase Server. The Add Essbase Server (formerly Analytic Server) dialog box opens. Add Essbase Server dialog box Enter Essbase Server name, Username, Password, and click OK. To add Provider Services, right click Provider Services and select Add Hyperion Provider Services. The Add Hyperion Provider Services dialog box opens. Add Hyperion Provider Services dialog box

7 If all the servers are running on the same machine, enter the server name as localhost. If Provider Services is running on another machine, enter the IP address of that machine. Click OK. Configuring the Analytic Server with Hyperion System 9 BI+ Analytic High Availability Services This section details how to configure Analytic High Availability Service with Analytic Server; specifically the registration process for High Availability Server and Analytic Server in the Analytic Administration Services (EAS) Console. Note that the following procedures refer to Analytic Administration Services (EAS) Release 9. To configure the Analytic Server with Analytic High Availability Server: Select Start > Programs > Hyperion System 9 BI+ > Analytic Services > Analytic Server to start Analytic Server. Select Start > Programs > Hyperion System 9 BI+ > Analytic High Availability Services > Start High Availability Services Server - HTTP to start the High Availability Server. Select Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Start Administration Service Server to start the EAS server. Select Start > Programs > Hyperion System 9 BI+ > Analytic Administration Services > Start Administration Services Console to launch the EAS Administration Console. Analytic Administration Services Login dialog box Select an Administration Server, enter the user credentials, and click OK to log on to EAS Admin console.

8 To add an Analytic Server user to Admin console, expand Administration Servers, <server name>, right click Users and select Create User. Create User on Administration Server dialog box Enter Essbase user credentials, select Administrator Privileges, and click OK.

9 To add Analytic Server, right click Analytic Servers, and select Add Analytic Server. Add Analytic Server dialog box Enter the Analytic Server name, user credentials, and click OK. To add High Availability Servers, right click High Availability Servers, and select Add High Availability Servers. Analytic High Availability Services-Add High Availability Servers dialog box

10 Enter the Server Name, user credentials, and IP address of the machine where the server is running, and click OK. If all the servers are running on the same machine and default port, leave the default URL as it is and click OK. If EDS is running on another machine or port, enter the IP Address of that machine in the URL area. To add Analytic Server, expand High Availability Servers, <server name>, right click Essbase and select Create Analytic Server. Analytic High Availability Services dialog box If all the servers are running on the same machine, enter the server name as localhost. If Analytic Server is running on another machine, enter the IP address of that machine. Click OK. Deploying EssbaseObjects.war file To deploy the EssbaseObjects.war file: Copy the updated EssbaseObjects.war file to the following folders: HABNET_HOME\products\Essbase\habnet\Server\servlet HABNET_HOME\deployments\Tomcat\5.0.28\webapps Navigate to HABNET_HOME\bin and start any of the Hyperion Application Builder for.net Servers (Tomcat, WebLogic, or WebSphere). Top of Document Known Issues The following are some known issues in Oracle s Hyperion Application Builder for.net Release :

11 Embedded JAPI Utility The Embedded JAPI Utility for UNIX contains a corrupted script in the ESSJapiUtil.sh file. Errors are displayed when you run this file. Following are the errors found while running the ESSJapiUtil.sh file:./essjapiutil.sh: line 1: cls: command not found./essjapiutil.sh: line 3:../lib/ESSJAPIUtility.jar: Permission denied./essjapiutil.sh: line 3:../lib/ess_es_server.jar: Permission denied./essjapiutil.sh: line 3:../lib/ess_japi.jar: Permission denied./essjapiutil.sh: line 3:../lib/soap.jar: Permission denied./essjapiutil.sh: line 3:../lib/log4j jar: No such file or directory./essjapiutil.sh: line 3:../lib/cpld14.jar: Permission denied./essjapiutil.sh: line 4: cls: command not found./essjapiutil.sh: line command not found./essjapiutil.sh: line 7: /common/config/ /setjavaruntime.sh: No such file or directory./essjapiutil.sh: line 9: REM: command not found Executing EssJapi Utility to update the domain.db./essjapiutil.sh: line 13: \bin\java: command not found To prevent errors when running the ESSJapiUtil.sh file, you must do these tasks: 1. Navigate to the directory <HABNET_HOME>/Server/bin. 2. Open the ESSJapiUtil.sh file, using an editor such as the VI editor. 3. In the ESSJapiUtil.sh file, replace the existing code with the following code and save the file. #!/bin/bash clear export localcp=.:../lib/essjapiutility.jar:../lib/ess_es_server.jar:../lib/ess_japi.jar:../lib/soap.jar:../lib/log4j jar:../lib/cpld14.jar: source $HOME/set_hyphome_*_1.sh clear set +v if [ "x${hyperion_home}" = "x" ]; then printf "ERROR: Environment variable HYPERION_HOME is not set.\n" exit 1 fi source $HYPERION_HOME/common/config/ /setJavaRuntime.sh if [ "x${java_home}" = "x" ]; then printf "ERROR: Environment variable JAVA_HOME is not set.\n" exit 1 fi # Get JRE or JDK

12 echo Executing EssJapi Utility to update the domain.db "${JAVA_HOME}/bin/java" -cp $localcp -DAPS_HOME=$APS_HOME com.habnet.essjapi.essjapiutility $1 4. Before running the ESSJapiUtil.sh file, confirm that the prerequisites are set, for more information, see the Hyperion Application Builder for.net Developer's Guide. 5. Run the ESSJapiUtil.sh file. Configuration Utility When running the Hyperion Configuration Utility after upgrading products from release to release 9.2.0, the product selection page may display multiple listings for a product or may not list the product you are trying to configure. If this problem occurs, perform these steps: Navigate to the following directory: (Windows): <HYPERION_HOME>\common\config\product\<product>\<release number> (UNIX): <HYPERION_HOME>/common/config/product/<product>/<release number> Where <HYPERION_HOME> is the Hyperion Home location on the machine and <product> is the product name or abbreviation, for example: c:\hyperion\common\config\product\planning\9.3.0 Delete the oldest *.xml file from this directory. For example, if the directory contains two files named planning_1.xml and planning_2.xml, delete the older file. Re-run the Configuration Utility. Top of Document Defects Fixed in this Release Grid Adapter for Web-OWC11 Spread Sheet Adapter ( ) One of the requirements for the Grid Adapter for Web-OWC11 Spread Sheet Adapter is that the object link supports 127 properties in the OWC11 adapter. The current version of this adapter in.net supports only 27 properties. Top of Document Managing Sample Applications These sample applications are developed using Application Builder for.net Components present in this release. Windows Samples Two Windows samples are located in the Windows Samples directory. WinApp1: This application demonstrates the usage of ComboBoxAdapter and gridadapterowc11 for Windows. WinApp2: This application demonstrates the usage of TreeViewAdapter for Windows.

13 To run the Windows sample applications, open the project files in Visual Studio.NET and confirm that the references to the Application Builder for.net assemblies point to the correct locations. ASP.NET Samples Two ASP.NET samples are located in the Web Samples directory. WebApp1: This application demonstrates the usage of listboxadapter for Web. WebApp2: This application demonstrates the usage of treeviewadapter and gridadapterowc11 for Web. To setup the ASP.NET sample applications, perform these steps: 1. Right click the <Sample Web application> directory name in the Windows Explorer and select Sharing. 2. In Web Sharing, select Share this folder. 3. In Alias, provide name HABNETSamples. 4. Run the Microsoft Management Console. This is most commonly found at: Control Panel > Administrative Tools > Information Services Manager. 5. In the left hand tree view, expand: <name of computer> > Default Web Site. 6. Expand the HABNETSamples virtual directory you have just created. 7. Right click and select Properties. 8. Under Application Settings, click Create and OK to close the dialog box. You can now open the sample ASP.NET project files in Visual Studio.NET. However, to work with the sample application, you must build and run the project. Note 1: The <Sample Web application> means either WebApp1 or WebApp2 directory as the preceding steps can be generally used to configure these sample applications. Note 2: To work with the sample applications that use OWC11, you must install Internet Explorer Web Controls, You can install Internet Explorer Web Controls from the following location: Note 3: Both the Windows and Web samples application uses the following the configurations details. HABNET server APS Essbase : running on local machine : running on local machine : running on local machine Essbase Application : Demo Essbase Database : Basic User Name :< User Name > Password :< Password > User has to change these configurations using sign-on dialog of dataserver component on each sample page as per their environment.

14 Copyright 2008, Oracle and / or its affiliates. All rights reserved.