Application Servers

The Application Server component handles all application operations between client computers and databases. It increases the scalability of the product by maintaining the client connections and their state, thereby relieving the Database server of a huge load.

Application Server uses connection Objects to create a temporary connection between various clients and databases and executes client requests. Once a request is executed, the connection is closed and the Object is returned to the connection pool.

Preinstallation Tasks

Identify and install the prerequisite software. See Software Requirements by Component — Application Server.

  • If you are installing Application Server on a Windows NLBS cluster and connections to Application Server are made through HTTP (with load balancing), follow these steps:

    1. Ensure that:

      • Application Server is installed on all NLBS host machines.

      • Virtual root names of Application Server are identical on all servers.

    2. Execute sproc_AddMachinestoNLBS with the following parameters:

      • Parameter1: @tNLBS: This parameter represents the virtual IP address of the NLBS Cluster.

      • Parameter2: @tMachines: This parameter contains the list of computer names that are part of the NLBS Cluster.

        The computer names must be separated by the comma delimiter. For example, Exec sproc_AddMachinestoNLBS N'172.17.32.100', N'HostMac1, HostMac2'

    3. Ensure the following are configured in the Windows Firewall Settings dialog box:

      • In the Exceptions tab, select the COM+ Network Access, Distributed Transaction Coordinator, and COM Surrogate check boxes.

      • Select the Notify me when Windows Firewall blocks a new program check box.

  • When connecting to Application Server using HTTP, we recommend that you modify the settings in the Web.config file as indicated below:

    <httpRuntime
executionTimeout="900"
maxRequestLength="5248"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="2000"
enableVersionHeader="true"
/>

    These settings are explained below:

    • executionTimeout="[seconds]": This attribute represents the time (in seconds) before a request automatically times out.

    • maxRequestLength="[KBytes]": This attribute indicates (in kilo bytes), the maximum size for a request that can be accepted.

    • useFullyQualifiedRedirectUrl="[true|false]": This attribute indicates whether the URL for Client redirects must be fully qualified.

    • minFreeThreads="[count]": This attribute specifies the minimum number of free threads to enable the execution of new requests.

    • minLocalRequestFreeThreads=" [count] ": This attribute specifies the minimum number of free threads to enable execution of new local requests.

    • appRequestQueueLimit="[count]": This attribute specifies the maximum number of requests that can be queued for the application.

    • enableKernelOutputCache="[true|false]": This attribute indicates whether the http.sys cache must be enabled on IIS 7.5 and higher versions. By default, this value is True.

    • enableVersionHeader="[true|false]": This attribute indicates whether the X-AspNet-Version header must be output with each request.

    The Web.config file is located in the folder in which Application Server is installed.

     

Set Up Application Servers

  1. In the Installation menu, click App Servers. The Application Server Settings screen is displayed. Closed

    Application Server Settings

  2. Click Add to add a line to the Settings screen.

  3. Select an appropriate Action. The following Action values are available:

    • None – Performs no action.

    • Install – Performs a fresh installation or upgrade of a component. You can install or upgrade multiple components at the same time.

    • Uninstall – Removes all subcomponents on that machine and uninstalls the component from Programs and Features.

    • Reinstall – Retries to install a subcomponent.

    • Add – Installs an additional component on the computer where one or more components already exist. You can add only one component at a time.

    • Remove – Uninstalls a single component. You can remove only one component at a time.

    Optional: Click Select All to set the Action field to Install for all components listed on this screen. Click Unselect All to set the Action field to None.

  4. Enter the Machine Name for the component to be installed.

  5. Select a Database Link for Application Server.

  6. Click Options (ellipsis) icon to view and edit the Options form.

    App Server Options

    Options Fields
    Field Description
    Allow HTTP Connection Enables a connection from Client to Database through HTTP or HTTPS. The check box is selected by default.
    IIS Virtual Root: If Allow HTTP Connection is selected, the IIS Virtual Root text box is enabled and you can change the name of IIS virtual root.
    If the check box is cleared, the IIS Virtual Root text box remains blank and Application Server uses DCOM configuration.

    For a Trusted log on: <Application Server Name>_Trusted.

    This virtual root is used for authenticating Trusted Security Users over HTTP. This virtual root is created for users who will log on to Application Server using a trusted connection. The user will not be required to specify information in the above format to log on to Application Server. This information will be automatically interpreted when the user logs on to the computer on which Application Server is installed.

    For an Application or Custom log on: <Application Server Name>.
    Main Database Main database and name of the database server selected in the Database Settings screen.
    Destination Directory The destination directory of the Main Database File (MDF) for Application Server.

  7. Click OK to save changes on the Options form. The form is closed.

  8. Click copy icon to copy a line. Edit the copied line as needed.

  9. Click Delete icon to delete a selected line.

  10. Click Test to ensure the setup for the corresponding line is correct. If a test on a particular line fails, check all associated fields and click Test again.

  11. If all tests pass, click right arrows.

