Act for Web Tips

By Patricia Egen • May 23rd, 2016

ACT for the Web is a pretty cool application. It is a great way to access your ACT data from a browser which is convenient when you are not near your main computer. In the process of working with the tool, we’ve found a few tricks and recommendations on improving the installation and performance. I wrote it up in a document and thought I’d post it here as a blog article. Note – this is going to be long but the idea is you can reference it later or print it for future review.

Overview

The installation and configuration instructions in the recent ACT! Premium for Web Administrator’s Guides (shipped with the product) are actually pretty good. If you are Very Familiar with Windows Server administration and particularly the IIS and ASP.NET components you will do fine with just those instructions. These notes attempt to point out things to check and be aware of that are not explicitly mentioned in the Administrator’s Guide or are glossed over in that manual. Also, these notes reflect my experience with my own ACT! for Web installation and experience with our own customers but should by no means be considered to cover every variation possible of ACT! Premium for Web installations. In any case, consider the Administrator’s Guide a Must Read.

Also, anytime you run into a situation that is not covered in the Administrator’s Guide or these notes, remember the first place to check should be the ACT! KnowledgeBase on http://www.act.com.

ACT! Premium for Web is supported for installation on both Windows Server operating systems as well as Windows Desktop (Client) operating systems. Installation on a desktop operating system is not recommended for production use and I support that recommendation. However, I run ACT! Premium for Web on Windows 8.1 (a client operating system) for testing and demonstration purposes and it runs fine. These notes will point out differences in the client versus server operating systems and configurations where appropriate.

My experience is primarily with ACT! Premium for Web on Windows Server Server 2008 R2 and Windows Server 2012 both 2012 and 2012 R2.

These notes assume that this is an ACT! Premium for Web installation where the web server is the same machine as the SQL data base server. If the installation is being split, then it is more work and there are other considerations necessary in configuring the web server and the ASP.NET impersonation user ID. The Administrator’s Guide goes over some of those considerations. All of our ACT! Premium for Web installations have been single server setups.

Preparation

ACT! Premium for Web depends on the Microsoft IIS (Internet Information Server) component of the Windows operating systems and also the ASP.NET component. These components serve as the platform on which the web component operates. ACT! Premium for Web will not function correctly if these components are not installed and enabled.

IIS is installed by default on most Windows Server 2003 (and 2000) installs. IIS is usually NOT installed by default on most Windows desktop installs. The ASP.NET component also may or may not be installed by default along side IIS. Verify or install as follows:

Windows Server
– IIS and ASP.NET are most easily installed using the “Manage Server” tool. They are both installed by adding the “Application Server” role and the Web Server role to the server. Add these role via “Manage Your Server” if they arenot already displayed.  Also, in the Mange Server Features dialog, drill down into the highest level of .NET shown (usually 4.0 or 4.5 on these levels of Windows Server) and make sure that the ASP.NET feature is installed.  Check the box and let the Manage Server tool do its update if you made any additions.
– Sometimes an IIS installation or installation of a service pack or security patch will turn off the ASP.NET extension in IIS as a security exposure. Well, it actually is a security exposure, but is required for ACT! Premium for Web so get over that and make sure it is turned on. Either select “Manage this application server” from the “Manage Your Server” tool, or start the IIS Manager tool directly from Start/Administrative Tools/IIS Manager. Once there, expand “Internet Information Services” the “local computer” then click “Web Service Extensions” in the tree view. This will show the installed extensions and whether they are enabled or prohibited. Any line that starts “ASP.NET” needs to show “Allowed”. If it shows Prohibited, select that entry and click “Allow” in the right hand window.

If any roles or features were added I suggest a re-boot of the server at this point before attempting to install any Act! software just to make sure that everything is updated at the Windows level.

Windows Desktop (Window 8.1 and Windows 10 in particular)
– IIS and ASP.NET are installed via the “Turn Windows features on or off” option on the “Programs and Features” object on the Control Panel or Settings panel. On the main panel, make sure “Internet Information Services” is checked and drill down and make sure that at least “World Wide Web Service” is checked.
– ASP.NET will be installed and enabled as part of the installation of the .NET Framework later.

The .NET 4.0 Framework is a built-in component of both current Windows Server versions and Windows Desktop versions.  If the .NET Framework 4.0 (or 4.5 or 4.6 depending on your Windows version) is not clicked as Installed then again use the “Turn Windows features on or off” functino to enable it.

Once IIS and the .NET Framework 4.0 are installed, I recommend running a Windows Update and get any and all security patches and updates for both the base Windows and the IIS and .NET Framework components.

Some customer IT administrators may want to see ACT! Premium for Web installed into a non-default IIS web site or configuration. This is possible but the ACT! Premium for Web installs to the Default Web Site using port 80 and to virtual directory /APFW. It can be moved later (see the ACT! Knowledge Base item 14868).  There is some configuration changes that can be made and I will mention them later.

Installation

The Administrator’s Guide recommends creating the ASP.NET impersonation account before installing the software. I find it does not really matter when you do that task. If you are doing an upgrade installation, the impersonation account already exists. If necessary, ask the old installation of ACT! what the account logon is if you do not already know it (use the Tools/Web Site Administration panels). Potentially you will have to reenter the login ID and password on the new installation. If this is not an upgrade installation, you can wait and create the account after you have the ACT! software installed. I will go over hints and tips about the impersonation account later.

