This step of the process assumes that you have already copied the files to c:\inetpub\wwwroot per the instructions in Deployment and installed SQL Server and the Databases onto the server, and have verified that the databases are installed and working.

Some of these steps may be slightly different depending upon the operating system that you are using, and it is strongly recommended that this installation be done by someone familiar with configuring Dot Net applications in an IIS environment..

Make sure the ASP Dot Net State Service is Running!

Go into the "Services" tool in the administration set-up area, and make sure that the "ASP Dot Net State Service" is running. If it is not, please start it, and change it's properties so that it starts automatically.

Here are the instructions on how to Deploy the Application Layers to LocalHost

1) Make Sure IIS is running!

2) Open Windows Explorer and navigate to c:\inetpub\wwwroot

3) Open the "Enterprise" directory. You will see many sub-directories there including "EnterpriseASP" and "EnterpriseWS"

4) Right-Click on the "EnterpriseWS" Directory

4) Select "Properties"

5) Select "Web Sharing"

6) On the Web Services Tab, the "Share On" drop-down should say "Default Web Site", if not, click on the drop down and select it.

7) Click on the "Share This Folder" radio button, and then the "EnterpriseWS" entry should come up under the "Aliases" list.

8) Now press the "Add" button, and an "Add Alias" or "Edit Alias" box should pop-up on the screen, Accept the defaults for the "Access Permissions" part of the screen ((Read Should be checked) and under the "Application Permissions" section "Execute Including Scripts" should be selected. Accept the other defaults given and select "OK"

9) Select "Apply" and close this window

Repeat all of the same above steps for "EnterpriseASP", and any of the other Enterprise applications that you will be using, like EnterpriseHelp, EnterpriseHelpDesk, EnterpriseCRM, EnterprisePOS, EnterpriseCart, EnterpriseBudget.
 

Configure IIS To Run The Application Layers

Configure the properties of the applications by following these steps:

1) Open IIS Manager

2) Navigate down through "Web Sites" to Default Web Site and then to EnterpriseWS,  select "EnterpriseWS", open the properties form.

3) On the "Virtual Directory" Tab, make sure that under the "Application Settings" area that Execute Permissions are set to "Scripts and Executables" and that there is an application created for this directory. If not, then press the create button to create the application for this directory and continue.

4) Select "Directory Security" then press the "edit" button next to the "Anonymous access and authentication control" icon

5) Make sure that "Anonymous access" checkbox is selected, and "allow IIS to control Password" is selected (if you have this option) and that "Integrated Windows Authentication" is selected at the bottom"

6) The ASP Dot Net Tab should show the ASP Dot Net version as 2.0 or greater. This should be the case since you should not have installed any other framework on this server other than the Dot Net 2.0 Framework.

7) Click on the documents tab and make sure that Default.aspx and index.html appear as default documents.

8) Still within IIS Manager, Navigate down through "Web Sites" to Default Web Site and then to /Enterprise, and then to /EnterpriseWS,  select "EnterpriseWS", open the properties form.

Please note that /EnterpriseWS  and /Enterprise/EnterpriseWS are two different directories and they both need to be properly configured.

9) On the "Directory" Tab, make sure that under the "Application Settings" area that Execute Permissions are set to "Scripts and Executables" and that there is an application created for this directory. If not, then press the create button to create the application for this directory and continue.

10) Select "Directory Security" then press the "edit" button next to the "Anonymous access and authentication control" icon

11) Make sure that "Anonymous access" checkbox is selected, and "allow IIS to control Password" is selected (if you have this option) and that "Integrated Windows Authentication" is selected at the bottom"

12) The ASP Dot Net Tab should show the ASP Dot Net version as 2.0 or greater. This should be the case since you should not have installed any other framework on this server other than the Dot Net 2.0 Framework.

13) Click on the documents tab and make sure that Default.aspx and index.html appear as default documents.

Repeat all of the same above steps  1 - 13 for "EnterpriseASP".

For the applications that are not a Child of the /Enterprise directory, like EnterpriseCRM, EnterprisePOS, EnterpriseCart, EnterpriseHelpDesk, EnterpriseHelp, EnterpriseBudget, you would only need to do steps 1 - 7.

Setting the Main Configuration Files:

