Udostępnij za pośrednictwem

  • Artykuł

Creating an application

Updated: 2009-04-09

You can create an application by using the Planning Administration Console.

Note

The terms Windows SharePoint Services and SharePoint Services are used collectively in PerformancePoint Server documentation to refer to Office SharePoint Server 2007 and Windows SharePoint Services 3.0.

Create an application using the Planning Administration Console

  1. Open the Planning Administration Console, and connect to a computer that is running Microsoft Office PerformancePoint Server 2007.

  2. When the connection is established, click Applications in the navigation pane of the window, and then click Create.

  3. In the Application name text box, type a name for the new application.

  4. In the Label text box, type a unique label for the new application. Avoid use of the underscore character (_) in labels.

  5. In the Description box, type a description of the application.

  6. In the SQL Server name box, type the name of the computer that is running Microsoft SQL Server 2005 and that will contain the application database.

    Note

    If you are using a named instance of Microsoft SQL Server 2005, enter the server name in the following form: MyServerName\ThisInstanceName.

  7. In the Application Database Name box, type the name of the SQL Server database that you want to use as the application database.

  8. [Optional] In the Staging Database Name box, type the name of the SQL Server database that you want to use as the staging database for the new application. The staging database and the application database must be on the computer that is running SQL Server.

    • If you do not enter the name of the staging database at this point, you can create the database later by using the Edit an Application dialog box.

    • If you do enter the name of the staging database in the Staging Database Name box, Planning Server generates the CreateStagingDB.sql script. By default, Planning Server creates a staging database that uses the specified name. Alternatively, you can select Generate application creation scripts for manual execution in step 16 to create the staging database manually and Planning Server generates the CreateStagingDB.sql script at the specified location.

      If the database you name in this box already exists, an error message reports to you that the database cannot be created.

  9. In the Form Template Location box, type the URL for the network share or Microsoft SharePoint® Products and Technologies Web site that stores the form templates for the application. Microsoft Office PerformancePoint Server 2007 distributes form templates to users through an assignment. Users access the form template for an assignment at the specified URL.

    For a secure deployment, make sure access permissions are enforced on all directories that store the form templates.

    Warning

    If you do not specify a storage location for the application form templates, users of PerformancePoint Add-in for Excel may receive errors. In addition, the users will be able to save to a non-standard location. If PerformancePoint Add-in for Excel users save the form templates in a non-standard location, Planning Business Modeler cannot display a list of form templates.

  10. In the Report Storage Location text box, type the URL for the network share or SharePoint Products and Technologies Web site that stores the supporting reports for the application. PerformancePoint Server distributes reports to users through an assignment. Users access a report for an application at the specified URL.

    Warning

    If you do not specify a storage location for the application reports, users of PerformancePoint Add-in for Excel may receive errors. In addition, the users will be able to save to a non-standard location. If PerformancePoint Add-in for Excel users save reports in a non-standard location, Planning Business Modeler cannot display a list of reports.

  11. In the Assignment Forms Location box, type the URL for the network share or SharePoint Products and Technologies Web site that stores the assignment.

  12. In the Assignment Master Forms Location box, type the URL for the network share or SharePoint Products and Technologies Web site that stores the master forms for the application.

  13. Click to select the Enable native SQL/MDX rules check box. When enabled, this feature makes it possible for business analysts to write rules in SQL, MDX Query language, or MDX Script.

    Important

    Enabling native SQL Server rules and native MDX rules could pose a security risk, as they have processing capabilities that could affect many objects.

  14. Click to select the Excel macro support check box to enable users of PerformancePoint Add-in for Excel to use macros they create for PerformancePoint Server.

    Note

    If you disable Excel macro support, users will not be able to use Microsoft Office PerformancePoint Server 2007-related macros. However, users will be able to run other Excel macros, depending on the user security setting in Excel.

  15. [Optional] Click to select Automatically execute application creation scripts if you want Planning Server to execute the SQL Server Data Definition Language (DDL) application creation scripts that Planning Server generates automatically.

    The Automatically execute application creation scripts option is best used for non-production deployments, such as test deployments.

    If you selected Automatically execute application creation scripts, you must provide the following information for the default model site:

    • In the Model site name box, type the name for the new application's default model site.

    • In the Model site label box, type a unique label for the application's default model site.

    • [Optional] In the SQL FileGroup box, type the name of the SQL FileGroup that will be associated with the default model site.

      Note

      Planning Server does not create a SQL Server FileGroup for you. A SQL Server database administrator must create SQL Server FileGroups in the application database in advance, or you can specify an existing SQL Server FileGroup.

    • In the Analysis Services server name box, type the name of the computer that contains the instance of SQL Server Analysis Services that stores the model site data.

      To create an application for use in a production environment, use the manual execution option described in step 9.

      Note

      In a distributed deployment, a database administrator must grant dbcreator permissions to the PerformancePoint Server service identity account before creation scripts can be automatically executed or if using the Planning Outbound Database feature is required. For more information, see Prepare SQL Server to host an application database. In a single-server installation, this step is not required.

  16. [Optional] Click to select Generate application creation scripts for manual execution if you want to customize the DDL scripts that PerformancePoint Planning Server generates, and then execute the scripts manually.

    If you decide to run the DDL scripts manually, you must initialize the application after the scripts are executed. To do this, click Initialize on the Applications page to open the Initialize an Application dialog box.

    If you select this option, in the Output Folder Location text box, type the location for the DDL where the generated scripts will be stored.

    To customize the scripts, move to the location specified, change the scripts as appropriate, and then manually execute the scripts.

    The following list shows the order in which the generated scripts must be executed.

    1. CreateAppDB.sql

      CreateAppDB.sql contains the CREATE DATABASE statement. A database administrator can customize CreateAppDB.sql to set configuration elements such as the size of the log file or the size of the application database.

    2. TypeLibMasterSchema.sql

      TypeLibMasterSchema.sql contains the CREATE TABLE statement. A database administrator can also add SQL FileGroup data with this script.

    3. UpdateApplicationsStatusScript.sql

      Note

      When you manually execute TypeLibMasterSchema.sql on the application database, You will see a list of the following message:

      "Warning! The maximum key length is 900 bytes. The index 'Sec_ConsolidationMethod_PK' has maximum length of 1040 bytes. For some combination of large values, the insert/update operation will fail."

      "Warning! The maximum key length is 900 bytes. The index 'Sec_ExchangeRate_PK' has maximum length of 1040 bytes. For some combination of large values, the insert/update operation will fail."

      Please ignore these messages. We have verified that these messages are harmless in this case. We will remove them in later release of the product.

    4. CreateStagingDB.sql.

  17. Click OK to close the Create an Application dialog box.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable content for PerformancePoint Monitoring Server.

See Also