2012 PROFITstar Budget Manager

Installation Guide

Last revised: 10/31/2012

Intended audience: IT professionals

This document is available at:

http://profitstarhelp.jackhenry.com/dev/BudgetManager2012Install.pdf

Installation Overview

A server administrator will need to perform the installation of the 2012 edition of

PROFITstar Budget Manager on a server machine. The following list provides a high-level

overview of the initial installation process:

Verify that the server machine meets the system and hardware requirements.

Verify that the Budget Manager installation prerequisites are met.

Decide on a unique name for the Web Application. It is recommended that

"BudgetManager" be used.

Install Budget Manager using the Budget Manager Installer.

Budget Manager needs to have rights to use SQL Server. Budget Manager runs under

the IIS app pool identity credentials. These same credentials need to be added to

SQL Server as a security login.

o If IIS and SQL are on the same server, use SQL Server Management Studio to

add a Login.

o If IIS and SQL are on different servers, the identity/credentials used need to

exist at the domain level. There are various ways to do this—any of which must

be set up to meet the institution's security policies. (Refer to Appendix 1 if SQL

and IIS are on separate servers and the Domain Account is used. Refer to

Appendix 2 if SQL and IIS are on separate servers and the Network Service

Account is used.) For additional information related to configuring IIS and SQL on

different servers, refer to Microsoft‘s product documentation.

Create the first Budget Manager Admin user and test launch Budget Manager.

2

Note: No Budget Manager installation is required on client workstations. The only

software prerequisites for the workstations are a supported browser and the Microsoft®

