Installation

The Web Engine and the ISAPI Plug-In are delivered on the Sage 100 installation program. This article covers the installation process for the Web Engine and the ISAPI Plug-In. For installation information about installing Sage 100, refer to the Installation and System Administrator’s Guide, which is available on the Sage 100 documents page.

Before Installing the Web Engine

The Web Engine is primarily responsible for the merging of HTML pages with data. You must have Sage 100 installed before installing the Web Engine. The system requirements for running the Web Engine are the same as those for Sage 100. For a complete list of system requirements, refer to the Supported Platform Matrix. To access the matrix, see article ID 47649 in the Sage Knowledgebase at support.na.sage.com.

Before installing the Web Engine, decide on one of the following configurations for incorporating SSL technology in your Web pages:

  • Always use SSL encryption when redirecting requests to the Web Engine.
  • Use SSL encryption for redirecting requests to the Web Engine for select Web pages (such as the Shopping Cart Web pages), when the external request to IIS uses SSL encryption.
  • Never use SSL encryption when redirecting requests to the Web Engine.

Depending on which configuration you select, the bold portion of the URL in the sample MASISAPI.INI file below would differ. This URL resembles the URL to the Web Engine.

[Http Remappings]
www.example.com=http://servername:2953

[Https Remappings]
www.example.com=https://servername:2954

If you are configuring your system to always use SSL encryption or to use SSL encryption for select Web pages, you must generate an SSL certificate in a .pem file format before installing the Web Engine. For more information, see Generating an SSL Key.

Installing the Web Engine

After installing Sage 100, you are ready to install the Web Engine.

Note: You must uninstall your previous Web Engine before proceeding. Because your templates may be deleted or replaced, back up any templates, .htm files, and the IW folder before uninstalling.

To begin the installation process

  1. Click the applicable Sage 100 product from the installation Autorun screen, click Productivity Applications, and then click Install eBusiness Manager Web Engine to begin the installation.

  2. After the Welcome and Software License Agreement windows appear, the Web Engine Setup program prompts you to select a destination folder. Click Browse to locate a folder.

    The folder you select must not be the MAS90 folder. Sage 100 and the Web Engine can be installed on the same server, but must be installed to separate folders.

    Click Next to begin the installation process.

  3. Enter the port number to use for the Web Engine. By default, the port number used by the Web Engine is 2953.

    Make a note of the port number; you will need to enter it in the Port field for the Web Engine address in eBusiness Manager Options.

  4. After entering the port number, you are prompted to secure your connection between IIS and the Web Engine through SSL. If your connection between IIS and the Web Engine is already secure (using a fire wall, dedicated connection, or some other proxy), you do not need to connect using SSL; however, if your connection between the IIS and the Web Engine is through the Internet, SSL is strongly recommended.

    Note: Click No if you are not using SSL encryption for any of your Web pages.

    If you click No in the Question dialog box, go to the next step; otherwise, complete the following:

    1. Enter the SSL port number to use for the secure connection and then click Next. By default, the SSL port number used by the Web Engine is 2954.

      Make note of the port number. You will need to enter it in the SSL field for the Web Engine address in eBusiness Manager Options.

    2. Click Browse to browse to the location of your certificate file. The certificate must be in .pem format. Click Next.

      Note: For information on creating a .pem file, see Generating an SSL Key.

  5. Enter the Universal Naming Convention (UNC) path to the MAS90 folder for the installation you are making available for use with the eBusiness Manager module.

    For example, if your server's name is ACCOUNTING and the share point containing the MAS90 folder is APPS, you would enter \\ACCOUNTING\APPS\MAS90 and click Next. You can also click Browse to locate the MAS90 folder.

    Note: The MAS90 folder cannot be the share point.

    If you are installing the Web Engine on the same server, you must still specify the UNC path to the MAS90 folder, not the local drive path.

  6. If you are installing the Web Engine on a SQL server, the SQL Server Information window appears. Type the server name where SQL is running.
  7. After entering the path to the Application Server, you are prompted to select a program folder for the Web Engine program icon. Select an existing folder or type a new folder name and then click Next.
  8. When you are prompted to configure the Web Engine as a service:
    • Click Yes to run the Web Engine as a Service.
    • Click No to run the Web Engine as an Application.

    If you have completed running the Web Engine Setup program, and you want to change your configuration selection, you must uninstall the Web Engine, and re-run the Web Engine Setup program.

    Important! Before uninstalling the Web Engine, create a backup of any Web templates that you modified.

    To change or view your Web Engine configuration settings, you must stop the service.

  9. The Start Copying Files window opens. Review the settings listed and click Back to make changes or click Next to accept all.
  10. Click Finish.

Running the Web Engine

To run the Web Engine as a stand-alone application, select Start menu > All Programs > Sage > Web Config. Running the Web Engine in this manner requires a persistent user logon, and this user must have sufficient permissions to access the share point and all data on the Application Server.

Note: You must access Web Config before running the service for the first time.

Security on the Server

The server should be protected from unauthorized access, especially if the server is in an easily accessible area. Windows server provides two features for protecting a server: screen savers and lock workstation. Use either of these features to prevent users from accessing the server on which the Web Engine is running. When choosing a screen saver, select one with minimal functionality that requires little computation by the computer.

ISAPI Plug-In Setup

The ISAPI Plug-In is responsible for redirecting Internet requests to the Web Engine. You must have Sage 100 and the Web Engine installed before setting up the ISAPI Plug-In. For a complete list of system requirements, refer to the Supported Platform Matrix.

Note: Do not install the ISAPI Plug-In if an ISP is hosting your Web site.