Note: Trace logs for Application Server must be enabled only from Talisma Trace Client available in the Application Server installation folder. While trace logs for other components can also be enabled from this location, Application Server traces cannot be enabled from Talisma Trace Client available in other locations.

 

Perform Other Operations

  1. From the Start menu, select Programs, Administrative Tools, Component Services. The Component Services screen is displayed.

  2. Browse to the following path: Console Root/Component Services/Computers/My Computer/COM+ Applications

  3. Right-click ApplicationServer, and select Shut down from the shortcut menu.

  4. Right-click ApplicationServer, and select Start from the shortcut menu.

Notes:

Ensure that Application Server is restarted in the following scenarios:

  • When a CampusNexus CRM license is updated.

  • When a database is configured after the installation of Application Server.

  • When the date or time has been modified on Application Server.

  • When one or more of the following values are modified in the TalismaObjectAssembly.Config file, which is located in the Talisma Shared folder:

    • Compression size
    • Poll Interval
    • Pool Size
    • Internal Account Password

 

  1. From the Start menu, select Run. The Run dialog box is displayed.

  2. Type iisreset in the Open field.

  3. Click OK. The IIS Service is stopped and restarted.

 

By default, Application Server is configured to run using an interactive account, which is for the User who is currently logged on. It is recommended that you configure Application Server to run under an Account that has been granted administrative privileges. To do so:

  1. From the Start menu of the Application Server computer, select Settings, Control Panel. The Control Panel is displayed.

  2. Double-click the Administrative Tools icon. The Administrative Tools screen is displayed.

  3. Double-click the shortcut for Component Services. The Component Services screen is displayed.

  4. Expand the following nodes: Component Services, Computers, My Computer, COM+ Applications. All COM+ applications are listed.

  5. Right-click Application Server, and select Properties from the shortcut menu. The COM+ Application Server Properties dialog box is displayed.

  6. Select the Identity tab.

  7. In the Account area, select the This user option, and click Browse to locate a User who has administrative privileges on the Application Server computer.

  8. Specify a password for the User in the Password field.

  9. Type the password again in the Confirm Password field.

  10. Click OK. Application Server is now configured to run using a local administrator account.

If you have installed iServices, carry out the following steps for each iService:

  1. Select an iService component node.

  2. Right-click on the node, and select Properties from the shortcut menu. The relevant Properties dialog box is displayed.

  3. Click the Identity tab.

  4. Select the This User option.

  5. In the User field, click Browse to select the domain User name.

  6. In the Password field, type the password of the domain User account.

  7. In the Confirm password field, type the password you have specified in the Password field.

  8. Click OK. The Properties screen is closed.

  9. Start the Service of the iService component node. To do so, right-click on the iService component node you have selected in step 1, and select Start from the shortcut menu.

  10. Close the Component Services screen.

 

You can create a local user account so that it is accessible even without logging on to the computer. To do so, follow these steps:

  1. From the Start menu, select Programs, Administrative Tools, Computer Management. The Computer Management screen is displayed.

  2. Browse to the following path: Computer Management/System Tools/ Local Users and Groups/Users.

  3. Right-click in the right pane and select New User from the shortcut menu. The New User dialog box is displayed.

  4. Type the required details.

  5. Clear the selection for the User must change password at next logon option.

  6. Select the User cannot change password and Password never expires options.

  7. Click Create.