Silverlight® 4.0 plugin (http://www.silverlight.net/). If Silverlight is not installed on the

client workstation, the user will be prompted through a quick installation on first use.

Budget Manager installation prerequisites:

IIS 7 or greater with ASP.NET v4 or later.

o Installing IIS 7 on Windows Server 2008 or Windows Server 2008 R2

(http://learn.iis.net/page.aspx/29/installing-iis-7-and-above-on-windows-server-

2008-or-windows-server-2008-r2/)

o Microsoft .NET Framework 4 (Standalone Installer)

(http://www.microsoft.com/download/en/details.aspx?id=17718)

Microsoft® SQL Server® 2008 or Microsoft SQL Server 2008 R2. (Any edition can be

used that is appropriate for the number of users that will be using the product.)

Active Budget Manager Product Key.

Other pre-installation resources:

Budget Manager 2012 System Requirements

(http://profitstarhelp.jackhenry.com/dev/BudgetManager2012SysReq.pdf)

Budget Manager Installation Steps:

Download the 2012a.027 BudgetManagerSetup.exe file from the Budget Manager

release/upgrades page of the Client Portal

(https://forclients.jackhenry.com/Release_Upgrades/ProfitStarPROFITabilityCUPRO/Page

s/BudgetManager.aspx). This file will need to be copied to the machine that will host

Budget Manager, if that machine is not connected to the Internet.

If a prior version of Budget Manager has never existed on the targeted server machine,

you will need to have your institution‘s Budget Manager product key available to install

the program. (If applicable, a legacy Budget Manager key will work with this

installation.)

The person installing this software must have access to the institution‘s servers and

have administrator rights to install the software. When the 2012a.027

BudgetManagerSetup.exe is placed on or copied to the server machine, double-click

the file to launch the Budget Manager installer and follow the step-by-step instructions.

3

1. Welcome to the Budget Manager Installation Wizard – Close all Windows programs

before running the Setup program.

Click Next to continue through the Installation Wizard steps.

2. Product Key – This step is hidden if the installer detects that Budget Manager was

previously installed on the current machine.

When this step is displayed, a Budget Manager product key must be entered. If the

Budget Manager program was previously installed on a different machine and you

have that product key, it can be used for this installation. If Budget Manager is being

installed for the first time, you will use the 2012 key that was provided to the

institution.

If you do not have this institution-specific Budget Manager information, please

contact your Client Services Analyst at 800-356-9099.

3. Select Web Site – Select the appropriate Web Site and specify a name for the Web

Application. Valid default settings are displayed.

4

4. Set the SQL Server Connections – Select the SQL Server that will store the Budget

Manager database. When the Server name arrow is clicked, the installer will retrieve a

list of server names that are public in the domain. This list could be incomplete if some

network systems are slow to respond or if certain systems are shielded from view. If you

do not see the correct server name in the provided list, the name can be manually

entered in the box, followed by a backslash.

Note: If IIS and SQL are installed on the same server, you can specify a local

installation by entering ―.\‖ (without the quotes) as the server name.

The Authentication choices are Windows Authentication and SQL Server

Authentication.

The Next button will be enabled when all of the necessary information is provided.

5

5. Outgoing Email Server Configuration – Enabling Budget Manager to be able to send

outgoing email messages via your email server is an optional step in the Budget

Manager installation. In this screen it is only necessary to provide your Email Server

name.

If this is not initially set up, it can be configured later in the IIS Manager.

6

6. Ready to Install – This step provides a recap of the settings selected to this point

in the installation process. Review the information on this screen to ensure that the

configuration settings are correct. If necessary, use the Back button to return to a

previous step.

When Next is clicked, the BudgetManager database is created.

7. Database Installation – When you get to this step in the Budget Manager installation,

it is necessary to complete some setup work in the SQL Server. To accomplish this,

leave the Budget Manager Installer open and switch to the SQL Server Management

Studio program. The following two steps (8 and 9) are performed in the SQL

Server Management Studio.

7

8. Login – New: General page - SQL Server Management Studio

When SQL and IIS are on the Same Server

In this step, authentication between SQL and IIS is set up. Even though, for this

step, it is assumed that these two Microsoft applications are on the same machine,

they still need the ability to communicate with each other.

Note: Refer to Appendix 1 if SQL and IIS are on separate servers and the Domain

Account is used. Refer to Appendix 2 if SQL and IIS are on separate servers and the

Network Service Account is used.

The Budget Manager web application runs under the IIS app pool identity

credentials, so these same credentials need to be added to SQL Server as a security

login. To do this, find Security > Logins, in the left pane of the SQL Management

Studio application. Next, right-click on Logins and select New Login.

8

When the Login - New page opens, enter IIS APPPOOL\BudgetManager in the

Login name field—assuming that ―BudgetManager‖ was used for the Web

Application name in Step 3.

Login - New (SQL 2008 R2)

In addition to the Login name, an authentication method must be specified.

Windows authentication is selected by default. When this setting is used, no

mapping to credentials or passwords is needed.

9

9. Login – Server Roles - SQL Server Management Studio

Next, the appropriate roles must be assigned to this newly created login.

Select Server Roles from the left pane to display the Server roles list. By default

public is selected. Add dbcreator to the list and click OK.

Login Properties - Server Roles (SQL 2008 R2)

When IIS and SQL are on the same server, no additional settings need to be

changed on the other pages associated with this login. The default settings are

adequate.

After saving these settings, you may close the SQL Management Studio.

10

10. Database Installation – Now, return to the Budget Manager Installer and click the

Test Launch Budget Manager button.

11. When the Test Launch Budget Manager button is clicked, the Budget Manager

Administration page should display. Click the Update Database button to proceed.

11

12. After clicking the Update Database button, if the SQL settings are correct and the

database is up to date, then this page is displayed, which is used for assigning a

username and password to the first Budget Manager Admin user. Passwords must be at

least 7 characters long and must contain at least one non-alphanumeric character. In

addition, passwords are case sensitive. Click Create User to complete this action.

Note: Any additional users will be created in the Budget Manager program.

13. The following page confirms that the created user was added as an administrator. Close

the browser and return to the Budget Manager Installer.

12

14. Database Installation – Now that you have connected to the SQL server and created

an Admin user, the database installation is complete. Click Next to continue.

13

15. Click Finish to close the Budget Manager Installer.

14

16. Provide the URL for the Budget Manager database to the user who is designated as the

initial Budget Manager administrator.

Since the Microsoft® Silverlight® 4.0 plugin is required, when the initial Budget

Manager administrator or subsequent users attempt to open Budget Manager for the

first time, they will be prompted to install Microsoft Silverlight if it is not already

installed on the client workstations.

15

Appendix 1

If SQL and IIS are on Separate Servers and the Domain Account is Used

If SQL and IIS are on separate servers, one way to establish authentication between

these two Microsoft applications involves using the domain account.

In brief, this is accomplished by pausing the Budget Manager installation after Step 7;

going into the SQL Management Studio on one server and making a few changes; then

going into the IIS Manager on another server and making changes; and finally returning

to the Budget Manager Installer, at Step 10, to complete the installation process.

In the SQL Management Studio

After Step 7, open the SQL Management Studio, on the appropriate server, so that the

existing or newly created domain account can be added to the ‗Login‘ area.

To begin, find Security > Logins, in the left pane of the SQL Management Studio

application. Next, right-click on Logins and select New Login. When the Login - New

page opens, enter the Login name.

The example below uses FinancialInstDomain\DomainAcct as the Login name.

Login - New (SQL 2008 R2)

16

Next, the appropriate roles must be assigned to this newly created login.

Select Server Roles, in the left pane, to display the Server roles list. By default public

is selected. Add dbcreator to the list and click OK.

Login Properties - Server Roles (SQL 2008 R2)

After saving these settings, you may close the SQL Management Studio.

17

In the Internet Information Services (IIS) Manager

After making the necessary changes in the SQL Management Studio, you will need to

open the IIS Manager, on the other server.

Select the Application Pool you created and go to Advanced Settings.

Application Pools – Advanced Settings (IIS 7.5)

18

In the Advanced Settings panel, change the Identity setting, which initially displays

ApplicationPoolIdentity, by clicking the button.

Advanced Settings - Identity (IIS 7.5)

19

Select the Custom account option and click the Set button.

Application Pool Identity – Custom account (IIS 7.5)

In the User name box, enter the domain account that you used in the Login name, on

the SQL Login – New page, along with its corresponding password.

Custom account – Set Credentials (IIS 7.5)

When this change is made, the application pool is configured to run as the specified user

identity.

Click OK three times to save your changes and return to the Application Pools page. Close the IIS

Manager and return to Step 10 of the Budget Manager Installer to complete the installation process.

20

Appendix 2

If SQL and IIS are on Separate Servers

and the Network Service Account is Used

If SQL and IIS are on separate servers, a way to establish authentication between these

two Microsoft applications is to create a Network Service account.

In brief, this is accomplished by pausing the Budget Manager installation after Step 7;

going into the IIS Manager on one server and making changes; going into the SQL

Management Studio on another server and making changes; and finally returning to the

Budget Manager Installer, at Step 10, to complete the installation process.

In the Internet Information Services (IIS) Manager

After Step 7, open the IIS Manager, on the appropriate server.

In the IIS Manager, select the Application Pool you created and go to Advanced

Settings.

Application Pools – Advanced Settings (IIS 7.5)

21

In the Advanced Settings panel, change the Identity setting, which initially displays

ApplicationPoolIdentity, by clicking the button.

Advanced Settings - Identity (IIS 7.5)

22

When the Application Pool Identity box opens, drop down the Built-in account list and

select NetworkService.

Application Pool Identity – Built-in accounts (IIS 7.5)

When this change is made, the application pool is configured to run as a built-in account,

where the account becomes the name of the computer followed by a $. For example, if

the name of the IIS server is WebServer, the account name is WebServer$.

Click OK twice to save your changes and return to the Application Pools page. Close the

IIS Manager and open the SQL Management Studio, on the other server.

23

In the SQL Management Studio

The following changes are made on the SQL server.

To begin, find Security > Logins, in the left pane of the SQL Management Studio

application. Next, right-click on Logins and select New Login. When the Login - New

page opens, the only thing to do here is to enter the Login name.

In the example below, the IIS server is FinancialInstDomain\WebServer$. Actual

Budget Manager clients will provide their own Login name, formatted like this.

Do not use the Search button as this account will NOT be located in Active Directory.

Login - New (SQL 2008 R2)

24

Next, the appropriate roles must be assigned to this newly created login.

Select Server Roles, the left pane, to display the Server roles list. By default public is

selected. Add dbcreator to the list and click OK.

Login Properties - Server Roles (SQL 2008 R2)

25

The newly created account is now listed as a Login on the SQL server.

New Login Listed (SQL 2008 R2)

At this point, the work on the SQL server is complete and you may return to the Budget

Manager Installer, at Step 10, to complete the installation process.