To set up the ISAPI Plug-In

  1. Install the ISAPI Plug-In.
  2. Enable Web service extensions on the IIS server.
  3. Generate an SSL key.

Access to the Web Engine

The Windows server on which you install the ISAPI Plug-In must have access to the server running the Web Engine, which may be behind a firewall. For a description of this security configuration, see IIS Configuration Settings.

Before installing the ISAPI Plug-In, make sure you can access your Web site from a workstation that is not connected to the main network (for example, from home or another business).

Installing the ISAPI Plug-In

Follow these steps to install the ISAPI Plug-In.

Note: The ISAPI Plug-In should only be installed on a Windows Server operating system.

To install the ISAPI Plug-In

  1. Click Browse on the Sage 100 installation program. Open the ISAPI Plug-in folder on the Windows server. The ISAPI Plug-in folder contains the following .dll files:
    • libeay32.dll
    • masisapi.dll
    • openssl.dll
    • ssleay32.dll
  2. Copy the four .dll files to one of the following locations. Make sure that Web users have read-only access to the Scripts folder.
    • To install the ISAPI Plug-In for multiple Web sites, copy the .dll files to the Scripts folder under the Inetpub folder.
    • To install the ISAPI Plug-In for one Web site only, copy the .dll files to the Scripts folder under the root folder of your website. Create the Scripts folder if it does not already exist.

    Note: If your IIS hosts multiple Web sites, the ISAPI Plug-In does not need to be re-installed for each Web site if the .dll files are copied to the Inetpub\Scripts folder. The ISAPI Plug-In does need to be re-installed for each Web site if the .dll files are copied to the Scripts folder in the root folder of a Web site.

  3. To register the Server Side Include on IIS, in the Windows Control Panel, double-click Administrative Tools. Then Double-click Internet Information Services (IIS) Manager.
  4. In the Internet Information Services (IIS) Manager window, right-click the website used for eBusiness Manager and then click Properties.
  5. In the Properties window, click the Home Directory tab and click Configuration.
  6. In the Application Configuration window, click either the Mappings tab or the App Mappings tab, as applicable. Click Add.
  7. In the Add/Edit Application Extension Mapping window, in the Executable field, click Browse and browse to the location of the MASISAPI.DLL file.
  8. In the Extension field, type PVX. Accept all other default settings, and click OK.
  9. In the Application Configuration window, verify that PVX appears in the Application Extensions panel or the Application Mappings panel, as applicable. Click OK.
  10. Click OK to close the Properties window.

Installing the MASISAPI.DLL Plug-in for IIS for Windows Server

These instructions may vary depending on what versions of Windows Server you're using.

Note: The IIS Web Server roles must be fully configured and operational.

To install the MASISAPI.DLL plug-in

  1. Copy all the files in the ISAPI Plug-in folder found at the root of the Sage 100 installation program to the C:\Inetpub\Scripts folder in the IIS server. If the Scripts folder does not exist, create it.
  2. In the Windows Control Panel, click Administrative Tools. Double-click Internet Information Services (IIS) Manager.
  3. In the Internet Information Services (IIS) Manager window, on the Connections panel, double-click the server that is used for eBusiness Manager.
  4. Expand the Sites folder and select the website where the MASISAPI.DLL file will be installed.
  5. Double-click the Handler Mappings icon. In the Actions panel, click Add Module Mapping.
  6. In the Add Module Mapping window, enter the following:
    • Request path: *.pvx
    • Module: ISAPIModule
    • Executable (optional): Enter the path to the MASISAPI.DLL program file (for example, C:\Inetpub\Scripts\masisapi.dll)
    • Name: Sage EBM ISAPI
  7. Click Request Restrictions.

  8. On the Mapping tab, clear the Invoke handler only if request is mapped to check box.

    Note: Do not modify the settings in the Request Restrictions field.

  9. Click OK to close the Request Restrictions window.
  10. Click OK to add the Module Mapping.
  11. In the Do you want to allow this ISAPI extension message dialog box, click Yes.

Generating an SSL Key

To use the SSL capabilities of the Web Engine, create a .pem file that contains both the certificate and your private key in X509 format.

If you are unfamiliar with generating a certificate for secure transactions, consult a network consultant or business partner.

Modifying the ISAPI for Hosting Multiple SSL Sites

Because Host Header Names are not supported with Secure Socket Layer (SSL), if you are hosting multiple SSL Web sites from one Web server, the SSL proxy server will have difficulties locating the correct SSL Web site that a client browser requests.

To resolve this problem, if you are hosting multiple SSL Web sites from one Web server, you must distinguish each SSL Web site with a different TCP port and modify the MASISAPI.ini file. If there are multiple MASISAPI.ini files on the Web server, one for each SSL Web site, then modify each MASISAPI.ini file.

This procedure is not necessary if each Web server is hosting just one SSL Web site or none at all.

Note: You can place one MASISAPI.ini with all company information in the C:\Windows folder for all the SSL Web sites to share.

To modify the MASISAPI.ini file

  1. Open the MASISAPI.ini file in Notepad. The MASISAPI.ini file is located in the root folder of each website.

  2. Add an entry for the server and port that the proxy is using to access each SSL Web site. Use the following example to determine the entry to add:

    Example
    Your Web server hosts two SSL Web sites. The Web server's IP address is 123.4.56.789. The first SSL Web site uses port 441 and its URL is https://website1.example.com. The second SSL Web site uses port 442 and its URL is https://website2.example.com. Based on this example, type the following entry:

    [Http Proxy Remappings]
    123.4.56.789:441=https://website1.example.com
    123.4.56.789:442=https://website2.example.com

  3. On the File menu, click Save.