How to set up Application Server in Microsoft Dynamics SL

Article translations Article translations
Article ID: 848124 - View products that this article applies to.
Expand all | Collapse all

TechKnowledge Content

Setting up an Application Server

To set up an Application Server in Microsoft Dynamics SL or in Microsoft Business Solutions - Solomon, define an Application Server configuration that controls how the Application Server processes requests. The configuration consists of:

Application Server name - must be the same as a Solomon user ID that is defined in User Maintenance (95.260.00).

Application Server parameters - polling interval (how often to check for new processing requests), e-mail profile (used to receive requests, send responses via e-mail), temporary file directory, and log management settings (when to begin overwriting existing log information with new information).

Application Server options - how the Application Server should handle report routing and requests that did not process successfully (i.e., incomplete requests).

Application Server groups and users - the Solomon IV groups and users who can submit requests to the Application Server.

To set up an Application Server

1. Define a user ID and password for the Application Server in User Maintenance. See the System Manager online help or user guide for more information.

Note - This user ID should be set up with access rights to the Application Server (96.010.00) screen in addition to any screens or reports that Solomon Desktop will be submitting requests through.

2. Start the Application Server Administration Wizard. To do this, Choose Module | Application Server | Add New Server Wizard or Choose Module | Application Server | Server Administration and click Add Server. Application Server Administration Wizard (96.070.00) displays.

3. Click Next. The window used to name the new Application Server displays.

4. Select the name of the Application Server from the list displayed, and click Next to continue. The window used to define Application Server polling, maximum requests allowed, e-mail, and temporary directory settings displays.

Note - If the Application Server name you want to use has not yet been defined, click Add User to access User Maintenance. Define the Application Server user name and password, close User Maintenance, and click Next to continue.

5. Type the number of the polling interval, in seconds, at Polling Interval (e.g., type 10 to specify that the Application Server should poll the request queue every 10 seconds for new requests).

6. Type the maximum number of requests the Application Server should allow at one time at Maximum Requests Allowed.

7. Type the Application Server's e-mail profile ID at Email Profile ID.

Note - The Application Server e-mail profile defined must be a valid Microsoft Exchange or Outlook profile (i.e., the machine where the Application Server will run must have a client installation of either Microsoft Exchange or Outlook and have a profile set up to access e-mail).

Note - For Application Server to function correctly, Outlook 2000 users must install Microsoft Collaboration Data Objects (CDO) during the Outlook 2000 installation. If Outlook 2000 has been installed without CDO, you must rerun the Office 2000 installation. Start the Office 2000 installation program, and select Add or Remove Features. Then, under the Microsoft Outlook section, select Collaboration Data Objects as the component to install and continue through the rest of the installation.

8. At Temporary Directory, define the directory path and name where the Application Server should store the temporary files it will generate during request processing. Use Browse to help locate the directory.

9. Click Next to continue. The window used to define Application Server logging options displays.

10. At Number of Entries, type the maximum entries the Application Server should retain in the log before it begins overwriting log information (e.g., type 1500 to have the Application Server begin overwriting with the 1501st entry).

11. At Number of Days, type the maximum number of days the Application Server should retain information in the log before it begins overwriting log information (e.g., type 15 to have the Application Server begin overwriting on day 15).

Note - If both entries are set to zero, the log will not be purged automatically and all entries will remain in the log until you purge them manually.

12. Click Next to continue. The window used to define when the Application Server should delete completed requests from the request queue displays.

13. Type the number of days (e.g., 10) the Application Server should retain completed request information in the request queue.

14. Click Next to continue. The window used to define e-mail report retention options displays:

Select "Delete reports after they have been emailed" to delete Solomon report files immediately after the report has been sent via e-mail to the correct recipients.

Select "Keep the reports in the temporary directory" to maintain the results of a report request in the Application Server temporary file directory even after the reports have been sent via e-mail to the correct recipients.

15. Click Next to continue. The window used to define how the Application Server should handle requests that did not finish processing (incomplete requests) displays:

Select "Automatically resubmit incomplete requests" to have the Application Server automatically resubmit incomplete requests for reprocessing.

Select "Leave in queue and flag as incomplete" to have the Application Server assign a Status of ''incomplete'' to the request and leave it in the request queue. The request can then be resubmitted or deleted from the ''View Request Queue'' screen.

16. Click Next to continue. The window used to identify the Solomon IV groups and users who can submit requests to the Application Server displays.

17. Select the Application Server group(s) at Groups.

18. Select the Application Server users at Users.

Note - If no groups and users are selected then any user can submit requests to the Application Server being defined.

19. Click Next to continue. The window used to identify whether or not the Application Server is the default Application Server for the groups and users identified in steps 17 and 18 displays.

20. Select all groups and users for which the Application Server should be the default Application Server.

21. Click Next to continue. The window used to complete Application Server setup displays.

Note - If one or more setup selections need to be changed, click Back until arriving at the incorrect selection, make the correct selection, and click Next until returning to the current window. Then continue with step 22.

22. Click Finish to complete Application Server setup and quit the Application Server Administration Wizard.

Additional Resources

1. For information on running Application Server, see Knowledge Base Article .

2. For information on changing Application Server properties and options, see Knowledge Base Article .

Keywords: create

This article was TechKnowledge Document ID: 135889

Properties

Article ID: 848124 - Last Review: June 8, 2012 - Revision: 4.0
APPLIES TO
  • Microsoft Dynamics SL 7.0
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Great Plains Solomon IV 5.0
  • Microsoft Great Plains Solomon IV 4.50
  • Application Server
Keywords: 
kbmbssolomondesktop kbmbsinstallation kbmbsmigrate KB848124

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com