Initialize an application
Updated: 2008-11-14
After an application has been created by manually running the application creation scripts, you must initialize the application to make it available to users. This procedure is necessary when you select Generate application creation scripts for manual execution in the Create an Application dialog box.
After the SQL Server Data Definition Language (DDL) scripts have been generated for the new application, the application state appears as DDL Scripts Prepared on the Application page. This means that the scripts can be modified for your IT or data center environment and then run by a database administrator. After the scripts are run, the application state changes to DDL Scripts Executed and the Initialize button becomes enabled. Then, you can open the Initialize an Application dialog box and enter the data that Planning Server requires to finish creating the application, as described in the following procedure.
To initialize an application
On the Applications page, select the application that you want to initialize. You may have to refresh the page to see recent changes to the list of applications.
Click Initialize. The Initialize an Application dialog box opens.
In the Model site name box, type the name for the default model site for the application. Names are meant to be user-friendly descriptors for objects. The name must be from one to 256 alphanumeric characters long. It is not case sensitive.
In the Model site label box, type a unique label for the default model site for the application. The label must begin with an alphabetical character, must be from one to 40 alphanumeric characters long. It is not case sensitive. The following characters are not permitted: . , ; ' ` : / \ * | ? " & % $ ! - + = ( ) [ ] { } < > ^ ~
Using an underscore character (_) in labels may cause naming conflicts when you use it in labels for applications and model sites. Because Planning Server uses an underscore to link these objects for internal representation, you may unintentionally create a duplicate internal name by using an underscore. Planning Server will not create an object if it has a duplicate internal name. For example, the following two application and root model site combinations produce the same internal name (Company_Sales_Category).
A dimension labeled "Company" with a hierarchy labeled "Sales_Category"
A dimension labeled "Company_Sales" with a hierarchy labeled "Category"
(Optional) In the SQL FileGroup box, type the name of the SQL FileGroup that is associated with the data in the model site. For example, the data could be private dimension data or measure group data for the model site. The SQL FileGroup must be created before you associate it with a model site. Otherwise, Planning Server will use the default SQL FileGroup. For more information about how to use SQL FileGroups with Planning Server applications, see the PerformancePoint Server 2007 Deployment Guide.
(Optional) In the Analysis Services computer name box, type the name of the server that will contain the data for the model site. This computer must be running Microsoft SQL Server 2005 Analysis Services. If you do not type a computer name, the omputer that is running SQL Server and that contains the application database will be used.
Click OK.