The local user account is created on the computer on which Application Server is installed.

 

On the computer where Application Server is installed, the value of the cacherefreshtime tag in the application.config file is set to 180, which indicates that the Application Server cache is refreshed every 3 minutes. The file will be available in the Installation folder.

It is recommended to set the value of cacherefreshtime Key to 14400 to ensure that the Application Server cache is not refreshed frequently.

<add key="CacheRefreshTime" value="14400" />

When the value of the cacherefreshtime tag is set to 14400, the Application Server cache is refreshed at the interval specified in this tag. Operations performed in Business Administrator such as creation of Users, Teams, Rules, and enabling Permissions to Users and so on will be reflected in Web Client only when the Application Server cache is refreshed.

For the operations performed in Business Administrator to be reflected immediately, perform the following steps on the computer where Application Server is installed:

  1. Reset IIS.

  2. Shut down and start the Application Server COM + Component. To do so:

    1. From the Control Panel, open Administrative Tools, and double-click Component Services.

    2. Navigate to the Component Services, Computers, My Computer, COM+ Applications node.

    3. Select the ApplicationServer node.

    4. Right-click the ApplicationServer node and select Shut down from the shortcut menu.

    5. Right-click the ApplicationServer node and select Start from shortcut menu.

 

You can configure additional connections to the database.

  1. From the Start menu, select Settings, Control Panel.

  2. Double-click Add/Remove Programs.

  3. From the list of programs, select Application Server <version number>.

  4. Click Change/Remove. The Add/Remove/Reinstall dialog box is displayed.

  5. Click Configure Databases. The Configure Database Servers page is displayed. Configure additional HTTP or DCOM connections to Application Server.

 

The file size for compression can be configured for Application Server and Client. By default, compression is disabled when connections to Application Server are made over a Local Area Network (LAN). To enable compression:

  1. On the computer where Client is installed, run Regedit from the command prompt. The Registry Editor is displayed.

  2. Browse to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Talisma\Common\ConnectionParameters\LAN

  3. Right-click the DWORD values Request and Response, and select Modify from the shortcut menu. The Edit DWORD Value dialog box is displayed.

  4. Specify the required data size in the Value data field, after selecting Decimal in the Base area. Compression is enabled for DCOM connections. Requests and responses that are greater than or equal to the specified size are compressed.

Notes:

  • By default, the value for the Request and Response DWORDs for the LAN key is 0, indicating that compression is disabled. Setting a value greater than 0 enables compression.

  • Values specified in the Value data field must be in bytes, indicating the file size for which compression must be enabled.

By default, data greater than or equal to 1024 bytes will be compressed when connections to Application Server are made over HTTP. You can modify this value. To do so:

  1. Browse to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Talisma\Common\ConnectionParameters\Internet

  2. Modify the DWORD values Request and Response, and specify the required data size in the Value data field, after selecting Decimal in the Base area.

 

Postinstallation Tasks

On the Application Server and Database Server computers, perform the following steps:

  1. Right-click the My computer icon, and select Manage from the shortcut menu. The Server Manager screen is displayed.

  2. In the left pane, navigate to the Configuration, Local Users and Groups, Groups node.

  3. In the right pane, right-click the Distributed COM Users group, and select Add to Group from the shortcut menu. The Distributed COM Users Properties dialog box is displayed.

  4. Click Add. The Select Users, Computers, or Groups dialog box is displayed.

  5. In the Enter the object names to select area, specify the names of the users you want to add to the Distributed COM Users group. Use a semicolon (;) to separate the names of multiple users.

  6. Click Check Names.

  7. Click OK. The users are added to the group.

  8. Click OK.

 

On the computer on which Application Service is installed, perform the following steps:

  1. Click Start, Run, type gpedit.msc, and click OK. The Local Group Policy Editor is displayed.

  2. Navigate to Computer Configuration, Administrative Templates, System, User Profiles.

  3. Double-click Do not forcefully unload the users registry at user logoff.

  4. Select Enabled.

  5. Click OK.

  6. Close the Local Group Policy Editor.

  7. Restart the Application Server computer.