Make sure you are logged on the server as an administrator. If the server is not a Domain controller, a local administrator account is sufficient. If the server is a Domain controller, you really need to be a Domain Administrator. I won’t debate the issues of using a Domain controller as the ACT! Premium for Web server. Many shops have a small number of servers and the Domain controller is either the only server or the only server accessible from the external internet, so practicality needs to override other desires sometimes. I have successfully installed and configured ACT! Premium for Web at the server console, logged on via Administrative Remote Desktop, and via other remote control software (GoToMeeting and GoToAssist being used most heavily).

If this is an upgrade, I recommend making a final backup of existing ACT! data bases using the old version before installing the new version. This is the best way to ensure that you can restore these backups with the old version of ACT! later if you find you need to fall back.

Let the installer guide you through the installation of the appropriate SQL Server version and the actual ACT! Premium for Web code. If this is an upgrade from one version of ACT! Premium for Web to another, follow the instructions in the Administrator’s Guide as to whether a deinstall of the previous version is required before the install of the new version.

At the point where the code is installed, bring up the ACT! Premium for Web GUI on the server. Go through the registration process, then verify that you can open the new ACTxDEMO data base. Any problems at this point get diagnosed the same way one would go about troubleshooting an installation of ACT! desktop. We want to ensure that the program code and SQL Server instance are communicating.

If this is an upgrade, now is the time to open the old version data bases and upgrade them to the new schema versions. This has to be done before you attempt to access the data bases from the web server, as the web server will blow up big time when it hits a schema mismatch.

Configuring the Web site

Now comes the point where ACT! Premium for Web is different from the desktop install and that is configuring the web server and configuring data bases to the web site.

Make sure you have a data base that is working with the ACT! GUI before continuing to attempt to configure the ACT! Premium for Web web site. Make sure the data base is marked as Tools/Database Maintenance/Share Database. Use the ACTxDEMO data base if necessary. I usually configure the ACTxDEMO data base to the web server, at least initially, to support testing of the ACT! Premium for Web installation. It can be removed later if having it publicly exposed is not desired.

The biggest hurdle in configuring the ACT! Premium for Web web site is the first two tabs – Web Server and User Account. If this is an upgrade, everything previously configured should carry forward. Just do the two tests as described in the Administrator’s Guide.

If the Web Server test fails, make sure that IIS is installed, the service is running (do Start/Run/IISRESET to see if it can be stopped and restarted), and that ASP.NET is allowed in the IIS Manager tool as described earlier. Usually these fixes will get you past this part. If necessary, see if the IIS server responds to anything. Open up a web browser on the server and type http://localhost. You should get a screen that you web site is under construction (client OS), or the base welcome page (usually a Small Business Server variant). This says that IIS is there and listening at least.

The next step is to create and set the ACT! for Web impersonation account. The required properties of the account are described in the Administrator’s Guide. But, basically what works are the following. If the machine is a client OS (Windows XP), you probably should use the user ID and password that you use to log on the system. On a server system, it depends if the machine is a stand-alone server, a member server in a domain, or a domain controller. If the machine is a stand-alone server or a member server, what I have found works best, if the data base server is the same machine as the web server, is to create a local Administrators account on the machine (not in the Domain/Active Directory). This account then has the run of the machine but can’t get to resources outside the particular server. I usually call my ids ActForWebUser and set the attributes “Password never expires” and “User cannot change password”. If the server is a Domain Controller, then a local administrator account is not an option, so create a Domain (Active Directory) user and make it a member of the Administrators group and the Domain Users group but NOT a member of the Domain Admins group.

So enter the user ID and password into the User Account tab. Remember that for a local administrator’s account, the domain will be the computer name. Click “Test” and see if it works. If the test fails, see the Administrator’s Guide. You may need to change permissions in either the Windows Registry or the file system folders where the ACT! Premium for Web files are installed. This is the APFW directory under the ACT for Web directory created by the installer (usually C:\Program Files (x86)\Act for Web\APFW). However, if the user ID is correctly set up as a machine administrator this should not be necessary.

If you get this far, try adding a data base to the web site using the Add/Remove Database tab. As I said earlier, I usually try adding the ACTxDEMO data base since it is pretty much a known entity. Now try logging on to ACT! Premium for Web via the web browser. Go to http://localhost/apfw . You should get the ACT! Premium for Web log on screen. Select the ACTxDEMO data base and you should be able to log on as Chris Huffman. Then try adding the real customer data base and try logging on to it.

One thing is, sometimes these configuration changes don’t seem to “take” immediately. Try a Start/Run/IISRESET to restart the IIS service tasks. That usually clears up things that should be dynamic but aren’t. I have seen situations where the web site just won’t come up after configuring the ACT! Premium for Web web site administrator. At that point what has cleared things up is a reboot of the server. Try that if all else fails.

Now try accessing the web server from somewhere else in the network. Now that you know the server works locally you are in a position to fight other network connectivity and potential firewall issues.

 

 

Leave a Comment

« | Home | »

  • Been sent a support request?

    Click here to enter your ticket number: Ticket

  • Our Business

    Our Mission
    Bridging the gap between technology and business processes. Provide quality business consulting, with an emphasis on technology, maintain superior client relationships and enjoy the trust and respect of our clients

  • Us in a nutshell

    Swiftpage
    CRM applications
    Data Conversion
    Custom Programming
    SQL Experts
    Lotus Notes
    Quotewerks
    Stonefield Query
    MS Office Programming
    Business analysis
    Process Workflow
    Social Media and SEO
    Linux, Mainframe
    Been there, done that



  • Facebook Like Us!