You will need to properly set-up the main configuration files for the application. The Main configuration files for the application are the Web.config files in both the /EnterpriseASP and the /EnterpriseWS sub-directories. If you set everything up properly and to their default locations, there are no changes that need to be made to the config files for the application to run. However, they should be checked anyway and you should become familiar with them. Please follow these steps to work with these files:

1) Open Windows Explorer and navigate to the /Enterprise directory in c:\inetpub/wwwroot

2) Navigate to the /EnterpriseASP directory.

3) Open the web.config file and make sure that all of the paths and settings in this file correspond to the actual locations where you installed the files, and make sure that the connection string properly matches the location of your database and the name of your default instance.

3) Navigate to the /EnterpriseWS directory.

4) Open the web.config file and make sure that all of the paths and settings in this file correspond to the actual locations where you installed the files, and make sure that the connection string properly matches the location of your database and the name of your default instance.

5) For the external applications like the Shopping Cart, POS System, and CRM System, the connection strings are in a file called common.ascx or can also be in the web.config file for that sub-application (if it has a web.config file) Please make sure that the paths and the connection strings in these files properly correspond to your installation as well.

Initial Set-up is now complete!

If you have done everything right, you should be able to enter this url in a browser and the applications login screen should load: http://localhost/enterprise/enterpriseasp/

If the login screen does not appear, please review the installation instructions again in great detail and review the "Troubleshooting" section of this help system. Typically, SQL Server errors mean that you either didn't install SQL Server 2005 properly (This is completely covered in an earlier help topic) or you did not properly adjust the web.config file. If you carefully read the error messages, it usually tells you exactly what the problem is and where. If it mentions a machine.config file and or says something about virtual directories, then you did not do the above steps properly and the virtual directory settings need to be reviewed.

For the greatest chance of success, this installation should be done by someone familiar with installing, configuring and maintaining Dot Net 2.0 Web Based applications.

Important Note! The application, as shipped, will run without having to be compiled. Please install, run, and troubleshoot the application from the browser before attempting to run it from Visual Studio 2005 or trying to compile it.

Compiling the Integral Accounting Enterprise Application:

Please note that the Integral Accounting Enterprise System is shipped completely compiled, so if you followed the installation instructions carefully and installed the system to it's default locations (Which is required by Technical Support) you can run the system without re-compiling.

During your first installation, you MUST run the program and test it BEFORE doing your first compile, since this would help isolate any installation issues.

You are going to need to compile the Enterprise Application when you make changes to the code, split the application or in some cases when the application is moved to difference servers.   Before attempting the compile, please review and be familiar with the common problems list in the Trouble Shooting Guide in the help system.

To compile the Integral Accounting Enterprise Application please follow these instructions: 

1) Navigate to the /Enterprise directory in c:\inetpub\wwwroot

2) Double-click on "Enterprise.sln" and Visual Studio 2005 should open

3) Sometimes when you open the solution, it will ask you to verify the connection properties. Enter all of the information that you used during the set-up of the software, namely the server location (should be (local) ), the instance name, the user (enterprise) the password (entx!2003n) and the database name (enterprise). After entering this information, press the "Test Connection" button. If this fails, then either you entered some wrong information or the SQL Server and Database installation was not done correctly.

If the Solution in Visual Studio2005 can not connect to the database, then the SQL Server 2005 CLR is not going to be configured and installed in the database properly, and every time the application attempts to access the CLR it will fail with an error like "Could Not Find Stored Procedure XXX_XXXCLR"

This is another important reason why you should use all of the default locations that we specify until you are 100% familiar with this application and all of the new Visual Studio 2005 / SQL Server 2005 features like putting code into the CLR.

4) To compile the application, you select the "Build" options from the top of the screen, then select "Rebuild Solution"

The application will now re-compile. You should re-boot the computer or restart IIS before accessing the newly re-compiled application.

Moving the Applications:

Once your initial application is deployed, you may want to move the various layers to other servers. We strongly recommend against this, and you should not do this,  until you completely understand how the layers inter-operate, how the system is designed and functions.

Each of the Integral Accounting Enterprise Layers can be deployed on a separate server or on any combination of servers by simply adjusting the web.config and/or app.config file, which is what the applications use to find each of the layers. So, for example, if you were to move the SQL Server from (LocalHost) to (NewServerName), you would have to update the web.config and/or app.config files for each of the layers to point to the new server. The same applies to the web services layer, of you were to move the web services layer to a different server other than LocalHost, you would have to adjust all of the web references to point to the new web service layer location in the web.config and/or the app.config file.